System Analysis and Design for Printing Incorporated Book Publishing

The report presents information about the current process and information systems being used by the book publishing business, Printing Incorporated Book Publishing. It covers the scope of the system, challenges, BA roles and challenges, use case modelling, key functional and non-functional requirements, event table, context diagram, process description, level 0 and level 1 DFD, ER diagram and data dictionary.

Executive Summary
The primary objective of the assignment is to learn about system analysis and design aspects for
a real-life scenario. From this assignment expertise in system analysis and design can be
improved. Information systems are important for businesses. So business are sometimes in hurry
while selecting the right information system. A business or system analyst is responsible for the
system analysis and design phase.
1

Contents
Introduction......................................................................................................................................3
Organisation Background................................................................................................................4
Scope of the current system.............................................................................................................4
Challenges........................................................................................................................................5
BA Roles and Challenges................................................................................................................5
Use Case Modelling.........................................................................................................................6
Key Functional and Non-Functional Requirements........................................................................7
Event Table......................................................................................................................................7
Context Diagram............................................................................................................................10
Process Description...................................................................................................................11
Level 0 DFD..................................................................................................................................11
Process Description...................................................................................................................11
Level 1 DFD..................................................................................................................................12
Process Description...................................................................................................................12
Entity Relationship Diagram.........................................................................................................13
Data Dictionary for the ER diagram..............................................................................................14
Conclusion.....................................................................................................................................18
References......................................................................................................................................19
2

Introduction
System analysis and design is an important part of an information system development project.
Businesses implement information systems to integrate it with their business operations and to
make it more profitable. That requires understanding of the current process, finding out the scope
of improvement possible by introducing an information system for the business and then
deploying the same. System analysis and design phase helps to understand system requirements.
If the system requirements are not clear then the primary objective of developing the information
system for a business will not be fulfilled (Dennis, Wixom, & Roth, 2012).
The purpose of the work is to present information about the current process and information
systems being used by the book publishing business, Printing Incorporated Book Publishing. The
business is planning to make changes in their current business operations and want to develop an
automated system to maintain their supply chain management process. The aim of the report is to
present various system models and description on how those can be useful and that will help to
identify the requirements of the proposed information system in future.
In the following sections of the report, there are information about the scope of the system, the
challenges being faced from the current system in relation to Business Analytics, key functional
and non-functional requirements, and system design diagrams like use case model, data flow
diagrams, event table, ER diagram etc.
All data for the report has been collected from the associated case study and relevant books.
3

Organisation Background
The Printing Incorporated Book Publishing is one of the old and major book publishing
companies in the Australia. It prepares, promote and sells eBooks. They produces eBooks from
the manuscripts of the authors. Then promotes and eBooks on the basis of sharing of royalty with
the authors. Other than selling from their own website, the company sells eBooks and printed
copies of the eBook from third party channels like the Amazon. From there they collect
revenues. The company is a leading name in feminist publishing domain and they offer different
formats of an eBook. For example PDF, MOBI, and ePub formats. All of their published work
are DRM free.
The company has staffs includes the sales staffs, admin staffs and so on. When an author submits
a manuscript, then it goes through many bins set for different phases of the publication process.
When an author asks for a manuscript or searches for the same, then the staffs need to search
each bin one by one.
When a customer purchase an eBook, they are delivered the book when the payment is received.
But when a customer submits an order for hardcopy then the book is printed and delivered to the
customer.
Management and accountant are interested in having a system that would fulfil all of their
accounting needs.
Scope of the current system
Currently, there is a semi-manual business process for the supply chain. The scope of the current
system is limited within the manuscript to eBook formation, promotions and sales of the eBook.
4

It includes the operations like tracking the manuscripts during the time of producing eBooks,
promotion and sales operations including taking orders from the customers and so on.
However the scope of other business processes are out of the scope of the system.
Challenges
Currently the business process is facing several channellings. Some of those are,
 There is no automated manuscript tracking system and poor handling of the manuscripts
in the bins for every stages of the publishing task is leading to inefficient and time
consuming search process, damages to the manuscripts and so on.
 Sales persons track their data manually in their systems. So, there is no centralised
database for orders and authors. When authors are approached for generating leads, then
it may happen that two or more sales person are approaching for the same author. It
wastes the time and effort of the salespersons. At the same time, when customers places
orders through the sales persons, those are not managed properly. There is also no
provision to track the sales figures from third party sales service providers like the
Amazon.
BA Roles and Challenges
There are various challenges in relation to the business analysis process. Those are,
 As there is no centralised database, so it is challenging to analyse the data. Data come
from heterogeneous sources like Amazon, sales databases of the sales employees and so
on. To process all these data it needs to have suitable business analytics platform. But the
business has no such platform yet.
5

 It is challenging to make strategic decisions. It needs reporting to be done manually. The
business is not able to analyse its sales performance effectively.
Use Case Modelling
The use case model has been developed by identifying the external entities and the relationships
between the entities and the system. The functions they perform with the help of the system is
represented as use cases.
The use case diagram is given below.
6

Key Functional and Non-Functional Requirements
The functional requirements of the current system are,
 A staff must be able to track the manuscripts from the bins.
 A staff must be able to search for a manuscript from the bins.
 An author must be able to submit manuscript manually.
 An author must be able to take updates of the status of the manuscript.
7

 Once book is published, a staff must be able to do promotional activities for the book.
 A customer must be able to purchase a book.
 A customer must be able to search for a book.
 A customer must be able to make online payment
 A sales person must be able to communicate with an author
 All sales persons must be able to see the list of the authors who have been already in
