Broadacre cycle hire assignment

CTEC0701 Problem Solving and Programming Module name: Problem Solving & Programming Module code: CTEC0701 Title of the Assignment: Broadacre Cycle Hire Assignment This coursework item is: (delete as appropriate) Summative Formative This summative coursework will be marked anonymously Yes No The learning outcomes that are assessed by this coursework are: 1. Demonstrate an understanding of object-oriented systems analysis theory to include: a. Identifying the system requirements and functionality from a given business scenario b. Document the system requirements using UML This coursework is: (delete as appropriate)

Individual

Group

This coursework constitutes 35 % to the overall module mark.

Date Set: 13/03/2017 Date & Time Due: 7th April 2017 before 1pm Your marked coursework and feedback will be available to you on: If for any reason this is not forthcoming by the due date your module leader will let you know why and when it can be expected. The Head of Studies (rgh@dmu.ac.uk) should be informed of any issues relating to the return of marked coursework and feedback.

11th May 2017

When completed you are required to submit your coursework to: 1. FOTAC GH.0.4a 2. Turnitin Late submission of coursework policy: Late submissions will be processed in accordance with current University regulations which state: “the time period during which a student may submit a piece of work late without authorisation and have the work capped at 40% [50% at PG level] if passed is 14 calendar days. Work submitted unauthorised more than 14 calendar days after the original submission date will receive a mark of 0%. These regulations apply to a student’s first attempt at coursework. Work submitted late without authorisation which constitutes reassessment of a previously failed piece of coursework will always receive a mark of 0%.”

Academic Offences and Bad Academic Practices:

These include plagiarism, cheating, collusion, copying work and reuse of your own work, poor referencing or the passing off of somebody else's ideas as your own. If you are in any doubt about what constitutes an academic offence or bad academic practice you must check with your tutor. Further information and details of how DSU can support you, if needed, is available at: http://www.dmu.ac.uk/dmu-students/the-student-gateway/academic-support-office/academic-offences.aspx and http://www.dmu.ac.uk/dmu-students/the-student-gateway/academic-support-office/bad-academicpractice.aspx

Tasks to be undertaken: See Assignment Brief Deliverables to be submitted for assessment: Word Processed Report How the work will be marked: See Marking Scheme Module leader/tutor name: Contact details: CTEC0701Problem Solving & Programming Foundation Year in Computing

Dawn Johnston dawn@dmu.ac.uk 1|Page

CTEC0701 Problem Solving and Programming

Broadacre Cycle Hire Assignment Your task is to create a set of system requirement documents for the Case Study below. You will need to read the case study several times and make notes before documenting the requirement needs for a new system.

Broadacre Cycle Hire Case Study The owner of Broadacre Cycle Hire has approached your software company to develop an

online system to help manage the cycle hire bookings. Broadacre Cycles is in a small village close to a large lake and forest. There are facilities for camping at the lake, various mountain bike trails throughout the forest and a perimeter track around the lake for walkers and cyclists.

The company have various types of bikes for hire; Adult Mountain bikes specifically for the off-road forest trails and adult and junior hybrid bikes and tandems only suitable for the perimeter track. Trailers for under 5’s can also be hired but are only available for the adult hybrid bikes. There are two bike technicians that carry out monthly maintenance, complete a safety checklist on all bikes prior to being hired and on return, and move the bikes required for that day from the storage unit to the collection point.

Bikes can be hired for half a day or a full day. Customers that are booked into the campsite for a minimum of 3 days can hire a bike for the duration of their holiday and will receive a 10% discount on the full day hire fee. All customers pay a deposit for each bike they hire and this is refunded when the bike is returned in good order and on time.

•

• • • • •

bikes need to be reserved at least two weeks in advance and has to include o the customer details o the number of bikes (including trailers) and type o the duration of the hire a credit or debit card deposit is taken at the time of the reservation a confirmation letter is sent to the customer full payment should be me made on the day of the bike hire o the customer needs to provide photo ID at the time of payment o the customer needs to provide confirmation of their camping booking a safety checklist is completed and recorded prior to being hired and on return at the collection point with the customer the deposit is refunded in full if the bike is returned undamaged and on time

The receptionist deals with all reservations, payments, customer details, proof of ID and camping, refunds, cancellations, producing the daily hire list and confirmation letters.

The bike technicians are responsible for monthly maintenance records, safety checklists and ensuring the correct bikes are ready at the collection point each morning.

CTEC0701Problem Solving & Programming Foundation Year in Computing

2|Page

CTEC0701 Problem Solving and Programming All reservations are currently made over the phone but it is hoped that the new online system will also allow the customers to register their details so they can make online reservations, receive email confirmation and pay their deposit.

