- Information
- AI Chat
Systems engineering
Software Engineering (CS391)
Fayoum University
Recommended for you
Preview text
Systems engineering
The process of developing a system is a complicated one in which the components that will eventually make up the system are first created or acquired, and then they are combined to form the whole system.
The conceptual design serves as one end of the bridge, and the system requirements serve as the other.
development processes. The definition of business needs, as well as high-level functional and non-functional system requirements, takes place during the conceptual design phase. You can think of this as the beginning of the development process; hence, the steps indicated in Figure 19 will overlap with one another.
After the contracts for the system pieces have been agreed upon, the next step in the process is more extensive requirements engineering.
A model of the process of developing systems can be found in figure 19. The processes involved in systems engineering typically adhere to a "waterfall" process model, which is comparable to the model that I mentioned in Chapter 2. The waterfall model is still used in higher-level systems engineering processes, despite the fact that it is not suitable for most forms of software development. These processes are plan-driven and nonetheless adhere to the waterfall paradigm.
Processes that are driven by plans are utilised in the field of systems engineering since individual components of the system are produced in isolation. Many independent contractors are simultaneously working on several distinct subsystems. As a result, it is necessary to design the interfaces to these elements
before beginning the development process. Changes made during the development phase of a system that incorporates hardware and other equipment can be prohibitively expensive and, in some cases, even impossible to implement. Because of this, it is absolutely necessary to have a complete understanding of the system requirements before beginning work on the development or construction of the hardware.
The fact that various organisations use different nomenclature for each stage of the process is one of the characteristics of systems engineering that might be one of the most confusing aspects. There are instances when requirements engineering is included in the process of development, and there are other times when it is a stand-alone activity.
However, after the conceptual design stage, there are seven primary development activities that take place:
The process of developing, assessing, and documenting the high-level and business needs that were discovered in the conceptual design is what is referred to as requirements engineering. In Chapter 4, I went over the most significant activities related to requirements engineering.
There is a large amount of overlap between the architectural design phase and the requirements engineering process. Establishing the system's overall architecture is a part of the procedure that needs to be done.
finding all of the different parts of the system and having a knowledge of how they all fit together is a requirement.
communications with any other systems that are present in the environment. The "go live" step, which marks the completion of the process and allows users to begin utilising the system to support their work, is the apex of the process.
Even though the process as a whole is governed by a plan, the processes of requirements development and system design are intricately intertwined. The standards, as well as the high-level criteria
Systems engineering
Course: Software Engineering (CS391)
University: Fayoum University
