|Essential Artifacts (in order
||State at milestone
||One or more executable architectural prototypes
have been created to explore critical functionality and architecturally
significant scenarios. See the note below on the
role of prototyping.
||Updated and reviewed. New risks are likely to
be architectural in nature, primarily relating to the handling of non-functional
||Refined based on early project experience. The
development environment, including the process, tools and automation support
required to support the construction team will have been put in place.
||The tools used to support the work in Elaboration
||Created and baselined, including detailed descriptions
for the architecturally significant use cases (use-case view), identification
of key mechanisms and design elements (logical view), plus definition
of the process view and the deployment view (of the Deployment
Model) if the system is distributed or must deal with concurrency
Model (and all constituent artifacts)
||Defined and baselined. Use-case realizations
for architecturally significant scenarios have been defined and required
behavior has been allocated to appropriate design elements. Components
have been identified and the make/buy/reuse decisions sufficiently understood
to determine the construction phase cost and schedule with confidence.
The selected architectural components are integrated and assessed against
the primary scenarios. Lessons learned from these activities may well
result in a redesign of the architecture, taking into consideration alternative
designs or reconsideration of the requirements.
||Defined and baselined. Major data model elements
(e.g. important entities, relationships, tables) defined and reviewed.
Model (and all constituent artifacts, including Components)
||Initial structure created and major components
identified and prototyped.
||Refined, based on new information obtained during
the phase, establishing a solid understanding of the most critical use
cases that drive the architectural and planning decisions.
||Updated and expanded to cover the Construction
and Transition phases.
|Guidelines, such as Design
Guidelines and Programming Guidelines.
||The guidelines used to support the work.
||Iteration plan for the construction phase completed
Model (Actors, Use
||A use-case model (approximately 80% complete)all
use cases having been identified in the use-case model survey, all actors
having been identified, and most use-case descriptions (requirements
capture) have been developed.
||Supplementary requirements capturing the non
functional requirements are documented and reviewed.
||Tests implemented and executed to validate the
stability of the build for each executable releases created during the
||A baselined composition of the various mechanisms
and key software elements that embody the fundamental characteristics
of the test automation software system.
||State at milestone
||Updated if architectural investigations uncover
issues that change fundamental project assumptions.
||May be developed as a formal artifact; frequently
not formally maintained, evolving into an early version of the Design
||User Manuals and other training materials. Preliminary
draft, based on use cases. May be needed if the system has a strong
user interface aspect.
||The document templates used to develop the document