A

Project Report
On

“RADHIKA JEWELLARS”

Submitted in partial fulfillment of the requirements for the award of degree

Post Graduate Diploma in Computer Application
From
Pt. Ravishankar Shukla University, Raipur (C.G.)

Year: 2018-19

Guide by: Submitted By:

Mr. Vikas Sharma kajal vanshi
(Dept.of computer science)

Submitted to

Agrasen Mahavidhyalay, purani basti , Raipur

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

1
 CERTIFICATE OF APPROVAL
This is to certify that the project work entitled “RADHIKA JEWELLARS” is
carried out by kajal vanshi, a student of PGDCA II Sem at Agarsen
Mahavidyalaya Purani Basti is here by approved as a credible work in the
degree of Post Graduation Diploma In Computer Application during the year
2018-19 From Pt. Ravishankar Shukla University, Raipur (CG).

Mr.Vikas Sharma
H.O.D
(Dept. of Comp. Sci.)

2
 CERTIFICATE
This is to certify that the project work entitled “RADHIKA JEWELLARS”
Submitted to the Agarsen Mahavidyalaya by kajal vanshi,in partial fulfillment
for the requirement relating to nature and standard of the award of Post
Graduation Diploma In Computer Application degree by, Pt. Ravishankar
Shukla University, Raipur (CG) for the academic year
2018-19.This project work has been carried out under my guidance.

(Guide Name)
Mr. Vikas Sharma

Mr. Vaibhav Ingle

3
 CERTIFICATE OF EVALUATION
This is to certify that the project work entitled “RADHIKA JEWELLARS” is
carried out by kajal vanshi, a student of PGDCA II Semester at Agarsen
Mahavidyalaya, after proper evaluation and examination, is hereby approved
as a credible work in the discipline of computer science and is done in a
satisfactory manner for its acceptance as a requisite for the award of Post
Graduation Diploma In Computer Application II Semester during the year
2018-2019 from Pt. Ravishankar Shukla University, Raipur (CG)

Internal Examiner External Examiner

4
 DECLARATION
This is to certify that the project work entitled “RADHIKA JEWELLARS”
which is submitted by me in the partial fulfillment for the award of the degree
of Post Graduation Diploma In Computer Application, Agrasen
Mahavidyalaya Purani Basti, 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 kajal vanshi
Date: PGDCA II Semester

5
 ACKNOWLEDGEMENT
This project is an inspiration, support, guidance, corporation and
facilities that were extended to us at their best and by person at all levels.
We were indebted to all of them.
We wish to acknowledgement our profound sense of gratitude to
the project guide Mr. Vikas Sharma for their remarkable guidance and
continued encouragement during the development of project. It was a
matter of great felicity and privilege for us to work under the aegis. We
would like to extend our special thanks to (Principal of- Agrasen
Mahavidyalaya Purani Basti) for boosting our confidence when we
were lacking so.
We offer our sincere thanks to Department staff members. Finally we
would also like to thank our entire classmate for their corporation and
support. We would like to pay our everlasting regards to our “Agrasen
Mahavidyalaya Purani Basti” Where this project gets completed.

6
 Index
1. Objective & Scope of the project
2. Theoretical Background of Project
3. Definition of problem
4. System Analysis & Design
5. Methodology adopted, system Implementation & Detail of Hardware & Software used
6. System maintenance & Evaluation
7. Cost and benefit Analysis
8. Detailed Life Cycle of the project
o ERD,DFD
o Input and Out Put Screen Design
o Process involved
o Methodology used for testing
o Test Report, Printout of the code sheet

9. Conclusion

10. Future Scope of the Project

11.soft copy

7
OBJECTIVE AND SCOPE OF PROJECT

OBJECTIVES :-
As we all know about the manual work which creates much waste of time to maintain the records

for an organization. Here is presenting a product related with USHA SAHU through which the

user can Add, Modify or replace the records such as: Employee detail, Staff Detail, Connection

detail, Report details, Expences details for their organization. This project includes a login

window which contain a unique ID and Password , with the help of which, this project becomes

much secure and only the user who is eligible for accessing the project will be authorized for any

changes regarding the project.

This project is easy to use for all. Its features like Menu driven programming makes it

familiar with the user. Multiple of works can be done at a point of time.

It enhances accuracy in calculation and reduce the efforts. This software mainly deals

with computerized system.

8
THE FOLLOWING TOPICS INTRODUCE SELECTED NEW FEATURES:

 New Client/Server Active Data Object (ADO) Features

