Skip to content
Marcus Ottosson edited this page Aug 28, 2014 · 2 revisions

An architectural scenario is a crisp, concise description of a situation that the system is likely to face in its production environment, along with a definition of the response required of the system.

Scenario 1

# Overview
How the user typically interacts with the system.

# System state
User has finished working on a task and is ready
to commit his work for review by peers.

Scenario 2

# Publishing multiple INSTANCES
2.1: User configures INSTANCES to be pyblished
2.2: User runs APP
2.3: User pyblishes

Language, software and platform agnostic, feature film-strength quality assurance for content.

Table of contents

Architecture

Developer Resources

Strategies

More

Community

Clone this wiki locally