Final Lab report 20 marks
Lab No. 1 :
Lab’s Topic :
The most important information mentioned in this lab:
List the heading and most important of the lab;
- Use Case Diagram: The diagram illustrates the interactions between actors (Student,
Registrar) and use cases (Register, Add, Remove).,
- Actors: Student and Registrar.,
- Use Cases: Register, Add, Remove.,
- This diagram helps visualize the functional requirements of the system from the
perspective of different users.,
Student implementation in the lab :
( paste or screenshot for tour work here)
Student explain:
( comments , what is student understand after doing this work)
This lab introduced me to Use Case Diagrams, which are used to identify the functional
requirements of a system. By modeling the interactions between actors (e.g., Student,
Registrar) and use cases (e.g., Register, Add, Remove), I gained insight into how different
stakeholders interact with the system. This exercise emphasized the importance of
identifying user roles and their corresponding actions to ensure comprehensive system
design.
1
Final Lab report 20 marks
Lab No. 2 :
Lab’s Topic :
The most important information mentioned in this lab:
List the heading and most important of the lab;
- Class Diagram: The diagram defines the attributes and methods of the Students class.,
- Attributes: Name, ID, filed (likely a typo, should be file).,
- Methods: Login, Add Material, Delete Material.,
- This class represents the functionality and data structure of a Student in the system.,
Student implementation in the lab :
( paste or screenshot for tour work here)
Student explain:
( comments , what is student understand after doing this work)
Through this lab, I understood how to represent object-oriented concepts using a Class
Diagram. The Students class encapsulates both data (attributes like Name, ID) and
behavior (methods like Login, Add Material, Delete Material). This exercise reinforced my
understanding of object-oriented programming principles, such as encapsulation and
abstraction, which are crucial for designing robust software systems.
2
Final Lab report 20 marks
Lab No. 3 :
Lab’s Topic :
The most important information mentioned in this lab:
List the heading and most important of the lab;
- Entity Relationship Diagram (ERD): The diagram shows the relationship between
Students, Teacher, and Section.,
- Students can be associated with multiple Teachers and Sections.,
- A Teacher can teach multiple Students.,
- A Section can have multiple Students.,
- A Teacher can teach up to two Sections.,
- Each Student belongs to exactly one Section.
Student implementation in the lab :
( paste or screenshot for tour work here)
Student explain:
( comments , what is student understand after doing this work)
In this lab, I learned how to model relationships between entities using an Entity
Relationship Diagram (ERD). The key takeaway was understanding cardinality constraints,
such as "one-to-many" and "many-to-many" relationships. For example, a Student can be
associated with multiple Teachers and Sections, while a Teacher can teach multiple
Students. This helped me grasp how real-world systems can be represented in a database
schema.
3
Final Lab report 20 marks
Lab No. 4 :
Lab’s Topic :
The most important information mentioned in this lab:
List the heading and most important of the lab;
- Inheritance Diagram: The diagram shows a simple inheritance hierarchy for shapes.,
- Shape is the base class.,
- Square and Circle inherit from Shape.,
- This demonstrates the concept of inheritance in object-oriented programming.,
Student implementation in the lab :
( paste or screenshot for tour work here)
Student explain:
( comments , what is student understand after doing this work)
In this lab, I learned about inheritance, a fundamental concept in object-oriented
programming. The Shape class serves as the base class, and Square and Circle inherit from
it. This allows for code reuse and promotes modularity. For example, common properties
or methods related to shapes can be defined in the Shape class, while specific
implementations (e.g., calculating area or perimeter) can be overridden in derived classes
like Square and Circle. This exercise reinforced the benefits of inheritance in organizing
and maintaining complex software systems.
4
Final Lab report 20 marks
Lab No. 5 :
Lab’s Topic :
The most important information mentioned in this lab:
List the heading and most important of the lab;
- Class Diagram: The diagram depicts the structure of an Order Management System, including
classes like Customer, Order, OrderDetail, Item, and Payment.,
- Classes:,
- Customer: Contains attributes like name and address.,
- Order: Contains attributes like date and status, along with methods for calculating subtotal, tax,
and total.,
- OrderDetail: Contains attributes like quality and taxStatus, along with methods for calculating
subtotal, weight, and tax.,
- Item: Contains attributes like shippingWeight and description, along with methods for getting
price, tax, and stock status.,
- Payment: Contains subclasses like Cash, Check, and Credit, each with specific attributes and
methods.,
- This diagram illustrates how different components of an Order Management System are
interconnected and how polymorphism is utilized through inheritance.,
Student implementation in the lab :
( paste or screenshot for tour work here)
Student explain:
( comments , what is student understand after doing this work)
This lab focused on designing a complex system using Class Diagrams. I learned how to model
relationships between classes, such as aggregation (e.g., Order contains OrderDetail) and
inheritance (e.g., Cash, Check, and Credit inherit from Payment). The use of polymorphism through
method overriding (e.g., authorized() in Check and Credit) demonstrated how different payment
methods can share a common interface while providing specialized implementations. This exercise
enhanced my understanding of how to design scalable and maintainable software systems.
