Assignment Case Study D - ActiveGo Disclaimer: The situation described in the following case study is fictional, and bears no resemblance to any persons, businesses, or organizations, living or dead. Any such resemblance, if exists, is merely coincidental, and is not intentional. ActiveGo is a local sports equipment hire service, which is finally looking to upgrade its paper-based systems to an ICT solution to manage its growing customer base and equipment tracking system. ActiveGo records information about each of its customers, including first name, last name, address, email address, phone number, and date of birth. It also has branched out into providing hire services to business customers, who have a company name instead of a first name and last name, and do not have a date of birth. The sports equipment that ActiveGo hires outcomes in many different pack types, such as a 'mini soccer pack' or a 'frisbee golf pack'. There are multiple copies of each pack type, and ActiveGo does not differentiate between different packs of the same type - one 'mini soccer pack' is considered the same as another 'mini soccer pack'. However, ActiveGo does keep track of how many 'complete' and 'incomplete/damaged' packs of each type there are at a given storage location. ActiveGo manages multiple storage locations. Packs are not assigned to a particular storage location, so ActiveGo just records how many packs of each type (and how many of them are 'complete' and 'incomplete/damaged', as previously mentioned) are stored at each location. Each storage location is defined by the suburb they are located in (e.g. "Bruce", "Belconnen"). As should be obvious, each pack can only be stored at one location at a time. Customer hires are recorded, with the start date, end date, pickup location, drop-off location, and the type of pack hired. Each pack type has a different standard daily fee, which determines the initial cost of hire to be paid upon pickup, plus a deposit amount that is returned to the customer when the pack is returned in a complete and undamaged state. Upon return, the condition of the returned pack is recorded, along with the actual date of return. One of the things that ActiveGo would like is a weekly report of incomplete/damaged pack types and locations to be generated, so they can work out if they can combine the components of two or more incomplete/damaged packs to make one more complete package. A future improvement might be to track individual components of packs, but they are not looking to add this functionality at this time. ActiveGo would also like the system to automatically return the deposit once a pack has been checked and confirmed to be complete and undamaged, and/or invoice late fees if a pack is not returned on time. Late returns are charged 150% of the standard daily fee (or 1.5 times the standard daily fee) per day or part there of late.

7. Use case description (2 marks) Your report is expected to contain one use case description for one of the most interesting use cases of the system that is sufficiently complex to justify further explanation using a use case description. a) (1 mark) The use case description itself b) A 1-2 paragraph justification for why the use case being described is one of the most interesting and complex use cases of the system that warrants further explanation using a use case description