Scribd
Upload
88 views2 pages

(A) Describe The Concepts of User Requirements and System Requirements and Why These Requirements May Be Expressed Using Different Notation

The document describes user requirements and system requirements. User requirements are statements of expected services and constraints in natural language. System requirements specify functions, services, and constraints precisely for implementation. Different notations may be used because requirements have different readers like managers, users, engineers. When testing non-functional requirements, metrics for properties like speed, size, ease of use, reliability, robustness, and portability should be measured using standards like response times, memory size, training time, failure rates, restart times, and target dependencies.

Uploaded by

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

(A) Describe The Concepts of User Requirements and System Requirements and Why These Requirements May Be Expressed Using Different Notation

The document describes user requirements and system requirements. User requirements are statements of expected services and constraints in natural language. System requirements specify functions, services, and constraints precisely for implementation. Different notations may be used because requirements have different readers like managers, users, engineers. When testing non-functional requirements, metrics for properties like speed, size, ease of use, reliability, robustness, and portability should be measured using standards like response times, memory size, training time, failure rates, restart times, and target dependencies.

Uploaded by

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

Assignment8_612_std49532

Name Aye Thida


Roll No EMCS-980
Assignment8

(a) Describe the concepts of user requirements and system requirements and why these
requirements may be expressed using different notation.

The concepts of user requirements and system requirements can be describe as follow:

 User requirements are statements, in a natural language plus diagrams, of what services
the system is expected to provide and the constrains under which it must operate.
 System requirements set out the system’s functions, services and operational constraints
in detail. The system requirements document (sometimes called a functional
specification) should be precise. It should define exactly what is to be implemented. It
may be part of the contract between the system buyer and the software developers.

Different types of readers use them in different ways these requirements may be expressed using
different notation.

Readers of different types of specification are:

User Requirements Client managers


System end-users
Client engineers
Contractor managers
System architects

System Requirements System end-users


Client engineers
System architects
Software developers

Page 1 of 2
Assignment8_612_std49532

(b) When the system is being tested to check whether or not the system has met its non-
functional requirements, which metrics for specifying non-functional requirements should
be used.

Metrics for specifying non-functional requirements should be used are as followed table:

Property Measure

Speed Processed transactions/second


User/Event response time
Screen refresh time

Size K bytes
Number of RAM chips

Ease of use Training time


Number of help frames

Reliability Mean time to failure


Probability of unavailability
Rate of failure occurrence
Availability

Robustness Time to restart after failure


Percentage of events causing failure
Probability of data corruption on failure

Portability Percentage of target-dependent statements


Number of target systems

Page 2 of 2

You might also like