Chapter I

INTRODUCTION

1.1. Background

The project “Shree Shankar Itta Udhyog” is basically developed for customers who are facing
problems to buy bricks online. This organization was facing problems for storing details of
customers' orders. They still prefer recording the entries like old tradition way, so with
implementation of this system there will be efficient management of data and information.

1.2. Introduction of the Organization

Shree Shankar Itta Udhyog is providing the service since 2068 BS in Saptari, Kathmandu,
Nepal. It has been providing various services to their customers from very beginning. From
the beginning, they have been using old traditional methods for keeping the detail of
customers for viewing the information, facilities, offers provided by this organization.

The system is basically developed to meet the requirement of Shree Shankar Itta Udhyog.
The major purposes of developing this system are:

i. To make working procedure faster and automated.

ii. To make the existing manual system into computerized form.
iii. To increase customer access from most different part of the city.

1.3. Current Situation of the Organization

In the current situation Shree Shankar Itta Udhyog their data in a traditional way. This result
in delay in operation of the information.

1
1.4. Problem statement of the Report

Shree Shankar Itta Udhyog has kept paper record in filling which is very much difficulty for
the owner to keep the track of it's sales. As we all know that now a days everything is
computerized so if they also can keep the track in the computer it will be very useful for
upcoming days.

All the problems are going to be minimized by this web application which by the way keep
the record, update and delete of all types of products, sales and information of Shree Shankar
Itta Udhyog.

1.5. Objectives of project

• To systematically record products, payments, customers, orders and sales.

• To develop Web based Bricks management system.
• To remove the difficulty faced by the customers while buying the Bricks.

1.6. Literature Review

There are many problems in Bricks data management system such as high cost, low security,
and poor performance of real-time. The paper deals with a simulation study on a planned
production plant in the brick industry. We implemented this plant in TAYLOR 11. Although
the boundary conditions seemed relatively simple, we had to manage a complex, non-linear
system. For this reason we implemented “dynamic priority” to the main part of the system,
the travelling crane. Still this sophisticated logic was not enough to guarantee good operation,
because in some situations the system runs out of capacity. We then gave recommendations
how to improve the situation for a perfect operation of the production system. For this
purpose we finally made an analysis of the necessary investment costs against the running
costs caused by system breakdown. (Erwin Rybin Department of Simulation and
International Networks Austrian Research Center Seibersdorf A-2444 Seibersdorf,
AUSTRIA, Felix Breitenecker Department of Simulation Technique Vienna University of
Technology A-1 040 Vienna, Wiedner Hauptstrasse 8-10, AUSTRIA)

2
In today’s world and era of internet, e-commerce is growing by leaps and bounds keeping the
growth of brick-and-mortar businesses in the dust. In many cases, brick-and-mortar
businesses are resorting to having a counterpart which is internet or e-commerce driven.
People in the developed world and a growing number of people in the developing world now
use e-commerce websites on a daily basis to make their everyday purchases. Still the
proliferation of e-commerce in the under-developed world is not that great and there is a lot
to desire for.

In this study, discrete-event simulation was applied to the improvement of a production

process in the brick industry, with particular emphasis on material handling and transport via
a travelling crane within this process. The simulation deals with a planned manufacturing
plant. The aim of the simulation is to prove, if the planned capacity of the components is
sufficient. We got the layout of the plant in CAD-format and the data (capacities, cycle times,
etc.) in EXCEL. The simulation was just for security reasons; the company plans to build the
plant on this given data.

Designing e-commerce user interfaces is not an easy task. Therefore, guidelines for designing
a good user's interface are needed for developer. The objectives of this paper is to revise
existing guidelines and rules for designing a good interface and implement it in the e-
commerce website development. An early analysis has been conducted, which is an
evaluation of 2 e-commerce websites. From the evaluation, a number of usability issues have
discovered. A prototype of e-commerce website, namely brickind.com, has been developed.
The guidelines that has been studied and results from the early analysis will be used in
designing the prototype.

