Home / BA / Requirement Classification schema

Requirement Classification schema

Requirement Classification Schema

There are 4 classifications in requirements which are listed below

 

Business Requirements

                Stakeholder Requirements

                Solution Requirements

                                1) Functional requirements

                                2) Non- functional requirements

                Transition Requirements

 

Business Requirements

          The Purpose of a business requirements is to execute project’s needs and goal towards its success. Business requirements describes the goal of the project, whom it will be benefited and what methods will be used to evaluate it. Business Requirements describes how a how a project is to be executed.

 

Stakeholder Requirements

          Stakeholder Requirement describes the needs of a client, what he requires for the project, describe the decisions about business needs, goals, objectives in a stakeholder point of view. stakeholder requirements serves as a bridge between business requirements and solution requirements.

 

Solution Requirements

                        Solution requirements describes the solutions for the requirements of a project

Solution Requirements are classified into two types

Functional Requirements

Non-Functional Requirements

Functional Requirements

            Functional Requirements describes the solutions like behavior of a program, capacity of an application, at what functions the solution must support and what information will be managed, and ensure how the outcomes and results should be. Manual solutions also have a  functional requirements.

 

Non Functional Requirements

            Non Functional Requirements describes conditions under which a solution must be efficient and qualities that a solution must have. There are some standards

 

Usability: The usability of a software or application should be user friendly, where the portability of a screen and login pages , etc., should be easy to understand for the end users, users will also start to explore about the performance or usability of a system for example if the system is running an application and alternatively the user needs to open another system at that time the system performance will be accessed, at that time performance shouldn’t slowdown even though one application is running on the back ground.

Reliability: Reliability is the one requirement to some extent how users can rely on the solution to be accessible and work what needed. It show how frequently the system shows critical failures.

Performance: The performance is nothing but the execution of the system how fast the system shows the output of a user requirement, like loading of new page, payment execution time, buffering period

Security: It is a non functional requirement which the end user does not know about it but it is very essential requirement of how the system and the data is protected from the hackers and other cyber crime people, etc.,

Compatibility: compatibility defines how the system will adapt with another and third party system with  the same environment and work together with progress of a project

Data Integrity: It is critical approach of to implement of usage of system which gathers ,saves, and recover data.it will be consistent and accuracy.

 

 

Transition Requirements

                   Transition requirements can be explained clearly with the example if a person is shifting a furniture into a new house he needs a vehicle to carry all the furniture, after the completion of shifting the need of a vehicle is not required ,like the same way transition requirements is the one in which a requirement is need at a specific period of time for facilitation of transition from the current state to desired future state

 

 

About Chockalingam Lakshmanan

Check Also

Agile Vs Waterfall Methodologies

There are two popular methods of software development. Waterfall Methodologies Agile Methodologies Though  both the …

Leave a Reply

Watch Dragon ball super