Arts Gallery Management System: Project Report

Arts Gallery Management System
ARTS GALLERY MANAGEMENT SYSTEM
PROJECT REPORT
Submitted in partial fulfillment of the requirements
for the award of the degree of
BACHELOR OF COMPUTER SCIENCE
MAHATMA GANDHI UNIVERSITY
KOTTAYAM-686560 2016-2019
SUBMITTED BY
ALIYABEEVI PM REG NO : 160021108564
SEENATH AA REG NO : 160021108593
SAMEENA A REG NO:16002118592
Under the guidance of
Mrs. RINI BERNIN
DEPARTMENT OF COMPUTER SCIENCE
AL AMEEN COLLEGE, EDATHALA
MAHATMA GANDHI UNIVERSITY
Page No 1
AL-AMEEN COLLEGE
EDATHALA, ALWAYE
DEPARTMENT OF COMPUTER SCIENCE
CERTIFICATE
This is to certify that the project entitled “ARTS GALLERY MANAGEMENT

SYSTEM” is a bonafide record of the work done by Aliya beevi P M, Seenath A.A,
Sameena A M with Register Numbers 160021108564,160021108593,160021108592 of
department of Computer Science, Al Ameen college Edathala in partial fulfillment of the
requirements for the award of the degree of Bachelor of Computer Application by
Mahatma Gandhi University, Kottayam during the year 2016-2019.
Project Guide Head of the department
Submitted for the university exam held on.................
Page No 2
ACKNOWLEDGEMENT
I am using this opportunity to express my gratitude to everyone who supported me

throughout the course of the project. I am thankful for their aspiring guidance, invaluably
constructive criticism and friendly advice during the project work. I am sincerely grateful
to them for sharing their truthful and illuminating views on a number of issues related to
the project.
I express my deep and sincere gratitude to prof . SASITHARAN M.B , Principal, Al-
Ameen College Edathala for the overwhelming support and direction.
I express my special thanks to Dr.CINI KURIAN, IQAC coordinator for all the support
and kind co orperation to complete the project.
I am deeply indebted to Mrs.BEENATRIES N JOY, Head of the department for her

guidance, help and encouragement for the completion of my project work.
I express my warm thanks to Mrs.RINI BERNIN, Project guide for her support and
guidance.
Page No 3
ABSTRACT
Art gallery management system is project that stores and retrieves art details including
Their sales in their gallery. This project is developed to manage the art gallery artist
details, art details, customer details, sales details and report details. The administrator
will enter the username and password to login to the system. If the username and
password are correct, it will open the next form. If the entered details are not correct, it
will show the error message. All artist details available in the art gallery are added by the
administrator. The added artist details can be modified or deleted by the administrator.
The artist name, specialist, address and phone no, gallery website are managed in this
module . All art details of the art gallery are added by the administrator. The added art
details can be modified or deleted by the administrator. The art id, art name, picture and
category , artist, price are managed in this module. The art id will automatically
generated . All customer details of the art gallery are added by the employee. The
added customer details can be modified or deleted by the employee. The customer id,
customer name, quantity, total price are managed in this module. The customer id will
automatically generated. All sales details available in the art gallery are added by the
employee. The sales id , customer details, date, art details are managed in this module.
Then the system generates the artist reports, art reports, customer reports, sales report, to
the administrator .
CONTENTS
Page No 4
TITLE
PAGE NO
1. INTRODUCTION 7
1.1 Project overview 8
1.2 Literature survey 9
2. SYSTEM ANALYSIS 10
2.1 Existing system 11
2.2 Proposed system 11
2.3 Feasibility study 12
3. SYSTEM DESIGN 14
3.1 Data modeling 15
3.2 Data flow diagram 15
3.3 ER Diagram 22
3.4 SYSTEM DESIGN SPACIFICATION 22
3.5 Input design 23
3.6 Output design 24
3.7 MODULE DESIGN 29
4. SYSTEM SPECIFICATION 31
4.1 Hardware specification 32
4.2 Software specification 32
Page No 5
4.3 Overview of visual basic 33
4.4 Overview of MySQL 33
5. SYSTEM DEVELOPMENT 35
5.1 Module description 36
6. SYSTEM TESTING 37
6.1 Testing 38
6.2 Test cases 41
7. SYSTEM IMPLEMENTATION 45
7.1 Software Implementation 46
7.2 System Maintenance 47
8. RESULTS 48
9. CONCLUSION AND FUTURE ENHANCEMENT 48
10. ANNEXURE 1 52
11. ANNEXURE 2 59
Page No 6
1.INTRODUCTION
1.1 PROJECT OVERVIEW
The project on “Arts Gallery Management System” deals with the transactions
happening in an arts gallery. The main objective of this project is to automate the
existing manual system to maintain the records of the arts gallery to be computerized.
So that the arts gallery employee details and customer details can be stored and
calculations can be performed much faster and it also helps to faster access of the
information’s which are being already stored. Arts gallery management system is a
software application maintaining the records related to all the activities held on an arts
gallery.
The application can be used in any arts gallery to stored the details of the
employee and customers for better calculations. The admin can read and write
information about the employee , artist and art details. Admin can create, update and
delete the records of artist and employee according to their requirements.
Page No 7
The project has many components: employee details, customer details, art
details, artist details, payment details and sales details. It reduces the work load of the
administrator. It provides the fast retrieval of information about the art. All details will
be available on a click.
The objective of the project is to make good software with an overall

