Software architecture document

Solo disponible en BuenasTareas
  • Páginas : 9 (2156 palabras )
  • Descarga(s) : 0
  • Publicado : 7 de marzo de 2011
Leer documento completo
Vista previa del texto
Software Architecture Document

Online Catering Service 1.0

Yummy Inc.

[pic]

SAD Revision History

|Date |Version |Description |Author |
|2005-03-16 |0.1 |Significant Use-Cases : the key requirements |Yummy Inc. || | | |Architecture Team |
|2003-03-18 |0.2 |Candidate architecture : the high level architecture of|Yummy Inc. |
| | |the system|Architecture Team |
|2003-03-20 |0.3 |Initial Deployment Model |Yummy Inc. |
| | | |Architecture Team |
|2003-04-24 |0.4 |Key abstractions : the keydata elements used in the |Yummy Inc. |
| | |system |Architecture Team |
|2003-04-29 |0.5 |Analysis Model |Yummy Inc. |
| || |Architecture Team |
|2003-05-05 |0.6 |Design Model |Yummy Inc. |
| | | |Architecture Team |
|2004-05-11|0.7 |Concurrency mechanisms |Yummy Inc. |
| | | |Architecture Team |
|????-??-?? |0.8 | |Yummy Inc.|
| | | |Architecture Team |

Table of Contents

1. Introduction 4

1.1 Purpose 4
1.2 Scope 5
1.3 Definitions, Acronyms and Abbreviations 5
1.4 References 5
1.5 Overview 5

2. Architectural Representation 6

3. Architectural Goals andConstraints 7

3.1 Technical Platform 7
3.2 Transaction 7
3.3 Security 7
3.4 Persistence 7
3.5 Reliability/Availability (failover) 7
3.6 Performance 8
3.7 Internationalization (i18n) 8

4. Use-Case View 8

4.1 Ordering Menus 8
4.2 Use-Case Realizations 9

5. Logical View 9

5.1 Overview 9
5.2 Architecturally Significant Design Packages 11

6. Process View 13

7.Deployment View 13

8. Implementation View 15

8.1 Overview 15
8.2 Layers 15

9. Data View 15

10. Size and Performance 16

11. Quality 16

Introduction

This document comes as a complement to the article “Developing a J2EE Architecture with Rational Software Architect using the Rational Unified Process®” [RUPRSA]. It illustrates what can be the content of a Software ArchitectureDocument (SAD) produced during the RUP Elaboration phase.

As stated in the companion article, a RUP Software Architect will typically perform height major steps in order to define a global architecture, and each time an activity is completed, a specific section of the SAD is enriched accordingly.

|Architectural activities |Software Architecture...
tracking img