Introduces new features of ADO, including support of RDO, segmentation of the ADO/Jet

architecture, and enhanced error management.

 New Remote Data Object (RDO) Features

Summarize what’s new in RDO, including event-driven programming, a new client batch cursor

library, batch optistic queries, and more.

 New Remote Data Control Features

Presents a table outlining six new properties to implement optimistic client batch update.

9
 EVENT DRIVEN PROGRAMMING

Visual Basic is Object Oriented, i.e. it revolves around readymade objects and it is called
as EVENT DRIVEN, i.e. all the activities in a program are triggered by one event or another.
Each object has its own properties,

Determining its position, size, color, the appearance and nature of its text, and much more. Each
object also has its own event handling procedures.
In an event driven application the code doesn’t follows a predefined path, it executes
different code section in response to events. Events can be triggered by the user action, by
message from the system of other application or even from application itself. The sequence of
this event determines the sequence in which codes executes. Thus the path through the
application code written each time the program runs.
Visual basic system knows all about event handling procedures. It knows what a button is
and how it works. It also knows how to handle images, menus, dialog boxes, driven and
directory lists, and much else. The programmer’s job is to determine where, how and when an
object appears on screen, what its caption reads and what happens when an event occurs. The
event might be the opening of a form, the user clicking on a box. The programmer does not have
to write code to trap these events the system does that automatically. Because the program code
runs in response to event, as at any point whole range of event might be possible. The flow of
execution is not as fixed as in a traditional program.
The Pointer :-
The pointer is different from the rest of the tools, and is used for selecting object
that have been placed on the form. The system reverts to this when finished using any other tool.
It is marked by an arrow cursor.

A Picture Box :-
A picture box holds pictures created with paintbrush or similar art packages.
These must be in an acceptable- .BMP, .WMF, .ICO or .DMB, note that the commonly used
.PCX format is not acceptable.

10
Labels and Text boxes :-
Labels and Textboxes both hold text, but only the textboxes is capable of
receiving input from the user.
A Frame :-
A frame simply holds things together. If you place a set of controls within a
frame, they are all moved together as the frame is moved. Note that once a control has been
placed in a frame, it cannot be moved out onto the form and vice versa.
Command Button :-
Command button are one method of selection. They are typically used where
there are only a limited number of options – the choice may be OK or cancel, start or Quit.
Check Boxes :-
Check boxes act as toggle switches, turning options on or off.
Option Button :-
Option buttons are normally used to select one from a set of mutually exclusive
options.
List Boxes :-
List boxes display lists of items, so that the user can see what is available and
select one. If the list is too long to fit in the box, vertical scroll bars will be added at run time.

A Combo Box :-
A combo box combine a drop-down list with a slot in which users can enter their
own data when the program is running.
The Horizontal and Vertical scroll bars :-
The horizontal and vertical scroll bars are used on form to give a very flexible
means of setting values. You set the minimum and maximum values-anything between- 32768
and 32767.
The Timer :-
The timer is unusual in that it is of fixed size and is invisible once the program is
running. Its purpose is to control actions that must take place at or after intervals.

11
The Drive List box, Directory List box and File List box :-
The Drive List box, Directory List box and File List box can be used together to
give the standard Windows file management facilities. When the program runs they will initially
display the current drive and directory.
The Shape :-
The shape (a circle, oval, square or rectangle) and the Line are for purely
decorative purposes. For anything other than the simplest design, you will probably be better off
creating it with Paintbrush and importing into a picture or image box.
An Image :-
An Image is a limited version of a picture box. It has fewer features, but is
updated faster.
The Data Control :-
The Data control allows you to read records in from a database.

The Command Dialog and Grid :-

The Command Dialog and Grid controls are made available through the CMDIALOG. VBX and
GRID. VBX files. The first produces standard Windows dialog boxes for file opening and
saving, printing and similar operations.
OLE :-
OLE stands for Object Linking and Embedding. This control allows you to make a two-way link
with an object in another Windows application.

12
BACKEND :- MS-ACCESS

Access is an electronic database management system whose purpose I to help you to collect,

retrieve and present data for e.g.- with a company personal database you may want to collect

data, retrieve for viewing and exporting to Excel.

Objects of Access Database: Following are the six types of objects available in Access.

1. TABLES: A table is collection of data about a specific topic such has products and
suppliers. Tables are the fundamental structure in an access database because it stores the
data that you would be managing. Using a separate table for each topic means that you store
that data only once, which makes your database more efficient, and reduces data entry
errors.

