<Nombre del proyecto> Version: 0.

9
Vision Date: dd/mm/yyyy
Vision Document

Library System
Software Development Plan
Version 0.9

Confidential Ó<Company Name>, 2021 Page 1 of 13

<Nombre del proyecto> Version: 0.9
Vision Date: dd/mm/yyyy
Vision Document

Revision History
Date Version Description Author
02/01/2002 0.9 Preliminary version as a proposal by Patricio Letelier Torres
development.

Confidential Ó<Company Name>, 2021 Page 2 of 13

<Nombre del proyecto> Version: 0.9
Vision Date: dd/mm/yyyy
Vision Document

Table of Contents
1. Introduction4

1.1 Purpose4
1.2 Scope4
1.3 Summary4

2. Project Overview5

2.1 Purpose, Scope and Objectives5

2.2 Assumptions and Constraints5
2.3 Project deliverables5
2.4 Evolution of the Software Development Plan7

3. Project Organization7

3.1 Participants in the Project7

3.2 External Interfaces.........................................................................................................................................8
3.3 Roles and Responsibilities8

4. Process Management8

4.1 Project Estimates8

4.2 Project Plan8
4.2.1 Plan of the Phases9
4.2.2 Project Calendar10
4.3 Project Monitoring and Control13

5. References13

Confidential Ó<Company Name>, 2021 Page 3 of 13

<Nombre del proyecto> Version: 0.9
Vision Date: dd/mm/yyyy
Vision Document

Software Development Plan

1. Introduction
The project has been requested by Rolando Jimenez based on a Scrum methodology.. It is important
highlight this since we will use SCRUM terminology in this document.

1.1 Purpose
The purpose of the Software Development Plan is to provide the necessary information to control the
project. It describes the software development approach.
The users of the Software Development Plan are:
The project manager uses it to organize the agenda and resource needs, and to carry out his
follow-up.
The development team members use it to understand what they need to do, when they need to.
do it and what other activities depend on it.

1.2 Scope

The Software Development Plan describes the overall plan used for the development of the 'System for
Library Management.” For version 1.0 of the Software Development Plan, we have based ourselves on the
requirements gathering through the stakeholders of the company and/or institution to make a
estimated resource approximation, once the project has started. Subsequently, the progress of
project and the follow-up in each of the iterations will cause the adjustment of this document
producing updated new versions.

1.3 Summary
After this introduction, the rest of the document is organized into 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 the costs and estimated planning, defines the phases and milestones of the project and
describe how its follow-up will be carried out.
Planes y Guías de aplicación — proporciona una vista global del proceso de desarrollo de software,
including methods, tools, and techniques that will be used.

2. Project Overview
2.1 Propósito, Alcance y Objetivos

The information that is included below has been extracted from the different meetings that have taken place.
celebrated with the client who requested the system from the beginning of the project, Rolando Jimenez.

Confidential Ó<Company Name>, 2021 Page 4 of 13

<Nombre del proyecto> Version: 0.9
Vision Date: dd/mm/yyyy
Vision Document

The library management system carries out the management of the library at the Bolivian University.
Computer science. Entering a competitive market like the one the university is immersed in.
it will entail a predictable adaptation to new information systems and technological evolution. For
Hello, it is considered necessary to develop a new library management system that allows for a
faster, automatic, and secure management of loans, purchases, and returns of material
bibliographic.
The project must provide a proposal for the development of all subsystems or modules.
involved in the management of the library. The following subsystems are in place:
a) Module of bibliographic material, including:
Procedure for the registration of bibliographic material.

Procedure for modifying bibliographic material data.

Procedure for the removal of bibliographic material.
b) Module for reserving bibliographic material, including:
Search for bibliographic material.
Reservation of bibliographic material.
c) Módulo de préstamo de material bibliográfico, incluyendo:
Recording of loans of bibliographic material.
d) Module for borrowing bibliographic material, including:
Record of bibliographic material return.

