1. Additional research and assumptions (1 mark) Your report is expected to describe the additional research and investigation that has been used to inform and improve the analysis and modelling in the remainder of the assignment, citing specific sources where necessary. This may include websites, articles, and examples of similar systems or businesses. In addition, you are expected to list and describe any assumptions made that affect the analysis and modelling in the remainder of the assignment. This section is expected to describe the following: a) (1 mark) What has been added or expanded upon, compared to the case study as provided, and what other sections of the assignment these additions and expansions are most relevant to. For those additions/expansions based on research and investigation, cite the specific sources that have informed these additions and expansions; for those additions/expansions based on assumptions, explain and justify why the assumption has been made. Remember that additions/expansions, and particularly assumptions, should not contradict or conflict with anything already described in the case study. If you are working on the same case study for Assignment 2 as you did for Assignment 1, it is acceptable for your additional research and assumptions to be similar to those you have made in the previous assignment. However, it is expected that the impact and relevance of these additions and expansions will differ given the different content of this assignment compared to the previous assignment.

SAM 11486 / SAM G 6677 Assignment 2 - Group Semester 2 2022 Page | 9 2. Context diagram (3 marks) Your report is expected to include a context diagram for the system. The context diagram should include the following elements: a) (1 mark) System, including an appropriate name b) (1 mark) External entities c) (1 mark) Dataflows 3. Data dictionary (2 marks) Your report is expected to include a partial data dictionary that describes all of the most important data flows present in the context diagram and dataflow diagram. Note that a complete data dictionary is not expected, however it is expected that the data dictionary includes all important information data flows and explains any dataflows that need additional clarification or decomposition. The data dictionary should contain both of the following elements: a) (1 mark) Algebraic data dictionary entries b) (1 mark) Tabular data dictionary entries 4. Dataflow diagram (4 marks) Your report is expected to contain a top-level DFD that describes the core processes of the system. The dataflow diagram should contain the following elements: a) (1 mark) Processes b) (1 mark) Data flows c) (1 mark) Data stores Your DFD should also include external entities, however these should be the same as those identified in your context diagram so there is no separate mark awarded for these as part of the DFD requirement. In addition, it is expected that your DFD should balance with and be consistent with your context diagram, taking into account your data dictionary entries. d) (1 mark) Consistency between the context diagram, data dictionary, and DFD 5. Process specifications (2 marks) Your report is expected to contain one process specification for one of the most interesting processes of the system that is sufficiently complex to justify further explanation using a process specification. This process specification is to be provided using one (and only one) of the formats covered in the unit. a) (1 mark) The process specification itself b) (1 mark) a 1-2 paragraph justification for why the process being described is one of the most interesting and complex processes of the system that warrants further explanation using a process specification

SAM 11486 / SAM G 6677 Assignment 2 - Group Semester 2 2022 Page | 10 6. Use case diagram (4 marks) Your report is expected to contain a use case diagram that describes the core use cases of the system. The use case diagram should contain the following elements: a) (1 mark) Use cases b) (1 mark) Actors c) (1 mark) Associations between actors and use cases d) (1 mark) Complex use case diagram features such as generalisation, includes, and/or extends associations 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) (1 mark) 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

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 out comes 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 - for example, one 'mini soccer pack' is considered exactly 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. Individual 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. The storage locations are defined by the suburb they are located in (e.g. "Bruce", "Belconnen"). As should be obvious, each individual 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 for 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 or more complete packs. A future improvement might be to track individual components of packs, but they are currently focusing on the core aspects of pack hire an returns at the moment. 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 thereof late. As an ICT business analyst, you will be tasked with analysing and modelling ActiveGo's current business practices in order to better understand the current situation of the business, with a view towards creating a single, updated ICT system to manage their delivery management system.4. Dataflow diagram (4 marks) Your report is expected to contain a top-level DFD that describes the core processes of the system.