Requirements Analysis A quick View

Requirements Analysis:

Software engineering task bridging the gap between system requirements engineering and software design.

Requirement analysis Fills the pit fall of Software organization. Application requirement are changed day by day but base line and design is a construct which can be modified but not changed. such scope of future requirement and changes of requirement, Necessity of requirements must analysand before implementation.

------------------------------------------------------------------------------------------------------------------------

Profit:

Financial Analysis Clears the “Profit Haze"

Clear design and Scope

Best User and development support

Low change in system design

Reduce cost of maintenance

Disadvantage:

Extra Cost for analysis ( who will pay)

Time ( rapid development require and quick development may halt)

------------------------------------------------------------------------------------------------------------------------

Analysis Objectives:

Identify customer’s needs.

Evaluate system for feasibility.

Perform economic and technical analysis.

Allocate functions to system elements.

Establish schedule and constraints.

Create system definitions.

----------------------------------------------------------------------------------------------------------------------

What Vs How dilemma

We learn what the user needs are.

We propose how to address them by defining system requirements.

We specify what we are going to build in system requirements.

We describe how to address this by designing the system.

The system design says what we are going to build.

The software requirements tell how we will build part of the system in software.

The software requirements tell what we will build in software.

The software design how we are going to structure the software.

The software design tells what software structure we will build.

The code tells how this will be implemented.

-------------------------------------------------------------------------------------------------------------------------

Requirements Analysis Document (RAD)(IEEE 830)

1. Introduction

1.1 Purpose of the system

1.2 Scope of the system

1.3 Objectives and success criteria of the project

1.4 Definitions, Acronyms, and abbreviations

2. Current System

3. Proposed System

3.1 Overview

3.2 Functional Requirements

3.2.1 User

3.2.2 Optional Capabilities

(There are numerous extensions that one might consider for this project. You will not be graded on whether you have satisfied any of these requirements, yet we must provided them)

3.3 Nonfunctional Requirements

3.3.1 Usability

3.3.2 Reliability

3.3.3 Performance

3.3.4 Supportability

3.3.5 Implementation

3.4 System Models

3.4.1 Scenarios

Not present

3.4.2 Use case model

4. Extended Use Cases

(Some of the details in these use cases implies a specific user interface modality, which we are suggesting because of the implied simplicity in implementing application.)

5. Sample GUI

6. Appendix

7. End Notes

--------------------------------------------------------------------------------------------------------------------------

Gap Analysis

Gap Analysis is the process of comparing two things in order to determine the difference or “gap” that exists between them. Once the gap is understood, the steps required to bridge the gap can be determined.

Most often gap analysis is used to compare two different states of something; the current state and the future state. But Gap can analyzed with user requirements and Organization functional procedures with standardization.

-------------------------------------------------------------------------------------------------------------------------

Gap analysis can be conducted on:

a system – features that exist in the system now versus the features that need to exist in the future

a system interface – data that a system provides to an interface now versus data that will need to be provided in the future

a business process – activities and steps of a current business process versus the activities and steps that will be supported by the business process in the future

business goals and metrics – how well a business meets certain goals and metrics now versus the targeted goals and metrics at some point in the future.

---------------------------------------------------------------------------------------------------------------------------

The following technology gaps were identified  in most organization:

1.No consensus on durability tests and performance levels in organization

2.No standardized tests for comparison of optical effectiveness and clarity of application functionality

3.No comprehensive specifications or guidance regarding Application requirements