Software Project Management Planning (SPMP)

1.Introduction
In Addis Ababa Science and Technology university (AASTU) there are different
management activities that are performed. Among those management activities
AASTU Students Dormitory Management is one of the major management activities
which are performed to arrange and allocate dorms for students. In this process
there is a potential problem associated with the Dormitory Management. So the
team initiated this project to identify and analyze those problems and to put
possible solutions.
This project deal with the dormitory management system in Addis Ababa Science and
Technology university. It is very helpful to both administrators and students as well as
proctors. The growing quality demand in the university makes it necessary to exploit the
whole potential of stored data efficiently, not only the student information data, but also a
resource management, in order to minimize costs and improve the care given to the
students.
The document is organized into five sections. The first section describes the overview
and deliverables of the project. The second section presents the software process model to
be used, and the organizational structure of the project and team members roles and
responsibilities. The third section describes management issues for monitoring and
controlling project status. The fourth section describes the methods and tools that are to
be used throughout the project. The fifth section discusses the resources required for the
successful completion of the project, the work break down, cost estimation and schedule
for the project.
1.1 Overview the project
Designing a user interface for the new Dormitory Management System.
To develop a database to keep the overall records associated with the
management process.
Enabling students to have all information about their dormitory information
before coming to campus, so that students may not face difficulties after coming
there.
Every students data collected when a student get into dormitory life will be
stored in a data base so that there is no loose of student record.
design a user-friendly system.
The main objective of this project is to develop a new Web Based Dormitory
Management System which solves the problem with the existing system. This is
achieved by designing a web based application program that will change the actual
manual processing to a computerized environment.
1.2 Project Deliverables
The project will a produce A Resource Management System that is easy to install because
it is a platform independent application and also easy to use. The system must pass the
acceptance test suite as described in the project agreement.

1
 Software Project Management Planning (SPMP)

The following items will be produced by the AASTU Students Dormitory Management
System:
A Software Project Management Plan (SPMP) defining the technical and managerial
processes necessary for the development and delivery of the system (This document)
Risk management plan(RMP)
Quality assurance plan(QAP)
Requirement analysis document(RAD)
Agreement between client and developers, representing a contract between the client
and the developers of what is going to be delivered.
A Requirements Analysis Document (RAD) describing the functional and global
requirements of the system as well as 4 models - the use case model, the object model,
the functional model and the dynamic model. This document is created in interaction with
the application domain experts.
A System Design Document (SDD) describing the design goals, tradeoffs made
between design goals, the high-level decomposition of the system, concurrency
identification, hardware/software platforms, data management, global resource handling,
software control implementation and boundary conditions. This document forms the basis
of the object design. This document is read by the analyst as well as the object designer.
A Object Design Document (ODD) is which is composed of two documents. The first
document is an updated RAD. The code related data will be in the form of Java Doc
output from the code from each team.
A Test Plane Design (TPD) describing the unit and system tests performed on the
system before delivery along with expected and actual results. This document is used by
the developers and maintainers.
Source code for all subsystems of the AASTU Students Dormitory Management
System.
User manual document(UMD)
2 Project Organization and Responsibilities
This section describes the organizational structure of the project and how roles and
responsibilities project team.

2.1. Organizational Structure

The project leads are as follows:

2
 Software Project Management Planning (SPMP)

Client (AASTU)

Project Manager

( Michael Wondemu )

Cross-functional team leader Development team leader

(Anley Solomon) ( Kaleabe Yohannes)

Architecture team System analyst team

System Designer team

HCI team programmer team

Maintenance team

Risk Management team leader Configuration team leader

(Misgana Gabiso) (Tadiyos Solomon)

Risk Management team Configuration team

Quality Assurance team leader

( Hashim Nuri)

Quality Assurance team

Configuration team leader

( Tadiyos Solomon)
3
 Software Project Management Planning (SPMP)

Figure 1: Organizational Structure of the Project

2.2.Roles and Responsibilities