performance. It should be easy to work. The software should be able to extract
information from databases and make the reports very easily. The software and its
operations should be safe and unauthorized access should not be allowed. The aim of
developing and implementing the software is to automate the complete system
through computer with maximum user interactions. The developed software is easier
and flexible to handle. The system is more efficient and cost effective because manual
working can be reduced. The manual errors can be lessened. The software is user
friendly and completely based on menu driven. The key feature of this application is
that it brings multiple fields of data over single platform, which in turn gives a faster
result upon use.
This system is developed using Visual Basic 6.0 as front end and MS SQL as back
end.
1.2 LITERATURE SURVEY
Arts gallery management system is one of the useful types of data analysis for art
gallery. The purpose of arts gallery management system is to maintain a good
communication between the employee and the customer. It includes different types of
arts. The project includes the information about the customer. Admin can frequently
analysis all the details of the customer also he can handle the updation of new arts and
artist.
When we add an arts in the system we can specify the position or the shelf number
of the art. This system is also provide another session to add details of employee.
Page No 8
Page No 9
2. SYSTEM ANALYSIS
2.1 EXISTING SYSTEM
In the existing system, the data was recorded on paper and this was very time
consuming. This system is a manual system which takes lot of time in preparing.
Hence the method restricts the user to do multiple comparisons and searches on a
convenient manner. The earlier system has limitations concerning the updating and
editing of data. There are also duplications in the data stored and discrepancies in the
accounts. This system needs a number of employees and a lot of time for any process.
Therefore it is difficult to find out the details since it is stored in more than one
register. It provides all the users with the same access and allows all users to make
changes in the system, hence making the system inefficient.
Disadvantages of existing system
Page No 10
 Time Consuming
 Less User Friendly
 Difficult to Organize
 Duplication may Occur
 Less Accurate
 Requires More Effort to Process/Retrieve
2.2 PROPOSED SYSTEM
The proposed system is a computerized system which can overcome the drawbacks of
the existing system. The proposed system is informative, user friendly and designed
exclusively for maintaining system data in a well-organized manner. As the system
data is well-organized, duplication of data won’t occur. The system is designed to
provide all the necessary information about the maid agency management system. The
system provides a user friendly interface with all possible operations and details
listed. This helps in saving time and enables the user to
access data quickly. This system provides a well plotted user interface and a working
environment field with all necessary options and data.
Most problems of manual system can be solved by this system. The new system will
work on a Windows based platform.
Advantages of proposed system
 User Friendly Interface

 Enables to Search for Records
 Allows Easy Addition of Details
 Minimizes Redundancy
 High processing speed
2.3 FEASIBILITY STUDY

2.3.1 Introduction
Feasibility study is made to see if the project on completion will serve the purpose of
the organization for the amount of work, time and effort spent on it. Study lets the
developer foreseeing the future of the project, its usefulness and finding out whether a
new system is required or not.
Page No 11
The study is carried out to the best system that meets performance requirement. This
entails identification, description and evaluation of candidate system and selection of
the best system for the job. It simply identifies whether the proposed system is
feasible to the organization or not. There are three aspects in the feasibility study
portion of the preliminary investigation.
i) Technical feasibility
ii) Economic feasibility
iii) Operational feasibility
2.3.2 Technical Feasibility

The system must be evaluated from technical viewpoint first. The assessment of
this feasibility must be based on outline design of the system requirement
in terms of input, output, programs and procedure having identified an outline
system, the investigation must go on to suggest the type of equipment, required
method of developing the system, method of running the system once it has been
designed. The project should be developed such a way that necessary functions and
Page No 12
performance are achieved within the constraints. The project is developed with latest
technology. There are only minimal constraints involved in this project.
2.3.3 Economic Feasibility

Here an evaluation of development cost weighted against the ultimate income or
benefit derived from the developed system. The cost for the development of the
project has been evaluated and we want to check that the cost does not exceed the
beneficial cost of the system. The economic and financial analysis is used for
evaluating the effectiveness of the candidate system. This project also undergone
economic feasibility study and found that it is feasible. So the cost for development
does not exceed its beneficial cost. This brought to as the conclusion that the system is
economically feasible in the context.
2.3.4 Operational Feasibility

In operational feasibility the entire application is checked whether the system will be
used if it is developed and implemented. Also it is checked whether there will be
resistance from user that may undermine the possible application benefits. There is no
barrier for implementing the system. The system also helps to access the information
immediately as need arises. Thus the system is found to be operational feasible.
Page No 13
3. SYSTEM DESIGN
3.1 DATA MODELING

