Lecture Notes Of Class 3: Introduction to UML (Unified Modeling Language)

Lecture Notes Of Class 3: Introduction to UML (Unified Modeling Language)

Objective:

The goal of this class is to introduce students to the Unified Modeling Language (UML), which is used for visualizing, specifying, constructing, and documenting the software system. By the end of this session, students should understand the importance of UML in software development and be familiar with several types of UML diagrams. Additionally, students will learn how to create a Class Diagram for a given system, such as a Library Management System.

What is UML (Unified Modeling Language)?

UML is a standardized modeling language used in the software industry to visually represent the design and architecture of a software system. It provides a set of graphical notations to create models that describe the structure and behavior of a system.

UML can be used in object-oriented programming (OOP) and is a way to communicate complex systems in a simplified and understandable manner. UML is especially useful during the design phase of the software development lifecycle.

Importance of UML:

1. Visualization: UML diagrams provide a visual representation of a system's architecture and behavior, which makes it easier for developers, architects, and stakeholders to understand how the system works.

2. Specification: UML helps in specifying the requirements of the system, detailing the system's behavior, interactions, and structure.

3. Construction: UML models guide the actual development of the system, ensuring developers know how to implement the required components.

4. Documentation: UML serves as documentation for future reference, allowing developers to maintain and update the system effectively.

Types of UML Diagrams:

UML consists of several types of diagrams, which can be broadly categorized into two main groups:

1. Structural Diagrams (Static Models):

These diagrams focus on the structure or organization of the system.

Class Diagram: Represents the structure of the system by showing the system's classes, their attributes, methods, and the relationships between them.
Object Diagram: A snapshot of instances of the objects in the system at a given point in time.
Component Diagram: Shows how components (modular parts of a system) interact with each other.
Deployment Diagram: Illustrates the physical deployment of artifacts on nodes (hardware).
Package Diagram: Organizes a system into packages (groups of related classes).

2. Behavioral Diagrams (Dynamic Models):

These diagrams focus on the behavior and interactions within the system.

Use Case Diagram: Represents the interactions between users (actors) and the system, showing what functionalities the system provides.
Sequence Diagram: Represents how objects interact in a sequence of time, focusing on the messages exchanged between objects.
Activity Diagram: Shows the workflow of actions in a system, describing the step-by-step flow of control.
State Diagram: Represents the states of an object and the transitions between them based on events.

Focus for Today: Class Diagram

Among the various UML diagrams, the Class Diagram is one of the most commonly used and is considered the backbone of object-oriented modeling. It helps in visualizing the classes in a system and how they are related to one another.

Key Components of a Class Diagram:

1. Class: A class is represented as a rectangle with three sections:

o Top Section: Contains the name of the class.

o Middle Section: Contains the attributes (properties) of the class.

o Bottom Section: Contains the methods (functions) of the class.

2. Attributes: Characteristics or properties of a class. For example, a Book class might have attributes like title, author, and ISBN.

3. Methods: Functions or behaviors of a class. For example, a Book class might have methods like borrow(), return(), and getDetails().

4. Relationships between Classes:

o Association: A relationship between two classes where one class uses or is linked to another. Represented by a line.

o Multiplicity: Specifies the number of instances of one class that can be related to another class. For example, "1" means one instance, and "*" means many instances.

o Inheritance (Generalization): A relationship where a subclass inherits properties and methods from a superclass. Represented by a line with a triangle pointing to the superclass.

o Aggregation: A special form of association where one class is part of another class. Represented by a line with a hollow diamond at the aggregate class.

o Composition: A stronger form of aggregation where if the parent object is deleted, the child objects are also deleted. Represented by a line with a filled diamond.

Creating a Class Diagram for a Library Management System:

Let's apply our knowledge to create a Class Diagram for a Library Management System. This system allows users to borrow and return books, and administrators to manage books and users.

Steps to Create a Class Diagram:

1. Identify the Main Entities: First, we need to identify the main entities in the system. Some key entities for a Library Management System could be:

o Book

o Member

o Librarian

o Transaction (Borrowing/Returning books)

2. Define the Attributes and Methods for Each Class:

o Book:

§ Attributes:

§ bookID

§ title

§ author

§ publisher

§ year

§ Methods:

§ borrowBook()

§ returnBook()

§ getDetails()

o Member:

§ Attributes:

§ memberID

§ name

§ email

§ phone

§ Methods:

§ register()

§ borrowBook()

§ returnBook()

o Librarian:

§ Attributes:

§ librarianID

§ name

§ employeeID

§ Methods:

§ addBook()

§ removeBook()

§ viewTransactions()

o Transaction:

§ Attributes:

§ transactionID

§ borrowDate

§ returnDate

§ bookID

§ memberID

§ Methods:

§ createTransaction()

§ closeTransaction()

3. Identify Relationships Between Classes:

o Book and Transaction: A Book can be associated with many Transactions, and a Transaction can involve only one Book at a time. This is an association relationship.

o Member and Transaction: A Member can have many Transactions, but each Transaction belongs to only one Member. This is also an association relationship.

o Librarian and Book: A Librarian manages many Books (Add/Remove). This can be an aggregation or association.

4. Draw the Diagram:

o Place all the classes (Book, Member, Librarian, Transaction) as rectangles.

o Connect them with lines to show relationships (association, aggregation).

o Add arrows where necessary to show direction (e.g., for inheritance or dependency).

Exercise: Draw a Class Diagram for a Library Management System

Based on the previous steps, try drawing a Class Diagram for a Library Management System using UML notation. Here's a rough outline:

scss

CopyEdit

+-------------------+ +-----------------+ +--------------------+ +------------------------+

+-------------------+ +-----------------+ +--------------------+ +------------------------+

| returnBook() | | returnBook() | +--------------------+ +------------------------+

| getDetails() | +-----------------+

+-------------------+ | borrowBook() |

| returnBook() |

+------------------+

Conclusion:

In this class, we learned about the importance and types of UML diagrams, with a focus on the Class Diagram. By creating a Class Diagram for the Library Management System, we understood how to define classes, their attributes, methods, and relationships between them. UML diagrams play a crucial role in the planning and design of complex software systems, providing clear and concise documentation for both developers and stakeholders.

Next Steps:

In the next class, we will continue to explore other UML diagrams, such as Use Case Diagrams and Sequence Diagrams, and how to apply them in the design of our software systems.

4o mini

You said:

continue

ChatGPT said:

ChatGPT

Class 3: Continuation – Understanding More UML Diagrams

In this section, we will continue exploring UML and dive into additional key diagrams that are important for system design. These diagrams provide a deeper understanding of the system’s behavior and interactions. After completing the Class Diagram exercise in the previous section, it is now time to discuss Use Case Diagrams, Sequence Diagrams, and Activity Diagrams in more detail.

1. Use Case Diagram

A Use Case Diagram is a behavioral diagram in UML that describes the functional requirements of a system. It illustrates the system's interactions with external entities, known as actors, and shows what the system is supposed to do in response to user inputs.

Key Components of a Use Case Diagram:

Actors: External entities that interact with the system, such as users or other systems. An actor can be a human, another system, or an organization. In the Library Management System, actors might include the Member and the Librarian.
Use Cases: Represent the system's functionalities. These are actions that an actor performs with the system, such as "borrow book," "return book," or "add book."
Associations: Lines connecting actors to the use cases they interact with, showing how the actor is related to the functionality.
System Boundary: A rectangle around the use cases that defines the scope of the system. This helps to visualize the boundaries of the system's functionalities.

Example: Use Case Diagram for a Library Management System

In our Library Management System, the actors and use cases could be as follows:

Actors:

Member: Can borrow and return books.
Librarian: Can add, remove, and update books in the system.

Use Cases:

Borrow Book: The Member borrows a book.
Return Book: The Member returns a borrowed book.
Add Book: The Librarian adds a new book to the system.
Remove Book: The Librarian removes a book from the system.
View Transaction History: Both the Member and the Librarian can view transaction history.

Diagram Example:

sql

CopyEdit

+-----------------------------------------+

| Library System |

| +-----------------------------------+ |

| | Borrow Book [ Member ] | |

| | Return Book [ Member ] | |

| | Add Book [ Librarian ] | |

| | Remove Book [ Librarian ] | |

| | View Transactions [ Member ] | |

| | View Transactions [ Librarian ] | |

| +-----------------------------------+ |

+-----------------------------------------+

2. Sequence Diagram

A Sequence Diagram is another behavioral diagram in UML that shows how objects interact in a particular sequence over time. It is useful for depicting the flow of messages between objects in response to a specific use case or action.

Key Components of a Sequence Diagram:

Objects: Represented by vertical dashed lines (lifelines). These are the entities that participate in the interaction.
Messages: Represented by horizontal arrows between objects. These indicate the communication or method calls between the objects.
Activation Boxes: Thin rectangles on the lifelines that indicate when an object is active (i.e., when it is performing a task).

Example: Sequence Diagram for Borrowing a Book

Let's consider the sequence of actions when a Member borrows a book. The objects involved could be:

Member (actor)
Library System (the system handling the process)
Book (the object representing the book in the system)

Step-by-Step Interaction:

1. The Member requests to borrow a book from the Library System.

2. The Library System checks if the book is available.

3. If the book is available, the Library System updates the status of the book to "borrowed" and registers the transaction.

4. The Library System confirms the transaction to the Member.

Diagram Example:

scss

CopyEdit

Member Library System Book

| | |

|--- borrowBook() ----->| |

| |--- checkAvailability() -->|

| | |-- isAvailable? -->|

| |<-- updateStatus()--|<-- borrowed -->|

| |--- registerTransaction() --->|

| |<-- confirmTransaction()--|

|<---- TransactionConfirmed----|

3. Activity Diagram

An Activity Diagram is a behavioral diagram that represents the flow of activities or tasks in a system. It is useful for modeling the workflow and describing the sequence of actions in a process.

Key Components of an Activity Diagram:

Activities: Represented by rounded rectangles. These are tasks that the system performs.
Transitions: Arrows that show the flow from one activity to another.
Start and End Points: The initial and final states of the activity flow. The start is shown by a filled circle, and the end is shown by a circle with a dot inside.
Decision Nodes: Diamonds represent decision points in the workflow, where the flow can branch based on conditions.

Example: Activity Diagram for Borrowing a Book

For the process of borrowing a book, the activities and flow could be as follows:

1. Start: The process begins when the Member requests to borrow a book.

2. Check Availability: The system checks if the book is available.

3. Decision Point: If the book is available, the flow continues; if not, the process ends with an error message.

4. Update Book Status: If the book is available, the system updates the book status.

5. Register Transaction: The system records the transaction.

6. End: The process ends when the transaction is successfully completed.

Diagram Example:

css

CopyEdit

[Start]

[Check Availability]--->[Available?]

| |

|--No-->[End] |--Yes-->[Update Book Status]

| |

| [Register Transaction]

| |

| [End]

Exercise: Draw a Use Case Diagram for the Library Management System

Now that we've understood the basics of Use Case Diagrams, try drawing a Use Case Diagram for the Library Management System using the information provided. Identify all the actors and their use cases in the system, then represent them in the diagram.

Conclusion and Wrap-up

In today's class, we've not only learned about Class Diagrams but also introduced several other key UML diagrams that are essential for designing and modeling software systems. These diagrams include:

Use Case Diagram: Represents the functionalities of the system from the perspective of its users.
Sequence Diagram: Depicts how objects interact in a specific sequence of actions.
Activity Diagram: Shows the flow of activities or tasks in a system.

By mastering these UML diagrams, students will be able to communicate effectively during the software design process, document the system’s architecture, and understand the behavior of the system from different perspectives.

Next Steps:

In the next class, we will explore State Diagrams, which represent the states of an object and the transitions between those states, and Component Diagrams, which show the physical components of a system and their interactions.

4o mini

You said:

yes...continue

ChatGPT said:

ChatGPT

Class 3: Continuation – State Diagrams and Component Diagrams

In this section, we will delve into State Diagrams and Component Diagrams, two more essential diagrams in UML. These diagrams help model the dynamic behavior of objects and provide insight into the physical structure of a system, respectively. We will explore their components, purposes, and how to create them.

4. State Diagram

A State Diagram (also known as a State Machine Diagram) describes the different states an object can be in during its lifecycle and how it transitions between these states. This type of diagram is particularly useful for modeling systems where objects undergo various state changes in response to events.

Key Components of a State Diagram:

States: Represented by rounded rectangles, each state shows a specific condition or situation in the lifecycle of the object.
Transitions: Arrows between states that show how the system moves from one state to another. Each transition is triggered by an event or action.
Events: Actions or occurrences that cause a state transition. For example, an event like "book borrowed" can trigger the transition from a "available" state to a "borrowed" state.
Initial State: Represented by a filled black circle, indicating where the system starts.
Final State: Represented by a filled black circle with a border, indicating the end of the lifecycle or process.

Example: State Diagram for a Book in the Library System

Consider a book in the Library Management System that can have several states during its lifecycle. These states could include:

1. Available: The book is available for borrowing.

2. Borrowed: The book has been checked out by a member.

3. Reserved: The book is reserved by a member but not yet checked out.

4. Returned: The book has been returned by the member.

5. Damaged: The book is in a damaged condition and cannot be borrowed.

Step-by-Step Transitions:

The book starts in the Available state.
When a member borrows the book, the state changes to Borrowed.
If the book is reserved but not yet checked out, it moves to the Reserved state.
Once the book is returned, it transitions back to the Available state.
If the book is damaged, it transitions to the Damaged state.

Diagram Example:

scss

CopyEdit

[Start] ---> [Available] ---> (borrowed) ---> [Borrowed]

| | |

|--- (reserved) ---------> [Reserved] |

| | |

|--- (returned) -----------> [Available] |

| | |

|--- (damaged) ---------> [Damaged] -------------------|

(returned) ---> [Available]

5. Component Diagram

A Component Diagram is a structural diagram in UML that describes the physical components or modules of a system. It shows how different components of the system interact with each other. These components can be software modules, subsystems, or even hardware elements.

Key Components of a Component Diagram:

Components: Represented by rectangles with a small rectangle at the top (like a "box-within-a-box"). Components represent logical or physical entities of the system, such as databases, user interfaces, or business logic modules.
Interfaces: Represented by a small circle or a lollipop symbol. These indicate the services provided by a component to other components or systems.
Dependencies: Represented by dashed arrows. A component depends on another component if it needs the other component's services.
Ports: Represented as small rectangles on the side of a component. Ports are the communication points through which components interact.

Example: Component Diagram for the Library Management System

In a Library Management System, the components could be:

User Interface (UI): The component where users interact with the system, such as browsing books or managing their account.
Database: Stores book details, member information, transaction history, and so on.
Book Management: A component responsible for managing book information (e.g., adding, updating, deleting books).
Transaction Management: A component handling the borrowing and returning of books, and maintaining transaction history.

These components interact with each other in the following way:

The UI component communicates with the Transaction Management component to handle borrowing and returning books.
The Book Management component interacts with the Database component to retrieve or update book information.
The Transaction Management component also communicates with the Database to store transaction records.

Diagram Example:

css

CopyEdit

[User Interface] --------------------> [Transaction Management] --------------------> [Database]

| | |

v v v

[Book Management] -------------------------> [Database] -------------------------> [Transaction History]

Exercise: Draw a State Diagram for a Library Book

Now, for the Library Management System, you are tasked with drawing a State Diagram for the Book object. Follow the steps provided in the State Diagram section above, and identify the various states that a book can be in throughout its lifecycle.

6. Summary of UML Diagrams

Let’s briefly summarize all the UML diagrams that we have covered in today's class. These diagrams collectively provide a comprehensive model of both the structure and behavior of a system:

1. Class Diagram: Represents the static structure of the system, including classes, attributes, methods, and relationships.

2. Use Case Diagram: Describes the interactions between external actors (users or systems) and the system’s functionalities.

3. Sequence Diagram: Shows the interaction between objects over time for a specific process or use case.

4. Activity Diagram: Models the flow of activities or tasks within a system or process.

5. State Diagram: Represents the various states of an object and the transitions between those states.

6. Component Diagram: Shows the physical or logical components of the system and how they interact with each other.

Next Steps:

In the next class, we will explore Deployment Diagrams to visualize the physical deployment of software components across hardware nodes. This will help you understand how software systems are implemented in the real world, making sure all components are properly configured and linked.

We will also continue to work on exercises and case studies to strengthen our UML diagramming skills and apply them in real-world software design scenarios.

Conclusion

With today's class, you should now have a solid foundation in creating and understanding the key UML diagrams. UML is an essential tool in the software engineering process, helping you design, visualize, and document a system's architecture, behavior, and interactions.

4o mini

You said:

continue

ChatGPT said:

ChatGPT

7. Assignment: Creating UML Diagrams for a Library Management System

In order to practice the concepts learned in this class, I would like you to create a set of UML diagrams for a Library Management System. This assignment will help you understand how different UML diagrams work together to represent the structure and behavior of a system.

Instructions:

1. Use Case Diagram:

o Identify the actors involved in the Library Management System (e.g., User, Admin, Library Staff).

o Identify the key functionalities that each actor interacts with (e.g., Borrow Books, Return Books, Reserve Books, Manage User Accounts).

o Draw the use case diagram that depicts the interactions between the actors and the system.

2. Class Diagram:

o Identify the main classes in the system (e.g., Book, User, Transaction, Reservation).

o Determine the attributes and methods for each class.

o Identify relationships between classes (e.g., inheritance, association, aggregation).

o Create a class diagram that shows how these classes are structured.

3. Sequence Diagram:

o Choose a process or use case to model (e.g., Borrowing a Book).

o Identify the objects involved in the sequence (e.g., User, Library System, Book).

o Show the interactions between these objects in a time-sequenced manner (i.e., how each object calls methods on the other objects).

o Draw the sequence diagram to visualize the interaction flow.

4. State Diagram:

o Create a state diagram for a Book object in the system.

o Identify the different states of the book (e.g., Available, Borrowed, Reserved, Damaged).

o Show how the book transitions between these states based on events (e.g., borrowed, returned, reserved).

5. Component Diagram:

o Identify the components of the system (e.g., UI Component, Database, Transaction Manager).

o Show how these components interact with each other and the interfaces they expose.

o Create a component diagram that visualizes the high-level structure of the system.

Deliverables:

A PDF or Word document containing all the diagrams mentioned above.
A brief explanation of each diagram (1-2 paragraphs), including the rationale behind the design choices and how each diagram contributes to the overall system design.

8. Tools for UML Diagramming

You can use any of the following tools to create your UML diagrams:

Lucidchart: A popular web-based diagramming tool that supports UML diagrams.
Draw.io: A free and open-source diagramming tool available online that supports UML.
StarUML: A downloadable UML modeling tool that allows you to create detailed UML diagrams.
UMLet: A simple, open-source UML tool that allows quick creation of UML diagrams.
Microsoft Visio: A diagramming tool available in many professional settings, with UML diagram templates.