2.2 Assumptions and Restrictions

The assumptions and constraints regarding the system, which directly arise from the interviews with
the client who requested the system is:
a) The implications of the following critical points must be considered:
Hire a domain and hosting
Multilingual characters
Secure systems: information protection, security in data transmissions, etc.
For the registration of books, the nomenclature used by the library will be respected.

2.3 Project deliverables

The following are indicated and described each of the artifacts that will be generated and used by the
project and which constitute the deliverables.

1) Software Development Plan

This is the present document.

2) Specification of requirements

This document defines the product vision from the customer's perspective, specifying the
needs and characteristics of the product. It constitutes a basis of agreement regarding the requirements

Confidential Ó<Company Name>, 2021 Page 5 of 13

<Nombre del proyecto> Version: 0.9
Vision Date: dd/mm/yyyy
Vision Document

of the system.

3) Additional Specifications

This document will capture all the requirements that have not been included as part of the cases of
they refer to global non-functional requirements. Such requirements include: legal requirements or
standards, application of standards, product quality requirements, such as: reliability,
performance, etc., or other environmental requirements, such as: operating system, requirements of
compatibility, etc.

4) Model of Analysis and Design

This model establishes the implementation of use cases in classes and moving from a representation
in terms of analysis (excluding implementation aspects) towards a design (including a
orientation towards the implementation environment), according to the progress of the project.

5) Data Model

Anticipating that the persistence of the system information will be supported by a database
relational, this model describes the logical representation of persistent data, according to the
approach for relational data modeling. To express this model, an Entity Diagram is used.
relationship and the relational diagram with its respective data dictionary

6) Implementation Model

This model is a collection of components and the subsystems that contain them. These components
includes: executable files, source code files, and any other type of files necessary for the
implementation and deployment of the system. (This model is only a preliminary version at the end of the phase
of Preparation, later it has quite a lot of refinement).

7) Deployment Model

This model shows the deployment of the system node type configuration, in which it will be done
the deployment of the components.

8) Test Cases

Each test is specified by a document that establishes the execution conditions, the
test inputs, and the expected results. These test cases are applied as tests of
regression in each iteration. Each test case will be associated with a test procedure with the
Instructions for taking the test, and depending on the type of test the procedure may be
automatable through a test script.

9) List of Risks

This document includes a list of the known and ongoing risks in the project, ordered by
decreasing order of importance and with specific contingency actions or for their mitigation.

10) Installation Manual

This document includes the instructions for installing the product.

Confidential Ó<Company Name>, 2021 Page 6 of 13

<Nombre del proyecto> Version: 0.9
Vision Date: dd/mm/yyyy
Vision Document

11) User Support Material

It corresponds to a set of documents and usability features of the system, including: Guides of
User, Operation Guides, Maintenance Guides and Online Help System

Product

The product files packed and stored on a CD with the appropriate mechanisms for
facilitate its installation. The product, from the first iteration of the Construction phase is
developed incrementally and iteratively, obtaining a new release at the end of each iteration.

The artifacts 19, 20, and 21 will be generated from the Construction phase, which is why they have been included.
here only to provide an overview of all the artifacts that will be generated in the process of
development.

2.4 Evolution of the Software Development Plan

The Software Development Plan will be reviewed weekly and refined before the start of each.
iteration.

3. Project Organization
3.1 Participants in the Project
Project Manager.
Work of César López Rodríguez, student of the sixth semester of the Systems Engineering career at the
Bolivian University of Informatics. With a modest experience in development methodologies,
CASE tools and notations, particularly UML notation and the SCRUM methodology. Also
will carry out the tasks of: requirements management, configuration management, documentation, and data design
Systems Analyst.
The established profile is: Systems Engineer with knowledge of UML, at least one of them with
experience in systems related to the line of the project, work that will be carried out by José Luis Martínez Herrero.
Systems Developer.
With experience in the project development environment, in order for the prototypes to be as
close to the final product. This work has been entrusted to Miguel Antonio Mascilla Guzmán,
Germán Mira Rico, José Antonio Mocholí Agües and Eduardo Bueno Medina.
Tester
The established profile is: Recently graduated Systems Engineer who will participate in the project, carrying out
labores de pruebas funcionales del sistema. Realizará la labor de Tester Rosa María Ogallar Verjillos.

