ITECH2002 – Systems Modelling

ITECH2002 – Systems Modelling
Assignment 1 Specification – 2021
Page 1/9
Systems Requirement Specification
1. TIMELINES AND EXPECTATIONS
Due date: Monday, Week 7, 11:55pm.
Weighting: 20%, maximum mark: 20.
Minimum time expectation: 30 hours.
You will be working in groups of three students.
Your assignment will be assessed by your tutor or lecturer if your lecturer is also your tutor. You will receive your mark and written feedback via Moodle two weeks after the due date or submission, whichever is later.
2. INTRODUCTION
You have been hired as a systems analyst to work with two other analysts. Your task is to document the functional requirements of Airbnb in UML.
In a typical learning environment, assignments are often based on hypothetical case studies, like those in the tutorials. Such case studies are limiting because you have little opportunity to investigate how authentic computer systems work, thus making it difficult to appreciate the complexity of an authentic system, the need of analysis and the usefulness of analysis tools. We hope that by investigating an authentic system you will appreciate the importance of analysis and the role of UML as a communication and analysis tool.
During the analysis stage, UML is used to specify systems requirements, which will be used to design a computer system. In this assignment, we will use UML to document a system that has already been computerised – like reverse engineering a system (from an existing computer system to specification). This has another advantage in that you can evaluate if your specification is close enough to the real system. However, be careful when reverse engineering so you do not also include the design decisions (such as login, click a button, hit Enter, etc) – please see your lecturer when you are unsure, we are more than happy to give you feedback.
Please note that the case study provided here is incomplete and you need to investigate Airbnb to complete the assignment, such as visiting their website or following Airbnb development in the news. If you cannot find the information you need, please talk to your lecturer or tutor.
You may also come up with functionality that does not yet exist but would add value to the business, but please discuss with your tutor first.
ITECH2002 – Systems Modelling
Assignment 1 Specification – 2021
Page 2/9
Section 3 describes the motivation behind the design of this assignment; Section 4 provides information on how and what to submit (note that Moodle has been set up, so there is only one submission from each group). The case study can be found in Section 5. Section 6 describes the tasks and mark allocation for individual and group work. Section 7 shows the marking rubric.
3. MOTIVATION.
The purpose of the assignment is to ensure that you know:
1. How to document functional requirements using three tools widely used in the IT industry: brief use case description, use case diagram and domain model class diagram. The use case and domain model class diagrams are part of the Unified Modelling Language (UML).
2. How different stakeholders contribute to the definition of requirements.
3. How to write constructive reflection using Gibbs’ reflective cycle.
The assignment addresses the following learning outcomes:
K1. Explain how models are used to assist in analysing and modifying existing business systems;
K2. Define various roles involved in the processes of system analysis;
K3. Describe techniques used to gather required information for system analysis;
K4. Explain the various stages of the system development life cycle;
S1. Identify appropriate models for given scenarios;
S2. Develop various models using a professional CASE tool;
S4. Perform Object Oriented Analysis and Design to construct various object models used to communicate the scope and requirements of the project.
A1. Write integrated reports, using appropriate models, providing detailed analysis of given textual scenarios.
4. WHAT AND HOW TO SUBMIT
1. Create a document in OneDrive and share it with your team members.
2. This assignment has eight tasks (see Section 6), and there are two types of submissions:
a. Group submission. Submit tasks 1 to 4 and 6 to 8 as a single report.
Submit your document via Moodle Shell. Moodle has been set up so each group submits only one document. You need to submit the group report in .docx or .odt or .pdf.
ITECH2002 – Systems Modelling
Assignment 1 Specification – 2021
Page 3/9
Please nominate a team member to submit. You need to submit only one document for the whole group. If you submit only your own work, you will lose all the group marks.
b. Individual submission. Submit constructive reflection (task 5) individually.
3. Plagiarism. Your submission will be checked by Turnitin, a plagiarism detection system. Students suspected of plagiarism will face disciplinary actions. Copying or allowing your work to be copied (including uploading your assessment to StuDoc or something similar) constitute plagiarism.
4. Working in groups can be challenging but being able to work in groups is a highly valuable skill. Please see the tips on Moodle Shell – “Groupwork Online” on top of the shell for successful group work.
5. CASE STUDY
The case study for this assignment is based on Airbnb (www.airbnb.com.au), initially a stay share platform but it is offering more services now. We will focus on the accommodation service.
We will investigate three subsystems of the Airbnb accommodation service:
1. Booking subsystem
2. Listings (Accommodation) subsystem; and
3. Airbnb Management subsystem.
These three subsystems are described in the following sections. Some functionality or processes may have been simplified or modified to meet certain learning objectives.
5.1 Booking Subsystem
Before booking, prospective guests search for suitable accommodation. They can specify the location they are interested in, check-in and check-out dates. Note that the dates can be fixed (exactly as users entered) or flexible (± 1, 3 or 7 days). Users also have to specify the number of guests – adults, children (aged 2 to 12), or infants (under 2). The system then lists all available accommodation that fit the search criteria. This list only provides an overview of the properties, and users can choose a rental property to see in detail.
For each available property on the list, the system should show a summary for the property. It should display a large cover photo, a one-line description, the number of guests it can accommodate, rooms available (bedrooms, the number of beds and bathrooms), reviewer
ITECH2002 – Systems Modelling
Assignment 1 Specification – 2021
Page 4/9
rating and the number of reviewers, prices (original and discount price if there is any) and a tag if there is any. Tags can be “New lower price” or “Rare find”.
Guests can also narrow down their search by specifying:
– Property types (house, bed and breakfast, apartment, boutique hotel, bungalow, cabin, etc)
– Unique stays (barn, campervan/RV, boat, campfire, castle, houseboat, lighthouse, plane, teepee, etc)
– House rules (pets allowed, smoking allowed)
– Host language (English, German, Urdu, Chinese, etc)
To help guests get an overview of prices vs address, the system should also display a map and overlay the prices over the map. Guests can also view each property displayed on the map or list in more detail. A detailed view should include all information in the brief display but it should also include:
– Other pictures.
– A map of the location.
– Name of the host
– Check-in and check-out dates
– Any special message (especially now re. COVID-19 restrictions)
– Other information, such as type of cleaning, how to check-in, cancellation policy, house rules, sleeping arrangements, amenities such as parking availability, kitchen, hangers, hairdryer, heating, wifi, iron, tv, washing machine, first aid kit, shampoo, etc – up to 26 amenities.
– Detailed description.
– Detailed house rules, including health and safety.
Prospective guests can also see the overall rating of the reviews in terms of cleanliness, communication, check-in procedure, accuracy, location and value. If they still have questions, they can also contact the host. If all goes well, they can reserve the accommodation – note that reservations can only be confirmed after full payment. Even after confirmation, guests can still cancel their booking but they are bound by the Airbnb standard cancellation policy and extenuating circumstances policy.
All guests have up to 14 days after checking out to review their experience. Similarly, hosts can also review their guests.
5.2 Listings (Accommodation) Subsystem
This system is mostly used by hosts. All hosts are responsible for adding and maintaining their listings. You may like to start exploring hosting in Airbnb. Tips: to get an idea of what kind of information hosts need to provide for a listing, have a look at the information that Airbnb needs to display for guests. Much of the information can only be provided by the
ITECH2002 – Systems Modelling
Assignment 1 Specification – 2021
Page 5/9
hosts; for example, price, description and pictures of the accommodation (
how many pictures can a host upload?).
All hosts are covered by Airbnb Host Protection Insurance, and a host can claim insurance if their guests are injured or if their property is damaged. Airbnb will assess each insurance claim. Bear in mind that this insurance is only available in some countries, so hosts need to check if this insurance is applicable to their listings.
Hosts can also donate their income, track their performance and request professional services, such as professional photography.
5.3 Airbnb Management Subsystem
This subsystem is mostly used by the Airbnb staff in running their services. Generally, bookings are managed by the hosts and their guests, but under exceptional circumstances, Airbnb has to block and cancel all bookings in a region for a period of time. All affected guests are reimbursed, and dependent on management decisions, Airbnb may also reimburse affected hosts.
Airbnb offers superhost badges to exceptional hosts. There is no need for the host to apply – Airbnb initiates this process. Airbnb does not endorse or sponsor hosts or their listings, but it gives superhosts some benefits.
To keep all guests and hosts up to date with policies as well as terms and regulations, Airbnb needs to notify all guests and hosts of changes. Some matters are more relevant to the wider public, such as alerts or a marketing campaign, and they should be publicly available. Airbnb also keeps track of which of their staff release which news articles. All news articles should only be displayed for a specified time.
The management of Airbnb also needs various reports on the financial performance of the platforms in various regions.
6. ASSESSMENT TASKS
This assignment has group work and individual work components. For diagramming (use case diagram and domain model class diagram), you may use any tools you are comfortable with; for example, popular web-based tools such as draw.io. You may use other tools but make sure all members in your group use the same tool.
The following sections describe the tasks for the group and individual work and the distribution of marks.
ITECH2002 – Systems Modelling
Assignment 1 Specification – 2021
Page 6/9
Task 1 – Individual work [14 marks]
1
1 mark – Stakeholders.
a. List four stakeholders of your subsystem.
b. Indicate whether they are internal operational, internal executive, external operational or external executive.
c. Describe the role of each stakeholder, that is how they “fit into the grand scheme of the IT solution” (Mason, 2020).
2
4 marks – Brief use case description.
Ten brief use case texts for your subsystem – each use case description must have actor(s), use case name and use case description. The written case study provides at least six use cases for each subsystem, so you need to add four more new use cases.
The new use cases must fit in with the case study and your subsystem– for example, the case study is based on Airbnb; therefore, a use case such as “calculate postage cost” is irrelevant.
You must include an actor for each use case.
Each use case must also apply these three concepts:
• can be computerised.
• perfect technology assumption (week 3).
• elementary business processes – EBP (week 3).
3
1.5 marks – use case diagram.
A use case diagram based on the brief use case description you have created.
4
5.5 marks – class diagram for each subsystem.
A class diagram for your subsystem. The class diagram must support all the use cases identified.
5
2 marks – constructive reflection (TO BE SUBMITTED INDIVIDUALLY)
Use Gibbs’ Reflective Cycle, as taught in Week 5, to reflect on your experience in working on this assignment.
ITECH2002 – Systems Modelling
Assignment 1 Specification – 2021
Page 7/9
Task 2 – Group work [6 marks]
6
1 marks – Consolidated report
The report must clearly list each student’s name and ID and which subsystem each member is responsible for.
7
4 marks – Consolidated class diagram.
Consolidate all the class diagrams from your team members into a single class diagram.
8
1 mark – Identify the subsystem for the attributes and classes.
Identify the subsystem where the classes and attributes of the consolidated domain model class diagram have come from. This could be achieved by colour coding the attributes from each subsystem; for example, black font for the Booking subsystem, blue font for the Accommodation subsystem and red font for the Airbnb Management subsystem. You must clearly indicate which colour is for which subsystem.
This will ensure that you have included all classes, relationships and attributes from all subsystems and help you and the markers in checking the consistency of the consolidated domain model class diagram.
ITECH2002 – Systems Modelling
Assignment 1 Specification – 2021
Page 8/9
7. MARKING GUIDE
ITECH2002 – Systems Modelling
Assignment 1 Specification – 2021
Page 9/9
Bibliography
Mason, D. 2020. ITECH2002 – Email conversation.
End of assignment specification


Buy plagiarism free, original and professional custom paper online now at a cheaper price. Submit your order proudly with us



Essay Hope