Coventry University Track Locate and Assemble Software Development Plan Nagarjuna Murthy

Version: 1.0 Date: 22/11/2011

TEAM-3

COVENTRY UNIVERSITY TRACK LOCATE AND ASSEMBLE (CUTLASS) Software Development Plan

Version 1.0

CONFIDENTIAL

(C) TEAM 3 2011

Page 1 of 14

Coventry University Track Locate and Assemble Software Development Plan Nagarjuna Murthy

Version: 1.0 Date: 22/11/2011

Revision History
Date 22/Nov/2011 Version 1.0 Description Software development plan Author Nagarjuna Murthy

CONFIDENTIAL

(C) TEAM 3 2011

Page 2 of 14

Coventry University Track Locate and Assemble Software Development Plan Nagarjuna Murthy

Version: 1.0 Date: 22/11/2011

Table of Contents 1. Introduction......................................................................................................5 1.1 1.2 1.3 1.4 1.5 2. Purpose................................................................................................5 Scope...................................................................................................5 Definitions, Acronyms and Abbreviations.............................................5 References...........................................................................................5 Overview..............................................................................................6

Project Overview..............................................................................................6 2.1 2.2 2.3 2.4 Project Purpose, Scope and Objectives...............................................6 Assumptions and Constraints...............................................................6 Project Deliverables...............................................................................7 Evolution of the Software Development Plan........................................8

3.

Project Organization.........................................................................................8 3.1 3.2 3.3 Organization Structure..........................................................................8 External Interfaces................................................................................9 Roles and Responsibilities....................................................................9

4.

Management Process....................................................................................10 4.1 4.2 Project Estimation...............................................................................10 Project Plan.........................................................................................12 4.2.1 4.2.2 4.2.3 4.2.4 4.3 Phase Plan...............................................................................12 Releases..................................................................................13 Project Schedule......................................................................13 Project Resourcing...................................................................13

Project Monitoring and Control............................................................13 4.3.1 Requirement Management........................................................13 4.3.2 Budget Control..........................................................................14 4.3.3 Quality Control...........................................................................14 4.3.4 Reporting and Management......................................................14 4.3.5 Risk Management.....................................................................14 4.3.6 Configuration management.......................................................14

CONFIDENTIAL

(C) TEAM 3 2011

Page 3 of 14

Coventry University Track Locate and Assemble Software Development Plan Nagarjuna Murthy

Version: 1.0 Date: 22/11/2011

List of Tables Table 1: Evolution of Software Development Plan......................................................8 Table 2: Roles and Responsibilities...........................................................................10 Table 3: CUTLASS Budget........................................................................................11 Table 4: Project Plan Schedule.................................................................................12 Table 5: Phase Plan Schedule..................................................................................14

List of Figures Fig 1: Organization Structure.......................................................................................8

CONFIDENTIAL

(C) TEAM 3 2011

Page 4 of 14

Coventry University Track Locate and Assemble Software Development Plan Nagarjuna Murthy

Version: 1.0 Date: 22/11/2011

Software Development Plan

1. Introduction 1.1 Purpose The objective of the software development plan is to collect the necessary information required to control and develop the project in different development stages. This software development plan is used by the following people: The project manager uses it to schedule and estimate the project in all the development stages, and to track the project through scheduled time, cost and quality with efficiency. The team members uses it to develop the project at different phases depending upon the requirements and the final outcome.

1.2

Scope

The software development plan describes the complete plan to be implemented by Coventry University to track and locate the lost or stolen electronic devices. The plan contains the information about each iteration plan. The project is planned and documented based on the project requirements as defined in the vision document.

1.3

Definitions, Acronyms and Abbreviations

CUTLASS Coventry University Track Locate and Assemble. TBD To Be Decided.

1.4

References Next Iteration Plan Hanan Al shanbri 2011

CONFIDENTIAL

(C) TEAM 3 2011

Page 5 of 14

Coventry University Track Locate and Assemble Software Development Plan Nagarjuna Murthy

Version: 1.0 Date: 22/11/2011

1.5

Overview

The software development plan contains the following information Project Outline defines the projects purpose, scope and objectives also describes the final results as to how the project has to be delivered. Project Organization provides the explanation of the organizational building of the project crew. Management Process describes the targets and principal phases of the project, provides the price and estimated time schedule, and explains in what way the project will be examined. Technical Process Plan provides information about methods, tools and techniques used, an overview of software development plan. Support Process Plan defines the configuration management plan

2.

Project Overview 2.1 Project Purpose, Scope and Objective

