MY Project 6sem

SHOPPING COMPLEX MANAGEMENT SYSTEM
CHAPTER I
INTRODUCTION
The project Shopping Complex Management System is a complete desktop

based application designed on PHP. The main aim of the project is to develop
Shopping Complex Management System Model software in which all the
information regarding the stock of the organization will be presented. It is an
intranet based desktop application which has admin component to manage the
shopping complex and maintenance of the shopping complex system. This
desktop application is based on the management of stock of an organization.
The application contains general organization profile, sales details and the
remaining stock that are presented in the organization. There is a provision of
updating the shopping complex also. This application also provides the
remaining balance of the stock as well as the details of the balance of
transaction. Each new stock is created and entitled with the named and the entry
date of that stock and it can also be update any time when required as per the
transaction or the sales is returned in case. Here the login page is created in
order to protect the management of the stock of organization in order to prevent
it from the threads and misuse of the shopping complex.
The information pertaining to the products are stores on an

SQL server side.
1
1.1 PROJECT TITLE
The project work is titled as “SHOPPING COMPLEX MANAGEMENT

SYSTEM”
OBJECTIVES
 Objectives and Scope of the Project
1) To develop the easy management of the inventory.

2) To be able to easily save time.

3) To handle the inventory details like sales details, purchase details and
balance stock details.
4) To provide details information about the stock balance.
2
SYSTEM STUDY & ANALYSIS
1. Proposed System Specifications

The developed web application software fulfils the following specific
requirements:
The following processes have been involved in the Web Based Processing
System.
Login (User/Admin)
Posting (Admin)
Logout (User/Admin)
Login Process
In is the process by which individual access to a computer system is controlled
by identification
Of the user using credentials provided by the user
A user can login to the system to check stocks and sale product and can then log
out or log off
(Perform a logout / logoff) when the access is no longer needed.
User Login Validation:

If the Administrator uses the valid user id and password, he can access the data.
2. FILE STRUCTURE
Source of Input:
Once the registered user login in to the system he/she can check the stock and
sale products. Their inputs will be stored in the respective database table.
Login Table:
The input of the login table is Username and Password. These two are the
primary inputs given by the Admin at the login stage.
3
3. System Users
For every web-based application, complexity is directly proportional to the
number of user categories for the system.
The users of this “INVENTORY MANAGEMENT SYSTEM” can be

categorized into two types. As requirements of all types of users are considered
in development of the system, it can be easily fit to all expectations of all types
of system users of any level. The two types of system users are:
 Admin
 User
Admin: Usually the person in-charge of the software system of the

INVENTORY MANAGEMENT SYSTEM; can Add, Edit
or Update, View Category (in the Category Table),
Subcategory (in the Subcategory Table), Product Details (in
the Product Details Table), Stock (in the Stock Table) and
can check Sell Details and Customer Details; and can also
change password of the admin if needed.
User: A user who is voluntarily interested in selling items from

this application INVENTORY MANAGEMENT SYSTEM;
can register own details to the system by inputs in the login
table giving Username and password of the user at the time
of the login stage and User can check Products Stock and
Sell Products.
4
4. Advantages of the Proposed System

 Saves time and efforts.
 The calculations are accurate.
 Get detailed information of the product easily.
5. Limitations of the Proposed System

 Frequent backups of the database files need to stored, taken in secondary
storage media devices like Optical Disks, External HDDs etc. to prevent
accidental loss.
 If the centralised database server crashes, then all the records will get
lost.
6. Feasibility Study
The main focus of the feasibility study is to determine whether it would
technically and financially feasible to develop the software.
In feasibility study, I tried to find out the feasibility of this system from the
following points of view:
 Economic Feasibility
 Operational Feasibility
 Technical Feasibility
 Time Feasibility
5
Economic Feasibility:
The economic feasibility aims at determining the benefits of the candidate