It defines all data objects that are processed within the system, The relationship
between the data objects, and information that is pertinent to the relationships. The
entity-relationship diagrams(ERD) addresses these issues and represents all data
objects that are entered, stored, transformed and produced within an application. Data
modeling tools provide a software engineer with the ability to represent data objects,
their characteristics and their relationships. Used primarily for large database
applications and other information system projects, data modeling tools provide an
automated means for creating comprehensive entity relationship diagrams, data object
dictionaries and related models.
3.2 DATA FLOW DIAGRAM
Page No 14
A data flow diagram is graphical tool used to describe and analyze movement of data
through a system. These are central tool and the basis from which the other
components are developed. The transformation of data from input to output, through
processed, may be described logically and independently of physical components
associated with the system. These are known as the logical data flow movement of
data between people, departments and workstations. A full description of a system
actually consists of a set of data flow diagrams.
In the DFD, there are four symbols
Process that transforms data flow
Source or Destination of data
Data store
Data flow
DATA FLOW DIAGRAM:
Page No 15
Page No 16
Page No 17
Page No 18
Page No 19
Page No 20
3.3. ENTITY RELATIONSHIP DIAGRAM
The ER model is a conceptual data model that views the real world as a construct of
entities and associations or relationships between entities. A basic component of the
model is the Entity-Relationship diagram, which is used to visually represent data
objects. The ER modeling technique is frequently used for the conceptual design of
database applications and many database applications and many database design tools
employ its concepts.
Entity Type
Weak Entity Type
Relationship Type
Attribute
Key attribute
Multivalued Attribute
Page No 21
ER DIAGRAM:
3.4 SYSTEM DESIGN SPECIFICATION
The system design specification(SDS) is a complete document that contains all of the
information needed to develop the system. Unlike the SRS, the targest audiences of
this document are the implementation and testing teams, so the SDS should be written
at a more technical level.
Input Output
design design
Database Module
design design
3.5 Input design
Page No 22
The design of an information system produces the details that state how
a system will meet the requirements identified during system analysis. Design goes
through logical and physical stages of development.
Logical design: It reviews the present physical system i.e., prepares input and
output specification; make edit, security, control specification; details the
implementation plan; and prepares a logical design walkthrough.
Physical design: It maps out the details of the physical system, plans the system
implementation, devises a test and implementation, and specifies any new hardware
and software.
3.6 Output design
Once the visual basic application architecture has been established and the
components of the architecture has been identified, you must define navigation
pathway that enable users to access vb application content and functions.
1. LOGIN
Field Data Type Constraints Description
Login_id Integer Primary key ID of the user
username Varchar(50) null Name of the user
password Varchar(50) null Password of the user
usertype Varchar(50) null Type of user either

staff or admin
2. EMPLOYEE DETAILS
Page No 23
Field data type Constraints Description
Emp_id Integer Primary key Id of the employee
Fname Varchar (50) Not Null first name of

employee
Mname Varchar (50) Not Null Middle name of

employee
Lname Varchar (50) Last name of

employee
Address Varchar (50) Address
Place Varchar (20) Not Null Place
District Numeric (10) Not Null district.
Pincode Varchar (50) Not Null pincode
Gender Varchar(9) Not null gender
Username Varchar (50) Name of the user

Primary key
Password Varchar(50) Not null Password of user
Usertype Varchar(50) Not null Type of the user
3. CUSTOMER
Page No 24
Customer id integer Primary key Id of customer
Fname Varchar (50) Not Null Customer first name
Mname Varchar (50) Not Null Middle name
Lname Varchar (50) Not Null Last name
Address Varchar (50) address
Place Varchar (50) place
District Varchar (20) Not Null district
Pincode Numeric (10) Not Null pincode
Phone no Numeric (10) Not Null Phone no
Email Varchar (50) email
4. ARTS DETAILS
art id integer Primary key Id of art
Artist id integer Foreign key Id of artist
Shelf id integer Foreign key Id of shelf
name Varchar (50) Not Null Name of the art
Description Varchar (50) about the art
Page No 25
Rate Number(18) rate
Status Varchar (20) status
5. ARTIST DETAILS
Artist id integer Primary key Id of artist
Fname Varchar (50) Not Null Artist first name
Mname Varchar (50) Not Null Middle name
Lname Varchar (50) Not Null Last name
Address Varchar (50) address
Place Varchar (50) place
District Varchar (20) Not Null district
Pincode Numeric (10) Not Null Pincode.
Phone no Numeric (10) Not Null Phone no
Email Varchar (50) email
6. PAYMENT
Page No 26
Payment id integer Primary key Id of payment
Sm_id integer Foreign key Id of sales master
Amount Numeric(18,0) Total amount
Date Varchar (50) Date of the

payment
7. SALES MASTER
Sm id integer Primary key Id of sales master
Date Varchar(50) Date of the sale
Customer id integer Foreign key Id of the customer
amount Numeric(18,0) Amount of the art
status Varchar (50) Status of the art
8. SALES CHILD
Field datatype Constraints Description
Sales id integer Primary key Id of sales child
Sm id integer Foreign key Id of the sales master
Art id integer Foreign key Id of the customer
Page No 27
9. SHELF
Field datatype Constraints Description
Shelf id integer Primary key Id of shelf
Shelf no integer Shelf number
3.7 MODUL DESIGN
 Login module
In general computer usage Administrator has the highest privilege over

the system. Administrator administrates over the entire functionalities
over the system such as adding new staff or deletes details of an existing
member and updating or editing the input details. The administrator is the
overall in charge of the system.
 Staff module
Staff is the second in charge, staff consist of maids and the other staffs
of the maid agency. They are given the privilege to update worker details and make
changes. However, they cannot assign other staffs upon a certain task nor delete any
existing content.
Page No 28
4.SYSTEM SPECIFICATION
Page No 29
4.1 SYSTEM REQUIREMENT SPECIFICATION
System requirements specification A detailed statement of the effects that a system is

required to achieve. A good specification gives a complete statement of what the system
is to do, without making any commitment as to how the system is to do it: it constrains
only the externally observable behaviour and omits any design or implementation bias.
A system requirements specification is normally produced in response to a user

