INFORMATICS PRACTICES PROJECT FILE

Project Report on
STUDENT RESULT MANAGEMENT SYSTEM
INFORMATICS PRACTICES
FOR
CLASS XII
(2023-24)
Submitted in partial fulfillment of the requirement of CBSE, Delhi
M.Meenakshi
REG NO: 20672919

UNDER THE GUIDANCE OF

Mrs. R. SUGANTHI M.C.A., M.E.,
(P.G.T Informatics Practices)

Mahatma Global Gateway (CBSE)

 Gopalakrishnan
Guruvasal,
Veerapanchan,
Madurai-625 020.

Mahatma Global Gateway (CBSE)

Gopalakrishnan Guruvasal,
Veerapanchan, Madurai-625 020.

INFORMATICS PRACTICES
2023-2024

BONAFIDE CERTIFICATE

This is to certify that this project entitled “GARMENT

MANAGEMENT SYSTEM” is a record of bonafide of work
carried out by MEENAKSHI.M [Reg No: 20672919] in
partial fulfillment of the requirements in Informatics
Practices prescribed by CBSE for AISSCE 2023-2024 in the
school Mahatma Global Gateway (CBSE), Madurai –
625020.

Submitted for the viva-voce examination held on , at

Mahatma Global Gateway (CBSE), Madurai.

Internal Examiner External Examiner

Principal

DECLARATION
I hereby declare that the project work

entitled

“GARMENT MANAGEMENT SYSTEM” submitted to

MAHATMA GLOBAL GATEWAY (CBSE) for the

Subject “INFORMATICS PRACTICES” under the

guidance of
 R. SUGANTHI (PGT IP) is a record of original work done

by me. I further declare that this project record or any part of

this has not been submitted elsewhere for any other Class.

Place: Mahatma Global Gateway (CBSE), Madurai-625 020.

Date :

Signature of the student

ACKNOWLEDGEMENT

At the outset I would like to take the opportunity of

expressing my sincere thanks to the Almighty for keeping me
in good health all through this grueling project work.

I would like to express my special thanks to my worthy

Academic Director Mrs. P. Hamsa Priya, Principal Mrs.
Meena Karuppiah and to my teacher guide Mrs. R. Suganthi
who provided motivation and valuable guidance to complete
this project.

I got ample opportunity to do research which enriched

my knowledge and widen my thoughts in this arena. I am
indebted to them.

I would also like to thank my parents and friends who

always inspired and helped me to complete this project.

Signature of the
student
TABLE OF CONTENTS
S.NO DESCRIPTION PAGE NO
01 INTRODUCTION 05
02 OBJECTIVES OF THE PROJECT 05
03 SCOPE OF THE PROJECT 06
04 HARDWARE AND SOFTWARE REQUIREMENTS 07
05 SYSTEM DEVELOPMENT LIFE CYCLE (SDLC) 08
06 SOURCE CODE 16
07 OUTPUT 19
08 TESTING 20
09 FUTURE ENHANCEMENT
10 CONCLUSION 23
11 BIBLIOGRAPHY
INTRODUCTION

This software project is developed to automate the functionalities of a User Friendly

Clothing Store. The purpose of the software project is to develop a program which

provides a friendly interface for the user to explore the products of the clothing store

and buy them according to their choice. This program mainly brings forth the usage of

GUI programming in the daily usage over the network. The program when made to

work over the network can prove to be an ultimate way of interaction between the user

and the store.

A MIS mainly consists of a computerized database, a collection of inter-related tables

for a particular subject or purpose, capable to produce different reports relevant to the

user. An application program is tied with the database for easy access and interface to

the database. Using Application program or front-end, we can store, retrieve and

manage all information in proper way.

This software, being simple in design and working, does not require much of training

to users, and can be used as a powerful tool for the automating the Clothing Store.

During coding and design of the software Project, Java NetBeans IDE, a powerful front-

end tool is used for getting Graphical User Interface (GUI) based integrated platform

and coding simplicity. As a back-end a powerful, open source RDBMS, My SQL is used

as per requirement of the CBSE curriculum of Informatics Practices Course.

Objective & Scope of the Project

The objective of the software project is to develop a computerized MIS to automate the

functions of a Clothing Store. This software project is also aimed to enhance the

current record keeping system, which will help managers to retrieve the up-to-date

information at right time in right shape.

The proposed software system is expected to do the following functionality-

