Types of Requirements
1. Business Requirement Specification (BRS)
2. Software Requirement Specification (SRS)
3. Functional Requirement Specification (FRS)
1. Business Requirement Specification
Business requirement specification describe in business terms what must be delivered to client
It is a high level document containing project requirements from customer
It contains problems from customer’s existing system
Person should be domain expert or functional expert and will be eligible to convert the BRS into SRS.
2. Software Requirement Specification
A SRS is basically an organization’s understanding of a customer or client’s system requirements and dependencies at a particular point in time prior to any actual design or development work.
It’s a two-way insurance policy that assures that both the client and the organization understand the other’s requirements.
A well written SRS accomplishes four major goals
• It provides feedback to the customer. A SRS is the customer’s assurance that the development organization understands the issues or problems to be solved.
• It decomposes the problem into component parts.
• It serves as an input to the design specification.
• It serves as an input to the Testing for product validation check.
Content in SRS
1.1 Project Overview
1.2 Project Objective
2. Existing system
2.1 Constraints & Limitations.
3. Proposed system
3.1 System Overview
3.2 Need for the proposed system
4.1 Project Requirements
4.2 Project System
5. User Management.
3. Functional Requirement Specification
• A functional specification describes how a product will work entirely from the user’s perspective. Ti talks about features. It specifies screens, menus, dialogs and so on.
• A functional requirement defines a function of a software system or its component. A function is described as a set of inputs, the behaviour and outputs.
• A FRS defines how the system must behave when presented with specific inputs or conditions. These may include calculations, data manipulation and processing and other specific functionality.
Requirement change management or Change Request
• Prepare change request.
• Perform impact analysis (Work Product, effort, Schedule)
• Re-estimate delivery schedule
• Review impact with senior management and other affected groups as necessary
• Obtain approval from CCB
• Obtain customer sign off
• Implement the approved changes in the work item
• Perform review testing process to verify the implementation of change
• Update closure status of change request.
Test management Process (Testing Life Cycle)
Test process is accomplished integration of test process of
• Test initiation
• Test planning
• Test execution
• Test monitoring
• Test controlling
• Test closing
Approved PMP or SRS
• Identify test manager/ test lead
• Test estimation
• Identify risks, resources & process (Templates, guidelines) for the project
Test Planning-Major Activities
• Requesting for identified resources
• Prepare test plan
• Get the test plan approved
• Baseline the test plan
• Define the entry and exit criteria’s of each testing activity
Test Execution/ Monitoring /Controlling
• Execution of test plan includes identify the test scenarios, design test cases and executing the test cases.
• Track testing activities.
• Track testing progress
• Track issues , risks, complaints and resources
• Track testing changes & CM activities.
• Review testing progress
• Initiate corrective and preventative actions
• Revising the plan and schedule if requires.
• Release the application for UAT/ Production
• Perform closure analysis
• Submit the testing deliverables to project manager
o Test plan
o Test scenario documents
o Test case documents
o Defect reports
o Build Summary Reports
o Status reports
o Test scripts
o Product sign off document
• Release testing resources