Solution

Full form: CASE = Computer-Aided Software Engineering

CASE Diagram - Components

┌─────────────────────────────────────────┐
│           CASE Environment              │
│  ┌──────────┐  ┌──────────┐  ┌────────┐ │
│  │ Upper CASE│  │Lower CASE│ │Integrated│
│  │(Front-end)│  │(Back-end)│ │ CASE   │ │
│  └──────────┘  └──────────┘  └────────┘ │
│                Repository               │
│  ┌─────────────────────────────────┐    │
│  │  Central Data Dictionary / DB   │    │
│  └─────────────────────────────────┘    │
└─────────────────────────────────────────┘

Detailed Components:

1. Upper CASE (Front-end / Planning Tools): Supports early SDLC - requirement analysis, DFD/ERD/UML modelling, prototyping, project planning. Ex: Rational Rose, Visible Analyst.

2. Lower CASE (Back-end / Development Tools): Supports later SDLC - code generation, compilation, testing, debugging, reverse engineering. Ex: Compilers, debuggers, test generators.

3. Integrated CASE (I-CASE / Workbench): Combines upper + lower + repository for full lifecycle. Provides seamless integration.

4. Central Repository / Data Dictionary: Heart of CASE - stores all artifacts (requirements, diagrams, code, tests). Ensures consistency, version control.

5. Tools Framework: UI, methodology support, portability, integration services.

Upper = analysis/design, Lower = implementation/testing, I-CASE = end-to-end.