This project will describe the overall plan to be used by CUTLASS to track the lost or stolen electric devices. This will implement customised online tracking software in the registered devices. This software will give notification of updates on status report through any nominated electronic medium identifier. The subscriber will then be able to view the activity level of the device like timeouts, by tracking logs, unusual user behaviour and unauthorised user websites via cutlass website. The software is then automated to shutdown the device or to activate a sounding alarms or an onboard camera to identify the perpetrator(s). Mapping software, keystrokes or GPS used to find out the current location of the device. 2.2 Assumptions and Constraints

Project Assumption: This device called CUTLASS is mainly designed to protect resources of students. The device tracks, locates and assembles any electronic devices of the student, which is lost or stolen.

CONFIDENTIAL

(C) TEAM 3 2011

Page 6 of 14

Coventry University Track Locate and Assemble Software Development Plan Nagarjuna Murthy

Version: 1.0 Date: 22/11/2011

Students are required to register themselves along with their devices to the CUTLASS and should download the software from that particular website where the devices of students will be monitored. When there is any suspicious activity, the students are required to log into the CUTLASS website and should report about the activity. Whenever the device goes online, the software delivers status reports to the students in the website. The report contains collection of activities from the missing date. Student can change the configuration settings to describe the doubtful activities and they need to set the device in such a way that actions like alarming or activating the webcam on the device to identify the criminals should take place after the closing down of the device. GPS can be used to trace the whereabouts of the device. Constraints If the devices are used outside the university network, itll be difficult for the system to track the electronic device. If the system does not meet the specifications specified for the software it makes it difficult for the system to recognise the particular device. 2.3 Project Deliverables The following deliverables will be developed during the project Software development plan Iteration assessment and plans Vision document Use case models + Survey Glossary Supplementary specification Test plans Change request Design model Review records Release points

CONFIDENTIAL

(C) TEAM 3 2011

Page 7 of 14

Coventry University Track Locate and Assemble Software Development Plan Nagarjuna Murthy

Version: 1.0 Date: 22/11/2011

2.4

Evolution of Software Development Plan This software development plan will be restructured prior to start of each iteration and subsequent phase. The target period for the termination of each phase are listed below: Version 1.0 2.0 3.1 3.2 3.3 4.0 5.0 Inception Elaboration Construction Iteration 1 Construction Iteration 2 Construction Iteration 3 Transition Iteration 1 Transition Iteration 2 Phase Target Date 22 Nov 2011 10 Jan 2012 -TBD-TBD-TBD-TBD-TBD-

Table 1: Evolution of Software Development Plan 3. 3.1 Project Organization Organization Structure
Project Manager

Process Engineer

Development Manager Design Analyst

Test Manager

Software Engineer Implementer

Requirement Analyst Project Reviewer

Test Analyst

User Interface Designer Software Architect

Test Designer

Code Reviewer

Architect Reviewer Requirement Reviewer

Test Reviewer

Integrator

Tester

Technical Writer

Fig 1: Organization Structure

CONFIDENTIAL (C) TEAM 3 2011 Page 8 of 14

Coventry University Track Locate and Assemble Software Development Plan Nagarjuna Murthy

Version: 1.0 Date: 22/11/2011

3.2

External Interface The project team will interact with stockholder to record review reports, test reports and further requirements. The main contact foe CUTLASS will be Coventry University.

3.3

Roles and Responsibilities Roles Responsibilities

Project Manager

Project manager has the overall charge for the fruitful commencement, implementation, planning, monitoring and governing of the project. The project manager provides resources, sets priorities and interacts with users and the customers in order to maintain the team in the appropriate direction. The project manager also incorporates a set of

exercises to maintain quality and unity of the project artifact .

Process Engineer

The process engineer seizes the requirement of a part of the organization aspects of and describes stages the and

requirement

different

supporting software requirements. The process engineer is liable for project environment and offers related support for the crew.

Development Team Lead

Responsible for leading and coordinating technical activities and artifact throughout the project. Development team is responsible for user interface design, software architecture and design analysis.

CONFIDENTIAL

(C) TEAM 3 2011

Page 9 of 14

Coventry University Track Locate and Assemble Software Development Plan Nagarjuna Murthy

Version: 1.0 Date: 22/11/2011

Test Team Lead

Test team lead is responsible for managing the test disciplines like making test plans, executing test plans; tests set up, evolution and execution of tests, identify the errors and recovering from the errors and maintain test reviews.

Software Engineering Team Lead

Participates in the extended project manager team and responsible for implementation, design and analysis throughout the project.

Table 2: Roles and Responsibilities

4.

Management Process

4.1

Project Estimation Expenditures for the CUTLASS project is divided as shown below Management Requirement Design Code and Unit testing Integration and test Development Environment 5% 5% 10% 30% 40% 5% 5%