requirements specification or other expression of requirements, and is then used as the
basis for system design. The system requirements specification typically differs from the
expression of requirements in both scope and precision: the latter may cover both the
envisaged system and the environment in which it will operate, but may leave many
broad concepts unrefined.
4.1.1 HARDWARE SPECIFICATION
The selection of hardware and software configuration is very important task related to
system development.
Intel Pentium (2.5 GHz) [Similar /

Processor
Above.]
Page No 30
RAM 1 GB
Hard Disk 80 GB and above
Key Board Standard Keyboard
Monitor CRT or LCD monitor
Mouse Compatible Mouse
4.1.2 SOFTWARE SPECIFICATION
Operating System Windows 7 or Above
Front End Visual Studio 6.0
Back End SQL Server 2008
4.2 OVERVIEW OF VISUAL BASIC 6.0
Visual Basic 6.0 is the newest of the popular programming language. With its new
features, Visual Basic is even stronger contender in the application development areas
than ever before.
Visual Basic was designed to accommodate beginner programmers. Programmers can

not only create simple GUI applications, but also to develop complex applications.
Programming in VB is a combination of visually arranging components on controls
on a form, specifying attributes and actions for those components, and writing
additional lines of code for more functionality. Since VB defines default attributes and
actions for the components, a programmer can develop a simple program without
writing much code.
Visual Basic can create executable (EXE files).ActiveX controls, or DLL files, but is
primarily used to develop Windows applications and to interface database systems
.dialog boxes with less functionality can be used to provide pop – up capabilities.
Page No 31
Controls provide the basic functionality of the application, while programmers can
insert additional logic within the appropriate event handlers.
Visual Basic6.0 is an addition to VB products. It allows windows application and easy

learning which enables us to create programs quickly for PC without being an expert
in C++ or other programming language.
4.3 OVERVIEW OF SQL SERVER 2008
SQL Server 2008 is an integrated database management and analysis solution that
delivers increased security, scalability and availability to enterprise data and analytical
applications, while making them easier to build, deploy and manage. It is
comprehensive software that enables to reliably manage mission – critical information
and confidently run today’s increasingly complex business applications. SQL server
2008 allows gaining greater insight and achieving faster results for a competitive
advantage. The key capabilities of SQL Server 2008 are the following:
High Availability: Ensure business continuity with the highest levels of system
availability through technologies that protect data against costly human errors and
minimize disaster recovery downtime.
Performance and Scalability: deliver an infrastructure that has proven record in

handling today’s large amounts of data and critical enterprise workloads.
Security: Provide a secure environment to address privacy and compliance

requirements with built in features that protect data against unauthorized access.
Manageability: Manage infrastructure with automated diagnostics, tuning and

configuration to reduce operational costs while reducing maintenance and easily
managing very large amounts of data.
Developer Productivity: Build and deploy critical business ready applications more
quickly by improving developer productivity and reducing project lifecycle times.
Business Intelligence: Gain deeper insight into the business with integrates
comprehensive analysis and reporting for enhanced decision making.
Page No 32
5. SYSTM DEVELOPMENT
Page No 33
5.1 MODUL DECRIPTION
Module description is defines the each modules in the project. Mainly two
modules are in the Art Gallery Management System.
 ADMIN
The administrator will enter the username and password to login to the
system. If the username and password are correct, it will open the next form. If the
entered details are not correct, it will show the error message. All artist details
available in the art gallery are added by the administrator. The added artist details can
be modified or deleted by the administrator. The artist name, specialist, address and
phone no, gallery website are managed in this module. All art details of the art gallery
are added by the administrator. The added art details can be modified or deleted by the
administrator. The art id, art name, picture and category, artist, price are managed in
this module.
 EMPLOYEE
Employee can also login to the system with their own password and user
name.All customer details of the art gallery are added by the employee. The
added customer details can be modified or deleted by the employee. The
customer id, customer name, quantity, total price are managed in this module.
Page No 34
The customer id will automatically generate. All sales details available in the art
gallery are added by the employee. The sales id , customer details, date, art
details are managed in this module.
6. SYSTEM TESTING
Page No 35
6.1 TESTING
Testing is a set of activity that can be planned in advance and conducted systematically,
which is aimed at ensuring that the system works accurately and efficiently before live
operations commences. Software testing is the process used to measure the quality of
developed computer software. Usually, quality is constrained to such topics as
correctness, completeness, security, but can also include more technical requirements as
described under the ISO standard ISO 9126, such as capability, reliability, efficiency,
portability, maintainability, compatibility, and usability. Testing is a process of technical
investigation, performed on behalf of stakeholders, that is intended to reveal quality-
related information about the product with respect to the context in which it is
intended to operate. An information point is that software testing should be distinguished
from the separate discipline of Software Quality Assurance (SQA),which encompasses
all business process areas, not just testing
There are many approaches to software testing, but effective testing of

complex products is essentially a process of investigation, not merely a matter of
creating and following routine procedure. One definition of testing is “the process of
questioning a product in order to evaluate it”,where the “questions” are operations the
tester attempts to execute with the product , and the product answers with its behaviour
in reaction to the probing of the tester.
In general, software engineers distinguish software faults from software

failures. In case of a failure, the software does not to do what the user expects. A fault is
Page No 36
a programming error that may or may not actually manifest as a failure. A fault can also
be described as an error in the correctness of the semantic of a computer program.
 Testing is the process of correcting a program with intend of finding an

error.
 A good test case is one that has high probability of finding a yet
undiscovered error.
 A successful test is one that uncovers a yet undiscovered error.
Testing Objective
 Testing is a process of executing a program with the intent of finding

an error.
 A good test case is one that has high probability finding an
undiscovered error.
 A successful test is one that uncovers an undiscovered error.
Testing is vital to success of the system. System testing makes a logical

