unit 5 (OOSE)

 

Object-Oriented Testing and Design Patterns (RGPV Notes)

Important: Using the same terminology throughout:

• OOA = Object-Oriented Analysis
• OOD = Object-Oriented Design
• OO Testing = Object-Oriented Testing

---

1. Object-Oriented Testing

Definition

Object-Oriented Testing is the process of testing classes, objects, methods, interactions, and relationships in an object-oriented software system.

Objectives

1. Find errors in classes and objects.
2. Verify software requirements.
3. Ensure system quality.
4. Improve reliability.
5. Validate object interactions.
6. Check correctness of design.
7. Ensure proper functionality.

---

2. Correctness of OOA and OOD Models

Definition

Correctness means the OOA and OOD models accurately represent the user requirements.

Correctness Checks

1. All requirements are included.
2. Classes are properly identified.
3. Relationships are correctly defined.
4. Use cases match requirements.
5. Objects perform required functions.
6. No missing functionality.
7. Design supports implementation.

Example

If a Course Registration System requires student registration, then Student and Registration classes must be present.

---

3. Consistency of OOA and OOD Models

Definition

Consistency means all UML models agree with each other and contain no contradictions.

Consistency Checks

1. Class names should remain same in all diagrams.
2. Relationships should be consistent.
3. Use cases should match class operations.
4. State transitions should be valid.
5. Object interactions should follow design.
6. No conflicting information.
7. All diagrams should support the same requirements.

Example

If a Student class exists in Class Diagram, it should also appear where required in Sequence Diagram and Use Case Diagram.

---

4. Testing Strategies for OO Software

Definition

Testing Strategy is a planned approach used to test object-oriented software.

Types of Testing

1. Unit Testing

Tests individual classes and methods.

2. Integration Testing

Tests interaction between classes.

3. System Testing

Tests the complete software system.

4. Validation Testing

Checks whether requirements are satisfied.

5. Acceptance Testing

Performed by customer or end user.

---

7-Mark Answer: Testing Strategy

1. Unit Testing verifies individual classes.
2. Integration Testing verifies object interactions.
3. System Testing checks complete system behavior.
4. Validation Testing checks requirements.
5. Acceptance Testing is performed by users.
6. Testing improves software quality.
7. Testing helps identify defects early.

---

5. Test Cases for OO Software

Definition

A Test Case is a set of inputs, conditions, and expected outputs used to verify software functionality.

Components of a Test Case

1. Test Case ID
2. Objective
3. Input
4. Execution Steps
5. Expected Output
6. Actual Output
7. Result

---

Example

Login Test Case

Field	Value
Test Case ID	TC01
Input	Valid Username & Password
Expected Output	Login Successful
Result	Pass

---

Advantages

1. Easy defect tracking.
2. Improves quality.
3. Ensures requirement coverage.
4. Supports systematic testing.

---

6. Project Management

Definition

Project Management is the process of planning, organizing, executing, and controlling software projects.

Activities

1. Project Planning
2. Resource Allocation
3. Scheduling
4. Risk Management
5. Cost Estimation
6. Monitoring
7. Project Control

---

Objectives

1. Complete project on time.
2. Complete project within budget.
3. Achieve project goals.
4. Improve productivity.
5. Reduce risks.

---

7. Rational Tool Mentor

Definition

Rational Tool Mentor is a support feature in Rational Rose that provides guidance for UML modeling and software development activities.

Features

1. Provides development guidelines.
2. Supports UML modeling.
3. Helps project documentation.
4. Improves development process.
5. Provides best practices.
6. Helps beginners learn UML.
7. Supports Rational Rose users.

---

8. Introduction to Design Patterns

Definition

A Design Pattern is a reusable solution to a commonly occurring software design problem.

Purpose

1. Reuse proven solutions.
2. Improve software design.
3. Reduce development time.
4. Increase maintainability.
5. Improve flexibility.

---

Types of Design Patterns

1. Creational Patterns

Deal with object creation.

Example: Singleton

2. Structural Patterns

Deal with class and object structure.

Example: Adapter

3. Behavioral Patterns

Deal with communication between objects.

Example: Observer

---

Advantages of Design Patterns

1. Reusable solutions.
2. Better code quality.
3. Easier maintenance.
4. Faster development.
5. Improved flexibility.
6. Better communication among developers.
7. Reduced complexity.

---

Revision Points (Quick Notes)

Object-Oriented Testing

• Tests classes, objects, methods, and interactions.
• Improves software quality.

Keyword: Testing Objects and Classes

---

Correctness

• Requirements are correctly represented.
• No missing functionality.

Keyword: Right Model

---

Consistency

• All UML diagrams agree with each other.
• No contradictions.

Keyword: Same Information Everywhere

---

Testing Strategy

• Unit Testing
• Integration Testing
• System Testing
• Validation Testing
• Acceptance Testing

Keyword: Unit → Integration → System → Validation → Acceptance

---

Test Case

Contains:

• ID
• Input
• Steps
• Expected Output
• Result

Keyword: Verify Functionality

---

Project Management

• Planning
• Scheduling
• Resource Allocation
• Risk Management
• Monitoring

Keyword: Plan and Control Project

---

Rational Tool Mentor

• Guidance tool in Rational Rose.
• Provides best practices.

Keyword: UML Development Support

---

Design Pattern

• Reusable solution to common design problems.

Types

• Creational
• Structural
• Behavioral

Keyword: Reusable Design Solution

---

2-Mark Revision Sheet

Correctness

Model correctly represents requirements.

Consistency

All UML models agree with each other.

Unit Testing

Testing individual classes.

Integration Testing

Testing interaction between classes.

Test Case

Input + Expected Output + Result.

Project Management

Planning and controlling software projects.

Rational Tool Mentor

Guidance feature of Rational Rose.

Design Pattern

Reusable solution to a common software design problem.

---

Last 30-Second Revision

OO Testing → Correctness → Consistency → Testing Strategy → Test Case → Project Management → Rational Tool Mentor → Design Pattern → Creational → Structural → Behavioral