When describing a system, explain why you may have to start the design of the system architecture before the requirements specification is complete.
Architecture design:
It is the high-level structures of a software system and also the discipline of developing such structures and systems. In this the structure includes the software elements, relations among them, and the properties of both elements and relations. It acts as the blueprint for the system and also the developing project, laying out the tasks that are required to be executed by the design teams.
Explanation of Solution
Importance of describing architecture before writing specifications:
- In a model of software development process, architecture design becomes the first page of the system as it describes how the system is organized as a set of communicating components.
- It is difficult to formulate the specifications written for the whole system as they increase the complexity. It becomes easier to define the specifications when the system is divided into subsystems. It defines the specifications and also put place it inside the respective subsystem.
- With this process of developing subsystems and their respective specifications, we can readily jump into the implementation stage. Few reasons behind the fact that the architecture has to designed before specifications are written, are as follows:
- It provides the structure.
- The subsystems are developed and their specifications can be written concurrently.
- It allows the manufacturing of hardware components by sub-contractors and also provides a model for system costing.
Want to see more full solutions like this?
Chapter 6 Solutions
Software Engineering (10th Edition)
Additional Engineering Textbook Solutions
Introduction to Java Programming and Data Structures, Comprehensive Version (11th Edition)
Artificial Intelligence: A Modern Approach
Java How To Program (Early Objects)
Differential Equations: Computing and Modeling (5th Edition), Edwards, Penney & Calvis
Java: An Introduction to Problem Solving and Programming (8th Edition)
Starting Out with Programming Logic and Design (4th Edition)
- A preliminary evaluation of software packages and vendors begins during the _____________ phase when the two or three strongest contenders are identified. a. system investigation b. system design c. system analysis d. feasibility analysisarrow_forwardExplain the goals of each typical system development stage.arrow_forwardGive an explanation of why, while creating a system, you may need to begin building the system architecture before the requirements definition is finished.arrow_forward
- Give an explanation of why, while creating a system, you may need to start building the system architecture before the requirements definition is complete.arrow_forwardExplain how an engineer who is in charge of producing a system requirements specification may keep track of the linkages between the system's functional and non-functional needs in order to ensure that the system meets all of its requirements.arrow_forwardPlease explain how a responsible engineer may keep track of the interdependencies between functional and non-functional needs when writing a system requirements specification.arrow_forward
- During the process of putting up a system requirements specification, you might be of assistance to an engineer by providing some instances of what they could do in order to keep track of the links between the functional and non-functional needs.arrow_forwardDescribe some methods an engineer who is tasked with developing a system requirements specification can use to keep track of the interconnections between the system's functional and non-functional requirements.arrow_forwardExplain how an engineer in charge of developing a system requirements specification may keep track of the relationships between functional and non-functional demands.arrow_forward
- When selecting a model for the system, what steps are followed?arrow_forwardDefining a system model is a complex task. What should be taken into account while developing the most basic of models?arrow_forwardSoftware/System Requirements AIM: To create a SOFTWARE/SYSTEM REQUIREMENTS SPECIFICATIONS An SRS is basically an organization's understanding (in writing) of a customer or potential client's system requirements and dependencies at a particular point in time (usually) prior to any actual design or development work. It's a two-way insurance policy that assures that both the client and the organization understand the other's requirements from that perspective at a given point in time. The SRS document itself states in precise and explicit language those functions and capabilities a software system (i.e., a software application, an eCommerce Web site, and so on) must provide, as well as states any required constraints by which the system must abide. The SRS also functions as a blueprint for completing a project with as little cost growth as possible. The SRS is often referred to as the "parent" document because all subsequent project management documents, such as design specifications,…arrow_forward
- Principles of Information Systems (MindTap Course...Computer ScienceISBN:9781305971776Author:Ralph Stair, George ReynoldsPublisher:Cengage Learning