Introduction to Computer Systems and Iterative Design

Process and System Decomposition

  • Decomposition is the process of breaking down a task into every single constituent step.
  • An example of decomposition using a daily chore involves identifying every specific action required to clean a table:
    • Identify the waste to be discarded.
    • Throw the waste down into the appropriate receptacle.
    • Place utensils in their correct designated locations.
    • Dispose of napkins.
    • Pour the remains of a soup into a liquid-specific bin.
  • This minute level of detail is necessary before moving to the next phase of development, which is design.

Design Phase Methodologies

  • The design phase utilizes two primary tools for visualization and planning:
    • Structure charts.
    • Flow charts.
  • Pseudocode is the third step in the process and is developed only after the structure and flow charts are completed.
  • It is vital to follow this specific order—structure charts, then flow charts, then pseudocode—to establish a disciplined habit and avoid the sloppiness often associated with jumping directly into coding.

Iterative Testing and Module Development

  • Iterative testing is a cycle where coding and testing occur several times during development.
  • The process for developing a program or a set of programs follows these logical steps:
    1. Each individual module of the program is written.
    2. Every individual module is tested immediately after it is written.
    3. If errors or inconsistencies are found, the code is fixed.
    4. The test is repeated until that specific part of the module or system is consistent and functional.
  • Documentation is a mandatory requirement for every test performed. Without documented results, it is impossible to track progress or identify which iterations have been completed.
  • Test documentation should include:
    • The test number (e.g., Test Number 11, Test Number 22, Test Number 33).
    • The specific module currently undergoing testing.

Components of a Computer System

  • A computer system is a multi-faceted entity that extends beyond mere software. It consists of:
    • Software.
    • Data.
    • Hardware.
    • Communication of data.
    • People (both the operators who use the system and the developers who create it).
  • Computer systems vary in scale, from small-scale applications to large-scale enterprise systems.
  • Systems are composed of subsystems, which are identified using the aforementioned structure charts and decomposition techniques.
  • To solve any problem using a computer system, the problem must be decomposed into its component parts:
    • Inputs.
    • Processes.
    • Outputs.
    • Storage.

Data Lifecycle: Input, Process, Output, and Storage

  • Every system must have its parts identified by analyzing how data moves through it.
  • Key questions for system analysis include:
    • What is the data coming into the system (Input)?
    • How will that data be stored (Storage)?
    • What specific operations must be performed on that data (Process)?
    • What information is being produced by the data (Output)?

Application Case Study: Fitness Monitoring System

  • A fitness system illustrates the practical application of input, process, storage, and output:
    • Input: A sensor detects the biological data of the user, such as heart rate.
    • Storage and Process: The system counts the heart rate, sends the data in, and stores it.
    • Frequency and Calculation: The system takes one reading every 66 seconds. Given there are 6060 seconds in a minute, these ten readings are used to calculate Beats Per Minute (BPM).
    • Output: The resulting data is displayed on a screen, often in the form of a graphic.
  • Threshold Logic and Visual Feedback:
    • Below 6060 or 6565 BPM: The user is classified as resting or not yet warming up.
    • 7070, 8080, or 100100 BPM: The user has reached the aerobic level.
    • Beyond 120120 BPM: The user has reached the fat burning stage.
    • 165165 to 170170 BPM: The system identifies the user is reaching their limit. At this threshold, the output display might change the color of the numbers to warn the user.
    • 175175 to 180180 BPM: The user is reaching their VO max, which represents a state of exhaustion or danger.
  • Other subsystems within a fitness app, such as diet monitoring or water intake tracking, must be decomposed in the same way to identify their specific functions and requirements.

System Lifecycle Stages

  • The development process is categorized into specific sections:
    • 7.1.17.1.1: Analysis.
    • 7.1.27.1.2: Design.
    • 7.1.37.1.3: Coding.
    • 7.1.47.1.4: Testing.

Questions and Discussion

  • Question (Suzie): Is there a specific order required to perform these steps?
  • Answer: Yes. A strict order must be maintained to avoid sloppy programming habits. Developers should first complete structure charts, move to flow charts, and only then begin work on pseudocode. This disciplined approach ensures the system is well-thought-out before any actual programming occurs.