<Project Name>

Software Development Plan

Version <1.0>
 Revision History
Data Version Description Author
18/03/2010 <0.5> Project start. Rafael Freitas, Alex,
Vanessa
01/06/2010 1.0 Creation of the first version. Rafael Freitas, Alex,
Vanessa
01/07/2010 1.1 Creation of the next release containing Rafael Freitas, Alex,
more advanced resources. Vanessa
01/10/2010 2.0 Penultimate release, where the will be made the Rafael Freitas, Alex,
latest modifications. Vanessa
20/10/2010 <2.0 final> Software installation. Rafael Freitas, Alex,
Vanessa
 Content
1. Introduction 4
1.1 Purpose 4
1.2 Scope 4

2. Project Vision 4
2.1 Propósito do Projeto, Escopo e Objetivos 4
2.2 Premissas e Restrições 5
2.3 Project Artifacts 5
2.4 Evolution of the Software Development Plan 5

3. Project Organization 5
3.1 Organizational Structure 5
3.2 Roles and Responsibilities 6
3.3 Team 6

4. Project Management 7
4.1 Project Estimates 7
4.2 Project Plan 7
4.2.1 Phase Plan 7
4.2.2 Releases 8
4.2.3 Project Schedule 8
4.2.4 Project Resources 9
4.2.5 Budget 9
4.3 Project Control and Monitoring 10
4.3.1 Requirements Management Plan 10
4.3.2 Schedule Control Plan 10
4.3.3 Budget Control Plan 10
4.3.4 Plano do Controle de Qualidade 10
4.3.5 Communication Plan 10
4.3.6 Metrics Plan 10
4.4 Risk Management Plan 11
4.5 Closure Plan 11

5. Support Plans for the Process 11

5.1 Configuration Management Plan 11
5.2 Evaluation Plan 11
5.3 Documentation Plan 11
5.4 Quality Assurance Plan 12
5.5 Problem Solving Plan 12
5.6 Process Improvement Plan 12
Software Development Plan
Software Development

1. Introduction
 The objective of this document is to define in detail relevant factors for planning, execution and
monitoring of the development of the Contabic project, which will be carried out by Taurus Softwares. These
factors mainly encompass scope, timeline, resources, quality, risks.
1.1 Propósito

The main purpose of this document is the planning of the software control development.
Contabic costs.
1.2 Scope

The scope of this system is to implement the cost control system in companies that require it.
use of this.

2. Project Vision
2.1 Project Purpose, Scope, and Objectives

Development of a cost control system that assists a company in managing

questions like:
Registration of active employees and departments.
The administrator has the power to register new employees and in which departments this
employee will work.
Department Registration
The administrator has the power to register the company's departments.
Management of movements
Financial managers will have the power to confirm all transactions made by
employees.
Department management
The administrator has the power to close a specific department, clearing its account.
Manage job assignments
The administrator has the power to assign positions of financial agent and financial manager to
certain employees.

2.2 Premises and Restrictions

At the client's request, CONTABIC will be a web software that will run on a server.
Apache Tomcat.
It will be developed using the JAVA programming language.
The work will be carried out by a team of three people, who will work for about eight hours per
day for approximately 9 months.
The budget is estimated at R$ 44,500.00
 Team consisting of three members.
Estimated time for project production is 1570 hours.
Three microcomputers with technology and requirements necessary for production and testing of
system.
Operating license in accordance with laws.
Work of at least 6 hours daily per person.

2.3 Project Artifacts

Fase Artifact Delivery date

Project development of Development plan of 09/04/2010
software Software.
Look for the requirements Requirements document 14/04/2010
Implementation Implementation of components 14/08/2010
Testes Software tested and approved for 20/10/2010
loading to the web
Integration Software loading 27/10/2010

2.4 Evolution of the Software Development Plan

Visual version 0.5 Analysis of the visual structure and necessary items for
implementation.
Version1.0 Creation and testing of the main elements of the system
Version1.1 Creation and testing of the system's advanced features

