Task
1. System Wide (Non-Functional) Requirements
a) Analysis of NFRs
Analyse the Case Study documents and determine the non-functional requirements (NFRs) or system quality attributes necessary to meet the needs identified in the Case Study. Consider the case study against the checklist provided. Prioritise the identified relevant NFRs, and specifically identify the 3-5 most important. For each of these high priority NFRs identify both benefit it confers and the cost of supporting it.
|
NFR
|
Trigger Question
|
Impact
|
Answer
|
Strategy
|
Priority
|
|
|
|
|
|
|
|
b) System Wide Requirement Document
Document and expand your analysis in a System Wide Requirement document. Use the System Wide Requirement Specification template provided in the Resources/Assignment 2 section of the subject Interact site. Make sure your SWRS document addresses:
i) System wide services (required system functionality not captured by a single use case) These are the ‘F' of FURPS+: e.g. auditing, printing, authentication).
ii) Non-functional requirements (system qualities). These are the URPS of FURPS+. Identify the specific NFRs you considered relevant from the checklist under the general URPS+ catego-ries.
iii) Any required system interfaces with external systems.
iv) Any business rules that must be applied.
v) Any constraints that will affect the design of the system. (Interfaces and constraints are the ‘+' of FURPS+)
2. Architecture Notebook
Analyse the Case Study documents and develop a candidate architecture to meet the functional and non-functional requirements you have identified in Assignment 1 and the system wide requirements identified in Task 1. Document this candidate architecture in an Architectural Notebook. Use the tem-plate provided in the Resources/Assignment 2 section of the subject Interact site. Make sure the architectural notebook addresses:
i) The key concerns driving the overall architecture. (These should correspond with the 3-5 most important NFRs you identified.)
ii) Any assumptions and dependencies that affect the architecture.
iii) Any architecturally significant requirements. (E.g. a requirement for persistent data may require access to a database)
iv) Decisions, constraints, and justifications that shape the architecture.
v) Architectural mechanisms used to implement requirements (e.g a database or XML file to im-plement a persistence requirement)
vi) Any architectural frameworks or patterns that will be applied
3. Component Diagram
Document your proposed architecture with a high level logical view showing functional and technical components in a component diagram.
4. Deployment Diagram
Document how your proposed architecture maps to the intended deployment environment with a de-ployment diagram showing how your functional and technical components will be distributed over hardware nodes.