✓ To provide a user friendly, Graphical User Interface (GUI) based integrated and

centralized environment for MIS activities.

✓ The proposed system should maintain all the records and transactions, and should

generate the required reports and information when required.

✓ To provide graphical and user-friendly interface to interact with a centralized database

based on client-server architecture.

To identify the critical operation procedure and possibilities of simplification using

modern IT tools and practices.

In its current scope, the software enables user to retrieve and update the information from

centralized database designed with MySQL. This software does not require much training time
of the users due to limited functionality and simplicity.

During the development of Clothing Store "Vogue" project, Java NetBeans IDE, a powerful.

open source event-driven form-based development environment is used for modular design and

future expandability of the system.

Despite of the best effort of the developer, the following limitations and functional boundaries

are visible, which limits the scope of this application software.

1. This software can store records and produce reports in pre-designed format in soft copy.

There is no facility yet to produce customized reports. Only specified reports are

covered.

2. There is no provision to calculate fine or penalty etc. for defaulter members; however it

can be developed easily with the help of adding modules.

3. Some application areas like updation of stock, saving of last purchase etc. are not

implemented in the project. It facilitates the buyer to go through the products of the store

and choose as per his wish to buy the product. This project is made by keeping in mind

that it is to be used over the network, which can facilitate ease of shopping

So far as future scope of the project is concerned, firstly it is open to any modular expansion Le.

other modules or functions can be designed and embedded to handle the user need in future. Any

part of the software and reports can be modified independently without much effort.
 SYSTEM SPECIFICATION

HARDWARE REQUIREMENTS:

I.OPERATING SYSTEM :
WINDOWS 7 AND ABOVEC
II. PROCESSOR :
PENTIUM(ANY) OR AMD

ATHALON(3800+- 4200+ DUALCORE)

 MOTHERBOARD : 1.845 OR 915,995 FOR PENTIUM
0R MSI

K9MM-V VIAK8M800+8237R
PLUS CHIPSETFOR AMD
ATHALON
 RAM : 512MB+
 Hard disk : SATA 40 GB OR ABOVE
 CD/DVD r/w multi drive combo: (If back up required)
 FLOPPY DRIVE 1.44 MB : (If Backup required)
 MONITOR 14.1 or 15 -17 inch
 Key board and mouse
 Printer : (if print is required – [Hard copy])

SOFTWARE REQUIREMENTS:

 Operating System: Windows OS

 Programming Language: Python
 Database: MySQL
 SOFTWARE DESCRIPTION

PYTHON :

Python is a high-level, interpreted, interactive and object-oriented scripting

language. Python is designed to be highly readable. It uses English keywords
frequently where as other languages use punctuation, and it has fewer
syntactical constructions than other languages.

 Python is Interpreted − Python is processed at runtime by the

interpreter. You do not need to compile your program before executing
it. This is similar to PERL and PHP.

 Python is Interactive − You can actually sit at a Python prompt and

interact with the interpreter directly to write your programs.

 Python is Object-Oriented − Python supports Object-Oriented style

or technique of programming that encapsulates code within objects.

 Python is a Beginner's Language − Python is a great language for the

beginner-level programmers and supports the development of a wide
range of applications from simple text processing to WWW browsers to
games.

History of Python:

Python was developed by Guido van Rossum in the late eighties and early
nineties at theNational Research Institute for Mathematics and Computer Science
in the Netherlands.

Python is derived from many other languages, including ABC, Modula-3, C,

C++, Algol-68,SmallTalk, and Unix shell and other scripting languages.

Python is copyrighted. Like Perl, Python source code is now available under
the GNU GeneralPublic License (GPL).

Python is now maintained by a core development team at the institute,

although Guido vanRossum still holds a vital role in directing its progress.
Python Features:

Python's features include −

 Easy-to-learn − Python has few keywords, simple structure, and a

clearly definedsyntax. This allows the student to pick up the language
quickly.
 Easy-to-read − Python code is more clearly defined and visible to the
eyes.

 Easy-to-maintain − Python's source code is fairly easy-to-maintain.

 A broad standard library − Python's bulk of the library is very

portable andcross-platform compatible on UNIX, Windows, and
Macintosh.

 Interactive Mode − Python has support for an interactive mode

which allowsinteractive testing and debugging of snippets of code.

 Portable − Python can run on a wide variety of hardware platforms

and has the sameinterface on all platforms.

 Extendable − You can add low-level modules to the Python

