Professional Documents
Culture Documents
Two Example of Synopsis
Two Example of Synopsis
1. SYNOPSIS 1.1 Title of the Project: Departmental Store Management System A department
store is a retail establishment which specializes in selling a wide range of products without a
single predominant merchandise line. Department stores usually sell products including apparel,
furniture, appliances, electronics, and additionally select other lines of products such as paint,
hardware, toiletries, cosmetics, photographic equipment, jewellery, toys, and sporting goods.
Certain department stores are further classified as discount department stores. Discount
department stores commonly have central customer checkout areas, generally in the front area
of the store. Department stores are usually part of a retail chain of many stores situated around
a country or several Countries. In other words, a departmental store is a large retail store
suffering a variety of merchandise and services and organized in separate departments. The
Departmental Store Management System is based on the departmental store, which keeps the
track of Inventory, Sales, Purchase & personnel. The system is Management Oriented. This
system gives the management an efficient way to handle their main operational areas such as
customer care, inventory control, point of sales & analysis, Profits.
Duplication of data They also use DOS based systems with monotonous Look Maintaining
records is not Integrated Chances of Information Leakage or Loss of Information increases
The time to access the data increases Increases the paper work 1.2 Problem: In the
departmental stores most of the work is done manually by maintaining registers. This involves
many limitations such as: & duplication of data having many gaps & inefficiency in forecasting
due to batch process or lack of information due to either manual systems or old software. So,
there is a Lack of Tools for manipulation of data.
1.3 Purpose of the Project: Departmental store is a place where we get all our daily use
products. These products are the basic requirements such as clothes, utensils, grocery, toys,
watches etc. From the administrator point of view, the management of these products is not an
easy job. Since they need to keep track of the products, their various suppliers, the customer
details, their employees etc. All these jobs are done mostly manually or using some old
software.
1.4 Scope & Handles the inventory, accounting According to the user, provides the relevant
data Provides Security to the data Objective of Project: The project aims to develop
software which will store data about their different products, their manufactures, product’s
Inventory status, customer records and even the record of their employees. This system
provides accounting, inventory, invoicing information in integrated fashion, preferably with
Graphics User Interface (GUI). The objective of the project is to create a system that: & Less
chances of information Leakage Efficient data storage that will reduce the redundancy of data
Less prone to errors Auto Checking the stocks, Performance of the Employee employee
information
1.8 Conclusion: Here we have tried to develop a software that will help the administrator to have
a quick access to all the information flow in the departmental store.
. INTRODUCTION 2.1 Organization Profile Apna Bazar is a reputed departmental store which
specializes in selling a wide range of products without a single predominant merchandise line. It
sells a variety of different products like appliances cosmetics, photographic equipment,
jewellery, toys, and sporting goods clothes, fashion accessories, cd’s, dvd’s, books, eatables,
etc. Such a market carries large number of transactions on a daily basis like sale of various
products, buying these products from suppliers, recognizing goods that are need to be ordered,
making payments to the supplier etc.
2.2 Introduction to the Project: The main aim of developing departmental store management
system is to build a user friendly, efficient and robust system that will handle all transactions
related to the store. The DSMS i.e. Departmental Store Management System will record details
of all products and information relating sales and current stock of those products. All the
information will be stored in consistent and structured format which will allow easier retrieval of
data. . The system is Management Oriented. This system gives the management an efficient
way to handle their main operational areas such as customer care, inventory control, point of
sales & analysis, Profits.
3. SYSTEM STUDY & ANALYSIS 3.1 Problem Definition: Development of user friendly
departmental store database management system that provides solution for storing product
information, their sales, total stocks, orders and delivery information, customer accounts
information, payments etc. Developing a software the will be useful to the store administrators.
Understanding the system properly so that all it’s problems are identified correctly. Also,
identifying all the alternatives that exists to achieve our objectives with respect to modifying the
system, even all the various way to implement the alternatives.
3.2 Feasibility Study A feasibility study is the study of positive possibilities of the project. It is
also measure of how beneficial or practical development of information system would be to an
organization. The different types of feasibility are as follows:
Economic feasibility Operational feasibility Technical feasibility Scheduled & Resource feasibility
The cost if nothing changes (i.e. the proposed system is not developed) for a project to be
judged feasible, it must pass all these tests. If any one of these issues appears infeasible the
decision must be reconsidered. The benefits in the form of reduced costs or fewer costly
errors. The cost of hardware and software for the class of application being considered.
The cost to conduct a full system investigation If the Organization has adequate cash flow for
funding the development 3.2.1 Economic Feasibility Higher level of automation most often
requires more funds. Hence based on the hardware and software specification a desirable
alternative costs and benefits to see if the investment made in creating / developing a new
system is costlier or more beneficial Financial benefits must equal or exceed the costs. To
assure this one mist estimate following:
The nature Loss of employment due to increased automation. Change of job responsibility.
Loss of control on employee by staff/management. Level of computer competency.
Corporate Culture. 3.2.2 Operational Feasibility A system with an easy interface will always
help the user to use the system. The new system has completely user friendly interface. It has
been designed to be pretty intuitive, so that even an inexperienced person can easily handle the
system. Business functions are reengineered to achieve broader scope and higher level of
automation. Manual processes too are modified. Every company has its own culture and new
system should fit the company culture. The issues to be taken into concern are: & level of user
involvement in the development & It is usually a practice to include people trained in
organizational behavior to assist in managing these changes. Revisal of old, longstanding
work procedures. implementation of system.
3.2.3 Technical feasibility The necessary software required for the development of admission &
Microsoft Access The above as well as required hardware already available in the firm; also
there is required expertise for handling system. Thus in the presence of required hardware,
software the proposed system is technically feasible. Visual Basic 6.0 student profile
systems were:
3.2.4 Scheduled & Resource feasibility The Schedule of the project is actually the periodic
progress of the project. This is carefully monitored. Whenever the upper management indicates
that their has to be a change in the system then the schedule has to be adjusted again and the
schedule is revised. It is the schedule makes to reach the prescribed deadline, which is
invariably revised to suit use requirements. In the resource feasibility, the primary resource is
the team member and their designation i.e. analysts, technician and user have to be managed.
Their skills have to be continuous & updated & revised. A new system variably has less
capability than the organization ultimately desires.
Schedule feasibility : It is measure of how reasonable the project schedule is Are the deadlines
reasonable? Can the deadline be extended? Is the deadline desirable or compulsory if yes how
much?
3.3.1 SYSTEM STUDY: It is always necessary to study & recognize the problem of existing,
which will help in finding out the requirements for the new system. System study helps in finding
different alternative for better solution. The project study basically deals with different operation
& steps:
Data Gathering Study of Existing System Analyzing problem Studying various documents
Feasibility study for further improvement
Then we analyzed the format of the report generated by that system. Then we studied the
config of database we noted the difficulty of that system which motivated them to have new
system. Initially, we collected all the information which they wanted to store . Following are
steps taken during the initial study:
3.4 Current System: A department store is a retail establishment which specializes in selling a
wide range of products without a single predominant merchandise line. A departmental store is
a store which sells a variety of different products like apparel, furniture, appliances, electronics,
and additionally select other lines of products such as paint, hardware, toiletries, cosmetics,
photographic equipment, jewellery, toys, and sporting goods clothes, fashion accessories, cd’s,
dvd’s, books, eatables, etc. Such a market carries large number of transactions on a daily basis
like sale of various products, buying these products from suppliers, recognizing goods that are
need to be ordered, making payments to the supplier etc. Till recently, all such information was
stored in the form of paper. Hence it becomes difficult to manage such vast amounts of
information by the current manual system. Also the information stored on paper is not reliable
and retrieval of any data becomes inconvenient and time consuming. This leads to wastage of a
lot of time, effort and space.
Unorganized data Error prone data Tedious calculation for user Time delay in calculating &
generating reports Complications in analyzing stored data Poor report generation Increases the
paper work Chances of Information Leakage or Loss of Information increases Maintaining
records is not Integrated Duplication of data
They also use DOS based systems with monotonous Look & duplication of data having many
gaps & inefficiency in forecasting due to batch process or lack of information due to either
manual systems or old software. So, there is a Lack of Tools for manipulation of data.
Also the system is intended to take very few inputs from the user. The user interface will be
designed using VB 6.0 and database will be implemented in MS-ACCESS. It will have a
comfortable and user friendly GUI. The developed system will also print bills and reports and
maintain various transactions of the super-market. Access to database will be based on
logon-id and password. Different person will have different login-id and a distinct set of access
rights. Creating a database for the stores containing the information present with them on the
paper in the existing system. 3.5 Proposed system: The proposed system may include
following features:
User friendly, accurate and robust system. Store various product information, it’s supplier
information & their sales. Handle order placing and delivery. Store information about delivery of
orders & their payments. Manage stock of all products. Production of bills. Security of data.
Integration of all functions in to one system. Remove redundancy of data. Remove
inconsistency of data.
4. SYSTEM DEVELOPMENT We have used the waterfall model for developing the system.
Requirement Gathering: The works begins with the information gathering. Developer and
customer meet and define the overall objectives for the software, identify whatever requirements
are known, and outline areas where further definition is mandatory. In our software development
process, we gathered information from the various developers and users to know about the
existing system. This will help us to develop a proposed system. Analysis: After gathering all the
requirements from the user, we need to distribute the various requirements that we have
already collected. We discard the unnecessary requirements & only consider the
relevant requirements. Also some requirements that have not been considered but are very
much needed also need to be discovered to avoid changes in the project in the later stages.
Design: This step focuses on four distinct attributes of the program:
The design process translates requirements into a representation of the software that can be
assessed for quality before coding begins. The design process is documented and become a
part of the software configuration. That means, in a design process we designed the form
layouts of the system, which in turn used for the coding purposes. Coding: In the coding process
the design must be translated into a machine-readable form. If design is performed in a detailed
manner, coding can be accomplished mechanistically. For coding purposes we used Visual
Basic 6.0 language. Testing: The testing process focuses on the logical internals of the
software, ensuring that all statements have been tested, and on the functional externals, that is,
conducting testes to uncover errors and ensure that defined input will produce actual results that
agree with required results. Maintenance: After all of these processes, the maintenance of the
system takes into consideration. It is required because of the errors that have been encountered
in the system or because the customer requires functional or performance enhancements.
Ellipse represents the attributes of the entity. The traditional approach to system development
places a great deal of emphasis on data storage requirements for the new system. Data storage
requirements include the data entities, their attributes, and the relationships among the data
entities. The model used to define the data storage requirements is called the Entity-
Relationship Diagram. For the Departmental Store: Lines connecting the rectangles show the
relationships among data entities. Rectangles represent data entities 4.2 E-R Diagram An
ER-Diagram (Entity Relationship Diagram) is a graphical model of the data needed by a system.
This included the entities about which information is stored and the relationship among them. It
is produced in structured analysis methods. On the Entity-Relationship Diagram:
The departmental store also keeps the information of all of the inventories. Each product is
identified by its product-id. The departmental store also keeps the information of the suppliers.
Each supplier is identified by its supplier-id. It also stores the name, address and product-id that
the supplier can supply. Employees of the departmental store are identified by their
employee-id values. The management stores the name, addresses, position, salary of each
employee. It also keeps track of the employee’s start date and, thus, length of employee.
Customers of the departmental store are identified by their customer-id values. It stores each
customer’s name and address where the customer lives. Customer may have accounts with the
store for their purchasing purposes. The departmental store is organized into branches. Each
branch is located in a particular area and is identified by a unique name. The store monitors the
assets of each branch. DATA REQUIRQMENTS: The data requirements process may be
based on interviews with the database users, and on the designer’s own analysis of the
organization. The major characteristics of the departmental stores are:
The DAMAGES entity set, with attributes Emp_Id, supplier-id, product-id, quantity, price and
replaced. It is a weak entity set. The SUPPLIER entity set, with attributes supplier-id, supplier-
name, product-id, Address and Phone_no. The EMPLOYEE entity set, with attributes
Emp_Id, Ename, Branch_Id, Gender, Address, Phone_no, Date of Birth, Position, Hire_Date,
Salary, Order_Id, Purchase. The CUSTOMER entity set, with attributes Cust_Id, Cname,
Address, Phone_no, Total_Amt and Balance. The STOCK entity set, with attributes supplier-
id, product-id, category, quantity and pay rate. The BRANCH entity set, with attributes branch
no, location, manager, target and sales. ENTITY_SET DESIGNATION: From the
characteristics of the data requirements we begin to identify entity set and their attributes: