Benutzer:Andreas Plank/Design-Types: Unterschied zwischen den Versionen

Aus Open Source Ecology - Germany
Zur Navigation springen Zur Suche springen
(Die Seite wurde neu angelegt: „== Explaining the dimensions == {| class="vertical-align-top" style="border-collapse: collapse;" |+ Software Design-Types after http://design-types.net |- | s…“)
 
(translate)
Zeile 1: Zeile 1:
== Explaining the dimensions ==
+
<languages/>
 +
== <translate>Explaining the dimensions</translate> ==
  
 
{| class="vertical-align-top" style="border-collapse: collapse;"
 
{| class="vertical-align-top" style="border-collapse: collapse;"
|+ Software Design-Types after http://design-types.net
+
|+ <translate>Software Design-Types after http://design-types.net</translate>
 
|-
 
|-
| style="background-color:#d1fedd;width:350px;" | '''Simple''' means:
+
| style="background-color:#d1fedd;width:350px;" | <translate>'''Simple''' means:
 
* to keep code simple for better understandability
 
* to keep code simple for better understandability
 
* to omit unnecessary things (lower risk; fewer bugs)
 
* to omit unnecessary things (lower risk; fewer bugs)
Zeile 10: Zeile 11:
 
* to prefer explicit solutions instead of implicit ones
 
* to prefer explicit solutions instead of implicit ones
 
* etc.
 
* etc.
| <br/><br/><br/><big>VS.</big>  
+
</translate>
| style="background-color:#d1fedd;width:350px;" | '''Powerful''' means:
+
| <br/><br/><br/><big><translate>VS.</translate></big>  
 +
| style="background-color:#d1fedd;width:350px;" | <translate>'''Powerful''' means:
 
* to build powerful and generalized solutions
 
* to build powerful and generalized solutions
 
* to have flexibility/extensibility by foresighted design
 
* to have flexibility/extensibility by foresighted design
Zeile 17: Zeile 19:
 
* to master complexity
 
* to master complexity
 
* etc.
 
* etc.
 +
</translate>
 
|-
 
|-
| style="background-color:#dce3f3;width:350px;" | '''Abstract''' means:
+
| style="background-color:#dce3f3;width:350px;" | <translate>'''Abstract''' means:
 
* to think in concepts and abstractions
 
* to think in concepts and abstractions
 
* to locus on the big picture and component interactions
 
* to locus on the big picture and component interactions
Zeile 24: Zeile 27:
 
* to build models otttie real world
 
* to build models otttie real world
 
* etc.
 
* etc.
| <br/><br/><br/><big>VS.</big>
+
</translate>
| style="background-color:#dce3f3;width:350px;" | '''Concrete''' means:
+
| <br/><br/><br/><big><translate>VS.</translate></big>
 +
| style="background-color:#dce3f3;width:350px;" | <translate>'''Concrete''' means:
 
* to think in code or simultaneously transfer ideas into code immediately
 
* to think in code or simultaneously transfer ideas into code immediately
 
* to optimize algorithms for better performance
 
* to optimize algorithms for better performance
 
* to understand systems by reading the code
 
* to understand systems by reading the code
 
* etc.
 
* etc.
 +
</translate>
 
|-
 
|-
| style="background-color:#fee6da;width:350px;" | '''Pragmatic''' means:
+
| style="background-color:#fee6da;width:350px;" | <translate>'''Pragmatic''' means:
 
* to fulfill requirements asap
 
* to fulfill requirements asap
 
* to focus on customer needs to guarantee a value
 
* to focus on customer needs to guarantee a value
Zeile 37: Zeile 42:
 
* to bring others down to earth
 
* to bring others down to earth
 
* etc.
 
* etc.
| <br/><br/><br/><big>VS.</big>
+
</translate>
| style="background-color:#fee6da;width:350px;" | '''Idealistic''' means:
+
| <br/><br/><br/><big><translate>VS.</translate></big>
 +
| style="background-color:#fee6da;width:350px;" | <translate>'''Idealistic''' means:
 
* to make things right—not only 80%
 
* to make things right—not only 80%
 
* to consider all aspects not only functional ones
 
* to consider all aspects not only functional ones
Zeile 44: Zeile 50:
 
* not to misuse existing concepts, APls, etc.
 
* not to misuse existing concepts, APls, etc.
 
* etc.
 
* etc.
 +
</translate>
 
|-
 
|-
| style="background-color:#fefacd;width:350px;" | '''Robust''' means:
+
| style="background-color:#fefacd;width:350px;" | <translate>'''Robust''' means:
 
* to protect applications against risks and potential bugs
 
* to protect applications against risks and potential bugs
 
* to define and adhere to standards
 
* to define and adhere to standards
Zeile 51: Zeile 58:
 
* to use proven solutions which stood the test of time
 
* to use proven solutions which stood the test of time
 
* etc.
 
* etc.
| <br/><br/><br/><big>VS.</big>
+
</translate>
| style="background-color:#fefacd;width:350px;" | '''Technologic''' means:
+
| <br/><br/><br/><big><translate>VS.</translate></big>
 +
| style="background-color:#fefacd;width:350px;" | <translate>'''Technologic''' means:
 
* to use new. modern and more productive technologies and to get rid or legacy
 
* to use new. modern and more productive technologies and to get rid or legacy
 
* to evolve with technology to be more competitive
 
* to evolve with technology to be more competitive
 
* to broaden your personal horizon
 
* to broaden your personal horizon
 
* etc.
 
* etc.
 +
</translate>
 
|}
 
|}

Version vom 10. September 2018, 11:10 Uhr

Sprachen:
Deutsch • ‎English

Explaining the dimensions

Software Design-Types after http://design-types.net
Simple means:
  • to keep code simple for better understandability
  • to omit unnecessary things (lower risk; fewer bugs)
  • to reduce complexity
  • to prefer explicit solutions instead of implicit ones
  • etc.



VS.
Powerful means:
  • to build powerful and generalized solutions
  • to have flexibility/extensibility by foresighted design
  • to have configurable solutions
  • to master complexity
  • etc.
Abstract means:
  • to think in concepts and abstractions
  • to locus on the big picture and component interactions
  • to know all potential consequences ol a change -
  • to build models otttie real world
  • etc.



VS.
Concrete means:
  • to think in code or simultaneously transfer ideas into code immediately
  • to optimize algorithms for better performance
  • to understand systems by reading the code
  • etc.
Pragmatic means:
  • to fulfill requirements asap
  • to focus on customer needs to guarantee a value
  • to omit unnecessary things
  • to bring others down to earth
  • etc.



VS.
Idealistic means:
  • to make things right—not only 80%
  • to consider all aspects not only functional ones
  • to know that everything has its right place
  • not to misuse existing concepts, APls, etc.
  • etc.
Robust means:
  • to protect applications against risks and potential bugs
  • to define and adhere to standards
  • to avoid too much magic and complexity to reduce risks
  • to use proven solutions which stood the test of time
  • etc.



VS.
Technologic means:
  • to use new. modern and more productive technologies and to get rid or legacy
  • to evolve with technology to be more competitive
  • to broaden your personal horizon
  • etc.