Gabriel Rene Moreno Autonomous University.

Faculty of Technology

Master's in Software Engineering

Software Project Management Plan.

(PAPS)

Integrated information system for managing operations in the area of

marketing, inventories, and human resources for the National Chain of

FarmaCorp Pharmacies.

Module Introduction to Software Engineering

Teacher Ing. José Antonio Benavente B.
Student Ing. Ernesto Soto Roca.

Santa Cruz - Bolivia

 Software Project Management Plan

TABLE OF CONTENTS
Software Project Administration Plan................................................... 1
1.1. Introductionn ............................................................................................................. 7
1.2. Backgrounds ............................................................................................................ 8
1.3. Planteamiento of the problem. 9
1.3.1. Situation Problematica ..................................................................................... 9
1.3.2. Situation Desired. 12
1.4. Delimitaciones ....................................................................................................... 12
1.5. Objectives ................................................................................................................ 12
1.5.1. Objetivo General. 12
1.5.2. Objetivos Specifics. 12
1.6. Justificación ........................................................................................................... 13
1.6.1. Justification Theoretical. 13
1.6.2. Justification Methodological. 13
1.6.3. Justificación Practicea ...................................................................................... 13
1.7. Design Methodological. 14
1.7.1. Type of Research. 14
1.7.2. Processes Methodologicals ................................................................................. 14
1.7.3. Methods .......................................................................................................... 15
1.7.4. Técnicas for information collection. 15
[Link]. Sources Primaries:....................................................................................... 15
[Link]. Sources Secondary schools:................................................................................... 15
1.7.5. Resources useds ......................................................................................... 15
1.8. Scope .................................................................................................................. 16
1.8.1. Requirements functional. .............................................................................. 16
1.8.2. Requirements non-functional. ........................................................................ 18
[Link]. Specifications Supplementary. 18
[Link]. Time of learning. 18
[Link]. Identification of the user's own application.. 18
[Link].1. User passwordo ................................................................................. 19
[Link]. Confiabilidad .................................................................................................. 19
[Link].1. System availability time. 19
[Link].2. Time between failures. 19
[Link].3. Downtime. 19
[Link].4. Event registrations ..................................................................................... 20
[Link]. Performance. 20
[Link].1. Online customer access. 20
[Link].2. Response time. 20
[Link].3. Amount of user attention. 20
[Link]. Portability Maintenance Ease. 20
[Link].1. Update transparent to the user. 20
[Link]. Standards of decoding. 20
[Link]. Restrictions of Design. 20
[Link].1. Design Standardso ................................................................................... 20
[Link].2. Architecture standards. 21

2
 Software Project Management Plan

[Link]. Motor databases ................................................................................... 21

[Link]. Client of the navigatedr ..................................................................................... 21
[Link]. Server Web. 21
[Link]. Language of programming. 21
[Link]. Requirements of documentation, online help and manuals, assistance
technique. 21
[Link].1. Manual User. 21
[Link].2. Help online. 21
[Link].3. Guides Installation and Configuration. 21
[Link].4. Support Technician. 21
[Link]. Interfaces ........................................................................................................ 22
[Link].1. Interface of user ...................................................................................... 22
[Link].2. Interface of Hardware. 22
[Link].3. Interface of Communications. 22
[Link].4. Interfaces of Software. 22
[Link]. Requirements of Licenses. 22
[Link]. Legal, Copyright and Other Notes. 23
[Link]. Standards Applicable. 23
[Link]. Installation In Motion. 23
1.9. Metrics. ................................................................................................................ 24
1.9.1. Metrics size-oriented. 24
[Link]. Data project management historical records. 24
1.9.2. Metrics function-oriented. 24
1.10. Estimates. 25
1.10.1. Estimates based on lines of code. 25
1.1.1. Estimates COCOMO. (COnstructive COst MOdel). 27
1.1.2. Estimates Function point based.. 29
Fuente: Elaboración propia............................................................................................... 29
Source: Self-made. 30
1.2. Analysis of Risk.. 31
Source: Own elaboration. 32
1.2.1. Planning of the risk.. 33
Source: Own preparation. 36
1.2.2. Analysis on the consequences of risk. 37
Source: Self-made. 38
Source: Own elaboration. 40
1.2.3. Analysis from the obtained data:........................................................................... 41
1.3. Planning Temporal. 41
1.3.1. Identification of tasks : .................................................................................... 41
Source: Own elaboration. 41
1.3.2. Diagram of Gantt. 42
1.3.3. Diagrama of network. 43
[Link]. Phase to starto .................................................................................................. 43
Source: Own elaboration. 43
[Link]. Phase of preparation. 44
Source: Own elaboration. 44
Phase under construction. 45

3
 Software Project Management Plan

Source: Own elaboration. 45

[Link]. Phase of transition.. 46
Source: Own elaboration. 46
1.4. Organization Internal. 47
1.4.1. Structure. .......................................................................................................... 47
Source: Own preparation. 47
1.4.2. Paradigm of the organization.. 47
1.4.3. Organización of the team. 47
1.5. Resources. 48
1.6. Recursos Humans.. 48
1.7. Equipos: ................................................................................................................. 48
1.8. Costo of the Projecto ................................................................................................. 48
ANNEXO .49
ANNEX A-01. ........................................................................................................ 50
Model for business. 50
2. ANNEX A-02. ................................................................................................. 53
a. Model of requirement. 53
3. ANNEX A-03. .57
a. Model of analysis. .................................................................................................... 57

TABLE OF ILLUSTRATIONS
Illustration 1: Problematic Situation. 11
Illustration 2: Identification of local infrastructure. 22
Illustration 3: Network diagram start phaseo ....................................................................... 43
Illustration 4: Network diagram preparation phase. 44
Illustration 5: Network diagram construction phase. 45
Illustration 6: Network diagram transition phase.. 46
Illustration 7: Business Process Manage Supplier Orders. 50
Illustration 8: Business process management of returns to suppliers. 51
Illustration 9: Business process for managing the company's internal orders ................. 52
Illustration 10: Functional use case diagram for the inventory moduleo ......................... 53
Illustration 11: Administrative Use Case Diagram of the System. 54
Illustration 12: Administrative Use Case Diagram of the System. 55
Illustration 13: Functional use cases of the sales system. 56
Illustration 14: class diagram of inventory system analysiso ................................... 57
Illustration 15: sales module analysis class.. 58

4
 Software Project Management Plan

PAYROLL TABLE
Table 1 Estimation of lines of code. 25
Table 2: Staff list. 26
Table 3: Information domain valuesn ...................................................................... 29
Table 4: Adjustment values of complexityd.......................................................................... 29
Table 5: Payroll sheet. 30
Table 6: Initial Risk Listing. 32
Table 7: Contingency plan. 36
Table 8: Risk Assessment. 38
Table 9: Risk Assessment. 40
Table 10: Task Identification. 41
Table 11: Organic structure of the equipmento ............................................................................. 47
Table 12: Controlled decentralized model. 47

5
 Software Project Management Plan

Software Project Management Plan

PAPS

6
 Software Project Management Plan

1.1. Introduction
The present document is a Software Project Administration Plan (PAPS).
For the development of an integrated information system for operations management in the
marketing area, inventory, and human resources for the National Chain of
FarmaCorp Pharmacies.
FarmaCorp, National Pharmacy Chain is a Business Unit of the group
NEXOCORP, a company dedicated to the marketing of pharmaceutical products and
mass consumption, with more than 70 years in the Bolivian market.
Metrics and estimation of the project are carried out, and potential risks are managed.
project development. With these elements, the costs and the duration that it will have are defined.
product.
This chain has an Internal Regulation and specific Function Manuals according to
the role, as well as policies and regulations for the internal control of each branch. He wants
to have a modern high-tech computerized system that allows communication
between branches at the national level, technology that is also used in the sale of products
and services, management and control of inventories.

