36
Non-Functional Requirements
We have a:
Non-Functional Requirements
36
Non-Functional Requirements
OOSE Text p.115-
36
Types of Requirements
Functional
Describe
requirements
Non-functional
requirements
Consists
36
Functional requirements
What
What
What
What
The
36
Non-Functional requirements
Transcend locality
Non-functional Requirements
Verifiable; Measured
All
If
Some
Some
36
36
36
10
Platform
Technology to be used
36
11
Development Process/Methodology
36
12
If
36
13
More attributes(2 of 2)
36
15
16
36
17
Consider:
Others
36
18
Supplementary Specifications
36
19
Supplementary Specifications
Complement to Use Cases
Within the Use Case: Typically, if the amount of interaction in use cases is
large, the majority of requirements will be captured here and there may be just a
few, global, non-functional requirements.
Keep a balance between using the use cases and non-functional requirements.
36
20
36
21
36
22
Number
Non Functional
Requirement Name
Description
Applies to Use
Case(s):
Exceptions
You may wish to categorize these (or not). If not, omit column.
36wish a priority column!
23
You may also wish to add columns. You may
Examples
NonFunctional
Category*
Number
Non Functional
Requirement Name
Description
Applies to Use
Cases:
Exceptions
Persistency
Where Student
Objects are
Updated
None
Security
System Administrator
actor needs to be
authenticated
Those Use
Cases that
access the
Profile Database
None
Availability
None
36
24
Supplementary Specifications
36
25
36
26
responsibilities, etc.
..
their responsibilities,
the analysis mechanisms / non-functional requirements that these
analysis classes need to implement (persistence, security, legacy,
) and
the collaborations required to support the functionality described
in the use cases.
Checkpoints
36
27
<<boundary>>
<<control>>
<<entity>>
36
<<entity>>
28
Glossary
Analysis Classes
Supplementary
Specification
Are
Are
Are
Are
Are
Use-Case Model29
Trace down through the Use Case specifications for each Use Case.
Are all responsibilities covered? Are domain / application objects
captured? Properties?
Verify the analysis classes and their relationships are consistent with
collaborations that they may support.
Very important that you evaluate your results at the conclusion of Use
Case Analysis.
36
30
36
31
36
(continued)
32
The class should not define any attributes and responsibilities that
are not functionally coupled to the other attributes or responsibilities
defined by that class.
The classes should offer the behavior the use-case realizations and
other classes require. (These will be methods later)
36
35