Software Development Plan

<Company Name>
Reclutamiento y seleccin
Software Development Plan
Version <1.0>
Reclutamiento y seleccin Version: 1.0
Software Development Plan Fecha: 24/06/2016
<document identifier>
Revision History
Fecha Version Description Author
24/06/2016 1.0 <details> <name>
Confidencial KeyMaster, 2017 Page 2 of 11

Table of Contents
1. Introduction Error! Bookmark not defined.
1.1 Purpose Error! Bookmark not defined.
1.2 Scope Error! Bookmark not defined.
1.3 Definitions, Acronyms, and Abbreviations 5
1.4 References 5
1.5 Overview Error! Bookmark not defined.
2. Project Overview 6
2.1 Project Purpose, Scope, and Objectives Error! Bookmark not defined.
2.2 Assumptions and Constraints Error! Bookmark not defined.
2.3 Project Work Products Error! Bookmark not defined.
2.4 Evolution of the Software Development Plan 8
3. Project Organization 8
3.1 Organizational Structure 8
3.2 External Interfaces 9
3.3 Roles and Responsibilities 9
4. Management Process 9
4.1 Project Estimates 9
4.2 Project Plan 9
4.2.1 Phase Plan 9
4.2.2 Iteration Objectives 9
4.2.3 Releases 9
4.2.4 Project Schedule 9
4.2.5 Project Resourcing 9
4.2.6 Budget 9
4.3 Iteration Plans 9
4.4 Project Monitoring and Control 10
4.4.1 Requirements Management Plan 10
4.4.2 Schedule Control Plan 10
4.4.3 Budget Control Plan 10
4.4.4 Quality Control Plan 10
4.4.5 Reporting Plan 10
4.4.6 Measurement Plan 10
4.5 Risk Management Plan 10
4.6 Close-out Plan 10
5. Technical Process Plans 10

5.1 Development Case 10
5.2 Methods, Tools, and Techniques 10
5.3 Infrastructure Plan 10
5.4 Product Acceptance Plan 10
6. Supporting Process Plans 11

6.1 Configuration Management Plan 11
6.2 Evaluation Plan 11
6.3 Documentation Plan 11

6.4 Quality Assurance Plan 11

6.5 Problem Resolution Plan 11
6.6 Subcontractor Management Plan 11
6.7 Process Improvement Plan 11
7. Additional Plans 11
8. Annexes 11
9. Index 11

Software Development Plan
1. Introduccin
El Documento de Arquitectura de Software presenta la arquitectura del Sistema web Reclutamiento
y Seleccin, en las cuales ilustra un aspecto en particular del software desarrollado. Se pretende
de esta forma que el documento brinde al lector una visin global y comprensible del diseo
general del sistema desarrollado. Luego de describir en profundidad la arquitectura del sistema
Reclutamiento y Seleccin.
1.1 Propsito
Optimizar los procesos de una empresa en el rea de Recursos Humanos, para poder tener los
histricos de los candidatos que posterior mente se convertirn en empleados dentro de la
compaa previniendo lo ms posible errores humanos pudiendo sugerir los mejores perfiles para
los puestos requeridos tambin evitar el extravo y almacenamiento de documentos fsicos de los
candidatos.
Al ser los proceso eficiente y digitalizado reducir para la empresa costos de papelera, recurso
humano ayudara al personal de RH a liberarse de carga de trabajo.
1.2 Alcance
El proyecto en desarrollo tiene como alcance sistematizar y optimizar la administracin de
reclutamiento, ayudando a los empleados del rea con la mejor toma de decisin para la seleccin
del personal de determinada rea evaluando los perfiles solicitados con el del candidato a ocupar
un puesto.
1.3 Definiciones, acrnimos y abreviaturas
SRS (Sistema de Reclutamiento y Seleccin)
1.4 Referencias
Iteration Plans
Requirements Management Plan
Measurement Plan
Risk Management Plan
Development Case
Business Modeling Guidelines
User Interfaces Guidelines
Use-Case-Modeling Guidelines
Design Guidelines
Programming Guidelines
Test Guidelines
Manual Style Guide
Infrastructure Plan
Product Acceptance Plan
Configuration Management Plan