interpreter. These modulesenable programmers to add to or customize
their tools to be more efficient.
 Databases − Python provides interfaces to all major commercial
databases.

 GUI Programming − Python supports GUI applications that can be

created and ported to many system calls, libraries and windows
systems, such as Windows MFC, Macintosh, and the X Window
system of Unix.

 Scalable − Python provides a better structure and support for large

programs than shell scripting.

Apart from the above-mentioned features, Python has a big list of good
features, few are listed below −
 It supports functional and structured programming methods as well as
OOP.
  It can be used as a scripting language or can be compiled to byte-code
for building largeapplications.
 It provides very high-level dynamic data types and supports dynamic type
checking.

 It supports automatic garbage collection.

 It can be easily integrated with C, C++, COM, ActiveX, CORBA, and

Java.

PANDAS:

Pandas is a software library written for the Python programming language for
data manipulationand analysis. In particular, it offers data structures and
operations for manipulating numerical tables and time series.
To import this library:
import pandas as pd

MATPLOTLIB

Matplotlib is a plotting library for the Python programming language

and its
numerical mathematics extension NumPy.
To import this library:

import
matplotlib.pyplot
as pltimport
numpy as np
 MYSQL

A database system is basically a computer based record keeping system. The

collection of data , usually referred to as the database , contains information
about one particular enterprise. In a typical file-processing system , permanent
records are stored in various file. A number of different application program are
written to extract records from files and add records to the appropriate files A
data management system is answer to all these problem as it provides a
centralized control of the data.
Various advantages of data base system are:

 Data base system reduce data redundancy (data duplication ) to a

large extent.

 Data base system control data inconsistency to a

large extent.

 Database facilitate sharing of data.

 Database enforces standards.

 Centralized data bases can ensure data security.

 Integrity can be maintained through databases.

My SQL is a freely available source Relational Database Management System
(RDMS) that uses Structured query language (SQL). It is downloadable from
site WWW.MYSQL.ORG . In a MYSQL database , information stored in
tables. MYSQL provides you with a rich set of
features that support a secure environment for storing , maintaining ,
accessing data. MYSQLis a fast , reliable , scalable alternative to many of the
commercial RDBMSs available today.

MYSQL was created and is supported by MYSQL AB , a company based

in Sweden (ww.mysql.com) . This company is now a subsidiary of sun micro
systems , which holds the copyright to most of the code base. On APRIL 20,
2009 ORACLE CORP., which develops and sells the proprietary ORACLE
DATABASE, announced a deal to acquire sun Microsystems.

SYSTEM DEVELOPMENT LIFE CYCLE (SDLC)

 The systems development life cycle is a project management technique that divides

complex projects into smaller, more easily managed segments or phases. Segmenting projects

allows managers to verify the successful completion of project phases before allocating resources

to subsequent phases.

Software development projects typically include initiation, planning, design,

development, testing, implementation and maintenance phases. However, the phases may be

divided differently depending on the organization involved.

For example, initial project activities might be designatedasrequest,

requirements-definition, and planningphases, or initiation, concept-developmentand planning

phases. End users of the systemunder development should be involved inreviewing the output of

each phase to ensurethe system is being built to deliver the neededfunctionality.

PHASES OF SYSTEM DEVELOPMENT LIFE CYCLE

INITIATION PHASE

The Initiation Phase begins when a business sponsor identifies a need or an

opportunity.

The purpose of the Initiation Phase is to:

 Identify and validate an opportunity to improve business accomplishments of

the organization or a deficiency related to a business need.

 Identify significant assumptions and constraints on solutions to that need.

 Recommend the exploration of alternative concepts and methods to satisfy the

need including questioning the need for technology, i.e., will a change in the

business process offer a solution?

 Assure executive business and executive technical sponsorship. The Sponsor

designates a Project Manager and the business need is documented in a Concept

Proposal. The Concept Proposal includes information about the business process

and the relationship to the Agency/Organization.

 Infrastructure and the Strategic Plan. A successful Concept Proposal results in

a Project Management Charter which outlines the authority of the project manager

to begin

the project.

Careful oversight is required to ensure projects support strategic business

objectives and resources are effectively implemented into an organization's

enterprise architecture. The initiation phase begins when an opportunity to add,

improve, or correct a system is identified and formally requested through the

presentation of a business case. The business case should, at a minimum, describe

a proposal’s purpose, identify expected benefits, and explain how the proposed

system supports one of the organization’s business strategies. The business case

should also identify alternative solutions and detail as many informational,

functional, and network requirements as possible.

SYSTEM CONCEPT DEVELOPMENT PHASE

The System Concept Development Phase begins after a business need or

opportunity is validated by the Agency/Organization Program Leadership and the

Agency/Organization CIO.

The purpose of the System Concept Development Phase is to:

 Determine the feasibility and appropriateness of the alternatives.

 Identify system interfaces.

 Identify basic functional and data requirements to satisfy the business

need.

 Establish system boundaries; identify goals, objectives, critical success

factors, and performance measures.

 Evaluate costs and benefits of alternative approaches to satisfy the basic

functional requirements

 Assess project risks

 Identify and initiate risk mitigation actions, and develop high-level

technical architecture, process models, data models, and a concept of

operations. This phase explores potential technical solutions within the

context of the business need.

 It may include several trade-off decisions such as the decision to use

COTS software products as opposed to developing custom software or

reusing software components, or the decision to use an incremental delivery

versus a complete, onetime deployment.

 Construction of executable prototypes is encouraged to evaluate

technology to support the business process. The System Boundary Document

 serves as an important reference document to support the Information

Technology Project Request (ITPR) process.

 The ITPR must be approved by the State CIO before the project can move

forward.

PICTORIAL REPRESENTATION OF SDLC:

PLANNING PHASE

The planning phase is the most critical step in completing development,

acquisition, and maintenance projects. Careful planning, particularly in the early

stages of a project, is necessary to coordinate activities and manage project risks

effectively. The depth and formality of project plans should be commensurate with

the characteristics and risks of a given project. Project plans refine the information

gathered during the initiation phase by further identifying the specific activities

and resources required to complete a project.

A critical part of a project manager’s job is to coordinate discussions between

user, audit, security, design, development, and network personnel to identify and

document as many functional, security, and network requirements as possible.

During this phase, a plan is developed that documents the approach to be used and

includes a discussion of methods, tools, tasks, resources, project schedules, and

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 Master

Plan.

The purposes of this phase are to:

 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.

DESIGN PHASE

The design phase involves converting the informational, functional, and network

requirements identified during the initiation and planning phases into unified

design specifications that developers use to

script programs during the development phase. Program designs are constructed in

various ways. Using a top-down approach, designers first identify and link major

program components and interfaces, then expand design layouts as they identify

and link smaller subsystems and connections. Using a bottom-up approach,

designers first identify and link minor program components and interfaces, then

expand design layouts as they identify and link larger systems and connections.

Contemporary design techniques often use prototyping tools that build mock-up
designs of items such as application screens, database layouts, and system

architectures. End users, designers, developers, database managers, and network

administrators should review and refine the prototyped designs in an iterative

process until they agree on an acceptable design. Audit, security, and quality

assurance personnel should be involved in the review and approval process.

During this phase, the system is designed to satisfy the functional requirements

identified in the previous phase. Since problems in the design phase could be very

expensive to solve in the later stage of the software development, a variety of

elements are considered in the design to mitigate risk.

These include:

 Identifying potential risks and defining mitigating design features.

 Performing a security risk assessment.

 Developing a conversion plan to migrate current data to the new system.

 Determining the operating environment.

 Defining major subsystems and their inputs and outputs.

 Allocating processes to resources.

 Preparing detailed logic specifications for each software module. The result is

a draft System Design Document which captures the preliminary design for the

system.

 Everything requiring user input or approval is documented and reviewed by

the user. Once these documents have been approved by the Agency CIO and

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

The development phase involves converting design specifications into executable

programs. Effective development standards include requirements that

programmers and other project participants discuss design specifications before

programming begins. The procedures help ensure programmers clearly understand

program designs and functional requirements. Programmers use various

techniques to develop computer programs. The large transaction oriented

programs associated with financial institutions have traditionally been developed

using procedural programming techniques. Procedural programming involves the

line-by-line scripting of logical instructions that are combined to form a program.

Effective completion of the previous stages is a key factor in the success of the

Development phase.

The Development phase consists of:

 Translating the detailed requirements and design into system components.

 Testing individual elements (units) for usability.

 Preparing for integration and testing of the IT system.

INTEGRATION AND TEST PHASE

Subsystem integration, system, security, and user acceptance testing is

