vBy
1990, MIS organizations had learned (more or less) how to build
predictable and reliable big systems — using methodologies that prescribe
ways to build high-quality systems, and CASE (computer-aided software
engineering) tools to support analysts, designers, and developers in building bigger
systems better.
²A
methodology is a formal prescription for describing how software
should be built. They can range from loose frameworks describing basic design
approaches to 60-book encyclopedias that define every step and function required
to build an application.
²Fundamental
insight: software design is a formal process.
²CASE
tools offer ways to use computers to help automate the design process and the
associated methodologies.