Requirements

Requirement is a broad concept that defines any function, attribute, capability,

characteristic or quality of a system that gave value and advantage to a customer,
organization and internal or external stakeholders. Simply requirements fulfill the
expectations of users by implementing the software products. This can be known or
unknown, expected or unexpected or hidden from customer’s point of view. It mainly
used in development of the software/ system designing and also in system engineering
and enterprise engineering. Note that, requirements provide mutual understanding
between users and designers and describe the behavior of a system. The requirements
should adapt with the willingness of users or else the final outcome may cause many
failures. Further, identification of correct requirement is important to the initial stage of
system designing. Furthermore, requirements are categorized as business requirements,
user requirements and system requirements.

1. Business requirements

Business requirements describe why the organization carrying out the project/system. It
explores the benefits of the product which customer or organization expect to gain from
the final outcome. This covers the areas of problem statement, project vision, project
budget/ schedule/ resources, project objectives, scope statement, business process analysis
and stakeholder analysis. Project owner, stakeholder and project team create Business
Requirement Document (BRD) to examine business requirements. BRD is a living
document that maintain future requirements, updates and changes with all the practical
and measurable organization and customer expectations.

2. User requirements

User requirements to mean the high-level abstract requirements which describes what the
user does with the system or how user interact with the system. These requirements poses
as a primary inputs for the system requirement. Even, this express the services that the
system expected to provide to users and the limits to be implemented. Natural languages,
tables and diagrams are used to approach user requirements. The requirements need to be
identify clearly because different types of users use these in different ways. Client
managers, system end-users, client engineers, contractor mangers, system architects
usually interact with the user requirements. URD, the acronym of User Requirement
Document is a document that mentioned the introduction (project background, project
scope and objectives etc.), risks, assumptions, constraints, proposed system overview and
future business process. However, the users of user requirements are not familiar with
how the system will be implemented.

3. System requirements

M D H S Gunathilake (E157016) Requirements 1|Page

System requirements explain the details of what the system should do. System
requirements are concern with the system functions, services and operational limitations.
By the way, this is the part of a contract between the customer and system developers.
System end-users, client engineers, system architects are concern with the system
requirements. In addition, functional requirements, non- functional requirements, and
domain requirements are classified under the system requirement. This classification
based on the objective specificity which defines operational needs of the system to design
and develop and the traceability of requirements for the functional needs of the system.
Further, the documentation part of the functional and non- functional is called Software
Requirement Specification (SRS). SRS is the source that analysts use to communicate
requirement information in detail with system developers, testers and project
stakeholders.

a) Functional requirements
This explain services that the system should provide, how the system response to the
particular inputs and how the system react in different conditions. The inputs can be such
as addresses, names or calculations need for the system to work properly. And also
functional requirements defines what the system should not to do. Even, the statements or
goals that used to recognize the system behavior are called functional requirements.
Further, functional requirement describes a set of high-level requirements and consists set
of functions. Each high-level requirement collect data from users and dispatch data to
users. Note that the functions include input data set, output data set and processes which
require to obtain inputs from the outputs.
b) Non- functional requirements
Non-functional requirements express how the system should operate. The non-functional
requirements specify the characteristics and architecture of the system as a whole. The
main characteristics of the aforesaid requirements can be point out as performance,
usability, portability, security, scalability, reliability and maintainability. It is important to
achieve non-functional requirements without failures to meet successful outcome.
c) Domain requirements
Domain requirements can be functional requirement or non-functional requirement which
describes the expectations of a specific software, purpose or industry vertical.
Accordingly, the following example make clear view of the process of all types of
requirements.
Example: Hospital Patient Management System
The information of patients and patient’s families are stored in the system. Patients are
judged and treated by doctors. Under the supervision of doctors, nurses are delivering
various treatments. Patients' appointments are handled by medical receptionists and all
the system related information setup and upkeep by the IT personnel, who is in charge of
the system. The medical ethics manager is responsible for ensuring that the system
complies with current patient-care ethical principles. Managers of health-care

M D H S Gunathilake (E157016) Requirements 2|Page

organizations are the persons who use the system to get management data. Medical
records personnel ensure that the system data can be retained and preserved, as well as
that adequate record-keeping practices are in place.

M D H S Gunathilake (E157016) Requirements 3|Page