A

Project Report

On

Interior decoration

Submitted In Partial Fulfillment of the Requirements for the Award of the Degree

Post Graduate Diploma in Computer Application Sem - II

From

Pt. Ravishankar Shukla University, Raipur (C.G.)

Year: 2016-17

Guide by: Submitted By:

Mrs.Deepshikha Sharma Mamta Sen
(Dept.of computer science) Roll No.1656470

Submitted to

Gurukul Mahila Mahavidhyalay, Kalibadi, Raipur

Pt.RaviShankar Shukla University,Raipur(C.G)

 CERTIFICATE OF APPROVAL

This is to certify that the Project work entitled “Interior Decoration”

is carried out by Mamta Sen a student of PGDCA. at Gurukul Mahila
Mahavidhyalaya is hereby approved as a credible work in the discipline of
Computer Science & Information Technology for the award of degree of Post
Graduate Diploma in Computer Application during the year 2016-17 from Pt.
Ravishankar Shukla University, Raipur (C.G).

Mrs. Amita Telang

H.O.D
(Dept. of Comp. Sci.)
 CERTIFICATE

This is to certify that the project work entitled “Interior Decoration”

Submitted to the Gurukul Mahila Mahavidhyalay bY MAMTA SEN Roll
No.1656470 in partial fulfillment of the requirements relating to nature and
standard of the award of Post Graduate Diploma in Computer Application
degree by, Pt. Ravishankar Shukla University, Raipur (C.G) for the academic
year 2016-2017.

This project work has been carried under my guidance.

Guided by:
Mrs.Deepshikha Sharma
 CERTIFICATE OF EVALUATION

This is to certify that the project report entitled “Interior

Decoration” is carried out by Mamta Sen, a student of PGDCA at Gurukul
Mahila Mahavidhyalay, after proper evaluation and examination, is hereby
approved as a credible work in the discipline of Computer Science &
Information Technology and is done in a satisfactory manner for its acceptance
as a requisite for the award of degree of Post Graduate Diploma in Computer
Application during the year 2016-17 from Pt. Ravishankar Shukla
University, Raipur (C.G).

Internal Examiner External Examiner

Date: Date:
 DECLARATION
This to certify that the project report entitled ” Interior Decoration “,
which is submitted by me in the partial fulfillment for the award of the degree
of Post Graduate Diploma in Computer Application, Gurukul Mahila
Mahavidhyalay, comprises the original work carried out by me.

I further declare that the work reported in this project has not been
submitted and will not be submitted, either in part or in full for the award of any
other degree or diploma in this Institute or any other Institute or University.

Place : Raipur Name: Mamta Sen

Date: Roll no:

 ACKNOWLEDGEMENT

The satisfaction that accompanies that the successful

completion of any task would be incomplete without the mention of people
whose ceaseless cooperation made it possible, whose constant guidance and
encouragement crown all efforts with success.
Firstly I would like to say I am extremely
grateful and remain indebted to our guide Mrs.Deepshikha Sharma for being
a source of inspiration and for his constant support in the Design,
Implementation and Evaluation of the project. I am also thankful to Mrs. Amita
Telang for their constant constructive criticism and invaluable suggestions,
which benefited us a lotwhile developing the project on “Bajaj Automobile

(Mamta Sen)
”.

INDEX
S.No. Page No.
Particular
1. Synopsis of the project
2. Objectives & Scope of the project
3. Theoretical Background of project
4. Definition of problem
5. System Analysis and Design
6. System Planning
7. Methodology adopted, System Implementation & Details
of Hardware & Software used
8. System maintenance & Evaluation
9. Cost and benefits Analysis
10. Detailed life cycle of the Project
a. ERD, DFD
b. Input and Output screen design
c. Process involved
d. Methodology used for testing
e. Test report, Printout of the code sheet

11. User/Operational Manual Including Security aspects,

access rights,back up,controls,etc
12. Conclusion
13. References
14. Soft Copy Of the project
 Synopsis of the PROJECT

This project “Interior Decorator Management” use the

concept of database file to maintain the various transaction for hostel
management, i.e. adding new records of student, update the record
and delete the record as well as new hostel room facility and update
the record of room for hostel.
This project gives the detail of room from which the students are
related for their residence. It also maintains the records of all student
with their educational qualification and courses detail.
This project also gives the detail of all payments with the
student regarding hostel fees and their convenience as well as expense
of hostel date by date.

With project information crept in many doubts regarding the

project's database, front-end, etc. We started thinking about Ms-
Access's database as our Back-end and Visual Basic 6.0 as our Front-
end. But soon we realized that it wouldn‟t be portable from one
machine to other. Now what?

One whole day just passed thinking on this topic. We figured

