Structured Systems Analysis (DFDs, ERDs, etc.)

7297 Views
0 Likes
0 Comments
As long as practitioners recognize that use case diagrams are optional and iconic (as opposed to schematic), they shouldn't have problems. The diagrams are useful, for example, on whiteboards as a way of sketching and framing an agenda while people are writing up and reviewing use case detail on index cards. The trouble starts, however, when pr...
5289 Views
2 Likes
2 Comments
This article describes a common pitfall of thinking of analysis and design together as a single process, and highlights the need to treat analysis and design as two separate processes. The author, points out that much of the UML standard, as it is explained today, is described in terms of design artifacts rather than analysis artifacts. Author: Co...
5397 Views
0 Likes
0 Comments
Describes the difference between a data dictionary and an implicit data dictionary and why an implicit data dictionary (or no data dictionary at all) may spell trouble for your project. Can data dictionaries be used with UML Use Cases or an XP methodology? Author: Conrad Weisert
9750 Views
5 Likes
1 Comments

"Business Analysis is about thinking what your solution should do, while Design is about how to make it happen using the technology available. Don't ever combine the two - you save nothing."

This paper by Brian Cooney, principal instructor at IRM, describes the need for clear separation between the two phases and the benefits this provides for a successful project outcome.

Author: Brian Cooney

Page 2 of 2First   Previous   1  [2]  Next   Last   











Copyright 2006-2020 by Modern Analyst Media LLC