Object-oriented analysis and design

The ranking is done before Iteration 1, but then again before Iteration 2, and so forth, as new requirements and new insights influence the order. That is, the plan is adaptive, rather than speculatively frozen at the beginning of the project.

UP artifacts on Planning the Next Iteration

• The chosen requirements for the next iteration are briefly listed in an Iteration Plan. This is not a plan of all the iterations, only a plan of the next.
• If the short description in the Iteration Plan is insufficient, a task or requirement for the iteration may be written in greater detail in a separate Change Request, and given to the responsible party.
• The overall requirements ranking is recorded in the Software Development Plan.

2.4 What Artifacts May Start in Elaboration?

Artifact	Comment
Domain Model	This is a visualization of the domain concepts; it is similar to a static information model of the domain entities.
Design Model	This is the set of diagrams that describes the logical design. This includes software class diagrams, object interaction diagrams, package diagrams, and so forth.
Software Architecture Document	A learning aid that summarizes the key architectural issues and their resolution in the design. It is a summary of the outstanding design ideas and their motivation in the system.

Artifacts May Start in Elaboration? (cont.)

Artifact	Comment
Data Model	This includes the database schemas, and the mapping strategies between object and non-object representations.
Test Model	A description of what will be tested, and how.
Implementation Model	This is the actual implementation — the source code, executables, database, and so on.
Use-Case Storyboards, UI Prototypes	A description of the user interface, paths of navigation, usability models, and so forth.

End of the lecture 3