Choose the tool you are most comfortable with and that suits your needs for the assignment.

9. Review of Key Concepts in UML

To wrap up this lesson, let’s revisit the key concepts we've covered today:

UML helps us visualize, design, and document a system's architecture, structure, and behavior.
The Use Case Diagram helps us identify the system’s functionality and interactions with external entities.
The Class Diagram represents the system's structure by detailing classes, their attributes, methods, and relationships.
Sequence Diagrams show the flow of messages between objects in the system over time.
State Diagrams model how an object changes its state based on different events.
Component Diagrams show the physical components of a system and their dependencies.

These diagrams are essential for a software designer, providing a comprehensive way to model both static and dynamic aspects of a system. As you progress through your studies, you will become more comfortable with these diagrams, and eventually, you’ll be able to create complex models for real-world applications.

10. Practice Exercise: Building Your Own UML Diagram for a New System

To further solidify your understanding of UML, you can try creating UML diagrams for a system of your choice. For example:

Online Banking System: Design use cases such as Transfer Money, Check Balance, Update Account Info, etc.
Inventory Management System: Create a class diagram for Product, Supplier, Inventory, and their relationships.
E-commerce System: Draw a sequence diagram for the process of Placing an Order.

By practicing these exercises, you will gain hands-on experience and be well-prepared to tackle any UML-related tasks in your software engineering projects.

11. Next Class Preview:

In the next class, we will continue our journey into UML by discussing more advanced diagrams, such as Deployment Diagrams and Interaction Diagrams. These diagrams focus on the deployment of software components across a network or hardware infrastructure and how objects interact with one another in complex systems.

We will also start looking at how to incorporate UML into Agile Development processes, where UML diagrams are used to aid rapid prototyping and iteration.

Conclusion

This class has introduced you to the fundamentals of UML, a crucial skill for software developers and designers. By learning how to create various UML diagrams, you will be able to model and visualize your software systems more effectively, improving both your design and communication with stakeholders. Continue practicing the concepts and diagrams introduced today to become more proficient in UML.

Recommended Reading:

"UML Distilled: A Brief Guide to the Standard Object Modeling Language" by Martin Fowler.
"The Unified Modeling Language User Guide" by Grady Booch, James Rumbaugh, and Ivar Jacobson.

End of Class 3.

4o mini

You said:

yes

ChatGPT said:

ChatGPT

Great! It seems like you're all set with the lecture notes. If you have any questions about UML or if you'd like further elaboration on any part of the lesson, feel free to ask. Good luck with your teaching and your students' understanding of UML! 😊

4o mini

You said:

coninue...In the next class, we will continue our journey into UML by discussing more advanced diagrams, such as Deployment Diagrams and Interaction Diagrams. These diagrams focus on the deployment of software components across a network or hardware infrastructure and how objects interact with one another in complex systems.

ChatGPT said:

ChatGPT

Class 4: Advanced UML Diagrams – Deployment Diagrams and Interaction Diagrams

Objective:

In this class, we will dive into more advanced UML diagrams: Deployment Diagrams and Interaction Diagrams. These diagrams are essential for understanding the physical deployment of software systems and the interaction between objects in complex systems. By the end of this class, students will be able to visualize how software components are distributed across hardware and how they interact in real-time.

Topics to Cover:

1. Deployment Diagrams

2. Interaction Diagrams (Sequence Diagrams and Communication Diagrams)

1. Deployment Diagrams

A Deployment Diagram shows the physical deployment of artifacts (software components, databases, etc.) on hardware nodes (servers, computers, devices, etc.). This type of diagram is helpful in understanding how different components of a system are mapped to physical resources in a network.

Key Elements of a Deployment Diagram:

Nodes: Represent physical hardware or devices. For example, a Server or a Client Machine.
Artifacts: Represent software components, such as databases, applications, or libraries, that are deployed on the nodes.
Communication Associations: Represent the relationships or communication paths between nodes. These are typically shown as lines connecting the nodes, indicating how data or requests travel between them.
Deployment Specification: Defines how artifacts are deployed to nodes.

Example of a Deployment Diagram:

Let’s consider an Online Banking System:

Client Node: The user’s machine (which runs the browser).
Server Node: A web server hosting the application.
Database Node: A database server storing user accounts, transactions, etc.

In this case, the deployment diagram would show:

The Client Node communicating with the Web Server Node.
The Web Server Node communicating with the Database Server Node to retrieve or store data.

Purpose of Deployment Diagrams:

Visualize system architecture: Helps understand where different components of the system reside.
Optimize performance: Helps identify potential bottlenecks or issues related to hardware resources.
Hardware configuration: Shows how the software is mapped to the physical infrastructure.

Deployment Diagram Example:

A Web Application deployed across a Client Machine and Web Server.
The Web Server is connected to a Database Server.

2. Interaction Diagrams

Interaction Diagrams focus on how objects communicate with each other within a system. These diagrams help illustrate the sequence of messages or events that occur between different objects during the execution of a process or operation.

There are two primary types of interaction diagrams:

A. Sequence Diagrams

A Sequence Diagram shows how objects interact with each other in a time-ordered sequence. It’s helpful for modeling the flow of messages between objects during a particular operation or process.

Key Elements of a Sequence Diagram:

Objects: Represented by rectangles at the top of the diagram.
Lifelines: Represented by dashed vertical lines, they show the existence of an object over time.
Messages: Represented by arrows between objects, indicating the communication between them.
Activation Bars: Rectangles along the lifelines showing when an object is performing an action.

Example of a Sequence Diagram:

In an Online Shopping System, you might model the Checkout Process:

1. Customer sends a message to the Shopping Cart to process the checkout.

2. Shopping Cart sends a message to the Payment Gateway for processing payment.

3. Payment Gateway responds with a success or failure message.

4. If successful, Shopping Cart confirms the order with the Inventory System.

This sequence diagram would show the interactions between the Customer, Shopping Cart, Payment Gateway, and Inventory System.

B. Communication Diagrams

A Communication Diagram is similar to a Sequence Diagram, but it focuses on the relationships between objects and how they send messages to each other. These diagrams emphasize the links between objects rather than the timeline of messages.

Key Elements of a Communication Diagram:

Objects: Represented as nodes in the diagram.
Messages: Represented as labeled arrows, showing the communication between objects.
Sequence Numbers: Indicating the order in which messages are sent.

