Classical methodologies of systems analysis

From Systems Analysis Wiki
Jump to navigation Jump to search

Introduction

Classical methodologies of systems analysis emerged in the mid-20th century in response to the need to solve complex, ill-structured problems in management, engineering, economics, and social practice. These methodologies are based on the systems approach and offer structured procedures for analysis, modeling, and solution selection.

The development of classical methodologies is associated with the work of researchers such as E. S. Quade, S. L. Optner, Yu. I. Chernyak, E. P. Golubkov, and S. Young, each of whom contributed to shaping the practices of systems research. Their approaches define the fundamental stages of systems analysis—from problem formulation to the development and implementation of solutions.

Classical methodologies remain relevant today, serving as a foundation for modern methods of systems thinking and systems engineering.

Classical Methodologies of Systems Analysis

Classical methodologies of systems analysis represent a set of approaches developed in the 20th century to solve complex, ill-structured problems in various fields—from the defense industry to organizational management. These methodologies are based on the systems approach and include sequential stages of analysis, modeling, and decision-making.

General Structure of Systems Analysis Methodology

The general methodology of systems analysis includes the following stages:

  1. Problem identification and goal setting — defining existing problem situations and formulating the objectives of the analysis.
  2. Development of alternatives and decision-making models — generating alternative solutions and constructing models to evaluate them.
  3. Evaluation of alternatives and selection of solutions — analyzing and comparing alternatives using various criteria.
  4. Implementation of solutions — putting the selected solutions into practice.
  5. Evaluation of solution effectiveness and implementation consequences — analyzing the results of implementation and adjusting the strategy if necessary.
  6. Designing the organization to achieve goals — structuring organizational processes and resources to effectively achieve the set goals.

Quade's Methodology

The methodology proposed by E. S. Quade includes the following stages:

  1. Problem formulation — defining the problem and the scope of the study.
  2. Selection of alternative solutions — generating possible solutions.
  3. Analysis of resources required for the solution — analyzing the necessary resources and their costs.
  4. Model development — creating a model of the system to analyze alternatives.
  5. Selection of evaluation criteria — defining the criteria for comparing alternatives.
  6. Comparison of alternatives and decision-making — choosing the best solution based on the analysis.

Optner's Methodology

S. L. Optner proposed the following sequence of stages for systems analysis:

  1. Symptom identification — recognizing the signs of a problem.
  2. Determining the problem's relevance** — assessing the significance of the problem.
  3. Goal definition — formulating the objectives of the analysis.
  4. Revealing the system's structure and its defective elements — analyzing the current system and identifying its shortcomings.
  5. Defining the structure of opportunities** — identifying potential changes.
  6. Finding alternatives — generating possible solutions.
  7. Evaluating alternatives — analyzing the advantages and disadvantages of each option.
  8. Selecting an alternative — making a decision.
  9. Formulating the solution — developing an implementation plan.
  10. Gaining acceptance of the solution from the implementation team and management — coordinating the solution with stakeholders.
  11. Launching the solution implementation process — beginning the rollout.
  12. Managing the solution implementation process — monitoring execution.
  13. Evaluating the implementation and its consequences — analyzing results and making adjustments as needed.

Chernyak's Methodology

Yu. I. Chernyak proposed the following structure for systems analysis:

  1. Problem analysis — defining and formulating the problem.
  2. System definition — establishing the boundaries and elements of the system.
  3. Analysis of the system's structure — studying the interconnections and hierarchies within the system.
  4. Formulation of the overall goal and system criterion — defining objectives and evaluation criteria.
  5. Goal decomposition, identification of resource and process needs — breaking down the main goal into sub-goals and determining the necessary resources.
  6. Identification of resources and processes, composition of goals — integrating sub-goals and resources.
  7. Forecasting and analysis of future conditions — assessing external factors and their impact.
  8. Evaluation of goals and means — analyzing the alignment of goals with available means.
  9. Selection of options — choosing the most suitable solutions.
  10. Diagnosis of the existing system — assessing the current state of the system.
  11. Construction of a comprehensive development program — developing an action plan.
  12. Designing the organization to achieve goals — structuring the organization to implement the plan.

Golubkov's Methodology

E. P. Golubkov identified the following stages of systems analysis:

  1. Problem formulation — defining goals and constraints.
  2. Research — collecting and analyzing information.
  3. Analysis — building models and forecasting the consequences of decisions.
  4. Preliminary judgment — forming initial conclusions.
  5. Confirmation — verifying and refining the conclusions.
  6. Final judgment — making the final decision.
  7. Implementation of the adopted solution — putting the solution into practice.

Young's Methodology

S. Young proposed the following sequence of stages in the decision-making process:

  1. Defining the organization's goals — establishing strategic objectives.
  2. Identifying problems in achieving these goals — recognizing obstacles.
  3. Investigating problems and making a diagnosis — analyzing the causes and consequences of problems.
  4. Searching for a solution to the problem — generating possible solutions.
  5. Evaluating all alternatives and choosing the best one — conducting a comparative analysis of options.
  6. Reaching consensus on the solution within the organization — discussing and approving the chosen solution.
  7. Approving the solution — formally adopting the decision.
  8. Preparing to put the solution into action — planning the implementation.
  9. Managing the application of the solution — overseeing the implementation.
  10. Verifying the solution's effectiveness — evaluating the results and making adjustments as needed.

References

  • Optner, S. L. (1965). *Systems Analysis for Business and Industrial Problem Solving*. Prentice-Hall.
  • Quade, E. S. (Ed.). (1964). *Analysis for Military Decisions*. Rand McNally.
  • Cleland, D. I., & King, W. R. (1975). *Systems Analysis and Project Management* (2nd ed.). McGraw-Hill.
  • Young, S. (1969). *Management: A Systems Analysis*. Scott, Foresman.

See also