Abstract

During Covid-19 Pandemic, Offline Print shops are experiencing major dips
in foot traffic. Yet, this doesn’t mean shutting shops totally and trust that the circum-
stance will end. Merchants are utilizing the online space to receive orders, during
the lockdown. There are many existing systems for this problem but there are some
loopholes in each system, so there is a need for a system that offers the user to place
orders from anywhere any time using the mobile application with the help of cloud
computing. Before placing an order, the client should calculate of fairs, estimated
time of delivery should be calculated. The user would pay using various payment
methods like UPI, Net Banking, Debit Credit card, and shop owner shouldn’t need
to invest large amounts. Internet affects human life with its technological innova-
tion and fast development. Trust assumes a significant job in the Internet world;
however, a trust relationship between the receiver and seller is dynamic and hard to
quantify. Customer’s apparent trust in an e-commerce website is significant for the
accomplishment of online business. Given many associated usability issues when
performing tasks on a website, an online business needs to understand issues related
to usability problems of an e-commerce website and the techniques to identify these
issues. In the proposed system, there should be the use of the latest programming
languages, tools, and technologies like cloud computing. Thus, the system should
provide a simple and practical cloud-based printing solution. The online store is the
primary needs of online businesspeople. But there is a problem faced by business
people who run their business on the online shop website, especially the techni-
cal aspect of online shop website management that is hard to do. This problem is
very important because the need of businesspeople always changes rapidly based on
the business situation. This makes business people adopt the changes of business
needs to their online shop website. The proposed system adds a competitive edge to
your business with streamlined key processes and automated workflow and delivers
complete control, effective order maintenance, and monitoring to help the printing
business to increase sales.
Keywords— Cloud printing , Evaluation method, web print, Cloud computing
 INDEX

1 Synopsis 1
1.1 Project Title . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.2 Project Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.3 Internal Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.4 Sponsorship and External Guide . . . . . . . . . . . . . . . . . . . 2
1.5 Technical Keywords (As per ACM Keywords) . . . . . . . . . . . . 2
1.6 Problem Statement . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.7 Abstract . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.8 Goals and Objectives . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.9 Names of Conferences / Journals where papers can be published . . 4

2 Technical Keywords 5
2.1 Area of Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.2 Technical Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . 6

3 Introduction 7
3.1 Project Idea . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
3.2 Motivation of the Project . . . . . . . . . . . . . . . . . . . . . . . 8
3.3 Literature Survey . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

4 Problem Definition and scope 10

4.1 Problem Statement . . . . . . . . . . . . . . . . . . . . . . . . . . 11
4.1.1 Goals and objectives . . . . . . . . . . . . . . . . . . . . . 11
4.1.2 Statement of scope . . . . . . . . . . . . . . . . . . . . . . 11
4.2 Product Function . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
 4.3 Outcome . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
4.4 Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
4.5 Software Resources Required . . . . . . . . . . . . . . . . . . . . . 12

5 Project Plan 13
5.1 Project Estimates . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
5.1.1 Reconciled Estimates . . . . . . . . . . . . . . . . . . . . . 14
5.1.2 Project Resources . . . . . . . . . . . . . . . . . . . . . . . 15
5.2 Risk Management w.r.t. NP Hard analysis . . . . . . . . . . . . . . 15
5.2.1 Risk Identification . . . . . . . . . . . . . . . . . . . . . . 15
5.2.2 Risk Analysis . . . . . . . . . . . . . . . . . . . . . . . . . 16
5.3 Project Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
5.3.1 Project task set . . . . . . . . . . . . . . . . . . . . . . . . 17
5.3.2 Task network . . . . . . . . . . . . . . . . . . . . . . . . . 18
5.4 Team Organization . . . . . . . . . . . . . . . . . . . . . . . . . . 18
5.4.1 Team structure . . . . . . . . . . . . . . . . . . . . . . . . 18