This example changes the priority of the crane, depending on the number of products on the
buffer places, the products waiting for being processed on the machines and the number of
products waiting for leaving the system. We also developed a lot of other functions to make
the simulation as realistic as possible. Erwin Rybin Department of Simulation and
International Networks Austrian Research Center Seibersdorf A-2444 Seibersdorf, AUSTRIA

3
1.7. Methodology

a. Data Collection

The data and information needed for this project is collected from various sources and they
are:

i. Primary Source:
The information which is collected through self-involvement is the primary
information. These information are gathered through direct interview with the
organization and the information is more reliable and due to that information we can
gain ideas about what we will do to the system which is benefit for the organization.
ii. Secondary Source:
Other information used for this project is collected through books, websites, and case
studies of previous years of our seniors.

b. Proposed implementation method

This system has been developed using Waterfall Model. In Waterfall Model the requirements
are well known, and it is suitable for all the type of the business projects. It is also known as
inner sequential lifecycle. It is very simple to understand and use. In Waterfall Model, each
phase must be completed before the next phase can begin and there is no overlapping in the
phase. The Waterfall Model illustrates the software development process in a linear
sequential flow. This means that any phase in the development process begins only if the
previous phase is completed. In this Waterfall Model, the phases do not overlap.

For this given system Waterfall Model has been utilized as for the implementation method.

4
Figure 1.1. Waterfall Model

Figure: 1.1 The Waterfall Model

1.7.3. Tools Used

The tools used in development includes:

Draw.io:

Designed by Seibert Media, draw.io is proprietary software for making diagrams and charts.
The software allows you to choose from an automatic layout function, or create a custom
layout. They have a large selection of shapes and hundreds of visual elements to make your
diagram or chart one-of-a-kind. The drag-and-drop feature makes it simple to create a great
looking diagram or chart.

5
Visual Studio Code:

Visual Studio Code, also commonly referred to VS Code, is a source-code editor made by
Microsoft for Windows, Linux and macOS. Visual Studio Code is a source-code editor that
can be used with a variety of programming languages, including Java, JavaScript, Go,
Node.js, Python, C++ and Forton.

1.7.4. Technique of the project report

1.7.4.1. Problem Analysis

The main problem of the organization is that they didn’t have computerized system to
maintain record digitally.

1.7.4.2. Feasibility Analysis

The analysis of the project has led to conclusion that the project is feasible with time and
cost. The tools used for the development is almost Open Source involved less cost and
maintenance.

1.7.4.3. Technical Feasibility

This analysis helps to forecast the future movement. This system is build using Visual studio
code, which are well familiar and stable to us.

1.7.4.4. Operational Feasibility

In this analysis the system is analyzed on how well the proposed system solves the problem
and works in the real environment and how it satisfies the requirement analysis phase of the
system development.

6
 Chapter II

Tasks and Activities Performed

2.1. Analysis of Tasks and Activities

The summer project is of the highlighted subjects which helps to make students be some part
of professional world. Among the various options provided, I used JavaScript based web
system. Similarly, among the various organizations, I selected Sales Management System for
SRY Store, to understand the technical aspects of the real world in an organization.

2.2. Analysis of Possible Solutions

2.2.1. Requirement Analysis

Requirement analysis or requirements engineering is a process used to determine the needs

and expectations of a customer. The main objectives of requirement analysis are to identify
and evaluate the requirement of the proposed system. It helps to know about user
requirements, system requirements, functional requirements and non-functional requirements
for 'Sales Management System for SRY Store'.

2.2.2. Functional Requirement

Functional requirements are product features or functions that developers must implement to
enable users to accomplish their tasks. So, it's important to make them clear both for the
development team and the stakeholders. Generally, functional requirements describe system
behavior under specific conditions. Functional Requirements are also called Functional
Specification.

• Admin can login in the System.

• Customer can give order and they can pay by using the online payment.
• Admin can view the order given by the customer.
• Customer can add to cart the product and can increase quantity..
7
Functional Requirements can be briefly described by the help of Use-Case Diagram which is
shown below:

