ITI 202

Inheritance

An 'is-a' relationship in object-oriented programming where one class is a type of another class.

Aggregation

A 'has-a' relationship where one class contains another but does not own it.

Composition

A stronger 'owns-a' relationship where the contained object cannot exist without its owner.

Human-Centered Design (HCD)

The key principle involves involving the user throughout the design process.

Four Activities in HCD

Observation, Idea Generation, Prototyping, Testing.

Six Core Elements of HCD

Understand, Define, Ideate, Prototype, Test, Iterate.

Disparity of Benefit

A situation where those who contribute effort to a system are not the primary beneficiaries.

Example of Disparity of Benefit

Reviewers on Yelp provide value, but future users and companies benefit the most.

Use Case Diagram

Represents how users interact with different features of a system.

Key Elements of a Use Case Diagram

Actors, Use Cases, Relationships.

State Machine Diagram

Shows how an object transitions between different states.

Key Elements of a State Machine Diagram

States, Transitions, Initial State, Final State.

Behavioral Diagrams

Represent the behavior of a system over time and space.

Types of Behavioral Diagrams

Include Use Case Diagram, Sequence Diagram, Activity Diagram, State Machine Diagram.

Grouping in UML

To organize elements into packages or components for better system management.

Example of a Package in UML

A library system may have a 'Books' package containing Book, Author, and Genre classes.

Double Diamond Model

Visually represents the iterative nature of design thinking.

Four Phases of the Double Diamond Model

Discover, Define, Develop, Deliver.

Definition of a System

A set of interrelated components working together to achieve a specific purpose.

Example of a Real-World System

A car, where components like the engine, wheels, and sensors work together to transport people.

Deployment Diagram

Shows software components, how they are deployed, and how they communicate.

Key Elements of a Deployment Diagram

Nodes, Artifacts, Communication Associations, Deployment Specifications.

Sequence Diagram

Shows the order of interactions between objects in a system.

Key Elements of a Sequence Diagram

Objects/Actors, Lifelines, Messages, Activation Bars, Return Messages, Conditions and Loops.

Affordances in Design

Features that help users understand possible actions within a system.

Class Diagram

Represents the structure of a system, including classes, attributes, methods, and relationships.

Example of a Class in a Class Diagram

Class: Student; Attributes: Name, Age; Methods: Enroll, Study.

Structural Diagrams

Represent the static parts of a system that do not change over time.

Types of Structural Diagrams

Include Class Diagram, Object Diagram, Component Diagram, Deployment Diagram, Package Diagram.

Component Diagram

Shows how high-level components of a system are connected.

Example of a Component Diagram

A web application with frontend, backend, and database components.

Dynamic Diagrams

Represent the behavior or interactions of a system over time.

Types of Dynamic Diagrams

Include Sequence Diagram, Communication Diagram, State Diagram, Activity Diagram.

Activity Diagram

Represents the flow of control in a system.

Key Elements of an Activity Diagram

Activities, Start, End, Decision Node, Merge Node, Fork Node, Join Node, Swimlanes, Control Flows.

Interaction Diagrams

Show how objects communicate and interact.

Types of Interaction Diagrams

Include Sequence Diagram, Communication Diagram.

Key Elements of an Interaction Diagram

Objects/Participants, Messages, Activation Boxes, Return Messages.