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 Rationale/Summary

II. PROJECT OVERVIEW

2.1 Purpose, Scope, Objectives
2.1.1 Purpose
2.1.2 Scope
2.1.3 Goals
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 Development of the Project.
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 Schedule
4.3 Project Monitoring and Control
4.3.1 Revision history
4.3.2 Risk management

V. ANNEXES
1. INTRODUCTION

This Software Development Plan is a preliminary version prepared to be included in

the proposal prepared in response to the “(name of software)” project. This document
provides an overview of the proposed development approach.

The project uses a methodology of (name the software development methodology) in

which only phases will be carried out (name the number of phases in numerical form)

2
that defines the software methodology (name the acronym or methodology). ), It is
important to highlight this since we will use the terminology (acronym) (meaning of the
acronym) in this document. The details for the Analysis, Design, Development and
Implementation phases of the proposed system will be included to (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 name of the project).

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

The Objective of the development of the System is the Analysis, design,

implementation of a System (name of the software)", intended to (organize, control,
strengthen an area, automate, etc.) the information of the processes of (name the
processes that are are going to automate or systematize).

The objective of this System is to offer a comprehensive solution for the administration
of the company's resources (customers, products, services, etc.), involved in all the
processes of the Company "company name".

1.2 Scope
The Software Development Plan describes the overall plan used for the development
of “(name of software project)”. During the development process, the characteristics of
the product to be developed are defined, which constitutes the basis for planning the
phases or activities that must be completed until the implementation of the project.

For version 1.0 of the Software Development Plan, we have relied on capturing
requirements through (describing what media or mentioning media such as computers,
barcode readers, etc.) to make an improvement to the way in which The processes are
carried out, once the project has started and during the Start phase, test versions will
be generated to verify their proper functioning, in addition, the operation of each phase
will be monitored to make adjustments to the System, producing new updated
versions.

1.3 Rationale/Summary
The Company “name of the company” requires the implementation and
implementation of a personalized information system that allows it to provide timely,
reliable, updated and relevant information to the processes it carries out both (name
dependencies such as sales, services, warehouse, etc.) , enabling decision-making at

3
all organizational levels, this information being compatible with the processes and
controls established by the same institution.

You need a solution that allows the automation, safely and efficiently, of all the current
processes that are practiced in your daily business transactions.

The following system documentation (software name) for ”company name” 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.
• Process Management — explains estimated costs and planning, defines project
phases and milestones, and describes how they will be tracked.
• Application Plans and Guides — provides a global view of the software
development process, including methods, tools and techniques that will be
used.

II.- GENERAL VIEW OF THE PROJECT

2.1 Purpose, Scope, Objectives

2.1.1. Purpose: The purpose of the System Project (software name) of the Company
“company name” is to provide the facilities for the flow of information necessary to
control (mention that it controls, for example, sales, warehouse, information, etc.) that
it must support the project.

2.1.2. Scope: The Software Development Plan is a document that describes the
overall plan used for the development of the “software name”. During the development
process, the functional requirements that are defined according to the characteristics
of the product to be developed will be met, which constitutes the basis for planning the
(mention number of phases or modules to be developed).

For version 1.0 of the Software Development Plan, we have based ourselves on the
capture of requirements (mention the means of capture: computers connected to a
website, scanner, readers, etc.), and during the phase of (name said phase as start ,
testing, deployment) 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 (name of the company), is to fulfill the (can be systematization,
automation, control, etc.) of the incoming information of the processes of (name the

4
processes (e.g. warehouse, sales, capture).

The objective of this Information System is to offer a comprehensive and optimal

solution for the good administration of the company's resources (customers, products,
services, etc.), involving all the processes of the Company "company name".

2.2 Product to be delivered

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

2.3 The developed system

• Systems (for example sales control, user tracking, etc.)”, with a database engine
(mention names such as Mysql, Access, SQL Server 2005, etc.) and their
installation.
• Materials and guides for its implementation.
• Data Dictionary.
• Technical support for the Developed System, corresponding to the final
Implementation Phase, guaranteeing the quality, integrity and proper
functioning of the Software.

• .3.1 System Documentation: This document will show the entire process
(acronym and name of the software methodology used in the development of the
software) taken from the initiation phase to the finished product, which is the “name of
the software or system.” of information"

• .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 appropriate steps will be followed to

