COMP5510: Systems Analysis and Design Assessment 2: Systems Design and Implementation Proposal

University of Southern Queensland

Faculty of Business, Education, Law and Arts

School of Business

COMP5510: Systems Analysis and Design Assessment 2: Systems Design and Implementation Proposal

OVERALL ASSESSMENT WEIGHTING: 30%

Learning Objectives The combined objective of Assessments 1 and 2 is for students to acquire a comprehensive overview of the principles, methods, and techniques of systems development. Students will gain practical experience from a development project utilising a specific, contemporary development methodology.

On successful completion of this assignment, students will be ablell to:

• Define, explain, and justify the fundamental concepts, methods, and techniques used in information systems analysis and design.
• Apply contemporary information systems analysis and design methods and techniques to a realistic business case study.
• Develop and communicate effective systems analysis and design solutions for real-world business problems.

Introduction and Background “CycleSphere Brisbane” (hereafter referred to as CSB) is a specialist bicycle shop co-founded in 2015 by Sarah Jenkins and Mike Chen. CSB operates a retail storefront and an integrated repair workshop.

The business has three primary revenue streams:

1. Retail Sales: High-end, off-the-shelf bicycles, parts, and accessories.
2. Workshop: Servicing, repairs, and custom wheel building.
3. Custom Builds: Bespoke bicycle design and assembly, a high-margin but complex process.

CSB employs two full-time mechanics, one part-time sales assistant, and the two owners (Sarah manages retail and custom builds; Mike manages the workshop and inventory).

Following your “AS-IS” analysis in Assessment 1, you have identified significant operational inefficiencies. The current “system” relies on a combination of spreadsheets, a shared digital calendar, and paper-based records.

Key problems identified include:

• Workshop Scheduling: The digital calendar is frequently double-booked or incorrectly updated, leading to customer conflicts and mechanic downtime.
• Inventory Management: The retail system and workshop inventory are not linked. Mechanics often have to physically check stock for a repair, interrupting workflow. Parts “cannibalised” from retail stock for urgent repairs are not always documented, leading to stock discrepancies.
• Custom Build Tracking: Custom builds are managed via email and a paper folder for each client. This makes tracking build status, component orders, and customer change requests extremely difficult.

Your team has been engaged to design the “TO-BE” system to resolve these issues and provide a platform for future growth (e.g., integrating online tour bookings).

---

ASSIGNMENT DELIVERABLES

Structure your final report according to the deliverables listed below. Ensure you consult the detailed rubric on the COMP5510 StudyDesk for specific marking criteria.

1. Project Management Plan

Develop a comprehensive Work Breakdown Structure (WBS) for the entire project, from your current (post-analysis) phase through to final system delivery and handover. The WBS must reflect a standard system development lifecycle (e.g., Planning, Analysis, Design, Implementation, Testing, Deployment).

• Identify all major tasks and sub-tasks.
• Assign responsibilities (you may use generic roles like ‘Lead Analyst’, ‘Developer’, ‘Tester’).
• Estimate duration, start times, and finish times for each task. A Gantt chart is recommended to visualise the timeline.

2. “TO-BE” Process Model

Develop a detailed “TO-BE” process diagram using either Business Process Modelling Notation (BPMN) or Unified Modelling Language (UML) Activity Diagrams. This model must illustrate the improved, integrated workflow for CSB.

The model must clearly depict the processes for:

• Integrated Workshop Booking: From initial customer query (phone, online, or in-person) to job card creation, parts allocation, and job completion.
• Inventory Management: How parts are “reserved” for a specific workshop job or custom build, and how stock levels are automatically updated on “use” by mechanics or “sale” by retail staff.
• Custom Build Workflow: A new process tracking the build from initial customer consultation and quote, through component ordering, build stages, and final handover.
• Reporting: Show processes that generate key reports (e.g., monthly workshop profitability, inventory re-order levels, custom build status).

3. “AS-IS” vs. “TO-BE” Comparison and Change Management

Provide a professional analysis comparing the “AS-IS” process (from Assessment 1) with your proposed “TO-BE” model.

• Identify the specific changes to business processes, staff roles, and data requirements.
• Write a briefing note (memo) for the owners, Sarah and Mike, who will act as change managers.
• This note must clearly explain the anticipated impacts of the new system (e.g., new skills required, changes to daily routines) and recommend specific strategies to manage employee resistance and ensure smooth adoption.

4. Entity Relationship Diagram (ERD)

Draw a conceptual or logical Entity Relationship Diagram (ERD) for the new CSB system.

• The ERD must show all required entities (e.g., Customer, Bicycle, WorkshopJob, Employee, Component, Sale, CustomBuild).
• Clearly identify all attributes for each entity.
• Specify primary keys (PK) and foreign keys (FK) for all entities.
• Illustrate all relationships between entities, including correct cardinality (e.g., 1:1, 1:M, M:N) and optionality.

5. Data Normalisation

