You must design and implement a Java-based Oman Furniture in accordance with the scenario described below. You are required to implement the entire scenario, taking into consideration the good practices
Task/assessment brief:
You must design and implement a Java-based Oman Furniture in accordance with the scenario described below. You are required to implement the entire scenario, taking into consideration the good practices in system development. Also, the more functionality your system has, the higher the mark you can obtain (see assessment criteria on the relevant pages for details). This assignment is expected to be done individually by all students. You will be given ample guidance and support on the modelling and implementation of the system in your lectures and tutorials.
The Scenario
Design a system for the showroom Oman Furniture. The showroom showcases home-furniture and office- furniture. The home-furniture includes furniture for the living room, dining room, bed room and kitchen. The office furniture includes desks, seats, cabinets and storage. The shop provides furniture made with wood and metal. Each furniture product is identified by a unique 8 digit number. The system should provide frames to add, show, modify and delete the furniture details. The furniture details such as type, made, model, price etc. must be stored in the database.
-There are (2) main user types who will use the system, these are: Employee and admin.
Admin
The Admin is responsible for managing and maintaining the system. Admin functionalities include:
- Managingfurniture records (add, update, delete)
- Generatingand viewing reports:
- Orderreports
- Productdetails reports
Employee
Employees use the system to assist customers and process orders. Their responsibilities include:
- Searchingfor furniture using various filters (e.g., type, category, material)
- Creatingand managing customer orders, including: (add, update)
- Viewingorder details
- Cancellingcustomer orders if required
Deliverable
design documentation for the system with the corresponding explanation of the processes that you have undertaken and the relevant diagrams: o Use Case diagrams with use case description o Class diagrams, showing all the classes and their relationships together with the attributes and methods for each class a soft copy of your complete report and Java files The body of the report should include the following: a soft copy of your complete report and Java files The body of the report should include the following: I. Introduction and Objectives. Write a short description of the program and its objectives. II. Program Design. Discuss your adherence to program design principles, including professional and ethical principles. Also, include in this section the required diagrams (Use Case and Class Diagrams), with brief descriptions. III. Implementation and Testing. Take screenshots of important code snippets from each form and discuss. Test your program, show and then describe the testing process in this section. IV. Conclusion. Reflect on what you learnt from the experience. Focus on the challenges you have faced and how you overcame them. |
Additional instructions: Your student identification number must be clearly stated at the top of each page of the work. Each page must be numbered. Where appropriate, a contents page, a list of tables/figures and a list of abbreviations should precede your work. All referencing must adhere to School/Institutional requirements (Harvard Referencing Style) A word count must be stated at the end of your work. Your programme, year of study and the relevant module must be included as a footer on each page. Appendices should be kept to the minimum and be of direct relevance to the content of your work. All tables and figures must be correctly numbered and labelled. Your coursework report should be submitted by uploading it to Turnitin on the dates indicated for submission. Upload your report draft to MS Teams for formative feedback. REPORT FORMATTING DETAILS 1. Use A4-sized paper. 2. Margins of 1" on all sides of the paper. 3. Apply 1.5 line spacing. 4. Use Calibri font for the entire document. - size 12, bold for the Section Titles - size 11, for the section contents - size 9, italics, for figure numbers and labels. |
Word count (or equivalent): | 2400 words |
This a reflection of the effort required for the assessment. Word counts will normally include any text, tables, calculations, figures, subtitles and citations. Reference lists and contents of appendices are excluded from the word count. Contents of appendices are not usually considered when determining your final assessment grade. | |
Submission Details
Submission Deadline: | Main 1st February 2026 12th February 2026 | ||
Mid 6th November 2025 (Tentative) | Estimated Feedback Return Date | ||
Submission Time: | By 23:59 pm on the deadline day. | ||
Moodle/Turnitin: | Any assessments submitted after the deadline will not be marked and will be recorded as a non-attempt unless you have had an extension request agreed or have approved mitigating circumstances. See the Gulf College website for more information on submission details and mitigating circumstances. | ||
File Format: | The assessment must be submitted as a word document and submit through the Turnitin submission point. Your assessment should be titled with your: Student ID number, Module code and Assessment ID, e.g. 2410500 GAC3000 WRIT1 | ||
Feedback | Feedback for the assessment will be provided electronically via Turnitin / MS Teams / Face to Face. Feedback will be provided with comments on your strengths and the areas which you can improve. Module tutors give students two types of assessment feedback: formative, which is given when the student is working on the completion of an assignment or coursework, and summative, which is given upon completion of the module. A comprehensive assessment feedback on your performance will be given after the announcement of the results (10 Working Days). | ||
Assessment Criteria
On successful completion of the module, a student should be able to
- Evaluatethe basic theory and concepts of an appropriate programming paradigm and design, implement, test, and analyse programs using this paradigm.
- Demonstrateintermediate-level fluency in using an appropriate programming language and associated development tools/environments.
- Outlinethe need for a professional and ethical approach to system design and be able to model and analyse real-world problems using appropriate techniques.
In addition, the assessment will test the following learning outcomes:
- Demonstrateintermediate-level fluency in using an appropriate programming language and associated development tools/environments.
- Outlinethe need for a professional and ethical approach to system design and be able to model and analyse real-world problems using appropriate techniques.
Other skills/attributes developed
Graduate Attribute | Description | LO |
Discipline Expertise | Ability to solve real-world problems by applying the learnt principles and concepts in the discipline | LO2 |
Discipline Expertise | Ability to break down complex information to interpret or evaluate a problem or situation | LO2 |
Professional and Ethical | Ability to display professionalism and integrity in all circumstances. | LO3 |
Marking/Assessment Criteria
Description | Marks Allocated |
Introduction and Objectives | 10 |
Program Design | |
Discuss the professional and ethical principles(Minimum 5 Points *1 Marks) | 5 |
Include all (Use case & Class Diagram)the diagrams with a brief description of each diagram( 2 Diagram * 5 Marks) | 10 |
Implementation and Testing | |
Quality of Documentation(proper page numbering, table of contents, list of figures, proper citations, and references) | 10 |
Main Menu Design and User Login(2 Forms * 2.5 Marks) | 5 |
Admin (5 Marks ), Employee (5 Marks ), Order Management(5 Marks ), and Product Management (5 Marks ) Details | 25 |
Code Snippets | 10 |
Database(Minimum of 2 Tables * 5 Marks) | 10 |
Testing (Evaluation with users and evaluation against requirements) | 10 |
Conclusion | 5 |
Total | 100 |
Acknowledgement of the Use of AI
Student Name: | |
Student ID Number: | |
Module Code: | GIS5027 |
Assignment Title: | Object- Oriented System Design |
Date: | Enter a date. |
Acknowledgement (Check mark the appropriate) |
? No content generated by Artificial Intelligence (AI) technologies has been presented as my work. ? I acknowledge the use of [name of AI + URL] to generate materials for background research self-study in the drafting of this assessment. ? I acknowledge the use of [name of AI + URL] to generate materials that were included within inal assessment in modified form. |
The following prompts were input into [name of AI + URL]: |
List prompts here |
The output was changed by me in the following ways: |
Explain the actions taken here |
Marking Criteria / Rubrics
AY: AY 2025-2026 / 1st semester
Criteria | No Answer (0) | Very Poor (20) | Poor (30) | Satisfactory (40) | Good (50) | Very Good (60) | Excellent (70) |
Introduction (5 Marks) | Not provided | No Introduction provided | The introduction and objectives are poorly discussed or lacking | less documentation for introduction and objectives | Basic introduction and objectives have been completed including description; the purpose is noted for each function | Clearly documented the introduction and objectives including descriptions; the specific purpose is noted for each function | Clearly and effectively documented the introduction and objectives including descriptions; the specific purpose is noted for input requirements, processes, and output results |
Discuss the professional and ethical principles(Minimum 5 Points * 1 Marks) 5 Marks | Not provided | No information | Poorly documented the professional and ethical principles | Less information is documented about the professional and ethical principles | Basic information documented about the professional and ethical principles | Clearly documented the professional and ethical principles | Clearly and effectively documented the professional and ethical principles |
Use case diagram with an explanation(5 Marks) | Not provided | No use case diagrams(UCD) | Constructed use case diagrams (UCD) that do not fit the system design. | Constructed a UCD with at least 2 use case descriptions | Constructed a UCD with at least 3 use cases with good descriptions | Clearly documented and Constructed a UCD with at least 4- 3 use cases with proper descriptions | Effectively documented and Constructed a UCD with at least 4 use case descriptions |
Class diagram with explanation(5 Marks) | Not provided | No class diagram | Constructed class diagrams (CDs) that do not fit the system design. | Constructed a CD with at least 2 class descriptions | Constructed a CD with at least 3 class descriptions | Clearly documented and Constructed a CD with at least 4-5 class descriptions | Effectively documented and Constructed a CD with at least 4 class descriptions |
Quality of Documentation(For the proper page numbering, table of contents, list of figures, proper citations and references)(5 Marks) | Not provided | No proper format followed | Four of the items in the Excellent column are missing. | Two of the items in the Excellent column are missing. | Three of the items in the Excellent column are missing. | .One of the items in the Excellent column is missing | proper page numbering is evident, table of contents and list of figures are included, citations and referencing were properly done |
Main Menu Design and User Login(5 Marks) | Not provided | Implementation is not evident | Very poor implementation and the software does not work in almost all functions | Run with multiple errors, used basic coding but referenced the database, and met at least 3 specifications | Run with numerous errors, and used basic coding with less reference to the database, and met at least 2 specifications | Runs with few errors used complex coding that referenced the database, nd met at least 4 specifications | Excellently run with negligible errors, used complex coding that referenced the database, and met all of the specifications. |
Admin, Event Details, Attendance, and Cancellation Details (25 Marks) | Not provided | No, implementation has evidenced | .Very poor implementation and the software does not work in almost all functions | Run with multiple errors, used basic coding but referenced the database, and met at least 3 specifications. | Run with numerous errors, and used basic coding with less reference to the database, and met at least 2 specifications. | Runs with few errors, ued complex coding that referenced the database, an met at least 4 specifications. | Excellently run with negligible errors, used complex coding that referenced the database, and met all of the specifications. |
Listing details(5 Marks) | Not provided | Not Listed and details format followed | Very poor implementation and the software does not work in almost all functions | Run with numerous errors, and used basic coding with less reference to the database, and met at least 2 specifications | Run with multiple errors, used basic coding but referenced the database, and met at least 3 specifications. | Runs with few errors used complex coding that referenced the database and met at least 4 specifications | Excellently run with negligible errors, used complex coding that referenced the database, and met all of the specifications. |
Code Snippets(10 Marks) | Not provided | No proper format followed | No name, date, or assignment title included Poor use of white space (indentation, blank lines). Disorganized and messy Poor use of variables (many global variables, ambiguous naming). | Includes name, date, and assignment title. Fair use of White space Fair organisation of work. Fair use of variables (few global variables, unambiguous naming). | Includes name, date, and assignment title. White space makes the program fairly easy to read. Organized work. Good use of variables (few global variables, unambiguous naming). | Includes name, date, and assignment title. Good use of white space. Organized work. Good use of variables (no global variables, unambiguous naming) | Includes name, date, and assignment title. Excellent use of white space. Creatively organized work. Excellent use of variables (no global variables, unambiguous naming). |
Uses Vector or Database(10 Marks) | Not provided | Not used any vector or database | Very poor use of vector or database | Fair uses of one vector or table | Uses one vector or tables is implemented but the second one is not properly | Uses two vectors or tables are used but some columns or attributes are missing. | Excellently implementation and uses two tables or vectors. |
