The document discusses various aspects of project management including planning, scheduling, costing, and monitoring software projects. It also discusses requirement management which involves managing changes to software requirements and using tools like requirement traceability matrices. Configuration management is also covered which deals with version control and tools to manage changes made during a project. Finally, the document discusses software testing including test plans, test cases, classifications of defects, and testing principles.

1. PROJECT MANAGEMENT

2. PROJECT MANAGEMENT Project Management is nothing but Organising, planning and scheduling software projects. - Delivered on time - On Schedule - Software needed

3. Needs for Project Management Subject to Budget & Schedule Includes - Project Planning - Project Scheduling - Project Costing - Monitoring Reviews - Report Writing & Presentation

4. Project Management Manual (documentation) Automation Tool (Report - MPP )

5. Microsoft Project Plan - MPP

6. Requirement Management Requirement Management is managing changes in the evolving software in a cost effective manner. Having track of all requirements during the entire process of the software development to reduce the ratio of defects.

7. Requirement Management Manual (Traceability Matrix) Automation Tools Requisite Pro - Rational TBI Caliber – Technology Builder Incorporation QSS Doors – Quality System Software

8. Requisite Pro

9. Manual Requirement Traceability Matrix A Requirement Traceability matrix is created by associating requirements with the work products that satisfy them.

10. Requirement Traceability Matrix - Sample 148 The account number must exist in the Customer Database; if not, an appropriate error message must be displayed . 3.1 Functional Specification 147 An account number must be entered of 8 digits . Invalid account number must be diagnosed with appropriate error message. 3.1 Functional Specification Test case Requirement Section Source document

11. Configuration Management Standards and procedures for managing Version Control of a software product It mainly deals with - Version Control - changes made in project

12. Configuration Management Manual Automation tools

13. Manual (CM) Project Name CM System (Contains All the changes or versions) Shared (Current Version) Draft ( Forecasted )

14. Automation Tools(CM) Types Of Tools : VSS =>Visual Source Safe(Microsoft Product) Rational Clear Case =>(Rational Corporation Product) CVS =>Concurrent Version System.(free tool - Open Source) [wincvs.org]

15. Software configuration management plan (SCMP) CI - Configurable Item CR - Change Request CCB - Change Control Board Base Line ( No Changes ) Check In Check Out

16. What is primary role of software testing ? Determine whether the system meets specifications(producer view) Determine whether the system meets business and user needs(customer view)

17. Test Plan Road map for the entire testing activity Test Case Set of procedures which we execute in our system to find defect

18. Role of Tester Find Defect, Not Correcting the Defect What is Defect? Variance from the Customer’s Requirement.

19. What is Defects? The purpose of testing is to uncover defects. A defect is a variance from a Customer’s Requirement. Two categories of defects are: Variance from product specifications Variance from customer/user expectation.

20. Classifications of Defects Producers point of view Wrong : Specified in the SRS But Implemented Wrongly in the Project Missing : Specified in the SRS but not implemented in the project Extra : Not Specified in the SRS but implemented in the Project Customer point of view When it doesn’t meet his Business Scenario

21. Principles of Testing Principles of Testing: Testing must find the largest number of errors in the least amount of time. Test case development should begin immediately after requirements definition.

22. Testing Economics And Cost Traditional Testing Continuous Testing Accumulated Accumulated Accumulated Accumulated Test Cost Error Remaining Error Remaining Cost 0 20 10 $10 0 40 15 $25 0 60 18 $42 $480 12 4 $182 $1690 0 0 $582 Testing Requirement Code Production Design

23. Testing Policy A Testing Policy is management’s definition of testing a department. Quality Policy A quality policy is again a management definition of providing customer satisfaction for the first time and every time.

24. Testing Static Dynamic Functional Structural (Functionality of the program) (Logic of the Program) Black Box Testing White Box Testing