1 | P a g e

BISM7255 Business Information Systems Analysis and
Design
Individual Project
PART One
ASSESSMENT WEIGHTING: 40%
DUE DATE and TIME: 14 September 2021 AT 14:00
(AEST)
Overview

The Project requires you to design and create a business information system application (app)
for a retail business to be used to solve major accessibility issues, in particular for people with
a vision impairment. Further, it will support the sustainable development goal (SDG) 10 and
the subgoal 10.2:
“By 2030, empower and promote the social, economic and political inclusion of all, irrespective
of age, sex, disability, race, ethnicity, origin, religion or economic or other status “.
A fact sheet on vision impairment is available from the World Health Organisation.
Blindness and vision impairment (who.int)
We will also have a seminar guest speaker in August to further assist with the requirements.
The app will be tested by at least one user. A showcase will be held in Week 13 to facilitate
user testing. A reflection written on future possibilities for yourself and the project.

The project is divided into two parts. The first part will concentrate on planning and analysis.
The second part will be design and evaluation, which includes using reflective learning. The
details for the second part are in a separate document.

The Project Part 1 may be completed individually or as a pair. For Part 2, it must be completed
as an individual, as you as an individual are being assessed against the learning objectives.
Among all the assignments submitted, there should be no ideas or applications/prototypes that
solve the same problem in the same way. Although projects completed as a pair in Part 1 will
share some commonalities due to the first submission, they are to have a distinct design.

The overall idea is to simulate a small system or part of a larger system (a slice) that what
would be required to address the topic (paragraph one) for a business.
The ultimate aim of the Project is for you to gain first-hand experience in systems analysis and
design by actually becoming the actor/s under examination, and then reflecting upon the totality
of your experience. As such, students will examine, experience, and reflect upon many things
from many angles with respect to a central topic – a set of activities that if performed well sets
the foundations for becoming an Analyst-Designer.
Furthermore, as this is specifically an Information Systems course, the business idea and app
should include novel approaches to gathering, analysing, and producing information, the result
2 | P a g e

of which should lead to specific actions based on these insights. At the same time your
foundation knowledge and skills need to be solid. Therefore, the project will be undertaken
using a prescribed methodology.
It is expected that students in the course talk about the Project with each other, and even discuss
their potential solutions particularly in class. However, the final Project is a unique collection
of ideas, diagrams, solutions, experiences, and personal reflections and, as such, the final
product MUST be completed solely by each student. The exception to this is for Part 1 and then
only one project is submitted and unique. 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. Further, text book,
websites or other sources use must be limited to ideas and acknowledged. In case where an
assignment is perceived to not be a unique work, a loss of marks and other implications can
result. If a student is unsure about the degree of similarity among projects, he or she should
discuss this issue with the lecturer during office hours. There are also many retail management
solutions available online and in textbooks. However, what is being requested is not a standard
solution. Further, tutors will be monitoring progress during semester. For further
information about academic integrity and plagiarism and the consequences, please visit
http://ppl.app.uq.edu.au/content/3.60.04-student-integrity-and-misconduct

Project Signposts

The Project will start in the first week and run for the length of the course. Since the idea of the
Project is to continuously build out the System and refine it, with new instructions and
challenges each week until completion, the following represents a weekly overview of what is
required. Specifics for each week will be presented classes. This means that this document only
serves as a guide or roadmap for the Project, so that students know generally what is coming
at different points, which also allows those students who like to plan and tinker beforehand to
do so. However, this also means that coming to seminars and practicals is absolutely vital
to better outcomes from the course. However, it is understood that there may be students that
will find this difficult under the current pandemic. Should you miss a session or if for a reason
that would be approved for an extension, please email the lecturer before the next session for
advice on how to proceed. If this is going to be a regular occurrence please let the course
coordinator know as soon as possible so that appropriate arrangements can be put in place.
The entire Project process will basically be as follows:
Decide if doing the project part 1 individually or as a pair (secure a partner)=> create
long-term system vision => plan the project for the semester => investigate
requirements => create information system concept using EA for diagramming
(complete one type a week to stay on track) => collate and submit diagrams and
business case => Part 2 develop low code app for the system using Mendix => test the
system with users => gather feedback and refine system => redesign accordingly =>
reflect on future of system analysis and design and its possibilities as well as your own
(including when we work as part of a group).



3 | P a g e

An important decision (complete by the end of Week 1)

To work individually or as a pair

