Information System Project Plan for Opal Woodwork Company: BCO3447

This project report details the development of a business information system for Opal Woodwork, an Australian furniture company. The report begins with an introduction, client information, and business scenario, outlining the company's needs for an efficient system. It identifies key business processes like supplier and customer management, order placement, and inventory control. The report proposes system requirements, including supplier, customer, invoice, order, payment, payroll, delivery, stock, and customer relationship management systems. It utilizes BPMN diagrams for process modeling, context and data flow diagrams for system overview, and use case diagrams for user interactions. The project adopts the Scrum agile methodology for development. The report covers project planning, including tasks, timelines, and deliverables. It then moves on to information system design, implementation, and service-oriented architecture (SOA), recommending cloud computing for delivery. Finally, the report provides user documentation and data formats, offering a comprehensive overview of the project's development and implementation for Opal Woodwork.

Name
University
Course
Instructor

Table of Contents
Project introduction.......................................................................................................................4
Comprehensive client information and business scenario.........................................................4
Business scenario........................................................................................................................4
Business processes involved.......................................................................................................5
Requirements of the business information system..................................................................5
Business process modeling notation diagram with reference to (Chinosi, & Trombetta, 2012)
.........................................................................................................................................................6
Order placement BPMN............................................................................................................6
Inventory management BPMN.................................................................................................7
Context diagram with reference to (Zhao et.al; 2009).................................................................7
Data flow diagram with reference to (Fosdick & Osterweil, 2011)............................................8
Use case diagrams with reference to (Swain, Mohapatra, and Mall, 2010) and (Thakur, &
Gupta, 2014)....................................................................................................................................9
User registration use case..........................................................................................................9
Use case description...................................................................................................................9
Customer login use case...........................................................................................................11
Use case description for customer login.................................................................................11
Order Placement use case........................................................................................................13
Use case description for order placement..............................................................................14
Inventory management use case.............................................................................................15
Use case description for inventory management...................................................................15
Project development approach for the solution........................................................................16
Scrum methodology approach................................................................................................16
Advantages of scrum with reference to (Mahalakshmi & Sundararajan, 2013)................17
Disadvantages of Scrum.......................................................................................................18
Expected outcome........................................................................................................................18
Project Planning and Management............................................................................................19
Tasks..........................................................................................................................................20
Approaches...............................................................................................................................20
Deliverables...............................................................................................................................21
Information system design..........................................................................................................21
System implementation...............................................................................................................22

Services and SOA.....................................................................................................................22
The choice of platform.............................................................................................................22
Adoption of a delivery method................................................................................................23
Cloud computing as a delivery method or platform.........................................................23
Results Analysis and Conclusion................................................................................................24
User documentation.....................................................................................................................24
Inputs and outputs...................................................................................................................24
Input and output data formats...............................................................................................25
System environment.................................................................................................................25
References.....................................................................................................................................26

Project introduction
This is a business information system development project report for Opal Woodwork company.
The business information system aims to make Opal Woodwork business processes fast,
accurate, effective, efficient and consistent. Opal Woodwork aims to achieve business excellence
in their furniture industry through the use of the business information system. The report
identifies the business processes encountered by the company in its day-to-day activities,
proposes a way to solve them, proposes the requirements of the business information system,
proposes the approach to implement the project through scrum agile methodology, portrays how
the business information system would operate through context diagrams, dataflow diagrams,
and use case diagrams, it lays out the project plan for the entire business information system
project development, it recommends a delivery method through cloud computing, decomposes
the business processes into services, and gives a user documentation of the data formats.
Comprehensive client information and business scenario
Opal woodwork, an Australian furniture company that was established in 1995 has since
expanded its branches to three. Due to the complexity of the business processes it now handles,
Opal Woodwork now requires a business information system that can enable it to handle its
business processes efficiently and effectively. It has a budget for 236000 Australia dollars to
complete the project in two hundred days.
Business scenario
Opal Woodwork has suppliers who supply them with timber which they use to produce furniture
for their customers. These suppliers sent them invoices every end of the month. Opal Woodwork
then pay their suppliers after comparing the invoice with their records they make payment. The
records of stock of timber are also kept. Before Opal Woodwork runs out of timber they order for
more from their suppliers. After being made, the company displays the furniture to their
customers. Customers place orders for the furniture and can pay cash or cash on delivery. The
company offers delivery services for furniture that cost over ten thousand Australian dollars.
The company also has employees whom it pays on a monthly basis. All its employees are kept
on the payroll system.