The rule and responsibilities of the various positions are described below table:
Table 2: Members, roles and contact information
Name Roles E-mail Phone

AASTU Client
dormitory dean
and proctors
Kaleabe Development teem KaleabeYohannes@yahoo.com +251915169615
Yohannes leader

Michael Project Manager Michael_wondemu@yahoo.com +251921636677

Wondemu

Anley Solomon Cross-functional +251917008742

team leader

Hashim Nuri Quality assurance +251939763867

team leader

Tadiyos Configuration team +251913471158

Solomon leader

Misgana Gabiso Risk Management Misganagabisoo@yahoo.com +251946271124

team leader

This section describes the teams working on AASTU Students dormitory management
subsystems and their tasks:
Table 3: Roles and Responsibilities
Roles Responsibilities
Customer/Client(AASTU) o Defines the requirements
o Review design
o Resolve escalated issues
o Acceptance test planning & testing

4
 Software Project Management Planning (SPMP)

Project Manager o Drafts initial requirements.

(Michael Wondemu) o Verifies that all customers requirements are met.
o Researches existing/competing products Coordinates
and guides the team leaders.
o Forming team and assigning tasks.
o Managing the time budget.
o Do project planning, estimation and project schedule.
o Control and manage the project by coordinating activities.
o Keeps track of internal progress and exchange relevant.
information by means of team leader meetings.
o Resolve the issues on the project.
o Closing the project.
Cross-functional team leader o Integrate the system documentation (SPMP, RAD,
(Anley Solomon) SDD, ODD, Test Manual).
o Review final deliverable documentation for
completeness.

Architecture team o Maintain AASTU Students Dormitory Management

system model.
o Ensure consistency of system model with the design
model.
o Define software architecture.
o Create common class library.
o Create system integration plan.
Human Computer Interaction team o Set standards for common GUI elements.
(HCI) o Develops the style ("look & feel").
o Defines the hardware and software elements of
interface for System.
o Coordinate interfaces for overlapping subsystems
with the teams.
Development team leader o Coordinate and guides the team
(Kaleabe Yohannes) o Chairing review of the item made by his team.
o Providing feedback about team progress.
o Defined the requirements for the project
o Produce weakly plan
o Collect weakly report form his team.
o Weakly report to the project manager
Maintenance team o Authenticate the customer to the system.
o Maintain Network errors of the System.
o Maintain Database connectivity errors of the system.

System Analyst Team
System Designer team
o Analyze and defines system and/or project specific
requirements
o Maintains requirements control
o Produce RAD.
o Monitors design issues throughout the project

5
 Software Project Management Planning (SPMP)

o Maintains design control

o Produce system design document(SDD)
o Produce Object design document(ODD)
Programmer Teem o Following procedures and plans
o Develops and maintains the implementation standards
o Reviews designs for completeness prior to
implementation
o Establishes and maintains control over the implemented
Product
Risk Management o planned to reduce the probability/impact of the risk.
o planned to resolve the issue.
o Prioritizes the risks as they are identified and make the
project member aware of this.
Configuration team o Coordinate change requests .
o Provide version control for group's working directory
o Coordinates configuration management issues with
other groups .
o Installation of group specific software and hardware .
Quality Assurance teem o Systems Testing.
o Checking that all project document are consistent.

3.Managerial Process

3.1. Meetings

Team leadership will maintain the responsibility of maintaining and containing the project
schedule and ensuring that all work items are completed and on schedule. Leadership is
also responsible for the creation of all deliverables and scheduling/running meetings.
3.1.2 Team members meeting Time

There is a weekly project meeting for each group. The initial project meeting times are:
Cross-function Monday 8:00 p.m.
System Development Wednesday 4:30 p.m
Configuration and Configuration Thursday 4:30 p.m.
Risk Management and Quality assurance Tuesday 6:00 p.m.
3.2. Monitoring and Controlling

The project is managed by means of an established Work Breakdown Structure (WBS)

and different reports. This WBS shall be the basis for establishing project schedule and
for definition of project tasks and deliverables. The project manager collects actual
completion and resource utilization data from the team members in order to calculate
actual performance against predicted cost and schedule.