This is an important decision. There are risks both ways. These will be discussed in the first
seminar. Two of the major risks of working as a pair are: first, that your partner decides to
withdraw from the course or wishes to complete part one alone and secondly, the peer
evaluation (see separate section).

If a partner withdraws then the remaining partner will need to complete the work alone,
unless this occurs in the first couple of weeks and there is time to form a new partnership.

Where a partner wishes to work alone, this may occur but the work completed as a pair must
be clearly indicated on the submission and if not, then the work in common that was not
clearly identified will receive zero marks.

Please consider the risks carefully as when entering into a partnership (pair), you will be
accepting these risks.

Please register your partnership. Instructions will be given on Blackboard.


Part One Details

Case Scenario with scope
You have been approached by a home furnishing store to improve their retail management
system, specifically their online store. They have received customer feedback that their online
store is not user friendly and has been rated as having very poor accessibility for visually
impaired customers. You have been contracted to provide initial ideas on how to improve the
online store to improve the accessibility for visually impaired customers. A report is to be
submitted containing an initial business case and a set of UML diagrams of the requirements
for the improved online store. The following details have been provided as a starting point
and have been divided into three sections to help you create initial diagrams. Please review in
entirety to ensure consistency as you progress through your diagrams and their iterations.

The use case diagram is to show the online store subsystem. This system links to the other
parts of the retail management system. However, for simplicity of the project there will be
some duplication of functions and data that would be contained in the main system. What is
not to be duplicated is a full accounting or human resource management system functions.
For example, staff will not be rostered or paid in this system. Only some staff details will be
kept. Further, while order details will include amounts and payments, it may be assumed that
the finer accounting details would be catered for in the accounting system. Also, there is a
fleet management system for the delivery vans.

After a customer logs into the system, the current system has a menu and products are shown
that the system believes the customer will be interested in based on past orders and any
4 | P a g e

products that the customer has flagged to kept as a wish list. From the menu a customer can
update their profile, browse products, resume shopping if a shopping cart is active, place an
order, check the status of current orders, contact the store for assistance via chat during the
physical store opening hours, send an email at any time, and arrange for a new attempt for a
failed delivery or arrange a return of a product. The main page also has links to about us,
privacy policy and other useful information. There is also a service to help with home décor
and links to décor consultants who can be booked. These consultants are complimentary or
may have a nominal fee that is refunded on an order confirmation.

A staff member is allocated to oversee an order and ensure that the order is completed. This is
usually after a payment is confirmed, but can be sooner where a customer as requested
assistance or is through a décor consultant. A staff members’ menu includes seeing all
purchase orders plus past completed orders. They can also see notes for a customer and/or
orders. Customers do not see which staff members have been allocated to their order. Staff
members with supervisory responsibilities can see further details and can allocate staff
members to an order. There are different types of staff: décor consultants, customer relations
staff (who also oversee an order), pickup point staff, warehouse staff and delivery staff.

The home furnishing store is looking to you to suggest accessibility improvements. A few
ideas have been flagged as can be seen under the Case Data Requirements section.


A Typical Purchase Order

The following details will help you with an initial version of your first activity and system
sequence diagrams. The second diagram for each of these is to be the addition of accessibility
requirements. There will be the call to this new use case on the initial diagram, but there is
also most likely to be other changes to your initial version of the first use case diagram. As
the purchase order is also typically a focus object in a system, you will also find that this
section may assist you in selecting the object for your state machine diagram. Although it is
not mandatory that it be purchase order and you may select another object. Remember the
final diagrams must show the accessibility requirements, they are not just what is contained
in this text.

Currently a typical purchase order occurs after a customer has browsed and selected products
to be added to the shopping cart. For each product, there may be variables that need to
entered by the customer before the exact product can be added to the cart. These variables
include, but are not limited to: size, colour, quantity, gift, for pickup or delivery (some are
mandatory delivery).

Customers can request assistance via online chat or by telephoning during store opening
hours.

Once the customer has finished selecting the products then name and billing details are
confirmed. After which, delivery details are entered for new customers or confirmed for
existing for each product to be delivered. The customer can select the same for all. If pickup
5 | P a g e

then the customer is informed that they will be sent a text message when the order is ready to
be collected.

When a customer is ready to pay, vouchers and sale deductions are applied, then any delivery
fees are calculated before a customer nominates the payment method for any remaining
balances such as credit and debit cards and online payment methods such as Paypal, The
customer confirms they have read and agreed to the purchase order. The payment is then
processed. The customer is given an order number and sent an email containing a copy of the
purchase order.

