WHERE AM I?Project System Project Management Plan Version: SPMP Final Copy Prepared by Team #13 Efraim KORKMAZ – Selcuk DEMIRCI – Ismet Serturk BASOGLU January 7th, 2010 Where am I? PROJECT Preface In this report, the correct way to get team members has made plans. These reports and team members, supervisor checks. This report covers a summary including purpose, summary, objectives, constraints, schedule, budget summary. Moreover, this report contains managerial process like estimation, staffing resource allocation, quality control and risk management plans. Version History Version 1 2 Status* Released In Change Date 21.10.2009 08.01.2010 Responsible Ismet Serturk BASOGLU Ismet Serturk BASOGLU SPMP 1.0 SPMP 1.1 Version Definition *: Draft, In Review, Released, Approved, Rejected, In Change Atılım University COMPE/SE/ISE 491-492 2/36 Team # 13 (Team Lost) System Project Management Plan Version: Final Copy Where am I? PROJECT List of Figures List of Tables Table 1. Project Deliverables……………………………………………………………………..9 Table 2. Internal structure……………………………………………………………………….12 Table 3. Project Responsibilities…………………………………………………………………12 Table 4. Product Function I/O Summary…………………………………………………………13 Table 5. Function Point Metrics………………………………………………………………….14 Table 6. Complex Adjustment Values…………………………………………………………..16 Table 7. Project work activity……………………………………………………………………19 Table 8. Resource allocation for Work Activity………………………………………………..20 Table 9. Resource Allocation for customer Meeting……………………………………………20 Table 10. Resource Allocation for preparing SPMP…………………………………………….21 Table 11. Resource Allocation for preparing SRS………………………………………………22 Table 12. Resource Allocation for preparing SDD……………………………………………..22 Table 13. Resource Allocation for preparing STD……………………………………………….23 Table 14. Resource Allocation for Coding………………………………………………………23 Table 15. Resource Allocation for preparing Testing…………………………………………..24 Table 16. Resource Allocation for preparing User Manual……………………………………….24 Table 17. Resource Allocation for Deployment…………………………………………………..24 Table 18. Schedule and Budget Allocation for Customer Meeting………………………………..25 Table 19. Schedule and Budget Allocation for Preparing SPMP…………………………………25 Table 20. Schedule and Budget Allocation for Preparing SRS……………………………………26 Table 21. Schedule and Budget Allocation for Preparing SDD………………………………..26 Table 22. Schedule and Budget Allocation for Preparing STD…………………………………27 Table 23. Quality Control Plan…………………………………………………………………..28 Table 24. Probability of Risks……………………………………………………………………29 Table 25. Ratio of Probability……………………………………………………………………..29 Table 26. Product Time Schedule…………………………………………………………………32 Atılım University COMPE/SE/ISE 491-492 3/36 Team # 13 (Team Lost) System Project Management Plan Version: Final Copy ............................1...........................................3........................3...............................................................27 5.................................... PROJECT ORGANIZATION............28 5....................... MANAGERIAL PROCESS PLANS................................... Methods...............................................1........ SRS............................1............................................ For these IEEE templates considers for SPMP........................................1..............................................................................28 5..1.. Quality Control Plan............................... Reporting Plan.............34 7... SUPPORTING PROCESS PLANS..........4......................................................................................13 5.................................................. Project Deliverables.......................................3............................................................................. Each deliverable document will be reviewed by the supervisor.............................1...................4........................2.... Control Plan................................3........ and STD.................................. Internal Structure..... Infrastructure Plan......................................................................................2......2................1.9 2......2..........................................1.........2.......17 5...27 5.................................................19 5......................... ACRONYMS..... DEFINITIONS............................................................. Tools......12 4..............................................6 1..................... Resource Allocation...........13 5..............................24 5..................28 In our project.......................................................................................................................... Schedule Control Plan........... Product Acceptance Plan.............................................................................................3...3..............................................................3.................1.....35 All documents will be made according to IEEE standards......................... Budget Allocation......................................................... SDD.........................9 1...4...............................................................................27 5.........................................................................................................................27 5...3................................................................................................................................2.............................. Work Plan...........................................1.............................................................................................................................................................................................17 5..................................................................................29 6......................................................... If we will encounter any problem.................. and Objectives.......1.................34 7..... Quality Assurance Plan........................................................................................................................................................................................................................................................... Project Staff Training Plan...................... Evolution of the SPMP...32 7.............................................................................................................................4................................. Configuration Management Plan...........................19 5...................................................................................................28 5.11 4............................ Documentation Plan.. External Interfaces..........32 6..............................16 5................................1............................................3.......................... Schedule and Budget Summary.....................................................................................3 TABLE OF CONTENTS............................................................................................................................2.................................... OVERVIEW...............................................6 1................................................................. Estimation Plan.....................................................................3.......... Scope.........................1.................................................5..................................... Work Activities.........................................................2.........2........... each of metrics are saved system database.............................................................................................................4.. Requirements Control Plan........................... Risk Management Plan............................................. Project Responsibilities......................................................................................................................................................... and Techniques................................................... Project Summary.............................................................................................3................... Schedule Allocation.....3 LIST OF TABLES .........12 4............2.....................17 5.......6 1........................1................1..1...........7 1................1.............................6 1.......................32 6...............12 5.........................4....................................... Description of Risks..10 3..............................................................................12 4............................ Metrics Collection Plan...2.....35 Atılım University COMPE/SE/ISE 491-492 4/36 Team # 13 (Team Lost) System Project Management Plan Version: Final Copy ....3...........................................2 LIST OF FIGURES............................2........................................13 5................ Purpose...........4 1.......... Assumptions and Constraints..................................................................................................................3.............................Where am I? PROJECT Table of Contents PREFACE................... we will use these saved metrics with connect system database............................... TECHNICAL PROCESS PLANS.................................2............................... REFERENCE MATERIALS................34 7..................... Start-up Plan............................ Process Model.............................................31 6............... AND ABBREVIATIONS.......................................................................................31 6......................................... Resource Acquisition Plan............................................................... ...................................35 7........1................................................. Deployment Plan................................................ Appendix 1 – Ganchart.....................5.............................................................................Where am I? PROJECT 7............36 Atılım University COMPE/SE/ISE 491-492 5/36 Team # 13 (Team Lost) System Project Management Plan Version: Final Copy ...........................................4............... Review Plan.........................36 8............................................. APPENDICES...................................35 8.................................................................................................................................... . user will press search button and enter locations’ name or coordinate and find this location with the help of GPS program. Scope. 6/36 Team # 13 (Team Lost) System Project Management Plan Version: Final Copy Atılım University COMPE/SE/ISE 491-492 . user will press delete or show button and delete or show these objects from system database.1. with the enter name or coordinate.. • When user want delete or show saved objects like locations or path thoughts. Project Summary Purpose. we will do some operations like save path throught on a map. and show where he or she is with markers. • When user want where he or she is.1. coordinate. user will press save button and save this location or path throught from system database.1 Assumptions: We assumed that the following points exist: • Be present at the computer with the GPS map to establish a connection.2. 1. countries.2.1. • When user want to go somewhere and if user do not know this place.1.Where am I? PROJECT 1.2 Scope: The main goal and scope of our project is with the help of GPS is to mark and save where we are. they open GPS program in his or her mobile phone and start send coordinateness’ from host. 1.1.1 Purpose: Our main purpose of our project is with the help of GPS is to determine our position. path throught and search any location on a digital map.1. to save the way we go and search cities.1. • Due to external factors. streets etc.1. program will not work nicely. 1. save our location. and Objectives 1. Overview 1.1.1. Assumptions and Constraints 1.3 Objectives: Our objectives are .1. 1. And computer Take these coordinates from host. • When user want save something like location or path throught. Lack of adequate communication between team members. It defines which process model is chosen for the project life cycle.2009 Reviewed Initial Plan SPMP Document Revised version(submitted) Software Project Management 21.3. may not work properly.Where am I? PROJECT • • • • Due to system failures. Connection between GPS and Computer. the customer company if it exists.2009 processes 01.1.2 Constraints: Our project constraints are: • • • • To avoid a more expensive product Density of the other courses in the university Lack of experience of the members of the project.10.10. some functions may not work properly. Project Deliverables Description Delivery Date Work Product Problem Statement Initial Plan Define the problem (submitted) 30. purpose and objectives of the project. It is used to document agreed deliverables Atılım University COMPE/SE/ISE 491-492 7/36 Team # 13 (Team Lost) System Project Management Plan Version: Final Copy . Maybe. Program will bought by few users.2.09. Be limited to the project calendar. Not to find enough time.2009 Plans is used to define the scope.10. our project will not finish at the proper time.2009 Define the managerial (submitted) technical and01. • • 1. 1. Many plans are considered in order to define the assumptions and constraints of the project. Maybe.1. to specify roles and responsibilities of team members. 02.2010 is used to describe plans for STD Document Atılım University COMPE/SE/ISE 491-492 8/36 Team # 13 (Team Lost) System Project Management Plan Version: Final Copy .11. It includes a set of use cases which describes the user-system interactions. It specifies the form of the document used to specify system architecture and application design in a software related project.01.01.12.2010 At the end of first and second 26-27-28. It documents all the information about the design.Where am I? PROJECT and their dates.2009 used for complete description of design of the software of the system to be developed. Reviewed SDD Document Presentation Revised version 22.2010 Reviewed SRS Document SDD Document Software Design Description is 30.01.2010 semester 2 presentations will be done which reflects the work we done during project development.2010 Software Requirements16.2009 Specification is used to describe the behavior of the software of the system to be developed. It documents the functional and nonfunctional requirements of the system.03. Reviewed SPMP Document SRS Document Revised version 08. Revised version 25. Software Test Documentation15. Evolution of the SPMP After this report.2010 Table 1. Each and every updates of those deliverables will be announced from the website as well. SDD.06. SRS.Where am I? PROJECT testing the verification activity Reviewed STD Document Presentation software.1. 1. Schedule and Budget Summary We estimate schedule allocation in section 5.06. students and advisors with the new additions are possible. Any and validation 07.2010 last versions 18.4. These deliverables can be downloaded from our website.06.06.2010 Revised Version At the end of first and second15-16-17.2.2.2010 semester 2 presentations will be done which reflects the work we done during project development. All these documents will be prepared according to the IEEE standards. Project Deliverables Final Versions of documents Project Contest There will be four major deliverables in the project which are SPMP. All documents are given with07. Atılım University COMPE/SE/ISE 491-492 9/36 Team # 13 (Team Lost) System Project Management Plan Version: Final Copy . 1.4 combining with budget allocation. and STD. 1997 Atılım University COMPE/SE/ISE 491-492 10/36 Team # 13 (Team Lost) System Project Management Plan Version: Final Copy . Roger S. IEEE Standard for Software Project Management Plans Pressman. Work breakdown Structure. Software Engineering. E.. IEEE CS Press. Software Engineering Project Management. R.. Reference Materials • • • • • • IEEE Std 1058-1998. 4th edition. 1997 Fairley.Where am I? PROJECT 2. McGraw-Hill. Acronyms.Where am I? PROJECT 3. Definitions. and Abbreviations CMMI: Capability Maturity Model Integration SPMP: Software Project Management Plan SRS: Software Requirements Specification JVM: Java Virtual Machine V&V: Verification and Validation XML: Extensible Markup Language HW: Hardware SW: Software LOC: Line of Code KLOC: Kilo Line of Code IEEE: Institute of Electrical and Electronical Engineers JRE: Java Runtime Environment COCOMO: Constructive Cost Model IDE: Integrated Development Environment RAM: Read Only Memory XML: Extensible Markup Language SDD: Software Design Description STD: Software Test Documentation WBS: Work Breakdown Structure PC: Personal Computer Atılım University COMPE/SE/ISE 491-492 11/36 Team # 13 (Team Lost) System Project Management Plan Version: Final Copy . 4. External Interfaces This project is a senior project.com [email protected] demirci_40@hotmail. Therefore.Where am I? PROJECT 4. documents are delivered as a new version. Project Responsibilities Responsibility Project Member. Web Developer Web Developer.1. Internal structure 4. project will controlled by supervisor and quality group in each step. Documentation E-Mail [email protected] MEMBER NAME Ismet Serturk BASOGLU Efraim KORKMAZ Selcuk DEMIRCI Table 3. Project Organization 4.2. Documentation Tester. Phases Internal Structure Responsible Project Manager Web Developer Documentation Tester Project Management Web Development Documentation Testing & maintenance Table 2. Supervisor will determine mistakes on project before implementation. Project Responsibilities Atılım University COMPE/SE/ISE 491-492 12/36 Team # 13 (Team Lost) System Project Management Plan Version: Final Copy . After GPS team correct mistakes.3. This report is the first design of SPMP. 5. we can not expect an adequate data. system has saved Objects for Delete or Load some objects User will do Search User will as where I am • • • • • • Table 4.1. GPS Track Maker. path throught Delete objects like saved maps and path throught Load objects like saved maps and path throught by press load button Search something like cities. In the following subsections. Using the following function points.1. Number of external interface: 6 (Microsoft Visual C# 2008 or C# or Microsoft Visual Basic 2008. Start-up Plan This section contains our project’s estimation plan. OS. staffing plan. Managerial Process Plans 5. with enter location name or location coordinate User will ask where I am Outputs • Error Message (if user Search Wrong place or Press Load if system will not have saved Objects. Printing) Atılım University COMPE/SE/ISE 491-492 13/36 Team # 13 (Team Lost) System Project Management Plan Version: Final Copy . countries etc. all these plans will exist with their explanations in the details. we will predict our estimation plan. and training plan.Where am I? PROJECT 5. resource acquisition plan. countries etc… shown by after Press Search Button Shown where user is after user ask where I am Inquiries • User will look. Product Function I/O Summary Number of inputs: 6 Number of outputs: 4 Number of inquiries: 3 Number of files: There exist no files. Estimation Plan The beginning of a project.) Load Objects Show by after Press Load Button Searched cities. Inputs • • • • • Enter the GPS Program Save something like maps.. it is difficult to predict.1. Function Point Metrics Atılım University COMPE/SE/ISE 491-492 14/36 Team # 13 (Team Lost) System Project Management Plan Version: Final Copy .Where am I? PROJECT Measurement Parameter Inputs Outputs Inquiries Files External Interfaces TOTAL Count ( C) 6 4 3 0 6 Weighting Factor(W) 3 4 3 7 5 W*C 18 16 9 0 30 73 Table 5. heavily environment? utilized operational 1 5 Not directly related but will run in the same memory space with other operational programs. Complex Adjustment Values Function Point= Count-Total*[0. outputs.01*sum(Fi)] Atılım University COMPE/SE/ISE 491-492 15/36 Team # 13 (Team Lost) System Project Management Plan Version: Final Copy . 2 others are middle Authentication 5 mechanism and 8 9 Are the master files updated on-line? Are the inputs.65+0.Where am I? PROJECT # 1 Influence Factors Does the system require reliable backup and recovery? Weight (Fi) Comments There is no back-up facility provided 5 by the system Online data collection for batch 2 Are data communications required? 5 process Data transfer on-line in one direction 3 Are there distributed processing 1 functions? 4 Is performance critical? Online response time is not critical 4 5 Will the system run in an existing. files or inquiries complex? 1 0 1 1 1 2 1 3 1 4 Is the internal processing complex? flexibility make the system complex The code can be adopted to other Is the code designed to be reusable? 4 Are conversion and installation included in the design? Is the system designed for multiple installations in different organizations? Is the application designed to facilitate change and ease of use by the user? ΣFi 4 45 0 4 systems Only for mobile application There is no need to installation in different organization Design and interfaces make the system flexible Table 6. Transaction is online 6 7 Does the system require on-line entry? Does the on-line data entry require the input transaction to be built over multiple screens or operations? 4 1 Master files updated online Only security issues are complex. 0 for ab .5 GB RAM (min) 120 GB hard disk space Ethernet card 512 MB Graffic Card In addition to these HW requirements also the following SW requiremnets should be satisfied: Visual C# Visual Basic Atılım University COMPE/SE/ISE 491-492 16/36 Team # 13 (Team Lost) System Project Management Plan Version: Final Copy .01* 45] Function Point= 80.0*(4.65+0. we will use team members computers. Resource Acquisition Plan Our entire Project.711 months E/D ratio gives the recommended number of people.6574)1.35 for db So: E=3.12 = 16. These programs average Language factor is 58.Where am I? PROJECT Function Point= 73*[0. For Our Project it is: E/D=16.805 person-month D=2.40/1000=4.2.40 KLOC=4657.0 GHZ 1. 6574 By using cocomo equations.805)0.12 for bb .35= 6.5*(16.711=2. 2.1.5 for cb and 0. When we put it to the equation we get: LOC=80. E=ab(KLOC)bb (Effort) D=cb (E) db (Duration) Our Project is semi-detached so we use 3. 1.30*58=4657. 5. The worst computer has following hardwares: P IV – 3. 30 COCOMO LOC=FP*Language factor We use Visual C# or C# or Visual Basic.504 ≈3 as our group consist of three people we fulfill necessary human resources.805/6. we found the following results. 1 2.1.2 1. 5.2.4 2. they will gain knowledge about these programs. 5.1 1. When they meet.7 2.2 2.2.8 2. Visual Basic.6 2.3 2. C# and GPS Track Maker. Project Staff Training Plan GPS team members will learn that don’t know topics and develop them.3.5 2. Thus.3 2 2. Work Plan Work Activities In the following table you can see the work activities of the Our Project: 1 1. They will continuously search about this project. they transfer knowledge from member to another.Where am I? PROJECT C# GPS Track Maker MS Office MS Project Internet Explorer 5.9 2. The team members don’t have enough knowledge and experience in Visual C#.10 CUSTOMER MEETING Contact with customer Problem Description Requirements Gathering PREPARING SPMP Work Products & Activities Decomposition Product Size Estimation Process Model Resource Allocation Schedule Allocation Risk Management Plan Technical Process Plans Supporting Process Plans Documentation Review of SPMP Atılım University COMPE/SE/ISE 491-492 17/36 Team # 13 (Team Lost) System Project Management Plan Version: Final Copy .1. 6 4.5 5.12 3 3.2 4.2 5.7 3.3 5.8 5 5.9 4 4.8 3.5 3.Where am I? PROJECT 2.4 3.7 4.6 3.5 4.3 4.3 3.11 2.4 4.6 Revised SPMP Approval of SPMP PREPARING SRS Contact with Customer Formal Identification of User Group Product Functions Behavioral Requirements Specification Non-Behavioral Requirements Specification Documentation Review of SRS Revised SRS Approval of SRS PREPARING SDD SDD Basic Concepts Database Design Interface Design Algorithms Design Documentation Review of SDD Revised SDD Approval of SDD PREPARING STD V&V Management V&V Acquisition V&V Supply V&V Development V&V Operation V&V Maintenance Atılım University COMPE/SE/ISE 491-492 18/36 Team # 13 (Team Lost) System Project Management Plan Version: Final Copy .2 3.4 5.1 3.1 5.1 4. 2 6.7 5.1 7.2.1 6.2 6.2.9 5.3 7 7. Schedule Allocation We estimate schedule allocation in section 5. Resource Allocation Tables related to resource allocation are stated below: Atılım University COMPE/SE/ISE 491-492 19/36 Team # 13 (Team Lost) System Project Management Plan Version: Final Copy .3 8 8. 5.2 6.2. Project work activity 5.2.Where am I? PROJECT 5.1.2 9 9.1 Documentation Review of STD Revised STD Approval of STD CODING GPS Track Maker Management GPS Track Maker Parsing GPS Track Maker Creation CODE REVIEW Authorization User interface design Report Preparation TESTING GPS Test Location Test System Test USER MANUAL GPS User Manual Track Maker User Manual DEPLOYMENT Approval of the product Table 7.1 6.1 6.2.3.1.2 7.4 combining with budget allocation.2.10 6 6.1 8.2.8 5. Resource Allocation for customer Meeting PREPARING SPMP WBS 2.2 WORK PACKAGES Contact with customer Problem Description SW TOOLS Ms Office.1 2. 10581998 IEEE Std. 10161998 IEEE Standards IEEE Standards IEEE Std. Email IEEE Std. 8301998 IEEE Std.1 1. Java Team PC and peripherals HUMAN RESOURCES Team Team HW RESOURCES PC and peripherals Table 9. Planning And Coordination SW Engineering SW Engineering SW Engineering Knowledge of Java and GPS Track Maker Knowledge Of Control Engineering and Testing Techniques Knowledge of User Manual Standard Knowledge of Review Techniques BASED ON Face to face.2 WORK PACKAGES Work Products & Activities Decomposition Product Size Estimation SW TOOLS MS Office.Where am I? PROJECT WORK ACTIVITY Customer Meeting Preparing SPMP Preparing SRS Preparing SDD Preparing STD Coding Testing User Manual Deployment REQUIRED SKILL Human Relations Knowledge of IEEE Std and Estimation Techniques. 10581998 IEEE Std. MS Project MS Office HUMAN RESOURCES Team Team HW RESOURCES PC and Peripherals PC and Atılım University COMPE/SE/ISE 491-492 20/36 Team # 13 (Team Lost) System Project Management Plan Version: Final Copy .3 Requirements Gathering Ms Office. 10631987 IS 502 Standards Table 8. Resource allocation for Work Activity CUSTOMER MEETING WBS 1. Java 1. Visual C# Ms Office Ms Office.10 2.1 3.9 2.3 2.4 3. Visual C# HUMAN RESOURCES Team Team Team Team Team Team Supervisor and HW RESOURCES PC & Peripherals PC & Peripherals PC & Peripherals PC & Peripherals PC & Peripherals PC & Peripherals Atılım University COMPE/SE/ISE 491-492 21/36 Team # 13 (Team Lost) System Project Management Plan Version: Final Copy .11 2.Where am I? PROJECT Peripherals 2. Resource Allocation for preparing SPMP PREPARING SRS WBS 3.5 3.2 3.3 3.5 2.7 WORK PACKAGES Contact with Customer Formal Identification of User Group Product Functions Behavioral Requirements Specification Non-Behavioral Requirements Specification Documentation Review of SRS SW TOOLS Ms Office Ms Office Ms Office.7 2.6 2.12 Process Model Resource Allocation Schedule Allocation Risk Management Plan Technical Process Plans Supporting Process Plans Documentation Review of SPMP Revised SPMP Approval of SPMP MS Office MS Office MS Office MS Office MS Office MS Office MS Office MS Office Team Team Team Team Team Team Team Supervisor and Customer Team PC and Peripherals PC and Peripherals PC and Peripherals PC and Peripherals PC and Peripherals PC and Peripherals PC and Peripherals PC and Peripherals - Table 10.4 2.6 3.8 2. 3 5.1 4.2 4.4 4.4 WORK PACKAGES V&V Management V&V Acquisition V&V Supply V&V Development SW TOOLS MS Office MS Office. Visual C# MS Office MS Office 22/36 HUMAN RESOURCES Team Team Team Team HW RESOURCES PC &Peripherals PC &Peripherals PC &Peripherals PC &Peripherals Atılım University COMPE/SE/ISE 491-492 System Project Management Plan Version: Final Copy Team # 13 (Team Lost) .3 4.7 Team 4.8 3.2 5. Visual C# - HUMAN RESOURCES Team Team Team Team Team HW RESOURCES PC and Peripherals PC and Peripherals PC and Peripherals PC and Peripherals PC and Peripherals PC and Peripherals - 4. Visual C# Team PC & Peripherals PC & Peripherals Table 11.6 4.8 - Table 12.Where am I? PROJECT Customer 3. Resource Allocation for preparing SDD PREPARING STD WBS 5. WORK PACKAGES SDD Basic Concepts Database Design Interface Design Algorithms Design Documentation Review of SDD Revised SDD Approval of SDD SW TOOLS MS Office MS Office MS Office MS Office MS Office. Resource Allocation for preparing SRS PREPARING SDD WBS 4. Visual C# MS Office.5.9 Revised SRS Approval of SRS Ms Office.1 5. 3 WORK PACKAGES GPS Track Maker Management GPS Track Maker Parsing GPS Track Maker Creation CODE REVIEW Authorization User interface design Report Preparation Visual C# Visual C# MS Office SW TOOLS MS Office.2.1 6.Where am I? PROJECT 5.2 6.9 5.10 V&V Operation V&V Maintenance Documentation Review of STD Revised STD Approval of STD MS Office MS Office MS Office MS Office - Team Team Team Team - PC &Peripherals PC &Peripherals PC &Peripherals PC &Peripherals PC &Peripherals PC &Peripherals Table 13. Resource Allocation for Coding TESTING WBS 7.7 5.2.1 6.5 5.1. GPS Track Maker Management GPS Track Maker GPS Track Maker HUMAN RESOURCES Team Team Team Team Team Team Team HW RESOURCES PC &Peripherals PC &Peripherals PC &Peripherals PC &Peripherals PC &Peripherals PC &Peripherals PC &Peripherals Table 14.3 WORK PACKAGES GPS Test Location Test System Test SW TOOLS GPS Track Maker GPS Track Maker GPS Track Maker HUMAN RESOURCES Team Team Team HW RESOURCES PC &Peripherals PC &Peripherals PC &Peripherals Atılım University COMPE/SE/ISE 491-492 23/36 Team # 13 (Team Lost) System Project Management Plan Version: Final Copy .1 6.2 6.1 7.2 6. Resource Allocation for preparing STD CODING WBS 6.1.2.6 5.2 7.8 5. Budget and schedule allocation tables for each work activity are shown below: Customer Meeting WBS Work Packages Start Date (D.Y) Work Hour People Assigned Cost (YTL) Atılım University COMPE/SE/ISE 491-492 24/36 Team # 13 (Team Lost) System Project Management Plan Version: Final Copy .10.2009 Work Hour 1 2 2 People Assigned Team Team Team Cost (YTL) 45 90 90 Table 18. Resource Allocation for preparing User Manual DEPLOYMENT WBS 9.2.Y) 16. Resource Allocation for preparing Testing USER MANUAL WBS 8.1 and taken as a base of budget allocation.Y) 1.4.M.10.10.M.2009 16.3 Contact with customer Problem Description Requirements Gathering 16. Budget Allocation Work activities are stated in the section 5.1 1.1 8.Y) End Date (D.2 WORK PACKAGES GPS User Manual Track Maker User Manual SW TOOLS MS Office MS Office HUMAN RESOURCES Team Team HW RESOURCES PC &Peripherals PC &Peripherals Table 16.2 1.1 WORK PACKAGES Approval of the product SW TOOLS HUMAN RESOURCES Team HW RESOURCES PC &Peripherals Table 17.Where am I? PROJECT Table 15.2009 16. We determined the salary of each team member as 15 YTL/hour and assumed that supervisor has 20 YTL/hour salary.10.2.2009 16.2009 End Date (D.10.M.M. Schedule and Budget Allocation for Customer Meeting Preparing SPMP WBS Work Packages Start Date (D. Resource Allocation for Deployment 5.2009 16.10. 8 2.2009 5 Team 225 2.2009 20.2010 08.2010 06.11.10.2009 10 5 Team Team 450 225 3.2009 End Date (D.7 2.5 15.2009 19.2010 18.11.01.10.10.2009 25.10.11.2009 12.11.3 2.Y) 3.10.2009 06.2009 18.2010 08.11.4 2.2009 19.10.2009 19.10.2009 20.2010 25/36 6 1 Team Supervisor System Project Management Plan Version: Final Copy 270 20 Atılım University COMPE/SE/ISE 491-492 Team # 13 (Team Lost) .10.10.2009 21.2009 21.2010 5 4 2 2 3 3 2 10 1 6 - Team Team Team Team Team Team Team Team Supervisor Team - 225 180 90 90 135 135 90 450 20 270 0 Table 19.2009 19.7 17.10.01.6 3.9 2.11.M.1 Work Products & Activities Decomposition Product Size Estimation Process Model Resource Allocation Schedule Allocation Risk Management Plan Technical Process Plans Supporting Process Plans Documentation Review of SPMP Revised SPMP Approval of SPMP 17.2009 20.01.2 2.11.01.2009 25.4 11.01.2009 10.10.10 2.10.Where am I? PROJECT 2.2009 20.2009 20.2009 08.2009 20.10.10. Schedule and Budget Allocation for Preparing SPMP Preparing SRS WBS Work Packages Start Date (D.2009 Work Hour 1 2 People Assigned Team Team Cost (YTL) 45 90 3.M.2 Contact with Customer Formal Identification of User Group Product Functions Behavioral Requirements Specification Non-Behavioral Requirements Specification Documentation Review of SRS 10.10.11 2.2009 20.11.10.01.11.10.3 3.11.1 3.2009 10.2009 20.01.2009 3 Team 135 3.5 2.10.2009 14.2009 16.2010 06.01.12 18.Y) 10.6 2.2010 18.2009 13.11.11. 2010 22.Y) 09.2009 22.12.03.2010 12.03.2010 13.02.12.Where am I? PROJECT 3.2010 12.03.01.03.1 5.M.02.2009 22.Y) 4.2009 11.M.2010 13.2010 22.2010 10.5 4.2010 11.3 4.2010 Work Hour 4 5 10 12 8 1 8 People Assigned Team Team Team Team Team Supervisor Team Cost (YTL) 180 225 450 540 360 20 360 0 Table 21.2010 11.7 V&V Management V&V Acquisition V&V Supply V&V Development V&V Operation V&V Maintenance Documentation 09.Y) 5.01.12.2010 6 - Team - 270 0 Table 20.2 4.01.01.03.12.2009 30.2010 15.6 5.Y) 10. Schedule and Budget Allocation for Preparing SRS Preparing SDD WBS Work Packages Start Date (D.2010 22.12.2010 25.2009 13.03.2010 15. Schedule and Budget Allocation for Preparing SDD Preparing STD WBS Work Packages Start Date (D.6 4.2009 14.3 5.03.02.02.4 5.02.8 3.12.M.03.2009 13.02.12.4 4.2010 25.12.9 Revised SRS Approval of SRS 25.03.2009 12.1 4.2010 09.2009 30.2010 End Date (D.03.12.2010 09.2 5.12.5 5.2009 15.03.2010 Work Hour 4 3 3 4 3 3 8 People Assigned Team Team Team Team Team Team Team Cost (YTL) 180 135 135 180 135 135 360 Atılım University COMPE/SE/ISE 491-492 26/36 Team # 13 (Team Lost) System Project Management Plan Version: Final Copy .03.8 SDD Basic Concepts Database Design Interface Design Algorithms Design Documentation Review of SDD Revised SDD Approval of SDD 10.2010 22.2010 10.2010 25.7 4.03.2010 End Date (D.03.M. GPS team will not do next step. Team members have a meeting for revision. after the completion of the SPMP step. The results of the meeting between team members will be discussed with supervisor and keep on regular basis. Control Plan Requirements Control Plan Changes are to be made in the requirements. will control all working (documents.2010 1 8 - Supervisor Team - 20 360 0 Table 22. If supervisor is not give approval to the working . 5. Document will be examined for the major/minor revision.2.03. 5.2010 24.3. Schedule allocation and estimation plan will be reconsidered and updated. coding. Document will be updated as a new version of all projects. etc. and they effort to finish the Project.06. Schedule Control Plan The Project consists of certain time interval. Schedule and Budget Allocation for Preparing STD 5.3.2010 24.9 5.3.03.03.3. Resource allocation.) by GPS Team. 5.2010 24.Where am I? PROJECT 5. X Major revisions Atılım University COMPE/SE/ISE 491-492 27/36 Team # 13 (Team Lost) System Project Management Plan Version: Final Copy . demo.2010 24. meeting one or two days in a week.3.2010 24.10 Review of STD Revised STD Approval of STD 24. Budget is not important due to this project is a senior Project.1. Work Products and Suitable to Items Standards Software Requirements Specification (SRS) SRS Review SRS Approval Software Design Description (SDD) SDD Review X X X Needs Revisons Explation X Major revisions Revisions are made and plan is approved. Quality Control Plan Supervisor. Project group members constantly conversation in messanger. who is Atilla BOSTAN.03.8 5.06. Reporting Plan Each of versions of all the documents and updates and status reports will be sent and discussed with the supervisor and upon approval the approved document will be circulated to the other members of the committee. Table 23.3. each of metrics are saved system database. 5.5.3. Major revisions Revisions are made and plan is approved. 5.4. If we will encounter any problem. Metrics Collection Plan In our project.Where am I? PROJECT SDD Approval Software Test Documentation (STD) STD Review STD Approval Project Plan Project Plan Review Approval of Project Plan Design Design Review Design Approval Coding Test Implementation Product Review Product Approval X X X X X Revisions are made and plan is approved. The report on the status of the project will be sent to the members and interview about mistakes or lacks of reports.4. we will use these saved metrics with connect system database. Risk Management Plan Atılım University COMPE/SE/ISE 491-492 28/36 Team # 13 (Team Lost) System Project Management Plan Version: Final Copy . Quality Control Plan 5. 1. Thus.1.1.4.1.1. The GPS Team must.4. Disagree Between Team Members Atılım University COMPE/SE/ISE 491-492 29/36 Team # 13 (Team Lost) System Project Management Plan Version: Final Copy . Probability of Risks Probability > % 80 %80 .2.Where am I? PROJECT RISKS PROBABILITY IMPACT 1(low) – 5(high) REFERENCES Quality of product documentation and coding are not suitable Disagree between team members Unavailability of team members Timing Problem Health problem Mistake in coding System may be work not %35 3 5. GPS team prepares the project planning. try to prepare every documents of project in high priority and control all steps of documentation. Description of Risks Quality of product documentation and coding are not suitable 5. software documentation and coding with less experience.1. 5.1 %8 %8 %15 %35 %15 %15 2 2 4 1 4 4 5.2 5.4. probably Doubtable Unlikely Highly unlikely Table 25.4.4. Ratio of Probability 5.%61 %60 – %41 %40 – %21 < % 20 Uncertainty Statement Almost certainly Probable.4.1.3 Table 24. Team must do control the coding and test every week or control and test small part and back up codes every week.4. they must solve the problem between team members in early time and prevention disagreement things before the conflict.1. Atılım University COMPE/SE/ISE 491-492 30/36 Team # 13 (Team Lost) System Project Management Plan Version: Final Copy . If team have health problem. Before The GPS Team start does project. Mistake in Coding If The GPS Team does not want any mistake in coding.4.4. If The GPS Team has this problem. and may be prevent problem of time. Health Problem The GPS Team must take care of their health.4. 5. msn. they must do work overtime or adjust new part-time labors and work another team member to instead of ill team member.5.6. Team must use all communication (telephone.Where am I? PROJECT The GPS Team must behave respectfully and be careful not disagree with each other. Timing Problem The GPS Team must split the project and prepare the working program in weekly and check each team members program every week and control how project is run. e-mail …) . they have to adjust date before starting the project.3. 5. Unavailability of Team Members The GPS Team must use all common free time to work on project.1.1.4. they must do control the design again and again and contact with instructor when coding and designing.1. If Team does not want any problem. 5. 5. 5. If The GPS Team has a problem about meeting.4.1. System may be not Work The GPS Team must do not notice the mistake in design or coding.7. 18. 2009 Oct. 2009 Jan. 16. 2010 MAJOR Milestone YES YES YES YES Atılım University COMPE/SE/ISE 491-492 31/36 Team # 13 (Team Lost) System Project Management Plan Version: Final Copy . 2009 Oct. 23. 2009 Nov.8. 01. 2009 Oct. 2010 Jan. The schedule plan for the project table will be given in the following table. 20. 2009 Nov. 22.Where am I? PROJECT 6. a prototype of the project will be developed. 01. 2009 Nov.30. 2009 Nov. The initialization of the project will start in October 2009.21. Time Activity Start Date End Date (date/man) Defining PS Initial Planning Reviewing IP SPMP Documenting Reviewing SPMP SRS Documenting SDD Documenting Coding and Testing Total Elapsed Time Oct. 20. 16. And finally at the end of June 2010. Product Time Schedule TASK SPMP SRS DUE TO Oct. 17. we used Waterfall Process Model. 2010 4 21 6 44 6 42 44 100 267 date/man Table 26. 2010 June 19.1.18. 2009 June 10. 2009 Oct. 21. 2009 Dec. 2009 Dec. 2009 Oct. our project will be finished. 2009 Oct. Technical Process Plans 6. Process Model We in our project. 10. 08.26-27-28. 2009 REVİEW DATE DELIVERED Jan. 07. 10. table 24. 2010 Oct. 2009 Jan. at the end of January 2010. 2009 Oct. User Manual. Each team member has one PC with the operating system of Windows XP and Vista. XML. 2009 Mar.15. 2010 June 07. Java. Planning and Coordination.Where am I? PROJECT SDD STD Coding & Testing User Manual Final Product Jan. 6. 6.2. MS Office.5.409.3.Projects that help us the GPS Track Maker and JAVA programs can be downloaded from the internet and available free.4. and Techniques Tools and techniques used to realize these working and to develop final product are shown SW TOOLS: Java. These places may be one team member’s house. By the consultant and the client is missing a delivery point is checked to determine. SW Engineering Processes. internet connection. MS Project. and school’s studying room. library. 2010 NO 6. Infrastructure Plan This software. 2010 April 5. Tools. 2010 YES YES NO NO YES YES YES YES YES June 07.4. Then cover the missing points. Product Acceptance Plan Customer wants a review process will be reviewed and problems will be solved. We also use GPS track maker program for transfer data from GPS to computer and computer to GPS also we are make ourselves develop.. Review and Testing Techniques. a new version is created and delivered to the customer is Atılım University COMPE/SE/ISE 491-492 32/36 Team # 13 (Team Lost) System Project Management Plan Version: Final Copy . hardware and operating system are available from other sources and from the internet is provided by team members. Internet Explorer. HW TOOLS: PC and Peripherals PERSONAL SKILLS: Communication skills. GPS Track Maker 13. below: Methods. Group members identify themselves as areas of project work as a group and as individuals we project focuses. This process shall continue until the customer and supervisor satisfaction is achieved. In this way. and the product will deliver the necessary points will change. the customer really needs to improve the basic product warranties may be the result. Atılım University COMPE/SE/ISE 491-492 33/36 Team # 13 (Team Lost) System Project Management Plan Version: Final Copy . If there are problems to be solved.Where am I? PROJECT presented. 2. First Deliverable: Deliverable Name V1.0 Minor Change for Deliverable: Deliverable Name V1. Configuration Management Plan This part is very important for future changes for our project.0. Verification and Validation Plan: Verification Plan • • • The process of determining to make the right product.0. Project members must follow project Schedule very carefully and projects should be delivered in a time. Such as. Validation Plan • Products are made to ensure that the correct process. like SPMP V1. the report names will also change. Customer meetings are very important. As the regeneration of the report. • • Atılım University COMPE/SE/ISE 491-492 34/36 Team # 13 (Team Lost) System Project Management Plan Version: Final Copy . Supporting Process Plans 7.0 Major Change for Deliverable: Deliverable Name V2. Made full order to produce for needs of customers.1. About producing the right product.1. that’s why these meetings should be well organized. we will quickly review our previous report and we will change our report like desired format.1 7. like SPMP V1. When our project supervisor or customers comes a request for project change. Quality Assurance Plan Quality Assurance Plan: All project reports must be made according to the IEEE a standard format and should be submitted according to this format. All project’s delivered time and every steps made according to accuracy of the SW. Made full order to produce for needs of customers. like SPMP V2.Where am I? PROJECT 7. Documentation Plan All documents will be made according to IEEE standards. STD are completed. Second review is done by supervisor. are reviewed. Review Plan After each phase of Project which are SPMP. 7. SDD. SRS. Supervisor controls verification of the deliverable and to cover requirements of the product. SDD. Thus. Deployment Plan After our project is finish. Atılım University COMPE/SE/ISE 491-492 35/36 Team # 13 (Team Lost) System Project Management Plan Version: Final Copy .5. if people use GPS program.Where am I? PROJECT 7. First review is done by GPS team after the completion of deliverable. SRS. For these IEEE templates considers for SPMP.4. There are two types of review.3. 7. Each deliverable document will be reviewed by the supervisor. and STD. But. their computers or laptops must take signals from satellite. every people use our project. our project resembles a desktop application. 1.Where am I? PROJECT 8. Appendix 1 – Ganchart Atılım University COMPE/SE/ISE 491-492 36/36 Team # 13 (Team Lost) System Project Management Plan Version: Final Copy . Appendices 8.