touch with some other sales person.
 Management must be able to generate BA reports
 An accountant must be able to get the accounts reports
The non-functional requirements are,
 The process should not cause damage to manuscripts. It should provide methods to keep
the manuscripts safe and protected.
 The processes should be user-friendly and integrated with one another
 The accuracy and reliability should not dampen.
Event Table
The event table is,
Sl
N
o
Event Trigger Initiator Use Case Output Recipient
1 Submission
of manuscript
Author is
asked to
submit
Author Submit
Manuscript
Manuscript will
be submitted.
System
8

manuscript
2 Request the
status of a
manuscript
An author
ask for the
status of a
manuscript
given for
publishing
Author Request
Status
The search
result about the
status of the
manuscript
Author
3 Track
manuscript
status
A staff
tracks the
status of the
manuscripts
Author Track
Manuscript
Search results
and updates on
the status
Staff
4 Do
promotional
activities
A staff will
do
promotional
activities
for a book
published
Staff Promote
Book
Updates of the
promotional
activities
Author
5 Purchase a
book
A customer
purchases a
book
Customer Purchase
book
An author will
have some sale
of his/her book
Author
6 Search for a
book
A customer
searches for
a book
Customer Search book Search results Sales Staff
9

7 Make online
payment
A customer
is able to
make
payment for
an order.
Customer Make
Payment
Online
payment
confirmation
Accountant
8 Communicat
e to an author
A sales
person
approaches
to some
author.
Sales person Communicat
e with author
Communicatio
n records
Customer
9 View list of
authors
View list of
sales
persons
approachin
g to a visit/
Sales person View list Communicatio
n with authors.
Sales person
10 Generates
report
Different
BA related
reports are
generated
Managemen
t
Generate
report
Reports Managemen
t
11 Get accounts
reports
Different
accounting
reports for
the
Accountant Get Reports Accounting
reports
Accountant
10

accountant
Context Diagram
The context diagram is given below. There are 6 external entities and it shows that there is a
single process representing the complete system or the manual tracking.
Process Description
There is only one process. The single process is the basis of any context diagram. It shows the
system as a single and black-boxed process. Without going into the details the diagram shows
how the process interact with one another and with the external devices and phone based
systems.
11

Level 0 DFD
The level 0 diagram is given below.
Process Description
There are three processes here.
 Publishing process is focused on the publication process related tasks and data.
 Book sales process is focused on the sales of the books, orders from the customers,
registration of customers and so on.
 Reporting process is focused on creating reports for the management and the accountant.
12

Level 1 DFD
The level 1 DFD is given below.
Process Description
There are 7 processes. The description of the new process are,
 Generate lead is focused on generating leads
 Sell a book is focused only on the sales activities
13

 Register customer is focused on the process of a customer getting registered with the
company.
 Collect manuscript is focused on colleting the manuscripts from the customer.
 Promote a book is focused on the promotional aspects of selling a book.
 Reporting process is focused on creating reports for the management and the accountant.
Entity Relationship Diagram
The ER diagram is,
14

Data Dictionary for the ER diagram
Relation Attribute Key
Employee empID Primary key
15

empName
baseSal
pubComm
promoComm
Author authID Primary key
authFName
authLName
Street
citstatey
Zipcode
penname
Email
SSN
bestTimeToCall
Category catID Primary key
catName
catDesc
Task taskID Primary key
taskName
daysComplete
webName
salesQuarter
16

AuthorPhone authId Primary key, foreign key
Desc Primary key
phNumber
Lead leadID Primary key
empID Foreign key
authID Foreign key
Call callID Primary key
leadID Foreign key
callDt
callTime
Notes
Book bookID Primary key
catID Foreign key
authID Foreign key
bookTitle
Subtitle
numPages
Type
ISBN
salesPrice
salesFreq
unitCost
onHandQty
17

Production bookID Primary key, foreign key
taskID Primary key, foreign key
startDt
finishDt
Royalty bookID Primary key, foreign key
qtrEnding Primary key
totalPrice
saleschannel channelID Primary key
salesChName
SalesRecord channeID Primary key, foreign key
bookID Primary key, foreign key
netSales
pubSalesDt
promoSalesDt
Order orderID Primary key
custID Foreign key
Amt
orderDt
Payment paymentID Primary key
orderID Foreign key
Amt
payDt
mode
18

Member memID Primary key
custID Foreign key
JoinDate
paymentAC
OrderLine orderID Primary key, foreign key
bookID Primary key, foreign key
Qty
purchasePrice
offerPrice
Conclusion
In this report, different aspects of information system design and analysis processes have been
discussed. It will help the readers to learn about how a system analysis and design project can be
undertaken in a real-life scenario. Starting from the scope of the system, limited within the
manual tracking process.
19

References
Bronzite, M. (2012). System Development. New York: Springer .
Coronel, C., & Morris, S. (2016). Database Systems: Design, Implementation, and Management.
Cengage Learning.
Dennis, A., Wixom, B. H., & Roth, R. M. (2012). Systems Analysis and Design. NY: John Wiley
& Sons.
Ramez Elmasri, S. B. (2016). Fundamentals of Database Systems. Pearson.
Roebuck, K. (2012). Systems Development Life Cycle (SDLC). Aspley: Emereo Publishing.
Shelly, G. B., & Rosenblatt, H. J. (2012). Analysis and Design for Systems. NY: Cengage
Learning.
Tilley, S., & Rosenblatt, H. J. (2016). Systems Analysis and Design. Cengage Learning.
20