The document describes an executable model that allows testing software before implementation. It includes an outline, system configuration map, workflow chart, and execution example. The executable model uses tools like UML modeling, prototyping, and simulation to derive use cases, draw scenarios, design user screens, and map messages to steps. This allows demonstrating scenarios, reviewing designs, and generating test cases before development. The expected benefits are improved quality, increased productivity through simulation, improved business understanding, and prepared foundations for test automation.

1. Executable Model

2. Sections
Contents
1. Outline
2. System Configuration Map
3. Workflow Chart
4. Execution example
5. Expected Effect

3. Outline
 Based on the model that guaranteed traceability, 'Excutable model'
provides the environment that can be tested before implementation
through execution

4. Configuration Map
Use Case #1
Boundary
Control
Entity
Source Code

5. Components
Implementation Plan
 Tool
• StarUML NS (UML modeling tool)
• Prototyper (User UI drawing tool)
• Tool for a system Analyst
• Simulator (Tool that can be tested before development)
• Verify (Test automation tool)
 Model
• Web App Profile
• Simulation Profile
• Test Profile

6. Executable scenario
Implementation
 Derive Use Case
 Draw Use Case Scenario
• Derive user screen, business logic, data
• Derive business performance step
 With deduced user screen, utilizing 'Enki proto', design user screen
• Define required data while configuring user screen
• Define about action with button or screen
• Draw sample data set
 Draw Sequence Diagram
• Map 'Message of Sequence Diagram' onto 'Step of Scenario'
• Map 'Message' onto action with button or screen
• Map earlier derived screen onto 'Boundary'

7. Utilization Example
Implementation Plan
 Based on user requirement, after requirement analysis, utilize the executable model when
business manager demonstrates.
• Except implementation(Message) of Sequence, demonstrating screen unit movement
• To demonstrate, configure demonstrating data input remains as record
 In the phase before development, overall scenario review and design verification before
implementation when the design completed
• Based on inputted data for demonstration, review implementation through message linking of
sequence
 Generate test scenario based on the inputted data and Use Case scenario
• Leaving scenario and demonstration data, generate test scenario based on them
• Based on user screen design and correct test data, test automation is also available
• Need to configure an extra solution

8. Expected Benefit
 Before implementation, software quality improved and productivity
increased through simulation from screen unit of user to code
 Business understanding of developer improved through the flow of
screen unit and description
 Productivity increased through analysis / Design information and
traceability based test scenario management
 The foundation of test automation based on screen definition, the input
information of screen, etc. is prepared