Draft:System Anatomy: Difference between revisions
Content deleted Content added
m Legacypac moved page User:Berikman/System Anatomy to Draft:System Anatomy |
#REDIRECT System anatomy Tag: New redirect |
||
| Line 1: | Line 1: | ||
#REDIRECT [[System anatomy]] |
|||
{{Userspace draft|source=ArticleWizard|date=February 2011}} |
|||
A '''System Anatomy''' is simple visual description of a system, focusing on the dependencies between system capabilities. |
|||
The System Anatomy was first used in a project at Ericsson, and Jack Järkvik, is considered the inventor of the concept. After that, System Anatomies and the similar [[project_anatomy|Project Anatomies]] (also Integration Anatomies) have been used widely in different Ericsson projects and now they are being spread to other major companies with complex system development as well. |
|||
Anatomies can be said to be a human centric way of describing a system, since they are used as a means to obtain a common view of the system under development. |
|||
The anatomies are especially useful in development of large complex systems in integration driven development and as a means to coordinate agile development teams. |
|||
== History == |
|||
Advantages and limitations |
|||
The system anatomy, unlike its siblings (project anatomy, integration anatomy), is actually just another view of the system, different from product structures, UML-models and flow charts. By focusing on the system’s capabilities – both internal and money making ones – and the dependencies between those, the development team gets a common picture of the system to be developed, that is easier to grasp than many other models. |
|||
One of the key features of the system anatomy is its simplicity. That, of course, means that the anatomy cannot replace other models or design tools. It is only another way of describing the design, in SW tools, on paper or in the heads of the system engineers. |
|||
The system anatomy can be used as a starting point when creating an integration anatomy (aka project anatomy) that has more use as a project management tool. |
|||
== Example == |
|||
The following example is a simplified example of a system anatomy for an issue management system. |
|||
''This anatomy is drawn with the most basic capabilities at the top.The notation is that the work package at the end of the arrow is a dependant of the package at the beginning.'' |
|||
''In this example the anatomy also shows development progress (blue boxes).'' |
|||
[[image:System_Anatomy_Example.png|800px|Example of a system anatomy for a simple issue management system]] |
|||
== See also == |
|||
Project Anatomy |
|||
== References == |
|||
<!--- See http://en.wikipedia.org/wiki/Wikipedia:Footnotes on how to create references using <ref></ref> tags which will then appear here automatically --> |
|||
Lars Taxén (ED), The System Anatomy, Studentlitteratur, ISBN 978914407074 ('''not yet published''') |
|||
{{Reflist}} |
|||
== External links == |
|||
* [http://www.find-out.se Paipe (SW tool for Anatomies) FindOut Technologies] |
|||
<!--- Categories ---> |
|||
Latest revision as of 08:04, 15 February 2019
Redirect to: