OOSE Master Terminology Sheet

 

1. Object

Definition

A real-world entity having state and behavior.

Examples

  • Student
  • Employee
  • ATM

Used In

  • OOP Concepts
  • OOA
  • OOD
  • Class Diagram
  • Testing

Remember: Object = Real-world Entity

2. Class

Definition

A blueprint for creating objects.

Example

Student Class → Student Objects

Used In

  • OOA
  • OOD
  • CRC Cards
  • Class Diagram
  • Testing

Remember: Class = Blueprint

3. Attribute

Definition

Properties of a class.

Example

Student
--------
RollNo
Name

Used In

  • Class Diagram
  • OOA
  • OOD

Remember: Attribute = Data

4. Method

Definition

Function performed by an object.

Example

Display()
Register()

Used In

  • Class Diagram
  • OOP
  • Testing

Remember: Method = Behavior

5. Relationship

Definition

Connection between classes.

Types

  • Association
  • Aggregation
  • Composition
  • Inheritance
  • Dependency

Used In

  • UML
  • Class Diagram
  • OOD

6. Use Case

Definition

A function provided by the system.

Example

  • Login
  • Register Course
  • Withdraw Cash

Used In

  • Requirement Analysis
  • Use Case Diagram
  • RUP

Remember: Use Case = User Requirement

7. Actor

Definition

External user interacting with the system.

Example

  • Student
  • Customer
  • Admin

Used In

  • Use Case Diagram

Remember: Actor = User

8. OOA (Object-Oriented Analysis)

Definition

Process of identifying requirements, classes, objects, and relationships.

Output

  • Use Case Diagram
  • Activity Diagram
  • Analysis Class Model

Remember: OOA = WHAT system should do

9. OOD (Object-Oriented Design)

Definition

Process of converting analysis model into design model.

Output

  • Class Diagram
  • Interaction Diagram
  • Component Diagram

Remember: OOD = HOW system will do it

10. Encapsulation

Definition

Binding data and methods into one unit.

Used In

  • OOP Concepts
  • Design

Remember: Data + Methods Together

11. Abstraction

Definition

Showing essential features and hiding details.

Example

ATM Machine

Remember: Hide Complexity

12. Inheritance

Definition

Acquiring properties of another class.

Example

Vehicle
   ↑
 Car

Remember: Reuse Existing Code

13. Polymorphism

Definition

One interface, many forms.

Example

Method Overloading

Remember: Multiple Behaviors

UML Diagrams (Most Important)

Use Case Diagram

Purpose

Shows user requirements.

Contains

  • Actor
  • Use Case

Activity Diagram

Purpose

Shows workflow.

Contains

  • Activities
  • Decisions
  • Flow

Class Diagram

Purpose

Shows system structure.

Contains

  • Class
  • Attributes
  • Methods
  • Relationships

Interaction Diagram

Purpose

Shows communication between objects.

Types

  • Sequence Diagram
  • Collaboration Diagram

State Chart Diagram

Purpose

Shows states and transitions.

Example

ATM Card States

Component Diagram

Purpose

Shows software components.

Deployment Diagram

Purpose

Shows hardware deployment.

Testing Terminology

Correctness

Model correctly represents requirements.

Keyword: Right Model

Consistency

All UML diagrams agree with each other.

Keyword: No Contradiction

Test Case

Input + Expected Output + Result

Testing Strategy

  1. Unit Testing
  2. Integration Testing
  3. System Testing
  4. Validation Testing
  5. Acceptance Testing

RUP Terminology

RUP

Rational Unified Process

Keywords

  • Iterative Development
  • Use Case Driven
  • Architecture Centric

RUP Phases

  1. Inception
  2. Elaboration
  3. Construction
  4. Transition

Shortcut: IECT

Best Practices

  1. Develop Iteratively
  2. Manage Requirements
  3. Component Architecture
  4. Visual Modeling
  5. Verify Quality
  6. Control Changes

4+1 View Model

  1. Logical View
  2. Process View
  3. Development View
  4. Physical View
  5. Use Case View

Shortcut: LPDP + U

Design Pattern Terminology

Design Pattern

Reusable solution to common software design problems.

