Your task is to use Microsoft Visio to construct three UML diagrams, followed by a short, written reflection. All components must be submitted together in one Word document (.docx). Part 1: Use Case Diagram
Your task is to use Microsoft Visio to construct three UML diagrams, followed by a short, written reflection.
All components must be submitted together in one Word document (.docx).
Part 1: Use Case Diagram
Create a UML use case diagram showing the major interactions between users and the EventHub system.
Your diagram must include:
A system boundary labeled EventHub System Three actors: Student, Event Organizer, Administrator Four to six use cases representing major system functions At least one includes or extends a relationship Correct UML notation for actors, use cases, and associations Part 2: Class Diagram
Create a UML class diagram that represents the key structural components of EventHub.
Your diagram must include:
Four to six classes (e.g., Event, Student, EventOrganizer, Admin, Registration, Notification) Attributes for each class At least one derived attribute (marked with a slash, e.g., /availableSeats) At least two methods across your classes Correct UML relationships with multiplicity At least one example of generalization (inheritance) or aggregation Part 3: Minimal Sequence Diagram
Create a simple UML sequence diagram showing the interaction for:
“Student views event details.”
Use exactly three participants, arranged left to right:
Student EventHub UI Event Your sequence must include the following interactions:
Student to UI: requestEventDetails(eventID) UI to Event: getEventInfo(eventID) Event to UI: eventInfo (dashed return arrow recommended) UI to Student: displayEventDetails (dashed return arrow recommended) Part 4: Reflection on Object-Oriented Concepts
Write a short paragraph (5–7 sentences) addressing the following:
How your diagrams illustrate encapsulation or the concept of hiding internal details. The difference between static structure (class diagram) and dynamic interaction (sequence diagram). How your diagrams demonstrate at least one object-oriented concept, such as inheritance, aggregation, or message passing.