Task 1 - Create a Gantt Chart You will need to produce a Gannt chart that determines how you will manage your assignment. You should include a set of tasks for the duration of the assignment along with any milestones, sub tasks and task dependencies.

Task 2 – Identify the System Requirements Specify a set of requirements for the system, classifying them as functional requirements, nonfunctional system requirements, non-functional external requirements, or usability requirements, and assigning each a priority according to the MoSCoW classification (See Lecture Notes for MoSCoW). Present these as a set of lists.

Task 3 – identify and document the Use Cases Define a set of use cases for the system and show them on a use case diagram. a. Identify the actors. b. Identify the use cases for each of the actors you have identified. c. Write up the use case descriptions in MS Word d. Create a Use Case Diagram (you must use QSEE) Task 4 – Identify and document the Classes Create a Class diagram having identified your classes from your Use Cases. The class diagram should show the names of the classes, the attributes and the methods that the objects of each class can execute. You must use QSEE for the Class Diagram.

What you need to submit Present your system requirements documentation as a word-processed document (either .docx or .pdf). You should include a title page containing: • • • •

Module code and title Your P number ONLY Assignment title Deadline date

You should include your P number only in the footer of every page along with page numbers (there should be no page number displayed in the title page). This assignment is anonymously marked.

You should include a contents page and references where required.

Additional Advice •

Ideally there should be one complete Use Case diagram and a set of descriptions. However, you may create a use case for each actor as a separate Use Case diagram.

CTEC0701Problem Solving & Programming Foundation Year in Computing

3|Page

CTEC0701 Problem Solving and Programming •

When thinking about the classes try and identify what each object needs to DO first, and what attributes it needs to have to do it second.

Submission Details • • •

This individual assignment will be marked anonymously.

To be handed in with an Individual Cover Sheet in the Student Advice Centre (FOTAC) GH.0.4a by Friday 7th April 2017 before 1pm

th You should also submit the word-processed document through Turnitin by Friday 7 April

2017 before 1pm

CTEC0701Problem Solving & Programming Foundation Year in Computing

4|Page

CTEC0701 Problem Solving and Programming Marking Scheme 0–1 Gantt Chart

Not submitted or unworkable 0–5

Functionality

Too few functions identified. Functions Incorrectly/not classified.

0–1

Functionality (use of MoSCoW)

Use Case Description

Use Case Diagram

Class Diagram

Attributes

No evidence of MOSCOW

3

Some idea of how the assignment will be completed. No milestones, no dependencies

A reasonable idea of tasks with some dependencies and milestones

6 – 10

11 – 15

Correctly identified some main functions. Some correctly classified.

2 Some attempt to use MOSCOW.

4 A clear idea of tasks, dependencies considered and milestones included 16 – 20

Main important functions identified with mostly correct classifications.

Majority of functions identified with correct classifications.

3

4

MOSCOW used to good effect.

MOSCOW correctly used in majority of functions.

5 All detailed and clear Gantt chart that satisfies all requirements.

21 - 25 Identified main key functions and additional consideration given to wider functionality. Classifications correct 5 MOSCOW used throughout and all correct

0-3

4-8

9 - 13

14 - 17

18-25

Simply not workable

Serious attempt to understand, but not enough focus on the user.

Some of the right idea – could work with a bit of revision.

User’s needs are reflected in suitable inputs and outputs.

Detailed and professional view of use cases.

0-3

4-8

9 - 13

14 - 17

18-25

Simply not workable

Serious attempt to produce diagram but not enough understanding. No notation apart from associations

Mainly correct – relevant to descriptions. Some notation included.

User’s needs are reflected in suitable inputs and outputs. All descriptions accounted for.

Notation sufficient.

Detailed and professional view of these use cases.

0-1

2

3

4

5

Would simply not work for the user.

Poorly organised or missing important data.

Workable classes that model the main requirements.

Near complete classes derived from use cases. Multiplicity ok and notations attempted

Thoroughly professional. Gives real confidence in the design.

0–1

2

3

4

5

Some appropriate attributes included with some key attributes missing

Mainly appropriate, with minor key attributes missing

2

3

No attributes included 0–1

Methods

2

No methods included

CTEC0701Problem Solving & Programming Foundation Year in Computing

Some appropriate methods

Majority of attributes included 4

Mainly appropriate, with minor

Majority of methods included

5|Page

Well thought out attributes included 5 Well thought out methods included

CTEC0701 Problem Solving and Programming included with key methods missing

CTEC0701Problem Solving & Programming Foundation Year in Computing

key methods missing

6|Page