Business processes involved
Supplier registration and login business process which allows suppliers to register and login to
their accounts.
Invoice processing business process through which the company receives invoices from
suppliers. It can also use this to send invoices to customers.
Customer registration and login business process through which customers can access their
accounts.
Furniture ordering business process through which customers can order furniture from the
company.
A payment business process through which the company can receive payments from customers
and send payments to suppliers.
A payroll business process through which the company can pay its employees.
The delivery business process through which the company can monitor, manage and track
deliveries.
A stock management business process through which the company can control the timber and the
furniture in its stores.
A customer relationship management business process that allows the company to manage the
intimacy between it and its customers.
Requirements of the business information system
Supplier accounts system
An invoice system
Customer accounts system
Order placement system
Payment system
A payroll system

Delivery management system
Stock management or inventory management system
A customer relationship management system.
With all these requirements the business needs a business intelligent system (Yeoh, & Koronios,
2010) and (Yoo, Henfridsson, and Lyytinen, 2010)
Business process modeling notation diagram with reference to (Chinosi, & Trombetta, 2012)
Order placement BPMN
The order placement business process modeling notation diagram shows the process of ordering
for furniture. A customer logs in and places the order, the system receives the order and checks
for the stock of the furniture ordered, if the stock is not sufficient the customer is notified, if the
stock is sufficient then packaging request is sent to the store and an invoice is sent to the
customer who pays and the furniture he or she has ordered is delivered.

Inventory management BPMN
The inventory management business process management notation diagram depicts the process
of inventory management. An admin logs into the system, if there are furniture products that are
low in stock the system notifies the admin. When the admin adds the stock, the system receives
the information and updates the stock database.
Context diagram with reference to (Zhao et.al; 2009)

Opal Woodwork business information system has three entities; customer, admin, and supplier
who interact with the system differently. In the above context diagram, a customer can register
an account, log in to the account, place furniture orders and make payments. Supplier can send
invoices to Opal Woodwork. An admin can log into the system, get stock notifications from the
system, and update the furniture stock.
Data flow diagram with reference to (Fosdick & Osterweil, 2011)
The data flow diagram is a decomposition of the business information system depicting the
different subsystems. There are five subsystems within the business information system; the
registration subsystem, the login subsystem, the order placement subsystem, the invoice
subsystem, and the inventory subsystem. A customer registers an account through the
registration subsystem. A customer, Supplier, and the admin get access to their accounts through
the login subsystem. A customer places furniture orders through the order placement subsystem,
gets an invoice through the invoice subsystem and makes payment through the order placement
subsystem.
Supplier sends invoices to the company through the invoice subsystem and admin manages
furniture stock through the inventory management subsystem. The order placement subsystem

stores all the order details in the database. The invoice subsystem stores all the details of the send
and receive invoices in the database. The inventory management subsystem updates the database
when it comes to furniture products stock.
Use case diagrams with reference to (Swain, Mohapatra, and Mall, 2010) and (Thakur, &
Gupta, 2014)
User registration use case
Use case description
Use case name Customer registration
Participating Actors Customer

Flow of events A customer clicks on the customer
registration button
The system displays the customer registration
page
A customer enters registration details
The system validates the details entered by
the customer
If the details are valid the The system displays
the message customer registered successfully
If the details entered are not valid the The
system displays a registration failure message.
Entry condition Customer clicks the customer registration
button
Exit condition The system displays a customer has been
registered successfully.
Quality requirements Rejecting invalid customer details
Being able to register a customer.

Customer login use case
Use case description for customer login
Use case name Customer login
Participating Actors Customer
Flow of events A customer clicks on the account login button
The system displays the account login form
page
A customer enters login credentials
The system authenticates the details entered
by the customer

If the details are authentic, the system gives
the customer access to his or her own account.
If the details entered are wrong, the system
displays wrong credentials entered.
Entry condition Customer clicks on the account login button
Exit condition System gives the user access to his or her
account
Quality requirements Rejecting wrong login credentials
Giving account access to a customer with
correct login credentials.