system, which is accepted if its benefits overweigh the cost involved in the
development of the new system. Primary economic considerations are with
respect to the configuration of the system used. Also, the INVENTORTY
MANAGEMENT SYSTEM can be better managed by the people who know
to use computers by using this system, thus saving precious time. The cost
of such a system is moderately priced, which seems to be feasible enough,
considering the long term benefits that can be obtained from this system.
Thus, the project seems aptly feasible on economic grounds.
Operational Feasibility:
The proposed system provides easy to use features to maintain the

pertaining to the INVENTORTY MANAGEMENT SYSTEM, which is far
better than the manual process of keeping and accessing. Also the system
provides more security, reliability and accuracy in the operational process.
Technical Feasibility:
This involves determining whether the project’s required software

technology and hardware can be procured or not. This project software is
developed using ASP.net(C#) at front end and SQL SERVER 2008 at
backend as the Back-End Database; these technologies are easily available
and can be used to design and implement such a system. Hardware needed
to run this project system is also easily available in the market. So, the
project is technically feasible.
6
Time Feasibility:
It is the determination of whether the proposed project can be

implemented fully within the stipulated frame of time. The total time period
required to develop the software system is around 6 months. Once the
system has been developed, it takes only 2-3 days for getting it installed and
ready for operation. So, considering any desired date of installation, the
project can be easily implemented within the stipulated time period and is
time feasible.
7
DEVELOPMENT ENVIRONMENT
Software Technologies Used

Operating System: Windows 10
Web server: IIS
Web Browser: Internet Explore
Designing Tool: Visual Studio 2010 IDE
Server Side Scripting: ASP.NET (C#) 2008
SQL SERVER:
SQL (pronounced "ess-que-el") stands for Structured Query Language.

SQL is used to communicate with a database. According to ANSI (American
National Standards Institute), it is the standard language for relational
database management systems.SQL statements are used to perform tasks such
as update data on a database, or retrieve data from a database. Some common
relational database management systems that use SQL are: Oracle, Sybase,
Microsoft SQL Server, Access, Ingres, etc. Although most database systems use
SQL, most of them also have their own additional proprietary extensions that
are usually only used on their system. However, the standard SQL commands
such as "Select", "Insert", "Update", "Delete", "Create", and "Drop" can be
used to accomplish almost everything that one needs to do with a database.
This tutorial will provide you with the instruction on the basics of each of these
commands as well as allow you to put them to practice using the SQL
Interpreter.
1) Operating System:
For developing this web application, the latest version of Microsoft’s
Windows operating system, i.e., Windows 10 Pro (Fall Creators Update Version
1709) has been used.
2) Hardware Technologies Used
8
The following main hardware component has been used while developing
the system:
 Processor :Intel Core i3 processor (5th generation)
 Hard Disk : HDD 500GB.
 RAM : RAM 4GB.
9
TECHNICAL REQUIREMENTS OF THE PROJECT
For successful implementation of the project software into the computer

systems, the following minimum hardware and software specifications must be
installed:
Server System:
Hardware : * Intel Pentium or AMD Athlon Processor

* 2GB RAM
* 200 GB Hard Disk Drive
Software : * Web Server- IIS

* Web Browser- HTML5 and JavaScript enabled
browser (e.g. Google Chrome, Mozilla Firefox, and Apple Safari)
* DBMS Software - Oracle 11g

* Operating System- MS Windows / Linux
User System:
Hardware : * Intel Pentium or AMD Athlon Processor

* 512MB RAM
* 20 GB Hard Disk Drive
Software : * Web Browser - HTML5 and JavaScript enabled

browser (e.g. Google Chrome, Mozilla Firefox, and Apple Safari)
*Operating System- MS Windows / Linux
10
SYSTEM DESIGN AND DEVELOPMENT
The goal of the System Design phase is to transform the project system
requirements into a structure that is suitable for implementation in some
programming language. In technical terms, during the system design phase, the
software architecture is derived using information in the System Analysis phase.
Two distinctly different, popular design approaches are: (a) The Procedural
Approach, and (b) The Object-Oriented Approach.
In the development of this project system, we have used ‘the procedural
approach’. This traditional design approach is based on the data flow-oriented
design approach. It consists mainly of the activities of structured analysis and
structured design.
During structured analysis, the functional requirements are decomposed
into sub-functions and the data-flow among these sub-functions is analysed and
represented in the form of DFDs.
After the structured analysis, structured design is undertaken. In this, the system
is decomposed into modules, and the relationships among the modules are
represented in the form of ERDs.
1. Data Flow Diagram

