Chapter -2

SRS (System Requirements Specification)

2.1. Overview of the existing system

The overall activities in the Existing System the Customer is completely depending on the
manual process for buying the products. Considering the main problem of the manual
shopping system, the major purpose of this proposed system is to organize and manage the
items which is purchase and sold as well as the systems also aim generating the daily,
monthly, semi and yearly transaction reports and receipts for each sold items.
In addition to this some of the main purpose of this project is:
 Advertising products

 Decrease time and resource of customers etc.

 Provide sale and buy service to customer

 Provide good and fast service to customer

2.2. Major functions of the existing system

2.2.1. Business process of the existing system
2.2.2. Players in the existing system (Use cases and descriptions)
3. Use case Diagram
A use case is a sequence of transactions performed by a system that yields an outwardly
visible, measurable result of value for a particular actor. A use case typically represents a
major piece of functionality that is complete from beginning to end. An actor represents
whoever or whatever (person, machine, or other) interacts with the system. The actor is not
part of the system itself and represents anyone or anything that must interact with the
system.
4.1.1. Essential Use Case Description

Use case name Add to cart

Participating Actor Customer

Description The Customer adds the products what he wants to buy to the cart

Precondition The customer must view the products.

Flow of events Basic Action:

1. The customer wants to buy product

2. The customer search product that he wants

3. The customer adds products to his/her cart

4. The use case end

Post condition The item or product is added to the cart.
 Use case name Make payment

Participating Actor Customer

Description Here using the use case, the Customer will pay the bill.

Precondition The customer must select items with in a cart

Flow of events 1. The customer wants to pay bill

2. The customer goes to the sales person
3. The sales person calculates and put total price of the items
4. The customer pays the total price of the items.
5. The use case end
Post condition Receive items from sales person.

Use case name Add new Product

Participating Actor Sales Person

Description The Sales Person Add the product category to the shelf

Precondition The product must available on the shop

Flow of events Basic Action:

1. The Sales Person wants to add new product

2. The Sales Person add the product to the shelf
3. The use case end

Post condition The item is available to sale.

2.2.3. Business rules of existing system

2.2.4. Reports generated, forms ,documents, etc of the existing
system
2.2.5. SWOT Analysis of the existing system
2.3. Problems of the existing system
Some of the problems exist in the system:

 The store opened in a day 10 hours

only.
 There is no advertisement of product.
 It takes more time to processes transaction.
 There is no written items description and price.
 Use more labour.
 It is a time consuming process.
 The customer must be waiting until another customer is served.
 It is easy to stole materials

2.4. Proposed system

The proposed system is concern about the Online Shopping System transaction in order to
provide an alternative solution for the online shopping. For doing activities of the Online
Shopping System such as recording purchased and sold items and generating transaction of it.
And also these new systems protect and secure the Online Shopping System data files in
secured way.

2.5. Methodology & tools

2. 5.1. Data collection methods
We use primary data collection methods have been implemented for the identification of the
problem and understanding the existing system. Some of the methods we use: -

Interview: - The most important method that helps us to get most important and critical
information about the general view of the Shops is by interviewing owner of the Shop
material, seller of the Shop and some customers.

We ask some questions for Example: -

 How do you work currently?

 Have you any computerized system?
 Do you have an items list with their descriptions and price?
 What is the problem of the current system?
 How many employees you have?

We get responses from the persons and they also say that, the current system is used
manual system that means all activates performed by agenda. So that the system is
complex, more time consuming and redundant activity.
Observation: - this method is also used to collect data, done by direct seeing the working
environment. We have observed physically by going to some electronic shop in Hailu
electronic center shopping. Also we observed that there is no any computerized system in
the Shop and also information about the Shop and the service that the Shop provides were
not available easily. The team also observes that ordering is only by face to face.

2. 5.2. Hardware and software tools (Including programming

platforms, software tools, hardware devices etc)
2. 5.2.1. Hardware tools
Laptop: is used to organize our project documentation, implementation and test.

Desktop: is used to organize our project, documentation, implementation and test.

Printer: is device used to print document of our project.

Flash disk and Compact disk (CD): is device used to hold files of our project as a backup
purpose.

Cable connection: is used to refer and see the weakness and strength of different types of
projects done previous on the internet.

2. 5.2.2. Software tools

XAMPP MySQL server: allows users to define the data in database and manipulate that
data.

Notepad: it is an editor for the code.

Unified modelling language (Star UML): is a standardized modelling language, used to

draw all diagram needed

JAVASCRIPT: an object-oriented computer programming language commonly used to

create interactive effects within web browsers.

PHP: PHP (Hypertext Preprocessor) is a widely-used open source general-purpose scripting

language that is especially suited for web development and can be embedded into HTML.

Microsoft word: for the preparation of the documentation.

Microsoft power point: for the preparation of slide.

2.5.3. Minimum hardware and software requirements

