MAN5902 Business Systems Analysis

MAN5902 Business Systems Analysis

Assignment 1- Modelling Exercise

Worth: 30% of your final grade.

Individual Assignment

Due: See Canvas

Submit to: Canvas. Submit as a single Word document including all parts of the assignment. You do not need to include a separate cover sheet but your name and student number should also be included in the assignment document.

Word limit: N/A

Late assignments that do not have an extension will be penalised at the rate of 5% per day. For example, if your assignment was 2 days late and the original mark was 65%, your final mark will be 55%.

Completing this assignment will help you achieve Course Learning Outcome (CLO) 2:

Apply critical thinking and technical skills to solve authentic business problems [AQF S2, S3]:

2.1. Conceptualise problems or situations (critically investigate, analyse, synthesize and evaluate).

2.2. Apply technical skills to authentic situations.

2.3. Solve complex problems.

In addition, this assignment will assess the following Unit Learning Outcomes (ULOs):

Apply systems analysis, modelling and design techniques to real world problems.

Assess business requirements, stakeholder requirements, business solution/system requirements and transition requirements.

Conceptualise effective systems specifications and be persuasive in these presentations.

The assignment involves several exercises requiring you to carry out some systems analysis activities based on the material covered in Topics 1-3. The exercises are separate and do NOT form part of a single case study.

You may need to make assumptions where information is incomplete: state any assumptions clearly.

Your diagrams should be drawn using Visio or a similar tool, using the appropriate template for each diagram type. Diagrams should be pasted into the Word document.

Your diagrams must follow the correct notation and naming conventions, and each diagram should include a title and legend.

This is an INDIVIDUAL assignment.

There are no strict format requirements.

Please do not include the content of questions into your submission.

1. Stakeholders and Requirements (8 points)

The Kid Basketball Clubs Association (KBCA) is an organisation including kids basketball clubs that complete with each other regularly throughout the year. The matches are held each week, and volunteers from each club act as a referee and scorer. Each club is affiliated with in-house basketball courts and take turns to host the matches. No club can have a scorer or referee at a match they are participating in.

The Managing Committee of the KBCA has been manually organising the matches, and now would like to organize the matches via an information system (i.e., KidBasketball), which allows the matches to be auditable by the Australian Basketball Association (ABA). KBCA has developed a set of guidelines regarding how to ensure the process works properly and fulfills ABAs requirements.

The newly developed KidBasketball need to automate the process of assigning referees and scorers. Volunteers can thus receive advance notice of when the match will be, where the match will be held, and their roles (scorer or referee). Such notification can include the functions of calendaring and scheduling with a mechanism for advance notice of unavailability and messaging to find a substitute official. Such information will be stored in the central secure database of KidBasketball and will be accessible through different interfaces (e.g., computers and mobiles) by the committee members, ABA and the volunteers.

KidBasketball will maintain information about the volunteers, including whether they have had training in refereeing and/or scoring, have a government clearance for working with children, and have a current first aid certificate. The system will keep track of the matches to be held during the year.

KidBasketball also need to send text messages a week before, one day before, and the

morning of the Match. It also needs to link to a GPS system (such as Google Maps) to show where the competition is being held and how to get there. If a scheduled official is unavailable, she or he will be able to send a notification to KidBasketball, which will then assign other volunteers for the match.

(a) List the stakeholders for the proposed system and explain what their interests in the system are. (2 points)

(b) List and briefly describe the functional requirements as identified in the description. (4 points)

(c) Using the FURPS+ categories, identify and describe non-functional requirements. Address all of the categories (URPS+): if you consider that any of them are irrelevant, explain why. (2 points)

2. Use case modelling: user goal technique (10 points)

People nowadays increasingly use technology to improve their health, and one example is the fitness watch. In this task, considering the fitness watch as the context, you will use the user goal technique to identify all the use cases that would be relevant to the user (i.e., a swimmer). The swimmer includes both a recreational and a competitive swimmer, and different contexts (e.g., open water and swimming pool laps) need to be considered.

