SOFTWARE DEVELOPMENT PROPOSAL

Software Development Plan

Version 1.0

City or country
Year

1
 TABLE OF CONTENTS

I. INTRODUCTION
1.1 Purpose
1.2 Scope
1.3 Justification/Summary

II. PROJECT OVERVIEW

2.1 Propósito, Alcance, Objetivos
2.1.1 Purpose
2.1.2 Scope
2.1.3 Objectives
2.2 Product to be Delivered
2.3 The Developed System
2.3.1 System Documentation
2.3.2 Manuals
2.4 Evolution of the Software Development Plan

III. PROJECT ORGANIZATION

3.1 Participants in the Project Development.
3.2 External Interfaces
3.3 Roles and Responsibilities

IV. PROJECT MANAGEMENT

4.1-Project Estimates
4.1.1. Licenses
4.1.2. Software
4.1.3. Hardware
4.1.4. Summary
4.1.5. General conditions
4.2 Project Plan
4.2.1. Phase Plan
4.2.2. Project Calendar
4.3 Monitoring and Control of the Project
4.4.1 Historial de Revisiones
4.4.2 Risk Management

V. ANNEXES

2
I. INTRODUCTION

This Software Development Plan is a preliminary version prepared to be

included in the proposal developed in response to the project "(name of
software)". This document provides a global overview of the development approach.
proposed.

In the project, a methodology of (name the development methodology) is used.

of the software) in which only the phases will be carried out (name the
number of phases in numerical form) that marks the software methodology
(name the acronym or the methodology), It is important to highlight this since
we will use the terminology (acronym) (meaning of the acronym) in this document. There
will include the details for the phases of Analysis, Design, Development, and Implementation
of the proposed system for (mention areas or processes that will be
systematized or automated.

The proposed development approach constitutes a configuration of the process.

(mention the global process or the global area to be systematized) according to the
characteristics of the project (mention project name).

1.1 Propósito
The purpose of the Software Development Plan is to provide information
necessary to control the project. It describes the development approach of the
software.

The objective of the system development is the analysis, design, and implementation of a
System (name of the software), intended to organize, control, strengthen a
area, automate, etc) the information of the processes of (name the processes
that will be automated or systematized).

The objective of this System is to provide a comprehensive solution for management

of the company's resources (clients, products, services, etc.), involved
in all processes of the Company 'company name'.

1.2 Alcance
The Software Development Plan describes the overall plan used for development.
of "(software project name)". During the development process,
define the characteristics of the product to be developed, which constitutes the basis
for the planning of the phases or activities that must be completed by the
project implementation.

3
For version 1.0 of the Software Development Plan, we have based ourselves on the
requirements capture through (describe what means or mention the means)
such as computers, barcode readers, etc.) to make an improvement to
the way the processes are carried out, once the project has started and
During the Start phase, the trial versions will be generated to verify their
good functioning, in addition, the operability of each will be monitored
phase to make adjustments to the System by producing new versions
updated.

1.3 Justificación/Resumen
The Company 'company name' requires the implementation and establishment
from a personalized information system that allows providing information
timely, reliable, up-to-date, and relevant to the processes being carried out
(name dependencies such as sales, services, warehouse, etc.), enabling
decision-making at all organizational levels, this being
information compatible with the processes and controls established by it
institution.

A solution is needed that allows for automation, in a secure manner.

efficient, of all the current processes practiced in their Transactions
daily business.

The following system documentation (software name) for 'name of the

"company" in the following sections:
•Project Overview — provides a description of the purpose,
scope and objectives of the project, establishing the artifacts that will be
produced and used during the project.
Project Organization — describes the organizational structure of the
development team.
Management of the Process — explains the estimated costs and planning, defines
the phases and milestones of the project and describe how its monitoring will be carried out.
•Application Plans and Guides — provides an overview of the process of
software development, including methods, tools, and techniques that
they will be used.

4
II.- GENERAL OVERVIEW OF THE PROJECT

2.1 Propósito, Alcance, Objetivos