Figure 2.1: Use Case Diagram of Shree Shankar Itta Udhyog

8
Table 2.1 Use-Case Description (Login)
Use-case UC1-Login
Identifier
Primary Actor Admin and Customer
Secondary None
Actor
Description The admin, customer can login into the same system through a
login form for security.

Pre-Condition The admin and customer have to know the required username
and password.

Post- Condition User can perform required action in the system.

Success Login success message should be displayed.

Scenario
Failure Login failed message should be displayed.
Scenario

Table 2.2 Use-case Description (Manage Products)

Use-case Identifier UC2- Manage Products
Primary Actor Admin, Customer

Secondary Actor None

Description The admin can add the products and view

the products.

Pre-Condition The admin can add and view the records

only after logged in.

Post- Condition The database must be updated after add and

actions is performed.

Success Scenario Latest add action performed success

message is displayed.

Failure Scenario The database is not connected or

misconfigured.

9
Table 2.3 Use-case Description (Manage Order)

Use-case Identifier UC4- Manage Order

Primary Actor Admin

Secondary Actor None

Description The admin can manage the order of the product.

Pre-Condition The admin must check the list of orders.

Post- Condition The database must be updated.

Success Scenario The database must be updated.

Failure Scenario The database is not connected.

Table 2.4 Use-case Description (Update and View)

Use-case Identifier UC3- Update and View

Primary Actor Admin

Secondary Actor None

Description The admin can update the record of products and

customer and view records in table from database.

Pre-Condition The admin can perform the actions on already

recorded data.

Post- Condition The database must be updated.

Success Scenario Updated customers, products info can be viewed.

Failure Scenario The database is not connected.

10
Table 2. 5 Use-case Description (Logout)

Use-case Identifier UC5-Logout

Primary Actor Admin and Customer

Secondary Actor None

Description The actor can logout from the system.

Pre-Condition The admin must be logged in.

Post- Condition The database must be updated.

Success Scenario The successful logout message should be

displayed.

Failure Scenario The logout error message should be displayed.

11
2.2.3. Non-Functional Requirements

Simply said, a non-functional requirement is a specification that describes the system's

operation capabilities and constraints that enhance it's functionality. These may be speed,
security, reliability, etc. Non-functional requirements(NFRs) define system attributes such as
security, reliability, performance, maintainability, scalability, and usability. They serve as
constraints or restrictions on the design of the system across different backlogs.

The non-functional requirements for "Shree Shankar Itta Udhyog Management System" are:

• The SSIU management system will be available to the customers up to 24/7.

• The SSIU management system must be secured with proper username and password.
• All the product details in the system must be accurate and reliable.
• All the data should be secured so that the information will not be breached.

2.2.4. Software Requirements

Table 2.6: Software Requirements

Software Purpose
Draw.io In order to draw the ER-Diagram, Use-
case, Sequence diagram, Class-diagram
and so on.

Visual Studio Code In order to design layouts and to write

code.
Microsoft word To write documentation of the project.

12
2.2.5. Class Diagram

Class Diagram is a UML diagram that represents a static view of a system. It is the
composition of different classes which are linked to each other through association. Class
Diagram can be described with the help of figure shown:

Figure 2.2: Class Diagram

13
2.2.6. Activity Diagram

Activity diagram is another important diagram in UML to describe the dynamic aspects of the
system. Activity diagram is basically a flowchart to represent the flow from one activity to
another activity. The activity can be described as an operation of the system.

Figure 2.3.1: Activity Diagram for User Side

14
Figure 2.3.2: Activity Diagram for Admin side

15
2.2.7. Sequence Diagram:

Figure 2.4: Sequence Diagram

2.2.8. Component Diagram:

Figure 2.5: Component Diagram

16
2.2.9. Deployment Diagram

Figure 2.6: Deployment Diagram

2.2.10. Testing

