Vous êtes sur la page 1sur 12

DepartmentalStoreAutomation

SoftwareRequirementsSpecification
Version1.0
04/07/2015

Anand.K

Preparedfor
MCA
FinalYearProject
Instructor:BlessanPVarghese
2015

DepartmentalStoreAutomationSystem

TableofContents

INTRODUCTION........................................................................................................................3
Methodology.
3
PURPOSE......................................................................................................................................3
SCOPE..........................................................................................................................................4
DEFINITIONS,ACRONYMS,ANDABBREVIATIONS.......................................................................4
REFERENCES................................................................................................................................4
OVERVIEW....................................................................................................................................4
GENERALDESCRIPTION.........................................................................................................4
PRODUCTPERSPECTIVE...............................................................................................................4
PRODUCTFUNCTIONS...................................................................................................................5
Problemofexistingsystem
.. 5
USERCHARACTERISTICS..............................................................................................................6
GENERALCONSTRAINTS..............................................................................................................7
TechnicalFeasibility.
7
BehavioralFeasibility..
7
EconomicFeasibility
7
SPECIFICREQUIREMENTS.....................................................................................................8
SoftwareRequirement.
8
2

DepartmentalStoreAutomationSystem
HardwareRequirement.
8
FUNCTIONALREQUIREMENTS......................................................................................................9

Introduction

Methodology
Prototyping
Software prototyping is the activity of creating prototypes of software applications, i.e.,
incomplete versions of the software program being developed. It is an activity that can occur
in software development and is comparable to prototyping as known from other fields, such
as mechanical engineering or manufacturing.
A prototype typically simulates only a few aspects of, and may be completely different from, the
final product. Prototyping has several benefits: The software designer and implementer can get
valuable feedback from the users early in the project. The client and the contractor can compare
if the software made matches the software specification, according to which the software
program is built. It also allows the software engineer some insight into the accuracy of initial
project estimates and whether the deadlines and milestones proposed can be successfully met.

Purpose
This project is aimed at developing an online Sales and Inventory Management System (SIMS)
for a departmental store. This system can be used to store the details of the inventory, update the
inventory based on the sale details, produce receipts for sales, generate sales and inventory
reports periodically etc. This is one integrated system that contains both the user component
(used by salespersons, sales managers inventory managers etc) and the admin component (used
by the administrators for performing admin level functions such as adding new items to the
inventory, changing the price of an item etc).
3

DepartmentalStoreAutomationSystem

Scope
DepartmentalstoresinIndiahavegrownatanincrediblepaceandwithitthedemandforstore
managementsystemisgrowing.Thusthroughthisprojectabasicsoftwareisdevelopedtofulfill
thepurpose.Thesoftwaremoduleshavebroadenedthescopeofworkbyprovidingvarious
functionalitiesandallthesefeaturesenablethesoftwaretobecomeuserfriendlyandreliable.

Definitions, Acronyms and Abbreviations


