Home Care and Monitoring System

Software Development Plan

Revision History
Date Version Description Authors
14/12/2016 1.0 This document is written for the Muhammad Badeeh
first time. It may be modified Zafar
during elaboration.

Software Development Plan 1

Home Care and Monitoring System
Software Development Plan

SOFTWARE DEVELOPMENT PLAN

1. Introduction
1.1 Purpose

This document describes the whole plan for the development of “Home Care and
Monitoring System”. This plan describes all the activities that are to be performed during the
development of HCMS. These activities are described phase by phase.

1.2 Scope

This software development plan identifies the activities to be carried out for the completion
of project. These activities are discussed later in the document.

1.3 Definitions, Acronyms and Abbreviations

There are different acronyms used in this artifact. Their detail is given one by one.
 The “Home Care and MO” is written in short as UMS.
 PCIT stands for “Punjab College of Information Technology”.

1.4 References

 HCMS SRS
 HCMS Risk Information Sheet
 HCMS Use Case Model

1.5 Project Purpose, Scope and Objectives

The Home Care and Monitoring System (HCMS) is designed for Increasing Home
Security. This project will automate the Manual Security System. The earlier project in use is not
so sufficient to fulfill all the needs of the Security and Surveillance.

1.6 Assumptions and Constraints

There are four main constraints in the system. They are given below very briefly. Their
detailed information is available in “Risk Information Sheet”.
 The database (MS Access) engine, we are using has storage capacity problem with it.
 The project may not be completed in time, i.e. at the end of semester.
 The data related to the project may be lost due to system crash. This will result in late
completion of project.
 Team members are not familiar with the working of “CGate Crystal Reports” software that
is used in the project for generating reports.

Software Development Plan 2

Home Care and Monitoring System
Software Development Plan

1.7 Project Deliverables

 Software Development Plan

 Software Requirements Specifications
 Use Case Model
 Data Model
 Design Model
 Entity Relationship Diagram
 Prototype
 Iteration Assessment Report
 Status Assessment Report
 Release Notes

1.8 Evolution of Software Development Plan

This software development plan will be updated subsequently after phase or iteration. The
target dates of each phase are given below.

Phase Target Date

Inception 28 November, 2016
Elaboration 02 January, 2017
Construction Iteration 1 20 February, 2017
Construction Iteration 2 20 March, 2017
Transition 1 June, 2017

2. Project Organization
2.1 Organizational Structure

The team will be divided into three main groups. Each group is for Inception, Elaboration
and Construction phase. These groups will work under the leadership of Project Manager. The
details of these three groups can be seen as follow.

Project Manager

Requirements Specialist, Database Designer, Programmer,

Designer Architect Tester

Figure-1: Roles of team members

Software Development Plan 3

Home Care and Monitoring System
Software Development Plan

2.2 External Interfaces

The project team will work with the administrator. Every module will be tested by the
relevant person of the client organization. Through prototype the missing requirements will be
included. Every function rejected or objected by the user will be modified or clarified by the team.

2.3 Roles and Responsibilities

The following table shows the roles of team members that are represented in the above
given diagram. The responsibilities are also given in the table of each role.

Role Responsibility
Project Manager Project Manager is the leader of the team. He will manage the
(Sir Khawaja) resources (time). He coordinates interaction of the team and
user. He assigns the task to team members and makes sure that
the team is doing the “right” things.
Requirements Requirements specialist, lists all the requirements captured from
Specialist the user in his environment or by the prototype. He identifies all
(Basit) the functional requirements described by the user. He interacts
with the user and understands what he wants to communicate.
Then he communicates the user’s desire to team members.
Designer Designer describes the requirements specified by the
(Badeeh) Requirements Specialist in technical way. He gives these
requirements the diagrammatic representation to manage
artifacts and other related documents that would be required at
elaboration phase.
Database Designer Database designer, is responsible for managing the data in
(Badeeh) database and its representation. He manages the representation
of data in tabular format inside the database, defines their
relationships and makes sure that data integrity is achieved.
Architect Architect is responsible for managing all sorts of artifacts related
(Basit) to software design. He manages the technical activities. He
establishes the overall structure for the software and maps the
real-world scenario to computer system. He identifies the classes
and interfaces that would be required to implement the business
logic, their relationship and their responsibilities in the project.
Programmer Programmer is responsible for translating the design into
(Badeeh and Basit) executable format. He gives the soul to the body of system,
created by the architect.
Tester Tester, tests the implemented modules by the programmer. He
(Basit) makes sure that the programmer has made the “things right”. He
establishes the test standards to which the system should
conform for acceptance.

Software Development Plan 4

Home Care and Monitoring System
Software Development Plan

3. Project Plan
3.1 Phase Plan

The project is planed in phases. Each phase may require iterations to complete its
allocated task. These phase and iterations are listed below with their allocated time on the basis
of estimations.

