Recent changes to Software Architecture

Software Architecture modified by Johannes Lang

Johannes Lang — Tue, 12 Aug 2014 07:58:11 -0000

--- v2
+++ v3
@@ -1,16 +1,11 @@
-We acknowledge that this document uses material from the arc 42 architecture 
-template, <http: www.arc42.de="">. Created by Dr. Peter Hruschka & Dr. Gernot Starke.
+SASUnit is a unit testing framework for SAS(TM)-programs.
+The intended users of the system are software developers, and most of the stakeholders are software developers as well.

-1. [Introduction and Goals](Introduction and Goals)
-2. [Architecture Constraints](Architecture Constraints)
-3. [System Scope and Context](System Scope and Context)
-4. [Solution Strategy](Solution Strategy)
-5. [Building Block View](Building Block View)
-6. [Runtime View](Runtime View)
-7. [Deployment View](Deployment View)
-8. [Concepts](Concepts)
-9. [Design Decisions](Design Decisions)
-10. [Quality Scenarios](Quality Scenarios)
-11. [Technical Risks](Technical Risks)
-12. [Glossary](Glossary)
+As we started to document the software architecture of SASUnit, we found that we do not need a specific architecture documentation, because of the following reasons:

+* To describe the use of the system (and the necessary internals), there is already a documentation area called [User's Guide].
+* To discuss architectural decisions, the sourceforge ticketing system can be used.
+* The knowledge about the architecture is currently spread over multiple persons (mostly employees of HMS) who are able and willing to communicate it to new developers.
+* SASUnit is currently not integrated into a larger business solution which would justify a separate architecture documentation.
+
+Instead of an architecture document, an architecture discussion forum will be established.

WikiPage Software Architecture modified by Johannes Lang

Johannes Lang — Tue, 31 Jul 2012 13:52:18 -0000

--- v1
+++ v2
@@ -1,16 +1,16 @@
 We acknowledge that this document uses material from the arc 42 architecture 
 template, . Created by Dr. Peter Hruschka & Dr. Gernot Starke.
 
-1. [Introduction and Goals]
-2. [Architecture Constraints]
-3. [System Scope and Context]
-4. [Solution Strategy]
-5. [Building Block View]
-6. [Runtime View]
-7. [Deployment View]
-8. [Concepts]
-9. [Design Decisions]
-10. [Quality Scenarios]
-11. [Technical Risks]
-12. [Glossary]
+1. [Introduction and Goals](Introduction and Goals)
+2. [Architecture Constraints](Architecture Constraints)
+3. [System Scope and Context](System Scope and Context)
+4. [Solution Strategy](Solution Strategy)
+5. [Building Block View](Building Block View)
+6. [Runtime View](Runtime View)
+7. [Deployment View](Deployment View)
+8. [Concepts](Concepts)
+9. [Design Decisions](Design Decisions)
+10. [Quality Scenarios](Quality Scenarios)
+11. [Technical Risks](Technical Risks)
+12. [Glossary](Glossary)

WikiPage Software Architecture modified by Johannes Lang

Johannes Lang — Tue, 31 Jul 2012 13:50:31 -0000

We acknowledge that this document uses material from the arc 42 architecture template, . Created by Dr. Peter Hruschka & Dr. Gernot Starke. 1. [Introduction and Goals] 2. [Architecture Constraints] 3. [System Scope and Context] 4. [Solution Strategy] 5. [Building Block View] 6. [Runtime View] 7. [Deployment View] 8. [Concepts] 9. [Design Decisions] 10. [Quality Scenarios] 11. [Technical Risks] 12. [Glossary]