Evaluation Plan (only if this is a separate plannormally this is addressed in Section 6.2 of the
Software Development Plan)
Documentation Plan
Quality Assurance Plan
Problem Resolution Plan
Subcontractor Management Plan
Process Improvement Plan]
1.5 Resumen
[This subsection describes what the rest of the Software Development Plan contains and explains how the
document is organized.]
2. Project Overview
2.1 Proyecto de Propsito, alcance y objetivos
[A brief description of the purpose and objectives of this project and a brief description of what
deliverables the project is expected to deliver.]
2.2 Suposiciones y Restricciones
[A list of assumptions that this plan is based and any constraints, for example. budget, staff, equipment,
schedule, that apply to the project.]
2.3 Productos de trabajo del proyecto
El proyecto se realizara dentro de las siguientes fechas
Inicia el da 20 de mayo del 2016
Finaliza el da 30 de noviembre del 2016
Se entregaran Hitos durante el desarrollo del proyecto, Se establecieron 1 entrega durante el segundo
parcial y 2 entregas para el tercer parcial durante el sptimo cuatrimestre.
Para el octavo cuatrimestre Se establecieron 3 entregas durante el primer y segundo parcial y tercer
parcial.
Segundo parcial fechas de entrega

1 entrega: 30 de Junio del 2016.
1. Gestionar empleado.
Especificacin del caso de uso.
Diseo de pantalla o pantallas
Implementacin en cdigo
Pruebas
Liberacin de proceso
2. Gestionar usuarios.
Pruebas
Tercer parcial fechas de entrega

1 entrega: 14 de Julio del 2016.

1. Crear perfil.
Pruebas
2. Validar usuario.
Pruebas
2 entrega: 4 de Agosto del 2016.

1. Solicitar requerimiento.
Pruebas
2. Registrar candidato.
Pruebas
3. Programar entrevistas
Pruebas
Primer parcial fechas de entrega

1 entrega: 22 de Septiembre del 2016.
1. Registrar datos personales y laborales.
Pruebas
2. Evaluar perfil.
Pruebas
Segundo parcial fechas de entrega

2 entrega: 20 de Octubre del 2016.

1. Pre-seleccionar candidato.
Pruebas
2. Verificar de citas.
Pruebas
3. Seleccionar candidato.
Pruebas
Tercer parcial fechas de entrega

3 entrega: 3 de Noviembre del 2016.
4. Visualizar candidato.
Pruebas
5. Gestionar Expediente.
Pruebas
6. Gestionar lista negra.
Pruebas
2.4 Evolution of the Software Development Plan

[A table of proposed versions of the Software Development Plan, and the criteria for the unscheduled
revision and reissue of this plan.]
3. Project Organization
3.1 Organizational Structure
[Describe the organizational structure of the project team, including management and other review
authorities.]

3.2 External Interfaces

[Describe how the project interfaces with external groups. For each external group, identify the internal
and external contact names.]
3.3 Roles and Responsibilities
[Identify the project organizational units that will be responsible for each of the disciplines, activities, and
supporting processes.]
4. Management Process
4.1 Project Estimates
[Provide the estimated cost and schedule for the project, as well as the basis for those estimates, and the
points and circumstances in the project when re-estimation will occur.]
4.2 Project Plan
4.2.1 Phase Plan
[Include the following:
Work Breakdown Structure (WBS)
a timeline or Gantt chart showing the allocation of time to the project phases or iterations
identify major milestones with their achievement criteria
Define any important release points and demos.]
4.2.2 Iteration Objectives
[List the objectives to be accomplished for each of the iterations.]
4.2.3 Releases
[A brief description of each software release and whether its demo, beta, and so on.]
4.2.4 Project Schedule
[Diagrams or tables showing target dates for completion of iterations and phases, release points, demos,
and other milestones.]
4.2.5 Project Resourcing
4.2.5.1 Staffing Plan
[Identify the numbers and type of staff required here, including any special skills or experience, scheduled
by project phase or iteration.]
4.2.5.2 Resource Acquisition Plan
[Describe how you will approach finding and acquiring the staff needed for the project.]
4.2.5.3 Training Plan
[List any special training project team members will require, with target dates for when this training
should be completed.]
4.2.6 Budget
[Allocation of costs against the WBS and the Phase Plan.]
4.3 Iteration Plans
[Each iteration plan will be enclosed in this section by reference.]

