Professional Documents
Culture Documents
Online Shopping For Department of Computer Applications, CUSAT
Online Shopping For Department of Computer Applications, CUSAT
ONLINE SHOPPING
for
Department of Computer Applications, CUSAT
Submitted By:-
MAITREYEE
cusat
1
CERTIFICATE
Head of Department
Official Address
2
ACKNOWLEDGEMENT
SIGNATURE
3
SYNOPSIS:
Title : ONLINE SHOPPING
Duration : 4 months
Application Software
4
CONTENTS
1. Introduction
2. System Study
2.1 Existing System
2.2 Drawbacks in the Existing System
3. System Analysis
3.1 Proposed System
3.2 Scope
3.3 Need for the Proposed System
3.4 Feasibility Study
3.4.1 Technical Feasibility
3.4.2 Financial Feasibility
3.4.3 Operational Feasibility
4. Requirement Analysis
4.1 User Class and Characteristics
4.2 Functional Requirements
4.3 Performance Requirements
4.4 Non Functional Requirements
4.5 External Interfaces Requirements
4.6 General Constraints, Assumptions, Dependencies,
Guidelines
5
5. System Design Specification
5.1 Architectural Design
5.1.1 Data Flow Diagrams
5.1.2 Database Tables
5.1.3 User Case Diagrams
6. Testing
7. Software Quality Assurance Plan
8. Output Screen
Output of Pages
9. Conclusion
10. Scope for further development
11. Bibliography
6
1.INTRODUCTION
Online shopping is the process whereby consumers directly buy
goods, services etc. from a seller interactively in real-time without an
intermediary service over the internet.
7
have any social interaction. It also doesn't allow them to take the
merchandise home the same day they buy it.
Online shopping allows you to browse through endless possibilities, and
even offers merchandise that's unavailable in stores. If you're searching
for a niche product that may not be distributed locally, you're sure to
find what you're looking for on the internet. What's even more useful is
the ability to compare items, similar or not, online. You can search
through multiple stores at the same time, comparing material quality,
sizes and pricing simultaneously.
Shopping via the internet eliminates the need to sift through a store's
products with potential buys like pants, shirts, belts and shoes all slung
over one arm. Online shopping also eliminates the catchy, yet irritating
music, as well as the hundreds, if not thousands, of other like-minded
individuals who seem to have decided to shop on the same day.
Say 'goodbye' to the days when you stood in line waiting, and waiting,
and waiting some more for a store clerk to finally check out your items.
Online shopping transactions occur instantly-saving you time to get your
other errands done! Additionally, unlike a store, online shopping has
friendly customer service representatives available 24 hours a day, 7 days
a week to assist you with locating, purchasing and shipping your
merchandise.
8
2.SYSTEM STUDY
Information systems projects’ originate from many reasons: to
achieve greater speed in processing data, better accuracy and improved
consistency, faster information retrieval, integration of business areas,
reduced cost and better security. The sources also vary project proposals
originate with department managers, senior executives and systems
analysis.
Sometimes the real origin is an outside source, such as a government
agency which stipulates a systems requiremetns the organisattion must
meet. When the request is made, the first systems activity, the
preliminary investigation, begins. The activity has three parts: request
clarification, feasibility study and request approval
2.1 Existing System:
The existing system was an automated system. But
It was found to be inefficient in meeting the growing demands
of population .
2.1.1 Drawbacks in the existing systems:
Disadvantage of the existing system:
Time Consuming
Expensive
Needed an agent
9
3.SYSTEM ANALYSIS
.
• This system is all about the converting the shopping
• system from manual to online.
• Customer can buy products online after login to the site.
• Administrator is adding product to database.
• Administrator can edit or delete the products
from the database.
• After buying and making payment the products are
send to customers address that he has given.
• Customer can write feedback for the product or services.
• Admin can see daily sell and feedback given by customer.
• Administrator is adding the delivery report to the
database.
• Both admin and customer can see the delivery report.
• 3.1 Purpose:
Online shopping tries to enhance access to care and
improve the continuity and efficiency of services. Depending on the
specific setting and locale, case managers are responsible for a
variety of tasks, ranging from linking clients to services to actually
providing intensive shopping and delivery services themselves
Main objective
10
3.2 Scope:
11
Does the system contribute to the overall objectives of the
organizations?
12
organizational conflicts and policies; also external issues,
including social acceptability, legal aspects and government
regulations.
13
4.1 User Class and Characteristics:
1.General public
2. Customers
3.Administrator
Administrator can see the daily sell. Can also see the the
feedback
given by the customer.
14
keeping the daily sell .
Storing the feedback given by the customer.
keeping details about the product it is delivered
or not. etc.
Storing the items selected by the customer in the
temporary storage.
15
iii). Better component design to get better performance
at
peak time.
1. Security
2. Reliability
3. Maintainability
4. Portability
5. Extensibility
6. Reusability
7. Application Affinity/Compatibility
8. Resource Utilization
16
4.5.2 Hardware Interface:
Hardware requirements for Insurance on internet will be same for
both the parties which are follows:
Processor: - Pentium I or above.
HD: - 20 GB or above.
NIC: - For each party
17
There is no maintainability or backup so availability will get
affected.
The system is a single user system.
GUI features available.
18
5. SYSTEM DESIGN SPECIFICATION
19
The symbols used to prepare DFD do not imply a physical
implementation, a DFD can be considered to an abstract of the
logic of an information-oriented or a process-oriented system
flow-chart. For these reasons DFDs are often referred to as
logical data flow diagrams. The four basic symbols used to
construct data flow diagrams are shown below:
These are symbols that represent data flows, data sources, data
transformations and data storage. The points at which data are
transformed are represented by enclosed figures, usually
circles, which are called nodes. The principle processes that
take place at nodes are:
20
1. combining data streams
Gen.user
REQUESTS
use DATA
ST
BASE
customer
user
REQUEST
DATA
BASE ST DATA BASE
ADMIN.
SERVER
ONLINE
ADMIN CUSTOMER
SHOPPING
21
1 LEVEL DFD FOR ADMIN
LOGIN TABLE
ID &PASSWORD
ADMIN VIEW
REJECTED IF NOT LOGIN CUSTOMER
MACHED DETAIL
CUSTOMER
DETAILS
USER TABLE
ADD
PROD
UCTS ADD
&VIEW
DELIVERY
EDIT REPORT
PROD VIEW
VIEW
UCTS FEED DELIVERY DETAILS
DAILY
SELL BACK
ID &PASSWORD
CUSTOMER
REJECTED IF NOT LOGIN
MACHED
VIEW
DELIVERY
REPORT
BUY
PROD
UCTS
22
ER DIAGRAM
prod_name price
prod_id quantity
product
Buy product
phone
no
user_name Sex
dob email_id
make
payment write
feedback
account STORE
feedback
acc no bank name
ORDER_NO
feedback coment REPORT
pin no type
feedbac
k
23
5.1. 2. DATABASE DESIGN:
Primary key: - The field that is unique for all the record
occurrences.
24
DATA BASE TABLE DESIGN:
Category table
Column name Data type Key constraint
Cat_id int Primary key not null
Cat_name Char(20) Not null
PRODUCT TABLE
Column name Data type Key constraints extra
25
Admin Login table
Column name Data type Key constraint
User_id int Primary key not null
password Char(20) Not null
Login table
Column name Data type Key constraint
User_id int Primary key not null
password Char(20) Not null
26
Store table
Column name Data type Key constraint
Order_no int Primary key not null
report Char(20) null
Temp table
Column name Data type Key constraint
Prod_id int Foriegn key not null
Prod_name Char(20) Not null
Price Double Not null
Items Int Not null
User_id Int Not null
Purchage_date Date Not null
Order_no Int null
27
User table
Column name Data type Key constraint extra
User_id int primary key not Auto_increment
null
Password Char(20) Not null
User_name Char(20) Not null
sex Char(6) Not null
Address Char(40) Not null
Feedback table
Column name Data type Key constraint
User_id int not null
type Char(10) Not null
28
Account table
Column name Data type Key constraint
Bank_name Char(20) not null
Account_no Char(20) not null
password Char(20) Not null
balance double Not null
Sell table
Column name Data type Key constraint
Prod_id Int not null
Prod_name Char(20) not null
price Double Not null
items Int Not null
User_id Int Not null
Purchage_date Date Not null
Order_no int Not null
29
5.1.3 USER CASE DIAGRAM:
Login Validate
User
Perform
next task
Information
Logout
User2
30
6. TESTING
Software Testing is an empirical investigation conducted
to provide stakeholders with information about the quality of the
product or service under test, with respect to the context in which
it is intended to operate. Software Testing also provides an
objective, independent view of the software to allow the business
to appreciate and understand the risks at implementation of the
software. Test techniques include, but are not limited to, the process
of executing a program or application with the intent of finding
software bugs. It can also be stated as the process of validating
and verifying that a software program/application/product meets
the business and technical requirements that guided its design
and development, so that it works as expected and can be implemented
with the same characteristics.
31
6.1 Unit Testing:
32
6.2 Integration Testing
33
6.3 Validation testing
: At the validation level, testing focuses on user visible actions and user
recognizable output from the system. Validations testing is said to be
successful when software functions in a manner that can be reasonably
expected by the customer. Two types of validation testing
34
7.Software Quality Assurance Plan
Each development and maintenance project should have a Software
Quality Assurance Plan that specifies its goals, the SQA tasks to be performed,
the standards against which the development work is to be measured, and the
procedures and organizational structure.
The IEEE Standards for the Software Quality Assurance Plans states that the
plan should contain the following sections:
1. Purpose
2. Reference documents
3. Management
4. Documentation
5. Standards, practices and conventions
6. Reviews and Audits
7. Configuration Management
8. Problem reporting and corrective action
9. Tools, techniques and methodologies
10.Code Control
11.Media Control
12.Supplier Control
13.Records collection, maintenance and retention.
35
The purpose of this Software Quality Assurance
(SQA) Plan is to establish the goals, processes, and responsibilities required to
implement effective quality assurance functions for the ONLINE SHOPPING.
The goal of the SQA program is to verify that all software and documentation to
be delivered meet all technical requirements.
2. Reference documents:
3. Management:
An IEEE standard lays down three aspects that should be covered in the
Software Quality Assurance Plan:
36
authority to be able to perform independent verification that the processes
are adhered to.
The following describes the functional groups that influence and control
software quality.
37
Verifying the quality factors are implemented in the system
(software and hardware).
g). Logistics is responsible for:
1. Reviewing and commenting on the “” SQA Plan.
2. Implementing the quality program in accord ONLINE SHOPPING
assurance with this SQA Plan.
h). Software Configuration Management (SCM) is responsible for:
Implementing the SCM practices, processes, and procedures as
defined in reference and other program/project planning documents.
i). Independent Verification and Validation (IV& V) is responsible for:
Implementing the practices, processes, and procedures as defined
for IV&V in program/project planning documents.
j). Systems Engineering Process Office (SEPO) is responsible for:
1. Maintaining the SQA Process.
2. Ensuring SQA training availability.
3. Providing assistance in software process engineering and
software process improvement.
38
Evaluate System Requirements Analysis Process
39
Quality personnel will:
Carry out planned internal audits of the project to assess compliance with
quality objectives.
Agree on corrective action with the project manager for any
discrepancies, non-conformities found and ensure that corrective action is
taken.
Evaluate defect trends and take appropriate action.
4. Documentation:
40
To verify the delivery of a fully conforming, high-quality product,
every individual assigned to the project will participate in quality assurance.
This section describes the procedures used by SQA to verify that the quality
assurance provisions of this SQA Plan and applicable standards, practices,
conventions, and metrics are met.
The review and audits sections of Software Quality Assurance Plan will state
which technical and managerial reviews will be undertaken and how they will
be carried out. The ANSI standard suggests that the following would be a
minimum set of reviews:
41
Critical Design Review: The purpose of this review is to approve the
software detailed design document as a basis for further development
work.
Software Verification Review: The purpose of this review is to approve
the test plan. It is the evaluation of the adequacy and completeness of the
methods described.
Functional Audit: This is held to verify that all the requirements in the
software requirements specification have been met.
Physical Audit: This is held to verify that the software and its
documentation are internally consistent prior to delivery to the user.
In-Process Audit: In-Process audits of a sample design are held to verify
the consistency of the design.
7. Configuration Management:
42
For each problem, some corrective action and a target completion
date should be identified. The appropriate level of management should be made
aware of the problems and adverse trends. The corrective action taken will be
evaluated to ensure that it solved the problem without introducing any new
problems. Management should monitor the status of all unresolved problems.
Tools - SQA software tools include, but are not limited to,
operating system utilities, debugging aids, documentation aids, checklists,
structuring preprocessors, file comparators, structure analyzers, code analyzers,
standards auditors, simulators, execution analyzers, performance monitors,
statistical analysis packages, software development folder/files, software
traceability matrices, test drivers, test case generators, static or dynamic test
tools, and information engineering CASE tools.
Techniques - techniques include review of the use of standards,
software inspections, requirements tracing, requirements and design
verification, reliability measurements and assessments, and rigorous or formal
logic analysis.
Methodologies - methodologies are an integrated set of the above
tools and techniques. The methodologies should be well documented for
accomplishing the task or activity and provide a description of the process to be
used.
Fire Damage
Water Damage
Energy Variations
Structural Damage
Pollution
Unauthorized Intrusion
Viruses and Worms
Misuse of Software, Data and Services.
44
13. Records collection, maintenance and retention:
8. SCREEN SHOTS
45
HOME PAGE
USER PAGE
46
LOGIN PAGE
47
ADMINSTRATOR PAGE
ADMINSTRATOR login
48
REGISTRATION PAGE
49
CUSTOMER DETAILS
PRODUCT PAGE
50
delivery report
FEEDBACK PAGE
51
9. CONCLUSION
This is to conclude that the project that I
undertook was worked upon with a sincere effort. Most of the
requirements have been fulfilled up to the mark and
the requirements which have been remaining, can be completed with a
short extension.
52
11.BIBLIOGRAPHY
53
THANK U
54