0% found this document useful (0 votes)
124 views

Vedic Vidyashram Senior Secondry School: Computer Science Project

This document provides an overview of a library management system project created by three students. It outlines the objectives of applying programming skills to solve a real-world problem. It describes the existing manual system and proposed computerized system. It also includes sections on the marketing system development life cycle, phases of the marketing and sales systems, flow charts, source code, outputs, hardware/software requirements and conclusion.

Uploaded by

Saravanan
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
124 views

Vedic Vidyashram Senior Secondry School: Computer Science Project

This document provides an overview of a library management system project created by three students. It outlines the objectives of applying programming skills to solve a real-world problem. It describes the existing manual system and proposed computerized system. It also includes sections on the marketing system development life cycle, phases of the marketing and sales systems, flow charts, source code, outputs, hardware/software requirements and conclusion.

Uploaded by

Saravanan
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 23

VEDIC VIDYASHRAM SENIOR SECONDRY SCHOOL

COMPUTER SCIENCE PROJECT

SYNOPSIS OF LIBRARY MANAGEMENT SYSTEM

Project by
VISHNU PRIYAN .S
GURUASHOKAN.G
SARAVANAN.K
CONTENTS
PAGE
S.NO TITLE
NO.

01. INTRODUCTION

02. OBJECTIVE

03. EXISTING AND PROPOSED SYSTEM

MARKETING SYSTEM DEVELOPMENT


04.
LIFE CYCLE (MSDLC)

05. PHASES OF MARKETING SYSTEM AND


SALES SYSTEM

06. FLOW CHART

07. SOURCE CODE

08. OUTPUT

09. HARDWARE AND SOFTWARE


REQUIREMENTS

10. CONCLUSION

11. BIBLIOGRAPHY
INTRODUCTION

Information needed to develop marketing strategy is also


provided by MIS. It supports strategy development for new
products, product positioning, marketing communications
(advertising, public relations, and sales promotion),
pricing, personal selling, distribution, customer service and
partnerships and alliances.
OBJECTIVES

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 programming skills helps in developing a

good software.

• Anunderstanding of the different roles managers play and how


marketing information systems can support them in these roles

• Anappreciation of the different types and levels of marketing decision


making

•A knowledge of the major components of a marketing information system

• An awareness of the often under-utilized internal sources of


information available to enterprises

• Anability to clearly distinguish between marketing research and


marketing intelligence, and

• An understanding of the nature of analytical models within marketing


information system.
EXISTING AND 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 outdated

to rationalize your mistake. So, to keep pace with time, to bring about

the best result without malfunctioning and greater efficiency so to

replace the unending heaps of flies with a much sophisticated hard

disk of the computer.

One has to use the data management software. Software has

been an ascent in atomization various organizations. Many software

products working are now in 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 paper work has

to be done but now software product on 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.


MARKETING SYSTEM DEVELOPMENT LIFE
PROCESS

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 designated as


request, requirements-definition, and planning phases, or
initiation, concept-development, and planning phases. End
users of the system under development should be involved in
reviewing the output of each phase to ensure the system is
being built to deliver the needed functionality
PHASES OF MARKETING SYSTEM AND
SALES SYSTEM
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.
MARKETING 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 MARKETING


SYSTEM AND SALES SYSTEM:
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.
REQUIREMENTS ANALYSIS 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.
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.
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.
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.
FLOW CHART

PHYTHON-MYSQL
CONNECTING

SOFTWARE LOGIN WITH USER NAME AND


PASSWORD

ASK USERS TO ENTER HIS


CHOICE

YOUR NEED WILL BE


FULLFILLEED
WITH INTRACTING WITH MYSQL

AGAIN FIRST PAGE WILL BE


OPENED TO
FULLFILL THE USERS DEMAND
SOURCE CODE

from sys import exit