out many ways to backup the data and add portability to it, but all in
vein...
 OBJECTIVES AND SCOPES

Objective:-

This project is mainly designed for “INTERIOR DECORATION” They

have to keep records of “INTERIOR DECORATION” and their details.

Whereas, of computerized, all the information's will be friendly as

user. It reduces time consumption and company also and much more
accuracy also exists. It can update values and date automatically.

This graphical based user-friendly software help user to solved their

problems and retrieves any information very easily.
Scope:-

The scope of this module is to study and develop the computerized

“Member, Staff and schemes management ” for “POLICE STATION
MANAGEMENTSYSTEM”
The proposed system will function on:
1. Police stations management information .
2. Details of Police station management.
3. Details regarding criminals.
4. Search: chooses the option for data member, field and value for
search.
5. Informative record for available item
6. Data report:
 Member records
 Police station management information records
 The0retical background of project

Proposed System:-

The Present system Developed in Visual Basic / MS Access is a user

friendly and error proof package .It means all the requirement of the proper

Management System for the Agency.

 The report is made to be used in very comfortable manner, all the report is

managed using a single screen only so that the user may not be confused

 The between dates report used in this project is very user friendly & provides

wide variety of report

 This System avoids redundancy of data as it is developed in RDBMS.

 It occupies comparatively a little amount of disk Space.

 All the security levels maintained by the DBA prevent unauthorized users

from manipulating the data.

 DefinAtion of ProbleM

Problems in this project are following:

a. Details of all the members of an institute can not be maintained through

this software.

b. This software can not be used over network/internet.

c. Online registration is not possible using this software.

Solution Of These Problems:-

• Reliability: The project performs intended function with required

precision; hence this project is very reliable.

• Feasibility: The project maintenance is very easy and modifications

can be made in the existing system in future. All data will locate as

centralized.

• Online Processing: The online processing of the project is very simple

following the existing manual method without changes and suitable

validation is provided for the easy and correct access of users.

Security: Security measures are taken to avoid mishandling of database.

Password restrictions are provided to enter into database. A correct password
only will access to the database
 PURPOSE OF THE PROJECT

The project was initially formally discussed among us and later designedin VB
6.0. The project's back end is Microsoft Access. The program, as the name
suggests is an “Hostel Management” maintains records in the organization.

The main objectives of the project are:

1. To get work done fast.
2. To make-work easy, simple and unbiased.

While making the project we had following goals in our mind:

1. Make it user friendly

(a) By creating the database search option.
(b) Any operation requires just single mouse click.
(c) Frequent reporting
(d) Huge data storage facility

2. Concentrate on Accuracy

3. Make it reliable and Efficient

4. Fully Secure system

Only authorized user can update records
 SYSTEM ANALYSIS

INTRODUCTION:-

After analyzing the requirements of the task performed, the next step is to
analyze the problem and understand its context this first activity in the phase is
studying the existing system and other is to understand the requirement and
domain of new system. Both the activities are equally important, but the first
activity serves as the basis of the proposed system. Understanding the
properties and requirement of a new system is more difficult and require
creative thinking. It can be made effective only when we have through
understanding of the existing system. The process becomes even more difficult
when the existing system is almost entirely different from the one to be
developed.

ANALYSIS MODEL:-
The design starts after the requirement analysis is complete and coding
begins after the design is complete. Once the programming is complete the
testing is done. In this model the sequence of activity performed in a software
development projects are ……
 Requirement analysis

 Project planning

 System design

 Coding

 Unit testing

 System integration

Here the linear ordering of these activities is critical. End of the phase and the
output of one phase is the input of another phase. The output of each has to be
consistent with the overall requirement of the system. Some models are also
incorporated like after the people concerned with the project .Review
completion of each of the phase the work done.
FEASIBILITY STUDY:-
All project are feasible given unlimited resources and infinite time,
unfortunately. The development of a computer based system or product is more
likely plagued. By the scarcity of resources and difficult delivery dares. It is
both necessary and prudent to evaluate the feasibility of a project at the earliest
possible time.

NEED OF COMPUTERIZATION:-
We all know the importance of computerization. The world is moving ahead at a
lighting speed and everyone is running short of time. One always wants to get
the information and perform the task he/she/they desires within a short period
of time and that too with a good amount of efficiency and accuracy. In entry
pass management system this can be achieved through computerization
The whole process of maintaining records is a rather tedious job.
Quarries about past database are not easy to answer in the present system.
Searching of record manually is time consuming and requires data collection
from various registers.
 SYSTEM DESIGN

INTRODUCTION:-

Software design sits at the technical kernel of the software engineering

