CIS 454 - Software Implementation
Implementation Plan
of
Small Scientific Calculator
(SSC)
Version 2.0
February 2, 2010
TEAM MEMBERS
Rajika Tandon - TR ()
Xyz Abc ()
Table of Contents
1. Introduction 4
2. Reference Documents 5
2.1. Customer A-Specification 5
2.2. Design Document 5
3. Objectives 5
4. TASKS 17
4.1. descriptiON 5
4.2. teST PLAN 5
5. TASK allocation 17
6. time allocation 17
7. progress MONITORING 18
8. ISSUES 18
APPENDIX 19
GLOSSARY 22
refERENCES 22
List of Figures
1. Implementation & Test Chart 5
…………
…………
Note: Please label all the figures in your document and provide the names and figure numberings along with page numberings.
1. INTRODUCTION
2. REFERENCE DOCUMENTS
like your SRS, HLD, 3rd party s/w 9if relevant), platform-specific items (if relevant)
3. OBJECTIVES
Your objectives should be crystal clear and specifically spelled out, since you’ll use them as a building block for the rest of the implementation plan.
You can make references to your SRS and HLD (remember to mention the version of these documents you are referring to (normally the latest version)).
4. TASKS
4.1 DESCRIPTION
This part details what must be accomplished to achieve your objectives. As you enumerate tasks and assignments, these descriptions should be plainly and generally stated; you are not required to go into a step-by-step, micromanaged explanation of how the tasks will be carried out, however a proper organization gives a clear picture of your implementation plan. Emphasize the expected results associated with these tasks.
- You can discuss here about what has to be done in the project.
- What are the various modules in the project ?
- How you are going to organize the implementation sequence(s) ?
* What modules/parts of various modules† can be done at the same time (and integrated later) ?
* What has to be done before other modules or their parts can be started ?
You can give references to your Final Design Document (here you’ll explain the coupling, inter-dependence among various modules). You can refer to the diagrams in your HLD.
Explanation with the help of a Module/Package Diagram is a not mandatory, however they may be counted towards bonus. In case you give any such diagrams, you need to label them and explain each module/package with proper numbering.
†You may want to list your modules/classes in this section.
4.2 TEST PLAN
- You need to discuss the test plan (unit/integration).
- Also explain which other kinds of testing you are going to perform (on the entire system / on which parts of the system). Your motive should be clear as in why those tests are required.
5. TASK ALLOCATION
You can discuss here that how many people are going to work on the various modules of your project. Identification of responsible individual(s) for every module is important as it will give a clear-cut idea about who is doing what. This should be more/less decided by now.
6. TIME ALLOCATION
Each task should be paired with an appropriate time frame for completion. You need to give a chart for the implementation plan over time. A good chart will also include unit and integration test details. Proper labeling and color scheme add ease of understanding to the “implementation and test chart”.
A detailed chart is expected from you and carries a lot of weight in your implementation plan. The chart is left to the teams to decide since it is specific to the project under development. However, just to give you a rough idea about an overall chart (though you need to give a detailed chart), refer to the fig. 1.
Note that we are not expecting a highly detailed chart for the first version of implementation plan.
Background for the diagram below:
Suppose that I am developing a small scientific calculator which computes the logarithmic values, anti-logs, exponentation, hex-decimal-octal conversions and various trignometric functions like sine, cosine, tangent, secant, cosecant and cotangent. In this case I prepared a database of log, sine, cosine, tangent, hex tables etc. (This example is just to give you an idea of charting.)
Figure 1: Implementation & test chart for SSC Project
Note that explanation of the chart is also requried since your charts tend to become complicated.
7. PROGRESS MONITORING
Mention the progress of your team by preparing a list of tasks to be performed alongwith their responsible individuals and deadlines. This list is more like a checklist. You may need to update this from time to time. This will help you in framing your progress reports.
Team members should monitor each task’s progress and the completion percentage of each objective (you may have a “comments” column as well). When delays occur, try to see what is causing this problem like whether the responsible individual is not submitting assigned task on time? Did he or she have too many responsibilities to handle? You may then need to update your charts appropriately to account for the delay, and make a note of the previous deadline and the reason it was missed.
8. ISSUES
Note changes in SRS or HLD ant the reasons for those.
Note both problems and successes as you can also discuss the coupling issues in your project or the complications you may deal with the various implementation tasks.
Any other issue can be discussed here.
APPENDIX
GLOSSARY
REFERENCES
4
Small Calculator Implementation Plan (Prepared by Rajika Tandon)