6 Software requirement specification (SRS is to be prepared using relevant

mathematics derived and software engg. Indicators in Annex A and B) 19
6.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
6.1.1 Purpose and Scope of Document . . . . . . . . . . . . . . . 20
6.1.2 Document Conventions . . . . . . . . . . . . . . . . . . . . 20
6.1.3 Intended Audience And Reading Suggestions . . . . . . . . 20
6.1.4 Product Scope . . . . . . . . . . . . . . . . . . . . . . . . 20
6.2 OVERALL DESCRIPTION . . . . . . . . . . . . . . . . . . . . . 21
6.2.1 Product Perspective . . . . . . . . . . . . . . . . . . . . . . 21
6.2.2 Product Functions . . . . . . . . . . . . . . . . . . . . . . 21
6.2.3 User Classes And Characteristics . . . . . . . . . . . . . . 21
6.3 EXTERNAL INTERFACE REQUIREMENTS . . . . . . . . . . . 21
6.3.1 User Interfaces . . . . . . . . . . . . . . . . . . . . . . . . 21
6.3.2 Hardware Interfaces . . . . . . . . . . . . . . . . . . . . . 22
6.3.3 Software Interfaces . . . . . . . . . . . . . . . . . . . . . . 22
 6.3.4 Communications Interfaces . . . . . . . . . . . . . . . . . 22
6.4 OTHER NONFUNCTIONAL REQUIREMENTS . . . . . . . . . . 22
6.4.1 Performance Requirements . . . . . . . . . . . . . . . . . . 22
6.4.2 Safety Requirements . . . . . . . . . . . . . . . . . . . . . 22
6.4.3 Security Requirements . . . . . . . . . . . . . . . . . . . . 22
6.4.4 Software Quality Attributes . . . . . . . . . . . . . . . . . 22
6.4.5 Use Case View . . . . . . . . . . . . . . . . . . . . . . . . 23
6.5 Data Model and Description . . . . . . . . . . . . . . . . . . . . . 23
6.5.1 Data Description . . . . . . . . . . . . . . . . . . . . . . . 23
6.5.2 Data objects and Relationships . . . . . . . . . . . . . . . . 24
6.6 Functional Model and Description . . . . . . . . . . . . . . . . . . 24
6.6.1 Data Flow Diagram . . . . . . . . . . . . . . . . . . . . . . 24

7 Detailed Design Document using Appendix A and B 26

7.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
7.2 Architectural Design . . . . . . . . . . . . . . . . . . . . . . . . . 27
7.3 Class Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
7.4 Sequence Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . 28
7.5 Activity Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

8 Summary and Conclusion 31

8.1 Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

9 References 33
9.1 References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
List of Figures

5.1 Task Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

6.1 Use case diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

6.2 Data Flow diagram 0 . . . . . . . . . . . . . . . . . . . . . . . . . 24
6.3 Data Flow diagram 1 . . . . . . . . . . . . . . . . . . . . . . . . . 25

7.1 Architecture diagram . . . . . . . . . . . . . . . . . . . . . . . . . 27

7.2 Sequence diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
7.3 Activity diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
List of Tables

5.1 Risk Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

5.2 Risk Probability definitions [?] . . . . . . . . . . . . . . . . . . . . 17
5.3 Risk Impact definitions . . . . . . . . . . . . . . . . . . . . . . . . 17
CHAPTER 1

SYNOPSIS
1.1 PROJECT TITLE

Cloud Based Stock Price Prediction using News Sentiment Analysis

1.2 PROJECT OPTION

Internal Project

1.3 INTERNAL GUIDE

Prof.

1.4 SPONSORSHIP AND EXTERNAL GUIDE

Prof.

1.5 TECHNICAL KEYWORDS (AS PER ACM KEYWORDS)

1. Computer Systems Organization

(a) Web Technology

(b) Database Technology

(c) Cloud Computing

1.6 PROBLEM STATEMENT