process and is applied regardless of the development paradigm and area of
application. Design is the first step in the development phase for any engineered
product or system. The designer goal is to produce a model or representation of
an entity that will later be built. Beginning, once system requirement have been
specified and analyzed system design is the first of the three technical activities-
design, code and test that is to build and verify software.
The importance can be stated with a single word “Quality”
.Design is the place where quality is fostered in software development. Design
provides us with representation of software that can access for quality. Design
is the only way that we can accurately translate a customer view into a finished
software product or system. Software design serves as a foundation for all the
software engineering steps that follow. Without strong design we risk building
an unstable system-one that will fall when small changes are made, one that
will be difficult to test, one whose quality cannot be quality, cannot be accessed
until the last stage.
During design progressive refinements of data structure,
program structure and procedural details are developed reviewed and
documented. System design can be viewed from either a technical or project
management perspective.
Methodology adopted,system implementation &
detail

 Methodology Adopted:-

In this project,water fall model is used .

What is water fall model?

The waterfall model is a sequential software development model in which

development is seen as flowing downwards (like a waterfall) through several
phases.

The waterfall model is one of the earliest structured models for software
development. It consists of the following sequential phases through which the
development life cycle progresses:
 • System feasibility. In this phase, you consider the various aspects
of the targeted business process, find out which aspects are worth
incorporating into a system, and evaluate various approaches to building
the required software.

 Requirement analysis. In this phase, you capture software

requirements in such a way that they can be translated into actual use
cases for the system. The requirements can derive from use cases,
performance goals, target deployment, and so on.
 System design.In this phase, you identify the components that make
up the system. You define the exposed interfaces, the communication
between the interfaces, key algorithms used, and the sequence of
interaction. An architecture and design review is conducted at the end of
this phase to ensure that the design conforms to the previously defined
requirementsinteracting.

 Coding and unit testing. In this phase, you write code for the
modules that make up the system. You also review the code and
individually test the functionality of each module.
 Integration and system testing. In this phase, you integrate all
of the modules in the system and test them as a single system for all of
the use cases, making sure that the modules meet the requirements.

 Deployment and maintenance. In this phase, you deploy

software system in the production environment. You then correct any
errors that are identified in this phase, and add or modify functionality
based on the updated requirements.

The waterfall model has the following advantages:

  the It allows you to compartmentalize the life cycle into various phases,
which allows you to plan the resources and effort required through the
development process.

 It enforces testing in every stage in the form of reviews and unit testing.
You conduct design reviews, code reviews, unit testing, and integration
testing during the stages of the life cycle.
 It allows you to set expectations for deliverables after each phase.

The waterfall model has the following disadvantages:

 You do not see a working version of the software until late in the life
cycle. For this reason, you can fail to detect problems until the system
testing phase. Problems may be more costly to fix in this phase than they
would have been earlier in the life cycle.
 When an application is in the system testing phase, it is difficult to
change something that was not carefully considered in the system design
phase. The emphasis on early planning tends to delay or restrict the
amount of change that the testing effort can instigate, which is not the
case when a working model is tested for immediate feedback.
For a phase to begin, the preceding phase must be complete; for example, the
system design phase cannot begin until the requirement analysis phase is
complete and the requirements are frozen. As a result, the waterfall model is
not able to accommodate uncertainties that may persist after a phase is
completed. These uncertainties may lead to delays and extended project
schedules
HARDWARE & SOFTWARE REQUIREMENT

Introduction:-
The hostel management program is an application program for assisting
any hostel accommodation for educational institute and college for managing
the room records, student‟s address record their education detail records .
1. Purpose: automate the manual system
2. Scope of the Project: project/system deals with Block wise hostel rooms
detail, hostel room allocation detail records, payment/ fees receipt,
complain records, and print report
Goals & Purpose
The city hostel management would have the following goals :
- Provide a GUI for hostel to interface with the backend stock detail
database.
- Screens to add/update new admission for the students and room
allocations database
- Screen to search for any record of the student and their room status.
- Payment/Education Entry for students changing their room.

General description
1. Functionality and capabilities
(a) Complete system is GUI i.e. menu driven
(b) Generates any kind of report
(c) Students wise report
(d) Database has no limit

2. User characteristics: administrator has all rights for updating, deletion and
modification.
3. Information flow:
Enquiry for new room  Room Entry  Room Allocation Entry 
Payment / Receipt Entry  reports

4. General constraints
(a) Database will be update every year
(b) No automatic backup facilities
(c) No facility of online reports
SOFTWARE & HARDWARE REQUIREMENT

Programing Language : Microsoft Visual Basic 6.0

Interface requirements
Software :WINDOWS O.S., XP
1. MS ACCESS
2. MsPowerpoint

Front End : Visual Basic

Back End : Ms-Access

Processor :
 Minimum P1 machine or Higher version 133 Mhz
 We use P-IV machine 2.66 GHz.

