This document provides an overview of key topics in object-oriented analysis and design that will be covered, including iterative development processes like the Unified Process, UML notation, requirements analysis, OOA/D principles, design patterns, and more. It discusses thinking in terms of objects and their services and responsibilities. Homework is assigned to define and discuss use cases, domain models, interaction diagrams, and class diagrams. Students are responsible for all material in Chapter 1.
This document provides an overview of the CS6502 Object Oriented Analysis and Design course. The course covers UML design diagrams, design patterns, case studies, applying design patterns, and coding and testing. It discusses the objectives of learning OOAD skills, UML, mapping design to code, and testing techniques. Textbooks and reference materials are also listed. The syllabus outlines five units covering UML diagrams, design patterns, a case study, applying patterns, and coding and testing.
Object-oriented modeling and design uses objects and classes to model real-world concepts. It promotes better understanding of requirements through analysis, design, and implementation using object-oriented notations and processes. Key characteristics include identity, classification through classes, inheritance for sharing features among classes, and polymorphism where operations behave differently for different classes. Modeling involves creating class, state, and interaction models. Object-oriented themes like abstraction, encapsulation, and inheritance allow for flexibility, reusability, and low maintenance costs.
This document provides an overview of object-oriented analysis and design (OOAD) concepts. It discusses iterative development processes like the Unified Process and agile approaches. It emphasizes thinking in terms of objects and their services and responsibilities. The document also covers UML notation, requirements analysis, design patterns, OOA/D principles, and implementing designs in code. Students will study these topics and be assigned homework to define and discuss domain models, interaction diagrams, class diagrams, and use cases.
This document provides an overview of object-oriented analysis and design (OOAD) concepts. It discusses iterative development processes like the Unified Process and agile approaches. It emphasizes thinking in terms of objects and their services and responsibilities. The document also covers UML notation, requirements analysis, design patterns, OOA which identifies problem domain objects, and OOD which defines how software objects meet requirements. Students will study these topics and be assigned homework to define and discuss domain models, interaction diagrams, class diagrams, and use cases.
This document provides an overview of object-oriented concepts, including a definition of object-orientation, its core characteristics, and a history of its development and modeling. It discusses the evolution of modeling languages like OMT and UML, and explains the different types of models in object-oriented development, including class, state, and interaction models. Key aspects of object-oriented technology and modeling concepts are defined.
Module3 - Object Oriented Analysis & Functional Model.pdfGerard Alba
This document provides an overview of Module 3 which covers object-oriented analysis and design (OOAD) and the functional model. It discusses how OOAD uses the Unified Modeling Language (UML) to represent different components and interactions of a software system through various diagrams. Specifically, it explains that Module 3 will focus on the functional model, which illustrates system functionality and user interactions, while Modules 4-6 will cover the dynamic and static models. The document also distinguishes between analysis, which understands system requirements, and design, which produces specifications to be implemented.
This document provides an introduction to object-oriented concepts and modeling. It discusses what object orientation is, its key characteristics like identity and inheritance, and the history of OO modeling. The document outlines the different types of models in OO including class, state, and interaction models. It also describes the Unified Modeling Language (UML) as a standard visual modeling language and lists some common UML diagram types used.
This document provides an introduction to object-oriented concepts and modeling. It discusses what object-orientation is, its key characteristics like identity and inheritance, and the history of OO modeling. The Unified Modeling Language (UML) is introduced as a standard modeling language. The document outlines the different types of UML models including class, state, and interaction models and explains modeling as a design technique to visualize, specify, and document systems.
The document provides an overview of system development methodologies, with a focus on structured analysis and design versus object-oriented analysis and design. It discusses the analysis, design, and implementation phases of an object-oriented systems development life cycle. In the analysis phase, it describes how use case diagrams and class diagrams are used to model object-oriented analysis using the Unified Modeling Language. It also provides guidance on identifying domain classes from problem statements by looking for noun phrases and applying subject matter expertise.
The document provides an overview of object-oriented analysis and design (OOAD). It discusses the objectives of learning OOAD skills like UML design diagrams and mapping design to code. The agenda includes an introduction to OOAD, UML diagrams, implementation, and OO testing. Object-oriented analysis focuses on identifying domain objects and requirements, while object-oriented design defines software objects and their relationships to meet requirements. UML is the standard notation used to capture objects and relationships. The design is then mapped to code through implementation. Testing ensures the software functions as intended.
The document provides an overview of object-oriented analysis and design (OOAD). It discusses key OOAD concepts like iterative development, the Unified Process, UML notation, thinking in terms of objects and their services/responsibilities. It explains the differences between object-oriented analysis, which focuses on identifying domain objects, and object-oriented design, which defines software objects and how they collaborate. The document uses a dice game example to illustrate domain modeling with objects, interaction diagrams to show message flows, and a class diagram to define class attributes and methods.
This document provides an overview of object-oriented analysis and design (OOAD). It discusses key concepts like objects, classes, attributes, methods, analysis, and design. OOAD models a system as interacting objects and involves analyzing concepts in the problem domain and designing software objects to represent those concepts. The document contrasts the traditional procedural approach with the object-oriented approach, which focuses on logical solutions based on objects. It provides examples of objects and classes and explains how objects are grouped into classes to define common attributes and behaviors.
The document discusses Unit II of a syllabus which covers class diagrams, including elaboration, domain modeling, finding conceptual classes and relationships. It discusses when to use class diagrams and provides examples of a class diagram for a hotel management system. It also discusses inception and elaboration phases in software development processes and provides artifacts used in elaboration. Finally, it discusses domain modeling including how to identify conceptual classes, draw associations, and avoid adding too many associations.
The document provides an overview of software engineering analysis and design. It discusses how analysis and design transforms requirements into a system design and software architecture. It covers inputs/outputs of analysis and design like use case models and design documents. Analysis focuses on understanding problems while design focuses on solutions. The document also discusses software architecture patterns, use case realization, object-oriented concepts, and the boundary, control, and entity design pattern used to decompose applications into boundary, control, and entity objects.
The document discusses object-oriented analysis and design (OOAD), providing an overview of OO concepts like objects, classes, relationships, and the OO development life cycle, and outlines 5 units that will be covered including introduction to OO, UML, OO analysis, OO design, and CASE tools.
This document discusses object-oriented system design and modeling. It introduces key concepts like object-oriented principles, the software development lifecycle, and UML modeling. It explains that object-oriented concepts are widely used in software solution design across domains. Skilled professionals with a strong foundation in object-oriented design are needed to fulfill increasing requirements. The document then covers stages of software development like analysis, design, and implementation. It also discusses phases of object-oriented development like analysis, design, and self-contained objects and classes.
Object-Oriented Analysis and Design (OOAD) is a software engineering methodology that involves using object-oriented concepts to design and implement software systems. OOAD involves a number of techniques and practices, including object-oriented programming, design patterns, UML diagrams, and use cases.
Object Modeling Technique (OMT) is real world based modeling approach for software modeling and designing. It was developed basically as a method to develop object-oriented systems and to support object-oriented programming. It describes the static structure of the system.
Object Modeling Technique is easy to draw and use. It is used in many applications like telecommunication, transportation, compilers etc. It is also used in many real world problems. OMT is one of the most popular object oriented development techniques used now-a-days. OMT was developed by James Rambaugh.
Purpose of Object Modeling Technique:
To test physical entity before construction of them.
To make communication easier with the customers.
To present information in an alternative way i.e. visualization.
To reduce the complexity of software.
To solve the real world problems.
Object Modeling Technique’s Models:
There are three main types of models that has been proposed by OMT.
Object Model:
Object Model encompasses the principles of abstraction, encapsulation, modularity, hierarchy, typing, concurrency and persistence. Object Model basically emphasizes on the object and class. Main concepts related with Object Model are classes and their association with attributes. Predefined relationships in object model are aggregation and generalization (multiple inheritance).
Dynamic Model:
Dynamic Model involves states, events and state diagram (transition diagram) on the model. Main concepts related with Dynamic Model are states, transition between states and events to trigger the transitions. Predefined relationships in object model are aggregation (concurrency) and generalization.
Functional Model:
Functional Model focuses on the how data is flowing, where data is stored and different processes. Main concepts involved in Functional Model are data, data flow, data store, process and actors. Functional Model in OMT describes the whole processes and actions with the help of data flow diagram (DFD).
Phases of Object Modeling Technique:
OMT has the following phases:
Analysis:
This the first phase of the object modeling technique. This phase involves the preparation of precise and correct modelling of the real world problems. Analysis phase starts with setting a goal i.e. finding the problem statement. Problem statement is further divided into above discussed three models i.e. object, dynamic and functional model.
System Design:
This is the second phase of the object modeling technique and it comes after the analysis phase. It determines all system architecture, concurrent tasks and data storage. High level architecture of the system is designed during this phase.
FOR MORE INFORMATION CLICK ON THE LINK BELOW :
https://uii.io/programming
This chapter introduces object-oriented system development, including the concepts of objects, classes, inheritance, and encapsulation. It discusses the three main phases of OO development: object-oriented analysis (OOA), object-oriented design (OOD), and object-oriented programming (OOP). The chapter also outlines the benefits of the OO approach and provides an overview of the topics that will be covered in the book, including defining problem domain classes, graphical user interfaces, and data access classes.
This document discusses software engineering concepts related to object-oriented analysis and design. It defines key terms like object, class, attributes, and methods. It describes object-oriented analysis techniques like object modeling, dynamic modeling, and functional modeling. It also discusses object-oriented design concepts like abstraction, encapsulation, inheritance, and polymorphism. The document also introduces Unified Modeling Language (UML) diagrams like use case diagrams, sequence diagrams, and design principles like modularity, refinement, and functional independence.
Object-oriented analysis and design (OOAD) is a popular approach for analyzing, designing, and developing applications using the object-oriented paradigm. It involves modeling a system as a group of interacting objects at various levels of abstraction. Key concepts in OOAD include objects, classes, attributes, methods, encapsulation, inheritance, polymorphism, and relationships like association, aggregation, and composition. Common OOAD techniques include use case diagrams, which show interactions between actors and the system, and class diagrams, which describe the structure and behavior of system objects and their relationships.
This document provides an overview of object-oriented analysis and design. It discusses key concepts in object-oriented programming including objects, classes, attributes, methods, encapsulation, inheritance, polymorphism, associations, and persistence. The document uses examples like an employee payroll program to illustrate how an object-oriented approach models real-world entities as objects that can be easily modified, replaced and reused when requirements change.
The document discusses the key elements of the object model, including abstraction, encapsulation, modularity, and hierarchy. It explains that abstraction is one of the fundamental ways to cope with complexity in software design. Abstraction focuses on the essential characteristics of an object that distinguish it from other objects, from the perspective of the viewer. The object model provides a conceptual framework for object-oriented programming that is based on these elements.
The document discusses abstraction, which is a fundamental concept of object-oriented design. Abstraction involves focusing on essential characteristics of an object that distinguish it from others, separating an object's interface from its implementation. There are different types of abstractions from most to least useful: entity, action, virtual machine, and coincidental. Other key concepts discussed include contracts, invariants, exceptions, static and dynamic properties, and passive vs. active objects.
The document discusses abstraction, which is a fundamental concept of object-oriented design. Abstraction involves focusing on an object's essential characteristics and behavior while hiding implementation details. There are different types of abstractions from most useful to least useful. Effective abstractions model real-world entities and provide well-defined interfaces through contracts, preconditions, and postconditions. Both static and dynamic properties of objects must be considered.
This document provides an introduction to object-oriented concepts and modeling. It discusses what object-orientation is, its key characteristics like identity and inheritance, and the history of OO modeling. The Unified Modeling Language (UML) is introduced as a standard modeling language. The document outlines the different types of UML models including class, state, and interaction models and explains modeling as a design technique to visualize, specify, and document systems.
The document provides an overview of system development methodologies, with a focus on structured analysis and design versus object-oriented analysis and design. It discusses the analysis, design, and implementation phases of an object-oriented systems development life cycle. In the analysis phase, it describes how use case diagrams and class diagrams are used to model object-oriented analysis using the Unified Modeling Language. It also provides guidance on identifying domain classes from problem statements by looking for noun phrases and applying subject matter expertise.
The document provides an overview of object-oriented analysis and design (OOAD). It discusses the objectives of learning OOAD skills like UML design diagrams and mapping design to code. The agenda includes an introduction to OOAD, UML diagrams, implementation, and OO testing. Object-oriented analysis focuses on identifying domain objects and requirements, while object-oriented design defines software objects and their relationships to meet requirements. UML is the standard notation used to capture objects and relationships. The design is then mapped to code through implementation. Testing ensures the software functions as intended.
The document provides an overview of object-oriented analysis and design (OOAD). It discusses key OOAD concepts like iterative development, the Unified Process, UML notation, thinking in terms of objects and their services/responsibilities. It explains the differences between object-oriented analysis, which focuses on identifying domain objects, and object-oriented design, which defines software objects and how they collaborate. The document uses a dice game example to illustrate domain modeling with objects, interaction diagrams to show message flows, and a class diagram to define class attributes and methods.
This document provides an overview of object-oriented analysis and design (OOAD). It discusses key concepts like objects, classes, attributes, methods, analysis, and design. OOAD models a system as interacting objects and involves analyzing concepts in the problem domain and designing software objects to represent those concepts. The document contrasts the traditional procedural approach with the object-oriented approach, which focuses on logical solutions based on objects. It provides examples of objects and classes and explains how objects are grouped into classes to define common attributes and behaviors.
The document discusses Unit II of a syllabus which covers class diagrams, including elaboration, domain modeling, finding conceptual classes and relationships. It discusses when to use class diagrams and provides examples of a class diagram for a hotel management system. It also discusses inception and elaboration phases in software development processes and provides artifacts used in elaboration. Finally, it discusses domain modeling including how to identify conceptual classes, draw associations, and avoid adding too many associations.
The document provides an overview of software engineering analysis and design. It discusses how analysis and design transforms requirements into a system design and software architecture. It covers inputs/outputs of analysis and design like use case models and design documents. Analysis focuses on understanding problems while design focuses on solutions. The document also discusses software architecture patterns, use case realization, object-oriented concepts, and the boundary, control, and entity design pattern used to decompose applications into boundary, control, and entity objects.
The document discusses object-oriented analysis and design (OOAD), providing an overview of OO concepts like objects, classes, relationships, and the OO development life cycle, and outlines 5 units that will be covered including introduction to OO, UML, OO analysis, OO design, and CASE tools.
This document discusses object-oriented system design and modeling. It introduces key concepts like object-oriented principles, the software development lifecycle, and UML modeling. It explains that object-oriented concepts are widely used in software solution design across domains. Skilled professionals with a strong foundation in object-oriented design are needed to fulfill increasing requirements. The document then covers stages of software development like analysis, design, and implementation. It also discusses phases of object-oriented development like analysis, design, and self-contained objects and classes.
Object-Oriented Analysis and Design (OOAD) is a software engineering methodology that involves using object-oriented concepts to design and implement software systems. OOAD involves a number of techniques and practices, including object-oriented programming, design patterns, UML diagrams, and use cases.
Object Modeling Technique (OMT) is real world based modeling approach for software modeling and designing. It was developed basically as a method to develop object-oriented systems and to support object-oriented programming. It describes the static structure of the system.
Object Modeling Technique is easy to draw and use. It is used in many applications like telecommunication, transportation, compilers etc. It is also used in many real world problems. OMT is one of the most popular object oriented development techniques used now-a-days. OMT was developed by James Rambaugh.
Purpose of Object Modeling Technique:
To test physical entity before construction of them.
To make communication easier with the customers.
To present information in an alternative way i.e. visualization.
To reduce the complexity of software.
To solve the real world problems.
Object Modeling Technique’s Models:
There are three main types of models that has been proposed by OMT.
Object Model:
Object Model encompasses the principles of abstraction, encapsulation, modularity, hierarchy, typing, concurrency and persistence. Object Model basically emphasizes on the object and class. Main concepts related with Object Model are classes and their association with attributes. Predefined relationships in object model are aggregation and generalization (multiple inheritance).
Dynamic Model:
Dynamic Model involves states, events and state diagram (transition diagram) on the model. Main concepts related with Dynamic Model are states, transition between states and events to trigger the transitions. Predefined relationships in object model are aggregation (concurrency) and generalization.
Functional Model:
Functional Model focuses on the how data is flowing, where data is stored and different processes. Main concepts involved in Functional Model are data, data flow, data store, process and actors. Functional Model in OMT describes the whole processes and actions with the help of data flow diagram (DFD).
Phases of Object Modeling Technique:
OMT has the following phases:
Analysis:
This the first phase of the object modeling technique. This phase involves the preparation of precise and correct modelling of the real world problems. Analysis phase starts with setting a goal i.e. finding the problem statement. Problem statement is further divided into above discussed three models i.e. object, dynamic and functional model.
System Design:
This is the second phase of the object modeling technique and it comes after the analysis phase. It determines all system architecture, concurrent tasks and data storage. High level architecture of the system is designed during this phase.
FOR MORE INFORMATION CLICK ON THE LINK BELOW :
https://uii.io/programming
This chapter introduces object-oriented system development, including the concepts of objects, classes, inheritance, and encapsulation. It discusses the three main phases of OO development: object-oriented analysis (OOA), object-oriented design (OOD), and object-oriented programming (OOP). The chapter also outlines the benefits of the OO approach and provides an overview of the topics that will be covered in the book, including defining problem domain classes, graphical user interfaces, and data access classes.
This document discusses software engineering concepts related to object-oriented analysis and design. It defines key terms like object, class, attributes, and methods. It describes object-oriented analysis techniques like object modeling, dynamic modeling, and functional modeling. It also discusses object-oriented design concepts like abstraction, encapsulation, inheritance, and polymorphism. The document also introduces Unified Modeling Language (UML) diagrams like use case diagrams, sequence diagrams, and design principles like modularity, refinement, and functional independence.
Object-oriented analysis and design (OOAD) is a popular approach for analyzing, designing, and developing applications using the object-oriented paradigm. It involves modeling a system as a group of interacting objects at various levels of abstraction. Key concepts in OOAD include objects, classes, attributes, methods, encapsulation, inheritance, polymorphism, and relationships like association, aggregation, and composition. Common OOAD techniques include use case diagrams, which show interactions between actors and the system, and class diagrams, which describe the structure and behavior of system objects and their relationships.
This document provides an overview of object-oriented analysis and design. It discusses key concepts in object-oriented programming including objects, classes, attributes, methods, encapsulation, inheritance, polymorphism, associations, and persistence. The document uses examples like an employee payroll program to illustrate how an object-oriented approach models real-world entities as objects that can be easily modified, replaced and reused when requirements change.
The document discusses the key elements of the object model, including abstraction, encapsulation, modularity, and hierarchy. It explains that abstraction is one of the fundamental ways to cope with complexity in software design. Abstraction focuses on the essential characteristics of an object that distinguish it from other objects, from the perspective of the viewer. The object model provides a conceptual framework for object-oriented programming that is based on these elements.
The document discusses abstraction, which is a fundamental concept of object-oriented design. Abstraction involves focusing on essential characteristics of an object that distinguish it from others, separating an object's interface from its implementation. There are different types of abstractions from most to least useful: entity, action, virtual machine, and coincidental. Other key concepts discussed include contracts, invariants, exceptions, static and dynamic properties, and passive vs. active objects.
The document discusses abstraction, which is a fundamental concept of object-oriented design. Abstraction involves focusing on an object's essential characteristics and behavior while hiding implementation details. There are different types of abstractions from most useful to least useful. Effective abstractions model real-world entities and provide well-defined interfaces through contracts, preconditions, and postconditions. Both static and dynamic properties of objects must be considered.
Venngage’s AI Infographic Generator helps you bring clarity to your content by turning plain text into visually compelling infographics—automatically. Designed with marketers and communicators in mind, it’s built to simplify complex messaging and speed up your workflow.
With just a short prompt, the AI understands your intent and creates a structured infographic that fits your content type—whether you’re outlining a process, comparing features, or mapping out a timeline. The tool selects fonts, icons, layouts, and visual hierarchy for you, taking care of the heavy lifting in seconds.
Once generated, you can fully customize the design to align with your brand—tweak colors, edit text, replace visuals, and adjust layout elements using a simple drag-and-drop editor. The tool supports different infographic styles, making it ideal for internal reports, client presentations, blog content, and social media graphics.
What makes it valuable for marketers?
- Eliminate bottlenecks in the content creation process
- Get campaign visuals and data summaries out faster
- Repackage written content into visuals that perform better on social and email
- Communicate insights clearly with clients and internal teams
Whether you're on a tight deadline or just want to simplify your storytelling, Venngage’s AI helps you create high-impact visuals without relying on a designer or starting from scratch.
Generate AI Infographics here: https://venngage.com/ai-tools/infographic-generator
Download Link Below 👇
https://techblogs.cc/dl/
Wondershare Filmora Crack is a versatile video editing software designed for both beginners and intermediate creators.
Internet Download Manager Crack Patch Latest IDM Free DownloadDesigner
Download Link Below 👇
https://techblogs.cc/dl/
A premium Windows tool that maximizes download speeds and manages downloads efficiently. Internet Download Manager (IDM) is a tool to increase download speeds by up to 10 times, resume or schedule downloads and download streaming videos.
Elevate your wardrobe with this chic abstract print shirt. Featuring a collared V-neck and button-down front, this versatile piece offers a relaxed fit with long sleeves. The striking black and white pattern adds a modern touch to any outfit, perfect for both casual and semi-formal occasions.
2. Objective
• Object Oriented Analysis and Design Using UML
present the concepts and techniques necessary
to effectively use system requirements to drive
the development of a robust design model.
• In this intensive, students can learn to apply the
Unified Modeling Language (UML) to
fundamental object-oriented analysis and
design concepts including architecture, objects,
classes, components, stereotypes,
relationships, and all supporting diagrams.
3. • The UML is used throughout the project lifecycle
to capture and communicate analysis and design
decisions.
• Students will understand OOAD Concepts, learn
to represent it with UML and document it using
UML modeling tool. T
• he class will be concept & Case study driven and
wherever necessary tool will be used.
4. Chapter 00: Analysis and Design with UML
• Unified Modeling Language (UML)
• Why Construct Model?
• UML Diagram
• Type of UML Diagram
5. Chapter 01: Object Oriented Analysis and
Design (OOAD)
• Object Orientation (OO) and Object Oriented Method
(OOM)
• Object Oriented Modeling
• Polymorphism
• Inheritance
• Object Oriented Analysis and Design
• Jacobson Use Case Method (OO Software Engineering –
OOSE)
6. • System Development
– Requirement Model
– Analysis Model
– Design Model
– Implementation Model
– Test Model
– Unified Modeling Language (UML)
• The Value of UML
• History of UML
• Overview of the UML
7. Chapter 02: Complexity
• Complexity
• Complexity Crisis
• General Idea of How to Deal with Complexity
• The Structure of Complex System
• Five Attributes of a Complex System
• Bringing Order to Chaos
• On Designing Complex Systems
8. Chapter 03: The Object Model (OM)
• Element of Object Model
– Four Major Elements of OM
– Three Minor Elements of OM
Chapter 04: Classes and Objects
• Nature of an Objects
• Relationship among Objects
• Nature of Class
• Relationship among Classes
9. Chapter 05: Basic OOAD Process
• Basic OO Concept
• Basic OOAD Process
• The four Ps
Chapter 06: Project Management
• Project Management
• Software Project Management
• Project Plan Structure
• The Risk Management Process
• Organization of the Software Project
Management Plan Document
10. Evaluation System:
• Internal evaluation : 50
Attendance : 05
Assignment : 10
Case Study : 20
Internal Test : 10
Class Assignment : 05
• End Semester Evaluation : 50
12. What Is an Object?
• Definition: An object is a software bundle of
variables and related methods.
• As the name object-oriented implies, objects are
key to understanding object-oriented technology.
• You can look around you now and see many
examples of real-world objects: your dog, your
desk, your television set, your bicycle.
• Software objects are modeled after real-world
objects in that they, too, have state and behavior.
• A software object maintains its state in variables
and implements its behavior with methods.
13. • The following illustration is a common visual
representation of a software object:
14. • These real-world objects share two
characteristics: they all have state and they all
have behavior.
• For example, dogs have state (name, color,
breed, hungry) and dogs have behavior (barking,
fetching, and slobbering on your newly cleaned
slacks).
• Bicycles have state (current gear, current pedal
cadence, two wheels, number of gears) and
behavior (braking, accelerating, slowing down,
changing gears).
16. A Partial Sample Process
Build -
Exploratory
Emphasis
Explore Refine Plan Build Deploy
Plan and
Elaborate
Build - System
Functions
Emphasis
Build -
Infrastructure
Emphasis
33. A Simple Object Model
+Admit()
+Regsiter for Classes()
+Withdraw()
+Change Address()
+Calculate GPA()
+Graduate()
-ID Number
-Name
-Grade Point Average
STUDENT
+Create a Course()
+Delete from Course Master()
+Change in Course Master()
-Subject
-Number
-Title
-Credit
COURSE
+Add()
+Drop()
+Complete()
+Change Grade()
-Semester
-Division
-Grade
TRANSCRIPT COURSE
1
1
has record for>
0..*
0..*