CT044-3-1-IOOP

Group Assignment

This assignment covers the following Course Learning Outcomes (CLO):

	Learning Outcomes	Assessment
CLO2	Develop a solution by applying basic object-oriented concepts in a datasource based application. (C3, PLO2)	Group Assignment -    Implementation
CLO3	Explain the design and solution to develop an application. (A3,PLO5)	Group Assignment -   Documentation

ASSIGNMENT BRIEF

CarCare Service Center Management System

CarCare is a service center in Kuala Lumpur that offers car maintenance and repair services. The service center offers a comprehensive service from routine maintenance such as oil changes and tire replacements to more complex repairs like engine diagnostics and transmission overhauls. Customers must register with the service center before scheduling any services.

Overview of System:

The system includes 4 types of registered users: Admin, Mechanic, Receptionist and Customer. The system should have a login feature to allow the user to key in username/email and password only. The system should identify role of the user and redirect to respective homepage. Following are the functionalities of each role:

1.         Admin

-    Manage staff accounts (add, delete receptionist & mechanic)

-    Manage service information (add, edit, delete services offered & price - oil change, tire replacement, engine repair etc.)

-    View feedback from customer.

-    View reports on service completed and profit generated (filter by month)

2.         Receptionist

-    Manage customer account (add, delete customer)

-    Search  for  existing  service appointments  (based on customer name, vehicle number or appointment id) and assign it to mechanic

-    Check-in  &  check-out  customers  (update  the status of vehicles as they arrive, depart, generate bill and process payment)

-    View inventory requested by mechanics

-    Update own profile

3.         Customer

-    View service details (description, price, estimated time)

-    View and select services based on service type and preferred dates

-    Manage service appointment (schedule, reschedule or cancel)

-     Send feedback for service received.

-    Update own profile.

4.         Mechanic

-    View list of service tasks assigned to him

-    Record the progress  of each  service (completion status, collection time, any additional repairs etc.)

-    Manage parts inventory (request parts, update used parts and report any shortages)

-    Update own profile

IMPORTANT INSTRUCTIONS: This is a group assignment. Upon submission of your assignment, you are required to present your assignment at a date and time specified by your module lecturer. Each  team  member  is  required  to   contribute  towards  some features  in  the  system   and documentation, present and explain his or her work accordingly. Each team member should also be able to answer questions during presentation with regards to the overall systems project and or specific question(s) related to the codes used in the development.

GENERAL REQUIREMENTS

The program you submit should be able to compile without errors using Visual Studio. You should comply with the following coding style. guidelines for the system:

    Use C# features

    Use GUI for the user interface

    Use object-oriented concepts in the solution

    Document your codes by using comments where necessary

    Use indentation

    Use meaningful names for identifiers

You should store all the data in a database management system such as  Microsoft SQL Server, SQL Server Standalone database or any other supported database so that the information can be retrieved later.

This  is  a  standalone  application  and  used  by  the  specified  users  in  the  above  description. Validation of input data should be included for various input values to prevent invalid values to be entered and to prevent errors. The implementation code must include at a minimum the use of object-oriented programming concepts such as classes, methods and objects.

COMPLETED APPLICATION DELIVERABLES

The completed application and documentation must be uploaded to Moodle onor before 10.00pm on the due date.

    The project source folder must be zipped before uploading to Moodle.

    Ensure that your zip file contains all the relevant source code.

    The font size used in the report must be 12pt, and the font type used should be Times New Roman.

    Full source code is not to be included in the report. The report must be typed and clearly printed.

    Header and Footer

Ensure that headers and footers are included in the documentation.

    Header: Module code and module name on the left followed by page number (right).

    Footer: The intake code (left) and institution name (center) of the footer.

DOCUMENTATION GROUP ASSIGNMENT REPORT

As part of the assessment, you must submit the project report by uploading to Moodle in the following format:

1.   Cover Page:

All reports must be prepared with a front cover. The front cover should be presented with the following details:

•         Module Code & Title

•         Intake

•         Student’s ID Number and Name

2.   Contents

a.   Storyboard that shows the draft design of the screens to be implemented in the system. This may be documented through free-hand sketches or may be documented using a wire-framing tool such as Pencil (https://pencil.evolus.vn/), an open-source software. (refer to Appendix A for sample)

b.   A use-case diagram showing the actors and uses-cases in the application

c.   A class diagram showing the classes and methods used in the application

d.   Explanation of the codes implemented in the system where the following Object- oriented programming concepts has been used:

    Classes

    Methods

    Objects

In each of the above, provide code snippets to support the explanation where the concepts were applied.

e.   Test Plan and testcases documenting the functions tested in the system. At least 15 test cases should be documented. (refer to Appendix B for sample)

3.   Conclusion

A critical assessment of the system developed which includes the strengths, the weaknesses and recommendations for future enhancements.

4.   References

•   You may source algorithms and information from the Internet or books. Proper referencing of the resources should be evident in the document.

•   Any references must adhere to APA referencing format which can be accessed from

http://library.apiit.edu.my/apa-referencing/

5.   Workload Matrix (refer to Appendix C for template)

The workload matrix should indicate the section or task completed by each team member. Individual Marks will be distributed accordingly by each team member’scontribution towards the assignment.