Functional requirements

Practical class #1

Prepared by
Ph.D, docent of Software Engineering Department of ICIT NAU
Guchenko Inna Volodumurivna
What are Requirements?
IEEE Definition

1. a condition or capability needed by a user to solve
a problem or achieve an objective
2. a condition or capability that must be met or
possessed by a system or system component to
satisfy a contract, standard, specification, or other
formally imposed document
3. a documented representation of a condition or
capability as in (1) or (2)
Slide: 2
What are Requirements?
ISEB have 7 types of requirement:

1. General Requirement
2. Business Requirement
3. Functional Requirement
4. Detailed Requirement
5. Non-functional Requirement
6. Data Requirement
7. Technical Requirement
Slide: 3
What are Requirements?
IIBA have 6 types of requirement:

1. Business Requirements.
2. User Requirements
3. Functional Requirements
4. Quality of Service Requirements
5. Assumptions and constraints
6. Implementation requirements.
Slide: 4
Levels of requirements (1)
Slide: 5
Levels of requirements (2)
Business requirements represent high-level objectives of the
organization or customer who requests the system. Business
requirements typically come from the funding sponsor for a
project, the acquiring customer, the manager of the actual users,
the marketing department, or a product visionary. Business
requirements describe why the organization is implementing the
systemthe objectives the organization hopes to achieve.
User requirements describe user goals or tasks that the users must
be able to perform with the product. Valuable ways to represent
user requirements include use cases, scenario descriptions, and
event-response tables.
Functional requirements specify the software functionality that
the developers must build into the product to enable users to
accomplish their tasks, thereby satisfying the business
requirements. Sometimes called behavioral requirements.
The term system requirements describes the top-level
requirements for a product that contains multiple subsystemsthat
is, a system (IEEE 1998c). A system can be all software or it can
include both software and hardware subsystems. People are a part
of a system, too, so certain system functions might be allocated to
human beings.



Slide: 6
7
Functional Requirements
What inputs the system should accept
What outputs the system should produce
What data the system should store other systems might use
What computations the system should perform
The timing and synchronization of the above

Depend on the type of software, expected users, and the
type of system where the software is used
Functional user requirements may be high-level statements
of what the system should do, but functional system
requirements should describe the system services in detail
Functional Requirements Examples
The solution will automatically validate customers against the ABC
Contact Management System

The solution will enable users to record customers sales

The solution will enable Customer Order Fulfilment letters to be
automatically sent to the warehouse.

Question: What does solution mean in this context?
Examples of poor
functional requirements
1. Be able to use diary functionality

2. Be able to flag premium customers

3. Be able to track and report on sales

4. Increase accuracy of sales information

5. Allow authorised users of team-leader and above to cancel sales orders

6. Prompt the owner of the sales order to
notify the customer of cancelled sales
orders.
Functional Requirement Prioritisation
Logic
Must have: the project objectives cannot be met without this requirement

Should have: the project objectives can be met without this requirement
but not as well as with it

Could have: this requirement only maps to one or more principles

Wish list: this requirement does not map to any project objectives or
principles.
Functional requirements
properties (1)
Slide: 11
Functional requirements
properties (2)
Slide: 12
Functional requirements
properties (3)
Slide:
13
Bad requirements examples
(discuss)
Slide:
14
Explanations
Slide: 15
Task
Write functional requirements for any imagine software.
Each student choose his own software!!!
Slide: 16