Professional Documents
Culture Documents
01 ACKNOWLEDGEMENT
02 INTRODUCTION
04 PROPOSED SYSTEM
07 SOURCE CODE
08 OUTPUT
09 TESTING
11 BIBLIOGRAPHY
1
PROJECT ON CREATING CLOTH STORE MANAGEMENT SYSTEM
INTRODUCTION
This programme helps the users to add a DATA of customers of all those who does
shopping . Today’s world is full of completions and the only winner of this race is the
one who challenges everybody in that specific field.
This program is one example of how one shop can be different in function from the
other.
The objective of this project is to let the students apply the programming
knowledge into a real- world situation/problem and exposed the students how
2
PROPOSED SYSTEM
Today one cannot afford to rely on the fallible human beings of be really
wants to stand against today’s merciless competition where not to wise saying “to
err is human” no longer valid, it’s out-dated to rationalize your mistake. So, to keep
pace with time, to bring about the best result without malfunctioning and greater
One has to use the data management software. Software has been an ascent
markets, which have helped in making the organizations work easier and efficiently.
Data management initially had to maintain a lot of ledgers and a lot of paperwork has
to be done but now software production this organization has made their work faster
and easier. Now only this software has to be loaded on the computer and work can
be done.
This prevents a lot of time and money. The work becomes fully automated
and any information regarding the organization can beobtained by clicking the
3
SYSTEM DEVELOPMENT LIFE CYCLE (SDLC)
4
PHASES OF SYSTEM DEVELOPMENT LIFE CYCLE
INITIATION PHASE
5
SYSTEM CONCEPT DEVELOPMENT PHASE
6
PICTORIAL REPRESENTATION OF SDLC:
PLANNING PHASE
7
user input. Personnel assignments, costs, project schedule, and target dates are
established.
A Project Management Plan is created with components related to acquisition
planning, configuration management planning, quality assurance planning, concept
of operations, system security, verification and validation, and systems engineering
management planning.
REQUIREMENTSANALYSIS PHASE
This phase formally defines the detailed functional user requirements using
high-level requirements identified in the Initiation, System Concept, and Planning
phases. It also delineates the requirements in terms of data, system performance,
security, and maintainability requirements for the system. The requirements are
defined in this phase to a level of detail sufficient for systems design to proceed.
They need to be measurable, testable, and relate to the business need or
opportunity identified in the Initiation Phase. The requirements that will be used to
determine acceptance of the system are captured in the Test and Evaluation
MasterPlan.
Further define and refine the functional and data requirements and document
them in the Requirements Document,
Complete business process reengineering of the functions to be supported
(i.e., verify what information drives the business process, what information is
generated, who generates it, where does the information go, and who
processes it),
Develop detailed data and process models (system inputs, outputs, and the
process.
Develop the test and evaluation requirements that will be used to determine
acceptable system performance.
8
DESIGN PHASE
9
Business Sponsor, the final System Design Document is created to serve as
the Critical/Detailed Design for the system.
This document receives a rigorous review by Agency technical and functional
representatives to ensure that it satisfies the business requirements.
Concurrent with the development of the system design, the Agency Project
Manager begins development of the Implementation Plan, Operations and
Maintenance Manual, and the Training Plan.
DEVELOPMENT PHASE
10
security and issue a security certification and accreditation prior to
installation/implementation.
Testing as a deployed system with end users working together with contract
personnel
IMPLEMENTATION PHASE
This phase is initiated after the system has been tested and accepted by the
user. In this phase, the system is installed to support the intended business
functions. System performance is compared to performance objectives established
during the planning phase. Implementation includes user notification, user training,
installation of hardware, installation of software onto production computers, and
integration of the system into daily work processes. This phase continues until the
system is operating in production in accordance with the defined user requirements.
11
The purpose of this phase is to:
12
SOURCE CODE(main)
c1=conn.cursor()
c1.execute('use old')
print("WELCOME TO GRAND CLOTH STORE MANAGEMENT
SYSTEM")
print(' ')
from time import gmtime,strftime
a=strftime("%a,%d%b%y",gmtime())
print(a)
print(' ')
print("1.login")
print("2.To create account")
print("")
print('')
choice=int(input("enter your choice:"))
print(' ')
13
if choice==1:
a=int(input("enter user_id:"))
c1.execute("select passwd from login where
user_id = "+str(a)+";")
data=c1.fetchall()
data=data[0]
data=list(data)
data=data[0]
data=str(data)
print(' ')
print(' ')
b=int(input("enter passwd:"))
conn.cursor()
conn.commit()
if choice==2:
print('to create your account please enter
your user id and password')
c1=conn.cursor()
#c1=conn.cursor("('create table
login(user_id varchar(100) primary key,passwd
varchar(100),name varchar(100))')
v_user_id=int(input("choose your user id
(in integer):"))
14
print('')
v_passwd=int(input("create your password
(in integer):"))
print('')
v_name=input("your full name:")
print('')
c1=conn.cursor()
update="insert into login values("+
str(v_user_id) +","+ str(v_passwd) +",'"+
v_name +"')"
c1.execute(update)
conn.commit()
print("account created")
print("if shopping is done press 1.")
print("if you like to file any marketing
problem press 2.")
print("if no shopping is done press 3.")
choice=int(input("enter your choice="))
if choice==1:
v_customer_name=input("enter your name:")
v_gender=input("enter gender:")
v_phone_no=int(input("enter your phone
no:"))
v_items=input("enter item name:")
15
v_qty=int(input("enter quantity:"))
v_payment=int(input("make payment:"))
v_SQL_INSERT="insert into cloth
values('"+v_customer_name+"','"+v_gender+"',"+s
tr(v_phone_no)+",'"+v_items+"',"+str(v_qty)+","
+str(v_payment)+")"
c1.execute(v_SQL_INSERT)
print("THANK YOU...For your visit.")
if choice==2:
c1.execute('USE old')
v_rate_issue=int(input("rate your
difficultes out of 10="))
v_write_problem=input("write your
problem:")
v_SQL_INSERT="insert into sys
values("+str(v_rate_issue)+",'"+v_write_problem
+"')"
c1.execute(v_SQL_INSERT)
print("Your problem will be
rectified....thank you.")
if choice==3:
c1.execute('use old')
v_comment=input("comment about store here
please:")
v_SQL_insert="insert into comment
values('"+v_comment+"')"
16
c1.execute(v_SQL_insert)
print("THANK YOU FOR YOUR VISIT ....WISH
YOU BEST.")
conn.commit()
17
SOURCE CODE(Function calling)
1.
import mysql.connector as sql
conn=sql.connect(host="localhost",user="root",p
asswd="manager",database="old")
if conn.is_connected():
print('successfully connected')
c1=conn.cursor()
c1.execute('create table comment(comment
varchar(200))')
2.
import mysql.connector as sql
conn=sql.connect(host="localhost",user="root",p
asswd="manager",database="old")
if conn.is_connected():
print('successfully connected')
c1=conn.cursor()
c1.execute('create table problem(rate_issue
int(50),write_problem varchar(600))')
18
3.
import mysql.connector as sql
conn=sql.connect(host="localhost",user="root",p
asswd="manager",database="old")
if conn.is_connected():
print('successfully connected')
c1=conn.cursor()
c1.execute('create table login(name
varchar(50),user_id varchar(30)primary
key,passwd varchar(20))')
4.
import mysql.connector as sql
conn=sql.connect(host="localhost",user="root",p
asswd="manager",database="old")
if conn.is_connected():
print('successfully connected')
c1=conn.cursor()
c1.execute('create table old( v_customer_name
varchar(40),gender varchar(20),v_phone_no
int(50),v_items varchar(100),v_qty
int(20),v_payment int(30)')
19
OUTPUTS:--
WELCOME TO GRAND CLOTH STORE MANAGEMENT SYSTEM
Fri,03Jan20
1.login
2.To create account
enter your choice:2
To create your account please enter your user
id and password
choose your user id (in integer):6076
account created
if shopping is done press 1.
if you like to file any marketing problem press
2.
if no shopping is done press 3.
20
WELCOME TO GRAND CLOTH STORE MANAGEMENT SYSTEM
Fri,03Jan20
1.login
2.To create account
enter user_id:6076
enter passwd:6076
if shopping is done press 1.
if you like to file any marketing problem press
2.
if no shopping is done press 3.
enter your choice=1
enter your name:abhishek
enter gender:male
21
enter your phone no:9784625398
enter item name:jeans
enter quantity:2
make payment:5000
THANK YOU...For your visit.
22
TESTING
TESTING METHODS
Software testing methods are traditionally divided into black box testing and
white box testing. These two approaches are used to describe the point of view that
a test engineer takes when designing test cases.
SPECIFICATION-BASED TESTING
23
the output value (or behaviour), either "is" or "is not" the same as the expected value
specified in the test case. Specification-based testing is necessary, but it is
insufficient to guard against certain risks
The black box tester has no "bonds" with the code, and a tester's perception
is very simple: a code must have bugs. Using the principle, "Ask and you shall
receive," black box testers find bugs where programmers don't. But, on the other
hand, black box testing has been said to be "like a walk in a dark labyrinth without a
flashlight," because the tester doesn't know how the software being tested was
actually constructed.
That's why there are situations when (1) a black box tester writes many test
cases to check something that can be tested by only one test case, and/or (2) some
parts of the back end are not tested at all. Therefore, black box testing has the
advantage of "an unaffiliated opinion," on the one hand, and the disadvantage of
"blind exploring," on the other.
White box testing, by contrast to black box testing, is when the tester has
access to the internal data structures and algorithms (and the code that implement
these)
24
CODE COMPLETENESS EVALUATION
White box testing methods can also be used to evaluate the completeness of
a test suite that was created with black box testing methods. This allows the software
team to examine parts of a system that are rarely tested and ensures that the most
important function points have been tested.
25
HARDWARE AND SOFTWARE REQUIREMENTS
HARDWARE REQUIREMENTS:
SOFTWARE REQUIREMENTS:
I. Windows OS
II. Python
26
BIBLIOGRAPHY
27