School of Business IT and Logistics
Course/Unit code Assignment Assignment Group/Session name (if applicable)
number due date
ISYS2128 2 12/142024
Course/Unit name Program title
Digital Business Design and Innovation Report
Lecturer/Teacher’s name Wordcount
Chi Pham
This statement should be completed and signed by the student(s) participating in the preparation
of the assignment.
Declaration and statement of authorship:
1. I/we hold a copy of this assignment, which can be produced if the original is
lost/damaged.
2. This assignment is my/our original work and no part of it has been copied from any other
student’s work or from any other source except where due acknowledgment is made.
3. No part of this assignment has been written for me/us by any other person except where
such collaboration has been authorized by the lecturer/teacher concerned and is
acknowledged in the assignment.
4. I/we have not previously submitted or am currently submitting this work for any other
course/unit.
5. This work may be reproduced and/or communicated to detect plagiarism.
6. I/we permit a copy of my/our marked work to be retained by the school for review by
external examiners.
7. I/we understand that plagiarism is the presentation of the work, idea, or creation of
another person as though it is your own. It is a form of cheating and is a very serious
academic offense that may lead to expulsion from the University. Plagiarized material can
be drawn from, and presented in, written, graphic and visual form, including electronic
data, and oral presentations. Plagiarism occurs when the origin of the material used is not
appropriately cited.
8. Enabling plagiarism is the act of assisting or allowing another person to plagiarize or
copy your work.
Family name Given name Student number Student signature Date
Tran Le Gia Thong S3836262 Thong 12/14/2024
Further information relating to the penalties for plagiarism, which range from a notation on your
student file to expulsion from the University, is contained in Regulation 6.1.1 ‘Student
Discipline’ www.rmit.edu.au/browse;ID=11jgnnjgg70y and Academic Policy: ‘Plagiarism’
www.rmit.edu.au/browse;ID=sg4yfqzod48g1.
School date
Assessor’s comments Grade
stamp
(Office use
only)
Abbreviation
QA Quality Assurance
UI User interface
UX User Experience
IT Information Technology
I. Rich picture
Figure 1. BookMe rich picture with 3 problems including outdated user interface of system,
inventory management, and order visibility.
II. Use Case diagram
Figure 2. The use case diagram of new system to solve 3 BookMe problems
III. Project scope checklist
Project: Enhance BookMe system
Project Goal(s)/Objective(s) Overall Objective: Within a $300,000
budget, improve the BookMe system by
Overall goal (what, when, how much)
May 31, 2025.
Key objectives:
Improving the user experience
(account management, shopping
cart, reviews) is one of the main
goals.
Facilitate supply chain tracking and
inventory management in real time.
Give store managers access to
analytics tools.
Make sure the system is scalable and
secure.
Deliverables Key outputs include:
Major expected outputs User Account Management: creating
and managing profiles on social
media and logging in.
Enhancements to the shopping cart,
wishlist, and search are examples of
product interaction features.
Order management includes order
updates and purchase histories.
Reviews and Feedback: Systems for
reviews and comments.
Inventory & Supply Chain: Tools for
inventory modification, order
tracking, and real-time stock
updates.
Reporting: Managers' inventory
reports.
Milestones Important Occurrences:
Natural and significant project events
January 1, 2025: The start of the
project.
February 7, 2025: Features for user
accounts are finished.
Product interactivity features will be
delivered on February 28, 2025.
Deployment of the order
management system on March 15,
2025.
Inventory and supply chain features
are finished as of April 30, 2025.
Final testing and rollout on May 31,
2025.
Technical Requirements Assurance of Performance:
– to assure performance
Scalability: Able to accommodate
10,000 users at once.
Data security measures include
GDPR/CCPA compliance and end-
to-end encryption.
System Integration: Notifications,
stock updates, and login APIs.
Real-time inventory updates (less
than one second) and page load
times (less than three seconds) are
benchmarks.
Cross-Platform Compatibility:
Support for both desktop and mobile
devices.
Limits and Exclusions To Prevent Inaccurate Expectations:
– to avoid false expectations Customer loyalty programs and
physical store operations (including
payroll) are outside of our purview.
Dependencies on third parties: lack
of control over the functionality of
third-party services (like social
media APIs)
Geographic Restrictions: Only
domestic operations are able to
follow the supply chain.
Review with stakeholders To Get Better If Necessary:
– to improve if needed
Monthly Reviews: Management and
department heads receive progress
reports.
Biweekly Updates: Working
together with the UX/UI and
development teams.
User Testing: In March 2025, store
managers and customers will test.
Final evaluation: Prior to the
implementation in May 2025, a
performance evaluation with
stakeholders is conducted.
Table 1. Project scope check list of enhance BookMe system
IV. Work Breakdown Structure
Figure 3. Work Breakdown Struture of the BookMe new system
V. Gantt chart
Figure 4. The Gantt chart for the enhance of BookMe new system