Example of a Communication Diagram:

In the same Online Shopping System:

The Customer interacts with the Shopping Cart (as in the Sequence Diagram) but here, the focus will be on the objects involved and their relationships.
Shopping Cart, Payment Gateway, and Inventory System are linked by communication paths, showing how each component interacts to complete the process.

3. Practice Exercise: Create Advanced UML Diagrams for a Library Management System

Instructions:

Now that you’ve learned about Deployment Diagrams and Interaction Diagrams, let’s continue with the Library Management System example.

Deployment Diagram:

Imagine a scenario where the Library Management System is deployed on a Web Application that connects to a Database Server to store information about books, users, and transactions.
Draw a deployment diagram that shows the nodes involved in this system, including the Client (user interface), the Web Server (handling application logic), and the Database Server (storing data).

Sequence Diagram:

Model the process of Borrowing a Book:

1. The User selects a book.

2. The System checks the availability of the book.

3. The System records the transaction.

4. The User is notified of the successful transaction.

Create a sequence diagram showing the interactions between the User, Library System, and Book.

Communication Diagram:

Model the same Borrowing a Book process, but this time, focus on the objects and their relationships rather than the timeline.
Show how the User, Library System, and Book objects are related and how messages are passed between them.

4. Summary

In this class, we explored more advanced UML diagrams:

Deployment Diagrams: Show how software components are deployed across hardware infrastructure.
Interaction Diagrams: Focus on how objects communicate with each other, represented by Sequence Diagrams and Communication Diagrams.

These diagrams help visualize and structure the flow of data and interaction in a system, which is vital for understanding complex software systems.

5. Recommended Reading:

"UML 2 and the Unified Process: Practical Object-Oriented Analysis and Design" by Jim Arlow and Ila Neustadt.
"Learning UML 2.0" by Russ Miles and Kim Hamilton.

Next Class Preview:

In the next class, we will explore State Machine Diagrams and Activity Diagrams, both of which provide a more detailed view of how objects or components behave over time and how workflows are structured within a system.

End of Class 4.

4o mini

You said:

WRITE 10 ASSIGNMENTS FROM ABOVE CONCEPT(Class 3) WITH STEP BY STEP SOLUTIONS with proper explanation in details

ChatGPT said:

ChatGPT

Sure! Below are 10 assignments based on Class 3: Introduction to UML, with step-by-step solutions and detailed explanations.

Assignment 1: Create a Use Case Diagram for a Library Management System

Objective: Draw a use case diagram for a Library Management System.

Solution:

1. Identify Actors:

o User: Borrow books, return books, search books.

o Librarian: Manage books, issue books, check the status of books.

2. Identify Use Cases:

o For User: Borrow Books, Return Books, Search Books.

o For Librarian: Add Books, Remove Books, Issue Books, Check Availability.

3. Draw the Use Case Diagram:

o Use oval shapes for Use Cases and stick figures for Actors.

o Connect the actors to their respective use cases using lines.

Example:

sql

CopyEdit

[Use Case Diagram]

- User (actor) -> Borrow Books, Return Books, Search Books

- Librarian (actor) -> Add Books, Remove Books, Issue Books, Check Availability

Explanation:

Use case diagrams are designed to show how the system interacts with external users or systems. The actors represent users or external systems, and the use cases represent the functionality of the system.

Assignment 2: Create a Class Diagram for the Library Management System

Objective: Draw a class diagram for the Library Management System.

Solution:

1. Identify Classes:

o Book: Attributes (ID, Title, Author, ISBN, etc.), Methods (borrow(), return()).

o User: Attributes (ID, Name, Address, etc.), Methods (searchBooks(), borrowBook(), returnBook()).

o Librarian: Attributes (ID, Name, Role), Methods (addBook(), removeBook(), issueBook()).

2. Define Relationships:

o User and Book have an association (a user borrows a book).

o Librarian and Book have an association (librarian adds or removes books).

3. Draw the Class Diagram:

o Draw each class as a rectangle.

o List attributes and methods inside each class box.

o Connect classes using lines to represent relationships (e.g., associations).

Example:

scss

CopyEdit

[Class Diagram]

- Class User {ID, Name, Address | searchBooks(), borrowBook(), returnBook()}

- Class Book {ID, Title, Author | borrow(), return()}

- Class Librarian {ID, Name, Role | addBook(), removeBook(), issueBook()}

- Associations: User -> Book (borrow), Librarian -> Book (manage)

Explanation:

A class diagram represents the static structure of the system, showing classes, their attributes, methods, and relationships between classes.

Assignment 3: Create a Sequence Diagram for Borrowing a Book

Objective: Draw a sequence diagram for borrowing a book in a Library Management System.

Solution:

1. Identify the objects involved:

o User, Library System, Book.

2. Determine the flow of messages:

o User requests the Library System to borrow a book.

o Library System checks availability from Book.

o Library System confirms the book is available and updates status.

3. Draw the Sequence Diagram:

o Draw vertical lifelines for User, Library System, and Book.

o Use horizontal arrows to represent messages exchanged between the objects.

Example:

sql

CopyEdit

[Sequence Diagram]

- User -> Library System: borrowBook()

- Library System -> Book: checkAvailability()

- Book -> Library System: available()

- Library System -> User: confirmAvailability()

Explanation:

Sequence diagrams show how objects interact in a particular scenario over time, emphasizing the order of messages.

Assignment 4: Create a Deployment Diagram for the Library Management System

Objective: Draw a deployment diagram for a Library Management System.

Solution:

1. Identify the nodes (hardware components):

o User Device: Client computer or mobile.

o Web Server: Hosts the application.

o Database Server: Stores information about books, users, etc.

2. Identify the artifacts (software components):

o Library Application (hosted on the Web Server).

o Database (hosted on the Database Server).

3. Draw the Deployment Diagram:

o Represent nodes as 3D boxes.

o Show relationships (communication) between nodes.

Example:

scss

CopyEdit

[Deployment Diagram]

- User Device -> Web Server (Library Application)

- Web Server -> Database Server (Library Database)

Explanation:

Deployment diagrams show how software components (artifacts) are distributed across hardware nodes.

Assignment 5: Create a Communication Diagram for Borrowing a Book

Objective: Draw a communication diagram for borrowing a book in the Library Management System.

Solution:

1. Identify objects involved:

o User, Library System, Book.

