ABSTRACT

A developer's knowledge of a computing system's requirements is necessarily imperfect because organizations change. Many requirements lie in the future and are unknowable at the time the system is designed and built. To avoid burdensome maintenance costs developers must therefore rely on a system's ability to change gracefully-its flexibility. Flex

part |2 pages

INTRODUCTION TO FLEXIBILITY

chapter 1|10 pages

The Serious Problems with IT Today

chapter 2|22 pages

The Reality of Imperfect Knowledge

chapter 3|12 pages

Outcome, Not Methodology

chapter 4|16 pages

Realignment of Roles

chapter 5|16 pages

UniverSIS: A Flexible System

part |2 pages

WHAT IS REQUIRED TO ACHIEVE FLEXIBILITY

chapter 6|8 pages

Guidelines for Flexible Software Design

chapter 7|18 pages

The Importance of Stable Identifiers

chapter 8|26 pages

Regulation: Managing Artificial Limits

chapter 9|20 pages

Stable Information Structures

chapter 10|22 pages

The Generic-Entity Cloud

part |2 pages

HOW TO DESIGN FLEXIBLE SOFTWARE SYSTEMS

part |2 pages

FLEXIBILITY: DELVING DEEPER

chapter 17|26 pages

A Closer Look at UniverSIS

chapter 20|14 pages

Regulatory GECs

chapter 21|18 pages

GEC Applications and Extensions

chapter 22|20 pages

GEC Aids