SOFTWARE REQUIREMENT

ENGINEERING
ASSIGNMENT 1
Questions
Q1. System Requirements consist of functional and non-functional requirements and other
types of requirement. Research the prepare a report on following types of requirements.
State examples with each type as well.
Generally, system requirements are intended to communicate the functions that the system
should provide. And every computer based systems consists of many requirements

Functional requirements:
These are the statements of services that the system should provide, how the system should
react to particular inputs and how the system should behave in particular situations.
“Any Requirement Which Specifies What The System Should Do.”

In different words, a functional requirement will describe a particular behaviour of function of the
device when certain conditions are met, for example: “Send electronic mail while a brand new customer
signs up” or “Open a new account”.

Non-functional requirements
“Any Requirement That Specifies How The System Performs A Certain Function.”

In different words, a non-functional requirement will describe how a system have to behave and what
limits there are on its functionality.

Non-functional requirements cover all of the last requirements which aren't included through the
functional requirements. They specify standards that choose the operation of a system, as opposed to
precise behaviours, for example: “Modified facts in a database have to be updated for all customers
having accessing it within 2 seconds.”

Domain requirements:
Domain requirements are expectations associated with a specific sort of software program, reason or
industry vertical. Domain requirements may be functional or non functional. The common factor for
domain requirements is that they meet installed requirements or extensively common function units
for that category of software project.

Example of domain requirement is for software in medical equipment.

Inverse requirements:
They explain what the system shall not do. Many people find it convenient to describe their needs in this
manner

These requirements indicate the indecisive nature of customers about certain aspects of a new software
product.

Example: The system shall not use red color in.

Design and Implementation Constraints

The QDR must be able to curate data collected in batches from the Industrial-Equipment Network. At a
predetermined time each calendar day, the QDR must process all curate data and populate a list of
available elements for query. Setup and maintenance of the QDR application are the responsibility of
the customer. Setup and maintenance include: installation, hosting, host-security configuration, and
administration. There are no additional constraints on the VDS other than any defined for an application
that executes the MT Connect Agent in the standard documentation

• They are development guidelines within which the designer must work.
 These requirements can seriously limit design and implementation options
 Can also have impact on human resources

Examples ► The system shall be developed using the Microsoft .Net platform.

The system shall be developed using open source tools and shall run on Linux operating system
 Q2. Consider the Learning Management System of COMSATS (CUOnline) as your system
under study. For this system propose:

10 functional requirements.
1. The system should let Student to upload Assignment
2. The system should let Students view Marks.
3. The Students must upload assignment before the deadline.
4. The Students should upload the file of less then 2GB .
5. The system should authenticate/identify Student by CNIC, Contact number.
6. The system should allow Students to download the content in course content.
7. The system must show the status of submitted assignment and not submitted
assignment.
8. The system should authenticate the Registration number and password is right or
wrong.
9. The system should let Students view Attendance.
10. The system should let Students view history of fee and Installments in the fees.
5 non-functional requirements (mixture of product, organizational
& external).
1. In any type of system failure, the system shall take less than 10 seconds to recover
2. The system must have user friendly graphical interface.

3. The system should be easy to maintain and add new functionalities easily.
4. The system should shown content to the students who is registered in that course.
5. The System response time should not be more than one second for users.

5 domain requirements:
1. The system should be able to respond to 1 lac requests per minute.
2. The system should be able to access the student login.
3. The system doesn’t allow student to upload assignment after the deadline
4. The system must not be down for more than 2 minutes per week.
5. The system authenticates Students by Registration number.