--- title: "Goal (systems analysis)" source: "https://systems-analysis.info/eng/Goal_(systems_analysis)" wiki: "systems-analysis.info/eng" article: "Goal_(systems_analysis)" language: "en" categories: - "Category:Decision theory" - "Category:English" - "Category:Management" - "Category:Science" - "Category:Systems analysis" - "Category:Systems analysis terminology" - "Category:Systems approach" - "Category:Terminology" revision_id: 167 wiki_created_at: 2026-09-06T22:18:21Z wiki_modified_at: 2026-09-06T22:18:21Z downloaded_at: 2026-09-07T22:21:31Z --- # Goal (systems analysis) **A goal in systems analysis** is a fundamental concept representing the **desired future [state](https://systems-analysis.info/eng/System_state "System state")** of a [system](https://systems-analysis.info/eng/System "System"), its [behavior](https://systems-analysis.info/eng/System_behavior "System behavior"), or its [environment](https://systems-analysis.info/eng/System_environment "System environment"). The entire process of [systems analysis](https://systems-analysis.info/eng/Systems_analysis "Systems analysis"), including [managerial efforts](https://systems-analysis.info/eng/Management "Management") and the resolution of a [problem situation](https://systems-analysis.info/eng/Problem_in_the_context_of_systems_analysis "Problem in the context of systems analysis"), is directed toward achieving this goal. The formulation, structuring, and use of goals are a central, system-forming element of the systems analysis (SA) methodology, defining the direction of the study, the boundaries of the analysis, the basis for modeling, the selection of evaluation [criteria](https://systems-analysis.info/eng/Criterion "Criterion"), and the construction of alternative solutions. ## Goals in Systems Analysis Unlike its everyday or general philosophical understanding, in systems analysis (SA), a goal is viewed from multiple aspects and in an operational manner: 1. As a problem resolution: A goal is formulated as a desired state that eliminates the [problematic nature](https://systems-analysis.info/eng/Problem "Problem") of the current situation—a recognized gap between the actual and the desired. As noted by F. I. Peregudov and F. P. Tarasenko, a goal often arises from a [problem situation](https://systems-analysis.info/eng/Problem "Problem"). 2. As a state and trajectory (Multi-level representation): A goal includes not only the final desired state of the system (Y\*) at a specific point in time (T\*) but can also define a preferred development trajectory Y\*(t)—a sequence of intermediate states on the path to the result. The goal combines an ideal concept with its projection onto reality, taking constraints into account. 3. As a subjective representation and an objective reference point: - A subjective goal is an internal image of the desired future that exists in the mind of the [subject](https://systems-analysis.info/eng/Observer_in_the_systems_approach "Observer in the systems approach") of analysis or a stakeholder. It reflects their [preferences](https://systems-analysis.info/eng/Preferences "Preferences"), values, and vision. - An objective goal is a formulation that has undergone analysis, been specified, and verified for achievability within the real [constraints](https://systems-analysis.info/eng/Constraints "Constraints") and capabilities of the system and its environment. SA aims to transform subjective aspirations into operational, objectified goals. 4. As a system-forming factor: The goal determines which [elements](https://systems-analysis.info/eng/System_element "System element"), [connections](https://systems-analysis.info/eng/Connections_in_systems "Connections in systems"), and [processes](https://systems-analysis.info/eng/Process "Process") are essential for the analysis, what [functions](https://systems-analysis.info/eng/Function "Function") the system must perform, and which [criteria](https://systems-analysis.info/eng/Criterion "Criterion") will be used to evaluate its effectiveness. The system itself is often defined as a "means of achieving a goal." 5. Dynamism and evolution: The concept of a goal is not static. It develops and is refined as knowledge of the system and its [environment](https://systems-analysis.info/eng/System_environment "System environment") deepens. Abstract goals are made more concrete, and unattainable ones are transformed into a general direction for [development](https://systems-analysis.info/eng/System_development "System development"). 6. Teleological aspect: Introducing a goal into the description of a system gives the analysis a teleological character—explaining behavior by referring to its intended outcome (Aristotle: "final cause"). While this is limited in classical sciences, the category of the goal is widely used in complex systems theory, cybernetics, biology, and social sciences to describe purposeful behavior. ## Hierarchy of Goals and the Relationship with Means Goals in complex systems are almost always organized hierarchically: - Top level: Mission, vision, strategic goals that define the system's purpose and overall direction of development. - Middle level: Tactical goals, objectives, [functions](https://systems-analysis.info/eng/Function "Function") achievable in the medium term that detail the strategic directives. - Lower level: Operational goals, specific actions, activities, and resources required to complete tasks. A key principle of systems analysis is that **goals and means are interconnected and relative**. Achieving a lower-level goal serves as a means to realize a higher-level goal. As Yu.I. Chernyak noted, "what is a goal from one point of view is a means from another." It is crucial to avoid the **substitution of means for ends**—a common error where completing a specific task or using a tool becomes an end in itself, detached from the original strategic goal. Analyzing the relationship between goals and means allows for assessing the expediency of actions: "what is expedient to do depends on what is possible to do." ## Requirements for Goals For goals to be used effectively in SA, they must satisfy a number of requirements (often associated with the SMART principle, but with a systems-oriented emphasis): - Specificity (Specific): The goal must be clearly and unambiguously formulated, indicating a specific desired outcome. - Measurability (Measurable): It must be possible to assess the degree of goal achievement using [criteria](https://systems-analysis.info/eng/Criterion "Criterion") (quantitative or qualitative). This is necessary for the subsequent evaluation of alternatives and for control. - Achievability (Achievable/Realistic): The goal must be realistic, meaning it can be reached with the available resources, technologies, and [constraints](https://systems-analysis.info/eng/Constraints "Constraints"), considering the state of the [environment](https://systems-analysis.info/eng/System_environment "System environment"). - Relevance (Relevant): The goal must be relevant to the [problem](https://systems-analysis.info/eng/Problem "Problem") it is intended to solve and align with the system's higher-level goals. - Time-Bound (Time-bound): It is desirable to specify deadlines or time horizons for achieving the goal. - Operationality: The goal must be formulated in such a way that it can be used to build [models](https://systems-analysis.info/eng/System_model "System model"), develop alternatives, and establish evaluation [criteria](https://systems-analysis.info/eng/Criterion "Criterion"). - Consistency: Goals at different levels and from different stakeholders must be consistent with one another. ## System Goals and Subject Goals In analysis, it is important to distinguish between: - System goals: The target state or behavior toward which the system strives as part of its functioning (often determined by a supersystem or through evolution). Technical and many biological systems implement externally defined goals. - Goals of the [subject](https://systems-analysis.info/eng/Observer_in_the_systems_approach "Observer in the systems approach") (manager, analyst, stakeholder): Consciously formulated intentions regarding the system. The subject sets goals for the system or attributes goals to it during the analysis. Organizations, as social systems, can formulate their own missions and strategic goals. Understanding whose goals are being considered (the system's, its creator's, its user's, the analyst's) is critically important for correctly defining the SA task. Often, the goal for a subsystem is determined by its supersystem. ## Goal and System Function The [function](https://systems-analysis.info/eng/Function "Function") of a system describes its role, purpose, or the work it performs ("what the system does" or "what it is for" from the perspective of the supersystem or environment). A goal specifies this function by defining the desired result of its execution ("what the system must achieve"). - Example: The [function](https://systems-analysis.info/eng/Function "Function") of the heart is to pump blood; the [Goal](https://systems-analysis.info/eng/Goal "Goal") of the circulatory system is to sustain life by delivering oxygen. - A functional description may not imply a conscious striving for a result, whereas a goal-oriented description introduces the idea of directionality toward a desired state. In SA, one often first describes the [function](https://systems-analysis.info/eng/Function "Function") and then formulates the [goal](https://systems-analysis.info/eng/Goal "Goal") as a measurable result of its execution. ## Goal and Environment - Purposeful behavior: The existence of a goal allows a system to exhibit purposeful [behavior](https://systems-analysis.info/eng/System_behavior "System behavior"), adjusting its actions (often via feedback) to approach the goal and compensate for external disturbances. - Adaptability: The ability of a system to change its behavior or [structure](https://systems-analysis.info/eng/System_structure "System structure") to achieve a goal under changing conditions of the [environment](https://systems-analysis.info/eng/System_environment "System environment"). - Influence of the environment: The [environment](https://systems-analysis.info/eng/System_environment "System environment") imposes [constraints](https://systems-analysis.info/eng/Constraints "Constraints") on the attainability of goals and can be the source of the goals themselves (external demands, supersystem requirements). The context (legislative, economic, social) determines the relevance and priority of goals. A goal must always be aligned with the capabilities and requirements of the environment. - Defining boundaries: A goal helps determine which [elements](https://systems-analysis.info/eng/System_element "System element") and interactions to include in the [model](https://systems-analysis.info/eng/System_model "System model") of the system and what to classify as the [environment](https://systems-analysis.info/eng/System_environment "System environment"). ## Role of the Goal in Modeling and Evaluation Goals play a defining role at all stages of modeling and evaluation: - Defining the boundaries and [structure](https://systems-analysis.info/eng/System_structure "System structure") of the model: Goals determine which [elements](https://systems-analysis.info/eng/System_element "System element"), [connections](https://systems-analysis.info/eng/Connections_in_systems "Connections in systems"), and [processes](https://systems-analysis.info/eng/Process "Process") are significant and must be included in the [model](https://systems-analysis.info/eng/System_model "System model"). - Selecting evaluation [criteria](https://systems-analysis.info/eng/Criterion "Criterion"): Criteria are developed directly from the goals to measure the degree of their achievement. - Formulating the [objective function](https://systems-analysis.info/eng/Objective_function "Objective function"): In [optimization](https://systems-analysis.info/eng/Optimization "Optimization") problems (often solved using [operations research](https://systems-analysis.info/eng/Operations_research "Operations research") methods), the goal is formalized as an objective function to be maximized or minimized. - Evaluating alternatives: Solution options are compared and assessed based on their contribution to achieving the formulated goals, using the selected criteria. - Model validation: The adequacy of a model is verified, in part, by its ability to predict the achievement of system goals. ## Methodological Significance A clear formulation of goals is necessary for: 1. defining the boundaries of the system and its [interaction with the external environment](https://systems-analysis.info/eng/System_environment "System environment"); 2. designing adequate [models](https://systems-analysis.info/eng/Model "Model"); 3. constructing well-founded alternatives; 4. selecting [criteria](https://systems-analysis.info/eng/Criterion "Criterion") for evaluating and comparing options; 5. implementing an improving intervention without creating new problems. Without a clear goal, systems analysis loses its direction, risking becoming formalistic and ineffective. ## External links - Goal — Wikipedia ## See also - [Systems analysis](https://systems-analysis.info/eng/Systems_analysis "Systems analysis") - [Goal](https://systems-analysis.info/eng/Goal "Goal") (general concept) - [Problem](https://systems-analysis.info/eng/Problem "Problem") / [Problem in the context of systems analysis](https://systems-analysis.info/eng/Problem_in_the_context_of_systems_analysis "Problem in the context of systems analysis") - [Criterion](https://systems-analysis.info/eng/Criterion "Criterion") - [Objective function](https://systems-analysis.info/eng/Objective_function "Objective function") - [Function](https://systems-analysis.info/eng/Function "Function") - [System model](https://systems-analysis.info/eng/System_model "System model") - [Modeling](https://systems-analysis.info/eng/Modeling_(scientific) "Modeling (scientific)") - [Decision-making](https://systems-analysis.info/eng/Decision-making "Decision-making") - [Hierarchy](https://systems-analysis.info/eng/Hierarchy "Hierarchy") - [Requirements](https://systems-analysis.info/eng/Requirements "Requirements") ## Bibliography - Saaty, T. L., & Kearns, K. P. *Analytical Planning: The Organization of Systems*. — Moscow: Radio i Svyaz, 1991. - Cleland, D. I., & King, W. R. *Systems Analysis and Project Management*. — Moscow: Sovetskoye Radio, 1974. - Quade, E. S. *Analysis of Complex Systems*. - Optner, S. L. *Systems Analysis for Business and Industrial Problem Solving*. - Chernyak, Yu. I. Systems Analysis in Economic Management // *Systems Analysis in Economics*. - Young, S. *Systemic Management of an Organization*. — Moscow: Sovetskoye Radio, 1972. - Peregudov, F. I., & Tarasenko, F. P. *Introduction to Systems Analysis*. — Moscow: Vysshaya Shkola, 1989. - Volkova, V. N., & Denisov, A. A. *Systems Theory and Systems Analysis: A Textbook for Universities*. — Moscow: Yurayt Publishing, 2025 (or *Systems Theory*. Moscow: Vysshaya Shkola, 2006). - Mesarovic, M. D., Macko, D., & Takahara, Y. *Theory of Hierarchical, Multilevel, Systems*. — Moscow: Mir, 1973. - Sadovsky, V. N. *Foundations of General Systems Theory*. — Moscow: Nauka, 1974. — (Discusses expediency, active systems acting based on goals). - Bertalanffy, L. von. General System Theory — A Critical Review // *Sistemnye Issledovaniya. Yearbook 1969*. — Moscow: Nauka, 1969.