Wikipedia

Systems design

(Redirected from System designer)

The basic study of system design is the understanding of component parts and their subsequent interaction with one another.[1]

Systems design has appeared in a variety of fields, including sustainability,[2] computer/software architecture,[3] and sociology.[4]

Product Development

edit

If the broader topic of product development "blends the perspective of marketing, design, and manufacturing into a single approach to product development,"[5] then design is the act of taking the marketing information and creating the design of the product to be manufactured.

Thus in product development, systems design involves the process of defining and developing systems, such as interfaces and data, for an electronic control system to satisfy specified requirements. Systems design could be seen as the application of systems theory to product development. There is some overlap with the disciplines of systems analysis, systems architecture and systems engineering.[6][7]

Physical design

edit

The physical design relates to the actual input and output processes of the system. This is explained in terms of how data is input into a system, how it is verified/authenticated, how it is processed, and how it is displayed. In physical design, the following requirements about the system are decided.

  1. Input requirement,
  2. Output requirements,
  3. Storage requirements,
  4. Processing requirements,
  5. System control and backup or recovery.[8]

Put another way, the physical portion of system design can generally be broken down into three sub-tasks:

  1. User Interface Design
  2. Data Design
  3. Process Design

Web System design

edit

Online websites, such as Google, Twitter, Facebook, Amazon and Netflix are used by millions of users worldwide. A scalable, highly available system must be designed to accommodate an increasing number of users. Here are the things to consider in designing the system:

  1. Functional and non functional requirements
  2. Capacity estimation
  3. Database to use, Relational or NoSQL
  4. Vertical scaling, Horizontal scaling, Shard
  5. Load Balancing
  6. Primary-secondary Replication
  7. Cache and CDN
  8. Stateless and Stateful servers
  9. Datacenter georouting
  10. Message Queue, Publish-Subscribe Architecture
  11. Performance Metrics Monitoring and Logging
  12. Build, test, configure deploy automation
  13. Finding single point of failure
  14. API Rate Limiting
  15. Service Level Agreement

See also

edit

References

edit
  1. ^ Papanek, Victor J. (1984) [1972]. Design for the Real World: Human Ecology and Social Change (2nd ed.). Chicago: Academy Chicago. p. 276. ISBN 0897331532. OCLC 12343986.
  2. ^ Blizzard, Jacqualyn; Klotz, Leidy (2012). "A framework for sustainable whole systems design". R Design Studies. 33 (5): 456–479. doi:10.1016/j.destud.2012.03.001.
  3. ^ Lukosh, Heidi; Bekebrede, Geertje; Kurapati, Shalini; Lukosch, Stephan (2018). "A Scientific Foundation of Simulation Games for the Analysis and Design of Complex Systems". Simulation & Gaming. 49 (3): 279–314. doi:10.1177/1046878118768858. PMC 6187265. PMID 30369775.
  4. ^ Werner, Ulrich (September 1987). "Critical heuristics of social systems design". European Journal of Operational Research. 31 (3): 276-283. doi:10.1016/0377-2217(87)90036-1.
  5. ^ Ulrich, Karl T.; Eppinger, Steven D. (2000). Product Design and Development (Second ed.). Boston: Irwin McGraw-Hill.
  6. ^   This article incorporates public domain material from Federal Standard 1037C. General Services Administration. Archived from the original on 2022-01-22.
  7. ^   This article incorporates public domain material from Dictionary of Military and Associated Terms. United States Department of Defense.
  8. ^ Arden, Trevor (1991). Information technology applications. London: Pitman. ISBN 978-0-273-03470-4.

Further reading

edit
edit
 
Look up systems design in Wiktionary, the free dictionary.
Retrieved from "https://en.wikipedia.org/w/index.php?title=Systems_design&oldid=1236957349"