What is the outcome of system design? The outcome is:

• A. The architecture, framework, and structure that supports the process in progressing to system implementation and testing.
• B. A roadmap that allows the testers to determine whether the system can withstand peak volume transactions.
• C. An assurance that the users will be totally satisfied with the system being designed.
• D. An accounting of all the costs involved with the selection, implementation and maintenance of a system.

Answer: (A)

System design yields the architectural blueprint that defines how the system will be built and how its components interact as it moves toward implementation and testing. It sets out the structure, the modules, the interfaces between them, data flows, and how nonfunctional requirements like performance, security, and reliability will be achieved. This blueprint guides developers during construction and provides a concrete plan for quality assurance to validate during testing.

Other options describe outcomes that belong to different stages or concerns. Planning for peak load is part of performance or capacity planning, not the overarching design blueprint. User satisfaction is an outcome of fulfilling requirements and UX design, not the structural plan itself. Cost accounting relates to budgeting and project management rather than the structural design that coordinates construction and verification.