2. Draw the objects and their relationships:

o Show User, Library System, and Book as nodes.

o Draw lines to represent communication between these objects.

3. Define the message flow:

o User sends a message to Library System: borrowBook().

o Library System asks Book: checkAvailability().

o Book responds: available().

o Library System sends confirmation to User.

Explanation:

Communication diagrams show the interactions between objects and how they are linked, emphasizing the flow of messages.

Assignment 6: Create a State Machine Diagram for Book Status

Objective: Draw a state machine diagram for the status of a book in the Library Management System.

Solution:

1. Identify the states:

o Available, Borrowed, Reserved, Returned.

2. Define state transitions:

o Available -> Borrowed (when a user borrows the book).

o Borrowed -> Returned (when the book is returned).

o Available -> Reserved (when a user reserves the book).

3. Draw the State Machine Diagram:

o Represent states as circles and transitions as arrows between them.

Explanation:

State machine diagrams show how an object (in this case, a book) moves between different states during its lifecycle.

Assignment 7: Create a Use Case Diagram for an Online Shopping System

Objective: Draw a use case diagram for an Online Shopping System.

Solution:

1. Identify Actors:

o Customer, Admin.

2. Identify Use Cases:

o Customer: Browse Products, Add to Cart, Checkout, Make Payment.

o Admin: Add Products, Remove Products, View Orders.

3. Draw the Use Case Diagram:

o Draw actors and use cases.

o Connect actors to the appropriate use cases.

Explanation:

Use case diagrams are used to capture the functional requirements of a system from an external user perspective.

Assignment 8: Create a Class Diagram for an Online Shopping System

Objective: Draw a class diagram for the Online Shopping System.

Solution:

1. Identify Classes:

o Product: Attributes (ID, Name, Price), Methods (addProduct(), removeProduct()).

o Customer: Attributes (ID, Name, Address), Methods (addToCart(), checkout()).

o Order: Attributes (OrderID, ProductList, OrderStatus), Methods (processOrder(), cancelOrder()).

2. Define Relationships:

o Customer and Product: Association (customer adds products to the cart).

o Order and Product: Association (order contains products).

3. Draw the Class Diagram:

o Show the classes, their attributes, methods, and relationships.

Explanation:

Class diagrams capture the static structure of a system, focusing on the classes and their relationships.

Assignment 9: Create a Sequence Diagram for the Checkout Process

Objective: Draw a sequence diagram for the checkout process in an online shopping system.

Solution:

1. Identify objects:

o Customer, Shopping Cart, Payment System, Order System.

2. Determine the flow of messages:

o Customer initiates checkout with Shopping Cart.

o Shopping Cart requests payment from Payment System.

o Payment System processes the payment and returns the result.

o Shopping Cart confirms the order with Order System.

3. Draw the Sequence Diagram:

o Use vertical lifelines and horizontal arrows for the message flow.

Explanation:

Sequence diagrams help visualize the flow of messages between different objects over time.

Assignment 10: Create a Deployment Diagram for an Online Shopping System

Objective: Draw a deployment diagram for an Online Shopping System.

Solution:

1. Identify the nodes:

o User Device: Client-side interface.

o Web Server: Hosts the shopping application.

o Database Server: Stores product data, user data, and orders.

2. Define artifacts:

o Shopping Application (on the Web Server).

o Product Database (on the Database Server).

3. Draw the Deployment Diagram:

o Represent the nodes as 3D boxes.

o Show the communication between the nodes.

Explanation:

Deployment diagrams show how software components are deployed across hardware resources, which is critical for understanding system architecture.

These assignments will help students understand key UML concepts by giving them practical exercises to create various diagrams and understand the underlying system components and interactions.

4o mini

You said:

WRITE 50 no of MCQs only FROM ABOVE CONCEPT with explanation

ChatGPT said:

ChatGPT

Here are 50 Multiple-Choice Questions (MCQs) based on the UML (Unified Modeling Language) concepts covered in Class 3: Introduction to UML. These questions test the understanding of various UML diagrams like use case, class, sequence, deployment, and state machine diagrams.

MCQs on UML Concepts

1. What is the purpose of a Use Case Diagram?

a) To show the internal working of the system
b) To describe the system’s functionality from the user’s perspective
c) To define the class structure of the system
d) To represent the deployment of software components

Answer: b) To describe the system’s functionality from the user’s perspective
Explanation: Use case diagrams help visualize the functional requirements of a system from an external user's perspective, identifying actors and use cases.

2. Which diagram is used to represent the interaction between objects over time?

a) Class Diagram
b) Sequence Diagram
c) State Machine Diagram
d) Use Case Diagram

Answer: b) Sequence Diagram
Explanation: Sequence diagrams show the sequence of messages exchanged between objects over time to accomplish a specific function.

3. Which diagram would you use to visualize the structure of a system in terms of its classes and relationships?

a) Class Diagram
b) Use Case Diagram
c) Sequence Diagram
d) Activity Diagram

Answer: a) Class Diagram
Explanation: Class diagrams define the static structure of a system, showing the classes, their attributes, methods, and relationships.

4. What symbol represents a class in a class diagram?

a) A rounded rectangle
b) A square box
c) A rectangle with three compartments
d) A circle

Answer: c) A rectangle with three compartments
Explanation: A class in a class diagram is represented by a rectangle divided into three parts: the class name, attributes, and methods.

5. What does the relationship between a class and another class represented by a line with a diamond symbol indicate?

a) Inheritance
b) Association
c) Aggregation
d) Dependency

Answer: c) Aggregation
Explanation: Aggregation is a special type of association indicating that one class is a part of another class but can exist independently.

6. In a sequence diagram, what does a vertical dashed line represent?

a) Message flow
b) Object lifeline
c) Activation bar
d) Object creation

Answer: b) Object lifeline
Explanation: In a sequence diagram, the vertical dashed line represents the lifeline of an object, indicating that the object exists during that period.

7. Which of the following represents the dynamic behavior of a system?

a) Use Case Diagram
b) Sequence Diagram
c) Class Diagram
d) Deployment Diagram

Answer: b) Sequence Diagram
Explanation: Sequence diagrams represent the dynamic behavior by showing the interaction of objects over time.

8. What does a solid line with an arrowhead indicate in a class diagram?

a) Association
b) Inheritance
c) Dependency
d) Aggregation

