Editing Software design (section)

== Design concepts ==

Design concepts provide a designer with a foundation from which more sophisticated methods can be applied. A set of design concepts has evolved including:

*[[Abstraction (computer science)|Abstraction]] - Abstraction is the process or result of generalization by reducing the information content of a concept or an observable phenomenon, typically to retain only information that is relevant for a particular purpose. It is an act of Representing essential features without including the background details or explanations.
*[[Program refinement|Refinement]] - It is the process of elaboration. A hierarchy is developed by decomposing a macroscopic statement of function in a step-wise fashion until programming language statements are reached. In each step, one or several instructions of a given program are decomposed into more detailed instructions. Abstraction and Refinement are complementary concepts.
*[[Modularity]] - Software architecture is divided into components called modules.
*[[Software Architecture]] - It refers to the overall structure of the software and the ways in which that structure provides conceptual integrity for a system. Good software architecture will yield a good return on investment with respect to the desired outcome of the project, e.g. in terms of performance, quality, schedule and cost.
*[[Control Hierarchy]] - A program structure that represents the organization of a program component and implies a hierarchy of control.
*[[Structural Partitioning]] - The program structure can be divided horizontally and vertically. Horizontal partitions define separate branches of modular hierarchy for each major program function. Vertical partitioning suggests that control and work should be distributed top-down in the program structure.
*[[Data Structure]] - It is a representation of the logical relationship among individual elements of data.
*[[Software Procedure]] - It focuses on the processing of each module individually.
*[[Information Hiding]] - Modules should be specified and designed so that information contained within a module is inaccessible to other modules that have no need for such information.

In his object model, [[Grady Booch]] mentions [[Abstraction (computer science)|Abstraction]], [[Encapsulation (computer programming)|Encapsulation]], [[Modularity|Modularisation]], and [[Hierarchy]] as fundamental software design principles.<ref>{{cite book|last1=Booch|first1=Grady|title=Object-Oriented Analysis and Design with Applications|date=2004|publisher=Addison Wesley|location=MA, US|isbn=0-201-89551-X|edition=3rd|url=http://dl.acm.org/citation.cfm?id=975416|access-date=30 January 2015|display-authors=etal}}</ref> The acronym PHAME (Principles of Hierarchy, Abstraction, Modularisation, and Encapsulation) is sometimes used to refer to these four fundamental principles.<ref>{{cite book|last1=Suryanarayana|first1=Girish|title=Refactoring for Software Design Smells|date=November 2014|publisher=Morgan Kaufmann|isbn=978-0128013977|pages=258}}</ref>