Student NAME:
MODULE CODE: CET131
MODULE TITLE: Software Engineering
MODULE LEADER: Sardar Jaf
SUBMISSION DATE AND TIME: As stated in the assignment submission page on Canvas for this module ASSIGNMENT: 1
Academic Misconduct is an offence under university regulations, and this involves:
• Plagiarism – where you use information from another information source (including your previously submitted work) and pass it off as your own. This can be through direct copying, poor paraphrasing and/or absence of citations. • Collusion – where you work too closely, intentionally, or unintentionally, with others to produce work that is similar in nature. This can be through loaning of materials, drafts or through unauthorised use of a fellow student’s work. • Asking another person to write your assignment – where you ask another individual or company to complete your work for you, be that paid or unpaid, and submit it as if it were your own.
• Unauthorised use of artificial intelligence – where you use artificial intelligence tools to generate your assignment instead of completing it yourself and/or where you have not been given permission to use artificial intelligence tools by your module leader. Please complete the following declaration around you use of artificial intelligence tools in your assignment.
STATEMENT ON USE OF ARTIFICIAL INTELLIGENCE TOOLS:
|
• I have used artificial intelligence tools to generate an idea for my assignment: YES/NO |
|---|
|
• I have used artificial intelligence tools to write my assignment for me: YES/NO |
|
• I have used artificial intelligence tools to brainstorm ideas for my assignment: YES/NO |
|
• I have used artificial intelligence tools to correct my original assignment: YES/NO |
DECLARATION
• I understand that by submitting this piece of work I am declaring it to be my own work and in compliance with the university regulations on Academic Integrity.
• I confirm that I have done this work myself without external support or inappropriate use of resources. • I understand that I am only permitted to use artificial intelligence tools in line with guidance provided by my Module Leader, and I have not used artificial intelligence tools outside this remit.
• I confirm that this piece of work has not been submitted for any other assignment at this or another institution prior to this point in time.
• I can confirm that all sources of information, including quotations, have been acknowledged by citing the source in the text, along with producing a full list of the sources used at the end of the assignment.
• I understand that academic misconduct is an offence and can result in formal disciplinary proceedings. • I understand that by submitting this assignment, I declare myself fit to be able to complete the assignment and I accept the outcome of the assessment as valid and appropriate.
Please read all instructions and information carefully.
This assignment contributes 50% to your final module mark and will assess the following learning outcomes:
• Ability to utilise appropriate software engineering tools to break down a programming problem into component parts (Learning Outcome 1).
Important Information
You are required to submit your work within the bounds of the University Infringement of Assessment Regulations (see your Programme Guide). Plagiarism, paraphrasing and downloading large amounts of information from external sources, will not be tolerated and will be dealt with severely. Although you should make full use of any source material, which would normally be an occasional sentence and/or paragraph (referenced) followed by your own critical analysis/evaluation. You will receive no marks for work that is not your own. Your work may be subject to checks for originality which can include use of an electronic plagiarism detection service.
For this assessment you are asked to submit an individual piece of work, therefore the work must be entirely your own. The safety of your assessments is your responsibility. You must not permit another student access to your work.
Referencing for this assessment should be done using the Harvard referencing system. (see your Programme Guide).
Please ensure that you retain a duplicate of your assignment. We are required to send samples of student work to the external examiners for moderation purposes. It will also safeguard in the unlikely event of your work going astray.
Submission instruction:
|
Submission Date and Time |
Check Canvas submission page for date and time of submission |
|---|---|
|
Submission Location |
Digital copy via Canvas |
|
Document Format |
1. A report containing the required software modelling diagrams for a fictitious system. |
|
Assignment weight |
30% |
|
Other requirements |
You must adhere to the above assessment requirements. Your source code will be checked for plagiarism. |
CET131 Assessment 1
Scenario
You have recently been employed as a graduate software developer working remotely for a new technology consultancy company. After completing a number of induction-based tasks, your line manager has issued you with your first client-based project.
WeAreCars are a new car rental company based in Sunderland. They are needing a software solution to assist in the rental of their vehicles. This solution needs to be a standalone windows forms based program to ensure future compatibility with legacy systems. The company has strict initial requirements and are on a tight budget due to them being a new company. However, WeAreCars wish to ensure the software is to be of the highest standard and do not want to launch the solution until all requirements are fully implemented and tested.
System Specification
WeAreCars would like a software application that will assist in the rental of cars. You are you required to model the software using certain UML diagrams to show the following software features:
● A staff login feature that allows a staff member to login into the system, using a fixed username and password
○ Username : sta001
○ Password: givemethekeys123
● A feature that displays a list of the currently rented cars
● A main booking feature that will process the booking. This area will allow a staff member to enter and/or select certain options (Mandatory fields are denoted with a *):
○ Customer First Name*
○ Customer Surname*
○ Customer Address*
○ Customer age*
○ Valid driving license*
■ If no, the booking can’t proceed
○ Number of days* (£25 per day)
■ Between 1 and 28
○ Type of car selected*
■ City car (No extra charge)
■ Family car (+ £50)
■ Sports car (+ £75)
■ SUV (+ £65)
○ Fuel type*
■ Petrol (No extra charge)
■ Diesel (No extra charge)
■ Hybrid (+ £30)
■ Full electric (+ £50)
○ Optional extras
■ Unlimited mileage (+ £10 per day)
■ Breakdown cover (+ £2 per day)
WeAreCars would like this system to be as robust and as user friendly as possible. Attention to detail and the inclusion of validation and help systems / tooltips are recommended.
Tasks to be completed
User case scenario (40%)
Detailed Use Case Scenario to show the tasks involving a staff member registering the renting out of a car (i.e., booking). Use the system requirements described above to assist you with this. You should use the template provided in the Canvas assignment page for your use case.
Flow chart (30%)
Detailed flow chart to demonstrate the process(s) involved in user credential validation and login.
Class diagram (30%)
Design a class diagram detailing all the required classes for the completed software prototype. Each class should show the attributes and the methods.
Marking Scheme
|
Tasks |
Up to 100% |
90% |
80% |
70% |
60% |
50% |
40% |
<40% |
0% |
|---|---|---|---|---|---|---|---|---|---|
|
Detailed Use Case Scenario (40%) |
Perfect use case develop ed to perfect level of detail and professi onally present ed |
Excellent use case developed to an excellent level of detail and profession ally presented. |
Comprehe nsive attempt and detailed use case, may only lack very minor detail but all sections have been attempted |
Very good and detailed use case, may lack some detail but all sections have been attempted |
Good attempt at the detailed use case, may lack some detail but all sections have been attempted |
Some confusion shown, few incomplete scenarios and lack of understan ding of some areas of the detailed use case. |
Several confusions shown, many incomplete scenarios and lack of understan ding of many areas of the detailed use case. |
Major confusion shown, incomplete scenarios and lack of understan ding of almost all areas of the detailed use case. |
You have not submitt ed this part of the assessm ent. incorrec t informa tion or missing too much details. |
|
Flow diagram (30%) |
Excellen t flow chart diagram has been made with no errors or lack of details. |
Very Good flow chart diagram have been made to show all of the system componen ts and their connection s. Including showing correct informatio n. But the design is slightly different from the system |
Very Good flow chart diagram have been made to show most of the system componen ts and their connection s. Including showing correct informatio n and mostly |
Very good flow chart diagram has been made to show most of the system componen ts and their connection s, the design partially reflects the system implement ation. |
Good flow chart diagram has been made to show most of the system componen ts and their connection s. But the design doesn’t reflect the system implement ation. |
Satisfactor y flow chart diagram has been made to cover some of the system componen ts, missing some details and doesn’t fully reflect the system implement ation. |
Satisfactor y flow chart diagram showing minimal details and doesn’t fully reflect the system implement ation. |
Good flow chart diagram has been made with incorrect informatio n, it doesn’t cover the complete system and doesn’t fully reflect the system implement ation. |
You have not submitt ed this part of the assessm ent. incorrec t informa tion or missing too much details. |
|
implement ation. |
reflects the system implement ation. |
||||||||
|---|---|---|---|---|---|---|---|---|---|
|
Class diagram (30%) |
Excellen t class diagram design has been made with no errors or lack of details. |
Very Good class diagram design have been made to show all of the system componen ts and their connection s. Including showing correct informatio n. But the design is slightly different from the system implement ation. |
Very Good class diagram design have been made to show most of the system componen ts and their connection s. Including showing correct informatio n and mostly reflects the system implement ation. |
Very good class diagram design has been made to show most of the system componen ts and their connection s, the design partially reflects the system implement ation. |
Good class diagram design has been made to show most of the system componen ts and their connection s. But the design doesn’t reflect the system implement ation. |
Satisfactor y class diagram design has been made to cover some of the system componen ts, missing details and doesn’t fully reflect the system implement ation. |
Good class diagram design has been made to cover some of the system componen ts, missing details and doesn’t fully reflect the system implement ation. |
Good class diagram design has been made with incorrect informatio n, it doesn’t cover the complete system and doesn’t fully reflect the system implement ation. |
No class diagram design has been made, incorrec t informa tion or missing too much details. |