2.5.3.1. Minimum hardware requirements
 Flash 16 GB
 Laptop
 Desktop
 RAM size 4 GB or more
 Processor speed 2.5 GHZ or more

2.5.3.2. Minimum software requirements

 Web Server Apache
 XAMPP
 Microsoft word office
 UML Visio 2013
 Operating System Microsoft Windows 10 or 11.
 Web Server Apache
 Relational Database Management System MySQL
 Programming languages PHP JavaScript, HTML5.

2.6. System analysis tools & techniques employed (DFD , OOSAD

tools etc.)
2.6.1. Data flow diagram
Shopping system data flow diagram is used to shows how data flows in a system.

Based on Hailu electronic center system activities, we represent the flows of data as follows:
2.7. Requirement analysis
2.7.1 .Functional requirements
The Functional Requirements Specification documents the operations and
activities that a system must be able to perform. Functional requirements should
include functions performed by specific screens, outlines of work flows
performed by the system, and other business requirements the system must meet

Administrator

 Manages Employees
 Accept feedbacks.
 Update profile.
 View order
 View report
Customer
 Register and login to site.
 View item, add to cart and Remove items from cart.
 Send feed back
 Order product
Warehouse employee
 Add, update and delete products

 View customer order

 Update profile.

2.7.2. Non-functional requirements

Non-functional requirement is a requirement that specifies criteria that can be used to
judge the operation of a system, rather than specific behaviours this requirement dose not
directly affect the performance of the proposed system but, they concerned with : -

 User Interface: - user friendly interface with easy navigational scheme.

 Error handling Mechanism: - handles invalid inputs and display user error in
meaningful messages.

 Security issue: - provides security tasks such as for registering, for modifying
user’s information and viewing needs authentication and authority.
  Maintainability: -When the website fails, it can be maintained easily. What
does it mean to say the web has failed? Over time the number of people using
the system will dramatically grow and customer demands will grow and change.
So this website can easily be rebuilt to fit the evolving customer demands and
the newly arriving changes. So it can be easily maintained and can grow to a
better version.

 Performance: -the performance of our website is measured in terms of load

time and number of requests handled. So it is fast in accepting inputs and
displays the result as well as requires small space.

 Modifiability: -The system is can easily modify or change the given

information.
 Availability: -The system will be available for 24 hours to users with internet
connection.
2.8. Feasibility study
2.8.1Technical feasibility
The proposed system can be technically feasible because the technical resources needed to
develop, install and to operate is available in the present infrastructure. Evaluating the
technical feasibility is the trickiest part of a feasibility study. A number of issues have to be
considered while doing a technical analysis.

Understand the different technologies involved in the proposed system: Before

commencing the project, we have to be very clear about what are the technologies that are to
be required for the development of the new system.

Find out whether the organization currently possesses the required technologies:

Is the required technology available with the organization?

If so is the capacity sufficient?

For instance- “Will the current printer be able to handle the new reports and forms required
fort the new system?”

 The technical issue usually raised during the feasibility stage of the
investigation includes the following:
  Does the necessary technology exist to do what is suggested?
 Do the proposed equipment’s have the technical capacity to hold the data
required to use the new system?
 Will the proposed system provide adequate response to inquiries, regardless
of the number or location of users?

 Can the system be upgraded if developed?

2.8.2. Operational feasibility

The proposed system can be used effectively after it has been developed. Users will
not have any difficulty with the new system to produce the expected benefits.
System will be developed based on the policies of the organization and it doesn’t
require much training for users. And the new system will not place any new
demands on users nor requires any operating changes. Since the proposed system
was to help reduce the hardships encountered. In the existing manual system, the
new system was considered to be operational feasible.

 User-friendly
 Reliability
 Security
 Portability
 Maintainability

2.8.3. Economic feasibility

Economic feasibility attempts to weight the costs of developing and implementing a new
system, against the benefits that would occur from having the new system in place. This
feasibility study gives the top management the economic justification for the new system.
There could be various types of tangible and intangible benefits and costs on account of
automation.

Benefits: the benefits of one system can be expressed in terms of tangible benefit and
intangible benefit.

A. Tangible benefits:

In the project going to be computerized there will be reduction of cost for materials used
for manual operation such as: pen, paper, human power, space needed to keep data record,
and save data storage and time that we are induced or brought in during manual system.
 Intangible Benefits
This refers to benefits that cannot easily be measured in terms of money and with certainty.
Some of the intangible benefits of the proposed system are: -

 It minimizes the work load of the worker

 Efficient work flow
 Increase speed of activity
 Save the loss of documents

 Increase flexibility
 On time information
 Increase security

2.8.4. Schedule feasibility

As we know planning is the first phase of any system so we need to start with the schedule
programs and our project is intended to be with in fixed time interval. Unless and otherwise
we may fall in difficulty in cost estimation and as well as we may fall in the financial
problem.