“DATTT” - Software Requirements Specification for Web Application (v0.1)        16/11/2014

“DATTT”

Software Architecture Document

Rational Unified Process

 

 

Version 0.1

 

 

Revision History

Date

Version

Description

Author

16/11/2014

0.1

Erstellung SAD

Lukas Marschar

17/11/2014

1.0

Bilder und kleine Texte eingefügt

Markus Barthel

 

 

 

 

 

 

 

 


Table of Contents

Revision History

Table of Contents

Introduction

Purpose

Scope

Definitions, Acronyms and Abbreviations

References

Overview

Architectural Representation

Architectural Goals and Constraints

Use-Case View

Use-Case Realizations

Logical View

Overview

Architecturally Significant Design Packages

Process View

Deployment View

Implementation View

Overview

Layers

Data View

Size and Performance

Quality


  1. Introduction

  1. Purpose

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.

  1. Architectural Representation

The play framework, which is used for this web application, uses MVC (Model-View-Control) for structuring.

  1. Architectural Goals and Constraints

The primary architectural goals are a flexible software design, safety and privacy.

  1. Logical View

  1. Overview

Das Schaubild verdeutlicht die MVC-Architektur. Hierbei zu beachten ist, dass der Controller als Mittler zwischen View und Model agiert. Vom View empfangene Eingbedaten werden im Controller verarbeitet und  je nach Aktion an das Model weitergeleitet. Umgekehrt werden Daten aus dem Model über den Controller an den View weitergegeben.


  1. Architecturally Significant Design Packages

  1. Process View

There’s only one process to take into account. The J2EE model automatically handles threads which are instances of this process.


  1. Data View

  1. Size and Performance

[n/a]

  1. Quality

The Software will be released only with basic functions. For the further development of the software, each part of the software should be able to be changed withoud any influence to other parts. So the software architecture should provide extensibility.

Our users can save many personal informations and important tasks in our software, so reliability and data security is another important aspect, which the software architecture can contribute.

        Page  of