2.1.1. Purpose: The purpose of the System Project (software name)
la Empresa “nombre de la empresa” es proporcionar las facilidades del flujo de
necessary information to control (mention that it controls example sales,
warehouse, information, etc.) that must support the project.

2.1.2. Scope: The Software Development Plan is a document in which it

describe the global plan used for the development of 'software name'. During
the development process will meet the functional requirements that are
define according to the characteristics of the product to be developed, which constitutes the
basis for the planning of the (mention number of phases or modules to
to develop) .

For version 1.0 of the Software Development Plan, we have based ourselves on the
requirements capture (mention the means of capture connected computers to
a website, scanner, readers, etc.), and during the phase of (name that phase as
start, test, implementation) the first functional version will be generated, which
will be used to refine this document.

2.1.3 Objectives: The Objective of the Information System (name of the software)
for the company (company name), it is to fulfill the (it can be
systematization, automation, control, etc.) of the incoming information of the
processes of (name the processes example, storage, sales, data entry).

The objective of this Information System is to provide a comprehensive solution and

optimal for the good management of the company's resources (clients,
products, services, etc.), involving all processes of the Company
company name

2.2 Product to be Delivered

The product to be delivered it is defined in each of the stages of the
methodology to be used, which must at least include the following:

2.3 The Developed System

•Systems of (for example sales control, user tracking, etc), with
database engine (mention names like Mysql, Access, SQL)
Server 2005, etc.) and installation of the same.
Materials and guides for your implementation.

5
 Data Dictionary.
Technical support for the Developed System, corresponding to the
Final Implementation phase, ensuring quality, integrity, and good
functioning of the software.

2.3.1 System Documentation: This document will show

the entire process (Acronym and name of the software methodology used in the
software development) carried from the initiation phase to the finished product
what is the "name of the software or information system"

2.3.2 Manuals: The following Manuals will be presented to have a better