Answer: b) Inheritance
Explanation: A solid line with an arrowhead in a class diagram indicates inheritance, where one class (subclass) inherits properties from another class (superclass).

9. Which UML diagram is used to model the deployment of a system on hardware?

a) Class Diagram
b) Deployment Diagram
c) Sequence Diagram
d) Activity Diagram

Answer: b) Deployment Diagram
Explanation: Deployment diagrams are used to show how the software artifacts are deployed across the hardware nodes in a system.

10. In a Use Case Diagram, which of the following represents a user or system interacting with the system?

a) Use Case
b) Actor
c) Association
d) System Boundary

Answer: b) Actor
Explanation: In use case diagrams, an actor represents a user or external system interacting with the system to achieve a goal.

11. Which of the following diagrams shows the state transitions of an object?

a) Class Diagram
b) Sequence Diagram
c) State Machine Diagram
d) Component Diagram

Answer: c) State Machine Diagram
Explanation: State machine diagrams model the states an object can be in and the transitions between these states.

12. In a sequence diagram, what does an activation bar represent?

a) Object creation
b) Message passing
c) Time spent by an object in a particular action
d) Object destruction

Answer: c) Time spent by an object in a particular action
Explanation: An activation bar in a sequence diagram indicates the period an object is active during message passing.

13. Which of the following represents an object’s life span in a sequence diagram?

a) Horizontal arrow
b) Vertical dashed line
c) Rectangle
d) Solid line with an arrowhead

Answer: b) Vertical dashed line
Explanation: The vertical dashed line in a sequence diagram represents the lifeline of an object, showing when it exists during the interaction.

14. What type of UML diagram would you use to model the flow of activities in a system?

a) Class Diagram
b) Use Case Diagram
c) Activity Diagram
d) Sequence Diagram

Answer: c) Activity Diagram
Explanation: Activity diagrams represent the workflow of activities, showing the sequence of actions and decisions.

15. Which symbol represents an actor in a Use Case Diagram?

a) Oval
b) Rectangle
c) Stick figure
d) Circle

Answer: c) Stick figure
Explanation: An actor in a use case diagram is represented by a stick figure, which signifies the user or external system interacting with the system.

16. In a class diagram, what does an association between two classes typically represent?

a) A relationship between two classes
b) A parent-child relationship
c) A dependency
d) A class hierarchy

Answer: a) A relationship between two classes
Explanation: An association in a class diagram represents a relationship between two classes, often shown as a solid line connecting the classes.

17. What does a solid diamond shape on a line in a class diagram indicate?

a) Inheritance
b) Aggregation
c) Dependency
d) Association

Answer: b) Aggregation
Explanation: A solid diamond represents aggregation, a type of association where one class is a whole and the other is a part.

18. Which diagram would be used to model the interaction of objects over time during a specific scenario?

a) Sequence Diagram
b) Communication Diagram
c) State Diagram
d) Use Case Diagram

Answer: a) Sequence Diagram
Explanation: Sequence diagrams focus on the interaction of objects over time for a particular scenario or use case.

19. What type of diagram would you use to model an online e-commerce checkout process?

a) Activity Diagram
b) Sequence Diagram
c) Class Diagram
d) Use Case Diagram

Answer: b) Sequence Diagram
Explanation: A sequence diagram would be used to model the checkout process, showing how messages are passed between objects over time.

20. Which of the following describes the relationship between an object and a service or function in UML?

a) Dependency
b) Association
c) Aggregation
d) Inheritance

Answer: a) Dependency
Explanation: A dependency represents a situation where one class depends on another to function, but the relationship is not as strong as an association.

21. What is a key characteristic of an Interaction Diagram?

a) It represents the state changes of an object.
b) It shows the order of messages between objects.
c) It shows the internal structure of an object.
d) It describes the deployment of a system.

Answer: b) It shows the order of messages between objects.
Explanation: Interaction diagrams (like sequence or communication diagrams) focus on how objects interact by showing the order of messages between them.

22. Which of the following is NOT a type of UML diagram?

a) Sequence Diagram
b) Data Flow Diagram
c) Class Diagram
d) Deployment Diagram

Answer: b) Data Flow Diagram
Explanation: Data Flow Diagrams (DFD) are not part of UML. UML has a different set of diagrams, such as sequence, class, and deployment diagrams.

23. What is the primary purpose of a State Machine Diagram?

a) To model interactions between objects
b) To show the states an object can be in and the transitions between them
c) To model the architecture of the system
d) To describe the flow of control in a system

Answer: b) To show the states an object can be in and the transitions between them
Explanation: A state machine diagram models how an object transitions between different states based on events or conditions.

24. In a Sequence Diagram, what does a solid arrow represent?

a) A synchronous message
b) An asynchronous message
c) An object creation
d) An object destruction

Answer: a) A synchronous message
Explanation: A solid arrow in a sequence diagram typically represents a synchronous message where the sender waits for a response before proceeding.

25. What does a dashed line with an arrowhead represent in a Sequence Diagram?

a) A return message
b) An activation message
c) An object destruction
d) An object creation

Answer: a) A return message
Explanation: A dashed line with an arrowhead in a sequence diagram indicates a return message, which is the response to a previously sent message.

26. In UML, which diagram is used to show the physical components of a system?

a) Class Diagram
b) Deployment Diagram
c) Sequence Diagram
d) Activity Diagram

Answer: b) Deployment Diagram
Explanation: Deployment diagrams show how software artifacts are distributed across hardware components in a system.

27. What is an actor in a Use Case Diagram?

a) A process or service within the system
b) A user or external system interacting with the system
c) A class within the system
d) A state transition in the system

Answer: b) A user or external system interacting with the system
Explanation: An actor is a role played by an external user or system that interacts with the system.

28. What is the main function of a Communication Diagram?

a) To model object interactions based on their sequence
b) To show the interaction between objects in terms of message passing
c) To represent the internal structure of a class
d) To depict the system architecture

Answer: b) To show the interaction between objects in terms of message passing
Explanation: Communication diagrams focus on showing how objects interact with each other by passing messages.

29. Which of the following UML diagrams focuses on time sequence of interactions between objects?

a) Use Case Diagram
b) Sequence Diagram
c) State Diagram
d) Class Diagram

Answer: b) Sequence Diagram
Explanation: Sequence diagrams show the time sequence in which interactions between objects occur.

30. In a UML Deployment Diagram, what does a node represent?

a) A class
b) A system component or hardware resource
c) A user interacting with the system
d) A method in a class