To Develop a cloud-based printing service for digital works so that consumers can
upload and print at any time to achieve an efficient online printing.

1.7 ABSTRACT

During Covid-19 Pandemic, Offline Print shops are experiencing major dips in foot
traffic. Yet, this doesn’t mean shutting shops totally and trust that the circumstance
will end. Merchants are utilizing the online space to receive orders, during the lock-
down. There are many existing systems for this problem but there are some loop-
holes in each system, so there is a need for a system that offers the user to place
orders from anywhere any time using the mobile application with the help of cloud
computing. Before placing an order, the client should calculate of fairs, estimated
time of delivery should be calculated. The user would pay using various payment
methods like UPI, Net Banking, Debit Credit card, and shop owner shouldn’t need
to invest large amounts. Internet affects human life with its technological innova-
tion and fast development. Trust assumes a significant job in the Internet world;
however, a trust relationship between the receiver and seller is dynamic and hard to
quantify. Customer’s apparent trust in an e-commerce website is significant for the
accomplishment of online business. Given many associated usability issues when
performing tasks on a website, an online business needs to understand issues related
to usability problems of an e-commerce website and the techniques to identify these
issues. In the proposed system, there should be the use of the latest programming
languages, tools, and technologies like cloud computing. Thus, the system should
provide a simple and practical cloud-based printing solution. The online store is the
primary needs of online businesspeople. But there is a problem faced by business
people who run their business on the online shop website, especially the technical
aspect of online shop website management that is hard to do. This problem is very
important because the need of businesspeople always changes rapidly based on the
business situation. This makes business people adopt the changes of business needs
to their online shop website. It is shown a comparative study on the effectiveness of
the various methods for online printing service. The proposed system adds a compet-
itive edge to your business with streamlined key processes and automated workflow
and delivers complete control, effective order maintenance, and monitoring to help
the printing business to increase sales.

Keywords— Cloud printing , Evaluation method, web print, component

technology, Cloud computing
1.8 GOALS AND OBJECTIVES

• To build a cloud-based application to upload document for printing from any-

where and anytime.

• To show nearest printing shop on map.

• To add various payment methods like UPI, Net banking, Debit/Credit cards,
Wallets for easy payment.

• To overcome and decrease the risk of Covid-19 spread.

1.9 NAMES OF CONFERENCES / JOURNALS WHERE PAPERS CAN BE

PUBLISHED

• IEEE Transactions on Artificial Intelligence

• International Journal for Research in Applied Science and Engineering Tech-

nology (IJRASET)

• ResearchGate
 CHAPTER 2

TECHNICAL KEYWORDS
2.1 AREA OF PROJECT

Web Technology, Cloud Computing, Database Technology

2.2 TECHNICAL KEYWORDS

1. Computer Systems Organization

(a) Web technology

(b) Database Technology

(c) Cloud Computing

 CHAPTER 3

INTRODUCTION
3.1 PROJECT IDEA

• Buyers and sellers can get together through the online trading space, and in
that way, we can enjoy more and more convenient business services. On-line
printing system provides basic printing service for digital works so that con-
sumers can upload and print at any time to achieve an efficient online printing
approach. In this system, on-line print ordering module has basically com-
pleted all the required features, and consumers can easily navigate to the var-
ious works hits, get a convenient and quick understanding about work-related
information, and make a purchase.

3.2 MOTIVATION OF THE PROJECT

• Online store is the main needs of online businesspeople today. But there is a
problem faced by businesspeople who run their business on online shop web-
site, especially the technique aspect of online shop website management that is
hard to do. This problem is very important because the need of businesspeople
always changes rapidly based on the business situation. This makes business-
people adopt the changes of business needs to their online shop website.

3.3 LITERATURE SURVEY

• A sale-oriented online-shop management support method for e-commerce,

