Timeline for Software design by pseudocoding?
Current License: CC BY-SA 3.0
12 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 3, 2012 at 20:43 | vote | accept | Gere | ||
| Jul 31, 2012 at 8:26 | comment | added | Yusubov | @Gerenuk, data flow diagrams can be made 1-to-1 with code flow. However, diagrams are generally used to see high level design and interaction between components/modules/use cases. | |
| Jul 31, 2012 at 8:22 | comment | added | Gere | @ElYusubov: Thanks for the explanation. It seems you also imply UML is more for presentation? For the actual design I don't put emphasis on it? In the end you propose 3 diagrams. Can they be made 1-to-1 with code to some extend. I mean on the opposite some things which work in diagram might not work with code - that I want to avoid. | |
| S Jul 31, 2012 at 8:20 | history | edited | Yusubov | CC BY-SA 3.0 |
Remove random formatting
|
| Jul 31, 2012 at 8:15 | review | Suggested edits | |||
| S Jul 31, 2012 at 8:20 | |||||
| Jul 31, 2012 at 4:24 | history | edited | Yusubov | CC BY-SA 3.0 |
Formatting
|
| Jul 30, 2012 at 21:50 | history | edited | kevin cline | CC BY-SA 3.0 |
spelling
|
| Jul 30, 2012 at 21:49 | comment | added | kevin cline | +1 for link to Pseudocode or Code. Just write the damn code. | |
| Jul 30, 2012 at 17:52 | history | edited | Yusubov | CC BY-SA 3.0 |
added a reference
|
| Jul 30, 2012 at 17:42 | history | edited | Yusubov | CC BY-SA 3.0 |
added 171 characters in body
|
| Jul 30, 2012 at 17:35 | history | edited | Yusubov | CC BY-SA 3.0 |
added 823 characters in body; added 306 characters in body
|
| Jul 30, 2012 at 17:29 | history | answered | Yusubov | CC BY-SA 3.0 |