CS304 Object Oriented Programming is the course where you stop writing simple programs and start designing systems. Assignment 1 for Fall 2026 is built around a film production company that plans to produce a new showbiz film titled The AI and Challenges, and it asks you to draw a complete UML class diagram for the whole production system. The assignment carries 20 marks and the due date is 5 November 2026, so it is worth doing properly rather than rushing a diagram the night before submission.
The solution file linked below walks through the full design step by step. It starts from the scenario, identifies every object, gives each class its attributes and functions, works out the relationships between the classes, and finishes with the complete class diagram. Use it to check your own diagram, to understand why each relationship is drawn the way it is, and to prepare for similar UML questions in quizzes and exams. It is written as a study reference, so read it with understanding rather than treating it as something to submit without reading.
What Does the Solution File Cover?
The file covers the complete UML class diagram for the Showbiz Film Production System. It follows the standard method taught in the course: extract the objects from the problem statement, find the attributes and functions for each object, identify the relationships among the objects, and then construct the final diagram with correct UML notation. Every one of the 11 classes named in the assignment is included, and the diagram applies encapsulation, inheritance, association, aggregation, and composition where each one fits.
Which Classes Are in the Diagram?
The 11 classes are Company, Producer, ScriptWriter, ScreenPlay, Scene, Dialogue, CrewMember, Director, Editor, Role, and Actor. Company is the production company that appoints the producer. Producer manages the overall production, hires the staff, and prepares the shooting schedule. ScriptWriter develops the story and prepares the screenplay. ScreenPlay is the written screenplay, Scene is one scene of it, and Dialogue is a dialogue spoken inside a scene. CrewMember is the common base class for the crew. Director defines the roles and guides the actors, Editor works on the recorded footage to produce the final film, Role is a role required for the film, and Actor performs an assigned role. Producer, Director, and Actor each carry 2 attributes and 2 functions, exactly as the assignment requires.
How Are the Relationships Defined?
Inheritance is used where one class clearly is a kind of another class. Director, Editor, and Actor all inherit from CrewMember, so they reuse crewId, name, and work() instead of repeating them in every class. Composition is used where a part cannot exist without the whole. A screenplay is made of scenes, so ScreenPlay to Scene is composition, and a scene is made of dialogues, so Scene to Dialogue is composition. Both are shown with filled diamonds. Aggregation is used for Company to Producer, shown with a hollow diamond, because the company appoints a producer but a producer can exist independently of this company. Everything else is association: the producer hires the crew members and the scriptwriter, the scriptwriter creates the screenplay, the director defines roles, a role is assigned to an actor, and the director guides the actors during rehearsals and filming.
Why Does Actor Inherit from CrewMember?
This is the point most students get wrong, so the solution explains it in detail. The scenario says the producer hires a scriptwriter and other crew members, including a director, an editor, and actors. That sentence lists actors among the crew members, so Actor is a subclass of CrewMember in this design. ScriptWriter is different: the scenario lists the scriptwriter separately from the crew members, so ScriptWriter is modeled as its own class, hired by the producer, which then creates the screenplay. Getting this distinction right is what turns an average diagram into a correct one.
How Do You Download the Solution File?
You can download the complete solution file from Google Drive using the link below. The file is a Word document because VU accepts assignments only as .doc or .docx files, so the solution is provided in the same format you will submit. It contains the object identification, the attributes and functions tables, the relationships with reasons, the explanation of every OOP concept used, and the final class diagram.
How Should You Use This Solution?
A solution file helps most when you use it to learn, not just to submit. Read the relationship explanations first and compare them with your own diagram. If your diagram differs, work out which version matches the scenario better before you finalize anything. Fill in your own name and student ID on your submission, and save your file with your VU ID, since that is how VU expects assignment files to be named. Also check your answers against the exact assignment file on VULMS, since question wording can vary.
- Download the file and read the full design explanation before you start your own diagram.
- Check each relationship and its type against the scenario description.
- Fill in your own name and student ID on your submission and save the file with your VU ID.
- Rewrite the explanation in your own words where your instructor expects original work.
- Keep the file for revision, because UML diagram questions return in midterm and final term exams.
For more study material, you can download course handouts from the VU handouts page and compact revision notes from the VU short notes page. Past papers are also useful for UML practice, and you can find them on the VU midterm past papers page.
Frequently Asked Questions
Is this the complete solution for CS304 Assignment 1 Fall 2026?
Yes. The file covers the complete UML class diagram for the Showbiz Film Production System, including all 11 classes named in the assignment, their attributes and functions, every relationship with its type and reason, and the final diagram. The assignment carries 20 marks and the due date is 5 November 2026.
Can I submit this solution file as it is?
You should treat it as a study reference. Add your own name and student ID, save the file with your VU ID, check it against your own assignment file on VULMS, and understand every relationship before submitting. Submitting work you do not understand is risky if your instructor asks about it later.
Why does Actor inherit from CrewMember?
Because the scenario lists actors among the crew members hired by the producer, along with the director and the editor. Actor therefore reuses the common crew data, crewId and name, and the work() function from CrewMember. ScriptWriter is modeled separately because the scenario lists the scriptwriter apart from the crew members.
What format does VU accept for this assignment?
VU accepts assignments only as .doc or .docx files for this assignment. Scanned images, PDF files, and zip files are not accepted. That is why the solution file is provided as a Word document, ready for you to adapt with your own details and submit on VULMS.
Last updated: October 2026.
