= SoftwareArchitecture =
Extracted and adapted from http://www.bredemeyer.com/pdf_files/ArchitectureDefinition.PDF

== Architecture Views ==

=== Conceptual Architecture ===
The Conceptual Architecture identifies the high-level components of the system, and the relationships
among them. Its purpose is to direct attention at an appropriate decomposition of the system without delv-
ing into details. 

Goals:
 * identification of components and allocation of responsibilities to components

=== Logical Architecture ===
In Logical Architecture, the externally visible properties of the components are made precise and unambiguous through well-defined interfaces and component specifications, and key architectural mechanisms are detailed. 

Goals:
 * design of component interactions, connection mechanisms and protocols (exchanged messages); 
 * interface design and specification; providing contextual information for component users

=== Execution Architecture ===
An Execution Architecture is created for distributed or concurrent systems. The process view shows the
mapping of components onto the processes of the physical system, with attention being focused on such
concerns as throughput and scalability. 

 * assignment of the runtime component instances to processes,threads and address spaces; 
 * how they communicate and coordinate; 
 * how physical resources are allocated to them

== UML simple steps ==
Reference: http://www.sparxsystems.com/resources/tutorial/uml_tutorial2.html

Steps:
 * Create use cases based on the user goals and how those goals are achieved by interacting with the system
 * Detail each use case with a best case scenario
 * With the details of the use cases, begin to construct a domain model (high level business objects), sequence diagrams, collaboration/communication diagrams and user interface models. These describe the 'things' in the new system, the way those things interact and the interface a user will use to execute use case scenarios.
 * With the domain model start to create a class model.
 * The class model is a precise specification of the objects in the system, their data or attributes and their behaviour or operations. 
 * A component represents a deployable chunk of software that collects the behaviour and data of one or more classes and exposes a strict interface to other consumers of its services. So from the Class Model a Component Model is built to define the logical packaging of classes. 


http://agilemodeling.com/essays/agileArchitecture.htm

http://www.sparxsystems.com.au/resources/uml2_tutorial/

http://agilemodeling.com/artifacts/useCaseDiagram.htm

http://agilemodeling.com/artifacts/crcModel.htm

http://agilemodeling.com/artifacts/robustnessDiagram.htm