From here, behind the scene for the customer, a staff member to oversee the order is allocated
as described previously. Warehouse staff are alerted to picking requirements and then once
processed, the order is then passed to the delivery staff to organise the delivery or take to the
pickup point. At each stage the customer can see how the order is progressing.


Case Data Requirements

The following text is to aid you with identifying the data requirements so that you can create
the domain model class diagram. A full retail management system would require more
classes. However, the data you are to consider is for the online retail system with the new
accessibility features.

The current system stores details about a customer and their preferences. It stores the
following as mandatory unless identified otherwise: account number (system allocated),
name (first name, last name with an option of storing a title), billing address, contact
telephone numbers (one mandatory), email address, password and security questions with
answers.

Remember that previously is was stated that a customer logs into the system and is shown
products the system believes the customer will be interested in based on past orders and any
products that the customer has flagged to kept as a wish list. All products have a product
number, product name, product description, brand, supplier (not displayed to a customer),
product category, product price, quantity on hand, product size and weight, assembly
requirements, images, delivery advice (can be collected or can/must be delivered using 1
person or 2 person store delivery van).

Customers browse the products usually by category or room type. Customer can add a
product to the shopping cart or to their wish list. The wish list keeps the date that product was
added and if a product is no longer available will let the customer know and suggest an
alternative product.

A shopping cart endures until a customer orders or removes the content from the cart. The
products are not considered sold and removed from a further sale until the customers payment
is approved.

6 | P a g e

A customer can select to pickup for the majority of products. Although some products must
be delivered. An order can have a mixture of pickup and delivery. Further, delivery address
may be different for each item. This caters for some items being identified as gifts. If there is
a different address then a different person can be identified to sign for a delivery. Delivery
notes are kept for all deliveries along with the date and time of delivery or failed delivery
where an order could not be safely left or there was no permission given to leave the order.
Failed deliveries have to be rescheduled in consultation with the customer.

When a customer is ready to pay, vouchers and sale deductions are applied, then any delivery
fees are calculated before a customer nominates the payment method for any remaining
balances such as credit and debit cards and online payment methods such as Paypal,

Customer do have the right to return a product with or without return delivery fees. Defective
products are not charged a return fee once a defect is verified.

To these current data requirements, it has been identified that additional information needs to
be stored to assist with accessibility. However, you will find that you will have additional
data requirements. It has been identified that storing some information about the accessibility
requirements for a customer as part of their profile would help support the customer and not
need them to re-enter their preferences. However, it is also recognised that not all customers
would like these kept. Privacy matters to the company. Customers may also have very precise
delivery requirements. Items placed in the incorrect place could become a hazard for a
visually impaired person.



Part One Tasks

After familiarising yourself with the business requirements you are now required to do
THREE tasks with tasks 2 and 3 being iterative until there is a reasonable level of
consistency:
1) Task 1: Find a name for the business and the online system. Put the name on the cover
page of the word file and on the Use Case Diagram that you will create.
2) Task 2: create the initial Business Case: this will include a system vision with problem
description, systems capabilities and business benefits plus the proposed improvements.
3) Task 3: Create the UML diagrams (see final submission content) based on the description
of business case and the. 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.








7 | P a g e


Part One Final Submission Content

Complete an initial Business Case ready for submission. It is being called an initial case as it
will not contain a feasibility report such as Cost Benefit Statement or Project Plan.
The Business Case must have a professional presentation. Use the following format &
presentation: ? Times New Roman ? Size 12 font ? 1.5 line spacing ? Left aligned ? Normal
margins (2.54 cm) ? Number all pages. The content must appear in the following order:
Cover Page
Table of contents
1. System Vision
Problem Description (up to 1 page with supporting citations)
System Capabilities (up to 1 page high level capabilities)
Business Benefits (up to 1 page)
2. Proposed Improvements from the current system to meet the major accessibility
and sustainability requirements. (two pages)

Reference List (APA or Harvard Style)
Appendices (make sure each diagram is clearly labelled with its name and not simply
a type label):
Use Enterprise Architect to draw the diagrams. The diagrams must have a readable font
size and not require the marker to tilt their head to mark.
Export each diagram as an image and paste it in to the Business Case WORD
DOCUMENT and submit the EA PROJECT FILE used to produce the portfolio.
IMPORTANT: You are allowed to use Enterprise Architect as part of a University
agreement. Set up and testing to completed by the end of Week 1. This is a student
responsibility and failure to ensure access will not be taken as grounds not to use
Enterprise Architect without watermarks. More on this during classes.
a. One Use Case Diagram
b. One Use Case Description (select one of the main/top level use cases from
your use case diagram) Must not be for non-functional requirement such as
login or for signup.
c. Two Activity Diagrams of the above Use Case Description (the top level use
case activity diagram and one of the include/extend use cases that is executed
by the submitted top level activity diagram)
d. Two Systems Sequence Diagrams (as for the activity diagram)
e. One Domain Model Class Diagram
f. Statechart/State Machine Diagram (one object only that is a class from the
domain model class diagram)
8 | P a g e