2. QUERIES: A query is a tool for asking questions about data in your tables and for
performing action to your data. Queries can answer questions such as how many students
are below age of 15. You use query to view, change the analyze data in different ways. You
can also use them as the sources of records for forms, reports and data access page.
3. FORMS: Forms let you display and enter data in a convenient format that looks like a
fill in the blank form. Your forms can be plain and simple or quit elaborate with graphics,
lines and automatic look-up features that may data entry quick and easy. Forms can even
include other forms that let you enter data into several tables at once.
4. REMOTES: A report is effective way to present the data in a printed format, because
you have a control over the size and appearance of everything on a report, you can display
the information the way you want to see it.
5. MACROS: A macro is a set of one or more actions that each perform particular
operation, such as opening a form or printing a report. Macros can help you to automate
common tasks. For example, you can run macro that print a report when a user clicks a
command button.
6. MODULE: A module is collection of a VB for applications declarations and
procedures that are stored together as a unit. Like macros, modules allow you to automate
and customize access.

13
 DEFINITION OF PROBLEM

 ALL WORK IS PERFORMED MANUALLY.

 BECAUSE OF MANUAL WORK IS TIME CONSUMING.
 NO SECURITY FEATURE IS THERE THAT WHY ANY ONE CAN
EASILY SEE THE RECORDS AND CHANG THE RECORDS.
 RETRIEVING DATA IS ALSO TIME CONSUMING.
 POSSIBILITY OF LOSING THE RECORD’S HIGH.

14
 SYSTEM ANALYSIS AND DESIGNING

SYSTEM ANALYSIS

EXISTING SYSTEM:

System Analysis is a detailed study of the various operations performed by a system and their
relationships within and outside of the system. Here the key question is- what all problems exist
in the present system? What must be done to solve the problem? Analysis Begins when a user or
manager begins a study of the program using existing system.

During analysis, data collected on the various files, decision points and transactions handled by
the present system. The commonly used tools in the system are Data Flow Diagram, interviews,
etc. Training, experience and common sense are required for collection of relevant information
needed to develop the system. The success of the system depends largely on how clearly the
problem is defined, thoroughly investigated and properly carried out through the choice of
solution. A good analysis model should provide not only the mechanisms of problem
understanding but also the frame work of the solution. Thus it should be studied thoroughly by
collecting data about the system. Then the proposed system should be analyzed thoroughly in
accordance with the needs.

System analysis can be categorized into four parts.

1. System planning and initial investigation
2. Information Gathering
3. Applying analysis tools for structured analysis
4. Feasibility study
5. Cost/ Benefit analysis.

In the current system we need to keep a number of records related to the student.

15
Proposed System

In our proposed system we have the provision for adding the details of the students. Another
advantage of the system is that it is very easy to edit the details of the student and delete a
student when it found unnecessary. Here is no facility of net connection, email facility is also not
provided. Online Admissions is not possible.
By developing the system, we can attain the following facilities:
Easy to handle and feasible.
Easy to operate.
Cost reduction.
Fast and convenient.
Computerization will almost minimize all the shortcoming of current manual system.
Computerization will be helpful in reducing extra manpower.
Data stored in computer is easily accessible than current manual system.
Searching any information in current manual system is tedious job as we have to go on
searching all the file and records.
Computerization make searching easy and instantaneous. Also, the results obtained are
consistent.
Computerization will definitely reduce paper work and thus reduce possibility of human
error.
It provides user-friendly interface to the user.
The graphical user interface makes the application more attractive and easily understandable
to the user.

Feasibility Study
Whatever we think need not be feasible .It is wise to think about the feasibility of any
problem we undertake. Feasibility is the study of impact, which happens in the organization by
the development of a system. The impact can be either positive or negative. When the positives
nominate the negatives, then the system is considered feasible. Here the feasibility study can be
performed in two ways such as technical feasibility and Economical Feasibility.

16
Technical Feasibility:
We can strongly says that it is technically feasible, since there will not be much difficulty in
getting required resources for the development and maintaining the system as well. All the
resources needed for the development of the software as well as the maintenance of the same is
available in the organization here we are utilizing the resources which are available already.

Economical Feasibility

Development of this application is highly economically feasible .The organization needed not
spend much m money for the development of t he system already available. The only thing is to
be done is making an environment for the development with an effective supervision. I f we are
doing so , we can attain the maximum usability of the corresponding resources .Even after the
development , the organization will not be in a condition to invest more in t he organization
.There fore , the system is economically feasible.