RAM :
 Minimum 32MB RAM.
 We use 256 MB RAM.

VGA Graphics :
 VGA Support On-Board Motherboard

Floppy Drive :
 1.44 MB – 3 ¼ “ Size

Printer :
 Laser Jet Printer
 Inkjet Printer

CD Rom/Writer :
 52x CD Writer/ROM
 Detailed life cycle of the project

Introduction of visual basic(fronted):-

Fronted:-
MS. Visual Basic the fastest and easiest way to create application for
MS Windows whether you are an experienced professional or brand new
windows programming Visual Basic provides you with a complete set of tools
to simply rapid application develop.

The VISUAL‟ part refer to the method used to create the graphical
user interface (GUI ).Rather than writing numerous lines of code to describe the
appearance and location of interface elements ,you simply add pre-built object
into place on a screen. If you have used a drawing program. Such paint you
already have most of the skills necessary to create an effective user
interface.The „BASIC‟ part refers to the Basic( beginners all purpose symbolic
instruction code) language, a language used by more programmers than any
other language in the history of competing Visual basic has evolved from the
original basic language and now content sever hundred statements function and
keywords, many of which relate directly to window GUI beginners can create
an useful application by learning just a few of the keywords, yet to power of the
language allows professionals to accomplish anything that can be accomplished
using any other window programming language.

BACKEND

In backend we use different tools through which we can manage the

data base in proper way.

MS ACCESS

MS Access is an interactive relational data base management system

for MS Windows. It helps to store, find, organize and present data meaningful.
MS Access is GUI (graphical user interface).MS Access takes
full advantages of the graphical in window which give access to data and
simple way to view and work with the information.
 PROJECT DESIGN

Data Flow Diagram

A data flow diagram is graphical tool used to describe and analyze

movement of data through a system. These are the central tool and the basis
from which the other component are developed. The transformation of data
from input to output, through processed, may be described logically and
independently of physical component associated with the system. These are
known as the logical data flow diagram. The physical data flow diagram shows
the actual implements and movement of data between people, departments, and
work stations. A full description of a system actually consists of a set of data
flow diagram. Using to familiar notations Yourdon, gain and sarson notation
develops the DFD. Each component in a DFD is labled with a descriptive
name. Process is further identified with a number that will be used for
identification purpose. The development of DFD’s is done in several levels.
Each process in lower level diagrams can be broken down into a more detailed
DFD in the next level. The top level diagram is often called context diagram. It
consist a single process bit which play vital role in studying the current system.
The process in the context level diagram is exploded into other process at the 1st
level DFD.
The idea behind the explosion of a process into more process is
that understanding at one level of detail is explosion is necessary and an
adequate amount of detail is described for analyzed to understand the process.
Larry Constantine first developed the DFD as a way of expressing
system requirement in a graphical from this lead to the modular design.
A DFD is also known as “ Bubble Chart” has the process of
clarifying system requirements and identifying major transformation that will
become program in system design to the lowest level of detail. A DFD consist of
a series of bubbles Joined by data flow in the system.

DFD SYMBOLS:

The DFD, there are 4 symbols

 A square defines a source (originator) or destination of system data.

 An arrow identifies data flow. It is the pipeline through which the
information flows.
 A circle or bubbles represent a process that transforms incoming data
flow into outgoing data flows.
  An open rectangle is a data store, data at rest or a temporary repository
of data.

ZERO LEVEL DFD

INPUT OUTPU
PROCESSING T
ENTITY RELATIONSHIP DIAGRAM (E.R.D)
OF HOSTEL MANAGEMENT
FLOW CHART
Start

Data Base Loading

User Name
password

If
Valid

MDIFORM

LOPAD/UNLOAD

REPORT

INSTANCE INSTALATION
CONNECTION PROCESS

End

Data Base Design

 DATA BASE TABLE

ORDER ENTRY DATABASE

Field’s Name Data Type

Block Text
Room_id_no Number
Capacity Text
Facilities Text
Rent Currency
Description Text

QUOTATION DATABASE FILE

Field’s Name Data Type

student_ID Text
Date_of_adm Date
Name Text
Address Text
Contact-No Text
Age Number
Gender Text
 WORK DETAIL ENTRY FILE

Field’s Name Data Type

Student_id Text
RoomNo Number
CourseName Text
Year Number
CollegeName Text
Course_duration Text

PAYMENT RECEIPT FILE

Field’s Name Data Type

Bill_No Text
Bill_Date Date
Distributor Text
Bill_Amount Currency
AmountPaid Currency
ReceiptNo Text
Balance Currency
Input & output screen design
Program List
Quotation Entry
Payment Detail
Order Entry
Payment List
Desine
 METHODOLOGY USED FOR TESTING

SOFTWARE TESTING