conducted during the integration and test phase. The user, with those responsible

for quality assurance, validates that the functional requirements, as defined in the

functional requirements document, are satisfied by the developed or modified

system. OIT Security staff assesses the system security and issue a security

certification and accreditation prior to installation/implementation.

Multiple levels of testing are performed, including:

 Testing at the development facility by the contractor and possibly supported by

end users

 Testing as a deployed system with end users working together with contract

personnel

 Operational testing by the end user alone performing all functions.

Requirements are traced throughout testing, a final Independent Verification &

Validation evaluation is performed and all documentation is reviewed and

accepted prior to acceptance of the system.

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.

OPERATIONS AND MAINTENANCE PHASE

The system operation is on-going. The system is monitored for continued

performance in accordance with user requirements and needed system

modifications are incorporated. Operations continue as long as the system can be

effectively adapted to respond to the organization’s needs. When modifications or

changes are identified, the system may re-enter the planning phase.

The purpose of this phase is to:

 Operate, maintain, and enhance the system.

 Certify that the system can process sensitive information.

 Conduct periodic assessments of the system to ensure the functional

requirements continue to be satisfied.

 Determine when the system needs to be modernized, replaced, or retired.

DBMS: MySQL

Host: localhost

User: root

Pass: root

DataBase: fashion

Table Structure: (Images Bellow)

Product Table:

Purchase Table:

Note: In Purchase table take the purchase ID as varchar (16)

Stock Table;

Sales Table:

Note: In Purchase table take the sale_id as varchar (16)

Python Code:

import os

import platform

import mysql.connector

import pandas as pd

import datetime

mydb=mysql.connector.connect(host="localhost",\

user="root",\

passwd="root",\

database="fashion")

mycursor=mydb.cursor()

def AddProduct():

L=[]

stk=[]

pid=input("Enter the Product ID : ")

L.append(pid)
IName=input("Enter the Product Name : ")

L.append(IName)

brnd=input("Enter the Product Brand Name : ")

L.append(brnd)

fr=input("Enter Male/Female/Kids : ")

L.append(fr)

sn=input("Enter Winter/Summer : ")

L.append(sn)

rate=int(input("Enter the Rates for Product :"))

L.append(rate)

product=(L)

sql="Insert into product

(product_id,PName,brand,Product_for,Season,rate)values(%s,%s,%s,%s,%s,%s)"

mycursor.execute(sql,product)

mydb.commit()

stk.append(pid)

stk.append(0)

stk.append("No")

st=(stk)

sql="insert into stock(item_id, Instock, status) values(%s,%s,%s)"

mycursor.execute(sql,st)

mydb.commit()

print("One Product inserted ")

def EditProduct():

pid=input("Enter product ID to be edited : ")

sql="select * from product where product_id=%s"

ed=(pid,)

mycursor.execute(sql,ed)
res=mycursor.fetchall()

for x in res:

print(x)

print("")

fld=input("Enter the field which you want to edit : ")

val=input("Enter the value you want to set : ")

sql="Update product set " + fld +"='" + val + "' where product_id='" + pid + "'"

sq=sql

mycursor.execute(sql)

print("Editing Don : ")

print("After correction the record is : ")

sql="select * from product where product_id=%s"

ed=(pid,)

mycursor.execute(sql,ed)

res=mycursor.fetchall()

for x in res:

print(x)

mydb.commit()

def DelProduct():

pid=input("Enter the Product)id to be deleted : ")

sql="delete from sales where item_id=%s"

id=(pid,)

mycursor.execute(sql,id)

mydb.commit()

sql="delete from purchase where item_id=%s"

mycursor.execute(sql,id)

mydb.commit()

sql="delete from stock where item_id=%s"

mycursor.execute(sql,id)

mydb.commit()

sql="delete from product where product_id=%s"

mycursor.execute(sql,id)

mydb.commit()

print("One Item Deleted")

def ViewProduct():

print("Display Menu: Select the category to display the data")

print("1. All Details")

print("2. Product Name:")

print("3. Product Brand:")

print("4. Product For:")

print("5. Product Season:")

print("6. Product ID:")

x=0

ch=int(input("Enter your choice to display : "))

if ch==1:

sql="select * from product"

mycursor.execute(sql)

res=mycursor.fetchall()

for x in res:

print(x)

x=1

elif ch==2:

var='PName'
val=input("Enter the name of Product : ")

elif ch==3:

var='brand'

