1.

Overview

The Defend-First Corporation has been designated to design the software for the US

government to track the network for the ground based stations. The software designed will

consists of Satellite data and ground based station data. It will be able to track satellite

information from its status to location and also it will able track ground based station

networking system which will user all the information about the ground based station. This

software shall help the government in monitoring the health condition of the satellite and

ground based station.

1.1 Project Summary

1.1.1 Purpose, Scope and Objectives

The purpose of this document is to describe the software development plan for software to

operate the network of Ground based tracking stations.

The SDP document consists of the project organization and detailed information on how the

Software for ground based tracking System will work. The document details the Work plan

and a risk management plan to formulate a system, which will be used to automate the

process.

The Objectives of this Document are:

 To identify the project deliverables.

 To identify roles and responsibilities.

 To provide details of Software Work Plan and Risk Management Plan.

 To describe process model.

  To identify tools and techniques used for the development plan.

Scope

This Project by Defense-First Cooperation for the US Government to operate the network of

Ground based station aims at providing a web enabled interface at the Centre Level for

monitoring the network at ground Level, which would be the source of relevant information and

an interface for providing information on satellite status and ground based stations services.

1.1.2 Assumptions and Constraints

This document will be developed in accordance with SDD and STS designed for the software to

operate the network of Ground based stations

1.1.3 Project Deliverables

Sr. No. Task Start Date End Date

Phase I – Conceptualization and Design 11-May-14 08-December-14

including Solution Recommendation

1. Project Inception 11-May-14 31-May-14
2. As-IS Process Study 1-June-14 12-July-14
3. To-Be Process 12-July-14 06-September-14
4. Preparation of DPR, 6-September-14 09-November-14

Change Management
5. Preparation of 9-November-14 08-December-14

Capacity building

management
Phase II – Program Management 8-December-14 10-April-15

including Development and Integration

and Implementation
6. Finalization of 8-December-14 15-December-14
 Project Plan by SI
7. Finalization of 15-December-14 3-January-15

Project Management

Tool in discussion

US government
8. Requirement 3-January-15 21-January-15

Gathering &

Validation
9. Development and 21-January-15 22-March-15

Implementation of

Software Application
10. Deployment of H/w 22-March-15 29-March-15

and N/w

components
11. Conducting User 29-March-15 6-April-15

Acceptance Testing

of the applications
12. Fine tuning of 6-April-15 15-April-15

Applications and IT

infrastructure
Go-Live of Application and Sign-off 15-April-15 11-May-15
13. Change Management 15-April-15 22-April-15

and Capacity

Building
14 System and Security 22-April-15 29-April-15

Audit
15 Project Appraisal 29-April-15 4-May-15

Report
16. Preparing Roadmap 4-May-15 11-May-15
 for future project

2. References
 Software Design Document to operate the ground based Station

 Software Testing Specification to operate the ground based Station

 IEEE-1058 Software Development Plan Standard

3. Definitions

Term or Acronyms Definitions

SI System Integrator
H/W Hardware
N/w Network
US United States
Ground Based Tracking Stations Devices used to communicate to orbital

satellite systems and ground based network

terminals. They provide a gateway to

capturing imaging data.

SDD Software Design Document
STS Software Testing Specification
SDP Software Development Plan
4. Project Organization
4.1 External Interfaces
The Organization Structure for this project is shown below:

N
t
e
w
m
o
C
g
n
r
e
t
i
l
a
S
P
r
G
S
U
(
b
t
D
s
o
o
r
ft
j
c
w
ti
i
v
N
n
a
M
e
g
m
m
e
tt
i
u
C
S
U
-
l
a
n
&
t
e
s
r
i
F
d
n
e
f
D
t

p
x
E
k
C
p
x
E
o
G
a
)
n
t
r
e
v
m
t
r
e
ti t
n
e

4.2 Roles and Responsibilities

1. Sponsor (US Government)

  Manage project implementation

 Provide approved SDD, STS and SDP

2. User (Ground Based Station and Satellite office of US Government)

 Review SDD, STS and SDP

 Conduct Testing

3. Project Manager (US Government)

 Manage Project development

 Manage project reviews