6
 Software Project Management Planning (SPMP)

4. Technical Process
4.1 Process Model
We in our project, we used Waterfall Process Model. Because we have a well-defined
requirement, and it is:
simple and easy to understand and use.
easy to manage due to the rigidity of the model each phase has specific deliverables
and a review process.
In this model phases are processed and completed one at a time. Phases do not
overlap.
4.2 Methods
Object Oriented Software Development method will be used in developing the Stand
Alone but connected in to pear to peer Computers for AASTU Students Dormitory
Management System. The implementation will be also using an object-oriented
programming language which supports a GUI application development.
4.3 Tools
Table 4: Tools used during software development
Software/Language Purpose
MS Office Word 2016, Foxit To produce RAD, SDD, TPD,
pdf and UMD
MS Visio 2016 To draw diagrams
NetBeans 7.4 For scripting
MySQL 5.0 Database
Helps to connect computers to
Network Driver
network

Hardware Requirements:
Computer
Hard -disk /CD
printer and Paper
Unshielded twisted pair cable
5. Work Breakdown Structure (WBS), Estimation and Scheduling
5.1. WBS
A Work Breakdown Structure (WBS) identifies tasks and deliverables associated with a
project. Resources are identified for each item within the WBS that facilitates budgeting
as well as assignment of responsibilities. Its purpose is to divide the entire project into
manageable pieces of activities in order to facilitate planning and control of cost,
schedule and
technical content.

7
 Software Project Management Planning (SPMP)

Table 5: Cost Breakdown Structure

5.2. Project Estimation
No Talks
1 Initiation
1.1 Start project
1.2 Develop project charter
1.3 Project charter approved
2 Planning
2.1 Prepare Software Project Management Plan(SPMP)
2.2 Prepare software Configuration Management Plan (SCMP)
2.3 Prepare Cross-functional Plan (CFP)
2.4 Prepare Risk Management Plan(RMP)
2.5 Prepare Quality Assurance Plan(QAP)
3 Software requirements Definition
3.1 Feasibility Study
3.1.1 Technical Feasibility
3.1.2 Schedule Feasibility
3.1.3 Economic Feasibility
3.1.5 Operational Feasibility
3.2 Define project scope
3.2.1 Specify functional requirements
3.2.2 Specify non-functional requirement
3.3 Analyze existing system
3.3.1 Assemble documentation on existing system
3.3.2 Identify data flows
3.3.3 Identify external interfaces
3.3.4 Identify problem domain
3.4 Produce System models
3.4.1 Produce use case diagram
3.4.2 Produce class diagram
3.4.3 Produce sequence diagram
3.5 Produce Draft RAD
3.5.1 Get feedback on RAD
3.5.2 Produce final RAD
4 Logical Design
4.1 Design Interfaces
4.1.1 Design external data interfaces
4.1.2 Design human interfaces
4.1.3 Design intersystem interfaces
4.2 Detail Design
4.3 Produce Object Design
4.3.1 Specify Attributes and Operations
4.3.2 Define Contracts
4.4 Produce draft SDD and ODD
4.5 Get feedback on SDD and ODD
4.6 Produce final SDD and ODD

8
 Software Project Management Planning (SPMP)

5 Physical Design
5.1 Design or specify physical database
5.1.1 Review logical database design
5.1.2 Determine access methods to be used
5.1.3 Normalize database
5.1.4 Design database architecture
5.2 Validate physical design
5.2.1 Validate data relations
5.2.2 Validate process relations
5.2.3 Validate teleprocessing network specifications
5.3 Validate physical design
6 Implementation
7 System Testing
7.1 Identify features to be tested and not to be tested
7.2 Specify testing materials required (HW/SW)
7.3 Specify Test cases
7.4 Produce draft TPD
7.5 Get feedback on TPD
7.6 Produce Final TPD
8 Final Implementation
9 Installation
9.1 Finalize conversion plan
9.2 Install software
9.3 Convert files/database
10 Close Project