As the information moves through the system, it is modified by a series
of transformations. A Data Flow Diagram (DFD) is a graphical technique that
depicts information flow and the transformations that are applied as the data
moves from input to output. A DFD may be used to represent a system at any
level of abstraction. DFDs may be partitioned into levels that represent
increasing information flow and functional details. A Level-0 DFD, also called
Context Diagram, represents the entire system as a single bubble with input and
output data indicated by incoming and outgoing arrows respectively. Additional
processes and information flows are represented as the Level-0 DFD is
partitioned to reveal more details.
11
Basic notations to create DFD:
The basic notations used to create the DFD are illustrated below:
SYMBOLS DETAILS
External Entity: The producer or

consumer of information that reside
outside the bounds of the system is
to be modelled.
Process: Transformation of
information residing within the
bounds of the system is to be
modified.
Data Flow: The flow of data is
denoted by the arrows. The
arrowhead indicates the direction of
flow of data.
Data Store: A repository of data that
is to be stored for use by one or more
processes may be simple buffer or
sophisticated database.
The Data Flow Diagrams - 0-levels, 1st level and 2nd level for the proposed
system are as follows:
12
13
14
15
16
17
2. E-R DIAGRAM (ENTITY RELATIONSHIP DIAGRAM:

Relationship Diagram represents the relationship between various entities and
their attributes. Relationship between entities makes up a data structure. There
are three types of relationship we can find in an ERD:-
* One-to-one
* One-to-many
* Many-to-many
Symbols used in E-R diagram are as follows:
Entity
Weak entity
Relationship
Attribute
Key attribute
Composite attribute
Identifying relationship
Multivalve attribute
Derived attribute
18
ER Diagram for INVENTORY MANAGEMENT SYSTEM (IMS)
19
20
3. Database Tables for IMS
Table Design: Usually, a collection of interrelated data is referenced to as

database. The database contains information about one particular
enterprise. Database system is designed to store and manage large
volume of information in tables. The management of data involves
both the definition structures of the storage information and
provision for the manipulation of information. In addition, the
database system must provide safety for the information stored in
database tables, despite system crashes or unauthorised access.
i) Table: Admin login
FIELD NAME DATA TYPE CONSTRAINTS
user_name Varchar(50) Primary key
password Varchar(50)
21
ii) Table: Category
Category_id Int Primary key
Category_name Varchar(50)
22
iii) Table: Subcategory
Category_id Int Foreign key
Subcategory_id Int Primary key
Subcategory_name Varchar(50)
23
iv) Table: Product Details
Subcategory_id Int Foreign key
Product_code Int Primary key
Product_name Varchar(50)
Product_description Varchar(200)
product_price float
MFD date
24
v) Table: Stock
Serial_no Int Primary key
product_code Int Foreign key
Stock Int
25
vi) Table: User login
user_name Varchar(50) Primary key
password Varchar(50)
26
vii) Table: Sale Details
Sale_details_id Int Primary key
Sale_id Int Foreign key
Product_code Int Foreign key
Quantity Int
Product_price Float
Total_price Float
27
viii) Table: Sale
Sale_id int Primary key
Sale_date date
Total_amount Float
ix) Table: Customer Details
Sale_id int Foreign key
Customer_id int Primary key
Customer_name Varchar(50)
Customer_phon_no bigint
SYSTEM TESTING
No program or system design is perfect, communication between the user