assumption that if all parts of the system are subject to variety of tests on-line response,
volume, stress, recovery and security and usability tests. A series of tests are performed
before the system is ready for user acceptance testing.
Test Procedure
The procedure is as follows:
 Prepare the test case.

 Record the expected results and verify whether in tune with actual results.
 If actual results are not in tune with the expected results, do the necessary
rework?
 Test again and check for the results.
 If the results are satisfactory, wind up testing.
Item Pass / Fail Criteria
The test case consists of different inputs with the expected results in each case.
During
Testing, the Tester records the Actual Test Results against the expected ones and if found
matching, the test case is assigned as a pass. Otherwise, the Test Case is assigned as a fail
and orders for Rework and Retest.
Page No 37
Stop Criteria
The testing can be wrapped up when
 Actual Test Results match with the expected ones.

 System performs well in the specified environment.
The different testing criteria conducted are following:
6.1.1 Unit Testing
The strategy for unit testing is that unit would be the standard approach for
performing unit testing, unless specifically stated. The unit test cases would have to be
created before coding. The unit test cases should be created for all public methods of
classes developed, unless specifically stated. Unit testing should be done for each class
as soon as its development is completed. Irrespective of methodology used, developers
should ensure code coverage specified in MTP is met during unit testing. Unit testing of
a developer’s code should be mandatory be performed before integration of code.
Interface testing can be considered complete, when unit testing of the business interface
is completed. Inter-subsystem integration and Client-server integration should not be
done unless interface testing is completed.
Advantages:
 Reduction in number of defects.

 Reduction in development time and effort.
 Reduction in integration and testing time and effort.
Detailed Strategy
Server side
The unit test cases would be created for the public methods of all server side
classes. Unit Test Cases need not be created for query Constructor and VO classes.
Interface testing would be done once all classes for a business method are unit tested and
developed. Unit testing of delegate classes in isolation is not required. Testing can be
done after integrating with server. Sever developers should do this testing.
Client side
Client side testing should be done before integration with server code. Dummy
delegates are to be used for the testing all flowers as per use case have to be tested. The
data displayed in the screen correctly represents the data got from the delegate. The
Page No 38
correct Screens/ Pop ups/ Messages are displayed. Testing should also check correctness
against the GUI specification of the corresponding screen.
6.1.2 Integration Testing
Integrated testing is a systematic technique for constructing the program structure

while at the same time conducting tests to uncover errors associated with interfacing. The
objective is to take unit tested components and build a program structure that has been
dictated by the design.
Bottom-up integration
Bottom-up integration testing begins construction and testing with atomic

modules (i.e., modules at the lowest levels in the program structure ). Because the
modules are integrated from the bottom-up, processing required for the modules
subordinate to a given level is always available and the need of stubs is eliminated.
A bottom-up integration strategy may be implemented with the help of the

following steps:
 Low level modules are combined into clusters(sometimes called builds) that
perform a specific software sub-function.
 A driver (a control program for testing) is written to coordinate test case
input and output.
 The cluster is tested.
 Drivers are removed and clusters are combined moving upward in the
program structure.
6.1.3 System Testing
System testing was done on a complete, integrated system in order

to evaluate whether the system compliance with its specified requirements.
The system was tested and checked whether it gives the results that are
expected from the software.
6.1.4 Validation testing
Page No 39
Validation testing is done on the virtual classroom system to check

whether boxes and combo boxes. In this software all the validations are done
using java script. The software validates each data provided through the
various forms and gives appropriate messages accordingly so that the user
will not be able to proceed without giving relevant information. The system
was given various wrong values to see the proper display of error messages.
6.2 TEST CASES
 Test cases of login module
No. Text Scenario Expected Result Result
1 Enter wrong user name and Display an ‘invalid’ message Passed

password
2 Enter correct user name and Load login page again with Passed
password valid message
3 Enter correct user name and Administrator can login to Passed

correct password of Administrator the system
4 Enter correct user name and User can login to the system. Passed
password of user The corresponding page
should load with menu
 Test cases of Employee module
1 When employee login go to Display employee home Passed

employee profile page
2 When select ‘view ‘ option, go to When click ‘Back’ button Passed

the customer, sales or payment ,move back to the employee
details as needed home page
Page No 40
3 When ‘LOGOUT’ button clicks Go back to the Login page Passed
 Test cases of sub module
1 When Admin login to the Displays ADMIN profile Passed

ADMIN profile
2 When select ‘ADD’ option , go to Display Employee, Art or Artist Passed
the forms of employee, art or form
artist
3 Can enroll details of the When ‘SUBMIT’ button clicks Passed
Employee, Art or Artist and store display a message box of “value
it inserted”
4 When select ‘VIEW’ option , go When ‘SUBMIT’ button clicks , Passed
to the sales, payment, arts or artist move back to the Admin page
details form as needed
5 When ‘LOGOUT’ button clicks Go back to the login page Passd
INTEGRATION TESTING
After the completion of testing each individual module, the modules are
linked together. Now it should work properly apart from working individually.
This linking modules often referred as interfacing. Data loss may occur at the time
of interfacing.
This should be carefully avoided because this will affect the other modules also.
Integration testing is systematic technique for constructing the program linkage
while conducting test at the same time to uncover errors associated with that
interface. The test were carried out each time a module was linked.
Page No 41
Integration test report
1 Working of software with the It should work properly apart Passed

modules linked from working individually
SYSTEM TESTING
When a system is developed , it is hoped that is performed properly . In practice,