5.2. Project Estimation

For estimating the project resources we have used the ad-hoc approach due to many
reasons. Firstly, it is simple. Compared to the other approaches the ad-hoc approach is
easier to follow. Secondly, we dont have a previous project to use the analogy approach.
Lastly, and we have found the expert judgment approach infeasible to this project.
5.2.1 Size Estimation
Project size estimation is an activity in software engineering that is used to estimate the
size of software application or component in order to implement other software project
management activities (such as estimating or tracking). Size is an inherent characteristic
of software just like weight is an inherent characteristic of a tangible material. it describes
how many thousands lines of codes the programmer must develop. Since estimation of
project size is base for others estimation we agreed up on the type of the project is
organic, small and simple and its size will approximately be 8KLOC.
5.2.2 Effort Estimation
The project is simple or organic and size of the project is 8 KLOC as per agreement of
the team members and also since COCOMO has been selected initial effort will be
calculated as follows.

9
 Software Project Management Planning (SPMP)

Step 1: The initial estimation (Ei) can be calculated as:-

Given
a=3.2, b=1.05, Size=8KLOC
Required: Ei=?
Solution
Ei= a*(KLOC)
Ei=3.2*(8)1.05= 28.40 man month
Step 2: The multiplying factors are determined for each attributes which are significant
role on
the project development.
Given rates on nine attributes according to the effort multiplier table, effort adjustment
factor
(EAF) is calculated according to intermediate COCOMO formula.
Table 6: Effort Attribute multiplier
Attribute Rating
1 Product
Required Reliability High (1.15)
Database Size Nominal (1.00)
Complexity of the
Low (0.85)
product
2 Computer
Execution time
High(1.11)
constraints
3 Personal
Analyst capacity High(0.86)
Programmer capability High(0.86)
4 Technology
Use of software tools High(0.91)
Development schedule High(1.04)

Step 3: Adjusting the initial estimate Ei using Effort Adjustment Factor (EAF) to E
(Effort)

EAF = 1.15*1*0.85*1.11*0.86*0.86*0.91*0.91*1.04
EAF=0.69
E=Ei*EAF
E =28.40*0.69
E=19.59Man Month
Step 4: Estimating the duration of the project D and Staff S required

10
 Software Project Management Planning (SPMP)

Given: c=2.5, d=0.38 for an simple project then

D=c*Ed
D =2.5*19.59pow 0.38
D =6.10 month
S=E/D
S =19.59/6.10
S =3.21 people
Though the project to be developed requires 2 people depending on the above calculation.
5.3. Schedule
The duration estimated for WAAMCS is approximately 6 months. Therefore, the
schedule for the complete realization of the WASAMCS is outlined as follows on table
given below.

Table 7: Schedule of the project

Dependency Dura Start End Date
from task no. tion Date
No Talks (days
)
1 Initiation 4/27/2017 5/4/2017
1.1 Start project 4/27/2017 4/29/2017
1.2 Develop project charter 4/28/2017 5/1/2017
1.3 Project charter approved 5/2/2017 5/4/2017
2 Planning 5/4/2017 7/6/2017
Prepare Software Project Management 5/4/2017 5/16/2017
2.1
Plan(SPMP)
Prepare software Configuration 2.1 5/17/2017 5/29/2017
2.2
Management Plan (SCMP)
2.3 Prepare Cross-functional Plan (CFP) 2.1 5/30/2017 6/12/2017
2.4 Prepare Risk Management Plan(RMP) 2.1 6/12/2017 6/24/2017
2.5 Prepare Quality Assurance Plan(QAP) 2.1 , 2.2 6/26/2017 7/6/2017
3 Software requirements Definition 7/7/2017 8/21/2017
3.1 Feasibility Study 7/7/2017 7/18/2017
3.1.1 Technical Feasibility 7/7/2017 7/10/2017
3.1.2 Schedule Feasibility 7/10/2017 7/12/2017
3.1.3 Economic Feasibility 7/13/2017 7/16/2017
3.1.5 Operational Feasibility 7/15/2017 7/18/2017
3.2 Define project scope 7/18/2017 7/25/2017
3.2.1 Specify functional requirements 2.1 , 3.1.1 7/18/2017 7/22/2017
3.2.2 Specify non-functional requirement 3.1.1 7/21/2017 7/25/2017
3.3 Analyze existing system 7/26/2017 8/7/2017
Assemble documentation on existing 7/26/2017 7/28/2017
3.3.1
system
3.3.2 Identify data flows 7/29/2017 8/2/2017

