You are on page 1of 7

Book for the slides

1) Systems Analysis and Design
Author: Elias M. Awad
2) Software Engineering, 6th edition
Author: Lan Sommerville
3) Software Engineering
Author: Roger S. Pressman


 The following activities are involved: i. Define sub-system interfaces: It defines the interfaces that are provided and required by each subsystem. 2. ii. Specify sub-system functionality: The specific functions provided by each subsystem are specified.System Design  It is concerned with how the system functionality is to be provided by the different components of the system. Identify subsystems: Different sub-systems that can individually or collectively meet the requirements are identified. iv. iii. Assign requirements to sub-systems: The requirements are assigned to subsystems.8 Sommerville p33 2 . Partition requirements: The requirements are analyzed and collected into groups. Fig. v.

System engineering process . 2.It involves the following phases: i) Requirements definition ii) System design iii) Sub-system development iv) System integration v) System installation vi) System operation vii) System evolution viii) System decommissioning Fig. . . .6 Sommerville 6th ed.The process involves consultation with system customers and end-users.Many different engineering disciplines may be involved in system engineering.It is intended to discover the requirements for the candidate system as a whole.It concentrates on deriving three types of requirement: 3 . i) System Requirements definition .

performance. iii) Sub-system development .The basic functions of the system are defined at an abstract level .g.It involves taking independently developed subsystems and putting them together to make up a complete system.The subsystems identified during system design are implemented.These are non-functional emergent system properties. iv) System integration . e.1) Abstract functional requirements .Detailed functional requirements specification takes place at the subsystem level. 3) Characteristics which the system must not exhibit . safety etc. availability.It is important to establish a set of overall system objectives ii) System design: as described in previous slide.. 2) System properties . 4 .

. vii) System evolution .The system’s computers are replaced with new faster machines.It may involve organizing training sessions for operators and changing the normal work process to make effective use of the new system.It means taking the system out of service after its operational lifetime. viii) System decommissioning .The system is put into operation after it has been installed. vi) System operation .System Engineering Process v) System installation . . the system is put into the environment in which it is intended to operate. and meet new requirements which have emerged. . The external environment of the system may change which may force to change the system. 5 .The system engineering activity should anticipate decommissioning and dispose the materials which are damaging to the environment.Large and complex software must have to evolve to correct errors in the original system requirements. and may reorganize itself.During this phase.

System Requirements . documenting. Software design specification .The description of the services and constraints are the requirements for the system. The system requirements document called functional specification should be precise. The specification add further detail to the system requirements specification.These are statements in a natural language plus diagrams. analyzing. and checking these services and constraints is called requirements engineering. of what services the system is expected to provide and the constraints under which it must operate. Requirements Engineering . User Requirements .It is the process of finding out.Requirements .It is an abstract description of the software design. 6 .It set out the system services and constraints in detail.

g. Functional requirements (Sommerville p100) 7 .. 3. and how the system should behave in particular situations. Domain requirements  These requirements come from the application domain of the system and that reflect characteristics of that domain. Functional requirements: ◦ ◦ These are statements of services the system should provide.Software system requirements are: 1. They may be functional or non-functional requirements. 2. timing constraints. how the system should react to particular inputs. Non-functional requirements:  These are constraints on the services or functions offered by the system. e.