17
 SYSTEM DESIGN

System Design is the solution to the creation of a new system. This is the important aspect made
up of several steps. The complete, efficient and successful system should provide the following
in succession: -
1. From where should we start
2. Where we have to go
3. Where should we stop

If the project is to be successful, we will need answer these questions. The answer of these
questions is schema manner and is known as system design. A systematic manner will be
followed so as to achieve beneficial result at the end. It involves starting with a vague idea and
ultimately developing it up into a useful system. The design phase is transition from a user
oriented to a document oriented to the programmers. The steps for the successful project are as
follows: -
1. We should define problem completely and the goals should be known before our
destination
In the next step, we should specify inputs and outputs of our interest

1. Then the structure of various database should be designed which will be used during the
programming

2. Next, we should design our programs of user friendly nature and always provide a way
to the user to read back the origin if he/she find any complex problem at any stage

3. We should know the function of each and every program which will leads us to or helps
us to read at the specified goal.

4. Then we write these individual programs which later on joining solve our problem

5. Next step involve then testing of these programs and correction – if necessary

6. At last, linking all the programs in a well-specified manner and combining in the form of
a menu, submenu etc. will be our defined problem.

18
METHODOLOGY ADOPTED SYSTEM IMPLEMENTATION &
DETAIL OF HARDWARE AND SOFTWARE REQUIREMENTS

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.

19
  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 interacting 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 requirements.
 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 the 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:

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

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

SYSTEM IMPLEMENTATION

Implementation is the stage in the project where the theoretical design is turned into a working
system. The implementation phase constructs, installs and operates the new system. The most
crucial stage in achieving a new successful system is that it will work efficiently and effectively.
There are several activities involved while implementing a new project. They are
1. End user training
2. End user Education
3. Training on the application software
4. System Design
5. Parallel Run and To New System
6. Post implementation Review

21
End user Training:
The successful implementation of the new system will purely upon the involvement of the
officers working in that department. The officers will be imparted the necessary training on the
new technology

End User Education:

The education of the end user start after the implementation and testing is over.
When the system is found to be more difficult to understand and complex, more effort is put to
educate the end used to make them aware of the system, giving them lectures about the new
system and providing them necessary documents and materials about how the system can do this.
Training of application software:
After providing the necessary basic training on the computer awareness, the users will have to be
trained upon the new system such as the screen flows and screen design type of help on the
screen, type of errors while entering the data, the corresponding validation check
At each entry and the way to correct the data entered. It should then cover information needed by
the specific user or group to use the system.
Post Implementation View:
The department is planning a method to know the states of the past implementation process. For
that regular meeting will be arranged by the concerned officers about the implementation
problem and success.

22
DETAILS OF HARDWARE AND SOFTWARE REQUIREMENTS

Software Requirements.

 Software is a set of instructions (computer program) that when executed provide desired
function and performance, data structures that enables the program to adequately
manipulate information, and the Documents that describe the operation and use of
program. The minimum software required to execute this application as well as operating
environment is also mentioned below:

 Operating system : Windows 98 or Windows above

Versions

 Back End : MS ACCESS

 Front End : VISUAL STUDIO 6.0

23
 Hardware Requirement

Memory : 128 MB RAM or higher

Processor : Pentium II or above
Disk Space : 10 GB or higher
Keyboard : Standard 101 keys
Mouse : PC Mouse
Monitor : SVGA Monitor or VGA Monitor
Printer : Laser printer

24
 SYSTEM MAINTAINENECE AND EVALUATION

Maintenance :

After the system was installed it was continuously analyzed

For defects, errors & compatibility problems. In case of an error
Or problem, it was rectified on the spot or within an acceptable
time frame.

Evaluation :

In today’s world, none of the system is completely perfect.

As the various requirements of user keeps on changing, the
Software needs to be further modified. <<<>>> is a report
generation tool which is used to represent data in different
Formats. Also, our proposed system can be further enhanced.
Our system has following limitations as follows:-

 All the various generated reports are in form of a file

Which is stored on the machine’s disk consuming some

Amount of space.
 This system does not supports multi-table queries in which more than one table is used.

 Also this system does not perform any of the summary

query operations.
 The new features can be added in our system to overcome the above limitations. These
are:

 We would like to reduce the disk space occupied by

our system’s report file.

 The proposed system should support various multitables