Admin: - Administrator (The Administrator have the authority to add and delete users.

References
Wikipedia - www.wikipedia.com

http://www.w3schools.com
http://www.freeproject.co.in/source/InventoryManagementSystem

Overview
This project is aimed at developing an Inventory Management System for a departmental store.
This system can be used to store the details of the inventory, update the inventory based on the
sale details, produce receipts for sales, generate sales and inventory reports periodically etc. This
is one integrated system that contains both the user component (used by salespersons, sales
managers inventory managers etc) and the admin component (used by the administrators for
performing admin level functions such as adding new items to the inventory, changing the price
of an item etc).
4

DepartmentalStoreAutomationSystem
This system runs on multiple terminals, offers a GUI interface to its users and connects to a
common database(s).

General Description

Product Perspective

The project is developed to automate the working of a Departmental


Store having wide range of products from Food, Electronics to decorative,
toiletries etc. A l l t h e p r o d u c t s a r e t o b e r e s t o c k e d i n t h e
D e p a r t m e n t a l S t o r e d e p e n d i n g o n t h e i n v e n t o r y a n d t h e r e q u i r e m e n t raised
when the stock of that item is low. The warehouse department keeps record of goods in stock.
The gatekeeper d o e s t h e g a t e e n t r y o f t h e v e h i c l e s c a r r y i n g t h e p r o d u c t s .
S a l e o f a n y product will directly debit the quantity of goods from the amount of stock with
the front shop inventory, along with the details of the counter selling it and the details of the
goods being sold, the time of sale etc.

Product Functions

This project will serve the following functions:1 Add and maintain records of available products.
2 Add and maintain customer details.
3 Add and maintain description of new products.
4 Add and maintain new entered category of products.
5 Provides economic/financial reports to the owner monthly or weekly and yearly.
6 Provides a convenient solution of billing pattern.
7 Make an easy to use environment for users and customers.
5

DepartmentalStoreAutomationSystem

Problem of existing system

1. Inability of modification of data: The managing of huge data effectively and efficiently for
efficient results, storing the details of the consumers etc. in such a way that the database can be
modified as not possible in the current system.
2. Not user friendly: The existing system is not user friendly because the retrieval and storing of
data is slow and data is not maintained efficiently.
3. Difficulty in reports generating: Either no reports generating in a current system or they are
generated with great difficulty reports take time to generate in the current system.
4. Manual operator control: Manual operator control is there and lead to a lot of chaos and errors.
5. Lot of paperwork: Existing system requires lot of paper work and even a small transaction
require many papers fill. Moreover any unnatural cause (such as fire in the organization) can
destroy all data of the organization. Loss of even a single paper led to difficult situation because
all the papers are interrelated.
6. Inability of sharing the data: Data cannot be shared in the existing system. This means that no
two persons can use the same data in existing system. Also the two departments in an
organization cannot interact with each other without the actual movement of data.
7. No support in decision-making: Existing system does not support managerial decisionmaking.
8. No support in strategic competitive advantage: Existing system do not support strategic
competitive advantages.

User Characteristics

1. Easiness in modification of data: The proposed system provides managing of huge data
effectively and efficiently for efficient results, storing the details of the customers, employees
etc. in such a way that the database can be modified.

DepartmentalStoreAutomationSystem
2. User friendly: The proposed system is user friendly because the retrieval and storing of data is
fast and data is maintained efficiently. Moreover the graphical user interface is provided in the
proposed system, which provides user to deal with the system very easily.
3. Reports are easily generated: Reports can be easily generated in a proposed system. So any
type of reports can be generated in a proposed system, which helps the managers in a decisionsmaking activity.
4. Sharing the data is possible: Data can be shared in proposed system. This means that two or
more persons can use the same data in existing system provided that they have right to access
that data. Also the two or more departments in an organization can easily interact with each other
without the actual movement of data.
5. No or very few paperwork: The proposed system either does not require paper work or very
few paper works is required. All the data is feted into the computer immediately and various bills
and reports can be generated through computers. Since all the data is kept in a database no data
of the organization can be destroyed. Moreover work becomes very easy because there is no
need to keep data on papers.
6. Support strategic competitive advantage: Proposed system supports strategic competitive
advantages. Since the proposed systems provide easiness in reports generating it will provide
strategic advantages among competitors.
7. Computer operator control: Computer operator control will be there no errors. Moreover
storing and retrieving of information is easy. So work can be done speedily and in time.

GeneralConstraints
Technicalfeasibility
Technicalfeasibilitycentersontheexistingcomputersystem(hardware,softwareetc)andto
whatextentitcansupporttheproposedsystemaddition.Forexample,ifthecurrentsystemis
operatingat70%capacity(anarbitraryvalue),thenanotherapplicationcouldoverloadthe
systemorrequireadditionalhardware.Ifthebudgetisseriousconstrainthentheprojectis
judgednotfeasible.Thetechnologiesandtheenvironmentwhichareusedinthisprojectarenot
feasible.

DepartmentalStoreAutomationSystem

Behaviouralfeasibility
Anevaluationofthebehavioroftheendusers,whichmayeffecttheenvelopmentofthesystem.
Peopleareinherentlyresistanttochangeandcomputershavetoknowtofacilitatechangesand
computershavetoknowntofacilitatechanges.Anestimateshouldbemadeofhowstronga
reactiontheuserstaffislikelytohavetowardsthedevelopmentofacomputerizedsystem.Itisa
commonknowledgethatacomputerinstallationhassomethingtodowithturnover,transfer,
retrainingandchangesinemployeejobstatus,thereforetheintroductionofacandidatesystem
requiresspecialefforttoeducate,sellandtrainthestaffonnewwaysofconductingbusiness.
Thepersonaloftheuserorganizationwillbeaffectedbytheproposedsystem.Astheaimofthe
systemisonlytosatisfytheinformationneeds,noemployeeswillloosetheirpositionbythe
proposedsystem.Infacttheproposedsystemwillhelptheorganizationinreducingthe
voluminousworkinvolved.Alsotheinvolvementofusersineverystageoftheprojectisgoing
toincreasethesuccessfactor.Thestaffinnotwelleducatedforrunningacomputerizedsystem.
Theyareadamantinperceivingamechanicalprocessofworkingastheyhavelongbeenusedto
themanualentrysystem.Thisaspectneedsconsiderableamountofattention.Oursystemisalso
feasiblefororganizationbecauseitsupportsoftheorganizationanditsstrategicplan.

Economicfeasibility
Theprocedureistodeterminethebenefitsandsavingsthatareexpectedfromacandidatesystem
andcompareitwiththecosts.Ifabenefitoutweighscosts,thenthedecisionismadetodesign
andimplementthesystem.Otherwisefurtheralterationsaremadeintheproposedsystem1.
Manpowercost2.Hardwareandsoftwarecost

SpecificRequirements
Theproductshouldbeeaslyencorperaedintotheexistingsystem.Itshouldhaveauserfriendly
interface.Systemshouldbesimplesoasitcouldbeeaslyunderstoodbytheuser.Thesystem
shouldberobustandsecure.Onlytheinformationrequiredbythespcificusershouldbe
displayedtohim.Everyuserexepttheadministratorshouldhaveonlyristrictedascess.

SoftwareRequirement

DepartmentalStoreAutomationSystem
FrontEnd1.Languageused:ASP.NET.Weusethislanguageissupportseventdriven
programmingfeature.
BackendSupportingSoftware:SQLServer.Thisisusedtostoringdataintheformoftables.It
iseasytouse.
OPERATINGSYSTEM:
Platform:Windows7.

HardwareRequirement

Pentium-i3 (Processor).
4GB Ram
2 MB Cache Memory
Hard disk 500 GB
Microsoft Compatible 101 or more Key Board

FunctionalRequirements

Module wise description


Name of the module-1: Admin
9

DepartmentalStoreAutomationSystem

Description: Can login to the system through the first page of the application and Can create
new user account for an employee and assign (if existing user) username and password.
Sub modules:
Add New Employee

Change Password

Change Price of Item

Add Category

Name of the module-2: Inventory Manager:


Description: Can login to the system through the first page of the application and can do the
following sub module task.
Sub modules:
Check Status Of Item

Change Password

Generate Reports Price and Category wise

Graph For Item

Name of the module-3: Sales Person:


Description: Can login to the system through the first page of the application and can do the
following sub module task.
Sub modules:
Searching Item

Change Password

Produce Bill

Cancel The Produced Bill

Name of the module-4: Sales Manager:


Description: Can login to the system through the first page of the application and can do the
following sub module task.
Sub modules:
Total Money Transactions per day
Change Password
10

DepartmentalStoreAutomationSystem

Bills Per Day

Returned Items Details

11

DepartmentalStoreAutomationSystem