Yoshitaka Sakurai, Takashi Kawabe, Takahiko Sakai, Kouhei Takada:When
a sales heading of the sales management pages provided by the system is (se-
lected and) set up, the system automatically generates a sales page preview
which can be checked and modified by sale managers. Product group Database
manager can generate, edit and delete a product group name also he has an
editing function to search and edit products belonging to a product group.

• The Design and Implementation of a Process-based Printing Order Man-

agement system, Yongbin Zhang, Huiling Ma: This paper presents a sys-
tem of information tracking to solve the problem of isolated order informa-
tion among production processes. The BPMN (Business Process Model and
 Notation) specification is adopted for establishment of order process model.
The model can be used to describe the company’s core business and the or-
der information transmission process with the process- oriented thinking. The
results show that order information can be transferred timely, fast and accu-
rately, which can avoid the delays or inaccuracies caused by manual operation.
Meanwhile the managers can always follow the tracks of the order progress
and provide clients with advice.

• Component Design of Business Process Web Content Management Sys-

tem for Online Shop Website Rizal Panji Islami, Adi Mulyanto:The busi-
ness people who run their business on online shop website, mostly face the
problems of technique aspect of online shop management which is hard to do.
This problem is very important which makes business people to adopt changes
of business needs to their online shop website. This paper presents designed
solution that is done by component design approach for business process web
content management system for online shop. The web content management
system is designed by analyzing atomic components that can be used to han-
dle needs of the business people.

• E – Commerce personalized recommendation system based on web min-

ing technology design and implementation, Sun Lin, Xu WenZheng:E -
commerce personalized recommence system design process and implementa-
tion process is implemented in this paper. In E–commerce site personalized
recommendation system based on a web mining process, first of all to the over-
all design, system design based on requirement analysis, and then to design the
process, the last is the database design.
 CHAPTER 4

PROBLEM DEFINITION AND SCOPE

4.1 PROBLEM STATEMENT

To Develop a cloud-based printing service for digital works so that consumers can
upload and print at any time to achieve an efficient online printing.

4.1.1 Goals and objectives

The Goals and Objectives of the given system are as follows:

• To build a cloud-based application to upload document for printing from any-

where and anytime.

• To show nearest printing shop on map.

• To add various payment methods like UPI, Net banking, Debit/Credit cards,
Wallets for easy payment.

• To overcome and decrease the risk of financial loss.

4.1.2 Statement of scope

• On-line printing system provides basic printing service for digital works so
that consumers can upload and print at any time to achieve an efficient on-
line printing approach. In this system, on-line print ordering module has basi-
cally completed all the required features, and consumers can easily navigate to
the various works hits, get a convenient and quick understanding about work-
related information and make a purchase.

4.2 PRODUCT FUNCTION

• Supports multiple file extensions.

• Multiple payment modes

• Find nearest printing shop on map.

• Options for paper type, paper size, paper quality

4.3 OUTCOME

• We propose a system that offers the user everything any printing company re-
quires to print manage their business from estimating, outsourcing, producing
job sheets, delivery dockets, accounts, management reports, diary system. Af-
ter placing order by the client calculation of fairs, the information will transfer
to the respective production team. With our system shop owner don’t need to
invest large amounts. We provide access to the full system, customize doc-
uments, and import information onto the system. Internet surfing affects the
modern life with its technological innovation and rapid change.

4.4 APPLICATIONS

• Online-Printing Shop

• Online Legal Documentation

• Online Photo Printing

4.5 SOFTWARE RESOURCES REQUIRED

Platform :

1. Programming Language: Python 3.5

2. Libraries: Flask, PyMYSQL

3. Tools : PyCharm, Python IDLE, Putty

4. Cloud : Amazon AWS

 CHAPTER 5

PROJECT PLAN
5.1 PROJECT ESTIMATES