7
 Software Project Management Plan

1.2. Background

FarmaCorp, National Pharmacy Chain is a Business Unit of the group.

NEXOCORP business, dedicated to the commercialization of pharmaceutical products and
mass consumption, with more than 70 years in the Bolivian market. The product offer to its
clients are varied, from pharmacists, medical supplies, to personal care,
cosmetics, dietary supplements, and others. As of today, it has 44 branches.
throughout the country, of which 33 branches are located in the department of
Santa Cruz, 6 in Cochabamba, 2 in the city of La Paz, 2 branches in the department
from Tarija and 1 in Oruro. FarmaCorp is an innovative company that works day by day with
Advanced Technology, International Standards, and Excellent Management,
continuously implements new ways of updating, providing training
permanent to all its administrative and operational staff, in customer service techniques,
pharmacological, management of modern operational programs and others; that has made it
worthy of several recognitions for its optimal development and efficient attention to the
clients. The staff of FarmaCorp is made up of a team of highly skilled professionals
trained and motivated, ensuring qualified human resources,
Bachelor's degree training in Pharmacy and Biochemistry, as well as at the level of
Higher Technician.1

1
[Link]

8
 Software Project Management Plan

1.3. Statement of the problem

1.3.1. Problematic Situation
Pharmacies operate 24 hours in three shifts seven days a week. The shifts of
7:00 a 15:00 y de 15:00 a 23:00 trabajan a puertas abiertas, mientras que el turno nocturno
from 11:00 PM to 7:00 AM at the closed door through the window.
During open house shifts, there are at least 4 sellers per branch. And it has a
regent who administers and supervises the work. Product orders (medications and
others) are formulated any day at the central office according to stock control. The point
replenishment is defined by the manager, as well as the quantity to request. The central office
consolidate the order from all branches, after checking stock in warehouses and
place the purchase order to the suppliers. The replenishment and supply of the
Products are delivered to the branches every day using the vehicles available.
company, however they fail to meet the demands and requests of the branches. A
way to attract customers and retain them, there is a record of customers (buyers) and
For each boliviano sold to customers, one point is considered accumulated. Therefore,
points can be accumulated until redeemed by the customer according to the catalog of
offers, at the moment the customer requires it. The catalogs of offers are prepared that
these are products (medications and others) on promotion, which are offered every month. They are
products of all kinds (cosmetics, hygiene, etc.) among which are also considered
those that are not sold or are about to expire.
On the other hand, raffles are held for holidays (Father's Day, Mother's Day, Christmas,
etc.) for which the customer can access coupons for the purchase of products. For each
Bs. 100.- the customer is entitled to a coupon for said contest. The prizes are varied.
from passages and paid vacations to vehicles. Within the functionalities
the following is obtained for the requested software product:
It is required to keep a record of the products (medications and others) that come in from each
supplier to the warehouses, and from there to the branches. These are sold to each customer,
way to control the stock at all times, in warehouses and branches.

9
 Software Project Management Plan

It is required to keep a record of the purchase volumes from suppliers and the payments.
made and the payments to be made according to the negotiation with each
supplier.
An invoice needs to be issued for the sale of medications to customers, keeping a
record of the sales value of the products. Also keep a record of the
points accumulated for purchases made by customers.
It is required to keep a record of customers, assigning them a code that will be their CI.
Through the purchases they make, to grant a bonus after a certain amount of
points accumulated.
It is required to keep a record of the points redeemed by customers and the catalogs of
offer.
The system must maintain a record of the staff working in the branches and the main office.
and warehouses. Allowing for personnel management, making assignments of
shifts, permits, vacations, etc.
The system must manage payroll for the staff, considering the benefits for
night shifts, holidays, public holidays and others. Also, as well as the discounts according to
correspond

10
 Software Project Management Plan

[Link]. Mind Map of the problematic situation:

Illustration 1: Problematic Situation

Source: Self-made

11
 Software Project Management Plan

1.3.2. Desired Situation

Having an integrated information system for the management of operations in the
marketing area, inventory, and human resources for the National Chain
FarmaCorp Pharmacies.

1.4. Delimitations
1.4.1. Scientific Delimitation
This information system is related to and based on the study of: Database.
Relational, Information System, Software Engineering, Process Application
Unified Development (PUD), Unified Language of Modeling (UML),
Multilayer Architecture.

1.4.2. Spatial Delimitation

FarmaCorp National Pharmacy Chain is a Business Unit of the group
business NEXOCORP. Located at Fourth Ring corner Av. Paragua north zone
with telephone 3-474808.

1.4.3. Temporal Delimitation

The software development took 14 months, starting on 03/08/2011.
1.5. Objectives
1.5.1. General Objective
Develop an integrated information system for operations management in the
marketing area, inventory, and human resources for the National Chain
FarmaCorp Pharmacies.
1.5.2. Specific Objectives
Identify the information requirements in the processes of
marketing, inventory, and human resources for the National Chain of
FarmaCorp Pharmacies.
Perform the analysis of the requirements posed as requirements

12
 Software Project Management Plan

Design the system considering the previous modules for their integration
using a layered architecture.
Implement the previously designed software components.
Conduct tests on the models and artifacts constructed.

1.6. Justificación
1.6.1. Theoretical Justification
In the development of this project, we will apply database knowledge.
relational, concepts of information systems, software engineering and
software architecture.

1.6.2. Methodological Justification

The Unified Development Process (UDP) will be used to organize the
different stages of work for the development of this project, in addition to
provide the artifacts that must be developed in the different phases. For
desarrollar los artefactos utilizaremos el Lenguaje Unificado de Modelado (UML)
to specify, build, visualize, and document the artifacts of a system
object-oriented software.
This methodology is justified because it reduces the difficulty of coordinating the multiple
etapas: Requerimiento, Análisis, Diseño, Implementación, Prueba de trabajo de un
software project.

1.6.3. Practical Justification

Contribute to the presentation of the project plan as the final work for the module
introduction to software engineering.
Likewise, deepen knowledge in the area of management and administration.
project.

13
 Software Project Management Plan

1.7. Methodological Design

1.7.1. Type of Research
A descriptive research type focused on management has been followed,
development of models and artifacts for management systems.

1.7.2. Methodological Processes

In the development of the project, the steps proposed by the life cycle will be followed.
Unified Process, due to its characteristic: Use case driven, focused on its
architecture, iterative and incremental software development, with its phases of:
Initiation, Elaboration, Construction and transition. In each of these phases, there are
five workflows: Requirements, Analysis, Design, Implementation and Testing.
The unified process uses the Unified Modeling Language (UML) to
prepare all the diagrams of an information system.
For the current project, the following phases and flows are proposed:

Illustration 1.1: Diagram of Phases and Flows

Source: IBM RUP Rational Unified Process.

14
 Software Project Management Plan

1.7.3. Methods
The methods used for the development of this project are Analysis and
Synthesis.
The Analysis to identify the causes and effects, and the Synthesis to
interrelate the systems.

1.7.4. Techniques for Information Collection