3.2 Roles and Responsibilities

Below are the main responsibilities of each position in the team.
development during the Initiation and Elaboration phases, according to the roles they play in RUP.

Position Responsibility

Confidential Ó<Company Name>, 2021 Page 7 of 13

<Nombre del proyecto> Version: 0.9
Vision Date: dd/mm/yyyy
Vision Document

The project manager assigns resources, manages priorities, coordinates

the interactions with customers and users, and keeps the team of
project focused on objectives. The project manager also establishes
a set of practices that ensure the integrity and quality of the
Project Manager
project artifacts. In addition, the project manager will be responsible for
supervise the establishment of the system architecture. Management of
risks. Project planning and control. Requirements management,
configuration and change management
Capture, specification, and validation of requirements, interacting with the
client and users through interviews. Development of the Model of
Systems Analyst
Analysis and Design. Collaboration in the preparation of tests
functional and the data model.
Prototype construction. System development. Collaboration in the
Developer of
development of functional tests, data model and in the
Systems
validations with the user

Preparation of functional tests, elaboration of documentation.

Tester
Develop implementation and deployment models.

4. Process Management

4.1 Project Estimates

El presupuesto del proyecto y los recursos involucrados se adjuntan en un documento separado.

4.2 Project Plan

This section presents the organization into phases and iterations and the project timeline.

4.2.1 Phase Plan

