User Requirements in software development

by Ruby Shaikh 23:45 2 comments

User Requirements

The user requirements should explain functional and non-functional requirements in such a way that they are understandable by system users who do not have detailed technical knowledge.

User requirements are defined using natural language tables and diagrams because these are the representations that can be understood by all users.

The readers of the user requirements include:

·       Client Managers

·       System End Users

·       Client Engineers

·       Contract Managers

·       System Architects

Problems in Expression of User Requirements Specification

1)    Lack of Clarity: Sometimes requirements are given in indefinite manner. It is expected that text should help in clear and accurate understand of the requirements.

2)    Requirements Confusion: There may be confusion in functional requirements and non-functional requirements, system goals and design information.

3)    Requirements Mixture: There may be a chance of specifying requirements together as a single requirement.

Example: User Requirement Document

The user requirements can be given in natural language as:

1)    The system should posses a traditional word dictionary and user supplied dictionary.

2)    When a word is found in the document which is not given in the dictionary, then the system should suggest 10 alternative words. These alternative words should be based on a match between the word found and corresponding words in the dictionary.

3)    When a word is found in the document which is not in any dictionary, the system should propose following option to user:

                           i.          Ignore the corresponding instance of the word and go to next sentence.

                         ii.          Ignore all instances of the world.

                       iii.          Replace the word with a suggested word from the dictionary.

                       iv.          Edit the word with user-supplied text.

                         v.          Ignore this instance and add the word to a specified dictionary.

Requirements Documentation: Software Requirement document

This is the way to represent requirements in a consistent format. Requirements document is called Software Requirements Specification (SRS).

Software requirement document is the requirement of the system. It should include both a definition and a specification of requirements. It is not a design document. As far as possible, it should include both a definition and a specification of requirements.

Requirements documentation is very important activity after the requirements elicitation and analysis. This is the way to represent requirements in a consistent format. Requirements document is called Software Requirement Specification (SRS).

The System Specification is the final product produced by the system and requirements engineer. It serves the foundation for hardware engineering, software engineering, database engineering, and human engineering.

Software Requirement Specification Document (SRS)

The final output of this phase is Software Requirement Specification document (SRS). The primary objective of analysis is problem understanding, while the basic objective of the requirements phase is to create the SRS.

Role of SRS document can be understood by its use in various contexts:

1)    Statement of user needs

2)    Contract Document – It is often appropriate to think of the SRS document as the document of a contract between the development team and the customer.

3)    Reference document

4)    Definition for implementation

5)    Legal Document – The SRS document can be used to determine any disagreements between the developers and the customers, which may occur in future. It may be used to resolve disputes between the customers and developers.

Components of SRS document

SRS document comprises of a complete information description, a detailed functional description, a representation of system behavior, an indication of performance requirements and design constraints, validation criteria and other information pertinent to requirements.

Components of SRS document include:

1)   Functionality: SRS must specify the functional requirements, which governs which outputs should be produced with given inputs.

2)   Performance: SRS must specify the performance constraints on the software system.

3)   Design constraints: SRS must specify any resource limits, operating environment, reliability and security requirements etc.

4)   External Interface: SRS must identify all the possible connections of the software with people, hardware or other software.

Aspects of System in SRS Document

1)    Functional Requirements: Functional requirements elaborates:

                           i.          What the system should do

                         ii.          How it should react to the input

                       iii.          How it should behave in particular situation

                       iv.           What it should not do

2)    Non-Functional Requirements: Non-functional Requirements include:

                           i.          Maintainability

                         ii.          Performance issues

                       iii.          Profitability issues

                       iv.          Space requirements

                         v.          Reliability

3)    Constraints: Constraints describe things that the system should or should not do. For example:

                           i.          Standards Compliance

                         ii.          How fast the system can produce results

                       iii.          Hardware to be used

                       iv.          Operating system or DBMS to be used.

                         v.          Data representation by the interface system.

Types of requirements

The requirements definition and specification documents describe everything about how the system is to interact with its environment.

Following are the kinds of items:

Mobile app Development companies in Jaipur provide best software development and software training kindly contact via click on the links.