Use your own experience, or that of a swimmer of your acquaintance, together with any research you need to do.

(a) Present your list in a table giving the use case name and an informative brief description (6 points). Try your best to provide as many as possible. Present your results in the form of a table with the headings:

No. Use case Brief Description

(b) Draw a use case diagram representing the same information (4 points).

3. Use case modelling event decomposition technique (12 point)

Use the event decomposition technique to carry out use case modelling for the system described below. For each use case you identify, provide the type of event, the use case name, a brief description, and the actors involved (if any). Present your results in the form of a table with the headings:

No. Type of event Use case Brief Description Actors (only for external events)

Fantastic Cave (FC) provides cave tunnel facilities which allow people to explore different caves in a secure environment. It has a total 16 tunnels with different grades.

Previously, Fantastic Cave manually managed the process of customer booking and cave maintenance. Now Fantastic Cave plans to implement an Information system, named Fantastic Cave Management System (FCMS). FCMS needs to manage the cave booking and maintain information about customers, staff, and cave sessions. It also needs to maintain the information about cave maintenance and keep track of staff safety induction training.

FCMS will allow customers to book online. Then customers will receive reminder texts about their booking the week before and the day before. Customers can cancel the booked sessions, but cancellation without incurring a charge is only possible up to 4 weeks before the session (after that the full price is payable). FCMS does not need to process any payment, which is completed by a third-party system.

A single cave session can cater for a group of 1 to 10 people and has one staff member as the leader. The leader needs to go through the cave first and have the rope affixed, and staff leaders are required to have had a full safety induction within the last 3 months. FCMS needs to ensure that staff meet the requirements of leader by recording training date and sending staff an email reminder one week before her/his induction expires. Customers must be accompanied by a trained staff member if they are under 13 years old.

Customers also need to meet various requirements, such as be under 70 years, not be pregnant and not have claustrophobia or breathing complaints. Such information is provided and confirmed during booking. Customers also need to provide other information during booking, such as name, address, and contact phone number, and the date and time of the session required. For group booking, a primary contact is needed and details of all customers are required. All customers also need to sign a statutory declaration that the information they provide is true. Such information needs to be stored following insurance and OHS requirements.

Each caving session lasts for 1 hour, with 15 minutes preparation time, and 5 minutes clean-up time.

While some caves provide the basic experiences, wet caves provide customers with semi-flooded experiences such that they can prepare for caving in river caves, including wearing breathing equipment. Web cave sessions are more demanding, and customers are required to have a swimming competency certificate, which is also confirmed during booking.

Safety is the top priority for Fantastic Cave. Between sessions, cave inspections are performed,including physical damage, cleanliness and hygiene, any dropped belongings from the previous session, etc. A technical check of the equipment (ropes and breathing equipment) is also conducted before and after sessions. These checks are recorded by the system.

Further, a full check of the caves is conducted by a service engineer at the beginning and end of every working day. Lastly, each cave must be fully serviced every three months or every 60 hours of use, whichever is sooner. The full service takes 2 days, and FCMS needs to monitor the availability of caves to ensure that at least two caves (one basic and one wet cave) are in service. While a wet cave is being serviced, the drainage system on the flood chambers is also inspected.

The hours of cave use are logged by the FCMS by adding the number of session minutes to the usage log at the end of each session. The cave is removed from the booking system until the full service is completed once it reaches 50 hours or two months of usage. If there are less than 10 hours of bookings over the next two days, these are allowed to take place, but no cave can operate for more than 59 hours without a service. The system updates the status of the cave and makes it bookable again once the service completes when the number of usage hours is reset. FCMS also records the dates, times, and details of each service.

FCMS needs to generate a few reports. First, FCMS needs to provide an ad-hoc status report on each cave, including whether it is in use or being serviced, its current hours of use and date of next scheduled service. The CEO also needs a report showing the customer usage of the caves, to understand the most popular times of year and types of bookings and plan for expansion.

