Scribd
Upload
7 views2 pages

Chapter 6

Uploaded by

yz1126
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
7 views2 pages

Chapter 6

Uploaded by

yz1126
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

Chapter 6

- Requirements engineering: The process of establishing and identifying the services that the customer
requires from a system and the constraints

- Types of requirement:
1- User requirements: Statements in natural language plus diagrams of the services the system
provides

2- System requirements: A structured document setting out detailed descriptions of the system’s
functions, services and operational constraints.

- Functional requirements:
- Statements of services the system should provide, how the system should react to particular inputs

- Describe functionality or system services.

- Depend on the type of software

- Functional user requirements may be high-level statements of what the system should do

-Non-functional requirements
- Constraints on the services or functions offered by the system such as timing constraints, and often
applied to the system as a whole

- Consists of product requirement (efficiency and security) , Organizational requirements(operational -


development) , external requirements(legalistive requirement)

-Metrics for specifying nonfunctional requirements


- speed, size, ease of use(training time) , Reliablity(mean time to failure , probablity of unavailability)

- Robustness (time to start after failure and events causes faliures)

- protablity(number of target systems)

Requirements engineering processes


1. Requirements elicitation;

2. Requirements analysis;

3. Requirements validation;

4. Requirements management.
Note: RE is an iterative activity

1- requirements elicitation and analysis:

find out about the application domain, the services that the system should provide, contains:

• Requirements discovery (The process of gathering information about the required and existing
systems)

- Contains Formal or informal interviews with stakeholders are part of most RE processes.

• Requirements classification and organization,

• Requirements prioritization and negotiation,

• Requirements specification.

2. Requirements validation:
• Validity. Does the system provide the functions which best support the customer’s needs?

• Consistency. Are there any requirements conflicts?

• Completeness. Are all functions required by the customer included?

• Realism. Can the requirements be implemented given available budget and technology

• Verifiability. Can the requirements be checked?

3. Requirements management: is the process of managing changing requirements during the


requirements engineering process and system development.

- Changing requirements: The business and technical environment of the system always changes after
installation.

- Deciding if a requirement change should be accepted

Made by:
‫مدرس برمجة‬

You might also like