Types

Creational

Object creation.

Structural

Class structure.

Behavioral

Object communication.

Most Repeated Definitions in Entire Subject

TermOne-Line Definition
ObjectReal-world entity
ClassBlueprint of objects
OOAIdentify requirements and objects
OODConvert analysis into design
Use CaseSystem functionality
ActorExternal user
Class DiagramStatic structure
Activity DiagramWorkflow
Interaction DiagramObject communication
State Chart DiagramStates and transitions
Component DiagramSoftware components
Deployment DiagramPhysical deployment
CorrectnessRight model
ConsistencyNo contradiction
Test CaseInput + Expected Output
RUPSoftware development process
Design PatternReusable solution

Golden Rule for RGPV

Whenever you see a question, first ask:

  1. Requirement related? → Use Case / OOA
  2. Structure related? → Class Diagram / OOD
  3. Behavior related? → Activity, Interaction, State Chart
  4. Testing related? → Correctness, Consistency, Test Cases
  5. Process related? → RUP, SDLC, Workflows

Comments

Post a Comment

Popular posts from this blog

⭐ UNIT – 3 (Easy Notes + PDF References) Wireless LAN • MAC Problems • Hidden/Exposed Terminal • Near/Far • Infrastructure vs Ad-hoc • IEEE 802.11 • Mobile IP • Ad-hoc Routing

  ⭐ UNIT – 3 (Easy Notes + PDF References) Wireless LAN • MAC Problems • Hidden/Exposed Terminal • Near/Far • Infrastructure vs Ad-hoc • IEEE 802.11 • Mobile IP • Ad-hoc Routing I have rewritten everything in easy school-level English so you can understand quickly. 🔵 1. What is WLAN? (Wireless LAN) (Page 1 U-3 Wireless & mobile computing ) WLAN = Wireless Local Area Network. It allows devices to connect without cables using radio, infrared, or microwave signals. Why WLAN? ✔ No wires needed ✔ Quick installation ✔ Can attach to existing wired network ✔ Useful in disasters or old buildings where wiring is impossible 🔵 2. Design Goals of WLAN (Page 2–3 – Table shown in PDF U-3 Wireless & mobile computing ) ✔ Simple to use Users should easily connect. ✔ Low power use Mobile devices need long battery life. ✔ No license needed Using license-free bands reduces cost. ✔ Handle interference There is a lot of radio noise; WLAN must work even in interference. ...
Read more

UNIT–5 (Simplified & Easy Notes) Software Architecture Documentation

  UNIT–5 (Simplified & Easy Notes) Software Architecture Documentation ✅ What is Software Architecture Documentation? It explains how the software system is structured . Helps developers understand system components , modules , and design , without reading code. Works as a communication tool between architect, developer & stakeholder. ⭐ Goals of Documentation (Very Important) Knowledge Sharing Helps new developers understand the system quickly. Communication Architects share design ideas with developers. Analysis & Review Used to check if architecture meets requirements. ⭐ Two Ways to Create Architecture 1. Top-Down Approach Start from big design → break into smaller parts. Used when system requirements are clear. 2. Bottom-Up Approach Start from small components → combine to form system. Used when building systems step-by-step. ⭐ Principles of Sound Documentation (Super Important – Exam Repeated) Princ...
Read more

Unit III – Basics of IoT Networking

  Unit III – Basics of IoT Networking (Simple English Notes) 1. Basics of IoT Networking Internet of Things (IoT) is a network of physical devices connected through the internet that collect and exchange data. Examples: Smart watch Smart home devices Smart agriculture sensors Smart vehicles Main functions of IoT networking: Connect devices Transfer data Process information Control devices remotely Basic flow: Sensors → Network → Cloud/Server → User Application 2. IoT Components IoT mainly consists of four components: 1. Sensors/Devices Collect information from surroundings Example: Temperature sensor Motion sensor Humidity sensor 2. Connectivity Connects devices with internet Technologies: Wi-Fi Bluetooth ZigBee RFID 3. Data Processing Processes collected data Uses cloud or local servers 4. User Interface Shows output to users Example: Mobile app Web dashboard 3. Functional Components of IoT Functi...
Read more