Use Spiral model in the SDLC and associated streams derived from assignments
1,2,3, 4 and 5( Annex A and B) for estimation.
The spiral model, originally proposed by Boehm [BOE88], is an evolution-
ary software process model that couples the iterative nature of prototyping with the
controlled and systematic aspects of the linear sequential model. It provides the
potential for rapid development of incremental versions of the software. Using the
spiral model, software is developed in a series of incremental releases. During early
iterations, the incremental release might be a paper model or prototype. During
later iterations, increasingly more complete versions of the engineered system are
produced.
A spiral model is divided into a number of framework activities, also called
task regions.6 typically, there are between three and six task regions.depicts a spiral
model that contains six task regions:

• Customer communication: tasks required to establish effective communica-

tion between developer and customer.

• Planning: tasks required to define resources, timelines, and other project re-
lated information.

• Risk Analysis: tasks required to assess both technical and management risks.

• Engineering: tasks required to build one or more representations of the ap-

plication.

• Construction and Release: tasks required to construct, test, install, and pro-
vide user support (e.g., documentation and training).

5.1.1 Reconciled Estimates

5.1.1.1 Cost Estimate Using COCOMO-II Model

Costing is the proposed or estimated cost of producing or undertaking something of

a software product. It can be calculated using COCOMO, COCOMO II models. For
costing of our system, Basic COCMO model is used.
The Constructive Cost Model (COCOMO) is an algorithmic software cost
estimation model developed by Barry W. Boehm. The model uses a basic regression
formula with parameters that are derived from historical project data and current as
well as future project characteristics.
Basic COCOMO computes software development effort (and cost) as a
function of program size. Program size is expressed in estimated thousands
of source lines of code (SLOC). COCOMO applies to three classes of software
projects:

• Organic projects - ”small” teams with ”good” experience working with ”less
than rigid” requirements

• Semi-detached projects - ”medium” teams with mixed experience working

with a mix of rigid and less than rigid requirements.

• 2 input: financial and News API’s

• output : Predict stock price.

5.1.1.2 Time Estimates

5.1.2 Project Resources

Project resources [People, Hardware, Software, Tools and other resources] based on
Memory Sharing, IPC, and Concurrency derived using appendices to be referred.

5.2 RISK MANAGEMENT W.R.T. NP HARD ANALYSIS

This section discusses Project risks and the approach to managing them.

5.2.1 Risk Identification

Risk analysis and management are the series of steps that help a project team to
understand and manage uncertainty.The team establishes a plan for managing the
risks.The primary objective to avoid risk,the team works to develop a contingency
plan that will enable it to respond in a controlled and effective manner.
 1. Have top software and customer managers formally committed to support the
project?

2. Are end-users enthusiastically committed to the project and the system/product

to be built?

3. Are requirements fully understood by the software engineering team and its
customers?

4. Have customers been involved fully in the definition of requirements?

5. Do end-users have realistic expectations?

6. Does the software engineering team have the right mix of skills?

7. Are project requirements stable?

8. Is the number of people on the project team adequate to do the job?

9. Do all customer/user constituencies agree on the importance of the project and

on the requirements for the system/product to be built?

5.2.2 Risk Analysis

The risks for the Project can be analyzed within the constraints of time and quality

Impact
ID Risk Description Probability
Schedule Quality Overall
1 Increase in complexity of Low Low High High
modules.
2 Size estimated may be low Low Low High High
3 Connectivity to Cloud Medium Low High High
4 Response from API Low Low High High

Table 5.1: Risk Table

 Probability Value Description
High Probability of occurrence is > 75%
Medium Probability of occurrence is 26 − 75%
Low Probability of occurrence is < 25%

Table 5.2: Risk Probability definitions [?]

Impact Value Description

Very high > 10% Schedule impact or Unacceptable quality
High 5 − 10% Schedule impact or Some parts of the project have low
quality
Medium < 5% Schedule impact or Barely noticeable degradation in qual-
ity Low Impact on schedule or Quality can be incorporated

Table 5.3: Risk Impact definitions