however some errors always occur. The main purpose of testing an information system is
to find the errors and correct them. A successful test is one which finds an error. Test is
done by checking comprehensive evaluation of the programs, manual procedure ,
computer operations and controls.
System testing report
No. Text Scenario Result
1 During operating system should performs as per specification. Passed
2 During operating system should meet user requirements . Passed
3 When correct inputs are entered output should be correct. Passed
4 Making sure that during operation, incorrect inputs will be deleted. Passed
The common view of testing held by users is that it is performed to

prove that there are no errors in a program. However , as indicated earlier, this is
virtually impossible, since analyst cannot prove that website is free and clear of errors.
The tester , who may be program fail. A successful test, Analysts know that an effective
testing program does not guarantee system reliability. There for reliability must be design
into the system.
Page No 42
Testing Strategies
A test is a set of data that the system will process as normal input.
However,
The data are created with the express intent of determining whether the system will
process them correctly.
7. SYSTEM IMPLEMENTATION
Page No 43
7.1 Software implementation
Systems implementation is the construction of the new system and

the delivery of that system into production (i.e., the day-to-day business or
organization operation ) . The implementation phase has one key activity:
deploying the new system in its target environment. Supporting actions
include training end-users and preparation to turn the system over to
maintenance personnel. After this phase, the system enters the operations and
maintenance phase for the remainder of the system’s operational life.
Multiple-release projects require multiple iterations of the implementation
phase – one for each release.
The purpose of the implementation phase is to deploy and enable operations

of the new information system in the production environment.
Implementation phases:
1. Coding:
Includes implementation of the design document into executable

programming language code. The output of the coding phase is
Page No 44
the source code for the software that acts as input to the testing
and maintenance phase.
2. Integration testing:
Includes detection of errors in the software. The testing process

starts with a test plan recognizes test-related activities, such as test
case generation, testing criteria, and resource allocation for
testing. The code is tested and mapped against the design
document created in the design phase. The output of the testing
phase is a test report containing errors that occurred while testing
the application.
3. Installation:
In this stage the new system is installed and rolled out.
Key Deliverables
 Fully installed system.
 Fully trained users.

 User and operational documentation.
7.2 SYSTEM MAINTENCE

The maintenance phase occurs once the system is operational. It includes
implementation of changes that software might undergo over a period of time, or
implementation of new requirements after the software is deployed at the customer
location. The maintenance phase also includes handling the residual errors that may exist
in the software even after the testing phase. This phase also monitors system
performance rectifies bugs and requested changes are made.
Maintenance, often turned support, is crucial activity for linking the experience of
users/ customers with the product delivery organization. We consider perspective on high
tech maintenance from bug fixing through to design focused activities.
Page No 45
Key Deliverables:
 Keep system live

 Maintain code
 Update software when required
Basically maintenance is what happens during the rest of the software’s life:
changes, correction, addictions, moves to a different computing platform and
more. This, the least glamorous and perhaps most important step of all, goes
on seemingly forever.
Page No 46
8. RESULT
The system is designed for storing the data of an arts, and artists of arts gallery
management system. Thus it provide a better way for easy paying and also well
known about the arts and artist. It make the calculations that held in the gallery
accurate and it is very easy to view the details. The output of the system is optimum.
The admin has the major role to see the whole details are done in the arts
gallery management system. The admin can add all the details, edit and view it. The
admin will add the arts and artist and also change the cost of the arts. The employee
will deals with the sales and payment in the gallery. Employee can also view the
customer details and their own profile. It is a good software to store the information of
the arts and artist in an arts gallery. It is more reliable and secured, it is also provide
effective customer satisfaction.
Page No 47
9. CONCLUSION AND FUTURE ENHANCEMENT
Page No 48
The ARTS GALLERY MANAGEMENT SYSTEM was successfully completed

within the time span allocated. All the modules are tested separately and put together
to form the main system. Finally the system is tested with the real data and everything
worked successfully. Thus the system has full filled with the entire objectives
identified.
The system has been developed in an attractive way in a limited platform

as a standalone application.
The project will give users a variety experience by use it. The above
mentioned has a design which has a both simple and standard look.
ARTS GALLERY MANAGEMENT SYSTEM is easy to use and the

employee can easily see their details and they can easily check their cost details of the
arts. It also helps the customers to view their arts details. It reduces time consumption
Page No 49
for each process. So, we are very thankful to everyone who cooperated with us to
complete this project. ARTS GALLERY MANAGEMENT SYSTEM is really helpful
to the employee, and customers of the gallery. Which keeps and industrial standard
and secure saving of the whole records. It will definitely make a difference in the arts
gallery procedures. It has a wide scope future. Admin can easily add the details of the
arts and artist in an easy and speed way. And calculations can be done in an efficient
manner. So the ARTS GALLERY MANAGEMENT SYSTEM will give customers to
a different approach and experiences….
11. ANXURE 1
Page No 50
LOGIN PAGE
Page No 51
ADMIN HOME PAGE
Page No 52
EMPLOYEE REGISTRATION
EMPLOYEE UPDATION
Page No 53
ART DETAILS
Page No 54
ARTIST UPDATION
VIEW CUSTOMER
ADDING SHELF NUMBER
Page No 55
VIEW ARTS
SALES DETAILS
Page No 56
Page No 57
12. ANEXURE 2
Page No 58
Login
Public u, id As String
Dim q As String, p As String
Private Sub Form_Load()
connect
u_txt.Text = ""
p_txt.Text = ""
End Sub
Private Sub login_cmd_Click()
If rs.State = adStateOpen Then
rs.Close
End If
q = "select login_id,usertype from login where username='" & u_txt.Text & "' and password='"
& p_txt.Text & "'"
rs.Open q, con, 3, 3
If rs.RecordCount > 0 Then
id = rs.Fields!login_id
u = rs.Fields!usertype
MDIForm1.Show
Page No 59
Unload Me
Else
MsgBox "invalid"
End If
End Sub
Arts details
Dim q, path As String
Dim artst_id(1000), shlf(1000) As Integer
Private Sub add_cmd_Click()
If cmbartn.Text = "" Or cmbshelfn.Text = "" Or a_txt.Text = "" Or d_txt.Text = "" Or