val=input("Enter the name of Brand : ")

elif ch==4:

var='Product_for'

val=input("Enter Male/Femal/Kids : ")

elif ch==5:

var='season'

val=input("Enter the Season : ")

elif ch==6:

var='product_id'

val=input("Enter the Product_id : ")

if x==0:

sql="select * from product where " + var + " = %s"

sq=sql

tp=(val,)

mycursor.execute(sq,tp)

res=mycursor.fetchall()

for x in res:

print(x)

def PurchaseProduct():

mn=""

dy=""

now=datetime.datetime.now()
purchaseID="P"+str(now.year)+str(now.month)+str(now.day)+str(now.hour)+str(now.minute)+str(no
w.second)

L=[]

Lst=[]

L.append(purchaseID)

itemId=input("Enter Product ID : ")

L.append(itemId)

itemNo=int(input("Enter the number of Items : "))

L.append(itemNo)

sql="select rate from product where product_id=%s"

pid=(itemId,)

mycursor.execute(sql,pid)

res=mycursor.fetchone()

for x in res:

print("rate is : ", x)

amount=x*itemNo

print("Amount is :", amount)

L.append(amount)

mnth=now.month

if mnth<=9:

mn="0"+str(mnth)

else:

mn=str(mnth)

day=now.day

if day<=9:

dy="0"+str(day)

else:

dy=str(day)
dt=str(now.year)+"-"+mn+"-"+dy

L.append(dt)

tp=(L)

sql="insert into
purchase(purchase_id,item_id,no_of_items,amount,Purchase_date)values(%s,%s,%s,%s,%s)"

mycursor.execute(sql,tp)

mydb.commit()

sql="Select Instock from stock where item_id=%s"

mycursor.execute(sql,pid)

res=mycursor.fetchall()

status="No"

for x in res:

print(x)

instock=x[0]+itemNo

if instock>0:

status="Yes"

Lst.append(instock)

Lst.append(status)

Lst.append(itemId)

tp=(Lst)

sql="update stock set instock=%s,status=%s where item_id=%s"

mycursor.execute(sql,tp)

mydb.commit()

print("1 Item purchased and saved in Database")

def ViewPurchase():

item=input("Enter Product Name : ")

sql="select product.product_id,
product.PName,product.brand,purchase.no_of_items,purchase.purchase_date,purchase.amount
from product

INNER JOIN purchase ON product.product_id=purchase.item_id and product.PName=%s"

itm=(item,)

mycursor.execute(sql,itm)

res=mycursor.fetchall()

for x in res:

print(x)

def ViewStock():

item=input("Enter Product Name : ")

sql="select product.product_id,product.PName,stock.Instock,\

stock.status from stock, product where \

product.product_id=stock.item_id and product.PName=%s"

itm=(item,)

mycursor.execute(sql,itm)

res=mycursor.fetchall()

for x in res:

print(x)

def SaleProduct():

now=datetime.datetime.now()

saleID="S"+str(now.year)+str(now.month)+str(now.day)+str(now.hour)+str(now.minute)+str(now.sec
ond)

L=[]

L.append(saleID)

itemId=input("Enter Product ID : ")

L.append(itemId)
itemNo=int(input("Enter the number of Items : "))

L.append(itemNo)

sql="select rate from product where product_id=%s"

pid=(itemId,)

mycursor.execute(sql,pid)

res=mycursor.fetchall()

for x in res:

print("The rate of item is :",x)

dis=int(input("Enter the discount : "))

saleRate=x[0]-(x[0]*dis/100)

L.append(saleRate)

amount=itemNo*saleRate

L.append(amount)

mnth=now.month

if mnth<=9:

mn="0"+str(mnth)

else:

mn=str(mnth)

day=now.day

if day<=9:

dy="0"+str(day)

else:

dy=str(day)

dt=str(now.year)+"-"+mn+"-"+dy

L.append(dt)

tp=(L)

sql="insert into sales (sale_id, item_id,no_of_item_sold,\

sale_rate,amount,date_of_sale) values(%s,%s,%s,%s,%s,%s)"

mycursor.execute(sql,tp)

mydb.commit()

sql="Select Instock from stock where item_id=%s"

mycursor.execute(sql,pid)

res=mycursor.fetchall()

for x in res:

print("Total Items in Stock are : ",x)

instock=x[0]-itemNo

if instock>0:

status="Yes"

tp=(instock,status,itemId)

