Summary

I l @ ve RuBoard

The iteration release plan prescribes schedules for all the increments of the system. The scenarios developed during analysis are the main input to this phase of development. The scenarios are examined and prioritized according to risk, importance to the customer, and the need to develop certain basic scenarios first. As each iteration is completed, risks are reevaluated and the project plan is updated as needed.

Earlier in the project life cycle, placeholder classes were created for the boundary classes for the system. Now, these classes must be finalized ”number of windows , window layout, and handling events from users. Classes typically are added to the model to facilitate the "how" of a system. Patterns provide the capability to reuse successful designs and architectures, which leads to more maintainable systems and increased productivity. As with any classes developed at this point in the life cycle, the classes created to instantiate the design pattern are added to the model and to the class diagram. Relationship design decisions include navigation, containment, refinement, and multiplicity implementation. Attribute data types and initial values are specified. Operation signatures are finalized. Analysis level diagrams are examined to determine if any inheritance may be added to the model. Operations in inheritance hierarchies are analyzed to determine if any polymorphism exists. If so, the operation is made either virtual or pure virtual.

The final step of design for an iteration is to add the methods that every good class needs ”for example, constructors, destructors, and copy constructors if the chosen language is C++. Rational Rose has very powerful code-generation capabilities. Code is generated based on information obtained from the diagrams, the specifications, and the options specified in the code-generation properties for each type of element.

Finally, the method bodies are implemented in the chosen language. Each iteration should be tested and documented before it is considered completed. The iteration is evaluated and any unmitigated risks are assigned to a future release.

I l @ ve RuBoard