Jump to text
On this page
Copy and source
Published source confirmed at last check

Source changed 2026-11-18 21:11:39 UTC · snapshot created 2026-11-18 21:12:35 UTC · last check 2026-11-18 22:10:10 UTC

SYSE.2:11 - SoTA-Echoing

The practice question is how much use description is needed to change the concept or expose the next architecture question. The selected approach develops a small linked proposal with progressive behavioural detail. Existing scenarios and slices can supply that content directly.

Current practice lineWhat changes in this patternSource and useAdoption status
Current use-case practice starts from user goals, admits human and nonhuman participants and failure paths, and revises end-to-end slices as work proceeds. Model-based system-architecture practice connects use cases to candidate functional groupings and interfaces.Start from a concrete use situation. As the use and the candidate System concept change, show how participants’ behaviour on success and failure paths connects the proposed use to the candidate concept.Jacobson et al., Use-Case 3.0: The Definitive Guide — Refreshed (2024); Weilkiens et al., Model-Based System Architecture, 2nd ed. (2022). These are provider and textbook Methods, not comparative proof of one universal sequence.Adopt and adapt. Use revisable slices and explicit links to candidate functioning; choose the representation form for the receiving engineering decision.
Agile and continuing requirements research treats models, requirements, traceability, monitoring, and compliance links as maintained parts of changing work rather than one frozen preliminary package.The linked proposal stays revisable, and representations are chosen for the decision and maintained only while they continue to carry useful claims.Liebel and Knauss, Aspects of modelling requirements in very-large agile systems engineering (2023; author preprint), report one Ericsson case, including model-maintenance and tool trade-offs. SYSE.19:11 gives the distinct source scopes and references for Hernández, Moros and Nicolás (2023), Norheim et al. (2024), and Kosenkov et al. (2025): DevOps requirements management, LLM requirements tasks, and regulatory compliance.Adapt. Maintain useful claims and choose representations by use; let the receiving project determine how requirements Work is organized.
Product-service system and servitization research treats useful offerings as configurations of products, service Work, provider and customer relations, capabilities, operations, digital support, and consequences. Reported performance is mixed and configuration-dependent.The Solution compares actual or proposed changes to the designated System, external Systems, interfaces, and Work arrangements and asks for the specialist results that make those alternatives credible.Brambila-Macias, Sakao and Kowalkowski (2018), Braga Junior, de Toledo and González (2020), Kim (2020), Brax et al. (2021), Åkesson et al. (2024), Menon et al. (2024), and Zhao et al. (2025). SYSE.8:11 develops the bounded offering/provider comparison.Adapt. Use the cross-boundary design pressure; establish each System, Work, provider relation, Method, and consequence directly in the receiving project.

A serious alternative is a progressive use-case slice following the Use-Case 3.0 guide. It starts with a user goal and can grow from a sketch through selected normal and failure paths toward a testable increment. It need not enumerate all scenarios before useful work starts.

Compare the two on the same moved-order facts in §5.2, including the stale stock record. A small slice for rescheduling an order can reveal the unsupported commitment and supply a failure path that holds it. The linked proposal should reveal the same failure. Its selected next result is the architecture question: which functioning, people, runtime and interfaces could support a commitment under the stated conditions? An adequate slice can supply those claims directly.

The trade-off depends on the next result. This linked proposal leaves implementation and path-specific acceptance tests unprovided while the bearer and interface choices remain open. Progressive slice practice supplies the route toward implemented, tested behaviour when that is needed. Neither representation earns a general effort advantage from being called small. In the ERP case, the proposed confirmation and reservation arrangements still need comparison, so §§4.3–4.6 return the functional and bearer question to C.32 and SYSE.5; a later testable slice can use that result.

Reopen the choice of a thin linked proposal when it appears coherent but a consequential path changes the functioning or bearer—for example, when another order consumes the promised stock between proposal and commitment. Add the missing path or use the progressive slice directly. Prefer an available scenario treatment when it supplies the required architecture claims with less reconstruction or maintenance. These are selection conditions, not evidence that one description form has superior project outcomes.

These current lines support continuing, use-led, model-linked revision in the settings examined. This pattern connects a use situation, subjects and relations, qualified consequences and a candidate concept, using compatible SYSE.16, SYSE.17 and SYSE.8 results. Relate evidence to the claim it can change. Assess transfer to another setting against the receiving use, Systems, relations and evidence.