queries as well as sub-queries operations

25
 ENTITY RELATIONSHIP DIAGRAM

NEW OPEN Detail

ADDMISSION

Has ADDMISSION

SANJEEVANIV STAFF DETAIL NEW ENTRY

RIDHASHRAM

Has
STAFF

Login

Has HELP

Administration Password

CONTACT
Complain

username

26
 DATABASE DESIGN
Database is an integrated collection of data and provides a centralized access to the data and
makes possible to treat data as a separate resource. Usually centralized data managing software
is called a Microsoft Access. The most significant different between Ms-Access and other type
of Data Management is the separation of data as seen by the program and data as store of on the
direct access storage device. This is the difference between logical and physical data.

TABLES

Login Table
Field Name Data Type
Username Text
Password Text

ADD Table
NAME TEXT
ADD TEXT
CONTACT NO. NUMBER
DATE OF BIRTH NUMBER

27
ITEM Table
ITEM CODE NUMBER
ITEM NAME TEXT
WEIGHT GMS NUMBER
RATE NUMBER
CATAGORY TEXT

TRANSACTION
S.NO. NUMBER
DATE NUMBER
CUSTOMER NAME TEXT
ADD TEXT

REPORT
CUSTOMER WISE ITEM WISE

28
Login Table

29
CATAGORY

CUSTOMER

30
ITEM

MAIN

31
MAIN0

MAIN2

32
 SCREEN DESIGNS:-

LOGIN FORM

33
SPLASH FORM

34
ITEM

35
NEW CUSTOMER

36
NEW CATAGORY

37
BILL

38
ENTRY FORM

39
REPORTS FORM

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

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

42
WHITE BOX TESTING DIAGRAM

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

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

44
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

45
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

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

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

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

49
 Coding

LOGIN FORM CODING

Private Sub Command1_Click()

If Text1.Text = "usha" And Text2.Text = "sahu" Then

Form1.Hide

form2.Show

Else

MsgBox "Please try again"

End If

End Sub

50
 MDI FORM CODING
Private Sub ITEM_Click()

Form1.Show

End Sub

Private Sub REPORT_Click()

DataReport2.Show

End Sub

Private Sub NEW CUSTOMR_Click()

Form2.Show

End Sub

Private Sub REPORT_Click()

DataReport3.Show

End Sub

Private Sub NEW CATAGORY_Click()

Form3.Show

End Sub

Private Sub BILL_Click()

51
Form4.Show

End Sub

Private Sub REPORT_Click()

DataReport1.Show

End Sub

Private Sub ENTRY FORM_Click()

Form 5.Show

End Sub

Private Sub REPORTS FORM_Click()

Form6.Show

End Sub

52
 NEW ITEM CODING

Dim db As Database

Dim rs As Recordset

Dim cat As Recordset ' catagory

Private Sub Combo1_GotFocus()

Combo1.BackColor = vbYellow

End Sub

Private Sub Combo1_LostFocus()

Combo1.BackColor = vbWhite

End Sub

Private Sub Command1_Click()

If Text1.Text = "" Or Text2.Text = "" Or Text3.Text = "" Or

Text4.Text = "" Or Combo1.Text = "" Then

MsgBox ("enter complete details")

Text1.SetFocus

Else

53
Flag = 0

rs.MoveFirst

For i = 1 To rs.RecordCount

If Text2.Text = rs.Fields(0) Then

MsgBox "Duplicate Entry"

Flag = 1

Exit For

End If

rs.MoveNext

Next i

If Flag = 0 Then

rs.AddNew

rs.Fields(0) = Text2.Text

rs.Fields(1) = Text1.Text

rs.Fields(2) = Text3.Text

rs.Fields(3) = Text4.Text

rs.Fields(4) = Combo1.Text

rs.Update

MsgBox "Record Saved Successfully"

Text1.Text = ""

54
Text2.Text = ""

Text3.Text = ""

Text4.Text = ""

Combo1.Text = ""

Text1.SetFocus

Else

Text2.SetFocus

Text2.SelStart = 0

Text2.SelLength = Len(Text2.Text)

End If

End If

End Sub

Private Sub Command2_Click()

If Text1.Text = "" Or Text2.Text = "" Or Text3.Text = "" Or

Text4.Text = "" Or Combo1.Text = "" Then

MsgBox ("No item Selected")

Else

rs.Delete

MsgBox "Item Deleted"

rs.MoveFirst

Text2.Text = rs.Fields(0)