Using the entities and attributes identified in your ERD, create a normalised data structure.

• Present the data structure in textual format (e.g., CUSTOMER(CustID [PK], FirstName, LastName, Phone)).
• Ensure all tables are normalised to the Third Normal Form (3NF).
• Briefly justify why your structure meets 3NF, identifying and resolving any transitive dependencies.

6. Testing Strategy

Outline a comprehensive testing plan for the new CSB system.

• Describe the different types of testing you will perform (e.g., Unit, Integration, System, User Acceptance Testing).
• For each testing type, explain what will be tested (e.g., “Integration testing will verify that a new workshop booking correctly reserves parts from the inventory module”).
• Describe the types of test data required (e.g., valid data, invalid/boundary data, high-volume data).

7. Training Plan

Identify the specific user groups at CSB who require training on the new system.

• User Groups: (e.g., Owners, Mechanics, Sales Assistant).
• For each group, describe the recommended training method (e.g., one-on-one, group workshop, video tutorials).
• List the specific topics that must be covered for each group (e.g., “Mechanics must be trained on how to use the tablet interface to log parts used in a job”).

8. System Changeover

Develop a detailed plan for system changeover.

• Discuss the potential changeover methods (e.g., Direct Cutover, Parallel, Phased, Pilot).
• Recommend one method for CSB and provide a strong justification for your choice, explaining why it is the best fit for this specific business (considering risks, costs, and operational disruption).
• Outline the key steps and timeline for your recommended changeover.

9. Report to Top Management

Write a formal report (executive summary style) to the owners of CSB, Sarah and Mike.

• Assume the design and implementation phases are complete.
• The report must summarise the project’s original objectives, the processes undertaken, the scope of the new system, and its key benefits.
• Conclude with clear recommendations for the post-implementation phase (e.g., ongoing support, future modules to consider).

10. Report Structure and Referencing

Your submission must be a single, professional report.

• Structure: Must include a Cover Page, Abstract, Table of Contents, Introduction, the main body (addressing items 1-9 above), Conclusion, and a Reference List.
• Referencing: All sources cited must be listed in a single, alphabetical list at the end. Use the Harvard Referencing System.

---

SUBMISSION REQUIREMENTS

• Submit a single file (Word or PDF) via the COMP5510 StudyDesk submission link.
• You may use software such as Microsoft Project, Visio, or free alternatives (e.g., diagrams.net) to create your WBS, BPMN, and ERD. These diagrams must be embedded within your single report file.
• Late submission penalties will apply as per university policy (5% reduction per business day, capped at 10 days).

Suggested Learning Resources

Al-Ma’aitah, D.M.A. 2020. ‘The impact of the change management on the systems development life cycle (SDLC) in the IT projects’. International Journal of Computer Applications, 174(38), pp.39-43.

Balc, A. 2022. ‘Data modeling and database design: concepts and practical approach’. International Journal of Computer and Information Technology, 11(1), pp.1-9.

Di Francescomarino, C., Ghidini, C., Maggi, F.M. and R-Moreno, M.D. 2019. ‘An abstract syntax for BPMN: a case for formal and practical usability’. Software & Systems Modeling, 18, pp.2375-2407.

Kerzner, H. 2021. Project management: a systems approach to planning, scheduling, and controlling. 13th ed. Hoboken, NJ: John Wiley & Sons.

