Background

Universe Bookshop is a medium-sized business started by Simon Lee in Australia. At

the start of the time, he used to sell books from his garage. He sells books to his friends and

families but after some time the business becomes popular. As the store gained recognition,

it expanded to serve a wider range of customers. As a result of the introduction of many

genres, which showed the market interest, Universe Book Shop grew to become a medium-

sized company.

Project scope

Determining the limits of the automated information system constitutes determining

the project scope in the context of the University Book Shop. The project scope is defined in

the table below:

Application to Key inclusions Key exclusions Focus areas Alignment with

case project goals

Indicate the Automation of the Capabilities or Improving the The scope as

extent of establishment and features that are effectiveness of described is by

Universe Book administration of not strictly order processing developing an

Shop’s client contacts. necessary for and customer integrated system

automated book relations. for expedited

information transactions. transactions in

system. bookshops.

Pay close Automated Significant Getting rid of the Ensuring the new

attention to the creation of infrastructure paperwork and system doesn't stray

automation of receipts and modifications laborious data into unrelated

critical company payment that don’t input related to functionality while

operations processing. immediately publisher and addressing the

related to affect the customer files. possibilities and

customer intended difficulties that have

relations, book company been recognized.

acquisition, and operations.

sales.

Simplifying the Expansion Removing

publisher ordering outside of the obstacles in the

procedure specified present system

bookstore that affect

activities into information

new business accessibility.

areas.

Communication

channels are
 integrated for

effective customer

and publisher

communication.

Problems and Opportunities

Problems

 Bottlenecks result from only one staff member having simultaneous access to critical
information.
 Paper-based files mean time-consuming searches and possible loss.
 Reconciling differences between the two forms takes more work.
 The manual maintenance of publisher and customer files results in inefficiencies.
 Sometimes files disappear, which results in delays and lowers client satisfaction.
 There's no efficient way to handle deadlines in the existing system.
 Transactions may be delayed or opportunities lost as a result of this weakness.
 Creating invoices by hand and keeping track of unpaid bills.

Opportunities

 The chance to develop a system that connects the essential components of

bookstore transactions.
 Integration of sales, communication channels, and customer connections to provide
a smooth process.
 Converting record-keeping from manual to computerized.
  Decreasing search times and increasing consumer and publisher information
accessibility.
 Putting in place an automated method for publishers and customers to
communicate.
 Adding functionalities for efficient deadline administration.
 Ensuring prompt transaction processing and enhanced customer support.
 Automating the generation of invoices and monitoring unpaid bills.
 Addressing existing inefficiencies to lower consumer complaints and transaction
failures.

Expected outcomes

 Streamlined Procedures: Automating critical business procedures, cutting down on

the interaction with humans, and expediting transactions in bookstores.
 Timely transaction policy: The order of books processed is ensured by the use of
efficient deadline management systems, which also increases overall operational
effectiveness.
 Enhanced customer experience: Accurate order processing, speedier response times,
and effective lines of communication all contribute to an improved level of customer
satisfaction.
 Efficient record-keeping: Make the switch from manual to automated record-keeping
systems, which will guarantee quick access to publisher and customer data ad cut
down on search times and mistakes.
Risks and mitigation strategies

Resource palnning
 Figure1. Resource chart

Source: Created by author

Project Phase Key Activities Milestones Deadlines

Initiation Conduct project kick-off Approval of project - [Date]

meeting. initiation.

Planning Define project scope and Finalization of project - [Date]

objectives. scope document.
 Identify and analyze risks. Completion of risk - [Date]
assessment.

Resource planning and Approval of resource plan. - [Date]

allocation.

Design Develop system design and Approval of system design. - [Date]

architecture.

Conduct user requirement Completion of user - [Date]

sessions. requirements
documentation.

Development Implement an automated Completion of initial - [Date]

information system. system development.

Conduct iterative testing and Approval of system testing - [Date]

refinements. phase.

Testing Comprehensive testing of the Completion of user - [Date]

automated system. acceptance testing (UAT).

Address and resolve identified Approval of the testing - [Date]

issues. phase.

Implementation Deployment of the automated Successful system go-live. - [Date]

system.

Monitor and address any post- Completion of post- - [Date]

implementation issues. implementation review.

Monitoring & Regular project status updates Ongoing monitoring of - [Date]

Control and progress reports. system performance.
 Address and mitigate any Continuous improvement - [Date]
emerging risks. initiatives.

Closure Review project outcomes Formal project closure. - [Date]

against initial objectives.

Document lessons learned Archiving of project - [Date]

and conduct knowledge documentation.
transfer.