Is the menu bar displayed in the appropriate contested some system related features included
either in menus or tools? Do pull –Down menu operation and Tool-bars work properly? Are
all menu function and pull down sub function properly listed ?; Is it possible to invoke each
menu function using a logical assumptions that if all parts of the system are correct, the goal
will be successfully achieved .? In adequate testing or non-testing will leads to errors that
may appear few months later.
This create two problem
1. Time delay between the cause and appearance of the problem.
2. The effect of the system errors on files and records within the system.

The purpose of the system testing is to consider all the likely variations to which it will be
suggested and push the systems to limits.
The testing process focuses on the logical intervals of the software ensuring that all
statements have been tested and on functional interval is

conducting tests to uncover errors and ensure that defined input will produce actual results
that agree with the required results.
Program level testing, modules level testing integrated and carried out.

There are two major type of testing they are

1. White Box Testing.
2. Black Box Testing.

White Box Testing

White box sometimes called “Glass box testing”, “clear box testing”, “transparent box
testing”, and “structural testing” is a test case design uses the control structure of the
procedural design to drive test case.
Using white box testing methods, the following tests were made on the system.

1. All independent paths within a module have been exercised once. In our system,
ensuring that case was selected and executed checked all case structures. The bugs
that were prevailing in some part of the code where fixed
2. All logical decisions were checked for the truth and falsity of the values.
While white-box testing can be applied at the unit, integration and system levels of the
software testing process, it is usually done at the unit level. It can test paths within a unit,
paths between units during integration, and between subsystems during a system–level test.
Though this method of test design can uncover many errors or problems, it might not detect
unimplemented parts of the specification or missing requirements.
WHITE BOX TESTING DIAGRAM

STATEMENT
TESTING

WHITE BOX DECISION

TESTING TESTING

CONDITION
TESTING
White Box Testing

White box testing assumes that the tester can take a look at the code for the application block
and create test cases that look for any potential failure scenarios. During white box testing,
you analyze the code of the application block and prepare test cases for testing the
functionality to ensure that the class is behaving in accordance with the specifications and
testing for robustness.

Input

The following input is required for white box testing:

 Requirements
 Functional specifications
 High-level design documents
 Detailed design documents
 Application block source code

White Box Testing Steps

The white box testing process for an application block is shown in Figure 6.2.
White box testing involves the following steps:

1. Create test plans. Identify all white box test scenarios and prioritize them.
2. Profile the application block. This step involves studying the code at run time to
understand the resource utilization, time spent by various methods and operations,
areas in code that are not accessed, and so on.
3. Test the internal subroutines. This step ensures that the subroutines or the nonpublic
interfaces can handle all types of data appropriately.
4. Test loops and conditional statements. This step focuses on testing the loops and
conditional statements for accuracy and efficiency for different data inputs.
5. Perform security testing. White box security testing helps you understand possible
security loopholes by looking at the way the code handles security.

BLACK BOX TESTING

Black-box testing is a method of software testing that tests the functionality of an application
as opposed to its internal structures or workings .Specific knowledge of the application's
code/internal structure and programming knowledge in general is not required. This is black
box testing enables the software engineering to derive a set of input conditions that will fully
exercise all functional requirements for a program. Black box testing is not an alternative to
White box testing rather it is complementary approach that is likely to uncover a different
class of errors that white box methods like.

The tester is only aware of what the software is supposed to do, but not how i.e. when he
enters a certain input, he gets a certain output; without being aware of how the output was
produced in the first place
1. Interface errors
2. Performance in data structure
3. Performance errors
4. Initializing and termination errors
BLACK BOX TESTING DIAGRAM

Input

The following input is required for black box testing:

 Requirements
 Functional specifications
 High-level design documents
 Application block source code

The black box testing process for an application block is shown below

Black box testing process

Black Box Testing Steps

Black box testing involves testing external interfaces to ensure that the code meets functional
and nonfunctional requirements. The various steps involved in black box testing are the
following:

1. Create test plans. Create prioritized test plans for black box testing.
2. Test the external interfaces. Test the external interfaces for various type of inputs
using automated test suite.
3. Perform load testing. Load test the application block to analyze the behavior at
various load levels. This ensures that it meets all performance objectives that are
stated as requirements.
4. Perform stress testing. Stress test the application block to analyze various
bottlenecks and to identify any issues visible only under extreme load conditions,
such as race conditions and contentions.
5. Perform security testing. Test for possible threats in deployment scenarios. Deploy
the application block in a simulated target environment and try to hack the application
by exploiting any possible weakness of the application block.
6. Perform globalization testing. Execute test cases to ensure that the application block
can be integrated with applications targeted toward locales other than the default
locale used for development.

Step 1: Create Test Plans