Version2.0 Summer semi-final in which the test will be carried out and the
correction of problems or improper facts that do not
thank the end user. This will be done with the
user participation.
Final version 2.0 System ready and distributed soon.

3. Project Organization
3.1 Organizational Structure
3.2 Roles and Responsibilities

Paper Description
Project Manager (PM) Responsible for planning and monitoring
of activities. Allocates resources, sizes tasks and
interact with the client.
Quality Analyst (SQA) Responsible for defining the process that ensures
the quality of the software being produced.
Conduct quality audits and collect metrics at
long of the project.
Systems Analyst (SA) Carry out the survey and analysis of requirements of
software.
Database Designer (DBA) Realiza o levantamento do banco de dados da
application.
Architect (ARQ) Define the system architecture.
Configuration Engineer (SCM) Responsible for defining and managing the control of
version.
Software Engineer (SW) Responsible for defining and managing control of
version.
Test Engineer Responsible for defining the testing environment and
planning of test cases.
JAVA Programmer Responsible for creating the source code.

3.3 Team

Name E-mail Papers

 Rafael Freitas Costa rafael@[Link] Project Manager, Designer
of the Database,
JAVA Programmer.
Alex Sonda alexsonda@[Link] Systems Analyst
Software Engineer and
Configuration Engineer,
JAVA Programmer.
Vanessa Oliveira assenavs1@[Link] Quality Analyst, Architect
the Test Engineer,
JAVA Programmer.

4. Project Management
4.1 Project Estimates

We estimate that with the personal effort of each one in the project and the willingness of time, it may be
develop and successfully complete the project in about 9 months, and with the amount of R$
44,500.00 it may be possible to develop the system as planned. If there is a need for reassessment of
proposed, it will be triggered during the weekly meetings.

4.2 Project Plan

4.2.1 Phase Plan

WBS
Documents
o Meeting with the client.
o Creation of the software development plan
o Creation of the requirements document.
Definition of functions
o Establish the functions for each team member
o Define tasks for each role.
o Find out each employee's satisfaction with their position.
Definition of the tools
o Choose which hosting server will be used
o Define the programming language to be used
o Define the database to be used
Development
o Criação dos diagramas.
o Code implementation
o Software test
 o Project closure
o Software loading to the web
o Training of employees who will use the software
Gantt chart

Documents
· Requirements gathering
· Creation of the software development plan
· Creation of the requirements document
Definition of functions
· Establish the roles of the team members
· Define tasks for each function.
· Findoutteamsatisfaction.
Definition of the tools
· Choose which hosting server will be used
· Define the programming language that will be used.
· Define the database
Development
· Development of diagrams
· Codeimplementation
· Tested software
Closing of the project
· Loading software for the web
· Training of employees who will use the software

18/3 2/4 17/4 2/5 17/5 1/6 16/6 1/7 16/7 31/7 15/8 30/8 14/9 29/9 14/10 29/10 13/11 28/11

4.2.2 Releases

This software will have exactly five releases, with the final release being delivered on 10/27/2010.

4.2.3 Project Schedule

Data Actions
18/03/2010 Meeting with the client, meeting with the team.
28/03/2010 Beginning of the software project creation, creation of
Gantt chart.
09/04/2010 Meeting with the developers to define the server
of the hosting that will be used.
14/04/2010 Delivery of the requirements document. Meeting with the
programmers to define the language that best fits
fits into the development of this project. It is important
the opinion of everyone.
17/04/2010 Meeting with the team, especially with the DBA to
definition of the best database for the
project development.
21/04/2010 Divide the team by defining the roles of each member.
22/04/2010 Establish the tasks of each assigned function for the
members in the previous step.
28/04/2010 Meeting with the team and check if there is any
 dissatisfaction with the assigned functions. If so,
investigate the possibilities of change.
10/05/2010 Beginning of the creation of the diagrams
01/06/2010 Start of the creation of the source code of the program,
using the language that was defined earlier.
14/08/2010 Start of the program tests, for later on
Carry out the implementation.
20/10/2010 Deployment of the software on the hosting server.
27/10/2010 Start of the user training phase
01/12/2010 End of the project.

