UML ASSIGNMENT – BISM 7255 – SEMESTER 1-2021 A Digital Solution for Seniors Craft Circle Dandelion
ASSESSMENT WEIGHTING: DUE DATE:
NEW VERSION: INTRODUCTION
Summary Task:
40%
12 April 2021 at 2:00pm 28 Feb 2021
The assignment asks you to create a collection of UML diagrams (eight diagrams) that visually represent a business information system for the workshops of seniors doing crafts projects, i.e., Dandelion Craft Circle.
Introduction of Case Scenario:
Dandelion Craft Circle is a creative space for seniors over 65 years old to come together for their interest in crafts and arts projects. Each week, a two hours workshop takes place where different creative pieces are created.
Over time, more and more seniors want to attend the crafts circle. The group’s Contact Person (CP), Patrick Keen, manages all matters related to the group with the Excel spreadsheet and pen and pencil. Doing it this way is very time consuming, bears the potential for mistakes and errors, and limits the possibility for others to get involved.
Hence, Patrick would like to have a digital solution to help him with the management of the workshops.
After consulting with the ‘mother’ organization, Arts and Crafts Queensland, which is responsible for all Queensland based crafts circles, Patrick decided to hire the IT consulting company Yellow Mountain to create the digital solution.
Paula Fuchs, the owner of Yellow Mountain, is tasked with the design of the system, and you are working with Paula to design the system. The service agreement contract states that Yellow Mountain captures the requirements, processes, and data needs in a comprehensive UML 2.5 portfolio that includes eight UML diagrams.
Paula suggests using the software Enterprise Architect (EA) from the company Sparx Systems for drawing the UML diagrams, and Patrick supports her in also using this software this time.
Note for BISM7255 students:
1) You must use the software Enterprise Architect to create the different UML diagrams.
2) No assignments with watermarks are allowed.
3) You must submit a UML 2.5 portfolio that as the main file – a word document where the
different UML diagrams are copied in.
4) You must also submit a SINGLE Enterprise Architect file that contains EIGHT UML 2.5
diagrams you created. Do not submit diagrams another student created because this is a case of student misconduct and will be dealt with according to UQ policies.
[New Version: Effective from 28 Feb 2021]
1
Students per Assignment
The assignment can be submitted as an individual assignment OR done by two students as a group assignment. Note that you must do a peer evaluation when done as a two-student group. For more details refer to the course’ Blackboard site.
Misconduct
It is understandable that students talk with each other regularly and discuss problems and potential solutions. However, it is expected that the submitted assignment is a unique work – all parts of the assignment are to be completed solely by the student(s) indicated on the first page of the assignment. The best practice to avoid misconduct is not to look at another student’s file(s) and not to show your solution to other students. In case where an assignment is perceived to not be a unique work, a loss of marks and other implications can result.
For further information about academic integrity, plagiarism and consequences, please visit
http://ppl.app.uq.edu.au/content/3.60.04- student-integrity-and-misconduct\
DETAILED INFORMATION ABOUT DANDELION CRAFT CIRCLE
In the following, you find details that allow you to create a truthful representation of the business case. You must capture the operation of the crafts circle as it is described here. You cannot fill in gaps or leave information out. If you do so, marks will be deducted.
In the meetings between Patrick and Paula, Patrick explains the digital system he has in mind. This means, he talks Paula through the scope (goals and requirements) of the solution, including how the process of registration of the weekly workshops goes, which data requirements of the digital solution he has, and how the complete lifecycle of a workshop looks like.
Registration Process:
Currently, seniors either call Patrick or send an email inquiring about attending a workshop, which is inefficient and makes it difficult for Patrick to keep a record of seniors’ information as well as restricting the number of attendees for each workshop.
Hence, he wants to have an automated process registration to eliminate any manual work, allowing seniors to register for weekly workshops in advance, and providing him with the ability to better manage capacities for each workshop.
The registration process will be overseen by a workshop head, who is crafts circle’s volunteer, and nominated by his or her fellow volunteers for a one-year term. The workshop head is responsible for updating and maintaining the records of registration, attendance, schedules, and other activities necessary to keep the crafts circle running smoothly.
The Scope of the Project
The following text provides you with the details you need to create the use case diagram. The use case shall present the workshop registration subsystem.
The goal of the digital solution is to automate the process of booking of the weekly crafts workshops. With the digital solution, a workshop head can open new workshops, along with editing information relevant to the workshops. The workshop head can also restrict the capacity
[New Version: Effective from 28 Feb 2021]
2
of each workshop. If a workshop does not have at least three seniors registered two days before the start date of the workshop, the workshop head has the option to cancel the workshop.
For the online booking, there is also a set capacity of 15 seniors per workshop. However, the workshop head or Patrick can change the number up to 20 places, which equals to the room capacity. It would be good if the system sends a notification to the workshop head and Patrick once 15 seniors have booked to allow for manually increasing the number for the ‘in-demand’ workshops. This means the workshop head and Patrick both need access to the system to change the workshop capacity.
Paula cannot believe it when Patrick tells her that some seniors do not show up to the crafts workshop despite having booked in advance. Hence, Patrick is confident that he normally can accommodate all seniors wanting to be creative.
Patrick also wants to set up a registration portal on the crafts circle’s webpage through which seniors can register for the workshops beforehand. Through the registration portal, seniors can log in, view all available workshops, and sign up for their preferred workshops. If they want to keep information about the booked workshop, they have the option to download an iCalendar file, which can be added to their Outlook/Google calendar. At times, seniors would like to cancel certain bookings due to unexpected events, such as sickness or a hospital visit. They can do so by clicking on the ‘Cancel’ button.
Seniors are required to sign up in advance through the ‘Register Now’ feature, but in reality, many do not register and simple ‘walk-in’ on the day of the workshop. Hence, in most weeks there are only less than 10 people booked in. This means that the walk-ins are allowed to attend the workshop. In fact, Patrick or the session head always try to make room for a few more people if their room capacity of 20 is not reached.
When workshop attendees come in, there is a sign-up sheet (paper) on the table next to the bucket for the workshop fee. Attendees are asked to sign and provide their name, the Arts and Crafts membership number, their contact details, and emergency contact details. Patrick would like to remove the paper sheet and put a computer at the entrance table. When a senior person enters the workshop room, Patrick would help this person to find his/her name in the pre- booking sheet or enter the details directly into the digital solution.
After each workshop, the workshop head generates a report to get the list of attendees of the week. Patrick needs to get the report because he needs to inform (every week) Arts and Crafts Queensland about the membership numbers of all attendees. He can also get a printout version if needed.
The weekly workshop fee is 10 Dollars per senior. At the moment, many seniors come to the weekly workshop and pay the fee at the door. Patrick would like them to pay in advance to avoid handling the cash every week. However, Patrick does not want to force payment at the time of the online booking because he is afraid it may negatively impact on the numbers. Hence, the system should give the option of online payment or pay at the door.
When attending a workshop, the seniors need to make sure they are members of Arts and Crafts Queensland to have insurance when attending. Arts and Crafts Queensland is the peak body representing all craft circles across the state of Queensland. They are a not-for-profit membership organization, and all seniors that attend a local craft circle, such as Dandelion Craft Circle, must be current members of Arts and Crafts Queensland.
[New Version: Effective from 28 Feb 2021]
3
Registration Process for Weekly Crafts Workshops
The following text provides you with the details you need to create the activity diagram and the sequence diagram. Both diagrams shall present the booking process for the weekly crafts workshops, however, the activity diagram needs to capture the process, whereas the sequence diagram captures the interactions between the actors [seniors & workshop head] and the system (each).
The process of helping seniors book a workshop at Dandelion Craft Circle starts when the senior goes to the craft circle’s website and there clicks on ‘Register Now’.
First, the system requires verification of the users’ identity by asking them to sign in to a valid account. If the senior is not a registered user, s/he will need to sign up for a new account. To do so, the senior enters personal information, including the age and disabilities, emergency contact, email address, and his/her contact number. After submitting the sign-up form, the senior receives a validation email to complete the sign-up process for the new account. The link contained in the email will expire two days from the date sent. When the senior has an account, s/he simply logs into the system by entering his/her login details, i.e., email address and password.
Once the senior is logged in, s/he can book any upcoming workshops. Initially, Patrick sets the capacity for each workshop to 15 crafts enthusiasts. If 15 people have signed up, any new bookings will be rejected, but the person is added to a waiting list. The workshop head and Patrick will receive a notification (via email and text message) and can increase the number of sign-ups for the workshop manually, either immediately or at a later stage. The increase is only possible to a maximum of 20 places to comply with the venues’ health and safety regulations. Subsequently, more places open up for booking and the seniors on the waitlist will be notified. Once they have confirmed their interest in a particular workshop, they will be automatically signed up for it.
The payment for the weekly workshop works as follows: There are two options for seniors to pay for the workshop – online or at the door. If sign-up is online, the seniors have an option to make the payment via credit card at the end of the booking process or later at the workshop. Once the payment is made via the online system, the system sends a receipt and, meanwhile, records the details of attendees. If the senior does not pay online, s/he will only receive an email with the confirmation of the workshop booking. For these seniors who choose to pay the fee on the workshop day (i.e., at the venue in cash or via credit card), the payment is recorded in the system at the time of payment.
Once a senior has booked a workshop, s/he is free to check out the detailed workshop plan and materials on the webpage. In most cases, attendees would like to get a reminder of the workshop. They can simply do so by clicking on the ‘Save to Calendar’ button on their booking page. In cases of seniors who want to sign up for more workshops, they can repeat the same process to book available workshops.
Data Requirements of the Digital Solution
The following text provides you with the details you need to create the domain class diagram. The diagram shall present the data structure of the entire crafts circle management system (beyond the workshop booking sub-system).
[New Version: Effective from 28 Feb 2021]
4
In the meetings with Patrick, Paula learns about various types of information that the system needs to keep track of, and that are important to different users of the system. Patrick provides her with a list of the essential information that needs to be captured by the system. You find the information in the Excel spreadsheet (see in Blackboard).
To help Paula better understand the information in the spreadsheet, Patrick also provides her with some additional information as below.
Patrick needs to maintain information about each member that is an account holder. In fact, the person who attends each of the workshops is not always the account holder, but can be the senior’s children or a caregiver.
For each senior, Dandelion Craft Circle only allows for a single sign-up for the account. The same rule also applies to the sign-up for a membership at Arts and Crafts Queensland.
Arts and Crafts Queensland offers two types of memberships, namely, Gold Star Membership and Standard Membership. The Gold Star membership provides access to crafts shows and online crafts workshops offered by Arts and Crafts Queensland, and the monthly crafts magazine. For people that hold the Gold Star Membership, Patrick wants to keep a record of who they are and what benefits (name of the benefit, description of the benefit) that are available to them. For those who hold the Standard Membership, he occasionally provides them with special discounts for particular workshops. In such cases, it requires the system to generate discount codes.
Patrick needs to hire a venue for the weekly crafts workshops. Usually, he contacts the owner of the venue in December to renew the lease for the following year. Now and then, their workshop room is not available on specific dates of the year. If this occurs, he would need to look for other venues for temporary use on those days.
Patrick would like to offer multiple crafts activities for each workshop, but also to have regular offerings. He believes that drawing is a great way for elderly people to express their emotions and experience. Indeed, creating a painting requires fewer skills than sewing or knitting and hence, every senior can do it. Hence, Patrick never arranges a workshop without offering either a water or oil painting option.
Patrick usually opens the registration for crafts workshops for an entire year in January. This allows the booking for more than one crafts workshop. Therefore, Patrick relies on the system to keep track of information about bookings, especially details that otherwise cannot be captured in the records of the members and scheduled workshops.
Patrick also wants to restrict the number of registrations for each workshop. If a workshop reaches its predetermined maximum attendance numbers, a waiting list will be open for this particular workshop. Otherwise, the system only generates a list of registration. Patrick worries that if someone accidentally deletes the registration list, the registration will no longer exist. Therefore, he wishes to set up two-factor authentication on the access of the list.
Workshop attendees can make payments online when they book for one or more workshops with vacancies. Alternatively, they are welcome to pay the workshop fees at the venue. For online payments, Patrick would like to capture the type of credit card and the billing address of the payee. For fees that are paid at the venue on the day, he needs to know the type of payment (cash or again via credit card).
[New Version: Effective from 28 Feb 2021]
5
The registration process is handled by the workshop head, who is one of the volunteers at Dandelion Craft Circle. Patrick would like to maintain records of all volunteers’ personal information and their administrative services. Additional information is also important for Patrick to know. Therefore, he wants to record volunteer contracts that include contract ID, the start date and end date of volunteering. Since these are additional information, they are not captured as part of their personal information nor the administrative services they are assigned to. For the workshop head, Patrick is interested in knowing more in-depth information, including their experiences with senior citizens, art background, and actual working hours per day.
The Lifecycle of a Crafts Workshop
The following text provides you with the details you need to create the state machine diagram. The diagram shall represent the different states of a crafts workshop and the transitions between the states.
At Dandelion Craft Circle, each workshop goes through a multiple-phase process to ensure the seniors enjoy the activities but also improve their skills in a certain craft. The lifecycle of a workshop includes several major phases – a planning phase, an online booking phase, a material preparation phase, a table set-up phase, a workshop running phase, and an assessment phase. A workshop head oversees the entire process.
The process starts when Patrick shares via email the evaluative feedback from the previous week with the workshop head. The Workshop head then reaches out to 3 volunteers to work with him or her in the next workshop. These four people form a working group for the week.
In the Planning phase, the workshop head first carefully reviews the feedback and researches about different types of crafts activities, such as sewing activities, painting activities, and woodwork activities. Then, the workshop head drafts a workshop plan laying out the following details: what budget and resources are required, what is important feedback from the last week, and which materials should be used in the week under planning.
Once the workshop plan is drafted, it is shared among the entire working group. The group members review and discuss the proposal, and eventually decide on whether to approve it or not. If the workshop is not approved, it is marked as Rejected and the initial planning process starts again. If the workshop is approved, it is marked as Approved and the workshop head is notified through email.
Once a workshop is approved, the workshop head goes ahead and opens the online booking for the workshop. The workshop is then flagged as open in the system and spots are available to be filled. Every time the system recognizes that 15 seniors have signed up for a workshop, it notifies the workshop head and Patrick who then may release more spots for waitlisted seniors.
From time to time, some seniors may decide to cancel a workshop. As a result, those spots open up and become available for the seniors on the waitlist. Note that bookings close one day prior to each workshop. At that point, if there are less than three seniors registered, the workshop will be canceled and removed from the list.
[New Version: Effective from 28 Feb 2021]
6
The workshop head and the volunteers start preparing different activities, such as cutting out old fabric and pulling buttons from old shirts, special dyes, knitting shapes, for the workshop three days before the workshop.
On the day of the workshop, the workshop head and the volunteers run the workshop together. They open the rented room for the seniors to come in, set up crafts activity stations, lay out crafts materials, and put out healthy snacks for everybody to enjoy. They also explain the crafts activities and the workshop’s housekeeping rules.
A smooth-running workshop is only possible through the efforts of the workshop head and the volunteers. Each workshop is generally a combination of painting and other planned crafts activities, which provide opportunities to create a unique art piece, master certain crafts skills, and emotionally work through experienced events.
Patrick has made it a habit to collect feedback about each workshop from the seniors through emailing them a short questionnaire. It generally takes him two days to receive feedback back from the seniors. The feedback is later entered into the system. After 24 hours of entering the feedback, Patrick carefully reads through the feedback and makes some personal notes that mark the end of one crafts workshop.
After familiarising herself with the business requirements at Dandelion Craft Circle, Paula and you are now required to do THREE tasks:
1) Task 1: Find a name for the digital solution. You must also give the solution a name. Put the name on the cover page of the word file.
2) Task 2: Create five UML models (one for each type) based on the description of business case. Document any assumptions you made (if any) underneath each diagram.
Hint: for state machine diagram, you will need to select the object that is evidently the focus of the case scenario.
3) Task 3: Create three additional UML models based on your understanding of the business case. The three UML models are activity diagram, sequence diagram, and state machine diagram. They must meet the following requirements:
• The Activity Diagram must model a business process that is NOT the ‘Registration
Process for Weekly Crafts Workshops’. You must select another business process that
is captured in another or other use cases of the Use Case Diagram.
• Activity Diagram and Sequence Diagram must depict the same business process.
• For State Machine Diagram, you must select an object that is NOT ‘crafts workshop’,
but an object captured as a different class in the Class Diagram. Once you have selected an object, you need to model a State Machine Diagram which depicts the states of the object (over its lifespan).
UML 2.5 Portfolio
All UML models MUST be created with Enterprise Architect (EA) and each diagram must be
exported as an image and pasted into a Word document that MUST be submitted as well.
The word document needs to include an overview page that must contain a table of contents with meaningful headings. For example, “Activity Diagram” followed by the name of the system. In addition, each diagram may have assumptions underneath only if needed. It is recommendable approximately 200 words (for the whole document) but can be less or more.
[New Version: Effective from 28 Feb 2021]
7
Also, it is desirable the use of bullet points. Furthermore, the word document must have the pages numbered and the diagrams must have a readable font size.
All models MUST be done in UML 2.5. This means it must comply with the tutorial material, and by extension the OMG UML specification version 2.5 or Sparx Systems’ UML recommendations.
Please make sure that you comply with the modelling guidelines as follows:
1) The models must be created with Enterprise Architect.
2) The models must be a truthful representation of the business case. This means you need to
create the diagram using the information provided in the assignment.
3) You must only model the automated part of the digital solutions. This means any manual activities that are not carried out by the system are going to be represented in the UML
models.
4) You must follow appropriate modelling conventions (the rules) that are specified in the
weekly tutorial files.
5) You must clearly capture the relationships between different types of UML models. This
means:
• The Activity Diagram must model the business process that is captured in one or more
use cases of the Use Case Diagram.
• Activity Diagram and Sequence Diagram must depict the same business process.
• The information contained in the Sequence Diagram should match the information
captured in the Class Diagram.
• State Machine Diagram must depict the states of a single object (over its lifespan); this
object is captured as a class in the Class Diagram.
For Task 2 (see p. 7), you must have the following details in each diagram:
N
Diagram Type
Detailed Requirements
1
Use Case Diagram
3 different actors
9 or more top level use cases
3 or more include relationships 4 or more extend relationships
2
Activity Diagram
3 partitions
25 – 30 activities
4 forks
4 joins
4 decision activities
3
Sequence Diagram
1 domain object that interacts with 2 actors in a complex sequence of interactions, including 12 input messages, 13 return values, and 4 self- messages. Parameters/input data must be included along with each input message.
You should also include combined fragments, specifically, 1 loop fragment, 2 opt fragments, and 2 alt fragments.
4
Class Diagram
21 domain classes with multiplicities, attributes, and operations. 3 cases of generalization/specialization relationships
[New Version: Effective from 28 Feb 2021]
8
3 cases of whole-part relationships (i.e., aggregation AND composition)
2 association classes
Please make sure that all information captured in the Class Diagram come from the excel spreadsheet and the case description.
5
State Machine Diagram
1 object, 9 or more major states, 1 composite states, 1 choice pseudo- state, and various transitions with triggers and guard conditions (if required).
You should also include initial state(s) and final state(s).
For Task 3 (see p. 7), you must have the following details in each diagram:
N
Diagram Type
Detailed Requirements
1
Activity Diagram
3 partitions
No less than 20 activities
No less than 2 forks
No less than 2 joins
No less than 3 decision activities
2
Sequence Diagram
1 domain object that interacts with 2 actors in a complex sequence of interactions, including…
1) no less than 10 input messages,
2) no less than 10 return values,
3) no less than 2 self-messages,
4) parameters/input data must be included along with each input
message.
5) combined fragments must be included, specifically, 1 loop
fragment, 2 opt fragments, and 2 alt fragments.
3
State Machine Diagram
1 object, 9 or more major states, 1 composite states, 1 choice pseudo- state, and various transitions with triggers and guard conditions (if required).
You should also include initial state(s) and final state(s).
Submission Process
The assignment must be submitted electronically through Blackboard. Please make sure that your submission includes TWO files:
1) Analysis and design assessment portfolio. This is a word file (not a PDF file).
2) An Enterprise Architect file that corresponds with your word file diagrams.
Export each diagram as an image and paste it in a WORD DOCUMENT and submit the EA FILE used to produce the portfolio. Files submitted as email attachments to teaching staff will not be accepted. Late submission will result in the deduction of marks.
[New Version: Effective from 28 Feb 2021]
9
Before the closing time of the submission, you can submit multiple times. Blackboard displays all submissions and we can see what the latest submission is and will only mark your latest submission. No submissions via email will be accepted.
Submission Date
Submission date: 12 April 2021 at 2:00pm
For each day (including Saturday and Sunday) after the 12 April 2021, the late submission penalties apply based on UQ examination policies until the assignment is submitted.
Consultation
There are two types of UML consultation – open consultation (i.e., drop-in session) and group consultation (i.e., 10-student group). In open consultation, students can spontaneously zoom in and ask questions during the consultation times without making an appointment in advance. For group consultation, however, students must make an appointment online with the tutor running that specific session, and only 10 slots are available for each session. There is no one- on-one consultation.
To ensure fair treatment to all students, tutors will not be allowed to look at your assignment files/works. Questions regarding your assignment will only be answered if they are general in nature, for example on the use of Enterprise Architect or general question on the different model notations.
Extension Application Procedure
A request for extension of the assignment due date will need to be done via the submission of an online application at this link: https://my.uq.edu.au/node/218/0#0
Neither course coordinators nor lecturers can grant assessment extensions to students.
Peer Evaluation
A group of students will get the mark after calculation of the peer evaluation results, also referred to as ‘Group Peer Assessment’. More details can be found at the course’ Blackboard site.
The student group needs to list the names and student numbers of both students at the first page of the assignment.
Each student must undertake the peer evaluation.
Marking Rubric
The project will be graded on its scope, usability, maintainability, consistency, credibility, and suitability in the target organization and style of the project report. You will also be graded as to how well you have followed the analysis and design procedures demonstrated during the course and the quality of the final presentation. For details, please refer to the marking rubric attached to the assignment.
[New Version: Effective from 28 Feb 2021]
10
Each assignment will be marked considering the two following main sections:
1) Correct use of diagrams notation: Each diagram MUST comply with the notation learned in tutorials, in particular UML 2.5. This means it must comply with the tutorial materials, and either the OMG UML specification version 2.5 or Sparx Systems’ UML recommendations. Although other notation conventions exist, only the one taught in the tutorials is considered correct for marking purposes.
2) Correct logic and consistency with the business case: Logic means that each diagram correctly represents the case description. The diagrams CANNOT include other information not given to you. There is no need to make assumptions. If you feel you need to make assumptions you most likely have not understood the case description correctly. It is recommended to see a tutor in person during consultation times.
Zero marks for the assignment will be given if the student does not use Enterprise Architect for the creation of the diagrams.
[New Version: Effective from 28 Feb 2021]
11
Marking Rubric Total Marks: 40 marks – Penalty per day late will be applied
Criteria
Developing Competency 0% – 50%
Adequate Competency 50% – 80%
High Level Competency 80% – 100%
UML Models – Notation Correctness
18 marks
Demonstrates a poor understanding of UML modelling notations and conventions. Most labeling of UML model elements are not in line with tutorial knowledge. Many errors exist in solution.
Demonstrates an adequate understanding of UML modelling notations and conventions in line with tutorial knowledge. Some errors exist in labeling UML model elements.
Demonstrates a good understanding of UML modelling notations and conventions in line with tutorial knowledge. Few or no errors exist in labeling UML model elements.
UML Models – Logical Correctness
18 marks
Most UML models do not precisely or comprehensively represent the business case. Many semantic errors exist in the solution. Relationships among different types of models are poorly captured or ambiguously expressed.
Some UML models do not precisely or comprehensively represent the business case. Some semantic errors exist in the solution. Relationships among different types of models are captured but only partially correct.
All UML models precisely, consistently, and comprehensively represent the business case. Few or no semantic errors exist in the solution. Relationships among different types of models are accurately and sufficiently captured.
Layout Report
9 marks
Numerous issues exist with respect to presentational quality of EA diagrams and report formatting.
A few issues exist with respect to presentational quality of EA diagrams and report formatting.
High presentational quality EA diagrams with professionally and consistently formatted report.
Marks are deducted based on the number of issues listed:
1) A cover page is not included.
2) Pages are not numbered.
3) Overview page is not included and there is no table of contents.
4) Solution is not split into logical sections and headings are not
meaningful.
5) The word limit does not comply with the requirements.
6) Words and/or elements are not readable in the diagrams / font size is
too small.
[New Version: Effective from 28 Feb 2021]
12
Good luck with the assignment!
Student Notes
[New Version: Effective from 28 Feb 2021]
13