REQUERIMIENTOS DE SOFTWARE

Project Control, Project Closing, Timeline template

Get Started. It's Free
or sign up with your email address
REQUERIMIENTOS DE SOFTWARE by Mind Map: REQUERIMIENTOS DE SOFTWARE

1. Tipos:

1.1. 1. De Usuario

1.1.1. Establish Project Administration Procedures

1.1.2. Establish Quality Control Procedures

1.1.3. Establish Progress Control Procedures

1.1.4. Establish Change Control Procedures

1.1.5. Establish Issue Resolution Procedure

1.1.6. Review Project Control Procedures

1.2. 2.De Sistema

1.2.1. Estimate Project Costs

1.2.2. Identify and Quantify Benefits

1.2.3. Determine Break-even Point

1.2.4. Analyze Risk

1.2.5. Review Business Case

1.3. 3. De Software

1.3.1. Prepare Initiation Stage Assessment

1.3.2. Review Initiation Stage Assessment

1.3.3. Follow-Up Initiation Stage Assessment

1.3.4. Compile Project Initiation Report

2. Clasificacion:

2.1. Funcionales

2.1.1. Update Project Schedule

2.1.2. Update Budget / Costs

2.1.3. Conduct Team Status Review

2.1.4. Create Status Report

2.2. No-Funcionales

2.2.1. Organizacionales

2.2.2. De Producto

2.2.3. Externos

2.3. De Dominio

2.3.1. Identify Project Issues

2.3.2. Assess Impact of Issues

2.3.3. Assign Resources

2.3.4. Resolve Issue

3. Objetivos

3.1. Para introducir los conceptos de necesidades de los usuarios y del sistema.

3.1.1. Prepare Product Evaluation

3.1.2. Conduct Product Evaluation

3.1.3. Initiate Maintenance Process

3.2. Describir los requisitos funcionales y no funcionales

3.2.1. Prepare for Project Closure Meeting

3.2.2. Conduct Project Closure Meeting

3.2.3. Follow Up Project Closure Meeting

3.3. Para explicar dos técnicas para la descripción de los requisitos del sistema.

3.3.1. Prepare Project Review

3.3.2. Conduct Project Review

3.3.3. Implement Process Improvement

3.4. Para explicar cómo se pueden organizar los requisitos de software en un documento de requisitos