[Link]. Primary Sources:
The techniques used for data collection are:
Direct interviews with the client, the administrative manager, manager of
operations with end users and with the IT managers of the company.
[Link]. Secondary Sources:
Information gathering by specialists from the Area: External suppliers, and
internal, operation manuals, books.

1.7.5. Recursos utilizados

Below is a list of the artifacts and tools used in the
project development:
[Link]. Design Artifacts
The design artifacts used are the following:
Activity Diagram, Use Case Diagram, Class Diagram
Deployment Diagram.

[Link]. Analysis Instruments

Company procedure and operations manuals.
Statutes, pharmacy regulation law.

15
 Software Project Management Plan

1.8. Scope
1.8.1. Functional requirements.
No. Functional requirements module
1 Approve request in finance department inventory
2 Search Product inventory
3 Define system access inventory
4 Prepare product stock report inventory
5 Prepare Supplier Order Report inventory
6 Prepare Sales Order Report inventory
7 Prepare summary of orders to supplier inventory
8 Prepare sales return report inventory
9 Issue Order Receipt to Inventory inventory
10 Issue Purchase Order Receipt to Supplier inventory
11 Issue Supplier Registration Form inventory
12 Issue return report of products to inventory inventory
13 Issue the delivery receipt of the supplier's order inventory
14 Issue a receipt for the products from the inventory department inventory
15 Issue return receipt to supplier inventory
16 Issue report of returns to supplier inventory
17 Manage Legal Provider inventory
18 Manage Natural Supplier inventory
19 Manage System User Administrative
20 Manage Backus of the database Administrative
21 Manage return to supplier inventory
22 Manage employee HR
23 Return products to inventory inventory
24 Place order for products from inventory inventory
25 Make a purchase order request to the supplier inventory
26 Reception of products from the supplier for return inventory
27 Disappoint Inventory department products inventory

16
 Software Project Management Plan

28 Receive Order Request from the sales department inventory

29 Receive order from suppliers inventory
30 Warehouse Registrar inventory
31 Registrar Product Category inventory
32 Registrar ABC Classification inventory
33 Register Country inventory
34 Branch Registrar inventory
35 Register department_Section inventory
36 Register the product subcategory inventory
37 Product Registrar inventory
38 Make purchase order request to supplier inventory
39 Restore database backup inventory
40 Manage Client sales
41 Schedule Creditors on request sales
42 Place the customer's order sales
43 Registrar Forma de Pago sales
44 Registrar Coin sales
45 Registrar Rubro sales
46 Registrar Subcategory {"text":"sales"}
47 Registrar qualification sales
48 Customer point registrars sales
49 Registrar category sales
50 Product Registrar sales
51 Registrar Cargo HR
52 Generate Monthly Payroll HR
53 Manage Discounts hr
54 Manage Bonds hr
55 Manage Contributions hr
56 Manage Transaction Log Administrative
Identification of functional requirements using ANNEX A-01, ANNEX A-02 as reference
Source: Own elaboration

17
 Software Project Management Plan

1.8.2. Non-functional requirements.

[Link]. Supplementary Specifications
The Supplementary Specifications contain the system requirements that do not
are outlined in the Software Requirements document. Some of
they are:

Legal requirements and application of standards

Attributes of the quality of the system to be built, such as usability and

performance

Environment and operating system requirements, compatibility, and constraints of

design

Other requirements not included in the requirements document.

software.

[Link]. Learning time

The time it takes for users to learn 80% of the system's functionality
must be:

User load: 2 days

User inquiry: 1 day
the Administrator: 3 days

Regarding the training of FarmaCorp staff in software handling and

system maintenance should consider a considerable amount of time for it
less than 25 hours of training, until the system management guidelines and
others have been duly acquired by the previously assigned personnel.

[Link]. User identification specific to the application

The user will log into the System with their username and password, which will be validated by

the Active Directory of Windows Server 2000 or 2003.

18
 Software Project Management Plan

[Link].1. User password

For user password registration, the following must be ensured
practices:

The password must be transmitted encrypted between the client, the web server and
the database server.
The password change will be made according to the
Account and password validity policies established in Active
Directory
According to the Active Directory Policies of Windows Server
When changing a password, the new password cannot be the same as the
previous.
After three failed attempts to access the system due to a password
incorrect, that user account should be blocked. According to the
Active Directory Policies.
The password must contain letters and numbers.
The password length must be 7 characters. According to the
Active Directory Policies.

[Link]. Reliability
[Link].1. System availability time
The application must be available 24 hours a day.

[Link].2. Time between failures

Being a high availability system, it will be included during failures.
from 0 to 5h. By management.

[Link].3. Downtime
The maximum downtime depends on the functioning of the,
coders servers, data servers and the bases themselves. The same must
to be

Common failures 40 minutes (estimated)

19
 Software Project Management Plan

Uncommon failures 1 hour. (estimated)

[Link].4. Event log

The application must maintain a log of events to record the different
events that take place on the database.

[Link]. Performance
[Link].1. Online customer access
Client users must be able to access data online, in real time.

[Link].2. Response time

The response time for user access should be 5 seconds.

The response time for an average transaction should also be 15

seconds.

[Link].3. Amount of user attention

The system must be able to normally serve 100 users at the same time.

[Link]. Supportability or Ease of Maintenance

[Link].1. Transparent update to the user
The characteristic of Web technology should be leveraged so that the
application updates and patches are installed and this operation is
transparent to the user.

[Link]. Coding Standards

The registers provided by IT 'Code Development Register' must be used.
of Applications.

[Link]. Design Restrictions

[Link].1. Design Standards
The registers provided by IT "Design Register" must be used.
"Applications" in n layers with [Link] 4.0 technology.

20
 Software Project Management Plan

[Link].2. Architecture Standards

The registers provided by IT "Architecture Register" must be used.
[Link] de Microsoft”.

[Link]. Database engine

The SQL Server 2007 database engine from Microsoft must be used.

[Link]. Browser Client

The application must be accessible using the following type of browser: Internet
Explorer 7 or higher.

[Link]. Web Server

The Web server must be Internet Information Server version 6.1 or higher.

[Link]. Programming language

The application must be developed in .NET using [Link], [Link], Visual
C#.Net, and SQL derivatives with T/SQL for the SQL Server database engine
2007 service pack 3 at minimum.

[Link]. Documentation requirements, online help, and manuals,

technical assistance.
[Link].1. User Manual
Adetailed user manual must be available.

[Link].2. Online Help

The user manual must be available online.

[Link].3. Installation and Configuration Guides

There must be installation guides and manuals for the system and configuration.
of control teams.

[Link].4. Technical Support

Farmacoop will consider technical support as a priority for qualification.
local (preferably) with the system, in which case it should be indicated the
company assigned for this service, in case of emergency.

21
 Software Project Management Plan

[Link]. Interfaces
[Link].1. User interface
Agraphical interface must be available.

[Link].2. Hardware Interface

The system must interpret the readings made in the system.
support the connection with barcode printers.
[Link].3. Communication Interface
Users must have an internet connection to be able to use the
web application. Communication with the devices must be via RS-
232, RS-485, MODEM or TCP/IP.

For the Network Environment: the application must have the capability to
function with the following characteristics

oLAN Networks

IIS SERVER SQL SERVER DOMAIN SERVER APPLICATION SERVER

RED LAN

CODINES SERVER

DIAGRAM OF
INSTALLATION OF EACH CODING
HEADQUARTERS CODING
ARL9000

RED RS485 CODING

CODING CODING

CODING

Illustration 2: Identification of local infrastructure