The first step in the process of black box testing is to create prioritized test plans. You can
prepare the test cases for black box testing even before you implement the application block.
The test cases are based on the requirements and the functional specification documents.

The detailed test plan document includes test cases for the following:

 Testing the external interfaces with various types of input

 Security testing
 Globalization testing

Step 2: Test the External Interfaces

You need to test the external interfaces of the application block using the following
strategies:

 Ensure that the application block exposes interfaces that address all functional
specifications and requirements. To perform this validation testing, do the
following:
1. Prepare a checklist of all requirements and features that are expected from the
application block.
2. Create test harnesses, such as NUnit, and small "hello world"' applications to
use all exposed APIs of the test application block.
3. Run the test harnesses.

Testing for various types of inputs

. After ensuring that the application block exposes the interfaces that address all of the
functional specifications, you need to test the robustness of these interfaces. You need to test
for the following input types:

 Randomly generated input within a specified range

 Boundary cases for the specified range of input
 The number zero testing if the input is numeric
 The null input
 Invalid input or input that is out of the expected range

This testing ensures that the application block provides expected output for data within the
specified range and gracefully handles all invalid data. Meaningful error messages should be
displayed for invalid input.

Step 3: Perform Load Testing

Use load testing to analyze the application block behavior under normal and peak load
conditions. Load testing allows you to verify that the application block can meet the desired
performance objectives and does not overshoot the allocated budget for resource utilization
such as memory, processor, and network I/O. The requirements document usually lists the
resource utilization budget for the application block and the workload it should be able to
support.

For example, the CMAB had the following performance objectives on a Web server (please
note that these objectives are totally fictitious and are only for the purpose of illustration):

 The CPU overhead should not be more than 7–10 percent.

 The application block should be able to support a minimum of 200 concurrent users
for reading data from SQL Server.
 The application block should be able to support a minimum of 150 concurrent users
for writing data to SQL Server.
 The response time for a client (the client is firing requests from a 100 Mbps VLAN in
the test lab) is not more than 2 seconds for the given concurrent load.

You can measure metrics related to response times, throughput rates, and so on, for the load
test. In addition, you can measure other metrics that help you identify any potential
bottlenecks.

Step 4: Perform Stress Testing

Use stress testing to evaluate the application block's behavior when it is pushed beyond the
normal or peak load conditions. The expectation from the system beyond load conditions is to
either return expected output or return meaningful error messages to the user without
corrupting the integrity of any data. The goal of stress testing is to discover bugs that surface
only under high load conditions, such as synchronization issues, race conditions, and memory
leaks.
Step 5: Perform Security Testing

Black box security testing the application block identifies security vulnerabilities within the
application block by treating it as an independent unit. The testing is done at run time. The
purpose is to forcefully break the interfaces of the application block, intercept sensitive data
within the block, and so on.

Depending on the functionality the application block provides, test cases can be identified.
Examples of test cases and tests can be the following:

 If the application block accepts data from a user, make sure it validates the input data
by creating test cases to pass different types of data, including unsafe data, through
the application block's interfaces and confirming that the application block is able to
stop it and handle it by providing appropriate error messages.

Step 6: Perform Globalization Testing

The goal of globalization testing is to detect potential problems in the application block that
could inhibit its successful integration with an application that uses culture resources different
than the default culture resources used for development. Globalization testing involves
passing culture-specific input to a sample application integrating the application block. It
makes sure that the code can handle all international support and supports any culture or
locale settings without breaking functionality that would cause data loss.

To perform globalization testing, you must install multiple language groups and set the
culture or locale to different cultures or locales, such as Japanese or German, from the local
culture or locale. Executing test cases in both Japanese and German environments, and a
combination of both, can cover most globalization issues.
Order List Report
Payment Detail Report
Quotation Detail Report
CODINGS OF PASSWORD PROGRAM

Private Sub Command1_Click()

If USERNAME = "NICKY" And PASSWORD = "77777" Then
FRMPROCESS.Show
Unload Form1
Else
MsgBox "USERNAME/PASSWORD NOT MATCH"
USERNAME = ""
PASSWORD = ""
End If

End Sub
End Sub

CODINGS OF PROGRESS BAR

Private Sub Timer1_Timer()

If ProgressBar1.Value < 100 Then
ProgressBar1.Value = ProgressBar1 + 10
Else
Form2.Show
Unload FRMPROCESS
End If
End Sub
CODINGS OF MAIN MENU PROGRAM

Private Sub Command1_Click()

frmquotation.Show
End Sub

Private Sub Command10_Click()

frmorderlist.Show
End Sub

Private Sub Command2_Click()

frmOrder.Show
End Sub

Private Sub Command3_Click()

frmPayment.Show
End Sub

Private Sub Command4_Click()

