Tanager

Domain Model

Version 4.0 – Elaboration Phase 4

 

Table of Contents

1.     Introduction. 3

1.1.        Purpose. 3

1.2.        Definitions, Acronyms, and Abbreviations. 3

1.3.        Diagrams. 3

1.4.        References. 3

2.     Domain Model 3

3.     Revision History. 5

 

1.              Introduction

1.1.         Purpose

This document provides the Domain Model for the Tanager project.  The Domain Model is the visual representation of the objects in the Tanager system domain and is generated from the Use Cases.

1.2.         Definitions, Acronyms, and Abbreviations

A complete list of definitions, acronyms, and abbreviations can be found in the Tanager Glossary.

1.3.         Diagrams

All diagrams in this document were generated using Gentleware’s Poseidon for UML tool.

1.4.         References

Fowler, Martin.  2004.  UML Distilled.  Boston MA: Addison-Wesley.  09 August, 2005 < http://www.awprofessional.com/bookstore/product.asp?isbn=0321193687&rl=1>.

Larman, Craig.  2005.  Applying UML and Patterns.  Westford, MA: Prentice Hall.  09 August, 2005 <http://www.phptr.com/title/0131489062>.

Poseidon for UML. 2005.  Gentleware AG.  20 January, 2007 <http://www.gentleware.com/uml-software-pe.html>.

 

2.              Domain Model

(click on image for a scalable version)

 

1.              Revision History

Date

Version

Description

Author

06 Feb, 2006

1.0 – Elaboration Phase 1

Initial Revision.  Created from Use Case descriptions, SSDs, and Operation Contracts.

Bob Lavey

15 Oct, 2006

2.0 – Elaboration Phase 2

Updated objects, attributes, and associations discovered during analysis.

 Bob Lavey

11 Jan, 2007

3.0 – Elaboration Phase 3

Updated objects, attributes, and associations discovered during analysis.

 Bob Lavey

20 Jan, 2007

4.0 – Elaboration Phase 4

Updated objects, attributes, and associations discovered during analysis.  Renamed SystemState element Status based on Dr. Leavens’ review of Elaboration Phase 3.

 Bob Lavey