Elaboration

From ESEEWiki

Elaboration in one sentence: Build the core architecture, resolve the high-risk elements, define most requirements, and estimate the overall schedule and resources.

As described in the Larman text on page 127, elaboration is the initial series of iterations during which, on a normal project:

• the core, risky software architecture is programmed and tested
• the majority of requirements are discovered and stabilized
• the major risks are mitigated or retired

Deliverables

• Domain Model Diagram - Elizabeth DeLouise

Identify conceptual classes, associations and attributes within your project domain. The diagram must use proper UML notation for a domain model diagram.

• Supplemental Specification - Elizabeth DeLouise

A complete set of the numbered FURPS+ requirements for your project. The functional requirement list must include requirements drawn out of the use cases. All requirements should be prioritized using a ranking system such as MoSCoW (http://en.wikipedia.org/wiki/MoSCoW_Method).

• System Sequence Diagrams (SSD) - Sylvia Luxenburg

SSDs for the most important (or most complex) use cases in the project. Proper identification and naming of system events, as well as correct UML notation is required.

• Deployment Diagram - Eric Pratt

A diagram that is representative of the hardware and software platform used to deploy your solution. Proper UML notation is required. Refer to Larman, Chapter 3 for details.

• Use Cases (80% complete) - Split Assignments

80% of all known use cases must be written out in detail using the fully dressed format, as discussed in class. Update the complete list of use cases.