perform maintenance on Clients, Products, Formulas, etc. It contains the
system architecture, 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: Through this manual we can have a guide for the correct use of
the system by the worker of the Company "name of the company", in this
document the appropriate steps will be followed to be able to make sales of the
different products and services . Aimed at the end user who will use the system,
performing their daily tasks. It will include, at least, the description of the
functions of the system in general and of each of its modules in particular and
how it is operated by the end user, description of the menu structure,
description of menus and screens, use of interactive aids, description of forms
and reports and a glossary of terms oriented to the processes that users are
going to carry out with the information system.

5
 • Installation Manual : Through this manual we can have a guide for the correct
installation of the system, in this document we will see the basic requirements for a
computer to be able to install the system and what applications it must have.

2.4 Evolution of the Software Development Plan

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

III. PROJECT ORGANIZATION

3.1 Participants in the Project.

Considering the Initiation, Preparation and Construction phases, it will be made up of
the following jobs and those in charge of them:

Database administrator. Name of the person, with modest experience in managing

(MYSQL database engine, Access, etc.).

Systems analyst. The established profile is knowledge of UML and the development
process (acronym for the software development methodology used in the project), with
which there is at least experience in systems related to the line of the project, work that
will be carried out name of the person.

Programmer. With experience in the project development environment, so that the

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

Documenter. He is in charge of carrying out requirements management,

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

3.2 External Interfaces

Below, the modules that will be part of the proposal for the “name of the software or
control system” for (company name) and their functional requirements, technical
aspects and characteristics of the information system will be described.

The example below contains information on how to complete the final steps of
the software development proposal.

MODULES THAT FORM PART OF THE PROPOSAL OF THE “SALES AND

SERVICES CONTROL SYSTEM OF THE TITO COMPANY”.

6
FUNCTIONAL REQUIREMENTS
To better specify the functionality of the software required by The Company “TITO”,
blocks of requirements called modules have been created, which will be interpreted as
a way of organizing and classifying the functionalities and not necessarily as software
modules.

SALES PROCESS REQUIREMENTS

You will have the following specific tasks:

• Generate monthly statistical reports on how many people (Clients) come to our
“TITO” establishment.
• Generate Receipt showing the quantity of products sold and the total price of
the sale.
• 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.

In addition, it will have and must manage the following general parameters:

• Series.- The number that identifies the receipt that is issued in the sale
• Type of Receipt.- The types of receipts that are issued when making a sale are
saved (slip, invoice, etc.)
• Type of Sales.- If it is cash or credit
• Sales.- Daily sales that are made from the sale of products
• Customers.-The data of those who buy the products.
• Product.- The different products that the bakery offers.

WAREHOUSE PROCESS REQUIREMENTS

You will have the following specific tasks:
• Register and update the stock of products by suppliers that enter the
warehouse.
• Register and update the stock of inputs by suppliers that enter the warehouse.
• Control payment to suppliers.
• Cancel a certain purchase.
• List complete supplier information (name, telephone, address, city, etc.).
• Add and delete a supplier.
• Control the output of inputs to other areas.

In addition, it will have and must manage the following general parameters:
• Supplier.- From whom the inputs are usually purchased.
• Type of Input.- Production Input and Sales Input.

7
 • Product.- The different products that the bakery offers
• Input. the different inputs (raw materials) that will be needed for production
• Warehousekeeper.- The one who is in charge of controlling the supplies and
products that are in the warehouse.
• Categories. The types of products (if they are cakes, breads, pizzeria, coffee,
etc.)
• Purchases.- the types of products (if they are cakes, breads, pizzeria, coffee,
etc.)
• Type of Purchase.- Cash or credit

SERVICE PROCESS REQUIREMENTS

You will have the following specific tasks:
• Register and update the services provided to various clients.
• Show and update the sales services to be performed on said vehicles.
• List and control the personnel selected to carry out the work of said services to
customer vehicles.
• List and control the services that have occurred.

REPORTING PROCESS REQUIREMENTS

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

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

NON-FUNCTIONAL REQUIREMENTS.
The information system will have the following operational characteristics.
• Ergonomics: The Software must be easy enough for the user to handle; That
is to say, the latter will be able to do all the operations in the system either using
the keyboard or the mouse.
• Integration: That is, you must integrate all the information and synchronize all
processes and events, which will allow you to obtain information at all times. All
software modules must integrate information.

• Scalability: The software design will support the increase in volume of

operations without the need to modify the source code.

8
 • Performance: The response time and duration of the functional options of the