Answer: b) A system component or hardware resource
Explanation: Nodes in a deployment diagram represent physical hardware or software components that execute system processes.

31. Which of the following is true about a Use Case Diagram?

a) It shows the internal details of how a system functions
b) It models interactions between classes
c) It illustrates the behavior of a system from a user’s perspective
d) It models system components and their relationships

Answer: c) It illustrates the behavior of a system from a user’s perspective
Explanation: Use case diagrams show the functionality of a system from the perspective of the users or external systems interacting with it.

32. What does a dashed line with an arrow in a State Machine Diagram indicate?

a) State transition
b) Object destruction
c) Message flow
d) Object creation

Answer: a) State transition
Explanation: In state machine diagrams, a dashed line with an arrow represents the transition between two states in response to an event or condition.

33. Which UML diagram focuses on modeling how data moves and changes through the system?

a) Sequence Diagram
b) Activity Diagram
c) Deployment Diagram
d) State Machine Diagram

Answer: b) Activity Diagram
Explanation: Activity diagrams model the flow of data and control within the system, showing the sequence of actions.

34. In a Class Diagram, what does a dashed line with a triangular arrowhead represent?

a) Dependency relationship
b) Aggregation relationship
c) Inheritance relationship
d) Association relationship

Answer: a) Dependency relationship
Explanation: A dashed line with a triangular arrowhead represents a dependency between two classes in a class diagram.

35. What is an example of a UML Behavioral Diagram?

a) Class Diagram
b) Sequence Diagram
c) Deployment Diagram
d) Component Diagram

Answer: b) Sequence Diagram
Explanation: Behavioral diagrams like sequence diagrams focus on modeling the behavior of the system or interactions between objects over time.

36. What type of UML diagram would be used to model a login process for a web application?

a) Use Case Diagram
b) Class Diagram
c) State Machine Diagram
d) Sequence Diagram

Answer: a) Use Case Diagram
Explanation: A use case diagram would represent the login process, showing the user interacting with the system to achieve the goal.

37. What does an actor in a Use Case Diagram typically represent?

a) A class or object in the system
b) A process within the system
c) A user or external system interacting with the system
d) A method or function within the system

Answer: c) A user or external system interacting with the system
Explanation: An actor represents a user or external system that interacts with the system to achieve a goal.

38. Which UML diagram would be used to model a system’s high-level architecture?

a) Class Diagram
b) Deployment Diagram
c) Sequence Diagram
d) State Machine Diagram

Answer: b) Deployment Diagram
Explanation: A deployment diagram shows the high-level architecture by representing hardware and software components and their interactions.

39. Which of the following symbols represents a transition in a state machine diagram?

a) A solid arrow
b) A dashed arrow
c) A rectangle
d) A circle

Answer: a) A solid arrow
Explanation: A solid arrow represents a transition between states in a state machine diagram, indicating the flow from one state to another.

40. Which diagram helps model the operational behavior of a system based on time and events?

a) Use Case Diagram
b) Activity Diagram
c) Sequence Diagram
d) State Machine Diagram

Answer: d) State Machine Diagram
Explanation: A state machine diagram models how an object behaves over time in response to different events, showing the states and transitions.

41. In a Sequence Diagram, what does the horizontal dashed line between two objects represent?

a) Activation
b) Return message
c) Object destruction
d) Object creation

Answer: b) Return message
Explanation: A horizontal dashed line represents the return message in a sequence diagram, indicating the response to a previous message.

42. What type of diagram would you use to model the object lifecycle in a system?

a) Activity Diagram
b) State Machine Diagram
c) Class Diagram
d) Sequence Diagram

Answer: b) State Machine Diagram
Explanation: A state machine diagram is used to model the different states of an object and how it changes over time in response to events.

43. Which diagram represents the flow of control between components of a system?

a) Sequence Diagram
b) Activity Diagram
c) Component Diagram
d) Deployment Diagram

Answer: b) Activity Diagram
Explanation: Activity diagrams show the flow of control and actions in the system, representing how activities are executed sequentially or in parallel.

44. What does a class diagram mainly show?

a) Interactions between objects
b) The structure and relationships of classes
c) The deployment of the system on hardware
d) The sequence of messages exchanged between objects

Answer: b) The structure and relationships of classes
Explanation: Class diagrams focus on representing the static structure of a system, with a focus on classes, attributes, methods, and relationships.

45. In a UML diagram, what is the role of a "trigger"?

a) To model the input of a system
b) To start a transition in a state machine diagram
c) To represent an event in a sequence diagram
d) To model the return message between objects

Answer: b) To start a transition in a state machine diagram
Explanation: A "trigger" represents the event that initiates a transition in a state machine diagram.

46. Which diagram would be best to model a login sequence in a web application?

a) Sequence Diagram
b) State Machine Diagram
c) Class Diagram
d) Activity Diagram

Answer: a) Sequence Diagram
Explanation: A sequence diagram would model the sequence of messages and interactions between the user and system during the login process.

47. What does a "solid triangle" at the end of an arrow in a class diagram represent?

a) Aggregation
b) Dependency
c) Inheritance
d) Association

Answer: c) Inheritance
Explanation: A solid triangle at the end of an arrow in a class diagram represents inheritance, where one class is derived from another class.

48. Which diagram would be used to model a database schema with relationships between tables?

a) Class Diagram
b) Sequence Diagram
c) Entity-Relationship Diagram
d) Component Diagram

Answer: c) Entity-Relationship Diagram
Explanation: Entity-Relationship diagrams are used to model the structure of a database, showing entities and their relationships.

49. Which of the following is a behavioral UML diagram?

a) Use Case Diagram
b) Class Diagram
c) Sequence Diagram
d) Component Diagram

Answer: c) Sequence Diagram
Explanation: Sequence diagrams are considered behavioral diagrams as they model the interactions between objects over time.

50. Which UML diagram would be used to describe the states an object goes through in a system?

a) Activity Diagram
b) Sequence Diagram
c) State Machine Diagram
d) Component Diagram

Answer: c) State Machine Diagram
Explanation: State machine diagrams describe the states an object can be in, the events that trigger state transitions, and the actions that occur during the transition.

Search This Blog

CodeLab

Lecture Notes Of Class 3: Introduction to UML (Unified Modeling Language)

Comments

Post a Comment

Popular posts from this blog

Lecture Notes Of Class 7: Writing Code Following Coding Standards