1 Document Description

1.1 Purpose

1.2 Document overview

1.3 Reading suggestions

1.4 Document dependencies

1.4.1 Documents which affect the architecture

1.4.2 Documents which the architecture affects

1.5 Distribution

1.6 Glossary

2 System Overview

2.1 The customer

2.2 Background

2.2.1 ArgoUML

2.2.2 Base-lining

2.3 System description

2.4 System environment

2.5 Users of the system

3 Use-cases

3.1 Purpose

3.2 Use-case notation

3.2.1 Notation

3.2.2 Use-case identity number

3.2.3 User categories

3.2.4 Traceable to requirement

3.3 Use-cases

4 Architectural Design Decisions

4.1 Module identification

4.2 Development environment

4.2.1 Programming language

4.2.2 Coding environment

4.2.3 Testing framework

4.2.4 CVS

4.3 Properties

4.3.1 Testability

4.3.2 Code reuseability

4.3.3 Extendability

4.3.4 General solution

4.4 Xerces

5 Design Method

5.1 Chosen and discarded methods

5.2 JOOM

5.2.1 Analysis phase

5.2.1.1 Object identification

5.2.1.2 Object classification

5.2.1.3 Class description

5.2.1.4 Description of Relations

5.2.1.5 Testing

5.2.2 Design phase

5.2.2.1 Creation of the system design

5.2.2.2 Infrastructure

5.2.2.3 Detailed design

5.2.3 Adaption of JOOM

6 Architecture Description

6.1 Overview and layering

6.2 Module and Architecture Entity Description

6.2.1 Notation

6.2.2 GUI

6.2.3 Model

6.2.4 XML-parser

6.2.5 Engine

6.2.6 UMLInterface

6.2.6.1 ModelFacade

6.2.7 Files

6.2.8 Document

6.2.9 Template

6.3 ArgoPrint template language

6.3.1 Notation

6.3.2 If-Then-Else

6.3.3 Bind

6.3.4 Call

6.3.5 Iterate

6.3.6 methodCalled()

6.3.7 Depicting example

6.4 Reflections on properties

6.4.1 Testability

6.4.2 Code reusability

6.4.3 Extendability

6.4.4 General solution

7 Reflections on Requirements

7.1 Functional requirements

7.2 Non-functional requirements

8 References

8.1 ArgoPrint documents

8.2 Book

8.3 Internet