Phase No. of Iterations Start End

Inception Phase 1 Week 4 Week 10
Elaboration Phase 1 Week 10 Week 12
Construction Phase 2 Week 12 Week 16
Transition Phase 1 Week 16 Week 17

3.2 Milestones

The end of each phase will be considered as the milestone. The details of each milestone
along their goals are given below. These details include the necessary documents that would be
prepared till the end of milestone.

Milestone Milestone Description

Inception Phase The Inception phase will develop the software requirements. It will
identify all the functional and non-functional requirements. It will also
develop an initial project plan. The major risks will be identified. All the
major use cases will be identified and explored.
Elaboration Phase Elaboration phase will result in the overall architecture and design of the
system. The conceptual model of system will be mapped to the software
model. The database design will be finalized. A prototype will be
developed with no functionality available at that level. The software
development plan will be revised if needed.
Construction Phase Construction phase will include the overall implementation of business
logic of the system. All the modules will be implemented one by one and
at the end they will be integrated. All the necessary requirements will be
completed to deploy system.
Transition Phase User manuals will be prepared for the user guidance, if required.
And the system will be deployed properly in the environment of the
user after acceptance test.

3.3 Schedule Plan

The following table shows the high-level schedule plan for the milestones, set for the UMS
project. This schedule plan includes the milestone name, iteration with its starting date and
expected finishing date. The schedule plan may be reviewed after each phase or an iteration
depending upon the work finished in that iteration.

Software Development Plan 5

Home Care and Monitoring System
Software Development Plan

Task Name Start Finish

Milestones Mon, 17/10/2016 Mon, 1/06/2017
Lifestyle Objectives (end Inception Phase) Mon, 17/10/2016 Mon, 28/11/2016
Lifestyle Architecture (end Elaboration Phase) Mon, 28/11/2016 Mon, 02/01/2017
Initial Operational Capability (end Iteration 1 of Mon, 02/01/2017 Mon, 20/02/2017
Construction Phase)
Initial Operational Capability (end Iteration 2 of Mon, 28/02/2017 Mon, 20/03/2017
Construction Phase)
Product Release Milestone (end Transition Mon, 1/06/2017 Mon, 17/06/2017
Phase)

3.4 Project Resourcing

1. Staffing Plan: Particular roles have been assigned to individuals of this project. These
roles are described in Figure-1.

2. Resource Acquisition Plan: In fact, software resource is required for the completion of
this project. However, we require Hardware Resources “Camera”, would be required to
surveillance of Household and House members. And Camera is essential for the project.
And it will be not used isolated from the project.

3. Training Plan: The team is skilled with all the necessary tools and techniques required
for the project. But software training would be required. A training plan has been devised
to learn this software.

3.5 Project Monitoring and Control

1. Schedule Control Plan: “Project Status Report” will be issued through “Actual vs.
Proposed” plan giving at the end of iteration of phase. An “Iteration Assessment Report”
will be prepared at the end of iteration. These reports will help the team to be on track and
according to their schedule.

2. Budget Control Plan: Since this project is a course requirement as well. So, this project
is being developed free of cost. So, no budget control plan is required and applicable here.

3. Quality Control Plan: Informal reviews will be acquired during the development of project.
This will ensure that the system is meeting its requirements.

4. Reporting Plan: Project assessment report will be prepared after iteration. This will
ensure that the progress on project in actual is equal to the expected progress.

5. Measurement Plan: Time estimate has been completed on the basis of project domain
and available human resource.

6. Risk Management Plan: Major risks and their remedies have been discussed in “Risk
Information Sheet”.

Software Development Plan 6

Home Care and Monitoring System
Software Development Plan

4. Technical Process Plans

4.1 Methods, Tools and Techniques

 The standard guidelines of RUP are used

 Microsoft Access is used to store information
 Java is used for front-end implementation and business logic
 CGate Crystal Reports software for generating reports

4.2 Infrastructure Plan

This project will be deployed at one specific home to check the correctness of the system.
All the necessary software will be installed as they would be required.

5. Supporting Process Plans

5.1 Documentation Plan

During the development of project the following documents will be prepared.

 SRS (Software Requirements Specification)
 Risk Information Sheet
 SDP (Software Development Plan)
 Use Case Model
 Entity Relationship Diagram
 UML design diagrams (as required)
 Project Status Assessment Report
 Iteration Assessment Report

5.2 Problem Resolution Plan

Team member meetings are arranged on regular basis. In these meetings, all the
problems related to project are discussed and their remedies are suggested.

5.3 Process Improvement Plan

In all the group meetings, the problems and lessons learned from that problems will be
discussed. And careful plan will be established to improve the process pace. And try to avoid the
repetition of mistakes been done in past.

_________________________

Software Development Plan 7