 Iterate the above steps as needed to complete the analysis.

2.1 Identification of needs.

The problem occurred before having computerized system includes:

 Filelost:-
When computerized system is no timplemented file is always lost
because of human environment. Some times due to some human
error there may be a loss of records.

 Filedamaged:-
When a computerized system is not there file is always lost due to
some accdent like spilling of water by some member on file
accidentally. Besides some natural disaster like floods or fires may
also damage the files.

 Difficult to search record:-

When there is no computerized system there is always a difficulty
in searching of records if the records are large in number .
 Space consuming:-
Afterthenumberofrecordsbecomelargethespaceforphysicalstorage
offileand records also increases if no computerized system is
implemented.
 Cost consuming:-
As there is no computerized system the to add each record paper
will be needed which will increase the cost for the management of
library.

2.2 Project Planning.

I studied and went through all set of tasks and activities regarding software
and identified them before project and also the time required for the

14
completion of project. Planning helped me in decision-making process
while I was studying how to initiate and what steps to follow to accomplish
the task. I also planned to finish the assigned task within appropriate cost,
effort, and resources to maintain the system feasible.

My planning was about all kinds of resources required and estimation

regarding total cost. I also finalized how much time it will take to launch the
web site with in the given constraint of the cost, effort and resources. In
resources I also considered human resources, reusable software resources
and environmental resources.

2.3 Project Scheduling.

Software project scheduling is an activity that distributes estimated effort

across the planned project duration by allocating the effort to specific
software engineering tasks. Every project has a deadline to complete. So,
software projects also have a deadline to meet. To complete a software
project within a time frame, proper scheduling should be done. In other
words, we can say that successful software projects are those that have
been successfully placed a schedule.

A software project scheduling involves plotting project activities against a

time frame. So, the scheduling is about developing a road map structure or
a network based on analysis of the tasks that must be performed to
complete the projects. The schedule evolves over time. During early stages
of project planning, a microscopic schedule is developed. This type of
schedule identifies all major software-engineering activities and the
product functions to which they are applied. As the project gets under way,
each entry on the macroscopic schedule is refined into a detailed schedule.
Here, specific software tasks are identified and scheduled. The scheduling
objective is to define all project tasks, build a network that depicts their
interdependencies, identity the tasks that are critical within the network,
ant then track their progress to ensure that delay is recognized “ one Day at
a time”.

2.4 Software Requirement Specification.

15
The Software Requirement Specification (JSMS) for the JEWELLERY SHOP
MANAGEMENT SYSTEM outlines the detailed requirements necessary for
the development and implementation of the system. This document serves
as a guide to ensure that the system meets the needs of all stakeholders,
providing a clear framework for its design, development, and testing.

The JEWELLERY SHOP MANAGEMENT SYSTEM must be capable of An

Jewellery Shop The main goal of this project was to create shopping cart,
which allows customers to shop and purchase the Jewellery products
online.Moreover, the project is also designed in such a way it lets managers
manage theproducts information. Customers can orders products, and they
will be contacted tofurther process the orders.

2.4.1 Functional Requirements.

What are the inputs to be given to the system and what output should be
generated this is called the Functional Requirement for any system. They
describe the relationship between the input and output of the system.

User Friendly Interfaces

Shopping cart is one of the important facility provided in online shopping, this lets
customer to browse different goods and services and once they select an item
topurchase they can place the item in shopping cart, and continue browsing till the
final selectionhave in the database. Limited access is available to the operator. As
this is generic software it can be used by a wide variety of outlets (Retailers and
Wholesalers) to automate the process of manually maintaining the records related
to the subject of maintaining the stock and cash flow:

a) Administrative Support Module (ASM):

This division works directly for the Administrator. The Administrator uses their
power to enter their user name and password. The following events
Administrator :-
 Registration and Cancellation of User.

16
  Adding, Updating and Deleting etc.
 Searching various things.

b) User Support Module (USM):

Here the user is that which does the administrator register. Administrator gives
him a user name and password, which helps him to authorized entry in the site.
After authorized entry a user can add, update and search the information. The
deletion power is not given for the user. This power is only for the administrator.

c) Visitor Support Module (VSM):

There are so many visitors, who can visit this site daily. The VSM support the
visitors to visit the site easily and frequently. They can use the Premium Services
of the site to take the information about the Jewellery Shop.

2.4.2 Non-Functional Requirements.

This describes the non-functional requirements of the system. Non-functional

requirements are those requirements that constitute the overall attributes of the
system such as portability, performance, security, etc.

 User Login

This module is used to authenticate user to access the system. When user enters
login corresponding password of the user is matched so as to prevent
unauthorized access

Web Application Architecture and its Required Tools.

To understand the web architecture the two things must be known one is web
browser and another is web server. Web browsers and servers cooperate to

17
provide content to a user. Consider a request for a static Web page. A user enters
a URL into a browser. The browser generates an HTTP request to the
appropriate we4b server. The web server maps this request to a specific file.
That file is returned in a HTTP response to the browser. The HTTP header in the
response indicates the type of text/plain.

The Web Browser

The web browser can be thought of as a universal user interface. Whether you’re
doing some simple web browsing or transacting online banking, the web
browser’s responsibilities are that of presenting web contents, issuing request to
the web server, and handling any results generated by the request. The ubiquity
of browsers, the generic HTML and Internet access is what makes this
interesting.

The Web Server

The web server is the heart of any web application. The web server is a program
running on the server that listens for incoming requests and generate the
responses according to the requests. Depending on the type of request, the web
server might look for a web page, or it might execute a program on the server.
Either way, it will always return some kind of results to the web server, even if
it’s simply an error message saying that it couldn’t process the request.

2.4.3 Software and Hardware Requirements.

Platform : Windows XP

RDBMS/Database : MY SQL 4.0

Language : PHP

18
 Internet Technology : HTML, PHP, Java Script, CSS

Server : Xamp or Wamp

Machine : Pentium III 733 MHZ

Main Memory : 128 MB

Hard Disk : 20 GB

Cache Memory : 256 KB.

Mouse, Floppy Drive, Extended keyboard, CD-ROM Drive, Monitor,

Printer, Backup device, UPS and Internet connection.

2.5 Software Engineering Paradigm Applied.

THE WATERFALL MODEL

Software development proceeds sequentially in the waterfall model. It is

the simplest and most widely used process model, The very first phase
starts from the planning through analysis, design, coding, testing and
implementation.The model is also referred to as the linear sequential
model or the software life cycle.

19