Source: Own elaboration

. WAN networks,ADSL of 1024 MB Frame Relay 128

[Link].4. Software Interfaces
It must be designed for Windows 32 bits /98/NT/2000/Seven environment.

[Link]. License Requirements

FarmaCorp will provide the corresponding licenses for all the Software that is
requires both Servers and Clients.

22
 Software Project Management Plan

[Link]. Legal, Copyright and Other Notes

The provision of equipment, installation service and
connection of equipment to the satisfaction of FarmaCorp. The operation guarantee

The system should refer to a period not exceeding one year after the
conclusion of the work, after the signing of a
provisional delivery of the service.

The acceptance tests must be carried out under the supervision of FarmaCorp.
For this purpose, the necessary tests and measurements will be conducted to assess the proper

functioning of the entire system at the hardware and software level.

[Link]. Applicable Standards

The development of the entire project must be governed by norms and patterns defined by
the IT and Telecommunications Management of FarmaCorp-Bolivia.

These include: Security Register, Application Architecture Register,

Application Design Registry, Code Development Registry of a
Application.

[Link]. Start-up
The start-up must be carried out at the headquarters.
company, for which all historical information must be migrated
available, perform electrical and software functionality tests
(Communication).

23
 Software Project Management Plan

1.9. Métricas.
1.9.1. Size-oriented metrics.
[Link]. Historical data of management projects.
PRODUCTIVE
LIFE
PRODUCTIVITY D(PF/ E) QUALITY D U R AT I O N For 6 months how many
PRO LDC E COST P. D O C . ERRORS DEFECTS PEOPLE KLDC (KLDC/ E) (Error/KLDC) (E/Person) people

A 18000 50 7000 600 89 22 5 18 0.36 21.5866 4.944444444 10 8.333333333

B 15800 38 5000 500 120 36 3 15.8 0.415789474 28.40342105 7.594936709 12.66666667 6.333333333
C 22000 45 9000 900 75 40 6 22 0.488888889 23.98511111 3.409090909 7.5 7.5
D 21200 52 15000 700 36 30 7 21.2 0.407692308 20.75634615 1.698113208 7.428571429 8.666666667
Average productivity (LDC) 0.41809266823.6828696
Average productivity (PF)
1.9.2. Function-oriented metrics
Weighting factor: COMPLEXITYADJUSTMENTFACTOR
Weighting factor Valoresdeajustedecomplejidad:0esnoinfluencia,1esincidental,2esmoderado,3esmedio,4essignificativoy5esesencia
1. Does the system require reliable backup and recovery? 5
Parameter Count SimpleComplex Subtotal
Number of user entries 56 3 4 6 224 2. Does it require data communication? 5
Numberof userexits 38 4 5 7 266 3. Are there distributed processing functions?
Number of requests for 15 3 4 6 60
2
Number of files 35 7 10 15,350 4. Is the performance critical? 3
Number of external interfaces 1 5 7 10 7 5. Will the system run in an existing and heavily used operating environment? 4
TotalCount
Ct 6. Does it require interactive data input? 3
907
7. Does the interactive data entry require that input transactions take place on multiple levels? 4
User entries. They are entries that provide different data to the application. Do not confuse them with user requests. 8. Are the master files updated interactively? 3
[Link],screens,[Link]. 9. Are the inputs, outputs, files, or requests complex? 2
User requests. It is an interactive entry that generates some response from the software in the form of interactive output. 10. Is internal processing complex? 3
Files. They are the files that can be part of a database or independent. 11. Has the code been designed to be reusable? 5
External interfaces. They are the files used to transmit information to another system. 12. Are conversion and installation included in the design? 5
13. Has the system been designed to support multiple installations in different organizations? 5
14 Has the application been designed to facilitate changes and to be easily used by the user? 5
∑[Link] 54
fi

PF = 1079.33 With this data, we update the historical average productivity data (PF).

24
 Software Project Management Plan

1.10. Estimates.
1.10.1. Estimates based on lines of code.
No. Requirement Sopt Smp SPess VE KLDC.
1 Approve request in the finance department 100 125 150 125 0.125
2 Search Product 90 95 120 98.33 0.098
3 Define system access 100 105 130 108.3 0.108
4 Prepare a product stock report 70 80 105 82.5 0.083
5 Prepare Supplier Order Report 75 90 105 90 0.09
6 Prepare Sales Order Report 70 87 105 87.17 0.087
7 Prepare summary of orders to supplier 60 95 105 90.83 0.091
8 Elaborar informe de devoluciones de venta 55 90 105 86.67 0.087
9 Issue Order Receipt to Inventory 60 100 105 94.17 0.094
10 Issue Order Receipt to Supplier 55 80 105 80 0.08
11 Issue Supplier Registration Form 55 80 105 80 0.08
12 Issue a record of return of products to inventory 55 80 105 80 0.08
13 Issue certificate of receipt of supplier's order 58 82 105 81.83 0.082
14 Issue receipt for products from the inventory department 55 80 105 80 0.08
15 Issue a return receipt to the supplier 55 80 105 80 0.08
16 Issue return report to supplier 55 80 105 80 0.08
17 Manage Legal Supplier 90 105 130 106.7 0.107
18 Manage Natural Supplier 80 105 130 105 0.105
19 Manage System User 83 105 130 105.5 0.106
20 Gestionar Backus de la base de datos 77 105 130 104.5 0.105
21 Manage return to supplier 80 105 130 105 0.105
22 Manage Employee 80 105 130 105 0.105
23 Return products to inventory 100 130 160 130 0.13
24 Place order for products from inventory 110 135 160 135 0.135
25 Make purchase order request to supplier 120 145 170 145 0.145
26 Reception of products from the supplier for return 100 125 150 125 0.125
27 Disappoint Inventory Department Products 80 105 130 105 0.105
28 Receive Order Request from the sales department 80 105 130 105 0.105
29 Receive order from suppliers 100 130 160 130 0.13
30 Warehouse Registrar 110 135 160 135 0.135
31 Registrar Product Category 120 145 170 145 0.145
32 Registrar ABC Classification 100 125 150 125 0.125
33 Registrar Country 80 105 130 105 0.105
34 Branch Registrar 80 105 130 105 0.105
35 Registrar department_Section 100 130 160 130 0.13
36 Register the product subcategory 110 135 160 135 0.135
37 Register product 120 145 170 145 0.145
38 Make a purchase order request to the supplier 100 125 150 125 0.125
39 Restore Database Backup 80 105 140 106.7 0.107
40 Manage Client 80 105 130 105 0.105
41 Program Credits on demand 100 130 160 130 0.13
42 Place the customer's order 110 135 160 135 0.135
43 Registrar Payment Method 120 160 170 155 0.155
44 Registrar Coin 100 125 150 125 0.125
45 Registrar Item 100 125 150 125 0.125
46 Registrar Subcategory 80 105 130 105 0.105
47 Registrar qualification 80 105 130 105 0.105
48 Register customer points 100 130 160 130 0.13
49 Registrar category 110 135 160 135 0.135
50 Product Registrar 120 145 170 145 0.145
51 Cargo Registrar 100 125 150 125 0.125
52 Generate Monthly Payroll 80 130 140 123.3 0.123
53 Manage Discounts 80 120 130 115 0.115
54 Manage Bonds 100 130 160 130 0.13
55 Manage Contributions 110 135 160 135 0.135
56 Manage Transaction Log 120 145 170 145 0.145
Total 4938 6374 7705 6,357 6.36
Table 1 Estimation of lines of code
Source: Own preparation

