#+SETUPFILE: ../../../template/level-2.org
#+TITLE: Application System Module Guide Template
#+DATE: <2014-08-20 Wed 00:00>
#+AUTHOR: vaeringjar
#+EMAIL: vaeringjar@land
#+DESCRIPTION: Version of the ASMG template.
#+KEYWORDS: template

This template requires needs a format check.

* [Project Title]
** [Subtitle or short description]
** [Authors]
** [Team or organization that is writing this document]
** Versions log
| DATE | V# | VERSION NOTES | [yyyy-mm-dd] |
|------+----+---------------+--------------|
|      |    |               |              |
|      |    |               |              |
|      |    |               |              |
|      |    |               |              |

* Table of contents

* [application name] System
Related Documents Requirements are located
[at the foobar wiki].

System Description Foobar makes a great travel companion.

Engineering Concerns Notes about reliability and security. Safety is a
non-issue with the foobar because none of the user have a chance of
foobaring themselves with anything sharp.

Likely Changes Hardware H1. hardware change H2. hardware change
H3. etc

Software

Wetware

Unlikely Changes Assumptions

* [application name] Module Guide
Goals of the Module Structure Design
Principle

* Subsystem1
Description of subsystem1 Behaviour Hiding
Modules Module name Service Secret Associated Changes Module2 name
Module3 name, etc Device Interface Modules Software Design Hiding
Modules Potential Issues Subsystem Design Markup Illustration

* Subsystem2

* Subsystem3, etc

* System Markup Illustration
* Appendices
Module Hierarchy [some cool picture of the hierarchical structure of
the foobar design with concern to available services, secrets, and
associated changes, but not to a particular use case or
implementation]

** Glossary
System - Hardware, Software, Wetware, often
affected or subjugated in that order, either ascending or
descending. In some cases, the lines of the foobar blur and some parts
do not seem so exclusive.  Hardware - The solids, materials, rocks, or
sticks.  Software - The electromagnetism stuffs.  Wetware - (2) People
http://www.catb.org/jargon/html/W/wetware.html Design - With concern
to modules that make the foobar.  Architecture - With concern to the
environment(s) where the foobar lives.

* Acknowledgements
This design document, the Application System Module Guide Template, is
based on the FWS design document by Professor David M. Weiss, with a
format conforming more to APA.

* License
© 2011 Alan Shea Anderson-Priddy Provided the License and
Acknowledgements sections remain intact, though you may add addendums
for documentation purposes, anyone may use this document, modify or
redistribute it under the licenses either the GNU-FDL 1.3 (or later)
or CC-BY 2.0 (or later), whichever pleases the user.
