Project Management


Published on

Published in: Business, Technology
  • Be the first to comment

No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Project Management

  2. 2. PROJECT MANAGEMENT <ul><li>Project Management is nothing but Organising, planning and scheduling software projects. </li></ul><ul><li>- Delivered on time </li></ul><ul><li>- On Schedule </li></ul><ul><li>- Software needed </li></ul>
  3. 3. Needs for Project Management <ul><li>Subject to Budget & Schedule </li></ul><ul><li>Includes </li></ul><ul><li>- Project Planning </li></ul><ul><li>- Project Scheduling </li></ul><ul><li>- Project Costing </li></ul><ul><li>- Monitoring Reviews </li></ul><ul><li>- Report Writing & Presentation </li></ul>
  4. 4. Project Management Manual (documentation) Automation Tool (Report - MPP )
  5. 5. Microsoft Project Plan - MPP
  6. 6. Requirement Management <ul><li>Requirement Management is managing changes in the evolving software in a cost effective manner. </li></ul><ul><li>Having track of all requirements during the entire process of the software development to reduce the ratio of defects. </li></ul>
  7. 7. Requirement Management Manual (Traceability Matrix) <ul><li>Automation Tools </li></ul><ul><li>Requisite Pro - Rational </li></ul><ul><li>TBI Caliber – Technology Builder Incorporation </li></ul><ul><li>QSS Doors – Quality System Software </li></ul>
  8. 8. Requisite Pro
  9. 9. Manual Requirement Traceability Matrix <ul><li>A Requirement Traceability matrix is created by associating requirements with the work products that satisfy them. </li></ul>
  10. 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. 11. Configuration Management <ul><li>Standards and procedures for managing Version Control of a software product </li></ul><ul><li>It mainly deals with </li></ul><ul><li>- Version Control - changes made in project </li></ul>
  12. 12. Configuration Management Manual Automation tools
  13. 13. Manual (CM) <ul><li>Project Name </li></ul><ul><ul><li>CM System (Contains All the changes or versions) </li></ul></ul><ul><ul><li>Shared (Current Version) </li></ul></ul><ul><ul><li>Draft ( Forecasted ) </li></ul></ul>
  14. 14. Automation Tools(CM) <ul><li>Types Of Tools : </li></ul><ul><ul><li>VSS =>Visual Source Safe(Microsoft Product) </li></ul></ul><ul><ul><li>Rational Clear Case =>(Rational Corporation Product) </li></ul></ul><ul><ul><li>CVS =>Concurrent Version System.(free tool - Open Source) </li></ul></ul><ul><ul><li>[] </li></ul></ul>
  15. 15. Software configuration management plan (SCMP) <ul><li>CI - Configurable Item </li></ul><ul><li>CR - Change Request </li></ul><ul><li>CCB - Change Control Board </li></ul><ul><ul><li>Base Line ( No Changes ) </li></ul></ul><ul><ul><li>Check In </li></ul></ul><ul><ul><li>Check Out </li></ul></ul>
  16. 16. What is primary role of software testing ? <ul><ul><li>Determine whether the system meets specifications(producer view) </li></ul></ul><ul><ul><li>Determine whether the system meets business and user needs(customer view) </li></ul></ul>
  17. 17. <ul><li>Test Plan </li></ul><ul><li>Road map for the entire testing activity </li></ul><ul><li>Test Case </li></ul><ul><li>Set of procedures which we execute in our system to find defect </li></ul>
  18. 18. Role of Tester <ul><li>Find Defect, Not Correcting the Defect </li></ul><ul><li>What is Defect? </li></ul><ul><li>Variance from the Customer’s Requirement. </li></ul>
  19. 19. What is Defects? <ul><ul><li>The purpose of testing is to uncover defects. </li></ul></ul><ul><ul><li>A defect is a variance from a Customer’s Requirement. </li></ul></ul><ul><ul><li>Two categories of defects are: </li></ul></ul><ul><ul><li>Variance from product specifications </li></ul></ul><ul><ul><li>Variance from customer/user expectation. </li></ul></ul>
  20. 20. Classifications of Defects <ul><li>Producers point of view </li></ul><ul><ul><li>Wrong : Specified in the SRS But Implemented Wrongly in the Project </li></ul></ul><ul><ul><li>Missing : Specified in the SRS but not implemented </li></ul></ul><ul><ul><li>in the project </li></ul></ul><ul><ul><li>Extra : Not Specified in the SRS but implemented in the Project </li></ul></ul><ul><li>Customer point of view </li></ul><ul><ul><li>When it doesn’t meet his Business Scenario </li></ul></ul>
  21. 21. Principles of Testing <ul><li>Principles of Testing: </li></ul><ul><ul><li>Testing must find the largest number of errors in the least amount of time. </li></ul></ul><ul><ul><li>Test case development should begin immediately after requirements definition. </li></ul></ul>
  22. 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. 23. Testing Policy <ul><li>A Testing Policy is management’s definition of testing a department. </li></ul><ul><li>Quality Policy </li></ul><ul><li>A quality policy is again a management definition of providing customer satisfaction for the first time and every time. </li></ul>
  24. 24. Testing Static Dynamic Functional Structural (Functionality of the program) (Logic of the Program) Black Box Testing White Box Testing
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.