MsgBox " THANKS FOR USING THIS PROJECT"
End
End Sub

Private Sub Command5_Click()

frmcatalog.Show
End Sub

Private Sub Command6_Click()

BILLPRINT.Show
End Sub

Private Sub Command7_Click()

frmpaymentlist.Show
End Sub

Private Sub Command8_Click()

WORKREPORT.Show
End Sub

Private Sub Command9_Click()

DataReport1.Show
End Sub
CODINGS OF MAIN MENU PROGRAM

Private Sub Dir1_Change()

File1.Path = Dir1.Path
End Sub

Private Sub Drive1_Change()

Dir1.Path = Drive1.Drive
End Sub

Private Sub File1_Click()

Dim cn As String
cn = Dir1.Path & "\" & File1.FileName
Image1.Picture = LoadPicture(cn)
lblcatalog.Caption = File1.FileName
End Sub
CODINGS OF NEW ORDER ENTRY PROGRAM

Private Sub cmdAdd_Click()

Data1.Recordset.AddNew
End Sub

Private Sub cmdDelete_Click()

'this may produce an error if you delete the last
'record or the only record in the recordset
Data1.Recordset.Delete
Data1.Recordset.MoveNext
End Sub

Private Sub cmdRefresh_Click()

'this is really only needed for multi user apps
Data1.Refresh
End Sub

Private Sub cmdUpdate_Click()

Data1.UpdateRecord
Data1.Recordset.Bookmark = Data1.Recordset.LastModified
End Sub

Private Sub cmdClose_Click()

Unload Me
End Sub

Private Sub Data1_Error(DataErr As Integer, Response As Integer)

'This is where you would put error handling code
'If you want to ignore errors, comment out the next line
'If you want to trap them, add code here to handle them
MsgBox "Data error event hit err:" & Error$(DataErr)
Response = 0 'throw away the error
End Sub

Private Sub Data1_Reposition()

Screen.MousePointer = vbDefault
On Error Resume Next
'This will display the current record position
'for dynasets and snapshots
Data1.Caption = "Record: " & (Data1.Recordset.AbsolutePosition + 1)
'for the table object you must set the index property when
'the recordset gets created and use the following line
 'Data1.Caption = "Record: " & (Data1.Recordset.RecordCount *
(Data1.Recordset.PercentPosition * 0.01)) + 1
End Sub

Private Sub Data1_Validate(Action As Integer, Save As Integer)

'This is where you put validation code
'This event gets called when the following actions occur
Select Case Action
Case vbDataActionMoveFirst
Case vbDataActionMovePrevious
Case vbDataActionMoveNext
Case vbDataActionMoveLast
Case vbDataActionAddNew
Case vbDataActionUpdate
Case vbDataActionDelete
Case vbDataActionFind
Case vbDataActionBookmark
Case vbDataActionClose
End Select
Screen.MousePointer = vbHourglass
End Sub
 CODINGS OF PAYMENT RECEIPT ENTRY PROGRAM

Private Sub cmdAdd_Click()

Data1.Recordset.AddNew
End Sub

Private Sub cmdDelete_Click()

'this may produce an error if you delete the last
'record or the only record in the recordset
Data1.Recordset.Delete
Data1.Recordset.MoveNext
End Sub

Private Sub cmdRefresh_Click()

'this is really only needed for multi user apps
Data1.Refresh
End Sub

Private Sub cmdUpdate_Click()

Data1.UpdateRecord
Data1.Recordset.Bookmark = Data1.Recordset.LastModified
End Sub

Private Sub cmdClose_Click()

Unload Me
End Sub

Private Sub Data1_Error(DataErr As Integer, Response As Integer)

'This is where you would put error handling code
'If you want to ignore errors, comment out the next line
'If you want to trap them, add code here to handle them
MsgBox "Data error event hit err:" & Error$(DataErr)
Response = 0 'throw away the error
End Sub

Private Sub Data1_Reposition()

Screen.MousePointer = vbDefault
On Error Resume Next
'This will display the current record position
'for dynasets and snapshots
Data1.Caption = "Record: " & (Data1.Recordset.AbsolutePosition + 1)
'for the table object you must set the index property when
'the recordset gets created and use the following line
'Data1.Caption = "Record: " & (Data1.Recordset.RecordCount *
(Data1.Recordset.PercentPosition * 0.01)) + 1
End Sub

Private Sub Data1_Validate(Action As Integer, Save As Integer)

'This is where you put validation code
'This event gets called when the following actions occur
Select Case Action
Case vbDataActionMoveFirst
Case vbDataActionMovePrevious
Case vbDataActionMoveNext
Case vbDataActionMoveLast
Case vbDataActionAddNew
Case vbDataActionUpdate
Case vbDataActionDelete
Case vbDataActionFind
Case vbDataActionBookmark
Case vbDataActionClose
End Select
Screen.MousePointer = vbHourglass
End Sub
 CODINGS OF ORDER REPORT PROGRAM

