Requirement types:

What is a requirement ?

 A condition or capability needed by a user to solve a problem or achieve an objective

 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 documents
 A documented representation of a condition or capability as in 1 and 2.

Functional requirements:

These are the requirements that the end user specifically demands as basic facilities that the system
should offer.

For example, in a hospital management system, a doctor should be able to retrieve the information
of his patients.

Non-functional requirements: These are basically the quality constraints that the system must satisfy
according to the project contract.

o Portability
o Security
o Maintainability
o Reliability
o Scalability
o Performance
o Reusability
o Flexibility
o Manageability
o Environmental
o Data Integrity
o Usability
o Interoperability

Some of the constraints of non-functional requirements are:

1. Interface constraints
2. Performance constraints: response time, security, storage space, etc.
3. Operating constraints
 4. Life cycle constraints: maintainability, portability, etc.
5. Economic constraints

Example- Functional

1) Authentication of user whenever he/she logs into the system.

2) System shutdown in case of a cyber-attack.

3) A Verification email is sent to user whenever he/she registers for the first time on some software
system.

Example- Non functional

1) Emails should be sent with a latency of no greater than 12 hours from such an activity.

2) The processing of each request should be done within 10 seconds

3) The site should load in 3 seconds when the number of simultaneous users is > 10000

Top three tools of information gathering for system analysis. The tools are:

1. Interviews and Questionnaires – Asking questions open ended close and probing
2. Revision of Literature, Procedures and Forms The following questions are deciding the forms
usefulness:

1. Do the forms include all the necessary information? What items should be added or detected?

2. How does the information in the form helps other users make for the better decisions?

3. Who use the form? How important are they to the user?

4.How readable and easy to follow is the form?

5. How many departments receive the existing form? Why?

3. On Site Observation. –

Another information gathering tool used in system studies is called the ‘on site observation’. On site
observation is the process of recognizing and noting people, objects and gets the information.

1.What is relationship with the other systems in the organization?

2. Is it a primary or a secondary use in organization?

3. Who runs the system? Who are the important people in it?

4. What kind of system is it? What does it do?

5.What is the history of system? How did it get to its preset stage of development?

Three techniques help users discover their needs for the new system:

Business Process Automation (BPA)- ex-Employee analytics and retention

Process automation gives organizations the ability to collect and analyse key employee performance
indicators. Using this information, organizations can improve employee productivity and job
satisfaction. Moreover, providing automation solutions like employee help desk support ensures
that your employees have the tools that they need to succeed. Concentrates on efficiency
Business Process Improvement (BPI)- Businesses often focus on trying to make these processes more
efficient in order to save time and money, but it’s not efficiency that should be the primary focus.
For any company to see positive growth and profit, the business processes it has in place needs to be
effective. Identify the process waste and work on it.

There are a number of process improvement examples that show how steps could be taken in a
business to make things more effective as well as efficient.

Cost Cutting – One process improvement example is in cutting costs. Through restructuring
processes, organization, and visualization it’s easy to spot redundancies and other items that wind
up increasing overhead costs. From there, unnecessary tasks are dropped. That restructure allows
for resources to be reallocated so you spend less while your processes flow better.

Reducing Communication Issues – Another business process improvement example is the

improvement of communication. Process improvement is intended to improve functionality by
streamlining communication, such as decreasing the number of emails and contact touch points
between departments and employees. This is often achieved using software that allows employees
and departments to see and share information – rather than chasing email threads through an
inbox.

Process Visualization – With process modelling, it becomes far easier to audit and continually make
improvements. Visualization allows you to follow the process and locate bottlenecks as they arise, or
opportunities to make that process more efficient.

Business Process Reengineering (BPR)- Business process re-engineering is the radical redesign of
business processes to achieve dramatic improvements in critical aspects like quality, output, cost,
service, and speed. Business process reengineering (BPR) aims at cutting down enterprise costs and
process redundancies on a very huge scale

Is business process reengineering (BPR) same as business process improvement (BPI)?

On the surface, BPR sounds a lot like business process improvement (BPI). However, there are
fundamental differences that distinguish the two.

BPI might be about tweaking a few rules here and there. But reengineering is an unconstrained
approach to look beyond the defined boundaries and bring in seismic changes.

While BPI is an incremental setup that focuses on tinkering with the existing processes to improve
them, BPR looks at the broader picture. BPI doesn’t go against the grain. It identifies the process
bottlenecks and recommends changes in specific functionalities
BPI is like upgrading the exhaust system on your project car. Business Process Reengineering, BPR is
about rethinking the entire way the exhaust is handled.

Widely used process modelling techniques

 Use Case Diagram • Data Flow Diagrams (DFD)

A use case diagram is used to represent the dynamic behaviour of a system. It encapsulates the
system's functionality by incorporating use cases, actors, and their relationships

Following are the purposes of a use case diagram given below:

 It gathers the system's needs.

 It depicts the external view of the system.
 It recognizes the internal as well as external factors that influence the system.
 It represents the interaction between the actors.

A use case diagram depicting the Online Shopping website is given below.
For DFD’S refer the earlier document

END