Architecture Repository/Artifacts/Abstract Wikipedia Architecture

= =

A library of code functions to support the Wikimedia projects and beyond, for everyone to call and re-use in the world's natural and programming languages

Status: This is a draft, in process, of the architecture modeling and discussion for Abstract Wikipedia project.

Mission statement
Enable everyone to collaboratively create and maintain a library of code functions to support the Wikimedia projects and beyond, for everyone to call and re-use in the world's natural and programming languages

Narratives (User stories)

 * User stories (TODO)

Capabilities

 * Capabilities model

Architecture models
This section includes the architectural models that are part of the discovery and model stages to define the architecture. This follows the Architecture practice, and involves collaborative modeling techniques like event sourcing. The goal of the process is to describe the domains of the system and model the architectural process. This work is ongoing.

Event models
These models aim to understand how the system works, mark the pain points, and discover where to dive deeper.

Event storming - first version
We began here to understand the events that happen in the system. And to tease out pain points / dense areas where we want to dive deeper.

Prioritized modeling how “validation” works next.

Link to artifact (Mural)

Event storming - cleaner version
Layered the events, as we identified them, and agreed this was accurate (with many remaining questions.)

Link to artifact (Mural)

Adding functions event sourcing
A model attempting to describe the actions and events that happen when a function is added to the system.

Link to artifact (Mural)

Ideal function dashboard model ("Happy puppy model")
This model was created from the view of an "ideal" workflow, to flush out behavior and interaction with the system.

Link to artifact (Mural)

Contexts and events in high-level model
A model fleshing out the user actions, system capabilities, and events in the system.

Link to artifact (Mural)

Capabilities and Flow models
These are models showing the capabilities and/or flow of data through the system.

Flow/Capabilities model - first draft
This was the first attempt to create a representation of the actions, flow, and events of the system.

Link to artifact (LucidChart)

Mission, Capabilities and Flow - second draft
A second iteration on the flow and capabilities model, connecting them to the team's missions statement.

Link to artifact (LucidChart)

Structure models
These are models describing a behavior of some system or several systems and their parts.

Top-level architectural model
This represents the top-level architecture of the system and its top-level services.

Wikifunctions Vue components
Link to artifact (Mural)