25
 Software Project Management Plan

For the effort estimation, the estimated lines of code will be used as
historical data on average productivity LDC:

Clearing E = kldc / p
Effort 24.11 people/month
Duration 8.04 months
Personal 3 programmer analysts, 1 manager, and 1 external consultant

Staff form
Salary
Employee cargo Monthly Duration Cost (noun)
(Sus.)
Ernesto Soto Roca Project manager 800 8 6400
Juan Martínez Sánchez Technology consultant 700 5 3500
María Zurita Sánchez Programmer Analyst 600 8 4800
Marcos Mariscal Martínez Programmer Analyst 600 8 4800
Federico Villa Marthi Programmer Analyst 600 8 4800
Total Cost 3300 24300
Table 2: Staff Schedule
Source: Own elaboration

Analysis of the results:

The data obtained using the LDC estimation technique results in:
Effort=24.11p/m
Duración=8.04 meses
With a total estimated cost according to the payroll of the staff of 24300 00/100
American dollars.

26
 Software Project Management Plan

1.1.1. COCOMO Estimates (Constructive Cost Model)

The formulas will be the following:

E = Effort = a KLDCeFAE (persona per month)

T = Tiempo de duración del desarrollo = c Esfuerzo d(months)
P = Personal = E/T(people)

LANGUAGE LDC/PF

Visual C# 32

SQL 12

Thus, after knowing that there are 32 LDC for each PF, due to being C#, the result
the KDLC will be as follows:

KLDC = (PF * Lines of code per PF)/1000 = (261.36*32)/1000 = 8.363 KDLC

SOFTWARE PROJECT a e c d

Organic 3.2 1.05 2.5 0.38

Semi-trailer 3.0 1.12 2.5 0.35

Built-in 2.8 1.20 2.5 0.32

The number of lines of code does not exceed 50 KLDC, and furthermore the management project,

COST DRIVERS EVALUATION

Very Low Nominal High Very Extr.

under high high
Required software reliability ["0.75","0.88","1.00"] 1.15 1.40
Database size - 0,94 1.00 1.08 1.16 -
Product complexity 0.70 0.85 1.00 ["1.15","1.30","1.65"]

Execution time restrictions - - 1.00 1,11 1.30 1.66

27
 Software Project Management Plan

Main storage restrictions - - 1.00 1,06 1,21 1,56

Virtual machine volatility 0.87 1.00 1.15 1.30 -
-
Computer response time - 0.87 1.00 1.07 1.15 -
Analyst capacity 1.46 1.19 1.00 0.86 0.71 -
Experience in the application 1.29 1.13 1.00 0.91 0.82 -
Programmers' capacity 1,42 1,17 1.00 0.86 0.70 -
Experience in used operating systems 1.21 1.10 1.00 0.90 -
Experience in programming language 1.14 1.07 1.00 0.95 - -
Modern programming practices ["1.24","1.10"] 1.00 0.91 0.82 -
Use of software tools 1.24 1.10 1.00 0.91 0.83
Project planning limitations 1.23 1.08 1.00 1.04 1.10 -

FAE=1,15*1,00*0,85*1,11*1,00*1,00*1,07*0,86*0,82*0,70*1,00*0,95*1,00*0,91*1,08
0.53508480

Calculation of development effort:

E = a KLDCeFAE = 3.2 * (8.363)^1.05 * 0.53508480 = 15.91 people/month

Calculation of development time:

T = c Effortd= 2.5 * (15.91)^0.38 = 7.15 months

Productividad:

PR = LDC/Effort = 8363/15.91 = 525.64 LDC/person per month

Average personnel:

P = E/T = 15.91/7.15 = 2.22 persons

Analysis of the results:

For a team of 3 people working for about 7 months, the team consists of 3 analysts.
programmer 1 manager and an external consultant.

28
 Software Project Management Plan

1.1.2. Point function-based estimates.

1.- Estimation of the values of the information domain.

Value of domain So Sp Pessimist Media FACTOR OF SUBTO
of information weighted WEIGHTING TAL
Simple Medium Complex
Number of Entries 45 50 60 50.83 3 4 6
203.33
Number of exits 30 40 50 40.00 4 5 7
160.00
Number of requests 4 6 9 6.17 3 4 6
24.67
Number of files 50 60 65 59.17 7 10 15
414.17
No. External interfaces 1 1 1 1.00 5 7 10
7.00
∑CT 809.17

Table 3: Information domain values

ADJUSTMENT VALUES OF COMPLEXITY

0 es no influencia, 1 es incidental, 2 es moderado, 3 es medio, 4 es significativo y 5 es esencial
1. Does the system require reliable backup and recovery?
4
2. Does it require data communication?
3
3. Are there distributed processing functions?
0
4. Is performance critical?
2
5. Will the system be executed in an existing and heavily used operating environment?
3
6. Does it require interactive data entry?
3
7. Does the interactive data entry require that input transactions be carried out on multiple
screens or operations? 4
8. Are the master files updated interactively?
3
9. Are the inputs, outputs, files, or requests complex?
3
10. Is the internal processing complex?
2
11. Has the code been designed to be reusable?
2
12. Are conversion and installation included in the design?
3
13. Has the system been designed to support multiple installations in different organizations?
3
14 Has the application been designed to facilitate changes and to be easily used by the user?
3
Fi 38
Table 4: Complexity adjustment values
Source: Own creation

PF=833.4416667

29
 Software Project Management Plan

Clearing E=PF/p
Average productivity (pf) 23.68287
Effort 35.19 people/month
Duration 11.73 months
Personal 3 programmer analysts, 1 manager, and 1 external consultant

Staff roster
Salary
Employee cargo Monthly Duration Cost (noun)
Sus.
Ernesto Soto Roca Project manager 800 11.73 9384
Juan Martínez Sánchez Technology consultant 700 5 3500
Mary Zurita Sánchez Programmer Analyst 600 11.73 7038
Marcos Mariscal Martínez Programmer analyst 600 11.73 7038
Federico Villa Marthi Programmer Analyst 600 11.73 7038
Total Cost 3300 33998
Table 5: Payroll Sheet
Source: Own elaboration

Analysis of the results:

The data obtained using the function point estimation technique giving as
Resultado:
Effort=35.19 p/m
Duración=11.78 meses
With a total estimated cost according to the payroll of the staff of 33998 00/100
American dollars.

30
 Software Project Management Plan

1.2. Risk Analysis.

Managing risk in the variables, client, process, and development environment, without meaning that these are the only category.
of risks that can affect the success of the project.
INITIAL RISK LIST

CAT. NRO RISK PROB. IMPACT

R1 Frequent changes in requirements by clients exist. 0.4 1
R2 He/She has no experience in previous projects with similar characteristics. 0.3 2
R3 Clear idea of the objectives that the project aims for and what the users want. 0.5 2
R4 There is no time for a formal specification of the requirements. 0.7 3
R5 Does not allow the development team to work, giving advice as a computer expert. 0.4 1
R6 Does not understand the product life cycle. 0.3 2
R7 There is no clear policy for standardization and monitoring of a methodology. 0.5 2
R8 The managers and developers are trained. 0.7 3
R9 Everyone knows the standards 0.4 1
There are templates and models for all documents resulting from the process. 0.3 2
Technical reviews of the design requirements specification and coding are applied. 0.5 2
R12 Technical reviews of the review and testing procedures are applied 0.7 3
R13 The results of the technical reviews are documented. 0.4 1
R14 Are there any mechanisms to ensure that a development process follows the standards? 0.3 2
R15 Configuration management is carried out 0.5 2
There are mechanisms to control changes in the requirements that impact the software. 0.7 3
Each subcontract is sufficiently documented. 0.4 1
R18 has been enabled and mechanisms for monitoring and technical evaluation of each subcontract are being
0.3 followed. 2
R19 Specification techniques for applications are available to facilitate communication with the client.0.5 2
Specific methods are used for software analysis. 0.7 3
A specific method is used for architectural and data design. 0.4 1
90% of the code is in high-level languages 0.3 2
R23 There are code documentation standards 0.5 2
Specific methods are used for test design. 0.7 3