import mysql.connector as sql
conn=sql.connect(host='localhost',user='root',passwd='manager'
,database='marketing_system_and_sales_system')
if conn.is_connected():
print('succesfully conected')
c1=conn.cursor()
print('marketing system and sales system')
print("1.login")
print("2.exit")
choice=int(input("enter your choice"))
if choice==1:
name=input("enter the user name:")
passwd=input("enter the password:")
while name=='vishnu' and passwd=='vishnu103' :
print('welcome')
print('1. registry for customer ')
print('2.registry for products seller')
print('3.registry for order placement')
print('4.modify the order details')
print('5.registry for cancelation of order')
print('6.display the customer details')
print('7.display the products availability')
print('8.display the datas about order placement')

print('9.display the order details')

print('10.display the cancellation of order')


if choice==1:
customer_name=input('enter the customer
name:')
product_name=input('enter the product

name:')
sql_insert="insert into customer_details
values(""'"+customer_name+"'," "'"+product_name+"'"")"
c1.execute(sql_
print('SUCCESSFULLY
REGISTERD'insert)
conn.commit())

elif choice==2:
customer_name=input('enter the customer
name:')
product_type=input('enter the product
type:')
product_brand=input('enter the product
brand:')
product_available=input('ONLY 3000 stocks
available:')
sql_insert="insert into products_brand
values(""'"+customer_name+"'," "'"+product_type+"'"")"

"'"+product_brand+"'," "'"+products_available+"'"")"

c1.execute(sql_insert)
conn.commit()
print('SUCCESSFULLY REGISTERD')

elif choice==3:

customer_name=input('enter the customer


name:')

product_name=input('enter the product


name:')

demanding_quantity=input('enter the

quantity: ')
sql_insert="insert into order_placement
values(""'"+customer_name+"'," "'"+product_name+"',"
"'"+demanding_quantity+"'"")"

c1.execute(sql_insert)
conn.commit()
print('successfully registerd')
elif choice==4:
customer_name=input('enter the customer
name:')
mobile_number=input('enter mobile number:')
address=input('enter your address:')
date_to_deliver=input('enter the date:'
sql_insert="insert into order_details
values(""'"+customer_name+"'," "'"+mobile_number+"',"
"'"+address+"'," "'"+date_to_deliver+"'"")"

c1.execute(sql_insert)
conn.commit()
print('SUCCESSFULLY REGISTERD')

elif choice==5:
customer_name=input('enter the customer
name:')
order_number=input('enter the order
number:')
products_contained=input('enter the product
contained in your order:')
reason_for_cancelation=input('enter the
reason for cancelling the order:')
confirm_cancelation=input('say YES or NO:')

sql_insert="insert into cancelation_of_order


values(""'"+customer_name+"'," "'"+order_number+"',"

"'"+products_contained+"',"

"'"+reason_for_cancelation+"',""'"+confirm_cancelation+"'"")"

c1.execute(sql_insert)
conn.commit()
print('SUCCESSFULLY REGISTERD')

elif choice==6:

sql_s="select*from customer_details"

c1.execute(sql_s)
a=c1.fetchall()
for i in a:
print(i)
break
elif choice==7:

sql_s="select*from products_brand"

c1.execute(sql_s)
a=c1.fetchall()
for i in a:
print(i)
break

elif choice==8:

sql_s="select*from order_placement"

c1.execute(sql_s)
a=c1.fetchall()
for i in a:
print(i)
break

elif choice==9:

sql_s="select*from order_details"

c1.execute(sql_s)
a=c1.fetchall()
for i in a:
print(i)
break

elif choice==10:

sql_s="select*from cancellation_of_order"

c1.execute(sql_s)
a=c1.fetchall()
for i in a:
print(i)
break

else:
print('sorry')
OUTPUT
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.
HARDWARE AND SOFTWARE
REQUIREMENT
I. OPERATING SYSTEM : WINDOWS 7 AND
ABOVE

II. PROCESSOR : PENTIUM(ANY)

OR AMD

ATHALON(3800+

- 4200+ DUAL

CORE)

SOFTWARE REQUIREMENT:
I. Windows OS
II. Python

You might also like