r_txt.Text = "" Then
MsgBox "please fill all fields"
Else
q = "insert into arts values('" & artst_id(cmbartn.ListIndex) & "','" &

shlf(cmbshelfn.ListIndex) & "','" & a_txt.Text & "','" & d_txt.Text & "','" & r_txt.Text &
"','available','" & path & "')"
con.Execute q
MsgBox "value inserted"
Unload Me
Art_details.Show
End If
End Sub
Private Sub Command1_Click()
Page No 60
MDIForm1.Show
End Sub
q = "select * from artist"
selt q
i=0
Do Until rs.EOF
cmbartn.AddItem rs.Fields!fname + " " + rs.Fields!lname
artst_id(i) = rs.Fields!artist_id
i=i+1
rs.MoveNext
Loop
q = "select * from shelf"
selt q
Do Until rs.EOF
cmbshelfn.AddItem rs.Fields!shelf_number
shlf(i) = rs.Fields!shelf_id
i=i+1
rs.MoveNext
Loop
End Sub
Private Sub Image1_Click()
End Sub
Private Sub r_txt_KeyPress(KeyAscii As Integer)
Page No 61
Select Case KeyAscii
Case vbKey0 To vbKey9
Case vbKeyBack, vbKeyClear, vbKeyDelete
Case vbKeyLeft, vbKeyRight, vbKeyUp, vbKeyDown, vbKeyTab
Case Else
KeyAscii = 0
Beep
End Select
End Sub
Artist details
Dim q As String
Private Sub back_cmd_Click()
manage_artist.Show
End Sub
Private Sub d_txt_KeyPress(KeyAscii As Integer)
Select Case Chr(KeyAscii)
Case 0 To 9
KeyAscii = 0
End Select
End Sub
Private Sub f_txt_KeyPress(KeyAscii As Integer)
Page No 62
Case 0 To 9
KeyAscii = 0
End Select
End Sub
Private Sub l_txt_KeyPress(KeyAscii As Integer)
Case 0 To 9
KeyAscii = 0
End Select
End Sub
Private Sub m_txt_KeyPress(KeyAscii As Integer)
Case 0 To 9
KeyAscii = 0
End Select
End Sub
Private Sub p_txt_KeyPress(KeyAscii As Integer)
Case 0 To 9
KeyAscii = 0
End Select
End Sub
Private Sub ph_txt_KeyPress(KeyAscii As Integer)
Page No 63
Case Else
KeyAscii = 0
Beep
End Select
End Sub
Private Sub pi_txt_KeyPress(KeyAscii As Integer)
Case Else
KeyAscii = 0
Beep
End Select
End Sub
Private Sub submit_cmd_Click()
If f_txt.Text = "" Or a_txt.Text = "" Or p_txt.Text = "" Or d_txt.Text = "" Or pi_txt.Text = "" Or
ph_txt.Text = "" Or e_txt.Text = "" Then
MsgBox "please insert values for all the fields"
Else
q = "insert into artist values('" & f_txt.Text & "','" & m_txt.Text & "','" & l_txt.Text & "','" &
a_txt.Text & "','" & p_txt.Text & "','" & d_txt.Text & "','" & pi_txt.Text & "','" & ph_txt.Text &
"','" & e_txt.Text & "')"
Page No 64
con.Execute q
Unload Me
Artist_details.Show
End If
End Sub
Customer details
Dim q As String
MDIForm1.Show
End Sub
Case 0 To 9
KeyAscii = 0
End Select
End Sub
Case 0 To 9
KeyAscii = 0
End Select
Page No 65
End Sub
Case 0 To 9
KeyAscii = 0
End Select
End Sub
Case 0 To 9
KeyAscii = 0
End Select
End Sub
Case 0 To 9
KeyAscii = 0
End Select
End Sub
Page No 66
Case Else
KeyAscii = 0
Beep
End Select
End Sub
Case Else
KeyAscii = 0
Beep
End Select
End Sub
Private Sub sub_cmd_Click()
ph_txt.Text = "" Or e_txt.Text = "" Then
Else
Page No 67
q = "insert into customer values('" & f_txt.Text & "','" & m_txt.Text & "','" & l_txt.Text & "','"
& a_txt.Text & "','" & p_txt.Text & "','" & d_txt.Text & "','" & pi_txt.Text & "','" & ph_txt.Text &
"','" & e_txt.Text & "')"
con.Execute q
Unload Me
customer_details.Show
End If
End Sub
Employee details
Dim q, Gender As String
manage_emp.Show
End Sub
Case 0 To 9
KeyAscii = 0
End Select
End Sub
Case 0 To 9
KeyAscii = 0
End Select
Page No 68
End Sub
male.Value = True
End Sub
Case 0 To 9
KeyAscii = 0
End Select
End Sub
Case 0 To 9
KeyAscii = 0
End Select
End Sub
Case 0 To 9
KeyAscii = 0
End Select
End Sub
Page No 69
Case Else
KeyAscii = 0
Beep
End Select
End Sub
Case Else
KeyAscii = 0
Beep
End Select
End Sub
Private Sub sub_cmd_Click()
If male.Value = True Then
Gender = "Male"
Page No 70
ElseIf female.Value = True Then
Gender = "Female"
End If
If rs.State = adStateOpen Then
rs.Close
End If
q = "insert into login values('" & u_txt.Text & "','" & pa_txt.Text & "','Employee')"
con.Execute q
q = "Select top(1)login_id from login order by login_id desc"
selt (q)
s = rs.Fields!login_id
ph_txt.Text = "" Or e_txt.Text = "" Or u_txt.Text = "" Or pa_txt.Text = "" Then
Else
q = "insert into employee values('" & s & "','" & f_txt.Text & "','" & m_txt.Text & "','" &
l_txt.Text & "','" & a_txt.Text & "','" & p_txt.Text & "','" & d_txt.Text & "','" & pi_txt.Text & "','"
& Gender & "','" & ph_txt.Text & "','" & e_txt.Text & "')"
con.Execute q
Unload Me
employee_details.Show
End If
End Sub
Page No 71
MDIForm
Private Sub arts_rpt_Click()
Unload DataEnvironment1
Arts_report.Show
End Sub
Private Sub MDIForm_Load()
If login.u = "admin" Then
n_add.Visible = False
n_vi.Visible = False
n_mksl.Visible = False
n_uparav.Visible = False
n_mng.Visible = False
ret.Visible = False
ElseIf login.u = "Employee" Then
n_manage.Visible = False
n_view.Visible = False
n_shelf.Visible = False
n_report.Visible = False
Else
MsgBox "invalid"
Page No 72
End If
End Sub
Private Sub n_art_Click()
Art_details.Show
End Sub
Private Sub n_artist_Click()
manage_artist.Show
End Sub
Private Sub n_artss_Click()
view_arts.Show
End Sub
Private Sub n_cust_Click()
view_customer.Show
End Sub
Private Sub n_customer_Click()
customer_details.Show
Page No 73
End Sub
Private Sub n_emp_Click()
manage_emp.Show
End Sub
Private Sub n_logout_Click()
login.Show
Unload Me
End Sub
Private Sub n_mksl_Click()
sales_details.Show
End Sub
Private Sub n_profile_Click()
manage_profile.Show
End Sub
Private Sub n_sales_Click()
view_sales.Show
End Sub
Private Sub n_shelf_Click()
Page No 74
shelf.Show
End Sub
Private Sub n_uparav_Click()
updateartsavailability.Show
End Sub
Private Sub ret_Click()
return_details.Show
End Sub
Private Sub salesreports_Click()
sales_report.Show
End Sub
Private Sub stf_rpt_Click()
staff_report.Show
End Sub
Page No 75