Testing is the method to check whether the actual software products matches the expected
requirements and to ensure that the software product is defect free. It involves execution of
software/ system components using manual or automated tools to evaluate one or more
properties of interest. The purpose of software testing is to identify errors, gaps or missing
requirements in contrast to actual requirements.

17
Table 2.7. Testing Table

UC01: Login

Unit Test Input Data Actual Result Expected Status

Effected Outcome

Login Username: Admin is logged Admin is logged Pass

[email protected] into the system. in.
Password:
admin123

UC02: Customer Registration

Unit Test Input Data Actual Result Expected Remarks
Effected Result
Add Product [email protected] Email fill is Email fill is Fail
Email= required. required.
Password=priya123

18
 UC03: Add Product

Unit Effected Test Input Data Actual Result Expected Result Remarks

Add Products Product name= As Expected Product added Pass

Brick
successfully.
Price= 17
Description=
Best Quality
Brick
Stock=20000
Image=
Brick1.jpg

UC04: View Orders

Unit Effected Test Input Data Actual Result Expected Remarks

Result
View Orders Click On Display the list Order Details pass
“Cart” of the product Displayed
orders.

2.3. Findings

After analyzing the problems of the organization, it was found that if the organization does
not use automated system for Sales management than it will become time consuming and
confusing. If organization use this Sales management system for recording and managing the
data information in the system then, it will be easy to kept record of those customers who
orders.

19
 Chapter III

Discussion and Conclusion

3.1. Discussion

The system can help to reduce the problems in the organizations, more reliable and consume
less time and afford. The system can provide the information of Customer that orders. The
system is assumed very helpful to the organization. Using this system will make the
organization work faster.

3.2. Conclusion

As per the objectives this system was completed in time. The functionality of the present
programming requires a proper approach towards programming advancement. This SSIU Store
website is intended to make easy for both organizations and customers. The developed system
provides solution to manual online management problems and also provide information such
as product details information, customer information.

This software offers stability, cost-effectiveness and usability. It provides the most flexible and
adaptable standards management system solutions for SSIU Store. User interface will help to
find out how convenient the system is.

20
 REFERENCES

• F&H Simulation. 1996. Taylor 11 User manual, Utrecht: F&H Simulation.

• AUTHOR BIOGRAPHIES ERWIN RYBIN is responsible for industrial and economic
simulations in the Austrian Research Center Seibersdorf. He received Ph.D. and MBA
from the technical university of Vienna, Austria. He works in the field of applied
simulation since 1993. He was project leader in many simulation and process
optimization projects for the European industry. His email and web addresses are
<erwin. rybinoarcs. ac. at> and <www.arcs.ac.at>.
• FELIX BREITENECKER is professor for simulation technique at Vienna University
of Technology (WT). He received M.Sc. and PhD of VUT. He got the venia legend
(prerequisite for professorship in Austria) for “Simulation and Mathematics of
Control”.
• Felix Breitenecker deals with continuous and discrete simulation in teaching, in
research and in industry projects. He is member of SCS, EUROSIM, and IMACS, and
he is past president of EUROSIM, the Federation of European Simulation Societies,
and at present President of ASIM, the German Simulation Society. His main interests
include modem simulation methods, comparison and evaluation of simulators, and
simulation applications in any area. Within ARGESIM, the ARGE Simulation News he
is editor-inchief of the journal Simulation News Europe. His email address: <Felix
.Breitenecker@tuwien. ac. at>.

21
 STUDENT DECLARATION

This is to certify that I have completed the Summer Project entitled “Shree Shankar
Itta Udhyog” under the guidance of Er. Dhiraj Kumar Jha in partial fulfillment of the
requirement for the degree of Bachelor of Information Management at Faculty of
Management Tribhuvan University. This is my original work and I have not submitted
it earlier elsewhere.

Name: Priyanka Kumari Sah

Date: March,2024

Signature:

22
 CERTIFICATE FROM THE SUPERVISOR

