[go: up one dir, main page]
Scribd
Upload
176 views1 page

Software Engineering - Lab PDF

The document provides instructions for a software engineering lab assignment on classifying requirements. Students are asked to classify sample requirements as either functional or non-functional based on definitions provided. Functional requirements specify system functionality, while non-functional requirements relate to system qualities rather than specific functions. Students are told to save their lab work in a folder structure with their name and date.

Uploaded by

yalla
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
176 views1 page

Software Engineering - Lab PDF

The document provides instructions for a software engineering lab assignment on classifying requirements. Students are asked to classify sample requirements as either functional or non-functional based on definitions provided. Functional requirements specify system functionality, while non-functional requirements relate to system qualities rather than specific functions. Students are told to save their lab work in a folder structure with their name and date.

Uploaded by

yalla
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/ 1

Software Engineering BSCS MCS FALL 2016

SOFTWARE REQUIREMENTS ENGINEERING


TIME 40 MINUTES
LAB WORK (Requirement Classification)
Objective To Classify the requirement into functional and non-functional requirements.
Background
Functional requirements (FRs) specify the software functionality that the developer must build
into the product to enable users accomplish their tasks, thereby satisfying the business
requirements. Non functional requirement as the name suggest, are those requirements which are
not directly concerned with the specific functions delivered by the system. Many non-functional
requirements (NFRs) related to the system as a whole rather than to individual functional
requirements. While failure to meet an individual functional may degrade the system, failure to
meet a non-functional system requirement may make whole system unusable. NFRs are of
different types namely usability requirements, reliability requirements etc.
Problem Description
Classify the following requirement by selecting the appropriate option.

ATM machine shall validate PIN of the user during login along with biometric verification.
Peak transaction Volume(s)- 20,000 calls in a busy hour, average duration 20 Secs, grade of services
99.98%
Brahe System Shall sounds the alarm for 10 seconds at frequency of 100H when the brake is applied.
Mean Time to failure (MTTF) -There should be no more than three Severity-1 outage per month.

Note: Fall all labs create a folder named SE LABS


SAVE labs in sub folders named with date for every lab assigned.

You might also like