Analysis and Design
Software development is a multi-step process
Each step needs to be managed well.

The Systems Analysis phase is the first phase to be performed within an SDLC.
It is initiated only and in conjunction with a project being authorized or approved.
Its purpose is to ensure the requirements to satisfy a business need have been identified
and translated into a notational form or models. As an iterative process, the Systems Analysis phase ensures the project team members are working together
to define and clarify the business need and promoting alternatives that could be utilized to address the business need.
The analysis phase defines the requirements of the system, independent of how these requirements will be accomplished.
This phase defines the problem that the customer is trying to slive. The deliverable result at the end of this phase is a requirement document.
The requirement document may be expressed in a formal language based on mathematical logic. The requirement document does not specify the architectural or implementation details,
but specifies information at the higher level of description.
A Software Requirements Specification (SRS) is a complete description of the behavior of the system to be developed.
It includes
Phase 1: INTRODUCTION
Product Overview
- Purpose
- Scope
- Reference
- Definition And Abbreviation
Overall Description
- Product Perspective
- Product Functions
- User Characteristics
- General Constraints
- Assumptions and Dependencies
|
Phase 2: SPECIFIC REQUIREMENTS
External Interface Requirements
- User Interfaces
- Hardware Interfaces
- Software Interfaces
- Communications Protoclis
- Memory Constraints
- Operation
- Product function
- Assumption and Dependency
Software Product Features Software System Attributes
- Reliability
- Availability
- Security
- Maintainability
- Portability
- Performance
Database Requirements Other Requirements |
Make Request |