This is to certify that the Summer Project entitled “Shree Shankar Itta Udhyog” is an
academic work done by “Priyanka Kumari Sah” submitted in partial fulfillment of the
requirements for the degree of Bachelor of Information Management, Tribhuvan
University under my guidance and supervision. To the best of my knowledge. The
information presented by her in the summer project report has not been submitted
earlier.

……………………
Signature of the Supervisor
Name: Er. Dhiraj Kumar Jha
Designation: Project Coordinator
Date: March, 2024

23
 EXECUTIVE SUMMARY

This report contains the procedure and steps taken to develop the Online Shree Shankar
Itta Udhyog. The aim of this project is to develop a web-based application which can
be used by the organization to automate the process of selling their products. This
application is able to handle a huge number of customers and their orders. It will
definitely boost the efficiency of selling the products. With the user-friendly and
modern User Interface it will surely meet the expectations of the customers. The
technology used for front-end including HTML, CSS with VS-code framework has
been used to develop this system. The system use authentication and authorization for
security of data and information.

24
 ACKNOWLEDGEMENTS

I would like to thank the University for including such a wonderful task in the
curriculum of BIM. Along with that I am thankful to our college Orchid International
College, for providing me the opportunity to gather such practical knowledge and Er.
Dhiraj Kumar Jha, my supervisor for his support to complete this project. I highly
appreciate the efforts shown by my teachers and classmates in the completion of this
project.

Sincerely,
Priyanka Kumari Sah
BIM 6th Semester
Orchid International College

25
 TABLE OF CONTENTS

STANT DECLARATION
CERTARCATE FROMENE PERF
TABLE OF CONTENT
LIST OF FRUBEN
LIST OF TARLAN
LIST OF ARBRETONS
CHAPTER INTRODUCTION
kground

1.2 bendatio Organization

Currere altuation of the organisatio

Puhkem of the report

13 Objective of the regist

16 Mathodology
La Data and buldirmatice.

1.6.2 Prejor famework

161 Tools used

La Feedniques of project report.

1.7 Linrature Review

CHAPTER 1 TASKS AND ACTIVITIES PERFORMED

26
21 Analysis of tusks, activities, problems and issues.
2.1.1.Analysis of Possible solutions

2.1.1.1 System Analysis and Design.

2.1.1.2 ER-Diagram.

2.2 Analysis of possible solution.

2.2.1 Requirement Analysis..

2.2.2 Functional Requirement.

2.2.3 Non-Functional Requirements

2.2.4 Solution Design.

2.2.4.1 Class Diagram...

2.2.4.2 Activity Diagram

2.2.4.3 Sequence Diagram

2.2.5 Testing.

CHAPTER III: LESSON LEARNT AND CONCLUSION.

3.1 Lesson Learnt

3.2 Conclusion

References..Appendices

27
 LIST OF FIGURES

Fig 1.1 Waterfall Model………………………………………………………….

Fig 2.1 Use-case Diagram………………………………………………………..
Fig 2.2 Class Diagram…………………………………………………………..
Fig 2.3 Activity Diagram………………………………………………………..
Fig 2.4 Sequence Diagram……………………………………………………….
Fig 2.5 Component Diagram……………………………………………………..
Fig 2.6 Deployment Diagram…………………………………………………….

28
 LIST OF TABLES

Table 2.1 Use-case Description (Login)

Table 2.2 Use-case Description (Manage Product)

Table 2.3 Use-case Description (Manage Order)

Table 2.4 Use-case Description (Update and view)..

Table 2.5 Use-case Description (Logout)

Table 2.6 Software Requirements

Table 2.7 Unit Testing:

Table UC01 Unit Testing (Login)

Table UC02 Unit Testing (Customer Registration)

Table UC03 Unit Testing (Add Product)

Table UC04 Unit Testing (View Order)

29
 LIST OF ABBREVIATIONS

BIM Bachelor Of Information Management

IT Information Technology

OIC Orchid International College

SSIU Shree Shankar Itta Udhyog

B2C Business to Consumer

OS Operating System

RAM Random Access Memory

SP Summer Project

TC Test Case

UC Use Case

30