Submission

The assignment must be submitted electronically through Blackboard. Files submitted as email
attachments will not be accepted. Late submission will result in the reduction of marks. The
business case file must be submitted through Turnitin. Detailed submission instructions and the
links will be provided closer to the due date. The EA project file will be submitted as a backup
for the diagrams in the business case and as proof of completion of the work in EA.

Peer Evaluation

Where Part 1 has been completed by a pair of students, they will receive the marks after the
calculation of the peer evaluation results, also referred to as ‘Group Peer Assessment’. More
details can be found at the course’s Blackboard site. A short survey that is administered
centrally will be made available for you to confidentially submit your evaluation of each other’s
contribution and your own work. Evidence will be requested for your evaluation.
Due date and time is same as for the Project Part 1. There can be no late submissions given the
way the survey is run.
The peer results will be used to leave the marks gained as is when both students agree that they
contributed equally or as a deduction from the marks gained where students have requested this
be done. This could be up to a 5% deduction. Negotiations will not be entered into and this is
a risk of doing the project as a pair. In the event that both students do not submit an evaluation
by the due date, it will be assumed that the students were in agreement and there will be no
deduction. In the event of only one student’s evaluation being submitted then this evaluation
will decide the deduction. Please note, do not ask the course staff what the other student
submitted as this will not happen.
Please note: larger deductions will be made where one of the group as emailed the course co-
ordinator during the project and the course coordinator is satisfied through investigation that
the other student has not contributed or has contributed little. Students will receive a warning
that this will be the outcome. Issues must be raised before the last week the project is due and
will not be accepted in the last week or after submission.

Marking Rubric

The project will be graded on its scope, usability, maintainability, consistency, credibility, and
suitability toward solving the topic as outlined in this document, how well project pieces
are linked and integrated, as well as the quality. This is evidenced by how well the student
ties together all of the required outputs. The student will also be graded as to how well they
have followed the analysis and design procedures demonstrated during the course and the
quality of the final presentation of the work. For details, refer to the marking rubric on
Blackboard.
You will be marked considering the two following main sections:
9 | P a g e

? Correct use of diagrams notation: Each diagram MUST comply with the notation taught
in the course. Although other notation conventions exist, it is considered correct the one
used in practical and written in the practical material.
Note: All models MUST be completed in UML 2.5. This means it must comply with the
course material, and either the OMG UML specification version 2.5 or Sparx Systems’
UML recommendations.
? Correct logic and consistency with the business case: Apply a consistent logic to solve the
required topic is essential. Logic means that each assumption made and what each diagram
describe MUST be considered in all the diagrams as the purpose of the assignment is solve
the topic as outlined previously in this document. For example, if the solution includes the
implementation of a new way of tracking orders, the diagrams CANNOT include other
conceptions that can contradict this solution.

Consultation

To ensure that equal and sufficient amount of time is allocated to every student, the average
consultation time (during busy consultation periods) will be limited to 10 minutes per student.
However, in circumstances when there are no other students are waiting, a longer consultation
time is possible. Similarly, to ensure fair treatment to all students, tutors will not be giving
step-by-step guidance on your Project files/works and/or do the Project for you – your Project
is YOUR Project, and YOU are ultimately responsible, not someone else.
Questions regarding your assignment will only be answered if they are general in nature.
Advisory points will be identified and will be announced on Blackboard. You must come
prepared to advice points for feedback to be given. This will be further detailed prior to
advice points. The time available will be limited to ensure all students requesting advice are
seen. As these are advisory extensions will not be available unless there are exceptional
circumstances.

Extension Application Procedure

Requests for extension of the assignment are to be submitted as per the ECP. Please also refer
to the Faculty’s late assignment policy. Neither course coordinators nor lecturers can grant
assessment extensions to students.

Submission Date

Submission date: 14 September 2021 at 14:00 (AEST)

If you do not have an approved extension the deductions as outlined in the ECP will be applied.