MDPE.1:2 - Solution
Frame the project around the subject whose change will make the next commitment worthwhile. The sections below describe the reasoning needed for the brief; they are not a fixed lifecycle.
MDPE.1:2.1 - Select the subject and scale
Start from the decision named by MDPE.8 or from an equally clear direct project question. Choose one primary
subject from the table above. Name any linked subjects and the relations through which their results will be used.
For example, a festival project may change an event-production System while also testing whether its curation and teaching relations support a style-development line. The festival is not thereby the style, and one edition is not the whole event series.
When the primary or linked subject is an engineered System, select the Systems Engineering result that is actually missing:
| Missing engineering result | Direct Systems Engineering pattern |
|---|---|
| Which actual or intended System is the project System-of-Interest, and when that focus must reopen | SYSE.1 — Choose and Reopen the Project System-of-Interest |
| Which linked use and System concepts make the intended value and boundary testable | SYSE.2 — Develop Linked Use and System Concepts |
| Which functional organization, bearers, and interfaces remain viable alternatives | SYSE.5 — Develop an Engineered System's Functional Organization and Bearer Alternatives |
| Which architecture is selected and what evidence reopens it | SYSE.6 — Decide and Reopen the Engineering Architecture |
| Which recursive realization arrangement can create, integrate, qualify, operate, and change the System | SYSE.3 — Plan the Next System-Realization Action (Recursive Realization Network) |
| Which assurance claim, evidence, uncertainty, and return must accompany the result | SYSE.4 — Prepare Engineering Assurance and Return Evidence |
These are conditional exits, not a mandatory sequence. MDPE.1 specializes their use by stating which
Music-or-Dance Work, style distinction, performance relation, and cultural consequence the engineered System is
meant to enable. Use Method Engineering when the project subject is a Method or Method family rather than the
engineered System or performance result.
MDPE.1:2.2 - State the intended Work and first use
Name the Work that will exercise or use the changed subject and the maintained domain Method it enacts. Examples of this Work include composing, choreographing, practising, teaching, partnering, improvising, rehearsing, performing, listening, judging, curating, producing, presenting, and archiving.
Name the performing or deciding Agent in ordinary language. Keep the technical U.System, SystemRole kind,
assignment, capability, and Work attribution recoverable when the claim relies on them. Instruments, software,
scores, recordings, venues, and publications can contribute without becoming Agents.
MDPE.1:2.3 - Separate proposal from realization
State what exists now and what the project proposes. A brief, score, choreography, MethodDescription, lesson programme, model, architectural description, or manifesto can describe a possible future. It does not make the performance, practice, style relation, or supporting System exist.
Name the realization Work expected to produce or change the world-side result. Name the earliest observation that would show whether the proposed result works with the performers, participants, instruments, partners, venues, and other receiving conditions.
MDPE.1:2.4 - Choose preservation and variation
State which distinctions must survive and which may change. Depending on the project, these may concern rhythm, timing, sound, movement quality, partner response, form, improvisational freedom, instrument relation, social function, participation, authorship, lineage, or another domain characteristic.
Avoid both extremes. Freezing one manifestation can destroy a living practice; unlimited variation can erase
the distinction the project meant to develop. MDPE.12 and MDPE.23 become relevant when the project needs an
observation or developed recognition capability to test the boundary.
When preservation, variation, safety, access, visibility, cost, authorship, participation, or cultural continuity cannot all be improved together, name the material conflict or unresolved live choice. State the affected Agents and Systems, which commitments cannot presently coexist, which decision the conflict changes, and what observation or authority is needed before choosing. Do not turn a disputed objective into an agreed requirement.
MDPE.1:2.5 - Name participants, affected Systems, and decision rights
Name who creates, performs, learns, teaches, curates, organizes, funds, publishes, senses, judges, and bears the effects as far as the decision needs them. Technical ability, authorship, funding, ownership of a venue, or platform visibility does not by itself grant authority over another Agent or a whole cultural practice.
When participation, access, cultural material, visibility, safety, attribution, or stewardship changes, state the authority, permission, commitment, consent, contest, refusal, exit, or revision relation on which the proposed decision relies. Leave a disputed part open when that relation is missing.
MDPE.1:2.6 - Set the recognition and reopen boundary
Name the Agent or population expected to distinguish or use the result, the conditions of recognition, and the first observation that can defeat the project basis. Familiarity with a label, press attention, official listing, or one approving response is not a recognition Method.
The brief closes when the next project commitment can be made or refused without changing the subject by accident. It reopens when representative Work, participant response, feasibility, authority, safety, recognition, cost, or another named condition defeats a relied-on claim.