Quality assurance

 Observance of Industry Guidelines: Make sure the development process complies

with industry standards and best practices to provide a stable and dependable

system.

 Testing Procedures: Create and carry out comprehensive testing procedures to find

and fix errors or inconsistencies in the system.

 Constant Monitoring: To guarantee the system's overall performance, put in place

continuous monitoring procedures to spot and correct any deviations from defined

quality standards.

 Peer Reviews: To guarantee code quality, conformity to coding standards, and

alignment with project objectives, facilitate cooperative peer reviews.

Systems Development Methodologies

Comparative analysis of three models

Criteria Waterfall Model Agile Methodology Incremental Model

Flexibility Low flexibility as High flexibility to Moderate flexibility,

changes is challenging accommodate with adaptability to
after the project starts. changes during changes in increments.
development.

Delivery Time Longer delivery time Shorter delivery time Moderate delivery time
before the final due to iterative and with progressive
product. incremental development.
development.

Documentation Extensive and clear May lack Documentation is

documentation at each comprehensive incremental and
stage. documentation due focused on the current
to its iterative nature. increment.

Customer Limited customer Active customer Customer involvement

Involvement involvement until the involvement is continuous but varies
end of the project. throughout the across increments.
development
process.

Testing and Testing is done after Continuous testing Easier testing and
Debugging the completion of the and debugging debugging due to
 entire project. throughout the smaller, manageable
development. increments.

Risk Identified risks are Embraces changes to Risks are managed

Management addressed at the manage risks and incrementally as new
beginning, but changes uncertainties more features are added.
are challenging. effectively.

Resource Resources are Resources can be Resources are allocated

Allocation allocated based on the adjusted dynamically incrementally based on
project plan, with little to meet changing the development of
room for adjustment. requirements. each increment.

Adaptability Limited adaptability to Highly adaptable to Adaptability is

changes in project changes and evolving moderate, primarily
requirements. business needs. focused on changes
within increments.

Agile methodology is suggested for the CEO’s ambitious goal and nature of project

need due to the flexibility, continual improvement, and adaption features.

Stakeholder and communication plan

Stakeholder Role/Interest Communication Plan

Simon Lee Decision-maker, Regular updates through bi-weekly meetings,
(CEO/Owner) Visionary detailed reports on project progress and
outcomes, and immediate notification of critical
issues.
Customers End-users, Feedback Monthly newsletters with system updates, a
providers dedicated customer helpline, periodic surveys for
feedback, and a user-friendly online platform.
Publishers Suppliers, Bi-weekly progress reports, direct communication
 Collaborators channels for order processing, and a dedicated
portal for publishers to track orders.
Sales Frontline staff, User Monthly team meetings for feedback, regular
Representatives perspective training sessions on system usage, and open
channels for reporting issues or improvements.
Managers and Operational Weekly team meetings for updates, access to
Staff involvement, System training resources, and a centralized platform for
users addressing operational challenges.
Australian Tax Regulatory body, Quarterly compliance reports, timely submission
Office (ATO) Compliance of necessary documents, and adherence to ATO
requirements guidelines for record-keeping and reporting.

Communication process

Continual Meetings

 Conduct regular meetings with Simon Lee biweekly to get regular updates on the

University store.

 Sales representatives, managers, and employees gather as a team once a month.

Channels of Direct Communication

 A dedicated customer care line for prompt assistance.

 Direct lines of contact for publishers to process orders.

Instructional Sessions

 Staff members and sales reps receive regular training.

 Availability of internet resources for lifelong learning.

Newsletters and Reports

 Monthly newsletters sent to publishers and customers.

  Simon Lee’s progress updates every two weeks.

Mechanisms of Feedback

 Client input through surveys conducted regularly.

 Provide avenues for employees and sales personnel to voice concerns or make

suggestions for enhancements.

Online Platforms

 Centralized platforms to handle operational issues for management and employees.

 Publishers may track orders and retrieve pertinent information using a dedicated

portal.

User Requirements

Use a multifaceted strategy to efficiently identify and gather user needs for the new

system. Complete in-depth surveys and interviews with important parties, such as Simon

Lee, managers, salespeople, consumers, and publishers. To guarantee inclusion, take into

account the users' cultural origins. Conduct focus groups to get a range of viewpoints and

expectations. To visually convey system features and accommodate varying learning styles,

use mock-ups and prototypes. Engage consumers in feedback sessions regularly to iteratively

revise needs. Through the use of an inclusive approach, a thorough knowledge of user

demands is ensured, resulting in a system that is compatible with a wide range of

expectations and cultural backgrounds.