CIS5200
ASSIGNMENT 2
OVERALL ASSESSMENT WEIGHTING: 20%
The overall objective, of assignments 1 and 2 combined, is that the students should acquire an overview of principles, methods and techniques of systems development, and gather experience from a development project in which a specific development method is used. On successful completion of this assignment students should be able to:
• Define and explain the fundamental concepts methods and techniques used in information systems analysis and design.
• Apply contemporary information systems analysis and design methods and techniques to a realistic case study.
• Effectively communicate systems analysis and design methods and techniques to real world problems.
Introduction and Background
Early in 2010, Mr Pavlov and Mrs Norris established a boarding kennel for cats and dogs (hereafter referred to as Pampered Pets Palace or PPP) in the Western suburbs of Brisbane. The kennel operates 7 days a week. The kennel capacity is as follows: 50 cat runs, 100 single-dog dog runs and 25 two-dog dog runs. The kennel has also recently completed 30 luxury units (20 for dogs and 10 for cats). In addition to simply providing board for animals, PPP, also provides additional services such as grooming, flea treatments etc. The kennel employs a number of staff in a variety of operations. Both owners are also actively involved in the day to day operations. There is a fulltime receptionist/office worker, Phyllis, and a number of kennel hands.
Now you have interviewed the Pampered Pets team, and you and have established their requirements for the TO-BE system to address the problems of no-show bookings, unavailability of pet accommodation and services not being provided. You may also provide the Pampered Pets team with some additional reports.
The sections below as the same as you will find on StudyDesk, and they are the deliverables you will be marked on. Please pay particular attention to the Assignment Details, Instructions, and Rubric available via the CIS5200 StudyDesk
Pampered Pets Palace – Time Management plan
Develop a Work Breakdown Structure (WBS) for the entire project through to delivery and, as you did in assignment 1 identify all the tasks to be undertaken, who will do them, and their start and finish times. This time your WBS will reflect a typical system development lifecycle including tasks around planning analysis design and implementation.
TO-BE Process
Develop a “TO BE” process diagram by using Business Process Modelling Notation (BPMN) or Unified Modelling Language (UML). The “TO BE” diagram should show the improvement of the process flow the organisation. Take into account:
• Customer information (owner and pet)
• Bookings made
• Payments
• Any other data entry/input processes you consider necessary.
• Reporting, including
o Invoices
o Sales Summaries
o Any other reports you consider necessary that could be valuable to the owners
Comparing “AS IS” and “TO BE” Process
You need to make a professional comparison between the “AS IS” process diagram that you provided in the assignment 1, and “TO BE” process diagram to assess the impact of change and prepare a briefing note for Mrs Norris, who has taken on the role of change manager, regarding the anticipated impact of the system. You should make recommendations to the management of PPP on how these impacts can be managed.
Entity Relationship Diagram (ERD)
Draw and ERD for PPP showing all the entities and their attributes, identifying keys, and relationships including cardinality as described in Module 9 and its associated readings
Data Normalisation
Using all the entities identified in your ERD, create a normalised data structure (to 3rd Normal form as described in Module 9 and its associated readings) for PPP that will ultimately form a relational database to store the company data.
Testing
What types of testing should be performed? What types of test data should be used? The testing in relation to the new Information Systems developed to automate the organization process? Please clarify this.
Training
Identify the specific groups of people who need training on the new system. For each group, describe the type of training you would recommend and list the topics you would cover.
System Changeover
Develop a plan for system changeover for the organisation. Discuss the method that should be used for systems changeover to enable “TO BE” process in the organisation.
Report to Top Management
Assume you have completed the design and implementation phases of your project for the organisation. Write a report to the top management (CEO). This report at a minimum should include the objectives, processes undertaken, scope, and recommendations to the top management (CEO).
Presentation/Report Structure
This task includes providing a cover page (title page) for your report and writing up your report details with clarity and professionalism.
References
All documents cited in your assignment must be listed in a single alphabetical list at the end of the assignment. The following USQ Library Resources to assist you with referencing correctly using the Harvard Referencing System: https://www.usq.edu.au/library/referencing/harvard-agps-referencing-guide. Endnote Bibliography Software for managing referencing is available to you for free as a USQ Student: https://www.usq.edu.au/library/referencing/endnote-bibliographic-software
Finally, there is no word limit for this assignment. We are looking for the quality not for the quantity.
DELIVERABLES (as shown on StudyDesk)
Very important: Structure your assignment according to Assignment 2 Instructions on StudyDesk, but be sure to include all of the following details. Also be sure to look at the Marking Criteria, which is the rubric on which you will be marked
• Cover Page
• Abstract
• Table of Contents
• Introduction
• Time Management Plan including WBS
• TO-BE process
• Comparing “AS IS” and “TO BE” Process
• Entity Relationship Diagram
• Data Normalisation
• Testing
• Training
• System Changeover
• Report to Top Management
• Conclusion
• Reference List
Submission Requirements
You need to submit your assignment 1 via the assignment 1 submission link on your CIS5200 Study Desk.
Do not email your work to the course leader. If you are unable to upload, notify the course leader of the issue so that it may be resolved for you to upload the assignment.
Note: You may use Microsoft Project and Visio that provided by USQ to create your Gantt chart and business models. Also, you need to submit your assignment in one file (Word or PDF). Assignment with separate different files will not be accepted.
Please note that:
The following is the USQ Assessment – Assignment (Late Submission) and Compassionate and Compelling Circumstances procedure that relate to Extensions and Late Assignments. They can be found under the following links:
• Assessment – Assignment (Late Submission) Procedure: http://policy.usq.edu.au/documents.php?id=14749PL#4.2_Assignments
• Assessment of Compassionate and Compelling Circumstances Procedures: http://policy.usq.edu.au/documents.php?id=131150PL
Students seeking extensions for any Assignment work must provide appropriate documentation to support their request before the due date of the assignment (see points 4.3 and 4.4 in the Assessment of Compassionate and Compelling Circumstances Procedures above to see what is considered as Compassionate and Compelling reason for an extension and the level of documentation that will be needed).
An Assignment submitted after the due date without an approved extension of time will be penalised. The penalty for late submission is a reduction by five percent (5%) of the maximum Mark applicable for the Assignment, for each University Business Day or part Business Day that the Assignment is late. An Assignment submitted more than ten (10) University Business Days after the due date will have a Mark of zero recorded for that Assignment.
• The StudyDesk Assignments submission tool will accept late assignments up until 23:55 pm on the 10th University Business Day after the due date.
END