and the designer is not always complete or clear, and time is usually short. The
result is errors and more errors. Theoretically, a newly designed system should
have all the pieces in working order, but in reality, each piece works
independently. Now is the time to put all the pieces into one system and test it
to determine whether it meets the user requirements. This is the last chance to
detect and correct errors before the system is installed for user acceptance
testing. The purpose of system testing is to consider all the likely variations to
which it will be subjected and then push the system to its limits. It is a tedious
but a necessary step in system development.
28
Test Data:
Preparation of the test data plays an important role in the system testing.
In case the test data are not properly designed, the system designer may not be
able to find some flaws in the system and may have a misconception of having a
perfect system, which may not fulfil the purpose, a sizeable number of synthetic
data having specially set data values, were created so as to test each and every
aspect of the system functions properly after implementation.
Definition of Testing:
The process of analysing a software item is to detect the differences
between existing and required conditions and to evaluate the features of the
software item. Or we can say that testing is a process of analysing a program
with the intent of finding errors.
Types of Testing:
The different types of testing technique that have been used during
development of the system under consideration are as follows:
(a) Module Testing:
This is carried out during the programming stage itself. Individual
programs are tested at the time of coding and necessary changes are
made on the module to make sure that the module, in the form of
individual program is working satisfactorily as regards to the expected
output from the module.
(b) String Testing:

After coding the entire individual programs, string testing is carried
out for each pair of programs where the output generated by one is used
as input to another program. This step is completed after making
necessary changes wherever required.
(c) Unit Testing:
29
Unit testing is essentially for the verification of the code produced

during code phase, that is the goal of this testing is to test the internal
logic of the modules.
(d) Integration Testing:

In this testing, many unit-tested modules are combined into
subsystem which is then tested. The goal of this testing is to see if the
modules can be integrated properly. In other words, the emphasis is on
testing the interfaces between the modules. This testing can be considered
as testing the design.
(e) System Testing:

The purpose of system testing is to identify and correct errors in
the candidate system. As important to this phase is, it is one that is
frequently compromised. Typically, the project is behind schedule or the
user is eager to go directly to conversion. In system testing, performance
and acceptance standards are developed. Substandard performance or
service interruptions that result in system failure are checked during the
test.
(f) Output Testing:

No system could be useful if it does not produce the required
output or in required format. Asking the users about the format required
by generated or displayed by the system under consideration.
Test Report:
Software testing is an important phase in Software Development Life Cycle.
Test summary report is an important deliverable which is prepared at the end of
testing project, or rather after testing is completed.
30
“For testing this software, I have adopted conventional method of testing, i.e., testing of
the software by entering dummy values”
31
GANTT CHART
A Gantt chart is a type of bar chart that illustrates a project schedule.

Gantt charts illustrate the start and finish dates of the terminal elements and
summary elements of a project. Terminal elements and summary elements
comprise the work breakdown structure of the project. Modern Gantt charts also
show the dependency (i.e., precedence network) relationships between
activities. Gantt charts can be used to show current schedule status using
percent-complete shadings.
Jan04 Feb04 March04 April04 May04 June04
32
CONCLUSION & FURTHER ENHANCEMENTS
Concluding Remarks:
The central concept of the application is to allow the customer to shop virtually
using the Internet and allow customers to buy the items and products of their
desire.
The information pertaining to the products are stores on an SQL server side.
The application was designed into two modules first for the customers who
wish to buy and sale the products. Second is for the administration who
maintains the database and updates the information pertaining to the products
and those of the customers.
The application which is deployed at the customer database, the details of the
items are brought forward from the database for the customer view based on the
selection through the menu and the database of all the products are updated.
Further Enhancements:
This project was undertaken for the fulfilment of BCA6 th Semester Major
Project. It helped me in learning how to deal with the software development
activities and to deliver within the given time slots. It is a platform given to me
so that I am able to take up any work given to me if I am going to work in any
organisation in the near future.
This software is still in its β-phase and requires several tweaks and
addition of many important features.
For future scope of the project software, this system can be updated in the
following areas –
 The Design can be made better and more user-friendly.
 The UI can be made more responsive to fit devices of all sizes and
shapes.
 Other areas (as per future needs).
