Difference between revisions of "General Architecture Design"

From EUDP
Jump to: navigation, search
(How)
 
(6 intermediate revisions by 2 users not shown)
Line 1: Line 1:
<imagemap>
+
<imagemap>Image:GeneralArchitectureDesign.png|
 
+
rect 148 89 237 144 [[System_Architecture_Design|System Architecture Design]]
Image:ArchitectureDesignOverview_img.gif
+
rect 151 248 233 304 [[Block_Interface_Design|Block Interface Design]]
 +
rect 153 327 233 384 [[Selecting_Technical_Platform|Selecting Technical Platform]]
 +
rect 155 409 233 465 [[Design_Partitioning|Design Partitioning]]
 +
#<!-- Created by Online Image Map Editor (http://www.maschek.hu/imagemap/index) -->
 +
desc none
 +
</imagemap>
  
 
+
==What==
  poly    45 253 103 253 103 272 45 272 45 253    [[Architecture Dynamics]]
+
  poly    43 272 104 272 104 291 43 291 43 272    [[Architecture Dynamics]]
+
  poly    37 167 112 167 112 186 37 186 37 167  [[Subsystem Design]]
+
  poly    52 186 96 186 96 205 52 205 52 186    [[Subsystem Design]]
+
  poly    52 82 96 82 96 101 52 101 52 82    [[Design Criteria]]
+
  poly    50 101 98 101 98 120 50 120 50 101    [[Design Criteria]]
+
  
 +
A system design
  
</imagemap>
+
==How==
 +
 
 +
'''The Dish'''
 +
 
 +
A system design with specification of the technical platform, a software architecture and hardware block diagram.
 +
 
 +
'''Ingredients'''
 +
 
 +
* Specification from [[General Analysis]]
 +
 
 +
'''Process'''
 +
 
 +
Using the previous specifications it is time to partition. The process of partitioning is a process of determining the best, most economical division between hardware and software within the given constraints.
 +
 
 +
Therefore the activities in this phase is highly parallel and iterative. The developer has to repeat the same process over and over until a satisfying design has been established.
 +
 
 +
==Why==
 +
 
 +
Having analysed the Problem Domain, built a general architecture, fixed the requirements in a formal way and specified the interfaces, a static block architecture has been established without considering how it shall be developed.
 +
 
 +
Likewise the behaviour of of the system has been established through analysis of the Usage Domain and the interfaces ended in a specification in Activity Diagrams showing the dynamics of the system.
  
[[Design Criteria]]
+
Now it is time to consider how these specifications can be designed into a robust construction obeying the found constraints. This is the time where the developer starts to think ''How can this be designed and implemented''.
  
[[Subsystem Design]]
+
The design specifications are the base for the Quotation process, where the developer sets up a development plan and calculates the expected costs.
  
[[Architecture Dynamics]]
+
The design specifications are also the base for the development - the Realisation - of the product when the customer has accepted the quote.

Latest revision as of 08:40, 26 September 2016

System Architecture DesignBlock Interface DesignSelecting Technical PlatformDesign PartitioningGeneralArchitectureDesign.png

What

A system design

How

The Dish

A system design with specification of the technical platform, a software architecture and hardware block diagram.

Ingredients

Process

Using the previous specifications it is time to partition. The process of partitioning is a process of determining the best, most economical division between hardware and software within the given constraints.

Therefore the activities in this phase is highly parallel and iterative. The developer has to repeat the same process over and over until a satisfying design has been established.

Why

Having analysed the Problem Domain, built a general architecture, fixed the requirements in a formal way and specified the interfaces, a static block architecture has been established without considering how it shall be developed.

Likewise the behaviour of of the system has been established through analysis of the Usage Domain and the interfaces ended in a specification in Activity Diagrams showing the dynamics of the system.

Now it is time to consider how these specifications can be designed into a robust construction obeying the found constraints. This is the time where the developer starts to think How can this be designed and implemented.

The design specifications are the base for the Quotation process, where the developer sets up a development plan and calculates the expected costs.

The design specifications are also the base for the development - the Realisation - of the product when the customer has accepted the quote.