1. Software Project ManagementforHMS [Hospital Management System]1 7/20/2012

2. What isSoftware Project Management? Software Project Management isthe art and science of planning andleading software projects. It is a sub-discipline of projectmanagement inwhich software projects areplanned, monitored and controlled.27/20/2012 3. Good project managementcannot guaranteesuccess37/20/2012 4. But poor management onsignificant projects alwaysleads to failure.4 7/20/2012 5. Software ProjectManagement Phases :-57/20/2012 6. 6 7/20/2012 7. Project Initiating Process Project Planning Process Project Executing Process Project Closing Process77/20/2012 8. Project Initiating Process Project CharterThe Project Charter is developed during theinitiation phase to formally authorize a project. It has details about the scope of the project, itsdeliverable and what domain needs, problems oropportunities the project addresses87/20/2012 9. Sr MilestoneProposed Date RemarkNo1Design of HMS07/05/2012 First Prototype Shown2Basic Features 03/06/2012 Without Reports3Complete Project 30/06/2012 With Reports9 7/20/2012 10. Feasibility Study A feasibility study has been conducted Technical Feasibility As the proposed system is intranet based; We usePHP and MySQL Legal Feasibility As the technology chosen is open source so theremay not be any legal issues of software.10 7/20/2012 11. SDLC Model Used11 7/20/2012 12. The Iterative Waterfall Model of the Software Life Cycle Requirement GatheringAnalysisDesignCodingTestingInstallation Operation &12 Support 7/20/2012 13. Cost Estimation137/20/2012 14. Business Case A Business Case helps to determine whether or nota project justifies an organizations investment into aproject. Obviously as the in-house resources are readilyavailable, there is no need to hire additionalmanpower; it justifies an organizations investmentinto a project147/20/2012 15. Project Planning Process Change Management Plan Change will happen during our project, theres no way to avoid it. We prepared for changes by developing our system in such a way that it accept changes. We used MVC(Model-View-Controller) architecture to build our system and hence we separates database, web design and web development.15 7/20/2012 16. Communications Management Plan The Communications Management Plan defines the communication requirements for the project and how the information is to be distributed. Effective communications is critical to the success of a project, for this reason we maintain proper flow of information within a team. Project Manager fixes an appointment with the client; accordingly system analysts visit the client and communicate with development team.16 7/20/2012 17. Cost Management Plan(REFER COCOMO FOR ESTIMATION OF EFFORTS ANDDURATION) The Cost Management Plan details how the project costs will be measured and reported upon. We estimated efforts and duration for our project by using COCOMO Model.177/20/2012 18. Human Resource PlanProject Managers 2Team Members Programmer2 DBA 2 System Analyst 218 7/20/2012 19. Project Management PlanThe Project Management Plan states how theproject being executed. See Gantt Chart Next [Reference Tool https://secure.gantto.com/login/gantto.html#demo]197/20/2012 20. TASK START DATEEND DATE 1 Requirement Gathering 05-Apr-201210-Apr-2012 2 Analysis 11-Apr-2012 20-Apr-2012 3 Design of HMS16-Apr-2012 07-May-2012 4 HMS [Basic Features] 08-May-2012 01-Jun-2012 5 HMS [Complete] 04-Jun-2012 13-Jul-2012207/20/2012 21. 21 7/20/2012 22. Work Breakdown Structure (WBS) [Source Tool - http://www.wbsplanner.com/free/wbsp36.php ]22 7/20/2012 23. WBS for HMS23 7/20/2012 24. Project Monitoring and Controlling Process We used timesheet for monitoring various tasks. Completed tasks have been marked cross.247/20/2012 25. Project AcceptanceWe will plan to prepare the Project Acceptancedocument of the project by the Project Sponsor(Client)25 7/20/2012 26. COCOMO Constructive Cost Model COCOMO applies to three classes of softwareprojects: Organic projects - "small" teams with "good" experience working with "less than rigid" requirements Semi-detached projects - "medium" teams with mixed experience working with a mix of rigid and less than rigid requirements Embedded projects - developed within a set of "tight" constraints. It is also combination of organic and semi-detached projects.26 7/20/2012 27. 27 7/20/2012 28. 28 7/20/2012 29. 29 7/20/2012 30. 30 7/20/2012 31. People required (P) = Effort Applied / DevelopmentTime P =16.69 / 7.29= 2.29 2.29 Persons for 7.29 Months 5.56 Persons for 3 Months ( 6 Persons * 30,000 ) = Rs. 1,80,000 For 3 Months => Rs. 5,40,000 BACK TO ORIGIN317/20/2012