You are on page 1of 11


A . Antony Alex MCA Dr G R D College of Science – CBE Tamil Nadu - India

• Expect to do a little bit of design during analysis and a little bit of analysis during design.Requirements Analysis • Software engineering task bridging the gap between system requirements engineering and software design. and component-level designs. 2 . • Provides software designer with a model of: • system information • function • behavior • Model can be translated to data. architectural.

• During System Requirements Analysis. providing the foundation for all future design and development efforts. the framework for the application is developed. reviewed and agreed upon with the Customer DecisionMakers.• The purpose of System Requirements Analysis is to obtain a thorough and detailed understanding of the business need as defined in Project Origination and to break it down into discrete requirements. which are then clearly defined. .

System Engineering Software Requirements Analysis Software Desigh .

Perform economic and technical analysis. Establish schedule and constraints. Evaluate system for feasibility.Analysis Objectives • • • • • • Identify customer’s needs. Allocate functions to system elements. Create system definitions. 5 .


because all of the major Customers and their interests are brought into the process of determining requirements. . and provide the best chance of creating a system that fully satisfies the needs of the Customers. • Since the requirements form the basis for all future work on the project. along with accompanying data and process models illustrating the information to be managed and the processes to be supported by the new system. • The primary goal of this phase is to create a detailed Functional Specification defining the full set of system capabilities to be implemented. it is of the utmost importance that the Project Team create a complete and accurate representation of all requirements that the system must accommodate. • Accurately identified requirements result from effective communication and collaboration among all members of the Project Team. from design and development to testing and documentation.NEED • System Requirements Analysis can be a challenging phase.

• Non-functional requirements: • Physical environment (equipment locations. multiple sites.). • User & human factors (who are the users.1 • Functional requirements: • input/output • processing.).Types of Requirements . • Interfaces (data medium etc. their skill level etc.). • error handling. etc. 8 .

Data (qualitative stuff). firewall). etc. Resources (finding.2 • Non-functional requirements (continued): • • • • • • Performance (how well is system functioning).Types of Requirements . Documentation. Security (backup. physical space). 9 .). Quality assurance (max. down time. MTBF.

Requirement Validation • Correct? • Consistent? • Complete? • Externally . • Each requirement describes something actually needed by the customer. • Internally . • Requirements are verifiable (testable)? • Requirements are undefined references.all desired properties are present. 10 .

Thank U .