31
 Software Project Management Plan

Tools are used to carry out planning and control. 0.4 1

R26 Not having project management tools 0.5 2
There are analysis and design tools 0.4 1
R28 There are no appropriate code generators for the application 0.3 2
R29 There are appropriate testing tools 0.5 2
R30 There are appropriate configuration management tools 0.7 3
A centralized database or repository is used. 0.4 1
R32 All development tools are integrated 0.3 2
Training has been provided to all members of the development team. 0.5 2
R34 There are experts to whom to ask for help about the tools 0.7 3
R35 There is online help and documentation available 0.4 1
Table 6: Initial risk listing
Source: Own elaboration

32
 Software Project Management Plan

1.2.1. Risk Planning.

CONTINGENCY PLAN
RISKS AFTER THE CUT-OFF LINE.
CAT. N. RISK PROB. IMP PREVENTION MANAGEMENT
That there are frequent changes of the If they will applytechniques The client must prioritize the
requirements from the identification of requirements, requirements in company of
clients. such as questionnaires, interviews with the development team. Which
personal information, identification of will not be changed until
problem using maps that ended the iteration that by
mentally, and the construction of the general takes two to four
evolutionary software prototypes weeks at most.
framed within a model
R1 0.4 1 incremental and iterative.
Has no experience in projects If elaborate questionnaires, The results of each iteration
previous ones with similar characteristics oriented a detecting them will serve as historical data
customer experience and real users of productivity y
Finally, with the use of effort technologies for the project, which
CLIENT similar, the ease or opposition will allow for adjusting the planning to
PROC. OF to the change. medical that evolves the
PRODUCTION R2 0.3 2 development
Clear idea of the objectives that If will work in Identify Construction of maps
it aims the project and of those who fully the mental situations, business processes
do users want. problematic, and the current problem of the company
it will solve the application. detecting the operation
R3 0.5 2 reality of the activities
No has Time for a The importance of defining a formal channel will be made clear.
specification formal of the from the client's participation in planning the meetings of
requirements. the prioritization of requirements and evaluation, and the start of iteration,
evaluation of the result in each according to the process.
R4 0.7 3 iteration.
Does not allow the team to work
development, for giving advice on
R5 computer expert 0.4 1

33
 Software Project Management Plan

Does not understand the life cycle of

product.
R6 0.3 2
There is no clear policy on There is a project plan, the update continues of the
normalization and monitoring of a planning temporal what project plan by the manager
methodology normara the development of the project. And self-planning
project of activities per team
R7 0.5 2 of development
There are managers and developers.
R8 formed 0.7 3
Everyone knows the standards A rigorous monitoring will be done for the detection of the device outside of
correction
to the application of standards and norms, y
standards proposed by the self-assessment plan.
R9 0.4 1 of project.
There are templates and models for everyone Adherence to standards and regulations for the detection of non-artifacts
the documents resulting from the process documentation. documented and out of
norm, y proceed athe
R10 0.3 2 correction.
PROC. OF Technical reviews are applied to the Presentations will be made to optimize the meetings.
PRODUCTION specification of requirements short iterations. Where self-evaluation and review of
ENVIRONMENT OF design and coding the review of the constructed artifacts will be carried out.
DEVELOPMENT deliverables and management of
R11 0.5 2 configuration.
Technical reviews are applied to the
R12 review and testing procedures 0.7 3
The results of the The management of making the meetings effective is considered.
technical reviews configuration self-assessment and review of
artifacts built,
identification for each
R13 0.4 1 deliverable.
Is there any mechanism to ensure
that a development process follows the
R14 standards 0.3 2
Configuration management is carried out The management of preparing the SQA Plan is contemplated for
R15 0.5 2 configuration for each project.
There are mechanisms to control the Review the activities of auditing the work products
R16 changes in the requirements that 0.7 3 engineering in agreement with the appointed, to verify their

34
 Software Project Management Plan

They have an impact on the software defined process. adherence with those
defined in the model of
process.
Each is sufficiently documented.
R17 subcontract 0.4 1
It has been enabled and is still being followed

mechanisms of follow-up y
evaluation technique of each
R18 subcontract 0.3 2
It is available
of techniques of Planning of the Inform the Performance:
application specification for Communications: determine how to gather and distribute information
facilitate communication with the client. information needs and about performance. This
communications of it includes status reports,
interested in the project. measurement of progress y
projections.
R19 0.5 2 s.
Specific methods are used to Information Distribution: Managing Stakeholders:
software analysis put the necessary information to manage communications to
willingness of the interested parties to meet the requirements of
the project when appropriate. those interested in the project and
R20 0.7 3 resolve controversies with it
A specific method is used for the
R21 architectural and data design 0.4 1
90% of the code is in languages of
R22 high level 0.3 2
There are documentation standards of
R23 code 0.5 2
Specific methods are used for the
R24 test design 0.7 3
Tools are used to carry out
R25 end planning and control 0.4 1
That it should not be tools of Define in advance the purchase of the licenses for the
ENVIRONMENT OF project management tools and technologies for management of configuration,
DEVELOPMENT R26 0.5 2 employ. planning.
R27 There are analysis and design tools 0.4 1 Have a case tool. Purchase the licensing for

35
 Software Project Management Plan

Enterprise Architect 7.0 said product

There are no code generators. The team has with putting into operation the
appropriate for the application generator tools generator of applications,
R28 0.3 2 code. process and forms.
Hey tools of test Be they will carry outTests to be conducted iteratively.
appropriate functional, completeness by suggested tests
iterations, behavior of the
R29 0.5 2 environment, and stress tests
There are management tools for The TEEM System of Use will be used. the tool
appropriate configurations Microsoft to manage the aforementioned
R30 0.7 3 product releases
A database is used or
R31 centralized repository 0.4 1
All the tools are The TEEM System will be used
integrated development Microsoft to manage the
R32 0.3 2 product releases
Training has been provided to everyone Make and disseminate information in a timely manner.
the members of the development team communication mechanisms and
R33 0.5 2 the team model.
There are experts to consult. A budget is estimated for the hiring process of the
R34 help about tools 0.7 3 technology consultant. consultant.

Table 7: Contingency Plan

Source: Own preparation

36
 Software Project Management Plan

1.2.2. Analysis of risk consequences

According to the risk analysis approach proposed by the United States Air Force
The overall risk exposure, ER, is determined using the following relationship:
ER=PxC
Where P is the probability of a risk occurring, and C is the cost of the project if the risk occurs.