scope of the System: (name the manuals if several are necessary and a brief
description

•System Manual: In this document, the steps will be followed

suitable for conducting the maintenance of Clients, Products,
Formulas, etc. contains the architecture of the system, structure of the
buttons that make up each module, general description of the processes,
data model, Process diagram according to the data flow of
each module and data dictionary.
User Manual: With this manual we will have a guide for the
correct use of the system by the employee of the Company 'name'
of the company
to be able to make sales of the different products and services. Directed at
end user who will use the system, performing their daily tasks.
It will include, at the very least, the description of the system functions in
general and each of its modules in particular and how to operate it
from the end user, description of the menu structure,
description of menus and screens, use of interactive aids, description
de formas y reportes y un glosario de términos orientados a los procesos
that users will carry out with the information system.
Installation Manual: With this manual we will have a guide
for the correct installation of the system, this document will cover
the basic requirements on a computer to be able to install the system and
what applications it should have.

2.4 Evolution of the Software Development Plan

The Software Development Plan is (mention time period whether weekly,
monthly, quarterly or as agreed in the contract) and will be refined before the start
of each (mention whether it is a phase or development module).

6
III. PROJECT ORGANIZATION

3.1 Participants in the Project.

Considering the phases of Initiation, Elaboration, and Construction, it will be made up of
the following jobs and those responsible for them:

Database Administrator. Name of the person, with experience

modest in the handling of (database engine MYSQL, Access, etc).

Analista de Sistemas. El perfil establecido es conocimientos de UML y el proceso

of development (acronym for the software development methodology used in the
project), so there is at least experience in related systems of the
Project line, work to be carried out by the person's name.

Programmer. With experience in the project's development environment, in order to

that the prototypes can be as close as possible to the final product. This
work has been assigned in the name of the person

Documenter. He is responsible for carrying out requirements management tasks,

documentation and design of the project's presentation scheme, the person in charge
is the name of the person.

3.2 External Interfaces

The modules that will be part of the proposal will be described below.
"software or control system name" for (company name) and its
requirements functionalities, technical aspects and characteristics of the system
of information.

The following example contains information on how to fill out the steps.
final stages of the software development proposal

MODULES THAT ARE PART OF THE PROPOSAL OF THE 'SYSTEM OF'

CONTROL OF SALES AND SERVICES OF THE COMPANY TITO.

FUNCTIONAL REQUIREMENTS
To better specify the functionality of the software required by the Company
"TITO", blocks of requirements called modules have been formed, which
they will be interpreted as a way to organize and classify the functionalities and
not necessarily as software modules.

7
SALES PROCESS REQUIREMENTS
It will have the following specific tasks:

Generate monthly statistical reports on how many people (Customers)

attend our establishment 'TITO'.
Generate a receipt that shows the quantity of products sold and the
total sales price.
List the prices of each product.
Generate and update the list of the different types of products sold
during the day.
Control and update profits and losses throughout the day.

It will also include and must manage the following general parameters:

Series - The number that identifies the receipt issued in the sale.
•Type of Receipt.- The types of receipts are stored that are
issue when making a sale (receipt, invoice, etc.)
•Tipo de Ventas.- Si es al contado o al crédito
Sales.- Daily sales made from the sale of products
Clients.- The data of those who buy the products.
•Product.- The different products offered by the bakery.

WAREHOUSE PROCESS REQUIREMENTS

It will have the following specific tasks:
Register and update the stock of products by suppliers that enter into
warehouse.
Register and update the stock of supplies by suppliers entering the
warehouse.
Control the payment to suppliers.
Cancel a specific purchase.
•List the complete information of suppliers (name, phone, address,
city, etc.)
Add and remove a supplier.
Control the supply outputs to other areas.

It will also account for and must handle the following general parameters:
Supplier - The one from whom the supplies are purchased.
•Tipo de Insumo.- Insumo de Producción e Insumo de Venta.
•Producto.- Los diferentes productos que oferta la panadería

8
 Input. the different inputs (raw materials) that will be needed for the
production
Storekeeper.- The one in charge of controlling the supplies and products that
they are in the warehouse.
Categories. The types of products (whether they are cakes, breads, pizzeria, coffee,
etc.)
Purchases.- the types of products (whether they are cakes, breads, pizzeria, coffee,
etc.)
•Tipo de Compra.- Al contado o al crédito

SERVICE PROCESS REQUIREMENTS

It will have the following specific tasks:
Register and update the services provided to the various clients.
Show and update the sales services to be carried out on said vehicles.
List and control the selected personnel for the execution of the work.
those services to the customers' vehicles.
List and control the services that have been produced.

REQUIREMENTS OF THE REPORTING PROCESS

You will have the following specific tasks:
Report the daily sales made by the seller during the course of
day.
Report the departure of supplies from the Warehouse either to the service area.
or of Sales.

In addition, it will account for and must manage the following general parameters:
Daily Sales - The sales made per day.
•Inputs.- the different inputs (raw material) that will be needed for
the production.

NON-FUNCTIONAL REQUIREMENTS.
The information system will have the following operational characteristics.
Ergonomics: The software should be easy enough to handle.
the user; that is to say, the latter will be able to perform all operations in the
system either using the keyboard or the mouse.
• Integration: That is, it must integrate all the information and synchronize.
all processes and events, which will allow obtaining information everywhere
moment. All software modules must integrate information.

9
 Scalability: The software design will support increasing volume
of operations without needing to modify the source code.
Performance: The response time and the duration of the options
The software functionalities of the company 'TITO' will be as fast as possible.
Therefore, the level of service required is such that the information system
does not suffer a decrease in its performance (degradation) regarding
at the level prior to production deployment.
•Technological compatibility: The software will run on the platform
technological of the new equipment that the company 'TITO' will implement.
User interface: The software must have a user interface
fully integrated in a graphical and user-friendly environment in all its
components.

TECHNICAL ASPECTS OF OUR SYSTEM.

Database Manager to Utilize: Our group proposes that the
The database manager for the present development must be SQL Server
2005 Express and MYSQL SERVER 5.0, which has been chosen taking into account the
the following evaluation criteria.
•Security. SQL Server 2005 Express and MYSQL Server 5.0 implements a
security level at the login and database level, which
guarantees the confidentiality of the data of the Company 'TITO'.
•Information integrity management. SQL Server 2005 Express validates
the integrity of the information that the user is trying to save when making a
transaction.
•Database synchronization. The replication process requires
database synchronization, for which SQL Server 2005 Express
guarantees through transactional or instant synchronization
depending on the functionality of the branch.
Data capacity: SQL SERVER 2005 Express and MYSQL SERVER 5.0
It supports up to terabytes of information, which means a great capacity.
of data and benefit for the company.
•User concurrency. The system proposed for the company 'TITO'
it will be implemented in a client-server architecture with concurrency
simultánea de los diferentes puntos de venta, ello implica que el manejador
the database guarantees this functionality as the company tends to
grow and the level of concurrency could be greater.
•Computer support. Currently, Microsoft is the largest company in the
the world and the technical support for its products is unlimited.

10
Integrated Development Environment (IDE) tool to use: Our
group suggests that the integrated development tool for the present
development must be JBUILDER, which has been chosen taking into account the
following evaluation criteria:
JBUILDER is an integrated development environment specifically designed
to facilitate the construction and development of web services and solutions and
desk.

Among its many features, its multi-language support stands out.

allows integrating code written in different languages into the same application
programming.
Security.- JBUILDER makes it easier for developers to write
secure applications. It will be possible to write safe unmanaged code or
obtain the IDE tools that allow creating and implementing
managed applications that use code access security
(CAS, Code Access Security).
Interface design using the Swing library in JAVA.
Integration with JAVA RUNTIME.
Creation of console applications
Other features to highlight include: an integrated development environment, a
complete debugger, Crystal Reports or an assistant for HTML design

Software Base: The platform of the base software that is currently will be the
same on which the application will run.

GENERAL CHARACTERISTICS OF THE INFORMATION SYSTEM.

The information system to be developed must allow for automation.
secure and efficient of all operational processes, the optimization in the use of
the company's resources, the consolidation and presentation of information from
support for decision-making at all levels of management, allowing for
among other information that facilitates the analysis of management.

The system to be implemented will have the following general technical characteristics:
The system will operate on the Windows 2000/NTWs/95/98/XP platform and
free software Ubuntu 9.10 (this is because it is taken into consideration the
platforms that the company will propose to use, both in resources of
hardware, as well as base software for the information system).
It will have a user-friendly graphical interface between the system and the user.

11
The system to be implemented is of Client/Server type and will use the engine of
database relate SQL Server 2005 Express and MYSQL SERVER 5.0.
The system will have several levels of security protected by
passwords, this will allow us dynamic access to the
different system options.
The information stored in the databases will be easily
"transportable" for use in another system, for example, to export the
information in the form of files for your use or consultation with Sheets of
calculation, Word Processors, flat files and/or others.
The system will provide reports, whether by screen, printer, or file.
The system will allow the consolidation of information, includes
data transmission mechanisms: manual and automatic.
The system will be developed in JAVA ECLIPSE/SQL SERVER 2005
EXPRESS Y MYSQL SERVER 5.0.
Automatic generation and printing of pre-designed documents in the
system.
Administration of historical information.

12
Revisiting the example of the company TITO, the following shows how
fill in the steps regarding numeral VI on project management for a
software development proposal.

IV. PROJECT MANAGEMENT.

4.1 Project Estimates

The following is the economic proposal for the execution of the present
project.

4.1.1. Licenses.
ITEM DESCRIPTION CANTIDAD PRECIO $ TOTAL
1 Java Eclipse Version 1 Free
Galileo
2 SQL Server 2005 Express 1 Free
3 MYSQL SERVER 2005 1 Free
4 Rational Rouse IBM 1 2252 USA 2252.00
5 Windows XP Profesional 1 750 USA 750.00
3002.00

4.1.2. Software.
ÍTEM DESCRIPCIÓN CANTIDAD PRECIO TOTAL
1 Analysis, design, implementation 1 9000.00 9000.00
Sales control system and
services of the company TITO

TOTAL 9000.00

4.1.3. Hardware.
ÍTEM DESCRIPCIÓN CANTIDAD PRECIO TOTAL
1 Micronics Pentium IV 1 2,754.00 2,754.00
(Depreciation: 1.67% monthly)
2 Samsung Pentium 4 1 2,448.00 2,448.00
2 LG Pentium 4 1 2,448.00 2,448.00
3 Canon PIXMA IP1600 printer 1 187.00 187.00
(Depreciation: 1.67% monthly)
TOTAL 7,837.00

4.1.4. Resumen.

13
 CATEGORY TOTAL
Licenses 3002.00
Software 9000.00
Hardware 7,837.00
Others (10%)
TOTAL 19839

4.1.5. General conditions.

As can be seen in the Economic proposal, it is divided into 3 main parts.

which are specified in the following lines to better define the structure
of costs presented:

•Licencias: Este rubro indica las licencias que la Empresa “TITO” deberá
acquire for software development. The acquisition of
these licenses because the Source Code of the Application (since the
source code of the software and the database), will belong to the
Company "TITO", and its acquisition is required to have the right
to make the required modifications.

•Software: Here the cost of analysis, design, and implementation is indicated.

software development, the same that is proposed for the disbursement to be in
equal monthly installments. ($2,000.00), which includes all the
taxes established by the relevant legal rules, which will be useful to us
for the expenses during almost the entire development of the System.

•Hardware: The acquisition of 2 computer units is suggested for the

software construction, as these will provide greater
ergonomic features that will allow to make the most of the
characteristics of these machines and expedite the construction of
System.

Others: Multiple expenses incurred throughout the

development of the project such as the payment of electricity consumption, CDs,
rental of computers, printing of documentation, sheets, some
last minute inconveniences and other expenses.

4.2 Project Plan

14
4.2.1 Phase Plan. The development will be carried out based on phases with one or
more iterations in each of them. The following table shows one of the
distribution of times and the number of iterations of each phase (for the phases of
Construction and Transition is just a very preliminary approximation.

PHASE NRO. ITERATIONS DURATION

Starting Phase 1 4 weeks

Drafting Phase 2 3 weeks
Construction Phase 2 5 weeks
Transition Phase 1 2 weeks

The milestones that mark the end of each phase are described in the following table.

DESCRIPTION FACE
In this phase, you will develop the necessary requirements of
product from the user's perspective, which will be
established in the Requirements Capture artifact. The
main use cases will be identified and a
Start Phase refinement of the Project Development Plan. The
client/user acceptance and the Development Plan
mark the end of this phase.

En esta fase se analizan los requisitos y se desarrolla un

architecture prototype (including the most important parts
relevant and/or criticisms of the system). At the end of this phase,
all use cases corresponding to requirements that
will be implemented in the first version of the phase of
Construction must be analyzed and designed (in the
Analysis / Design Model.
Development Phase
The review and acceptance of the prototype of the architecture of
system marks the end of this phase. The first iteration
will aim at the identification and specification of the
main use cases, as well as their preliminary implementation
In the Analysis / Design Model, it will also allow to do
a general review of the status of the artifacts up to this point
point and adjust if necessary the planning to ensure
the achievement of objectives. Both iterations will have
a duration of weeks.

15
 During the construction phase, the analysis is completed and
design all use cases, refining the Model of
Analysis/Design. The product is built based on 2
iterations, each producing a version to which it
Tests are applied and validated with the client/user.
Phase of
Construction The development of the supporting material begins
user. The milestone that marks the end of this phase is the version
from the version, with the partial operational capability of
product that has been considered as critical, ready for
to be delivered to the users.
In this phase, two versions will be prepared for distribution.
ensuring an implementation and change of the previous system
appropriately.
Transition Phase
The milestone that marks the end of this phase includes the delivery of
all the project documentation with the manuals of
installation and all the user support materials, the
completion of user training.

4.2.2 Project Calendar: Below is a project calendar of the

main tasks of the project including only the Initiation and Elaboration phases.
As discussed, the iterative and incremental process of RUP (Process
Unified Rational) is characterized by the parallel execution of all
development disciplines throughout the project, which means that most of the
artifacts are generated very early in the project but go
developing to a greater or lesser degree according to the phase and iteration of the
project

The following schedule has been established for this project. The date of
Approval indicates when the artifact in question has a state of completeness.
sufficient to submit for review and approval, but this does not eliminate the possibility
of its subsequent refinement and changes.

DISCIPLINES / ARTIFACTS
GENERATED OR MODIFIED BEGINNING APPROVAL
DURING THE STARTUP PHASE

BUSINESS MODELING

16
 Use Case Model
Week 1 Week 3
Business and Object Model of the
01/10 – 07/10 15/10 – 21/10
Business

REQUIREMENTS
Week 2 Week 3
Glossary
08/10 – 14/10 15/10 –21/10
Week 2 Week 3
Vision
08/10 – 14/10 15/10 –21/10
Week 3
Use Case Model next phase
15/10 –21/10
Week 4
Use Case Specification next phase
22/10– 28/10
Week 5
Additional Specifications next phase
29/10– 04/11
ANALYSIS / DESIGN

Week 6 and 7
Analysis / Design Model next phase
04/10 – 18/11
next phase
Week 8
Data Model
19/11– 25/11

IMPLEMENTATION
Week 9 and 10
User Interface Prototypes next phase
26/11 – 09/12
Week 11
Implementation Model next phase
10/12 – 16/12
TESTS
Week 12
Functional Test Cases next phase
17/12 –23/12
DEPLOYMENT
Week 11
Deployment Model next phase
24/12 – 30/12
Change and Configuration Management Throughout the project
Project management
Software Development Plan in
Week 10 Week 12
its version 1.0 and plans of the
31/11 – 02/12 07/12 –23/12
Iterations.

17
Environment Throughout the project

4.4 Project Monitoring and Control

4.4.1 Revision History

VERSION DATE DESCRIPCIÓN

1.0 08/08/2009 Preliminary version as a development proposal.

2.0 24/10/2009 Proposed version for approval at the end of the phase of
beginning.

3.0 03/11/2009 Revised version in the drafting phase.

4.0 05/11/2009 Revised version at the end of the Elaboration phase.

5.0 12/11/2009 Revised version in the first iteration of the phase of

construction.

6.0 07/12/2009 Revised version in the second iteration of the phase of

construction.

The project calendar will have a weekly follow-up and evaluation by the manager.
of the project, the defects detected in the reviews and formalized will have a
follow-up to ensure compliance regarding the solution of these
deficiencies.

For the review of each artifact and its corresponding quality guarantee,
They will use the review guides included in RUP.

4.4.2 Risk Management: Starting from the Initiation phase, a list will be maintained of
risks associated with the project and the actions established as a strategy for
mitigate them or contingency actions. This list will be evaluated at least once
in each iteration.

RISKS CONTINGENCY ACTIONS

18
1. Low intensity of Electric Energy, 1. Save every moment the
and that the advanced information being handled is lost,
and our entire system, or that takes into account aspects of
some failures at the time of security.
tests.

2. Pérdida de información la base de 2. Sacar una copia de seguridad cada

Data. certain time, as it is being
advancing the project.
They are handled with care, it is done the
3. Advanced information loss due to regular maintenance, is
some malfunction of the computer, other equipment loaned.
Failure of the equipment.

To the fire, which can destroy the General equipment, a copy is made almost
and files. daily of the files that are vital
for the company.

In the common theft, taking the equipment and Common theft, the doors are closed.
files. input and windows.

To the action of viruses, which damage all software that arrives, it is analyzed.
teams and files. in a system using software
antivirus.

IN ANNEXES

The annexes include the data flow diagrams, glossary, and other parts that
they cannot be placed within the body of the proposal. These annexes fulfill the

19
function of complementing the information that is intended to be made known for
to fulfill the development of the project.

20