case study

assignmentbrief2021.docx

Home >Information Systems homework help >case study

Assessment 2: Case Study-2

Due date:	Week 12
Group/individual:	Individual
Word count / Time provided:	2500
Weighting:	30%
Unit Learning Outcomes:	ULO-1 ULO-2 ULO-3 ULO-4

Assessment Details:

The Case Study-2 assessment covers the following topics: information system development, system development approaches, data modelling, IS project management, system requirements, user and system interfaces, and system testing, deployment and maintenance.

This assessment allows students to apply theoretical concepts to practice by analyzing case studies and proposing a suitable design. The Case Study-2 assessment covers the following topics: information system development, system development approaches, data Modeling, IS project management, system requirements, user and system interfaces, and system testing, deployment and maintenance.

Case Study: Online System for Kangaroo Taxi

Kangaroo Taxi is a new company in Australia, offering online booking services for their users. Kangaroo Taxi is about to launch an easy-to-use website allowing its users to access from smartphones. The website will enable the users to plan and book their trip. Upon the first use, users would be able to enter their details into the system, including their means of payments (e.g., credit card, PayPal, etc.). This will allow the users to use the Kangaroo Taxi in any subsequent bookings as well. Users can simply log in to their registered accounts and make a booking for a taxi by entering their pickup and destination address. The system will provide them with an estimated cost according to this information.

Suppose you are asked to develop this online system for Kangaroo Taxi. You have been given only three weeks to come up with a blueprint of the system design. After that, you will be presenting your design to a team of consultants. The online system should perform several activities such as adding or creating a new user, checking for available taxis and drivers in the area requested by the customer, calculating the cost of a trip, issuing an online ticket or receipt and processing all bookings transactions. In addition, you may add any other functions for this system.

Tasks:

1. Draw use case description for registering accounts and making a booking.

1. Draw use case diagram.

1. Identify all entities and their attribute and draw an E-R (Entity-Relationship) diagram.

1. Draw the class diagram.

1. Draw a Sequence diagram.

1. Draw activity diagram.

1. Design a data entry screen for entering membership details.

1. Design a booking taxi input screen that includes the date, time, pickup and destination address, type of the service, passenger name, contact number and payment methods. Plan suitable testing and deployment activities.

if you believe that you need to make additional assumptions, clearly state them for each situation *You can use Microsoft Visio or Microsoft Word to present your design.

Assignment Format

Submission:		Only through Canvas
Length:		2500 words max (+ or – 10%)
Font size:		12pt (min) Times Roman
Line spacing:		1.5 or double line spacing
Cover sheet:		APIC standard coversheet
Referencing:		Use Harvard referencing only

Marking Criteria and Rubric: The assessment will be marked out of 100 and will be weighted 30% of the total unit mark.

Marking Criteria	Not satisfactory (0-49%) of the criterion mark)	Satisfactory (50-64%) of the criterion mark	Good (65-74%) of the criterion mark	Very Good (75-84%) of the criterion mark	Excellent (85-100%) of the criterion mark
Introduction (5%)	Poor introduction with irrelevant details	Introduction is presented briefly and is missing the report outline	Introduction is generally presented along with the report outline	Introduction is well written, and the report outline is also discussed	Introduction is very well written, and the report outline is also discussed
Use Case description (10%)	Poorly discussion of the use case description	Brief discussion of the use case description	Good discussion of the use case description	Well discussion of the use case description	Excellent discussion of the use case description
Use Case diagram (10%)	Lack of evidence of understanding of use case diagram	Evidence of basic understanding of use case diagram	Evidence of good understanding of use case diagram	Clear understanding of use case diagram	Has excellent understanding of use case diagram
Entities, Attributes and ER diagram (10%)	Poor identification and description of Entities, Attributes and ER diagram	Brief identification and description of Entities, Attributes and ER diagram	Generally good identification and description of Entities, Attributes and ER diagram	Clear description identification and description of Entities, Attributes and ER diagram	Excellent identification and description of Entities, Attributes and ER diagram
Class Diagram (10%)	Lack of evidence of understanding of Class Diagram	Evidence of basic understanding of Class Diagram	Evidence of good understanding and identification of Class Diagram	Clear understanding and identification of Class Diagram	Has excellent understanding and identification of Class Diagram
Sequence diagram (10%)	Poor identification and description of Sequence diagram	Brief identification and description of Sequence diagram	Generally good identification and description of Sequence diagram	Clear description identification and description of Sequence diagram	Excellent identification and description of Sequence diagram
Activity diagram (10%)	Poor identification and description of activity diagram	Brief identification and description of activity diagram	Generally good identification and description of activity diagram	clear description identification and description of activity diagram	Excellent identification and description of activity diagram
Design a data entry screen (5%)	Poor design of data entry screen	Brief design of data entry screen	Good design of data entry screen	Well design of data entry screen	Excellent design of data entry screen
Design a booking taxi input screen (10%)	Poor design of booking taxi input screen	Brief design of booking taxi input screen	Good design of booking taxi input screen	Well design of booking taxi input screen	Excellent design of booking taxi input screen
Testing and deployment activities (10%)	Poor description of testing and deployment activities	Brief identification and description of testing and deployment activities	Generally good identification and description of testing and deployment activities	Clear description identification and description of testing and deployment activities	Excellent identification and description of testing and deployment activities
Summary (5%)	Summary not relating to the report	Brief summary of the report with some relevance	Generally good summary of the report	A section clearly summarizing the overall contribution	A section very clearly summarizing the overall contribution
References using Harvard style (5%)	Lacks consistency with many errors.	Unclear referencing/style	Generally good referencing/style	Clear referencing/ style	Clear styles with excellent source of references.