11
 Software Project Management Planning (SPMP)

3.3.3 Identify external interfaces 8/2/2017 8/5/2017

3.3.4 Identify problem domain 8/5/2017 8/7/2017
3.4 Produce System models 8/7/2017 8/15/2017
3.4.1 Produce use case diagram 3.2.1 8/7/2017 8/10/2017
3.4.2 Produce class diagram 3.4.1 8/8/2017 8/11/2017
3.4.3 Produce sequence diagram 3.4.1 8/11/2017 8/14/2017
3.4.4 Activity Diagram 3.4.1 8/14/2017 8/15/2017
3.5 Produce Draft RAD 3.4.1,3.4.2,3.4.3 8/16/2017 8/17/2017
3.6 Get feedback on RAD 3.5 8/16/2017 8/18/2017
3.7 Produce final RAD 3.6 8/19/2017 8/21/2017
4 Logical Design 8/21/2017 9/10/2017
4.1 Design Interfaces 8/21/2017 8/25/2017
4.1.1 Design external data interfaces 8/21/2017 8/23/2017
4.1.2 Design human interfaces 8/23/2017 8/24/2017
4.1.3 Design intersystem interfaces 8/25/2017 8/25/2017
4.2 Detail Design 8/28/2017 8/30/2017
4.3 Produce Object Design 9/1/2017 9/4/2017
4.3.1 Specify Attributes and Operations 9/2/2017 9/3/2017
4.3.2 Define Contracts 9/4/2017 9/4/2017
4.4 Produce draft SDD and ODD 4.1 9/5/2017 9/5/2017
4.5 Get feedback on SDD and ODD 4.1, 4.2, 4.3 9/6/2017 9/6/2017
4.6 Produce final SDD and ODD 4.5 9/7/2017 9/10/2017
5 Physical Design 4.1 9/11/2017 9/22/2017
5.1 Design or specify physical database 9/11/2017 9/15/2017
5.1.1 Review logical database design 9/11/2017 9/12/2017
5.1.2 Determine access methods to be used 5.1.1 9/13/2017 9/13/2017
5.1.3 Normalize database 5.1.1 9/14/2017 9/14/2017
5.1.4 Design database architecture 9/15/2017 9/15/2017
5.2 Validate physical design 9/17/2017 9/20/2017
5.2.1 Validate data relations 5.1.3 9/18/2017 9/18/2017
5.2.2 Validate process relations 5.2.1 9/19/2017 9/19/2017
Validate teleprocessing network 5.2.2 9/20/2017 9/20/2017
5.2.3
specifications
5.3 Validate physical design 5.2 9/21/2017 9/22/2017
6 Implementation 5.3 9/25/2017 9/29/2017
7 System Testing 9/29/2017 10/6/2017
Identify features to be tested and not to 6 9/29/2017 9/29/2017
7.1
be tested
Specify testing materials required 7.1 9/30/2017 10/2/2017
7.2
(HW/SW)
7.3 Specify Test cases 7.1 10/2/2017 10/2/2017
7.4 Produce draft TPD 7.3 10/3/2017 10/3/2017
7.5 Get feedback on TPD 7.4 10/4/2017 10/4/2017
7.6 Produce Final TPD 7.5 10/6/2017 10/6/2017
8 Final Implementation 7.6 10/8/2017 10/12/2017
9 Installation 10/12/2017 10/30/2017
9.1 Finalize conversion plan 8 10/12/2017 10/12/2017
9.2 Install software 7.6 ,8 10/13/2017 10/20/2017

