Development Process for Web-Enabled Applications – Requirements Analysis

Requirements Analysis

Policy

Policies governing requirements are:

· User Requirements are documented.

· User Requirements are reviewed by senior management.

· User Requirements are used to prepare Software Project Management Plans.

· Allocated requirements will be managed by skilled/trained application and domain experts.

· Software Project Plans, work products and activities are kept consistent with requirements and contracts.

· Changes to requirements are reviewed before being incorporated in the projects.

· Acceptance criteria, wherever appropriate, is clearly documented.

Objective

The objective is to prepare the Software Requirement Specifications (SRS) for the system being developed based on the inputs from the client.

Process Description

Requirement Analysis is the first technical step in the software engineering process. It is at this point that a general statement of software scope is refined into a concrete specification. This specification becomes the foundation for all software engineering activities that follow.

The Requirements Analysis process consists of the following steps:

· Preparation for Requirement analysis:

1. Identify the documents which can be taken as baseline for understanding the client requirements.

2. Study the existing system of the customer and become familiar with the customer’s business objective, methodology and tools to be used.

3. Identify methods for information gathering like interview with domain experts, customers, user-groups.

4. Plan for prototyping, if required.

5. Prepare questionnaires, if required, to elicit information.

· Gather requirements:

1. Establish objectives and scope of the system to be developed

2. Gather requirements like functional, Performance, Operating Environment etc

3. Prepare prototypes, if required. Evaluate and get feedback from the customer and incorporate the necessary changes.

4. Prepare Software Requirement Specifications (SRS) document as per template in.

5. Evaluate testing requirements. Identify and highlight non-testable requirements, if any.

6. Conduct an internal review of the SRS document and Acceptance Criteria by using checklist as per

7. Review of Software Requirement Specifications document by SEPG, Quality Analyst (QA), Head-Projects and Client. The review checklist for SRS appears in MT/TECH/FTR procedure.

8. Review of Software Requirement Specifications document by affected support groups (like HR, System Admin) and get commitments from them.

9. Review and update the project plan

10. Obtain customer sign-off for the Software Requirement Specifications (SRS) document

11. Identify Client Supplied Items

12. Bring the Client Supplied Items under Document Control Procedures.

Software Requirement Specification (SRS)

Software Requirement Specification (SRS) is a document that describes in a disciplined manner the complete requirements of the user. This document acts as the baseline for configuration management. The requirements should be organized under specific service categories:

· Function Related

· Presentation Related

· Performance Related

· Administration Related

In LinksMultiple, the SRS will be of 2 types namely

· SRS for New System Development

· SRS for Modifications / Enhancements to the existing system

SRS For New System Development

If the customer wants a new system to be developed, the following information should

be compiled prior to initiating requirements specification process:

· Information on the company and its business objectives and plan for the future

· Organizational Structure

· Customer’s methodology in terms of processes, information flow across the organization, codification scheme and tools & techniques

After completion of this process, the Project Manager/ Project Leader will consolidate all the requirements and prepare SRS document as per the template.

SRS for Modifications / Enhancements to the existing system

When the customer’s requirement is

· To modify / enhance the existing system

· The system specification document will be scrutinized by a team consisting of PM/ PL and end users to identify the areas of modification/ enhancements.

· To migrate to a different environment

· The PM/ PL will discuss with the customer the existing system, the target environment and modification/ enhancement required and also the migration of data from the present system to the target system.

It is the responsibility of the Project Manager /Project leader to adhere to section 2.4.

Changes to Requirement Specification

Changes to Requirement Specification should be handled through the change management procedure described in Configuration Management Plan (MT/TECH/CM) and customer sign-off should be obtained.

Deliverables from the process

The deliverables at the end of this process are:

· SRS document

· An updated Project Plan

· Review records and minutes of meeting

· List of Client Supplied Items, wherever applicable

Exit criteria

The exit criteria are:

· An approved SRS by the customer

· Review records for the approved SRS

· An updated and approved Project Plan

· Review records for the approved Project Plan

· Traceability matrix prepared (Refer to 12.3.5 for format of this matrix)

High Level Design

Back to the LinksMultiple eBay Auction | eBay Shopping home page