ch2

Definition: Socio-technical systems combine technical systems with people and processes.
Importance: Understanding the interplay between technology and human factors is essential for system effectiveness.

Distinction: Differentiate between socio-technical systems and computer-based systems.
Emergent Properties: Explore concepts like reliability and security as system properties.
System Engineering: Explain the processes involved in system engineering and procurement.
Organizational Context: Analyze how the context of an organization affects system design and use.
Legacy Systems: Discuss challenges related to legacy systems in businesses.

Emergent System Properties: Properties that arise from the interactions within the system.
Systems Engineering: The interdisciplinary approach to creating socio-technical systems.
Organizations and People: Role of individuals and organizational structure in system operation.
Legacy Systems: The implications of maintaining outdated systems in modern environments.

Definition: A system is a purposeful collection of inter-related components working towards a common objective.
Components: May include hardware (mechanical, electrical, electronic), software, and operators.
Interdependency: System behavior and properties are influenced by the relationships between components.

Technical Computer-Based Systems: Focus only on hardware and software without considering user interaction.
Socio-Technical Systems: Include human operators and operational processes, governed by organizational policies.

Emergent Properties: Holistic properties that depend on the full system integration rather than individual components.
Non-Deterministic: Outputs can vary despite identical inputs due to human interaction.
Complex Relationships: The ability of a system to support organizational goals is not merely about its technical design.

Whole System Properties: Characteristics that arise from system components and their relationships.
Examples:
- Volume: Changeable based on component arrangement.
- Reliability: System reliability varies with component reliability and unforeseen interactions.
- Security: Complexity in measuring due to potential unpredictable attacks.
- Repairability: Ease of diagnosing and fixing issues in the system.
- Usability: Affected by components, user interaction, and environment.

Functional Properties: Result from components working together towards an objective.
Non-Functional Properties: Relate to system performance, reliability, safety, and security in an operational context.

Hardware Reliability: Probability and time required for repair of hardware components.
Software Reliability: Likelihood of software producing incorrect outputs.
Operator Reliability: Probability of human error in system operation.
Relation: Interdependencies between components can lead to compounded faults.

Phases: Involves specifying, designing, implementing, validating, deploying, and maintaining systems.
Challenges: Miscommunication across disciplines can cause misunderstandings and issues in development.
Waterfall Model: Predominantly used due to the need for structured phases with limited iteration.

Types of Requirements:
- Abstract functional requirements: Defined at a high level without specifics.
- System properties: Non-functional requirements of the system.
- Undesirable characteristics: Specifications of unwanted system behaviours.

Partitioning Requirements: Organizing requirements into groups.
Subsystem Identification: Finding sub-systems that collectively fulfill overall system requirements.
Specification of Functions: Clearly defining the functionality and interactions among subsystems.

Incremental Approach: Systems built through gradual integration of individual components.
Common Challenges: Interface issues between subsystems often arise during gradual integration.

System Longevity: Large systems need to evolve to adapt to new requirements.
Decommissioning: The process of safely taking a system out of service, including environmental considerations.
Legacy Systems: Acknowledges the reliance on old systems that still provide essential services for businesses.

Impact on Processes: Changes required by new systems can affect work processes, jobs, and organizational dynamics.
Flexibility: As operational processes are designed, they should allow for human initiative to handle unexpected challenges.

Acquisition Steps: Involves preliminary specifications and architectural designs to guide development contracts.
Commercial Off-the-Shelf (COTS): Often a cost-effective alternative to custom system development.
Modification of Requirements: Specifications might need adjustment to fit the capabilities of off-the-shelf solutions.

Critical Operations: Older systems continue to play vital roles despite risks associated with outdated technology.
Components: Involves obsolete hardware, legacy application software, incomplete data, and business processes constrained by legacy systems.

System Integration: The successful melding of hardware, software, and human components is vital.
Emergent Properties: Understanding system-wide characteristics is critical for assessing performance.
Interrelation of Human Factors: Human and organizational dynamics significantly impact the success of socio-technical systems.