Rapid Prototyping and Top Down Development

🏗️ ViewTouch Development Philosophy

🎯 Core Principle

ViewTouch is all about building the interface first, then making the components of the Interface operate as desired.

---

📐 Top-Down Development Approach

The ViewTouch graphical interface allows and encourages the top-down, rapid development of software prototypes.

🏛️ Historical Development

The development of ViewTouch itself has always been a top-down process:

1. First Elements: Interface components (pages and buttons)
2. Initial State: No specific functionality attached
3. Evolution: Programmers then assign functionality to components
4. Result: User interface becomes a harbinger of the full-scale, functional software

---

🔄 Development Workflow

📋 Step 1: Interface Specification

• Overview Creation: Formulate system overview
• Subsystem Specification: Define (but don't detail) first-level subsystems
• Interface as Blueprint: Not-yet-functional interface reveals upcoming functions

⚙️ Step 2: Functionality Assignment

• Component Activation: Assign functionality to buttons and pages
• Iterative Refinement: Each component gains usefulness in greater detail
• User Feedback: Incorporate refinements based on user requirements

🏁 Step 3: System Completion

• Subsystem Development: Build many levels of subsystems
• Specification Fulfillment: Original interface specification becomes base elements
• Full Realization: Complete functional system emerges

---

🎨 Interface as Development Tool

📊 Dual Role of Interface

The ViewTouch interface serves as both product and specification tool:

• Product: The actual user interface users interact with
• Specification: Blueprint guiding development decisions
• Prototype: Rapid visualization of system capabilities
• Guide: Reveals required functionality and user workflows

🔄 Iterative Enhancement