4. Hardware Engineer

 Supervise system hardware requirement

5. Software Project Manager (Defend-First Corporation)

 Manage software development activities

 Develop and maintain SDP

6. Software Development team

 Prepare SDD, STS, SDP

 Code, integrate, and unit test the software to operate the network of Ground Based

Station

 Support testing and delivery of software to US Government

7. Testing team

 Prepare Test Plans/Procedures and Test Reports for the project

 Conduct Integration testing for the project

 Support Installation and Requirement testing

5. Managerial Process Plans

5.1 Work Plan

5.1.1 Work Activities
Work Activities for this project for US Government by Defense-First Cooperation is as follow:

1. Integration of the software with respective satellite

2. Tracking down the ground based station .

3. Checking and monitoring the Satellite and Ground based Station network health.

5.1.2 Schedule Allocation

The project wiil be implemented within time of 52 weeks. Therefore, there is a need to hold on

to a well-defined scope and close monitoring of project that will be accomplished. For less work

considerable segment of the project (6 weeks) were spent in requirements gathering and

development. Delivery of a project in a defined scope is ensured through by offering a third of

the project time to implementation (8 weeks).

5.1.3 Resource Allocation

 Human Resources - Allocate the human resources by skill set (Project and Program

management, software engineering, testing, , quality assurance and testing) assigned to

each task in the project's schedule.

 Software Resources - Allocate the software resources that are essential for the project, the

provider of the software.

  Hardware Resources - Identify the equipment that is essential for the project, the provider

of the equipment and the need dates.

5.2 Risk Management Plan

Risk management Plan will pact with the risks involved in the project during the

implementation stage.

Key risks involved during the Change Management stage are:

 Capacity Building plan failure

 Communication plan failure

Reasons due to which the Capacity Building Plan can be failed are listed below:

 Proper training is not provided to the employees

 Adequate infrastructure is not available

 Trainers are poorly trained

 Trained personnel are not available because of inside movement/ rotation

Reasons due to which Communication plan can be failed are listed below:

 Poor motivation levels of the employees

 Lack of adherence to the re-designed processes and service levels

 Lack of conviction about the new system among the employees

 Poor implementation of modes of communication strategy

System Integrator will identify the Risks management plan. The Risk management plan

would be submitted by SI and the same shall be validated and approved by the US
government or its representatives. The following table lists the indicative contingency

plans to manage the risks involved with the failure of the Capacity Building Plan and

Communication plan, to be approved by System Integrator in discussion with Government.

Contingency Plan

Capacity Building Plan failure (In favor) Communication Plan (In Favor)

Formation of a hub of employees skillful in Targeted group meetings with the Change

both the process and the technology Management teams at top management level

Ensuring availability of Train the Trainers For User communication use peer groups

Program at all times for proper training

Certify the successful training and capacity Constant Feedback sessions from Users

building execution

Make sure the instant support for training so Support of US Government orders through

that it meet any need in skill sets departmental orders and communications

6. Technical Process Plans

6.1 Process Model
The project team will use the evolutionary method designing of the software to operate the

network of Ground based stations via satellite. The method adopted for designing this project has

a aim to build a prototype that can be modified by user at anytime from anywhere. The will solve

a smaller problem, but, on the other hand, the implementation will be more primarily tested and

documented.

Factors that will make contribution to this project

• A main objective of this project was to design its graphical user interface for monitoring

the ground based station network status and its capabilities. The design and testing methods are

the major consideration in the Software Development and which will needed to be reused.

• It is also based on the consideration of external factors which includes tools, time, and

personnel. Reuse of the coding methods, system testing are highly recommended for this project

6.2 Methods, tools and techniques

Methods , tools and techniques used for this project are:

Project management Methodology:

 It will help in proper planning

- Project schedule and costing

- Responsibility factors

- Schedules for high level design and practices

- Establish task plan individually

- Milestones will be achieved easily

- Proper resources will be utilized

 - Budget will calculated on milestone basis

 Techniques used

- Gantt charts

- Pert Chart

- Work hours Sheet

- Weekly, Monthly Status report

 Tools Used

- MS Project, Azure for wireframe, MS Visio