sql="update stock set instock=%s,status=%s where item_id=%s"

print("Remaining Items in Stock are : ",instock)

mycursor.execute(sql,tp)

mydb.commit()

def ViewSales():

item=input("Enter Product Name : ")

sql="select product.product_id, product.PName,product.brand,\

sales.no_of_item_sold,sales.date_of_sale,sales.amount \

from sales, product where product.product_id=sales.item_id \

and product.PName=%s"

itm=(item,)

mycursor.execute(sql,itm)

res=mycursor.fetchall()
for x in res:

print(x)

def MenuSet(): #Function For The SFashion Store System

print("Enter 1 : To Add Product ")

print("Enter 2 : To Edit Product ")

print("Enter 3 : To Delete Product ")

print("Enter 4 : To View Product ")

print("Enter 5 : To Purchase Product")

print("Enter 6 : To View Purchases")

print("Enter 7 : To View Stock Detials")

print("Enter 8 : To Sale the item")

print("Enter 9 : To View Sales Detials")

try: #Using Exceptions For Validation

userInput = int(input("Please Select An Above Option: ")) #Will Take Input From User

except ValueError:

exit("\nHy! That's Not A Number") #Error Message

else:

print("\n") #Print New Line

if(userInput == 1):

AddProduct()

elif(userInput == 2):

EditProduct()

elif (userInput==3):

DelProduct()

elif (userInput==4):

ViewProduct()

elif (userInput==5):
PurchaseProduct()

elif (userInput==6):

ViewPurchase()

elif (userInput==7):

ViewStock()

elif (userInput==8):

SaleProduct()

elif (userInput==9):

ViewSales()

else:

print("Enter correct choice. . . ")

print("*"*80)

print("* * * * * * * Welcome to the Project of Fashion Store * * * * * * * ")

print("* * * * Developed by: Neha Tyagi, PGT CS, KV no. 5 Jaipur : * * * * ")

print("*"*80)

print("")

MenuSet()

def runAgain():

runAgn = input("\nwant To Run Again Y/n: ")

while(runAgn.lower() == 'y'):

if(platform.system() == "Windows"):

print(os.system('cls'))

else:

print(os.system('clear'))

MenuSet()

runAgn = input("\nwant To Run Again Y/n: ")

runAgain()
 TESTING
Software Testing is an empirical investigation conducted to

provide stakeholders with information about the quality of the product or

service under test[1] , 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. Software

Testing, depending on the testing method employed, can be implemented

at any time in the development process, however the most test effort is

employed after the requirements have been defined and coding process

has been completed.

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.

BLACK BOX TESTING

Black box testing treats the software as a "black box," without any
knowledge of internal implementation. Black box testing methods include:

equivalence partitioning, boundary value analysis, all-pairs testing, fuzz

testing, model-based testing, traceability matrix, exploratory testing and

specification-based testing.

SPECIFICATION-BASED TESTING

Specification-based testing aims to test the functionality of

software according to the applicable requirements.[16] Thus, the tester

inputs data into, and only sees the output from, the test object. This level

of testing usually requires thorough test cases to be provided to the tester,

who then can simply verify that for a given input, 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

ADVANTAGES AND DISADVANTAGES

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

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)

Types of white box testing:-

The following types of white box testing exist:

• api testing - Testing of the application using Public and Private APIs.

• Code coverage - creating tests to satisfy some criteria of code coverage.

For example, the test designer can create tests to cause all

statements in the program to be executed at least once.

• fault injection methods.

• mutation testing methods.

• static testing - White box testing includes all static testing.

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.
 Two common forms of code coverage are:

• Function Coverage: Which reports on functions executed and

• Statement Coverage: Which reports on the number of lines executed to

complete the test.

They both return coverage metric, measured as a percentage

FUTURE ENHANCEMENT

In near future, the system interface could be improved, with

more attractive, interactive and meaningful images; enhance the

system with an email and SMS or email notifications. Enhance the

current system by computerizing almost all the services provided

by the institution ,turning it into a complete LMS. And evolve the

system by developing several versions through users feedback. if a

complete solution has not been worked out.

 BIBLIOGRAPHY

• Informatics Practices by Preeti Arora

• Informatics Practices by Smita Arora

• www.tutorialaicsip.com/cs-xii-pra/project-synopsis-
cbse-class-12/

• www.python.mykvs.in
• www.csiplearning hub.com