The development will take place based on phases with one or more iterations in each of them. The following
The table shows the distribution of times and the number of iterations for each phase (for the phases of
Construction and Transition is only a very preliminary approximation.

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

Description Person

Start Phase In this phase, they will develop the product requirements from the
user perspective, which will be established in the artifact
Requirements specification. The main use cases will be
identified and a refinement of the Development Plan will be made
Project. The acceptance of the customer/user of the artifact
Requirements specification and the Development Plan mark the

Confidential Ó<Company name>, 2021 Page 8 of 13

<Nombre del proyecto> Version: 0.9
Vision Date: dd/mm/yyyy
Vision Document

end of this phase.

Phase of In this phase, the requirements are analyzed and a prototype is developed.
Preparation architecture (including the most relevant and/or critical parts of
system). At the end of this phase, all the corresponding use cases
requirements that will be implemented in the first release of the phase of
Construction must be analyzed and designed (in the Model of
Analysis / Design). The review and acceptance of the prototype of the
system architecture marks the end of this phase. In our case
in particular, for not including the following phases, the review and delivery of
all artifacts up to this point in development are also included
as a milestone. The first iteration will aim to identify
and specification of the main use cases, as well as their
preliminary realization in the Analysis / Design Model, also
It will allow for a general review of the status of the artifacts until
this point and adjust the planning if necessary to ensure the
achievement of the objectives.

Confidential Ó<Company Name>, 2021 Page 9 of 13

<Nombre del proyecto> Version: 0.9
Vision Date: dd/mm/aaaa
Vision Document

Phase of During the construction phase, analysis and design are completed.
Construction all use cases, refining the Analysis / Design Model. The
the product is built on the basis of 2 iterations, each producing
a release to which tests are applied and validated with the
client / user. The preparation of support material begins for
user. The milestone that marks the end of this phase is the version of the
release 2.0, with the partial operational capability of the product that is
has been considered as critical, ready to be delivered to the users
for beta testing.

Transition Phase In this phase, two releases will be prepared for distribution, ensuring
an implementation and change of the previous system in an appropriate manner,
including user training. The milestone that marks the end
this phase includes the delivery of all the documentation of
project with the installation manuals and all the supporting material
to the user, the completion of user training and the
product packaging.

4.2.2 Project Calendar

For this project, the following schedule has been established. The approval date indicates when the artifact in
the issue has a sufficient state of completeness to be submitted for review and approval, but this does not remove the
possibility of its later refinement and changes.

Module or task to be performed Start Date Fecha Fin Duration (days)

Bibliographic material module that allows registration,

modify and cancel books, magazines, theses, etc.
03/10/2016 14/10/2016 10
Module design document 03/10/2016 04/10/2016 2
Cover page of the module 05/10/2016 07/10/2016 3
Business cover of the module 10/10/2016 12/10/2016 3
Database access layer of the module 13/10/2016 14/10/2016 2
Web-based bibliographic material reservation module or
in the library 15/10/2016 25/10/2016 9
Module design document 15/10/2016 16/10/2016 2
Presentation cover of the module 17/10/2016 18/10/2016 2
Business module cover 19/10/2016 20/10/2016 2
Database access layer of the module 21/10/2016 25/10/2016 3
Bibliographic material loan module 26/10/2016 04/11/2016 8
Module design document 26/10/2016 26/10/2016 1
Cover page of the module 27/10/2016 28/10/2016 2
Business cover of the module 31/10/2016 02/11/2016 3
Database access layer of the module 03/11/2016 04/11/2016 2

Confidential Ó<Company Name>, 2021 Page 10 of 13

<Nombre del proyecto> Version: 0.9
Vision Date: dd/mm/yyyy
Vision Document

4.2.3 Gantt Diagram

Confidential Ó<Company Name>, 2021 Page 11 of 13

<Nombre del proyecto> Version: 0.9
Vision Date: dd/mm/aaaa
Vision Document

5. 4.2.4 Estimation of human resources

Phase Roll Cantidad Fecha inicio Fecha fin de Estimación

of of availability hours in
people's availability phase
assigned
to the role

Start Analyst 1 01/05/2020 07/05/2020 56

systems
Start Boss of 1 01/05/2020 07/05/2020 56
project
Preparation Analyst 1 08/05/2020 25/05/2020 86
systems
Construction Developer 1 28/05/2020 28/06/2020 240
of systems
Transition Developer 2 28/05/2020 28/06/2020 240
of systems
Transition Tester 1 01/06/2020 08/07/2020 480
Production Analyst 1 15/07/2020 18/07/2020 40
systems

4.2.5 Estimation of software resources

Environment software type Date Fecha fin Precio

start of the
available available
dad dad
Software tools Visual Studio 05/24/2020 06/28/2020 4500 Bs
2010
Sql Server
2008
Hardware
Network resources
Commercial components
TOTAL

Confidential Ó<Company Name>, 2021 Page 12 of 13

<Nombre del proyecto> Version: 0.9
Vision Date: dd/mm/yyyy
Vision Document

5.1 Project Monitoring and Control

Requirements Management
The system requirements are specified in the Requirements Specification artifact. Each
The requirement will have a series of attributes such as importance, status, iteration where it is implemented, etc.
These attributes will allow for effective tracking of each requirement. Changes in the requirements
they will be managed through a Change Request, which will be evaluated and distributed for
ensure the integrity of the system and the proper management of configuration and change processes.
Deadline Control
The project calendar will have weekly monitoring and evaluation by the project manager.
Quality Control
The defects detected in the reviews and formalized also in a Change Request will have a
follow-up to ensure compliance regarding the solution of these deficiencies for the review of
each artifact and its corresponding quality assurance will use the review guides and checklists
of verification) included in RUP.
Risk Management
From the Start phase, a list of risks associated with the project and the actions will be maintained.
established as a strategy to mitigate them or contingency actions.

6. References
List of risks
Test plan

Confidential Ó<Company name>, 2021 Page 13 of 13