RISK ASSESSMENT
Cost
CAT. NRO RISK PROB. IMPACT [Link]
[Link] effort Total(ER)
($us.)
Frequent changes in requirements by
R1 of the client
0.4 1 1 1 8 9
He/She has no experience in similar previous projects.
R2 characteristic
0.3 2 1 2 8 10
Clear idea of the objectives that the project aims for and of the
R3 what do users want
0.5 2 2 1 6 7
There is no time for a formal specification of the
R4 requirement
0.7 3 1 2 2 4
Does not let the development team work, by giving advice.
R5 computer expert
0.4 1 1 1 1 2
R6 Does not understand the product life cycle. 0.3 2 3 3 3 6
There is no clear policy for normalization and monitoring of
R7 a methodology
0.5 2 3 3 3 6
R8 The managers and developers are trained. 0.7 3 1 2 2 4
R9 Everyone knows the standards 0.4 1 1 1 1 2
There are templates and models for all documents.
R10 result of the process
0.3 2 4 2 2 4
Technical reviews of the specification are applied.
R11 requirements design and coding
0.5 2 2 2 2 4
Technical reviews of the procedures are applied
R12 review and test
0.7 3 2 1 1 2
R13 The results of the technical reviews are documented. 0.4 1 4 2 3 5

37
 Software Project Management Plan

Is there any mechanism to ensure that a process of

R14 development follows the standards
0.3 2 3 1 3 4
R15 Configuration management is carried out 0.5 2 4 2 2 4
There are mechanisms to control changes in the
R16 requirements that have an impact on the software
0.7 3 2 1 1 2
R17 Each subcontract is sufficiently documented. 0.4 1 4 3 2 5
Monitoring mechanisms have been enabled and are being followed.
R18 technical evaluation of each subcontract.
0.3 2 2 3 2 5
There are application specification techniques available for
R19 facilitate communication with the customer.
0.5 2 2 2 1 3
R20 Specific methods are used for software analysis. 0.7 3 1 1 3 4
A specific method is used for architectural design and
R21 of data
0.4 1 2 2 3 5
R22 90% of the code is in high-level languages 0.3 2 2 2 4
R23 There are code documentation standards 0.5 2 3 1 1 2
R24 Specific methods are used for test design 0.7 3 2 2 2 4
Tools are used to carry out planning and
R25 control
0.4 1 4 1 2 3
R26 That there are no project management tools 0.5 2 4 2 1 3
R27 There are analysis and design tools 0.4 1 1 1 3 4
There are no appropriate code generators for the
R28 application
0.3 2 5 3 3 6
R29 There are appropriate testing tools 0.5 2 6 3 2 5
R30 There are appropriate configuration management tools 0.7 3 7 2 1 3
R31 A centralized database or repository is used. 0.4 1 7 1 2 3
R32 All development tools are integrated 0.3 2 1 2 2 4
Training has been provided to all members of
R33 development team
0.5 2 1 2 1 3
There are experts to ask for help about the
R34 tools
0.7 3 2 3 1 4
R35 There is online help and documentation available 0.4 1 1 1 2 3
TOTAL 90 64 84 148
Table 8: Risk assessment.
Source: Original elaboration

38
 Software Project Management Plan

PRO IMPACT Cost

CAT. NRO RISK [Link] effort [Link] Total(E
B. O
s o ($us.) R)
That there are frequent changes in the requirements on the part of
R1 0.4 1 3 1 8 9
the client
He/She does not have experience in previous similar projects.
R2 0.3 2 1 2 8 10
characteristic
Clear idea of the objectives that the project aims for and those that
R3 0.5 2 2 1 6 7
users want
R4 There is no time for a formal specification of the requirements. 0.7 3 5 2 2 4
Does not allow the development team to work, giving advice on
R5 0.4 1 1 1 1 2
computer expert
R6 Does not understand the product life cycle. 0.3 2 3 3 3 6
There is no clear policy for standardization and monitoring of a
R7 0.5 2 3 3 3 6
methodology
R8 The managers and developers are trained. 0.7 3 5 2 2 4
R9 Everyone knows the standards 0.4 1 5 1 1 2
There are templates and models for all the resulting documents.
R10 0.3 2 4 2 2 4
of the process
Technical reviews of the specification are applied
R11 0.5 2 3 2 2 4
design and coding requirements
Technical reviews of the review procedures are applied and
R12 0.7 3 7 1 1 2
test
R13 The results of the technical reviews are documented. 0.4 1 4 2 3 5
Is there any mechanism to ensure that a development process
R14 0.3 2 3 1 3 4
follow the standards
R15 Configuration management is carried out 0.5 2 4 2 2 4
There are mechanisms to control changes in requirements
R16 0.7 3 7 1 1 2
that have an impact on software
R17 Each subcontract is sufficiently documented. 0.4 1 4 3 2 5
R18 Tracking mechanisms have been established and are ongoing 0.3 2 2 3 2 5

39
 Software Project Management Plan

technical evaluation of each subcontract.

Specification techniques for applications are available for
R19 0.5 2 2 2 1 3
facilitate communication with the client.
R20 Specific methods are used for software analysis. 0.7 3 1 1 3 4
A specific method is used for architectural design and
R21 0.4 1 2 2 3 5
data
R22 90% of the code is in high-level languages 0.3 2 2 2 4
R23 There are code documentation standards 0.5 2 3 1 1 2
R24 Specific methods are used for test design. 0.7 3 4 2 2 4
R25 Tools are used to carry out planning and control 0.4 1 4 1 2 3
R26 That there are no project management tools. 0.5 2 4 2 1 3
R27 There are analysis and design tools. 0.4 1 6 1 3 4
R28 There are no appropriate code generators for the application. 0.3 2 5 3 3 6
R29 There are appropriate testing tools 0.5 2 6 3 2 5
R30 There are appropriate configuration management tools 0.7 3 7 2 1 3
R31 A centralized database or repository is used. 0.4 1 7 1 2 3
R32 All development tools are integrated. 0.3 2 9 2 2 4
Training has been provided to all team members of
R33 0.5 2 8 2 1 3
development
R34 There are experts to whom you can ask for help regarding the tools. 0.7 3 7 3 1 4
R35 There is online help and documentation available 0.4 1 11 1 2 3
Table 9: Risk Assessment.
Source: Own elaboration

40
 Software Project Management Plan

1.2.3. Analysis of the obtained data:

If the estimated duration LDC is D(LDC)=8.04 months and the PF estimate is
of D(PF)=11.78 months plus 3 months for risk assessment. The estimated duration
It is 14 months old.

1.3. Temporal Planning

1.3.1. Task Identification:

TECHNICAL SHEET:
Integrated system of information for management of
operations in the area of marketing, inventories and
human resources for the National Pharmacy Chain
PROJECTS FarmaCorp
PROCESS Unified Software Development Process
DURATION 14 months (280 working days)
Information domain (25%) Test
Design Impl. to
TIME DISTRIBUTION Plan (3%) Business [Link]. Analysis (25%) (20%) (27%)
56 75
6 days 10 days 20 days 40 days 70 days days days
ITERATION PLAN TIME ASSIGNMENT.
INITIAL PHASE 28 days
Information domain 24 days
Develop the Project Plan 4 days
PHASE OF ELABORATION 96 days
E1: development of artifacts
primary 44 days
E2: Develop use cases
primary 52 days
Formal technical reviews 0 days
CONSTRUCTION PHASE 90 days
C1: Develop use cases
secondary 40 days
C2: Refinement of the application 50 days
Formal Technical Reviews 0 days
TRANSITION PHASE 66 days
T1: Capacitación y pruebas con
end users 20 days
T2: Refinement and correction of
errors 46 days
Table 10: Task identification
Source: Own elaboration

41
 Software Project Management Plan