5.3 PROJECT SCHEDULE

5.3.1 Project task set

Major Tasks in the Project stages are:

• Task 1: Topic Finalization

• Task 2: Market Analysis

• Task 3: Requirement Gathering

• Task 4: Detailed Design

• Task 5: Implementation

• Task 6: Integration

• Task 7: Module Testing

• Task 8: Detailed Documentation

• Task 9: Deployment
5.3.2 Task network

Figure 5.1: Task Network

5.4 TEAM ORGANIZATION

There are four students and one internal guide.The guide helps us with suggestions
and corrections when needed and necessary.

5.4.1 Team structure

1. Member 1

2. Member 2

3. Member 3

4. Member 4
 CHAPTER 6

SOFTWARE REQUIREMENT
SPECIFICATION (SRS IS TO BE
PREPARED USING RELEVANT
MATHEMATICS DERIVED AND
SOFTWARE ENGG. INDICATORS IN
ANNEX A AND B)
6.1 INTRODUCTION

6.1.1 Purpose and Scope of Document

Buyers and sellers can get together through the online trading space, and in that way,
we can enjoy more and more convenient business services. On-line printing system
provides basic printing service for digital works so that consumers can upload and
print at any time to achieve an efficient online printing approach. In this system,
on-line print ordering module has basically completed all the required features, and
consumers can easily navigate to the various works hits, get a convenient and quick
understanding about work-related information, and make a purchase.

6.1.2 Document Conventions

This is the Software Requirements Specification (SRS) for ‘Print on Air : imple-
mentation of a cloud-based printing order management system.’. The purpose of this
document is to give information about the end user’s requirements, both functional
and non-functional to the reader.

6.1.3 Intended Audience And Reading Suggestions

Audience of this SRS are other project developer, users like students, viewers that
will use system. This SRS contains detail description about the product, its func-
tioning, different external interfaces required, system features, Nonfunctional re-
quirements and some additional requirements.

6.1.4 Product Scope

On-line printing system provides basic printing service for digital works so that con-
sumers can upload and print at any time to achieve an efficient online printing ap-
proach. In this system, on-line print ordering module has basically completed all the
required features, and consumers can easily navigate to the various works hits, get
a convenient and quick understanding about work-related information, and make a
purchase.
6.2 OVERALL DESCRIPTION

6.2.1 Product Perspective

In this system, on-line print ordering module has basically completed all the required
features, and consumers can easily navigate to the various works hits, get a conve-
nient and quick understanding about work-related information and make a purchase.
However, we also need to improve in some areas, such as the module’s security
features, the lack of corresponding data encryption, and when transaction payments
should be involved; you can try to take other payment method such as UPI, net
banking, PayPal and other forms of payment. These functions will be discussed
separately in later research.

6.2.2 Product Functions

• Upload all types of document files.

• Notify vender about new order.

• Store data on Amazon AWS

• • Send notification to user after dispatched order.

6.2.3 User Classes And Characteristics

In our system have mainly two, first is the who uses a system, second is the admin-
istrator.

• User: user who can use application for order.

• Admin: These users has an authority to update, schedule and Configure a

system.

6.3 EXTERNAL INTERFACE REQUIREMENTS

6.3.1 User Interfaces

The user of the system must have a device with working internet connection to access
application.
6.3.2 Hardware Interfaces

No hardware interfaces needed except Device to use application.

6.3.3 Software Interfaces

Our project is based on Cloud Computing and web so, required account must be
signed up like AWS, Web Hosting etc.

6.3.4 Communications Interfaces

The system can be works only in online mode hence, communication interfaces are
compulsory.

6.4 OTHER NONFUNCTIONAL REQUIREMENTS

6.4.1 Performance Requirements

The system should take immediate action and show result as fast as possible.

6.4.2 Safety Requirements

The system/application is currently in developing phase so, should’t use for legal
purpose.