55
Text1.Text = rs.Fields(1)

Text3.Text = rs.Fields(2)

Text4.Text = rs.Fields(3)

Combo1.Text = rs.Fields(4)

End If

End Sub

Private Sub Command3_Click()

If Text1.Text = "" Or Text2.Text = "" Or Text3.Text = "" Or

Text4.Text = "" Or Combo1.Text = "" Then

MsgBox ("No item Selected")

Else

rs.Edit

rs.Fields(0) = Text2.Text

rs.Fields(1) = Text1.Text

rs.Fields(2) = Text3.Text

rs.Fields(3) = Text4.Text

rs.Fields(4) = Combo1.Text

rs.Update

MsgBox "Record Modified"

End If

End Sub

56
Private Sub Command4_Click()

rs.MoveFirst

Text2.Text = rs.Fields(0)

Text1.Text = rs.Fields(1)

Text3.Text = rs.Fields(2)

Text4.Text = rs.Fields(3)

Combo1.Text = rs.Fields(4)

End Sub

Private Sub Command5_Click()

rs.MovePrevious

If rs.BOF = True Then

MsgBox "First Record"

rs.MoveFirst

Text2.Text = rs.Fields(0)

Text1.Text = rs.Fields(1)

Text3.Text = rs.Fields(2)

Text4.Text = rs.Fields(3)

Combo1.Text = rs.Fields(4)

Else

57
Text2.Text = rs.Fields(0)

Text1.Text = rs.Fields(1)

Text3.Text = rs.Fields(2)

Text4.Text = rs.Fields(3)

Combo1.Text = rs.Fields(4)

End If

End Sub

Private Sub Command6_Click()

rs.MoveNext

If rs.EOF = True Then

MsgBox "Last Record"

rs.MoveLast

Else

Text2.Text = rs.Fields(0)

Text1.Text = rs.Fields(1)

Text3.Text = rs.Fields(2)

Text4.Text = rs.Fields(3)

Combo1.Text = rs.Fields(4)

End If

End Sub

58
Private Sub Command7_Click()

rs.MoveLast

Text2.Text = rs.Fields(0)

Text1.Text = rs.Fields(1)

Text3.Text = rs.Fields(2)

Text4.Text = rs.Fields(3)

Combo1.Text = rs.Fields(4)

End Sub

Private Sub Command8_Click()

Text1.Text = ""

Text2.Text = ""

Text3.Text = ""

Text4.Text = ""

Combo1.Text = ""

Text1.SetFocus

End Sub

Private Sub Command9_Click()

Form1.Hide

Form2.Hide

59
Form3.Hide

Form4.Hide

Form5.Hide

Form6.Hide

MDIForm1.Show

End Sub

Private Sub Form_Load()

Set db = OpenDatabase("mydb.mdb")

Set rs = db.OpenRecordset("item")

Set cat = db.OpenRecordset("catagory")

cat.MoveFirst

For i Combo1.AddItem cat.Fields(0)

cat.MoveNext

Next i

End Sub

Private Sub Text1_GotFocus()

Text1.BackColor = vbYellow

End Sub

Private Sub Text1_LostFocus()

Text1.BackColor = vbWhite

60
End Sub

Private Sub Text2_GotFocus()

Text2.BackColor = vbYellow

End Sub

Private Sub text2_KeyPress(KeyAscii As Integer)

If KeyAscii >= 48 And KeyAscii <= 57 Then

KeyAscii = 0

MsgBox ("please enter only characters")

End If

End Sub

Private Sub Text2_LostFocus()

Text2.BackColor = vbWhite

End Sub

Private Sub Text3_GotFocus()

Text3.BackColor = vbYellow

End Sub

Private Sub text3_KeyPress(KeyAscii As Integer)

If (KeyAscii < 48 Or KeyAscii > 57) Then

If KeyAscii <> 39 Then

If KeyAscii <> 32 Then

61
CONCLUSION

 The project has been appreciated by all the users in the organization.

 It is easy to use, since it uses the GUI provided in the user dialog.

 User friendly screens are provided.

 The usage of software increases the efficiency, decreases the effort.

 It has been thoroughly tested and implemented.

62
FUTURE SCOPE OF THE PROJECT

There are many more features which can be added to this project. In futures this software

can be expanded easily. Those features will make this software to perform many more function

& this will make more useful. Some of the features which can be added to this software are

following:

a. Details of all the members of an institute cannot be maintained through this

software.

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

c. Online registration is possible using this software.

63