Reference no: EM133506437

Business Systems Analysis

Assignment - Modelling Exercise

Learning Outcome 1: Apply systems analysis, modelling and design techniques to real world problems.

Learning Outcome 2: Assess business requirements, stakeholder requirements, business solution/system requirements and transition requirements.

Learning Outcome 3: Conceptualise effective systems specifications and be persuasive in these presentations.

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 outcome:
• 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.

1. Stakeholders and Requirements

The Kid basketball Clubs Association (KBCA) is an organization including kids' basketball clubs that complete with each 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 KBCAhave been manually organisingthe matches, and now would like to organize the matches via an information system (i.e., KidBasketball), which allows the matches to be auditable bythe AustralianBasketballAssociation (ABA). KBCA has developed a set of guidelines regarding how to ensure the process work properly and fulfill ABA's requirements.

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

KidBasketball will maintain information about the volunteers, including whether they have had training inrefereeing 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, and one day before, and the
morning of the Match. It also needs tolink to a GPS system (such as Google Maps) to show where the competitionis being held and how to get there. If a scheduledofficial 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, andexplain what their interests in the system are.

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

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

2. Use case modelling: user goal technique

People nowadays increasingly use technology to improve their health, and one example is the fitness watch. In this task, consider the fitness watch as the context, you will use the user goal techniqueto identify all the use cases that would be relevant to the user (i.e., a swimmer). The swimmer includes both a recreational to a competitive swimmer, 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.

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

3. Use case modelling - event decomposition technique

Use the event decomposition technique to carry out use case modelling for the systemdescribed below. For each event you identify, name the event, state the type of event, name the resultant use case and give a brief description of it, and name the actors involved. Present your results in the form of a table with the headings:

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

Previously Fantastic Cave manually manage the process of customer booking and cave maintenance. Now Fantastic Cave plans to implement an Information system, named Fantastic Cave Management System (FCMS). FCMS need 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 were completed by a third-party system.

A single cave session can cater for a group of 1 to 10 people, and have one staff member as the leader. The leader needs to go through the cave first and have the rope affixed, and staff being a leader are quired 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 send a staff an email reminder one week before her/his induction expires. Customers must be accompanied by a trained staff member if anyone is under 13 years.

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, 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 experience, 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 session cave inspection is made,
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 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 60 hours or three 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 69 hours without a service. The system updates the status of the cave and make it "bookable" again once the service completes, when the number of usage hours is reset. FCMS also records the dates, times, and details about 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. CEO also needs a report showing the customer usage of the caves, to understand what are the most popular times of year and types of bookings and plan for expansion.