TABLE OF CONTENTS When modeling the specification perspective of a construct (system, subsystem, or class) and how the construct will satisfy its requirements, what elements and their relationships collaborate to constitute the construct, and how these elements interact to provide functionality to its users, consider the guidelines above and herein which ought to be applied within a use-case-driven, architecture-centric, iterative and incremental, and risk-confronting effort that is object oriented and component based. Successive iterations evolve, elaborate, and refine the work of previous iterations with more detail. Steps need not be sequential, but may be executed in parallel, where multiple efforts regarding the same system are carried out concurrently.
Within the specification perspective of the roadmap, specification elements include use cases, interfaces, and operations; realization elements include subsystems, classes, and collaborations; and construct elements include any elements that may constitute the construct or system, including subsystems, packages, and classes which evolve from proposed candidate elements to accepted actual elements. Properties capture constraints and characteristics of elements.
Every constituent of the roadmap is optional and should only be applied if it adds value to the body of knowledge concerning the construct and facilitates achieving the overall objectives of the effort within the specific context of the effort. Those constituents of the roadmap that are applied constitute a roadmap instance. Reference the examples above and the Project Management System example used in Chapter 4 as the result of applying structural and behavioral modeling within the context of the roadmap.
Different...
