Ooad 2m+i

Short answer
1. Compare coupling and cohesion

2. Responsibility of access layer
3. Define debugging
4. What is meant by user sa sfac on?
5. Define associa on
6. Types of error
7. Characteris cs of bad design
8. Issues of so ware quality.
Long answer
1. Guidelines for iden fy the supersub rela onship.
2. A part of rela onship with pa ern example
3. Design axioms and collaries
4. Differen ate tes ng strategies
5. Guidelines for iden fying quality assurance test
6. Steps in design access layer
7. Usability tes ng
8. Users Sa sfac on test and it's guidelines
9. Guidelines for common associa on pa ern and eliminate the unnecessary
associa on.
1.Cohesion and Coupling : Effective System Usage:
Cohesion Coupling Users are satisfied when the system effectively supports their tasks and goals.
The system should provide the functionality and features necessary for users to accomplish their
Cohesion is the concept of intra-module. Coupling is the concept of inter-module.
objectives efficiently.
Cohesion represents the relationship within a Coupling represents the relationships between Positive User Experience:
module. modules.
User satisfaction in OOAD is associated with a positive overall experience.
Increasing cohesion is good for software. Increasing coupling is avoided for software.
This includes factors such as an intuitive user interface, efficient interaction, and a system that aligns
Cohesion represents the functional strength of Coupling represents the independence among with user expectations.
modules. modules.
5.Association
Whereas loosely coupling gives the best
Highly cohesive gives the best software. software. Association is a semantically weak relationship (a semantic dependency) between otherwise unrelated
objects. An association is a “using” relationship between two or more objects in which the objects have
In cohesion, the module focuses on a single In coupling, modules are connected to the other their own lifetime and there is no owner.
thing. modules.
As an example, imagine the relationship between a doctor and a patient. A doctor can be associated with
Coupling is created between two different multiple patients. At the same time, one patient can visit multiple doctors for treatment or consultation.
Cohesion is created between the same module. modules. Each of these objects has its own life cycle and there is no “owner” or parent. The objects that are part
of the association relationship can be created and destroyed independently.
2. Responsibility of access layer: 6.Types of error:
The access layer in object-oriented analysis and design (OOAD) is primarily responsible for  Syntax Errors
encapsulating data access logic, providing a clean separation between application logic and data storage  Logical Errors
mechanisms. It manages tasks such as database interactions, security enforcement, and encapsulation of  Runtime Errors
implementation details to enhance system modularity and maintainability.  Semantic Errors
 Design Errors
 Requirement Errors
3. Debugging  Integration Errors
 User Interface Errors
Debugging in Object-Oriented Analysis and Design (OOAD) is the process of identifying and fixing
errors in a software system. It involves: 7.Characteristics of bad design:
Issue Identification :  Lack of Modularity.
Recognizing discrepancies between expected and actual software behavior.  Inconsistent Naming Conventions
 Tight Coupling
Identifying logical errors, runtime issues, or failures to meet specified requirements.  Excessive Complexity
Analysis and Correction :  Inadequate Documentation
Analyzing the source of errors by examining code, data structures, and component interactions. 8.Issues of software quality:
Using debugging tools to make corrections, ensuring the software functions as intended.  Bugs and Defects
 Performance Problems
 Security Vulnerabilities
4.User Satisfaction  Usability Challenges
 Maintainability Issues
User satisfaction refers to the level of contentment and positive experience that users derive from
the software system being developed. It is a subjective measure that assesses how well the system meets
the needs and expectations of its intended users. Key aspects of user satisfaction include:

Ooad 2m+i

Uploaded by

Copyright:

Available Formats

Ooad 2m+i

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Ooad 2m+i

Uploaded by

Copyright:

Available Formats

Short answer

1. Compare coupling and cohesion

2. Responsibility of access layer: 6.Types of error:

You might also like