Documente Academic
Documente Profesional
Documente Cultură
Practical Software Development using UML and Java Chapter 4: Developing Requirements
Lethbridge/Laganire 2005
A C
B D
Lethbridge/Laganire 2005
Lethbridge/Laganire 2005
Narrowed scope
browsing courses
Lethbridge/Laganire 2005
Lethbridge/Laganire 2005
Lethbridge/Laganire 2005
Functional Requirements
What inputs the system should accept What outputs the system should produce What data the system should store that other systems might use What computations the system should perform The timing and synchronization of the above
Lethbridge/Laganire 2005
Quality Requirementts
All must be verifiable Examples: Constraints on Response time Throughput Resource usage Reliability Availability Recovery from failure Allowances for maintainability and enhancement Allowances for reusability
Lethbridge/Laganire 2005
10
4.6 Use-Cases: describing how the user will use the system
A use case is a typical sequence of actions that a user performs in order to complete a given task The objective of use case analysis is to model the system from the point of view of how users interact with this system when trying to achieve their objectives. It is one of the key activities in requirements analysis A use case model consists of a set of use cases an optional description or diagram indicating how they are related
Lethbridge/Laganire 2005
11
Use cases
A use case should Cover the full sequence of steps from the beginning of a task until the end. Describe the users interaction with the system ... Not the computations the system performs. Be written so as to be as independent as possible from any particular user interface design. Only include actions in which the actor interacts with the computer. Not actions a user does manually
Lethbridge/Laganire 2005
12
Scenarios
A scenario is an instance of a use case A specific occurrence of the use case a specific actor ... at a specific time ... with specific data.
Lethbridge/Laganire 2005
13
Lethbridge/Laganire 2005
14
Registrar Actor
Student
Professor Actor
Lethbridge/Laganire 2005
15
Extensions
Used to make optional interactions explicit or to handle exceptional cases. Keep the description of the basic use case simple.
Lethbridge/Laganire 2005
16
Generalizations
Much like superclasses in a class diagram. A generalized use case represents several similar use cases. One or more specializations provides details of the similar use cases.
Lethbridge/Laganire 2005
17
Inclusions
Allow one to express commonality between several different use cases. Are included in other use cases Even very different use cases can share sequence of actions. Enable you to avoid repeating details in multiple use cases. Represent the performing of a lower-level task with a lower-level goal.
Lethbridge/Laganire 2005
18
Lethbridge/Laganire 2005
19
Lethbridge/Laganire 2005
20
Example (continued)
Use case: Open file by typing name Related use cases: Specialization of: Open file Steps: Actor actions 1. Choose Open command 3a. Select text field 3b. Type file name 4. Click Open
Lethbridge/Laganire 2005
21
Example (continued)
Use case: Open file by browsing Related use cases: Specialization of: Open file Includes: Browse for file Steps: Actor actions 1. Choose Open command 3. Browse for file 4. Confirm selection
Lethbridge/Laganire 2005
22
Example (continued)
Use case: Attempt to open file that does not exist Related use cases: Extension of: Open file by typing name Actor actions 1. Choose Open command 3a. Select text field 3b. Type file name 4. Click Open 6. Correct the file name 7. Click Open System responses 2. File open dialog appears 5. System indicates that file does not exist 8 Dialog disappears
Lethbridge/Laganire 2005
23
Example (continued)
Use case: Bro se for file (i cl sio ) Ste s: Actor actio s System res o ses 1. I the desired ile is not displayed, 2. Contents o directory is select a directory displayed 3. epeat step 1 until the desired ile is displayed 4. elect a ile
Lethbridge/Laganire 2005
24
Lethbridge/Laganire 2005
25
Lethbridge/Laganire 2005
26
Lethbridge/Laganire 2005
27
Lethbridge/Laganire 2005
28
29
Lethbridge/Laganire 2005
30
Lethbridge/Laganire 2005
31
subsystem 1 Requirements
xxxx xxxxxxx xxx xxxxxxxxxxx xxxxx xxxxxxxxxxxxx xxxxxxx xxx xxxxxxxxxxxxxxx
sub-subsystems
Requirements Requirements Requirements Definition Requirements Definition Definition xxxx Definition xxxx xxxxxxx xxxx xxxxxxx xxxx xxx Requirements xxxxxxx xxx Requirements xxxxxxx xxx xxxxxxxxxxx xxxxxxxxxxx xxx Requirements Requirements xxxxx Specification xxxxxxxxxxx xxxxxxxxxxx xxxxx Specification xxxx Specification xxxxx xxxxxxxxxxxxx xxxxxxxxxxxxx xxxxx Specification xxxx xxxx xxxxxxx xxxxxxxxxxxxx xxxxxxxxxxxxx xxxxxxx xxxxxxx xxxxxxx xxxx xxxxxxx xxx xxx xxx xxx xxxxxxx xxxxxxx xxxxxxx xxxxxxxxxxx xxxxxxxxxxxxxxx xxx xxx xxxxxxxxxxxxxxx xxx xxx xxxxxxxxxxx xxxxxxxxxxx xxxxx xxxxxxxxxxxxxxx xxxxxxxxxxxxxxx xxxxx xxxxxxxxxxx xxxxx xxxxxxxxxxxxx xxxxx xxxxxxxxxxxxx xxxxxxxxxxxxx xxxxxxx xxxxxxx xxxxxxxxxxxxx xxxxxxx xxx xxx xxxxxxx xxxxxxxxxxxxxxx xxx xxxxxxxxxxxxxxx xxx xxxxxxxxxxxxxxx xxxxxxxxxxxxxxx
sub-subsystems
Requirements Requirements Requirements Definition Requirements Definition Definition xxxx Definition xxxx xxxxxxx xxxx xxxxxxx xxxx xxx Requirements xxxxxxx xxx Requirements xxxxxxx xxx Requirements xxx Requirements xxxxxxxxxxx xxxxxxxxxxx xxxxx Specification Specification xxxxxxxxxxx xxxxxxxxxxx xxxxx Specification xxxx xxxxx xxxx xxxxx Specification xxxx xxxxxxxxxxxxx xxxxxxxxxxxxx xxxxxxx xxxxxxxxxxxxx xxxxxxx xxxx xxxxxxx xxxxxxx xxxxxxxxxxxxx xxxxxxx xxx xxx xxxxxxx xxxxxxx xxx xxx xxxxxxx xxxxxxxxxxx xxx xxxxxxxxxxxxxxx xxx xxx xxx xxxxxxxxxxxxxxx xxxxxxxxxxx xxxxxxxxxxx xxxxx xxxxxxxxxxxxxxx xxxxxxxxxxx xxxxx xxxxx xxxxxxxxxxxxxxx xxxxxxxxxxxxx xxxxx xxxxxxxxxxxxx xxxxxxxxxxxxx xxxxxxx xxxxxxxxxxxxx xxxxxxx xxxxxxx xxx xxxxxxx xxx xxxxxxxxxxxxxxx xxx xxx xxxxxxxxxxxxxxx xxxxxxxxxxxxxxx xxxxxxxxxxxxxxx
Lethbridge/Laganire 2005
32
Lethbridge/Laganire 2005
33
Lethbridge/Laganire 2005
34
Requirements documents...
The document should be: sufficiently complete well organized clear agreed to by all the stakeholders Traceability:
Requirements document rationale
1.1 XXXX .... because 1.2 YYYY
Lethbridge/Laganire 2005
Requirements document...
A. B. C. D. E. Problem Background information Environment and system models Functional Requirements Non-functional requirements
Lethbridge/Laganire 2005
36
Some changes are enhancements in disguise Avoid making the system bigger, only make it better
Lethbridge/Laganire 2005
37
Lethbridge/Laganire 2005
38