Project Plan For agenttool III (Static) Version 2.0 Submitted in partial fulfillment of the requirements of the degree of MSE Deepti Gupta CIS 895 MSE Project Kansas State University Page 1 of 9
TABLE OF CONTENTS 1. Task Breakdown...3 1.1 Inception Phase...3 1.2 Elaboration Phase...3 1.3 Production Phase...3 2. Architecture Elaboration Plan...4 2.1 Revision of Vision Document...4 2.2 Revision of Project Plan...4 2.3 Architecture Design...4 2.4 Development of Prototype...5 2.5 Test Plan...5 2.6 Formal Technical Inspections...5 2.7 Formal Requirements Specification...5 3. Cost Estimate (based on current progress)...5 3.1 Comparison of estimates 6 4. Implementation Plan...6 4.1. Deliverables...6 4.2. Work Breakdown Structure...7 Page 2 of 9
1. Task Breakdown 1.1 Inception Phase The inception phase of the project will be focused on project requirements. A vision document will be prepared detailing the project overview and the critical project requirements. A project plan describing the work to be accomplished in each phase of the project will also be prepared. The project plan will include an estimate of the work load of the project and will establish a schedule for completion of all project activities. A software quality assurance plan will describe the required documentation, standards and conventions that will be used to ensure product quality. A simple prototype will be built during this phase just so as to establish the project feasibility. It will give an idea about the look and feel of the final product. The approval of the required documentation and the first prototype by the supervisory committee after the first presentation will mark the conclusion of the inception phase. 1.2 Elaboration Phase Architecture design will be the focus of this phase. The complete architectural design will be documented using appropriate UML diagrams. Revisions will be made to the initial vision document and the project plan based on feedback from committee members. At least one component of the project will be formally specified using formal specification methodologies. A test plan will describe the way in which testing will be carried out and how defects will be tracked and reported. The technical inspectors will perform architecture review and provide feedback. Finally the first prototype will be refined to demonstrate more product features / functionality. The approval of the required documentation and the second prototype by the supervisory committee after the second presentation will mark the conclusion of the elaboration phase. 1.3 Production Phase Project implementation and testing will be the focus of the production phase. A low level component design will be developed here. The work in this phase will primarily consist of code development, code documentation and unit testing. Page 3 of 9
1.3.1 Code development and testing All project components will be developed and integrated. Unit testing and integration testing will be performed. All test results will be evaluated and documented. Traceability will be established with the requirements as present in the vision document. 1.3.2 Documentation All code will be thoroughly documented. Javadocs will be generated to document package structure with information about various classes, methods and attributes. A test report outlining the conduction and results of the tests will be prepared. A user manual will be prepared which describes the installation and use of the software. The approval of the required documentation and the final project implementation by the supervisory committee after the third presentation will mark the conclusion of the production phase. 2. Architecture Elaboration Plan The following tasks will be completed in the elaboration phase and before the second presentation. 2.1 Revision of Vision Document The Vision Document will be revised to provide a complete representation of all requirements. These requirements will be ranked according to importance. The document revisions will be based on feedback from the committee members after the first presentation. The revised document will be approved by the major professor. 2.2 Revision of Project Plan Revisions will be made to the project plan to update any schedule changes for the project. These revisions will be based on feedback from the committee members after the first presentation. The updated cost and effort estimate will be approved by the major professor. 2.3 Architecture Design Complete project design will be documented with the help of UML diagrams. Each component in the architecture will be documented at the interface level. The underlying data model will be Page 4 of 9
refined, updated and documented. Class diagrams, sequence diagrams and state chart diagrams will be used as needed. 2.4 Development of Prototype The second prototype should be able to demonstrate more functionality and product features. Critical requirements as identified in the vision document will be demonstrated. 2.5 Test Plan A plan will be developed for the project to address the required tests to show that the product satisfies the requirements as mentioned in the vision document. The plan will include evaluation criteria for all critical use cases and a set of test data deemed adequate for acceptance testing 2.6 Formal Technical Inspections The architecture design will be inspected by Binti Sepaha and Dominic Gelinas, two other MSE students who have agreed to participate in the inspection. A formal checklist to be used by the inspectors will be prepared by the student. 2.7 Formal Requirements Specification At least one component of the design will be formally specified using methodologies like OCL and USE. As of now it is proposed that a part of the object model will be formalized. 3. Cost Estimate (based on current progress) The project is now at the end of the Elaboration Phase. According to the time log I have spent 136 hours on the project. I have spent 75 hours coding/debugging and 25 hours on documentation. The prototype for the project has around 2000 SLOC and it implements about 40% of the required features. From this data the following metrics can be calculated. 2000 SLOC / 75 hours = 26.66 SLOC/hour (productivity) 2000 SLOC /.40 = 5000 SLOC (total SLOC) The above calculations show that my productivity was 26.6 SLOC/hour and that there is about 5000 SLOC required for the project. There will be 3000 SLOC left for development. The following calculation estimates how much time will be required for the rest of the code development. Page 5 of 9
(3000 SLOC)/ 26.6 SLOC/hour = 113 hours (total remaining development Considering work of 5 hours per day: (113 hours) / 5 hours/day = 23 days I would estimate that the testing time would be 40 hours (8 days) and the remaining documentation will take about 40 hours (8 days). This would make the total time required for the rest of the project about 39 days. Hence: Coding/Debugging 23 days Testing and test documentation 8 days Documentation 8 days The Implementation Plan will provide a detailed WBS. 3.1 Comparison of estimates The initial code size estimate was 3.5KLOC based on comparison with the previous agent tool. The expected code size is now 5KLOC due to the fact that the GEF technology of Eclipse is being used for development. GEF design calls for additional code for user command handling and viewing of diagrams. The initial time estimate was about 7-8 months. This is being maintained and the above cost estimates based on current progress show that the project is expected to complete by the end of April which is 8 months from the start date. 4. Implementation Plan 4.1. Deliverables The following are the deliverables for presentation three. User Manual The user manual will include an installation guide and a user guide. The installation guide will include detailed information about setting up the plugins into Eclipse. A user guide will give an overview and explanations of common usage and user commands. Page 6 of 9
The internal design of each component will be documented. UML diagrams will be used for design. Source Code Well-documented source code will be submitted. This code will correspond directly to the architecture and component design. Action Items Action items identified during Presentation II, along with the efforts made to satisfy them, will be documented. Assessment Evaluation Test cases as identified in the Test Plan will be executed. Defect fixing will be done for all resolvable issues. Test results will be documented. The documentation will include a document detailing the testing done on the project with descriptions of the testing and known unresolved defects. Project Evaluation The entire software process starting from the first phase will be reviewed, including the usefulness of the methodologies used, the accuracy of the estimations, and the usefulness of the reviews. The tool will be reviewed and evaluated for whether it accomplishes the goals presented in the vision document and for the quality of the product. References The annotated bibliography will include cited references for all notations used in the portfolio. Formal Technical Inspection Letters Technical inspection of the architecture design of two other MSE students will be performed. Two letters from those MSE students stating that the developer successfully participated in their MSE project as an inspector will be obtained. 4.2. Work Breakdown Structure The following table breaks down the deliverables into tasks and lists the completion criteria and cost for each task. Page 7 of 9
Deliverable Task Completion Criteria Time Cost Goal Diagram Executable code March 15 5 days refinement March 19 Source code (Coding/Debugging Goal Diagram XML generation Executable code March 20 Role Diagram model + controller Role Diagram View + misc. Executable code March 21 March 23 Executable code March 24 March 27 3 day 4 days Role Diagram XML generation Executable code March 28 Organization Diagram model + controller Executable code March 29 March 31 3 days Organization Diagram View + misc. Organization Diagram XML generation Compiling all diagrams into individual plugins Executable code April 1 April 3 4 days Executable code April 4 4 plugins April 5 Assessment Evaluation / Testing (Testing and test documentation Action Items Run test cases and fix resolvable issues Document test results Document effort completing action items All test cases complete April 6 April 9 All test case results evaluated and documented All action items from Phase 2 performed and documented April 10 April 13 April 14 4 days 4 days for Goal Diagram for Agent Diagram UML component design UML component design April 15 April 15 for Role Diagram UML component design April 16 Page 8 of 9
for Organization Diagram UML component design April 16 User Manual Installation guide Approved by Major User Guide Approved by Major Formal Inspection Send and receive Approved by Major Letters letters from formal inspectors References All references documented in the portfolio Approved by Major April 17 April 18 April 19 April 19 Project Evaluation Document usefulness of project methodologies, practices and reviews Approved by Major April 20 Compile all project resources together Approved by Major April 21 Page 9 of 9