Sei sulla pagina 1di 6

Lab Manual

CPIT 250
System analysis and Design 1
1433/1434H

Lab – 5

Function requirement and non-function


requirement

Names I.D.

1. .……………..………………………………. ………………………………

2. ………………………………………………. ………………………………
Lab objective:
 Explain how to conduct the function requirement.
 Explain how to conduct the function requirement.
 How to conduct an event table.
Function requirement:
The Functional Requirement document (also called Functional Specifications or Functional
Requirement Specifications), defines the capabilities and functions that a System must be able
to perform successfully.

Functional Requirements should include:

 Descriptions of data to be entered into the system


 Descriptions of operations performed by each screen
 Descriptions of work-flows performed by the system
 Descriptions of system reports or other outputs
 Who can enter the data into the system.
 How the system meets applicable regulatory requirements

Examples of Functional Requirements

Interface requirements

 Field accepts numeric data entry


 Field only accepts dates before the current date
 Screen can print on-screen data to the printer

Business Requirements

 Data must be entered before a request can approved


 Clicking the Approve Button moves the request to the Approval Workflow

Regulatory/Compliance Requirements

 The database will have a functional audit trail


 The system will limit access to authorized users
 The spreadsheet can secure data with electronic signatures

Security Requirements

 Members of the Data Entry group can enter requests but not approve or delete requests
 Members of the Managers group can enter or approve a request, but not delete
requests
 Members of the Administrators group cannot enter or approve requests, but can delete
requests
Non-functional Requirements
Non-functional requirements are requirements that specify criteria that can be used to
judge the operation of a system, rather than specific behaviors.

Non-functional requirement is to describe/judge the operations of a system and it is


important to cover as it will determine the minimum, possible criteria to sign-off for the
deployment. A solution cannot operate successfully if the infrastructure/configurations
are done incorrectly, even though it may meet the functional requirements.

Some Areas that define as Non-Functional Requirements/Specification:

 Accessibility
 Performance/Response Time
 Usability
 Scalability
 Compatibility
 Reliability
 Maintainability
 Robustness
 Documentation
 Effectiveness
 Efficiency
Function and non-Function requirements example:
3.2.1 Functional requirement:
ID Requirement Definition
FR1 Create an account
FR1.1 The system shall enable a user to create an account
FR2 Select the places for rent
FR2.1 The system shall identify the possible places to the investor to allow him to
choose one of the available places
FR3 Place request
FR3.1 The system shall allow the investor to send a require place throw the system
FR4 View request status
FR4.1 The system shall allow user to show his place request status.
FR5 Login
FR5.1 The system shall allow to the all actors to gain the system throw supposed user
name and password.
FR6 Insert an empty place
FR6.1 The system shall allow the security staff to insert an empty places.
FR7 Review an agreement
FR7.1 The system shall allow security staff to reviewing the final approval
agreement.
FR8 Fill agreement form
FR8.1 The system shall allow the IMS staff to enter the agreement information after
the manually approval.
FR9 Reviewing companies orders
FR9.1 The system shall allow the IMS staff to response about the companies
requests.
FR10 Control activity
FR10.1 The system shall allow the IMS staff to control all the actors who has an
account in IMS website.
Table 3.1
Function Requirement
3.2.2. Non-Functional requirement:
User Interface

UI1: The system shall provide certain functionalities in the user interface according to the
user authorization

UI2: The system shall provide user friendly interface

UI2: The user interface shall be as GUI

 Hardware Interface
HI1: The system shall be implemented in a hardware-independent fashion and should not
rely on any particular hardware interfaces.

 Software Interface
SI1: The Investment management system shall communicate with the data base of KAU
system to extract the needed information including user name and password to validate the
user access to Investment management system.

 Security Requirements
SE1: The system shall provide log in page

SE2: The system shall allow user to access only the services which he/she authorize to
access

SE2.1: The system shall allow only authorized user to make and edit, delete.