Project Plan. CivicPlus Activity Metrics Tool. Version 1.0. Keith Wyss CIS 895 MSE Project Kansas State University

Transcription

1 Project Plan CivicPlus Activity Metrics Tool Version 1.0 Keith Wyss CIS 895 MSE Project Kansas State University

2 Table of Contents 1. INTRODUCTION REFERENCES WORK BREAKDOWN STRUCTURE INCEPTION PHASE ELABORATION PHASE PRODUCTION PHASE COST ESTIMATE COCOMO ARCHITECTURE ELABORATION PLAN REVISE VISION DOCUMENT REVISE PROJECT PLAN CREATE FORMAL SPECIFICATION CREATE ARCHITECTURAL DESIGN CREATE TEST PLAN CONDUCT TECHNICAL INSPECTION CREATE EXECUTABLE ARCHITECTURE PROTOTYPE

3 List of Illustrations Figure 1. Project Gantt Chart

4 List of Tables Table 1. COCOMO Cost Drivers and Effort Multipliers... 7 Table 2. Selected COCOMO Effort Adjustment Factors.. 8 4

5 1. Introduction This document serves as the initial project plan for the CivicPlus Activity Metrics Tool. It outlines the basic work breakdown structure and provides a cost estimate using the COCOMO estimation model References 1. Fairley, R. E Managing and Leading Software Projects. Hoboken, NJ: John Wiley & Sons, Inc. 2. Work Breakdown Structure This project will use an iterative process consisting of three phases: Inception, Elaboration, and Production. All requirements gathering, documentation, and software development will take place during these phases. The first phase will start in December 2013 and the other two phases will be completed during the spring of Figure 1 shows the work breakdown structure in the form of a Gantt chart. Figure 1 Project Gantt Chart 2.1. Inception Phase The first phase of the project is the Inception Phase. During the Inception Phase, the vision document, software quality assurance plan, project plan, and an initial prototype will be created. The vision document will contain two parts: the project overview and the requirements. The overview will state project goals and the main product features. The requirements specification will focus on capturing the main requirements of the project in use cases. The project plan will outline the details of the project phases and include a cost estimation and architecture elaboration plan. The software quality assurance plan will 5

6 describe the required documentation and the standards and conventions that will be used during product development Elaboration Phase The second phase of the project is the Elaboration Phase. During the Elaboration Phase, the vision document and project plan will be updated and revised as necessary. Additionally, a formal specification, architecture design, and test plan will be created at this time. The architectural design will be comprised of class and object diagrams complementing the relevant sequence diagrams with each. Additional charts and diagrams will be added to help in the representation of the product architecture. The formal specification will contain a specification based on a published, formal methodology. The test plan will address the required tests to show that the product satisfies the requirements Production Phase The final phase of the project is the Production Phase. During the Production Phase, the source code development will be completed along with the creation of a user manual, component design document, assessment evaluation, and project evaluation. The component design will document the internal design of each component. The assessment evaluation will detail all the testing done on the project. 3. Cost Estimate 3.1. COCOMO This project will use the COCOMO model for cost estimation. COCOMO is a regression-based estimation model developed by Barry Boehm in COCOMO uses 3 sets of equations for effort and schedule depending on what type of project is being estimated. This project will be considered a semidetached project because it s a web application that s driven by a database. For semidetached systems, the following equations will be used: Effort (staff-months) = 3.0 * (Size) 1.12 * EAF Time (months) = 2.5 * (Effort) 0.35 The effort is estimated in staff-months and size is estimated as thousands of source lines of code (KSLOC). The second equation calculates time and outputs it in months using the effort calculated in the first equation. Based on other web application projects that have been completed, this project will use 5 for the size parameter. Effort Adjustment Factor (EAF) is calculated using 15 different adjustment factors and a range of values to represent their individual effort multipliers. Table 1 lists these adjustment factors and the range of possible values for each. 6

7 Cost Drivers Effort Adjustment Factor Very Low Ratings Low Nominal High Very High Extra High Product Attributes RELY Required Reliability DATA Database Size CPLX Product Complexity Computer Attributes TIME Execution Time Constraint STOR Main Memory Constraint VIRT Virtual Machine Volatility TURN Computer Turnaround Time Personnel Attributes ACAP Analyst Capability AEXP Application Experience PCAP Programmer Capability VEXP Virtual Machine Experience LEXP Language Experience Project Attributes MODP Use of Modern Practices TOOL Use of Software Tools SCED Schedule Constraint Table 1 COCOMO Cost Drivers and Effort Multipliers Table 2 lists the adjustment factor values that will be used for this project and reasoning for each one. A lot of the factors have a high classification because I work on web applications using the C#.NET Framework every day at my job, so I am very familiar with most of the technologies and tools that will be used on this project. 7

8 Cost Drivers Classification Value Reasoning RELY Low 0.88 Required reliability is fairly low since any lost data can be generated by running the queries again. DATA Nominal 1.00 The database shouldn't be any larger than other production databases. CPLX Nominal 1.00 Familiar with.net framework and building web applications. TIME Nominal 1.00 Normal use of execution time. STOR Nominal 1.00 Should use normal amount of storage for web application. VIRT Nominal 1.00 Major changes shouldn't occur more than once every 6 months. TURN Nominal 1.00 Should have average turnaround time. ACAP Low 1.19 Don't have a large amount of experience being an analyst. AEXP Nominal 1.00 Have a good understanding and experience in web apps. PCAP High 0.86 Very capable with working on a project of this type and complexity. VEXP High 0.90 Have a lot of experience working with the Microsoft.NET stack. LEXP High 0.95 Work in C#.NET on a daily basis for over 3 years. MODP Very High 0.82 Use these practices on a daily routine. TOOL High 0.91 All tools available and very familiar with each. SCED Nominal 1.00 Flexible schedule, would just like to get done in May EAF 0.57 Table 2 Selected COCOMO Effort Adjustment Factors Using these values, EAF is calculated to be Plugging the EAF value and size estimation into the first equation gives the following result: Effort = 3.0 * (5) 1.12 * 0.57 = staff-months Using the effort result from the first equations gives the following time calculation: Time = 2.5 * (10.37) 0.35 = 5.67 months The result of 5.67 months seems about right for a project of this size and complexity. 4. Architecture Elaboration Plan The following tasks will be completed during the elaboration phase of this project Revise Vision Document The first version of the Vision Document will be updated with sequence diagrams and other details to help capture all the project requirements clearly. Any other missing sections from the inception phase will also be added to the Vision Document to make it accurate. The major professor will give the final approval on the revised Vision Document. 8

9 4.2. Revise Project Plan The first version of the Project Plan will be updated to reflect any scheduling conflicts or updates that may have been found. The major professor will give the final approval on the revised Project Plan Create Formal Specification A model of the Activity Metrics Tool will be formally specified and documented. The major professor and technical inspectors will give the final approval on the formal specification Create Architectural Design UML diagrams will be used to create the architectural design. The major professor and technical inspectors will give the final approval of the architectural design Create Test Plan A test plan will be created that follows the CivicPlus standards for unit and integration testing. The test plan will meet all requirements listed in the Vision Document. The major professor and technical inspectors will give the final approval of the test plan Conduct Technical Inspection The architectural design will be inspected by Jim Flynn and Derek Begnoche who are employees of CivicPlus. The developer will create an inspection checklist that will be submitted to the technical inspectors for them to provide feedback and approve the proposed design. The major professor will give the final approval of the inspection checklist and feedback Create Executable Architecture Prototype An executable prototype will be created and shown during the first presentation. The prototype will implement simple database operations and user login using the CivicPlus LDAP service. 9