6.4.3 Security Requirements

Here the system deployed on cloud so, there is no need of security mechanism.

6.4.4 Software Quality Attributes

• Reliability -The reliability that user can easily use application to order the
print.

• Availability -System deployed on amazon AWS cloud so there is 99.9 Percent

availability.

• Maintainability -Our system usually not required maintenance until some

modification to be done.
6.4.5 Use Case View

The purpose of use case diagram is to capture the dynamic aspect of a system. How-
ever, this definition is too generic to describe the purpose, as other four diagrams
(activity, sequence, collaboration, and State chart) also have the same purpose. We
will investigate some specific purpose, which will distinguish it from other four dia-
grams.

Figure 6.1: Use case diagram

6.5 DATA MODEL AND DESCRIPTION

6.5.1 Data Description

Data objects that will be managed/manipulated by the software are described in this
section. The database entities or files or data structures required to be described. For
data objects details can be given as below
6.5.2 Data objects and Relationships

Data objects and their major attributes and relationships among data objects are de-
scribed using an ERD- like form.

6.6 FUNCTIONAL MODEL AND DESCRIPTION

A description of each major software function, along with data flow (structured anal-
ysis) or class hierarchy (Analysis Class diagram with class description for object
oriented system) is presented.

6.6.1 Data Flow Diagram

6.6.1.1 Level 0 Data Flow Diagram

Highest abstraction level DFD is known as Level 0 DFD, which depicts the entire
information system as one diagram concealing all the underlying details. Level 0
DFDs are also known as context level DFDs.

Figure 6.2: Data Flow diagram 0

6.6.1.2 Level 1 Data Flow Diagram

The Level 0 DFD is broken down into more specific, Level 1 DFD. Level 1 DFD
depicts basic modules in the system and flow of data among various modules. Level
1 DFD also mentions basic processes and sources of information.
Figure 6.3: Data Flow diagram 1
 CHAPTER 7

DETAILED DESIGN DOCUMENT USING

APPENDIX A AND B
7.1 INTRODUCTION

This document specifies the design that is used to solve the problem of Product.

7.2 ARCHITECTURAL DESIGN

In this approach, provide an application to client which allows for purpose of print-
ing application which search or upload the required media of product and then it
processes further for printing it depends on input from user. It shows the all avail-
able venders nearby to user for printing. Then user can choose vendor and pay by
selecting payment mode. The uploaded document store on cloud storage. After com-
pleting task, notification will send to user automatically. It also encompasses time,
resource, technical requirements and client requirements. The proposed system will
able to maintain customer, employee and supplier details.

Figure 7.1: Architecture diagram

The proposed system will able to maintain customer, employee and supplier
details. This provides an easy way to search, filter and update the records. The sys-
tem able to manage and maintain invoice and order detail. The system would keep
records of customer order history and provision and filter for future use. This also
includes an efficient and accurate way to generate invoices. The stock management
system will provide an effective way to manage the stock and automatically noti-
fies when the reorder level is reached. It also able to provide stock reports for the
vendors.
7.3 CLASS DIAGRAM

The class diagram is the main building block of object-oriented modeling. It is used
for general conceptual modeling of the structure of the application, and for detailed
modeling translating the models into programming code. Class diagrams can also be
used for data modeling.
The purpose of class diagram is to model the static view of an application.
Class diagrams are the only diagrams which can be directly mapped with object-
oriented languages and thus widely used at the time of construction.

7.4 SEQUENCE DIAGRAM

The purpose of interaction diagrams is to visualize the interactive behavior of the

system. Visualizing the interaction is a difficult task. Hence, the solution is to use
different types of models to capture the different aspects of the interaction.

Figure 7.2: Sequence diagram

