Download Software Engineering-Applications of Computer Sciences-Project Report and more Study Guides, Projects, Research Computer Engineering and Programming in PDF only on Docsity!
Assignment 1
Q 1: What are non-functional Requirements?
Non functional requirements can be defined as follows:-
In systems engineering and requirements engineering, non-functional requirements are requirements that specify criteria that can be used to judge the operation of a system, rather than specific behaviors. It defines the overall qualities or attributes of the resulting system. It places restrictions on the product being developed, the development process, and specify external constraints that the product must meet.
"A non-functional requirement is a statement of how a system must behave, it is a constraint upon the systems behavior."
In general, functional requirements define what a system is supposed to do
whereas non-functional requirements define how a system is supposed to be. Non-
functional requirements are often called qualities of a system. Other terms for non-
functional requirements are "constraints", "quality attributes", "quality goals" and "quality
of service requirements".
Assignment 1
Non functional requirements are not really requirements but are constraints on implementing functional requirements.
The non-functional requirements are classified as follows:
1. Product Requirements:
Requirements which specify that the delivered product must behave in a particular way e.g. execution speed, reliability, etc.
2. Process Requirements:
Requirements which describe the processes the developing organization must follow and the constraints that they must obey. e.g. process standards used, implementation requirements, etc.
3. External Requirements:
Requirements which arise from factors which are external to the system and its development process e.g. interoperability requirements, legislative requirements, etc.
Q 2: Create a list of at least 12 non-functional requirements (with brief
description of each requirement) related to both the process and the
product.
1. Usability Requirements:
Concerned with specifying the user interface and end-user interactions with the system. Well structured user manuals, informative error messages, help facilities and consistent interfaces enhance usability.
2. Efficiency Requirements:
Non-Functional Requirements Classification:
Product Non-Functional Requirements:
Assignment 1
Deployment requirements include the requirements concerning installment of the product and training of end users.
2. Standards Requirements:
These are the requirements specified for the attributes of the process, e.g. coding standards, interface standards etc.
3. Processing Time Requirements:
For activities in a process simulation, the processing time can be specified, i.e. the time provided to complete each module of the product.
4. Resource Requirements:
Resource requirements are the resources required to complete the product in a simulated process. The values that are set can be additional to values specified in the process model on which the process profile is based, or the values may be overrides of values specified in the process model.
5. Documentation Requirements:
It refers to the process of providing communicable material used for a certain software development.
For example, a common type of software document frequently written by software engineers the SDF (software documentation folder). While developing the software, the engineer keeps a notebook detailing the development lifecycle of the project. It includes documentation of code, algorithms, interfaces, and APIs.
6. Verification Requirements:
It is the final requirement of a process; it proves that each requirement has been satisfied. Verification can be done by logical argument, inspection, modeling, simulation, analysis, expert review, test or demonstration.
Assignment 1
http://www.opfro.org/index.html?Components/WorkProducts/RequirementsSet/Require
ments/PortabilityRequirements.html~Contents
User’s need User’s concern Non-functional requirement
Function 1. Ease of use
- Unauthorised access
- Likelihood of failure
- Usability
- Security
- Reliability
Performance 1. Resource utilisation
- Performance verification
- Ease of interfacing
- Efficiency
- Verifiability
- Interoperability
Change 1. Ease of repair
- Ease of change
- Ease of transport?
- Ease of expanding or upgrading capacity or performance? 1. Maintainability 2. Flexibility 3. Portability 4. Expandability
Non-functional requirements
Process requirements
Product requirements (^) External requirements
Delivery requirements implementation requirements standards requirements
Usability requirements
Reliability requirements Safety requirements Efficiency requirements
Performance requirements Capacity requirements
Legal constraints Economic constraints Interoperability requirements
