The System Architect (together with the Project Manager in Develop Iteration Plan) selects the system use cases (and scenarios derived from these) to be realized, and thus used to derive subsystem, process, and locality requirements. The selection of system use cases and scenarios (that are captured in the System Architecture Document as the System Use-Case View) is driven by the following: In general the impact on architecture is correlated to the criticality. However, it must be noted that there might be critical use cases that have little or no impact, and vice versa, and some ancillary use cases can have a big impact on the architecture, which makes it questionable from a business perspective. The System Architect's main concern is to select a set of use cases that ensures broad coverage (participation) of system internals, while still satisfying other constituencies. |