Software Requirement and Design by GROUP 3

1.     Suggest the most appropriate generic software process model that might be used as a basis for managing the development of the following systems:

a)     Anti-lock braking system  This is a safety-critical system so requires a lot of up-front analysis before implementation. It certainly needs a plan-driven approach to development with the requirements carefully analysed. A waterfall model is therefore the most appropriate approach to use, perhaps with formal transformations between the different development stages.

b)     Virtual reality system  This is a system where the requirements will change and there will be an extensive user interface components. Incremental development with, perhaps, some UI prototyping is the most appropriate model. An agile process may be used.

c)     University accounting system  This is a system whose requirements are fairly well-known and which will be used in an environment in conjunction with lots of other systems such as a research grant management system. Therefore, a reuse-based approach is likely to be appropriate for this.

d)     Interactive travel planning system  System with a complex user interface but which must be stable and reliable. An incremental development approach is the most appropriate as the system requirements will change as real user experience with the system is gained.

2.       Explain why it is essential to have two separate requirements engineering activities in the process.

Requirements specification	Requirement Modification
which is the activity of translating the information gathered during the analysis activity into a (formal or informal, depending on the underlying process used) document that defines a set of requirements	Information about component that is selected during component analysis is used to analysis requirement specification. Requirements are modified according to available components. Requirement modification is critical then component analysis activity is reused to find relative solution.
Two types of requirements may be included in this document:       a.    User requirements are abstract statements of the system requirements for the customer and end-user of the system        b.   System requirements are a more detailed description of the functionality to be provided.	Elements:  All significant requirements, whether relating to functionality, performance, design constraints, attributes, or external interfaces.

3.       Suggest why it is important to make a distinction between developing the user requirements and developing system requirements in the requirements engineering process.

There is a fundamental difference between the user and the system requirements that mean they

should be considered separately.

a)The user requirements are intended to describe the system’s functions and features from a user perspective and it is essential that users understand these requirements. They should be expressed in natural language and may not be expressed in great detail, to allow some implementation flexibility. The people involved in the process must be able to understand the user’s environment and application domain.

b)The system requirements are much more detailed than the user requirements and are intended to be a precise specification of the system that may be part of a system contract. They may also be

used in situations where development is outsourced and the development team need a complete

specification of what should be developed. The system requirements are developed after user

requirements have been established.

BY GROUP 3

NOOR SUFIATUL ASNI (1054)
FARAH NADIAH (1062)
NURRATUL AIN (1052)
SITI HAJAR  (1044)
INSYIRAH (1039)
NADIAH (1098)
FILZAH (1060)
FAIZAH (1036)
ARINAH (1059)