Arts Gallery Management System: Project Report

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Arts Gallery Management System: Project Report

Transféré par

Droits d'auteur :

Formats disponibles

Arts Gallery Management System

ARTS GALLERY MANAGEMENT SYSTEM

Submitted in partial fulfillment of the requirements

for the award of the degree of

BACHELOR OF COMPUTER SCIENCE

MAHATMA GANDHI UNIVERSITY

ALIYABEEVI PM REG NO : 160021108564

SEENATH AA REG NO : 160021108593

SAMEENA A REG NO:16002118592

Under the guidance of

Mrs. RINI BERNIN

DEPARTMENT OF COMPUTER SCIENCE

AL AMEEN COLLEGE, EDATHALA

MAHATMA GANDHI UNIVERSITY

DEPARTMENT OF COMPUTER SCIENCE

This is to certify that the project entitled “ARTS GALLERY MANAGEMENT

Project Guide Head of the department

Submitted for the university exam held on.................

I am using this opportunity to express my gratitude to everyone who supported me

I am deeply indebted to Mrs.BEENATRIES N JOY, Head of the department for her

1.1 Project overview 8

1.2 Literature survey 9

2.1 Existing system 11

2.2 Proposed system 11

2.3 Feasibility study 12

3.1 Data modeling 15

3.2 Data flow diagram 15

3.4 SYSTEM DESIGN SPACIFICATION 22

3.5 Input design 23

3.6 Output design 24

3.7 MODULE DESIGN 29

4.1 Hardware specification 32

4.2 Software specification 32

4.3 Overview of visual basic 33

4.4 Overview of MySQL 33

5.1 Module description 36

6.2 Test cases 41

7.1 Software Implementation 46

7.2 System Maintenance 47

9. CONCLUSION AND FUTURE ENHANCEMENT 48

1.1 PROJECT OVERVIEW

The objective of the project is to make good software with an overall

1.2 LITERATURE SURVEY

2.1 EXISTING SYSTEM

Disadvantages of existing system

2.2 PROPOSED SYSTEM

Advantages of proposed system

 User Friendly Interface

2.3 FEASIBILITY STUDY

2.3.2 Technical Feasibility

2.3.3 Economic Feasibility

2.3.4 Operational Feasibility

3.1 DATA MODELING

3.2 DATA FLOW DIAGRAM

In the DFD, there are four symbols

Process that transforms data flow

Source or Destination of data

DATA FLOW DIAGRAM:

3.3. ENTITY RELATIONSHIP DIAGRAM

Weak Entity Type

3.4 SYSTEM DESIGN SPECIFICATION

3.5 Input design

3.6 Output design