Software Requirements Specification (SRS) document

Software Requirements Specification (SRS) document, containing:
• Introduction
􀂃 Purpose
􀂃 Scope
􀂃 Major Constraints and References
• Functional Requirements
􀂃 Context Diagram
􀂃 Functional Decomposition Diagram
􀂃 System Functions
􀂃 Database Requirements
􀂃 User Interface Requirements
􀂃 External Software Interface / Compatibility Requirements
􀂃 Reports Requirements
􀂃 Security Requirements
• Use Case Specifications
• Acceptance Criteria

Design Document:
1. The developers produce a "System Design" from the "System Specification". This takes the features required and maps them to various components, and defines the relationships between these components. The whole design should result in a detailed system design that will achieve what is required by the "System Specification

1.This process of designing exactly of the specifications are to be implemented. How the software to writen, including object modelwith properties and methods, Databse Designing,Cleint server architecture.

Out put of this Phase

• Detailed Design Document, containing:
  • Architecture Diagram
  • Detailed Sequence Diagram
  • Detailed Class Diagrams
  • Detailed Context Object Diagrams
  • Implementation Plan for each Function
  Stored Procedures
  Function Description
  •PhysicalDataMode

Project Manaager :

• Preparation of Software Requirements Specification (SRS)
• Formation Development Team,Test Team
• Management of requirements through out the project life cycle activities
• Preparation of Detailed Design Document
• Unit Test cases and Integration Test cases
• Guidance on programming and related coding conventions / standards

QA Manager :

• Preparation of System Test Plan
• Formation of Test Team
• Schedule Preparation
• Module Allocation
• Reviews on Test Process
• Client Intraction
• Verify Status Reports

Teast Team(Testers & Test Lead) :
Testing, is the core competence of any Testing Organization.

• Understand the Application Under Test
• Prepare test strategy
• Assist with preparation of test plan.
• Design high-level conditions
• Develop test scripts
• Understand the data involved
• Execute all assigned test cases
• Record defects in the defect tracking system
• Retest fixed defects
• Assist the test leader with his/her duties
• Provide feedback in defect triages
• Automate test scripts
• Understanding of SQL

Test Plan

This document is a deliverable to client. It contains actual plan for test execution with details to the minute.

Test Execution Sequence
Test scripts can either be executed in a random format or in an sequential fashion. Some applications have concepts that would require sequencing of the test cases before actual execution. The details of the execution are documented in the test plan.
Sequencing can also be done on the modules of the application, as one module would populate or formulate information required for another.

Allocation of test cases among the team
The Test team should decide on the resources that would execute the test scripts. Ideally, the tester who designed the test script for the module executes the test. In some cases, due to shortage of time or resource at that point of time, additional test scripts might have to be executed by some members of the team.

Clear documentation of responsibilities is done in the test plan.

Allocation of test cases on different passes
All test scripts may not be possibly executed in the first passes. Some of the reasons for this could be

• Functionality may some-times be introduced at a later stage and application may not support it, or the test team may not be ready with the preparation
• External interfaces to the application may not be ready
• The client might choose to deliver some part of the application for testing and rest may be delivered during other passes

Targets for completion of Phases
Time frames for the passes have to decided and committed to the clients well in advance to the start of test. Some of the factors consider for doings so are
Number of cases/scripts: Depending on the number of test scripts and the resource available, completion dates are prepared
Complexity of Testing: In some cases the number of test cases may be less but the complexity of the test may be a factor. The testing may involve time consuming calculations or responses from external interfaces etc
Number of Errors: This is done very exceptionally, Pre-IST testing is done to check the health of the application soon after the preparations are done. The number of errors that were reported should be taken as a benchmark