NAP
Software Architecture Document
Version <1.0>
Revision History
| Date | Version | Description | Author |
|---|---|---|---|
| 26/11/17 | 1.0 | added class diagram | Patrick Siewert |
| 01/07/18 | 2.0 | updated class diagram | Patrick Siewert |
| 01/07/18 | 2.1 | added Factory Pattern | Patrick Siewert |
Table of Contents
| 1. Introduction |
|---|
| 1.1 Purpose |
| 1.2 Scope |
| 1.3 Definitions, Acronyms, and Abbreviations |
| 1.4 References |
| 1.5 Overview |
| 2. Architectural Representation |
| 3. Architectural Goals and Constraints |
| 4. Use-Case View |
| 4.1 Use-Case Realizations |
| 5. Logical View |
| 5.1 Overview |
| 5.2 Architecturally Significant Design Packages |
| 6. Process View |
| 7. Deployment View |
| 8. Implementation View |
| 8.1 Overview |
| 8.2 Layers |
| 9. Data View (optional) |
| 10. Size and Performance |
| 11. Quality |
Software Architecture Document
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 significant architectural decisions which have been made on the system.
This document describes the architecture used in the NAP projekt. As we neather have a client-server architecture nor a database, this document only contains the mvc-pattern and the factory pattern
n/a
n/a
n/a
Model-View-Controller pattern
Goal is to apply the MVC pattern to our project. Since we are using Unity we do not have an external MVC framework but we use the Unity architecture which is similar to MVC. The difference is, that the view and the controller classes are not clearly divided.
The aim of the Factory Pattern is to create complex objects more easily. Instead of creating an object with the “new” operator, you call a method of the factory class.
The factory class enables you to create objects step by step. In this class, there are methods like “withSpeed(int speed)” which all return an instance of the factory class. When ready, the object will be created by a method like “get()” which does not return an instance of the factory class, but an instance of the object you want to create.
With the Factory Pattern, it is easier to create objects with many parameters that have to be set in the constructor. This is not the case in our project but still, this pattern is useful for us. Since we are working with the Unity Component Pattern we often have to call the method “getComponent” when changing attributes of an object at runtime. With the Factory Pattern, we only have to do this step once and afterwards just call our self-defined methods in the factory class.
n/a
n/a
n/a
n/a
n/a
n/a
n/a
n/a