“TITO” Company software will be as fast as possible. Therefore, the level of
services required is such that the comprehensive information system does not
suffer a decrease in its performance (degradation) with respect to the level prior
to being put into production.
• Technological compatibility: The software will run on the technological
platform of the new equipment that The Company “TITO” will implement.
• User interface: The software must have a final user interface entirely in a
graphical and friendly environment in all its components.

TECHNICAL ASPECTS OF OUR SYSTEM.

Database Manager to Use: Our group suggests that the database manager for this
development should be SQL Server 2005 Express and MYSQL SERVER 5.0, which
has been chosen taking into account the following evaluation criteria.
• Security . SQL Server 2005 Express and MYSQL Server 5.0 implement a level
of security 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 attempts to save when making a
transaction.
• Database synchronization . The replication process requires database
synchronization, for which SQL Server 2005 Express guarantees through
transactional or instantaneous synchronization depending on the functionality of
the branch.
• Data capacity : SQL SERVER 2005 Express and MYSQL SERVER 5.0
Supports up to terabytes of information, that means great data capacity and
benefit for the company.
• User concurrency . The system proposed to the Company "TITO" will be
implemented in a client-server architecture with simultaneous concurrence of
the different points of sale, this implies that the database manager guarantees
this functionality since the company tends to grow and the level attendance
could be higher.
• Informatic support . Currently Microsoft is the largest company in the world
and computer support for its products is unlimited.
Integrated Development Environment (IDE) tool to use: Our group proposes that
the integrated development tool for this development should be JBUILDER, which has
been chosen taking into account the following evaluation criteria:
• JBUILDER is an integrated development environment specially designed to
facilitate the construction and development of Web and desktop services and
solutions.

9
Among its many features, it is worth highlighting its multi-language support, which
allows code written in different programming languages to be integrated into the same
application.

• Security.- JBUILDER makes it easier for developers to write secure

applications. You can write secure unmanaged code or obtain IDE tools that
allow you to create and deploy managed applications that use Code Access
Security (CAS).
• Interface design using swing library in JAVA.
• Integration with JAVA RUNTIME.
• Creating console applications
• Other features to highlight are: an integrated development environment, a
complete debugger, Crystal Reports or an HTML design wizard

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

GENERAL CHARACTERISTICS OF THE INFORMATION SYSTEM.

The information system to be developed must allow the safe and efficient automation
of all operational processes, the optimization of the use of company resources, the
consolidation and presentation of information to support decision making at all levels.
management, allowing, among other things, information to be made that facilitates
management analysis.

The system to be implemented will have the following general technical characteristics:
• The system will work on the Windows 2000/NTWs/95/98/XP platform and
Ubuntu 9.10 free software (this is because the platforms that the company is
going to consider using, both in hardware and software resources, are taken
into consideration. basis for the information system).
• It will have a friendly graphical interface between the system and the user.

• The system to be implemented is Client/Server type and will use the database
engine relating 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, exporting the information in the form of files for
use or consultation with Spreadsheets, Word Processors, Flat Files and/or
others. .
• The system will provide reports, either by screen, printer or file.
• The system will allow the consolidation of information, including data
transmission mechanisms: manual and automatic.

1
0
• The system will be developed in JAVA ECLIPSE/SQL SERVER 2005
EXPRESS AND MYSQL SERVER 5.0.
• Automatic generation and printing of pre-designed documents in the system.
• Historical information management.

1
1
Returning to the example of the TITO company, below we see how to complete the
steps regarding numeral VI on project management for a software development
proposal.

IV. PROJECT MANAGEMENT.

4.1 Project Estimates

Below is the economic proposal for the execution of this project.

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

4.1.2. Software.
ITEM DESCRIPTION AMOUNT PRICE TOTAL
1 Analysis, design, implementation of 1 9000.00 9000.00
the “Sales and services control
system of the TITO Company”

TOTAL 9000.00

4.1.3. Hardware.
ITEM DESCRIPTION AMOUNT PRICE 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. Summary.

ITEM TOTAL
Licenses 3002.00
Software 9000.00

1
2
 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 cost structure presented:

• Licenses : This item indicates the licenses that the “TITO” Company must acquire
to build the software. The acquisition of these licenses is proposed because the
Source Code of the Application (from 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 of software

development is indicated, the same as the disbursement is proposed to be in
equal monthly installments. ($2,000.00), which includes all taxes established by
the pertinent legal regulations, which will serve us for expenses during almost the
entire development of the System.

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

construction of the software, because these will provide greater ergonomic
features that will make it possible to take full advantage of the characteristics of
said machines and speed up the construction of the System.

• Others : Multiple expenses incurred throughout the development of the project are
taken into account, such as payment for electricity consumption, CDs, computer
rental, printing of documentation, sheets, some last minute inconveniences and
other expenses.

4.2 Project Plan

1
3
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 the distribution of times and
the number of iterations for each phase (for the Construction and Transition phases it is
only a very preliminary approximation)

PHASE NO. ITERATIONS DURATION

Startup Phase 1 4 weeks

Preparation 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 PHASE
In this phase you will develop the necessary requirements of
the product from the user's perspective, which will be
established in the Requirements Capture artifact. The main
Startup Phase use cases will be identified and a refinement of the Project
Development Plan will be made. Client/user acceptance and
the Development Plan mark the end of this phase.

In this phase, the requirements are analyzed and an

architecture prototype is developed (including the most
relevant and/or critical parts 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 Construction phase
must be analyzed and designed (in the Analysis / Design
Model).

Preparation Phase The review and acceptance of the system architecture

prototype marks the end of this phase. The first iteration will
have as its objective the identification and specification of the
main use cases, as well as its preliminary implementation in
the Analysis / Design Model, it will also allow a general review
of the state of the artifacts up to this point and adjust if
necessary the planning to ensure compliance with objectives.
Both iterations will last weeks.

1
4
 During the construction phase, all use cases are analyzed and
designed, refining the Analysis/Design Model. The product is
built based on 2 iterations, each one producing a version to
which tests are applied and validated with the client/user.
Phase of
Construction
The development of user support material begins. The
milestone that marks the end of this phase is the release of
the version, with the partial operational capacity of the product
that has been considered critical, ready to be delivered to
users.
In this phase, two versions will be prepared for distribution,
ensuring adequate implementation and change of the previous
system.

Transition Phase The milestone that marks the end of this phase includes the
delivery of all project documentation with installation manuals
and all user support material, and the completion of user
training.

4.2.2 Project Schedule: Below is a schedule of the main tasks of the project including
only the Initiation and Preparation phases. As mentioned, the iterative and incremental
process of RUP (Rational Unified Process) is characterized by the parallel execution of
all development disciplines throughout the project, with which most of the artifacts are
generated very early in the project. project but are developed 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 approval date indicates
when the artifact in question has a sufficient state of completeness to undergo review
and approval, but this does not preclude the possibility of its subsequent refinement and
changes.

DISCIPLINES/ARTIFACTS
GENERATED OR MODIFIED DURING BEGINNING APPROVAL
THE START-UP PHASE

BUSINESS MODELING

1
5
 Business Use Case Model and Week 1 01/10 – 07/10 Week 3 10/15 – 10/21
Business Object Model
REQUIREMENTS

Glossary
Week 2 10/08 – 10/14 Week 3 10/15 –10/21

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

Week 6 and 7 10/04 –

Analysis/Design Model next phase
11/18

next phase
Data model Week 8 11/19 – 11/25

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

1
6
 Atmosphere Throughout the project

4.4 Project Monitoring and Control

4.4.1 Revision history

VERSION DATE DESCRIPTION

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

2.0 24/10/2009 Version proposed for approval at the end of the initiation
phase.

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

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

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

phase.

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

construction phase.

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

For the review of each artifact and its corresponding quality assurance, the review guides
included in RUP will be used.

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

RISKS CONTINGENCY ACTIONS

1
7
 1. Low intensity of Electrical Energy, and 1. Save the information being handled at
advanced information and our entire all times, taking into account security
System are lost, or it has some failures at aspects.
the time of testing.

2. Loss of information in the database. 2. Make a backup copy from time to time,
as the project progresses.

3. They are treated with care,

maintenance is carried out regularly, the
3. Loss of advanced information due to
loan of other equipment is planned.
computer damage, equipment failure.

To fire, which can destroy equipment and In general, an almost daily copy is made
files. of the files that are vital to the company.

To common theft, taking equipment and Common theft, entrance doors and
files. windows are closed.

To the action of viruses, which damage All incoming software is scanned on a

computers and files. system using antivirus software.

V ANNEXES

The annexes include the data flow diagrams, glossary and other parts that cannot be
located within the body of the proposal. These annexes fulfill the function of
complementing the information that is to be made known to comply with the development
of the project.

1
8