Plantilla rup

Solo disponible en BuenasTareas
  • Páginas : 8 (1810 palabras )
  • Descarga(s) : 0
  • Publicado : 10 de enero de 2011
Leer documento completo
Vista previa del texto
Documento de la Arquitectura del Software

Versión

[Note: The following template is provided for use with the Rational Unified Process. Text enclosed in square brackets and displayed in blue italics (style=InfoBlue) is included to provide guidance to the author and should be deleted before publishing the document. A paragraph entered following this style will automatically be set tonormal (style=Body Text).]

[To customize automatic fields in Microsoft Word (which display a gray background when selected), select File>Properties and replace the Title, Subject and Company fields with the appropriate information for this document. After closing the dialog, automatic fields may be updated throughout the document by selecting Edit>Select All (or Ctrl-A) and pressing F9, orsimply click on the field and press F9. This must be done separately for Headers and Footers. Alt-F9 will toggle between displaying the field names and the field contents. See Word help for more information on working with fields.]

Historia de Revisiones
|Fecha |Versión |Descripción |Autor|
| | | | |
| | | | |
| | | ||
| | | | |

Tabla de Contenido

1. Introducción 2
1.1 Propósito 2
1.2 Alcance 2
1.3 Definiciones, Acrónimos y Abreviaturas 2
1.4 Referencias 2
1.5 Resumen 2

3. Diagrama de Navegabilidad (Flujo de Procesos) 2

4. RepresentaciónArquitectónica DAO, MVC 2

5. Objetivos y Restricciones de Arquitectura LIMITES DIAGRAMA DE CLASES. 2

6. Vista de Casos de Uso CUADROS 2

7. Vista Lógica MVC 2
7.1 Resumen 2
7.2 Paquetes de Diseño Significativos dentro de la Arquitectura 2
7.3 Realizaciones de los Casos de Uso 2

8. Vista de Procesos. 2

9. Vista de Desarrollo HARDWARE EQUIPO.REQUISITOS MIN. 2

10. Vista deImplantación 2
10.1 Resumen 2
10.2 Capas 2

11. Vista de Datos (opcional) DIAGRAMA E.R. 2

12. Tamaño y Desempeño. IMPACTO+ARQUITECONICOREQUIERE UN TRABAJO MUY DETALLADO. DESCUENTO. 2

13. Calidad. CAMBIOS BRUSCOS 2
Documento de la Arquitectura del Software

Introducción

[The introduction of the Software Architecture Document provides an overview of the entire SoftwareArchitecture Document. It includes the purpose, scope, definitions, acronyms, abbreviations, references, and overview of the Software Architecture Document.]

1 Propósito

This document provides a comprehensive architectural overview of the system, using a number of different architectural views to depict different aspects of the system. It is intended to capture and convey the significantarchitectural decisions which have been made on the system.

[This section defines the role or purpose of the Software Architecture Document, in the overall project documentation, and briefly describes the structure of the document. The specific audiences for the document is identified, with an indication of how they are expected to use the document.]

2 Alcance

[A briefdescription of what the Software Architecture Document applies to; what is affected or influenced by this document.]

3 Definiciones, Acrónimos y Abreviaturas

[This subsection provides the definitions of all terms, acronyms, and abbreviations required to properly interpret the Software Architecture Document.  This information may be provided by reference to the project’s Glossary.]

4...
tracking img