System diagramming: Difference between revisions
Mr. MacKenty (talk | contribs) (Created page with "right|frame|Development<ref>http://www.flaticon.com/</ref> A system diagram is a visual model of a system, its components, and their interactions. Wi...") |
Mr. MacKenty (talk | contribs) No edit summary |
||
| Line 4: | Line 4: | ||
Diagrams, if properly constructed, are excellent mechanisms to communicate complex information to others, much like a well-made technical drawing. Designing is, among other things, an act of communication, so making sure one has an accurate and relatively easy to read account of design decisions is important for communicating that information to others.<ref>https://deseng.ryerson.ca/dokuwiki/design:system_diagram</ref> | Diagrams, if properly constructed, are excellent mechanisms to communicate complex information to others, much like a well-made technical drawing. Designing is, among other things, an act of communication, so making sure one has an accurate and relatively easy to read account of design decisions is important for communicating that information to others.<ref>https://deseng.ryerson.ca/dokuwiki/design:system_diagram</ref> | ||
== System flow charts == | |||
Creating system flow charts is a '''learned skill'''. You will need to practice. You will also need to create flow charts so they can be critiqued by a teacher. | |||
In general: | |||
# flowcharts must be of sufficient detail so another person can accurately describe how your program will work | |||
# flowcharts must not be cluttered. It is better to make 2 or 3 clear flowcharts rather than one visually cluttered one | |||
# flowcharts should be transferrable to [[pseudocode]] | |||
Revision as of 11:21, 21 April 2021
A system diagram is a visual model of a system, its components, and their interactions. With supporting documentation, it can capture all the essential information of a system's design. There are many variations of diagramming style.[2]
Diagrams, if properly constructed, are excellent mechanisms to communicate complex information to others, much like a well-made technical drawing. Designing is, among other things, an act of communication, so making sure one has an accurate and relatively easy to read account of design decisions is important for communicating that information to others.[3]
System flow charts[edit]
Creating system flow charts is a learned skill. You will need to practice. You will also need to create flow charts so they can be critiqued by a teacher.
In general:
- flowcharts must be of sufficient detail so another person can accurately describe how your program will work
- flowcharts must not be cluttered. It is better to make 2 or 3 clear flowcharts rather than one visually cluttered one
- flowcharts should be transferrable to pseudocode