Private Sub cmdAdd_Click()

Data1.Recordset.AddNew
End Sub

Private Sub cmdDelete_Click()

'this may produce an error if you delete the last
'record or the only record in the recordset
Data1.Recordset.Delete
Data1.Recordset.MoveNext
End Sub

Private Sub cmdRefresh_Click()

'this is really only needed for multi user apps
Data1.Refresh
End Sub

Private Sub cmdUpdate_Click()

Data1.UpdateRecord
Data1.Recordset.Bookmark = Data1.Recordset.LastModified
End Sub

Private Sub cmdClose_Click()

Unload Me
End Sub

Private Sub Data1_Error(DataErr As Integer, Response As Integer)

'This is where you would put error handling code
'If you want to ignore errors, comment out the next line
'If you want to trap them, add code here to handle them
MsgBox "Data error event hit err:" & Error$(DataErr)
Response = 0 'throw away the error
End Sub

Private Sub Data1_Reposition()

Screen.MousePointer = vbDefault
On Error Resume Next
'This will display the current record position
'for dynasets and snapshots
Data1.Caption = "Record: " & (Data1.Recordset.AbsolutePosition + 1)
'for the table object you must set the index property when
'the recordset gets created and use the following line
'Data1.Caption = "Record: " & (Data1.Recordset.RecordCount *
(Data1.Recordset.PercentPosition * 0.01)) + 1
End Sub

Private Sub Data1_Validate(Action As Integer, Save As Integer)

'This is where you put validation code
'This event gets called when the following actions occur
Select Case Action
Case vbDataActionMoveFirst
Case vbDataActionMovePrevious
Case vbDataActionMoveNext
Case vbDataActionMoveLast
Case vbDataActionAddNew
Case vbDataActionUpdate
Case vbDataActionDelete
Case vbDataActionFind
Case vbDataActionBookmark
Case vbDataActionClose
End Select
Screen.MousePointer = vbHourglass
End Sub
 PROBLEMS ENCOUNTERED

While developing the software, we faced many major and minor

problems. Initially, we were not able to connect the database to the front end
and faced some problems related to the connectivity and the consistency of the
database. Then it was very difficult to print the REPORT, as a required printer
driver was not available. Similarly we could not manipulate the Report Page
size.

During deployment, Project didn't work as expected, which helped us to

figure out that program can't be ported to client's machine without setup file as
the program was running fine on our machine but we were unable to run it on
the client's machine in absence of appropriate runtime DLLs (Dynamic Link
Libraries). The most exasperating problem was to print the form thus making it
impossible for us to work further.

We took the help of all the possible people we could ask them for, and
with their assistance we came out in triumph
 FUTURE ENHANCEMENTS

Even after continuous efforts, we couldn't do the following things and

hence decided to leave them for future when we will be more acquainted with
programming. We also tried to in-corporate possible requirement, and updates
but we were not able to do so.

At the outset, speed of the program can be increased. Secondly, the

program can be made more secure by providing multilevel security. The project
neither handles runtime errors nor it reports them to the user rather it crashes
and closes down or continues according to the user's wish, if any crash screen
appears. The database can be made more consistent through indexing the entries
and sorting them and finally storing them. Finally, the software can be upgraded
to VB.NET platform and its features can be added accordingly.
 CONCLUSIONS

It was a wonderful and learning experience for us while working on this

project. This project took us through the various phases of project development
and gave us real insight into the world of software engineering. The joy of
working as a team and the thrill involved while tackling while tackling the
various problems and adopting to the requirements put forward to us by the
customer, gave us a feel of the developers industry.
It was due to this project we came to know how professional software
software‟s are designed and what precautions should be taken. We also found
that it not just the task of an individual, rather a team work, which helped us in
making a firm grip on Visual Basic 6.0
The project has laid the path to the depth of the subject, that requires a
thorough study and in which an Engineering student have flair of proficiency.
We have left no stone unturned while developing this software and making it
easy to understand, easy to navigate through the forms and re-cycling.
We enjoyed each and every bit of work we have put into this project and
its successful completion has given us our credit
 REFERENCES

FOR FRONT END:

 VISUAL BASIC 6.0 BLACK BOOK

 MASTERIND IN VISUAL BASIC 6.0 BY PETER NORTAN

 VISUAL BASIC 6.0 COMPLETE

 COMPLETE REFERENCE VISUAL BASIC

FOR BACK END:

 MSOFFICE 2007 COMPLETE

 MSACCESS 2007 COMPLETE

Site Address

 www.associatedcontent.com

 www.members.tripod.com