Engineering.Reference:0.8.1 - Two questions behind the professional map
Anatoly Levenchuk’s Russian Guide to Systems Engineering for Engineer-Managers uses archroles for broad professional contributions to creating and developing systems. Its map crosses two questions. What are we helping to create, change or sustain? The source distinguishes cyberphysical systems, organizations, clientele, human capability and an investor base. A component can belong to a product. A team can belong to the organization providing that product. The provider undertakes to supply the product through its work. In product design, follow the constituents and operating whole that matter to its use. In a change to provision, follow the participating organizations and the work they must do together. For a change in capability, identify its bearer and what that bearer needs to be able to do. What contribution are we making to that target? Developing its use concept, shaping its architecture, designing its functioning, realizing it and operating it have different immediate results.
The first question selects the subject knowledge. Designing a pump requires knowledge of the relevant physical behavior, materials and operating conditions. Designing the organization that maintains pumps requires knowledge of work dependencies, commitments, decisions and actual cooperation. Designing how a technician acquires diagnostic ability requires knowledge of diagnosis and of learning. Similar architectural reasoning can help all three while leaving these professional requirements distinct.
The second question differentiates work on the same target. A functional account of a pump explains what it does and how its functions interact. A constructive design proposes what carries that behavior. A manufacturing method explains how to obtain the proposed embodiment. Each constrains the others, but an answer about one leaves a different question about the others. The engineering line of the source map makes these contributions visible:
| Professional contribution | Result needed from it | Knowledge and connection that make the result usable |
|---|---|---|
| Visionary or concept work | A reasoned account of valuable use and a system that could support it. | The receiving activity, alternatives and constraints connect the proposed benefit to a feasible system concept. |
| Architecture | Decisions about structures and characteristics that constrain several subsequent choices. | Knowledge of the system’s interactions, alternatives and consequences establishes which constraints must be shared and which choices can remain local. |
| Functional design, the source’s applied methodologist | A synthesis of the functions, dynamics and behavior of the system being engineered, whether product or creator. | Subject knowledge explains the transformations, interactions and conditions that a proposed embodiment must support. |
| Constructive design | Components and relations capable of carrying the selected functioning. | Knowledge of possible bearers connects function, architecture, realization, operation and maintenance. |
| Realization engineering | A way to produce, integrate, deploy or change the system. | The selected construction, available means and acceptance conditions must permit a working result. |
| Operation | The required functioning under actual operating conditions, with observations of what happens. | The use commitment, support and operating limits determine what can be sustained and which observations return to design. |
| Internal-platform engineering | Working means and access for the other contributors. | Their actual work determines the platform’s required contribution; the platform has its own use, architecture, realization and operation. |
Developer is a composite label in the source map. Its band groups functional design, constructive design, realization and operation. The surrounding source also uses development for broader work before operation and for narrower team design. Recover the intended scope in each use. The label helps describe a combination; its presence does not add another independent contribution alongside those it contains.
The source’s applied methodologist designs how the system functions. Adding automatic stopping at excessive pressure changes a pump’s functional behavior: sensing, the stopping condition and the interruption of flow must fit together. Casting a casing instead of machining it, while retaining the required pump behavior, changes realization and its compatibility with the design. If the immediate engineering subject is the production line, the line’s own transformations become the functional-design subject. The products and intended uses that the line must serve still ground the required capability and its acceptance. SYSE.5 develops this functioning-and-bearer construction. A researcher or practitioner developing another method keeps that method’s actual subject; the local source term does not name every kind of methodology.
These contributions arise from different questions needed to obtain and sustain the target’s functioning. Their unity comes from that shared result and their reciprocal constraints. A maintenance limitation can change the construction; an unavailable production method can change the architecture; an unaffordable operating arrangement can change the useful offer. Engineering.Reference:0.5 develops those returns. Paragraph order can help teach the questions, while actual work begins with the unresolved contribution and returns wherever its grounds change.
This map is useful within its engineering subject. Research can seek a warranted explanation without undertaking to construct a system. Cultural or artistic practice can have purposes and grounds that the engineering map does not exhaust. Even within engineering, an established supplier result can make fresh performance of one contribution unnecessary. Treat the map as a way to recover work, with a declared subject and useful variation, rather than an exhaustive register of professions.