CONFIDENTIAL

(C) TEAM 3 2011

Page 10 of 14

Coventry University Track Locate and Assemble Software Development Plan Nagarjuna Murthy

Version: 1.0 Date: 22/11/2011

CUTLASS Project Budget

Labour

Activities Requirement Analysis & Design Implementation Test Management Development Environment

Cost 20000 40000 60000 96000 40000 22000 41000

TOTAL LABOUR

319000

Non Labour

Services Materials Other Direct Charges

4000 20500 5400

TOTAL NON LABOUR

29900

TOTAL BUDGET

348900

Table 3: CUTLASS Budget

CONFIDENTIAL

(C) TEAM 3 2011

Page 11 of 14

Coventry University Track Locate and Assemble Software Development Plan Nagarjuna Murthy

Version: 1.0 Date: 22/11/2011

4.2

Project Plan The inception phase of the CUTLASS project can be observed as follows

TASK Inception Inception Begin Inception Kick off Requirements Requirements Meeting Management Inception Wrap up Conduct Quality Check Inception Complete

START DATE 23 Oct 2011 24 Oct 2011 24 Oct 2011 25 Nov 2011 31 Oct 2011 07 Nov 2011 13 Nov 2011 16 Nov 2011 21 Nov 2011

END DATE 22 Nov 2011 24 Oct 2011 24 Oct 2011 30 Nov 2011 06 Nov 2011 12 Nov 2011 15 Nov 2011 20 Nov 2011 21 Nov 2011

Table 4: Project Plan Schedule

4.2.1

Phase Plan

Phase

No of Iteration

Start

End

Inception Phase

18 Oct 2011

22 Nov 2011

Elaboration Phase

23 Nov 2011

10 Jan 2012

Construction Phase

-TBD-

-TBD-

Transition Phase

-TBD-

-TBD-

Table 5: Phase Plan Schedule

CONFIDENTIAL

(C) TEAM 3 2011

Page 12 of 14

Coventry University Track Locate and Assemble Software Development Plan Nagarjuna Murthy

Version: 1.0 Date: 22/11/2011

4.2.2

Releases

At this stage of the project, no announcements are scheduled. The primary release will be in the construction phase and its scope will be determined in that phase respectively. 4.2.3 Project Schedule

The Maiden project schedule for CUTLASS can be met in section 2.4. 4.2.4 Project Resourcing Staffing Plan The employees who are a part of this plan are listed in section 3.1 Resource Acquisition Plan Not Valid. Training Plan The employees who are into CUTLASS project have suitable skills where crew meeting and group discussions will have been conducted during inception phase to ensure that employees gain proper knowledge and techniques to support for the development of the project. Budget The CULTASS budget is described in the section 4.1.

4.3

Project Monitoring & Control

The purpose of this is to provide understanding of the CUTLASSs progress. So that appropriate actions can be taken when the projects functioning differs considerably from the plan. 4.3.1 Requirement management:

Process of analysing, tracking, prioritizing, reporting on requirements and communicating to the relevant stakeholders. It is continuous process. Here in CUTLASS, the system asks students to register their details and devices after the device is misplaced or lost the system continuously keep track of the device whenever it is online.

CONFIDENTIAL

(C) TEAM 3 2011

Page 13 of 14

Coventry University Track Locate and Assemble Software Development Plan Nagarjuna Murthy

Version: 1.0 Date: 22/11/2011

4.3.2

Schedule and Budget Control:

The CUTLASS project is expensive; it has to always keep track of the device whenever it is online and should notify the information on the website as to update the details of it as it becomes easy for a student to search his device. a developer has to keep track of the budget as how much he has to spend on specific applications on which he is been developing. 4.3.3 Quality Control:

It is the process where objects are reviewed for its quality involved in the development f a project and dwells on testing of the components to see the defects and documenting as to who takes the decision for rejecting the products to release. 4.3.4 Reporting and Measurement:

The CUTLASS has to document the report about the misplaced device whenever it comes online. The on board system alarms and the GPS tracks the location of the device. These things are reported on to the website. 4.3.5 Risk Management:

It focuses on identifying risk. It understands the upside and downside of all the factors affecting to the project where it increases the success probability and decreases the failure probability of the project. It is a continuous process, which keeps running throughout the development of project, addresses the risk step by step in a particular project. 4.3.6 Configuration Management:

It is a process, which focus on maintaining the systems performance and its requirements, designs and its functionalities. In the CUTLASS project, the system is configured in such a way that when the device comes online, it starts monitoring and the location is tracked where in regular intervals the updates are made on the website about the lost device.

CONFIDENTIAL

(C) TEAM 3 2011

Page 14 of 14