TRADITIONAL
Traditionally, system analysis
produces an analysis of the problem, then system design creates a design to implement that analysis, and then code is written to carry out the design. Testing the code may result in bugs (fixed in code), design changes (requiring redoing design and code), or system changes (requiring redoing analysis and design and code). Changes at any level require work and testing at all lower levels. Often, only the code is changed, and analysis and design are never updated.
SHLAER-MELLOR
In Shlaer-Mellor, analysis of independent domains can happen in parallel and concurrently. Simulation and testing can occur at the analysis level. The model translates directly into code. Changes to one domain need not affect other domains. Since change at the analysis level translates directly into code, code and analysis stay in sync.
Flexible C++
Matthew Wilson
My approach to software engineering is far more pragmatic than it
is
theoretical--and no language better exemplifies this than C++.
BYTE Digest editors every month analyze and evaluate the best articles from Information Week, EE Times, Dr. Dobb's Journal, Network Computing, Sys Admin,
and dozens of other CMP publications—bringing
you critical news and information about wireless communication,
computer security, software development, embedded systems,
and more!