1.3.2. Gantt Chart

42
 Software Project Management Plan

1.3.3. Network diagram

[Link].Start phase

Illustration 3: Network diagram startup phase

Source: Own preparation

43
 Software Project Management Plan

[Link]. Drafting phase

Illustration 4: Network diagram drafting phase

Source: Own elaboration

44
 Software Project Management Plan

[Link]. Construction phase

Illustration 5: Network diagram construction phase

Source: Own elaboration

45
 Software Project Management Plan

[Link]. Transition phase.

Illustration 6: Transition phase network diagram.

Source: Own elaboration

46
 Software Project Management Plan

1.4. Internal Organization

1.4.1. Structure.
Project Manager

Technology consultant

Analyst-programmer 1 Analyst–programmer 2 Analyst–programmer 3

Table 11: Organic structure of the team

Source: Own elaboration

1.4.2. Organizational paradigm.

The Unified Software Process will be used due to its iterative nature and
incremental software development.
1.4.3. Organization of the team

Table 12: Controlled decentralized model

The Decentralized Controlled (DC) model for the following reasons: It has a
project manager for 'senior management' tasks, has technical managers
operational for specific tasks. Problem solving is done in a group of
attention area. There should be coordination among the subgroups; communication between
subgroups and individuals are horizontal and there is vertical communication between the bosses

secondary and the team manager High modularity (people can do each one
yours

47
 Software Project Management Plan

1.5. Resources
1.6. Human Resources.
The available human resources for this project are as follows

Empleado cargo

Ernesto Soto Roca Project manager

Juan Martínez Sánchez Technology consultant
Maria Zurita Sánchez Programmer Analyst
Marcos Mariscal Martínez Programmer Analyst
Federico Villa Marthi Programmer Analyst

1.7. Equipos:

equipo
Employee cargo

Ernesto Soto Roca Project manager Personal computer

Juan Martínez Sánchez Technology Consultant Development team
María Zurita Sánchez Programmer Analyst Development team
Marcos Mariscal Martínez Programmer Analyst Development team
Federico Villa Marthi Programmer Analyst Development team

1.8. Costo del Proyecto

Taking data from LDC estimation techniques, Function Points, COCOMO plus the
evaluation of effort the cost of the project would be 30000 Sus. With a duration of 1
a year and 4 months.

48
 Software Project Management Plan

ANNEX

49
 Software Project Management Plan

ANNEX A-01.

Business model
Business process Manage supplier orders - (Activity diagram)
Created By: Ernesto Soto Roca on 03/08/2009
Last Modified: 18/02/2010
Version: [Link]:False
GUID: {98BDBBB2-0A49-437f-9A84-182824E667D9}

Business process Manage supplier orders

Supplier Inventory Manager Department of Finance

Start

Review the request for

request from the dept. of
inventory

Receive the order Check the product stock for

Receive the request warehouses approve the order to
from supplier
of order Inventory

If there is no stock of
product Place the observations Accept request from
Check the products to the order inventory request
of the order
Send the order
requested Request the quote for
products to supplier
If there are no observations

Make a request for

order to supplier
Store the
products
Receive the
financial compliance

Send the order of

products to the supplier

Final

2days
2days 1day

Ilustración 7: Proceso de negocio Gestionar los pedidos a proveedor

50
 Software Project Management Plan

Business process return management - (Activity diagram)

Created By: Ernesto Soto Roca on 04/08/2009
Last Modified: 04/08/2009
Version: [Link]:False
GUID: {CAD2B3F7-A04F-4c56-A57B-0125199CD020}

Illustration 8: Business process for managing returns to suppliers

51
 Software Project Management Plan

Business process to manage the company's internal orders - (Activity diagram)

Created By: Ernesto Soto Roca on 03/08/2009
Last Modified: 19/02/2010
Version: [Link]:False
GUID: {C977EBFA-E995-45d7-BF1D-138765AA4797}

Business process for managing internal orders of the company

Sales Department Inventory Manager

Start

Check the stock of Review the request for

product request from the dept. of
inventory
If there is no stock
product approve the order to
Inventory

Make a request for

request to the dept. of Place the observations Accept request from
to the order inventory request
inventory

Receive the order Prepare the order of

carried out product

Send the internal order to

If there is an observation
sale

Receive the
products and store

Final

Illustration 9: Business process for managing the company's internal orders

52
 Software Project Management Plan

2. ANNEX A-02.

a. Model of requirement
Functional use case diagram
Created By: Ernesto Soto Rocaon27/07/2009
Last Modified: 19/08/2009
GUID: {66ECD689-DBBB-47c0-A846-A76F15EE571C}

Illustration 10: Functional use case diagram inventory module

53
 Software Project Management Plan

Administrative Use Case Diagram of the System

Created By: Ernesto Soto Rocaon 07/27/2009
Last Modified: 27/11/2009
Version: [Link]:False
GUID: {EDCB1E1F-54EE-44f5-91F8-A2FA260A9BF1}

UC use case diagram for the administrative system

Use case diagram of functions for system administration

Manage User
of the system

Registrar
In charge of the system Branch

Operations Management

Manage backup of Define access to

the database system

Restore Copy of
database security
of data

System Assistant

Illustration 11: Administrative Use Case Diagram of the System

54
 Software Project Management Plan

Use Case Diagrams for Reports

Created By: Ernesto Soto Roca on 27/07/2009
Last Modified: 10/08/2009
Version: [Link]:False
GUID: {0F16152E-F3B5-45db-898F-29FDC4D1D14C}

UC diagrams of reporting use cases

Use case diagram for information requirement

management
management management
Issue report of
returns to Prepare a report on Prepare summary
provider of returns from from orders to
sale provider

Department of Finance
management
Draft Report of
orders to supplier

Issue minutes of
reception of
Issue Certificate of
Emit Department products
registration of
Proof of of inventory
Inventory Manager provider
order to
provider

Issue receipt Emit

of return to Proof of
provider inventory request
Issue certificate of
reception of
order of
provider managerial
Prepare report on
sales orders

Sales Department
Inventory Assistant
management
Prepare a report of Issue minutes of
product stock return of
products to
inventory

Illustration 12: Administrative Use Case Diagram of the System

55
 Software Project Management Plan

Use Case Model - (Use Case diagram)

Created By: Ernesto Soto Rocaon 06/05/2009
Last Modified: 20/05/2009
Version: [Link]:False
GUID: {B8005AFE-8E12-4030-9002-F659551228EE}

the use case model

Pharmaceutical sales system

Registrar
product
Registrar
Registrar
Sector
Currency
Manage
Client

Registrar
Perform the category
Customer service order of the Section manager
client
Registrar Sub
Category

Program
Credits on request
Registrar
Payment method
Registrar
rating

Illustration 13: Functional use cases of the sales system

56
 Software Project Management Plan

3. ANNEX A-03.

a. Analysis model.
Class diagram of Analysis -(Logical diagram)
Created By: Ernesto Soto Rocaon23/08/2009Last Modified: 03/08/2011
Version: [Link]:FalseGUID:{F185DB4E-212C-41e5-A398-6267C7A4AB7B}

Illustration 14: class diagram of inventory system analysis

57
 Software Project Management Plan

Domain Model - (Logical diagram)

Created By: Ernesto Soto Roca on 11/19/2005
Last Modified: 27/05/2009
Version: [Link]:False
GUID: {B8D51A91-B583-47f9-A3FA-5D2700A02F62}

Illustration 15: class s of sales module analysis.

58