Project Roles and Responsibilities

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 triage
• Automate test scripts
• Understanding of SRS

QA Manager

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

Project Manager

• 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

Software Requirements Specification (SRS) Contents

1. Introduction

• Purpose
• Scope
• Major Constraints and References

2. Functional Requirements

• Context Diagram
• Functional Decomposition Diagram
• System Functions
• Database Requirements
• User Interface Requirements
• External Software Interface / Compatibility Requirements
• Reports Requirements
• Security Requirements

3. Use Case Specifications

• Acceptance Criteria

Software Development Process

Plan: Device a Plan
Define your objective and determine the strategy and support methods required to archive that objective
Do: Execute the plan
Create the conditions and perform the necessary training to execute the plan.Make sure every one thoroughly understands the objectives and the plan.
Check: Check the result
Check to determine whether work is progressing according to the plan and whether the expected results are obtained. Check for performance of the set procedures, changes in conditions, or abnormalities that may appear
Act: Take necessary action
If your checkup reveals that the work is not being performed according to plan or that results are not what was anticipated , devise measures for appropriate action.Testing only involves only check component of the plan-do-check-act(PDCA) cycle

Software Development Life Cycle (SDLC)

1. System Information/Engineering and Modeling
a.The initial proposal phase to understand and identify the project requirements and main features proposed in the application
b. By the end of the study the entire client systems, the team furnishes a document that holds specific recommendations for the candidate system. Out Put of this phase

• A rough estimation of efforts and prices for entire project
• A Rough Schedule for entire phase
• Initial business functions in the project

2. System Requirement Analysis & Specification
The objective of this phase to identify and document the user requirements for a proposed system.This phase contains complete information of function, information of the domain for the software,behavior,performance,Interfacing.Out put of this phase is

• An estimate for effort or price for remaining project phases(Design, Development, Testing Deployment, Support)
• Details Schedule of the remaining Phases(Design, Development, Testing, Deployment, Support)
• The final functional specification and analysis for other phases

3. System Analysis and Design
a. This process of designing exactly of the specifications are to be implemented
b. How the software to written, including object model with properties and methods, Database Designing,client server architecture. Out put of this Phase A Final Design Specification
4. Code Generation
a. Design Must be Formatted in to machine readable format
b. With respect of the application the right programming language is used,

• A Beta version of application
• Preliminary Manuals and user document
• Preliminary Technical Documents

5. Testing
Once code is generated Program testing begins.Different testing methodologies are available to unrevealed the bugs.Out put of this phage

• A Final version of complete application
• A Final Manual
• A Final Technical Document

6. Deployment & Maintenance
In This software ready to deploy in customer place, maintenance period starts for the application.Application should create accept the changes in this phase

Quality Control & Quality Assurance

Quality Assurance
All those planned and necessary ideas to provide adequate confidence that the product/service will satisfy the given requirements of quality
Quality Control
All those necessary steps taken for fulfilling the requirements of quality

Some Major Computer System Failures Caused by Bugs

1. In August of 2006 a U.S. government student loan service erroneously made public the personal data of as many as 21,000 borrowers on it's web site, due to a software error. The bug was fixed and the government department subsequently offered to arrange for free credit monitoring services for those affected
2. A September 2006 news report indicated problems with software utilized in a state government's primary election, resulting in periodic unexpected rebooting of voter checking machines, which were separate from the electronic voting machines, and resulted in confusion and delays at voting sites. The problem was reportedly due to insufficient testing
3. Software bugs in a Soviet early-warning monitoring system nearly brought on nuclear war in 1983, according to news reports in early 1999. The software was supposed to filter out false missile detections caused by Soviet satellites picking up sunlight reflections off cloud-tops, but failed to do so. Disaster was averted when a Soviet commander, based on what he said was a '...funny feeling in my gut', decided the apparent missile attack was a false alarm. The filtering software code was rewritten

When to Stop Testing

It's difficult to determine exactly when to stop Testing.The following are some of the cases which can help to decide when to reduce/stop Testing
1. Deadlines(Release/Test Deadlines etc)
2. Test cases completed with certain percentage passed
3. Test budget depleted
4. Coverage of code/functionality requirements reaches a specified point
5. Bug rate falls below a certain level
6. Beta or Alpha testing period ends