When describing a system, explain why you may have to start the design of the system architecture before the requirements specification is complete.

Question

Want to see more full solutions like this?

Answer 1

Textbook Question

Chapter 6, Problem 6.1E

When describing a system, explain why you may have to start the design of the system architecture before the requirements specification is complete.

Expert Solution & Answer

Program Plan Intro

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?

Subscribe now to access step-by-step solutions to millions of textbook problems written by subject matter experts!

Students have asked these similar questions

Lab 07: Java Graphics (Bonus lab) In this lab, we'll be practicing what we learned about GUIs, and Mouse events. You will need to implement the following: ➤ A GUI with a drawing panel. We can click in this panel, and you will capture those clicks as a Point (see java.awt.Point) in a PointCollection class (you need to build this). о The points need to be represented by circles. Below the drawing panel, you will need 5 buttons: о An input button to register your mouse to the drawing panel. ○ о о A show button to paint the points in your collection on the drawing panel. A button to shift all the points to the left by 50 pixels. The x position of the points is not allowed to go below zero. Another button to shift all the points to the right 50 pixels. The x position of the points cannot go further than the You can implement this GUI in any way you choose. I suggest using the BorderLayout for a panel containing the buttons, and a GridLayout to hold the drawing panel and button panels.…

If a UDP datagram is sent from host A, port P to host B, port Q, but at host B there is no process listening to port Q, then B is to send back an ICMP Port Unreachable message to A. Like all ICMP messages, this is addressed to A as a whole, not to port P on A. (a) Give an example of when an application might want to receive such ICMP messages. (b) Find out what an application has to do, on the operating system of your choice, to receive such messages. (c) Why might it not be a good idea to send such messages directly back to the originating port P on A?

Discuss how business intelligence and data visualization work together to help decision-makers and data users. Provide 2 specific use cases.

Answer 2

Textbook Question

Chapter 6, Problem 6.1E

When describing a system, explain why you may have to start the design of the system architecture before the requirements specification is complete.

Expert Solution & Answer

Program Plan Intro

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?

Subscribe now to access step-by-step solutions to millions of textbook problems written by subject matter experts!

Answer 3

Textbook Question

Chapter 6, Problem 6.1E

When describing a system, explain why you may have to start the design of the system architecture before the requirements specification is complete.

Expert Solution & Answer

Program Plan Intro

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?

Subscribe now to access step-by-step solutions to millions of textbook problems written by subject matter experts!

Answer 4

Textbook Question

Chapter 6, Problem 6.1E

When describing a system, explain why you may have to start the design of the system architecture before the requirements specification is complete.

Expert Solution & Answer

Program Plan Intro

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?

Subscribe now to access step-by-step solutions to millions of textbook problems written by subject matter experts!

Answer 5

Textbook Question

Answer 6

Textbook Question

Answer 7

Expert Solution & Answer

Program Plan Intro

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.

Answer 8

Expert Solution & Answer

Program Plan Intro

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.

Answer 9

Expert Solution & Answer

Answer 10

Expert Solution & Answer

Answer 11

Program Plan Intro

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.

Answer 12

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.

Answer 13

Ch. 6 - When describing a system, explain why you may have...Ch. 6 - You have been asked to prepare and deliver a...Ch. 6 - Prob. 6.3E Ch. 6 - Prob. 6.4E Ch. 6 - Prob. 6.5E Ch. 6 - Prob. 6.6E Ch. 6 - An information system is to be developed to...Ch. 6 - Prob. 6.8E Ch. 6 - Prob. 6.9E Ch. 6 - Prob. 6.10E

When describing a system, explain why you may have to start the design of the system architecture before the requirements specification is complete.

Videos

Explanation of Solution

Want to see more full solutions like this?

Chapter 6 Solutions

Additional Engineering Textbook Solutions