The sequence diagram represents the flow of messages in the system and is
also termed as an event diagram. It helps in envisioning several dynamic scenarios.
It portrays the communication between any two lifelines as a time-ordered sequence
of events, such that these lifelines took part at the run time. In UML, the lifeline is
represented by a vertical bar, whereas the message flow is represented by a vertical
dotted line that extends across the bottom of the page. It incorporates the iterations
as well as branching.
Purpose of a Sequence Diagram-

• To model high-level interaction among active objects within a system.

• To model interaction among objects inside a collaboration realizing a use case.

• It either models generic interactions or some certain instances of interaction.

7.5 ACTIVITY DIAGRAM

The basic purposes of activity diagram is similar to other four diagrams. It captures
the dynamic behavior of the system. Other four diagrams are used to show the mes-
sage flow from one object to another, but activity diagram is used to show message
flow from one activity to another.

Figure 7.3: Activity diagram

The activity diagram helps in envisioning the workflow from one activity to
another. It put emphasis on the condition of flow and the order in which it occurs.
The flow can be sequential, branched, or concurrent, and to deal with such kinds of
flows, the activity diagram has come up with a fork, join, etc.
It is also termed as an object-oriented flowchart. It encompasses activities composed
of a set of actions or operations that are applied to model the behavioral diagram.
 CHAPTER 8

SUMMARY AND CONCLUSION

8.1 CONCLUSION

Buyers and sellers can get together through the online trading space, and in that way,
we can enjoy more and more convenient business services. On-line printing system
provides basic printing service for digital works so that consumers can upload and
print at any time to achieve an efficient online printing approach. In this system,
on-line print ordering module has basically completed all the required features, and
consumers can easily navigate to the various works hits, get a convenient and quick
understanding about work-related information and make a purchase. However, we
also need to improve in some areas, such as the module’s security features, the lack of
corresponding data encryption, and when transaction payments should be involved;
you can try to take other payment method such as UPI, net banking, PayPal and other
forms of payment. These functions will be discussed separately in later research.
CHAPTER 9

REFERENCES
9.1 REFERENCES

1. Real-Time Stencil Printing Optimization Using a Hybrid Multi-Layer On-

line Sequential Extreme Learning and Evolutionary Search Approach Hongya
Lu;Haifeng Wang;Sang Won Yoon;Daehan Won IEEE Transactions on Com-
ponents, Packaging and Manufacturing Technology Year: 2019 — Volume: 9,
Issue: 12 — Journal Article — Publisher: IEEE

2. PrintEase - A Smart Printing Application Richard Joseph;Simran Dembla;Suren

Sughand;Deepika Khithani 2018 International Conference on Smart City and
Emerging Technology (ICSCET)

3. An Online Method for Load Impedance Extraction for Printed Lines based on
Near Field Measurements Hui Xu;Donglin Su 2019 12th International Work-
shop on the Electromagnetic Compatibility of Integrated Circuits (EMC Compo)
Year: 2019 — Conference Paper — Publisher: IEEE

4. ThingiPano: A Large-Scale Dataset of 3D Printing Metadata, Images, and

Panoramic Renderings for Exploring Design Reuse Alexander Berman;Francis
Quek 2020 IEEE Sixth International Conference on Multimedia Big Data
(BigMM) Year: 2020 — Conference Paper — Publisher: IEEE

5. Research on Image Matching in Printing Defects Detection Based on Machine

Vision Yihong Wang 2019 IEEE 19th International Conference on Commu-
nication Technology (ICCT) Year: 2019 — Conference Paper — Publisher:
IEEE

6. A Research on Design of Campus Printing Service System Di Lu;Guoxin

Mao;Xi Wang;Wei Tan 2019 IEEE 2nd International Conference on Electronic
Information and Communication Technology (ICEICT) Year: 2019 — Con-
ference Paper — Publisher: IEEE

7. Application of Digital Virtual Prototype Technology in Simulation Design of

Paper Delivery Mechanism of Printing Press Ming He 2020 International Year:
2020 — Conference Paper — Publisher: IEEE