4.2.4 Project Resources

[Link] Staff Plan

All individuals in the project have expertise in their respective roles.

Paper Quantity Level of experience Allocation
Project Manager 1 Average Rafael
JAVA Programmer 3 High Everyone from the team

System Analyst 1 Media Alex

Software Engineer 1 Media Alex
Engineer of 1 Average Alex
Configuration
Architect 1 Average Vanessa
Test Engineer 1 Media Vanessa
DBA 1 Average Rafael
Quality Analyst 1 Average Vanessa

[Link] Resource Acquisition Plan

There will be no recruitment of personnel as the team is already formed, and regarding the physical aspect, it will be necessary.
only the company's own computers.

[Link] Training Plan

During the project development period, each group member will be responsible for seeking out the
necessary knowledge for the performance of your activity.

4.2.5 Budget

Item Cost Comments

Labor R$ 40,500.00 Cost with salaries
Extra costs R$ 4,000.00 Cost of maintenance of
equipment.

4.3 Project Control and Monitoring

4.3.1 Requirements Management Plan

The software requirements were defined based on the client's needs; however, they may come to
suffer modifications throughout the project.

4.3.2 Schedule Control Plan

There will be short weekly meetings with the team to evaluate the progress of the project and make corrections.
possible delays. There will also be reports that will be delivered monthly.

4.3.3 Budget Control Plan

Monthly, the expenses for the project will be evaluated; if there is any change in the budget, it will be
immediately analyzed the reason that led to the change and control measures will be taken, in case of
it will not be possible to circumvent the problem, a new budget will be prepared and this will be discussed with the client.

4.3.4 Quality Control Plan

The quality of the project will always be under the supervision of the Test Engineer and Quality Analyst.
which will report any eventual problems found during the development of the project. In case of
Problems will be addressed through meetings immediately with those responsible to discuss possible solutions.
to solve it.

4.3.5 Communication Plan

Reports will be generated weekly on the events that occurred during the week, in addition to email exchange.
emails and phone calls. A meeting will be held monthly with all team members to discuss the
project progress and difficulties that are being encountered.

4.3.6 Metrics Plan

During development, some metrics will be used to assess the quality of the software, among
they stand out:
Compatibility with hardware resources (e.g., printer)
Ease of use.
 Software design.
Organization of components with their relationships.

4.4 Risk Management Plan

The risks that will be taken into account are:

Description Risk level

Insufficient time for learning of
Medium
necessary technologies for software production.
Illness of team members, resulting in
Medium
delays.
Team members exit Low
Withdrawal of the project by the client Low
Data loss in the company due to technical reasons Very low
Data loss in the company due to external reasons
(lightning, hurricanes, etc)
Very low

4.5 Closure Plan

Presentation of the software to the client, software deployment on the web server, and user training
finals.

5. Support Plans for the Process

5.1 Configuration Management Plan

For the creation of this software, only the company's own computers will be needed.

5.2 Assessment Plan

The software will be tested for a period of one month using employees from the team itself and then will be
taken to the customer who will test it in their daily life, with support at all times.

5.3 Documentation Plan

Item number Tipo de documento

1 Software Plan
2 Requirements Document
3 Software user manual
 5.4 Quality Assurance Plan

The system will have a high level of reliability, as it will be tested by our analyst.
quality and test engineer. With that, every problem will be solved while still in the creation phase of
software.

5.5 Problem Solving Plan

As problems arise, reports will be made containing the problem and its reasons, and
meetings with those responsible so that they can present possible solutions to the problem, in case
In case of difficulties, a call may be made for the entire team to focus on its resolution.

5.6 Process Improvement Plan

After the completion of this project, an evaluation of its entire trajectory will be carried out analyzing its
deficiencies and strengths. This data will be stored to be used in upcoming projects that
forem made by Taurus Softwares.

Useful site for following the systematic processes in the preparation of artifacts for the software plan
[Link]