Software Requirements and Its types (from Stakeholder)

A thing that is needed or wanted to develop a software. Basically requirements are given by stockholders or person who is involved to develop software.









Two main types from user side:

1. User Requirements
2. System Requirements

• User Requirements

                  User requirement are statements in a natural language plus UML diagrams, of what system is expected to provide to system user, and the constraints under which it must operate.

In short, user requirements are totally written for user.

• System Requirements

                  System requirements are more detailed description of software systems functions, services and operational constraints. The system requirements document should define exactly what is to be implemented. It may be part of contract between system buyer or user and software developers.

In short, system requirement is basically a contract document in which software developer wrote detailed description of services given to user. 

Read More →

Software Requirements and Its types (from Developer)

A thing that is needed or wanted to develop a software is called software requirement. Basically requirements are given by stakeholders or person who is involved to develop software.

Two main types from developer side are:

1. Functional Requirements
2. Non-Functional Requirements

• Functional Requirements:

They are statement of services the system should provide, how the system reacts on a particular set of inputs and how the system should behave in particular situations. In some cases, the functional requirements may also explicitly state what the system should not do. In short, the boundaries in which we have to develop our software.

• Non-Functional Requirements:

These are constraints on the services or functions offered by the system. They include timing constraints, constraints on the development process and constraints imposed by standards.

In short, It elaborate the performance characteristics of functional requirements. 

Read More →

Unified Model Language (UML)

The Unified Modeling Language (UML) is a general-purpose modeling language in the field of software engineering, which is designed to provide a standard way to visualize the design of a system.
We use this language in System Modeling which is the phase of Requirement Engineering.




Basically five ways to write model language.

1. Activity Diagram
2. Use Case Diagram
3. Sequence Diagram
4. State Diagram
5. Class Diagram

Read More →

Requirement Engineering - Its Activities

Requirements engineering refers to the process of formulating, documenting and maintaining software requirements it is the sub-field of Software Engineering.

Requirement Engineering in used when we / department develop any software. But its not necessary in every software project.

  Around 7 activities are involved in requirements engineering:

1. Requirements inception or Requirements elicitation
2. Requirements identification - identifying new requirements
3. Requirements analysis - checking requirements and resolving stakeholder conflicts
4. Requirements specification - documenting the requirements in a requirements document
5. System modeling - writing requirements in Unified Model Language (UML)
6. Requirements validation - checking that the documented requirements and models are consistent and meet stakeholder needs
7. Requirements management - managing changes to the requirements as the system is developed and put into use

Read More →