Object-oriented systems analysis: modeling the world in data
Object-oriented systems analysis: modeling the world in data
Object oriented design with applications
Object oriented design with applications
Object-oriented software engineering
Object-oriented software engineering
Object lifecycles: modeling the world in states
Object lifecycles: modeling the world in states
Object-oriented modeling and design
Object-oriented modeling and design
Object-oriented analysis (2nd ed.)
Object-oriented analysis (2nd ed.)
Analysis/architecture models to ASG models: enabling the transition
TRI-Ada '92 Proceedings of the conference on TRI-Ada '92
Ada 9X and CASE: a methods perspective
TRI-Ada '93 Proceedings of the conference on TRI-Ada '93
Enabling reuse with Ada generics
WADAS '93 Proceedings of the tenth annual Washington Ada symposium on Ada: Ada's role in software engineering
| Hi-index | 0.00 |
When the ancient Egyptians built the pyramids, they built them with a strong sturdy base, and then added layers in gradually smaller increments until the top came to a point. We visit these monuments today and marvel at their architectural ingenuity. Imagine—they had advanced to such a stage, that they were able to determine that the pyramids would stand a lot longer if they were built with the point at the top, instead of at the bottom. Why hasn't the software development community been able to achieve this same level of advancement?One of the big questions facing many software organizations today is choosing between Object-Oriented or Structured Analysis as the method for analyzing requirements. While many make this choice based on being trendy, or building on past experience, etc., they fail to realize that the result of their choice may be the equivalent of building an upside-down pyramid. The key to making the right choice is based on an in-depth understanding of the patterns that exist in the designs of systems in specific application groups. Our experience applying The Practical Ada Design Method (PAdaDM) across a variety of applications has identified that Communication Systems, Database Systems, and Control Systems have distinguishing patterns in how they aggregate Ada design objects. When analyzing the requirements for these systems, knowledge of these patterns is fundamental for choosing an analysis method that aggregates its information in ways that map to those of the final design.All systems will contain a mixture of data (object), process (function), and state (behavior) characteristics, but certain analysis methods choose one of these characteristics as its base, and then build the rest on top. If your system characteristics aren't distributed with the same percentages as the method expects, you're building an upside-down pyramid. So, lets stop choosing the trendiest method, and look for the one that lets us model like the Egyptians!