Marking rubric

Criteria HD D C P F

1.6-2 1.4-1.5 1.2-1.3 1-1.1 0-0.9

Q1 a) Stakeholder analysis (CLO2.1)

(2 points) Demonstrates an exceptional ability to apply critical thinking skills, consistently identifying and analysing complex issues with depth and insight. All stakeholders are identified. Comprehensive and accurate explanations of interests are provided.

Demonstrates strong critical thinking skills, effectively identifying and analysing key issues. Most stakeholders are identified. Good explanations of interests are provided. Demonstrates good critical thinking skills, identifying and analysing most key issues. About half the stakeholders are identified. Reasonable explanations of interests are provided. Demonstrates basic critical thinking skills, identifying and analysing some key issues. Only a few stakeholders are identified. Some explanations of interests are provided. Demonstrates limited or no critical thinking skills, failing to identify and analyse key issues effectively. Few stakeholders are identified. Limited explanations of interests are provided.

3.2-4 2.8-3.1 2.4-2.7 2-2.3 0-1.9

Q1 b) Functional requirements, analysis (CLO2.1)

(4 points) Thoroughly identifies and describes functional requirements. Accurately identifies and describes most functional requirements. Identifies a reasonable number of functional requirements adequately.

Identifies functional requirements minimally. Identify few functional requirements.

1.6-2 1.4-1.5 1.2-1.3 1-1.1 0-0.9

Q1 c) Non-functional requirements analysis(CLO2.1)

(2 points) Demonstrates a comprehensive and nuanced understanding of non-functional requirements. Identifies most relevant non-functional requirements accurately and thoroughly, with only minor omissions or inaccuracies.

Identifies some relevant non-functional requirements, though some may be missing or inaccurately described.

Identifies some relevant non-functional requirements but may miss key elements or show inaccuracies. Fails to accurately identify relevant non-functional requirements. Significant omissions or inaccuracies are present.

4.8-6 4.2-4.7 3.6-4.1 3-3.5 0-2.9

Q2 a) Use cases (CLO2.1)

(6 points) Almost all use cases are identified with the correct format. Comprehensive and accurate descriptions are provided.

Most use cases are identified with the correct format. Good descriptions are provided. A reasonable number of use cases is identified. The format is correct for most use cases identified. Reasonable descriptions are provided.

Some use cases are identified. The format is correct for some use cases identified. Some descriptions are provided. Only a few use cases are identified. The format is not correct for most cases identified. Limited descriptions are provided.

3.2-4 2.8-3.1 2.4-2.7 2-2.3 0-1.9

Q2 b) Use case diagram technical skills (CLO2.2)

(4 points) Utilises technical skills with a high level of proficiency and precision. The diagram has no errors and follows the correct notations. The title and the legend are provided.

Shows a high level of proficiency in applying technical skills. The diagram has few errors and mostly follow the correct notation. Applies technical skills reasonably. The diagram has some errors or areas for improvement. A few parts do not follow the correct notation. Applies technical skills reasonably. The diagram has noticeable errors or areas for significant improvement. Some parts do not follow the correct notation. Applies technical skills inadequately. The diagram has frequent errors and significant misunderstandings. The whole diagram may not look like a use case diagram.

9.6-12 8.4-9.5 7.2-8.3 6-7.1 0-5.9

Q3 Use cases problem solving (CLO2.3)

(12 points) Provides comprehensive and creative solutions. All or almost all use cases are identified, and there are few errors regarding the format, types of events, actor, and descriptions. Provides well-developed solutions. Most use cases are identified, and there are few errors regarding the format, types of events, actor, and descriptions. Provides effective solutions. A reasonable number of use cases is identified, and there are some errors regarding the format, types of events, actor, and descriptions. Provides basic solutions. Some use cases are identified, and there are some errors regarding the format, types of events, actor, and descriptions. Provides ineffective or no viable solutions. Only a few use cases are identified, and there are many errors regarding the format, types of events, actor, and descriptions.