4.4 Project Monitoring and Control

4.4.1 Requirements Management Plan
[Enclosed by reference.]
4.4.2 Schedule Control Plan
[Describe the approach taken to monitor progress against the planned schedule and how to take corrective
action when required.]
4.4.3 Budget Control Plan
[Describe the approach to be taken to monitor spending against the project budget and how to take
corrective action when required.]
4.4.4 Quality Control Plan
[Describe the timing and methods to be used to control the quality of the project deliverables and how to
take corrective action when required.]
4.4.5 Reporting Plan
[Describe internal and external reports to be generated, and the frequency and distribution of publication.]
4.4.6 Measurement Plan
4.5 Risk Management Plan
4.6 Close-out Plan
[Describe the activities for the orderly completion of the project, including staff reassignment, archiving of
project materials, post-mortem debriefings and reports, and so forth.]
5. Technical Process Plans
5.1 Development Case
5.2 Methods, Tools, and Techniques
[List the documented project technical standards, etc., by reference:
Business Modeling Guidelines
User Interfaces Guidelines
Use-Case-Modeling Guidelines
Design Guidelines
Programming Guidelines
Test Guidelines
Manual Style guide]
5.3 Infrastructure Plan
[Enclosed by reference]
5.4 Product Acceptance Plan

6. Supporting Process Plans

6.1 Configuration Management Plan
6.2 Evaluation Plan
[As part of the Software Development Plan, this describes the projects plans for product evaluation, and
covers the techniques, criteria, metrics, and procedures used for evaluation this will include
walkthroughs, inspections, and reviews. Note that this is in addition to the Test Plan, which is not enclosed
in the Software Development Plan.]
6.3 Documentation Plan
6.4 Quality Assurance Plan
6.5 Problem Resolution Plan
6.6 Subcontractor Management Plan
6.7 Process Improvement Plan
7. Additional Plans
[Additional plans if required by contract or regulations.]
8. Annexes
[Additional material of use to the reader of the Software Development Plan.]
9. Index

Software Development Plan

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Software Development Plan

Uploaded by

Copyright:

Available Formats

<Company Name>

Confidencial KeyMaster, 2017 Page 2 of 11

5. Technical Process Plans 10

6. Supporting Process Plans 11

Confidencial KeyMaster, 2017 Page 3 of 11

6.4 Quality Assurance Plan 11

Confidencial KeyMaster, 2017 Page 4 of 11

Software Development Plan

Confidencial KeyMaster, 2017 Page 5 of 11

Segundo parcial fechas de entrega

Tercer parcial fechas de entrega

Confidencial KeyMaster, 2017 Page 6 of 11

2 entrega: 4 de Agosto del 2016.

Primer parcial fechas de entrega

Segundo parcial fechas de entrega

Confidencial KeyMaster, 2017 Page 7 of 11

Tercer parcial fechas de entrega

2.4 Evolution of the Software Development Plan

Confidencial KeyMaster, 2017 Page 8 of 11

3.2 External Interfaces

Confidencial KeyMaster, 2017 Page 9 of 11

4.4 Project Monitoring and Control

Confidencial KeyMaster, 2017 Page 10 of 11

6. Supporting Process Plans

Confidencial KeyMaster, 2017 Page 11 of 11

You might also like