33
APPENDIX A: SNAPSHOT
ADMIN LOGIN PAGE:
34
CATEGORY ADD:
VIEW CATEGORY:
35
UPDATE CATEGORY:
ADD SUBCATEGORY:
36
VIEW SUBCATEGORY:
UPDATE SUBCATEGORY:
37
ADD PRODUCT:
VIEW PRODUCT:
38
UPDATE PRODUCT:
39
ADD STOCK:
VIEW STOCK:
40
ADD USER:
VIEW USER:
41
UPDATE USER:
42
USER LOGIN:
43
USER VIEW STOCK:
SALE PRODUCT:
44
APPENDIX B: BIBLIOGRAPHY
Books Used for Reference:
1. ELMASRI, R. & NAVATHE, IN FUNDAMENTALS OF DATABASE SYSTEMS (5TH EDITION),

PEARSON.
2. MALL, R. IN FUNDAMENTALS OF SOFTWARE ENGINEERING (3 RD EDITION), NEW DELHI: PHI

LEARNING.
3. JONES, A.R. IN ACTIVE SERVER PAGE 3
4. STRUCTURED SYSTEM ANALYSIS AND DESIGN, (ISRD) GROUP, TATA Mc Graw HILL
EDUCATION PRIVATE LIMITED.
5. https://www.w3schools.com
6. https://www.stackoverflow.com
7. https://www.google.co.in
45

MY Project 6sem

Uploaded by

Copyright:

Available Formats

You might also like

MY Project 6sem

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

MY Project 6sem

Uploaded by

Copyright:

Available Formats

SHOPPING COMPLEX MANAGEMENT SYSTEM

The project Shopping Complex Management System is a complete desktop

The information pertaining to the products are stores on an

1.1 PROJECT TITLE

The project work is titled as “SHOPPING COMPLEX MANAGEMENT

 Objectives and Scope of the Project

1) To develop the easy management of the inventory.

4) To provide details information about the stock balance.

SYSTEM STUDY & ANALYSIS

1. Proposed System Specifications

User Login Validation:

The users of this “INVENTORY MANAGEMENT SYSTEM” can be

Admin: Usually the person in-charge of the software system of the

User: A user who is voluntarily interested in selling items from

4. Advantages of the Proposed System

 The calculations are accurate.

 Get detailed information of the product easily.

5. Limitations of the Proposed System

The economic feasibility aims at determining the benefits of the candidate

The proposed system provides easy to use features to maintain the

This involves determining whether the project’s required software

It is the determination of whether the proposed project can be

Software Technologies Used

SQL (pronounced "ess-que-el") stands for Structured Query Language.

 Hard Disk : HDD 500GB.

 RAM : RAM 4GB.

TECHNICAL REQUIREMENTS OF THE PROJECT

For successful implementation of the project software into the computer

Hardware : * Intel Pentium or AMD Athlon Processor

Software : * Web Server- IIS

* DBMS Software - Oracle 11g

Hardware : * Intel Pentium or AMD Athlon Processor

Software : * Web Browser - HTML5 and JavaScript enabled

*Operating System- MS Windows / Linux

SYSTEM DESIGN AND DEVELOPMENT

1. Data Flow Diagram

Basic notations to create DFD:

External Entity: The producer or

2. E-R DIAGRAM (ENTITY RELATIONSHIP DIAGRAM:

Symbols used in E-R diagram are as follows:

ER Diagram for INVENTORY MANAGEMENT SYSTEM (IMS)

3. Database Tables for IMS

Table Design: Usually, a collection of interrelated data is referenced to as

i) Table: Admin login

FIELD NAME DATA TYPE CONSTRAINTS

user_name Varchar(50) Primary key

ii) Table: Category

FIELD NAME DATA TYPE CONSTRAINTS

Category_id Int Primary key

iii) Table: Subcategory

FIELD NAME DATA TYPE CONSTRAINTS

Category_id Int Foreign key

Subcategory_id Int Primary key

iv) Table: Product Details

FIELD NAME DATA TYPE CONSTRAINTS

Subcategory_id Int Foreign key

Product_code Int Primary key