12
 Software Project Management Planning (SPMP)

9.3 Convert files/database 9.2 10/22/2017 10/30/2017

10 Close Project 9.3 11/1/2017 11/5/2017

5.3.1 Gantt Chart

For the simplicity we sketch Gantt chart for major activities, Gantt chart for initiation,
Planning, Requirement Elicitation, Logical Design , Physical design and
Implementation.
Figure 2: Gantt chart for Initiation

Apr 2017 May 2017

ID Task ID Task Name Duration Start Finish
27 28 29 30 1 2 3 4

1 1 Initiation 6d 4/27/2017 5/4/2017

2 1.1 Start project 2d 4/27/2017 4/28/2017

3 1.2 Develop project charter 2d 4/28/2017 5/1/2017

4 1.3 Project charter approved 3d 5/2/2017 5/4/2017

Figure 3: Gantt chart for Planning

13
 Software Project Management Planning (SPMP)

Figure 3: Gantt chart for requirement

Jul 2017 Aug 2017
ID Task Id Task Name Duration Start Finish
7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21

1 3 Software requirements Definition 32d 7/7/2017 8/21/2017

2 3.1 Feasibility Study 8d 7/7/2017 7/18/2017

3 3.1.1 Technical Feasibility 2d 7/7/2017 7/10/2017

4 3.1.2 Schedule Feasibility 2d 7/10/2017 7/11/2017

5 3.1.3 Economic Feasibility 2d 7/13/2017 7/14/2017

6 3.1.4 Operational Feasibility 2d 7/17/2017 7/18/2017

7 3.2 Define project scope 6d 7/18/2017 7/25/2017

8 3.2.1 Specify functional requirements 1d 7/19/20177 7/19/2017

9 3.2.2 Specify non-functional requirement 3d 7/21/2017 7/25/2017

10 3.3 Analyze existing system 9d 7/26/2017 8/7/2017

Assemble documentation on existing
11 3.3.1 3d 7/26/2017 7/28/2017
system
12 .3.3.2 Identify data flows 3d 7/31/2017 8/2/2017

13 3.3.3 Identify external interfaces 3d 8/2/2017 8/4/2017

14 3.3.4 Identify problem domain 1d 8/7/2017 8/7/2017

15 3.4 Produce System models 6d 8/7/2017 8/14/2017

16 3.4.1 Produce use case diagram 4d 8/7/2017 8/10/2017

17 3.4.2 Produce class diagram 2d 8/10/2017 8/11/2017

18 3.4.3 Produce sequence diagram 1d 8/14/2017 8/14/2017

19 3.4.4 Activity Diagram 2d 8/14/2017 8/15/2017

20 3.5 Produce Draft RAD 2d 8/16/2017 8/17/2017

21 3.6 Get feedback on RAD 3d 8/16/2017 8/18/2017

22 3.7 Produce final RAD 1d 8/21/2017 8/21/2017

Figure 4: Gantt chart for logical Design

Aug 2017 Sep 2017

ID Task ID Task Name Duration Start Finish
21 22 23 24 25 26 27 28 29 30 31 1 2 3 4 5 6 7 8 9 10

1 4 Logical Design 15d 8/21/2017 9/8/2017

2 4.1 Design Interfaces 5d 8/21/2017 8/25/2017

3 4.1.1 Design external data interfaces 3d 8/21/2017 8/23/2017

4 4.1.2 Design human interfaces 2d 8/23/2017 8/24/2017

5 4.1.3 Design intersystem interfaces 1d 8/25/2017 8/25/2017

6 4.2 Detail Design 3d 8/28/2017 8/30/2017

7 4.3 Produce Object Design 2d 9/1/2017 9/4/2017

8 4.3.1 Specify Attributes and Operations 2d 9/1/2017 9/4/2017

9 4.3.2 Define Contracts 1d 9/4/2017 9/4/2017

10 4.4 Produce draft SDD and ODD 1d 9/6/2017 9/6/2017

11 4.5 Get feedback on SDD and ODD 1d 9/7/2017 9/7/2017

12 4.6 Produce final SDD and ODD 1d 9/8/2017 9/8/2017

14
 Software Project Management Planning (SPMP)

Figure 5: Gantt chart for Physical design

Sep 2017
ID Task ID Task Name Duration Start Finish
11 12 13 14 15 16 17 18 19 20 21 22

1 5 Physical Design 10d 9/11/2017 9/22/2017

Design or specify physical
2 5.1 5d 9/11/2017 9/15/2017
database
3 5.1.1 Review logical database design 1d 9/12/2017 9/12/2017
Determine access methods to be
4 5.1.2 1d 9/13/2017 9/13/2017
used
5 5.1.3 Normalize database 1d 9/14/2017 9/14/2017

6 5.1.4 Design database architecture 1d 9/15/2017 9/15/2017

7 5.2 Validate physical design 3d 9/18/2017 9/20/2017

8 5.2.1 Validate data relations 1d 9/18/2017 9/18/2017

9 5.2.2 Validate process relations 1d 9/19/2017 9/19/2017

Validate teleprocessing network
10 5.2.3 1d 9/20/2017 9/20/2017
specifications
11 5.3 Validate physical design 2d 9/21/2017 9/22/2017

Figure 6: Gantt chart for implementation

Sep 2017 Oct 2017

ID Task ID Task Name Start Finish Duration
25 26 27 28 29 30 1 2 3 4 5 6

1 6 Implementation 9/25/2017 9/29/2017 5d

2 7 System Testing 9/29/2017 10/6/2017 6d

Identify features to be tested
3 7.1 9/29/2017 9/29/2017 1d
and not to
Specify be tested
testing materials
4 7.2 9/29/2017 9/29/2017 1d
required (HW/SW)
5 7.3 Specify Test cases 10/2/2017 10/2/2017 1d

6 7.4 Produce draft TPD 10/3/2017 10/3/2017 1d

7 7.5 Get feedback on TPD 10/4/2017 10/4/2017 1d

8 7.6 Produce Final TPD 10/5/2017 10/6/2017 2d

Figure 7: Gantt chart for installation

Oct 2017
ID Task ID Task Name Start Finish Duration
8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 1

1 8 Final Implementation 10/9/2017 10/12/2017 4d

2 9 Installation 10/12/2017 10/30/2017 13d

3 9.1 Finalize conversion plan 10/12/2017 10/12/2017 1d

4 9.2 Install software 10/13/2017 10/20/2017 6d

5 9.3 Convert files/database 10/23/2017 10/30/2017 6d

6 10 Close Project 11/1/2017 11/3/2017 3d

15
 Software Project Management Planning (SPMP)

6. References
1. befekadu belete ,sample SWPMP
2. Chris F. Kemerer Software Project Management Readings and Cases, Irwin, 1997
3.William Milam, Alongkrit Chuitinan SmartVehicle Challenge Problems Model Composition
and Analysis
4.Challenge Problems, Ford Motor Company, 2001
5.Ken Butts, Dave Bostic, et al. Usage Scenarios for an Automated Model Compiler, Ford
Research Laboratory, 2000
6.Watts S. Humphrey, Introduction to the Team Software Process, Addison-Wesley
7. www.wikipidia.com
8. JAMES Project, 15-413 Software Engineering Fall 1997, Carnegie Mellon University
Pittsburgh, PA 15213
9. R. Pressman, Software Engineering: a Practioner's Approach. Boston McGraw-Hill 2005.

16
 Software Project Management Planning (SPMP)

Group One (1) members and ID

No Name ID
1 Anley Solomon TEST 093/07
2 Hashim Nuri TEST 184/07
3 KaleabeYohannes ETS 0644/07
4 Michael Wondemu ETS 0777/07
5 Misgana Gabiso ETS 0800/07
6 Tadiyos Solomon ETS 0969/07

17