Documentations

Address Book
Chapter - 1
INTRODUCTION
1.1. Introduction To Project:
Statement of the Problem:

In the growing world, we has the vast types of social medias, networks, communities and
much more technologies which connects the people but the main thing is to keep the contacts of
the people. However, every mobile has their separate contact Address Book but now a days, the
chances of loss of mobiles are more, and there are many threat to the portable devices to keep
contact in mind and much more, to avoid these problems we can write the contacts in a diary but
writing in diary is not such sufficient because people cannot waste time on adding it and
searching it spending the minutes together.
-Brief description of Project:

The Address Book is the application developed by vb.net which is the Contact Manager
or Address Book for the Windows Operating system. This is developed in order to keep the
contact details of the people connected with them mucmust be safe. The main intention behind
developing the Address Book is to overcome the threat of contact loss. This project gives us the
option to store the unlimited Contacts with all the details safely and securely.
School of CSA, REVA University Page 1

Address Book
The front end used for the Address Book is VB.NET. and back end used for this is MS.
Access database. the main intention of using Ms.Access database is to store the database in safe
manner and at the chances of the software uninstallation or something else we could access back
all our contacts without straining only if we know the user name and password.
The project of Address Book consists of front end as the VB.NET and back end as the
MS.Access database. The main reason is to choose this is because of its flexibility and code
reusability.
1.2. Introduction to Visual Basic.NET:

The visual basic is the integrated development environment(IDE) which is a powerful
graphical user interface(GUI) development software, which works on the windows Up and
above. This software comes in three editions: learners, professional and enterprise edition. VB
also has third party controls for specialized task.
Fig: Visual Basic . NET
What makes the VB different from almost from other programming tool is the ease with
which the interface can be developed. We initially draw the user interface, much like paint

Address Book
diagram. In addition, when you have done drawing the interface, the command buttons,
textboxes, labels and etc… will be automatically recognize the user actions., such as a mouse
movements and button clicks. VB also comes with the containers like menu designing which is
both like popup and direct menus on a snap and toolbox and much more.
Only after you design the complete form the traditional programming process will starts.
This leads to the second step in building a VB applications: writing the code to activate the
interface you built in the step one. The point is, objects in VB will recognize events like mouse
clicks: how the objects are respond to them based on the code you write, you will almost always
need to write code in order to make controls respond to the events. This makes VB programming
fundamentally different from conventional programming.
Programs in conventional programming languages runs from the top – down. For older
programming languages, execution starts from the first line and moves with the flow of the
program to different parts as needed. A VB program works completely differently. The core of
VB program is a set of independent pieces of the code that are activated by, and so respond to,
only the events they have been told to recognize. This is a fundamental shift. Now instead of
designing a program to do what the programmer thinks should happen, the user is in control.
Much like programming code in VB that tells your program how to respond to events
such as mouse clicks occur in what VB calls event procedure or is used by an event procedure to
help the procedure carry out its job.
The third step is inevitable press of finding and fixing the errors. Not even god can help
you debug the semantic errors but VB surely helps you to debug errors by providing debugging

Address Book
tools like ‘Run to Curser’, ’Break Points’, ‘stepping in and stepping out’ and etc.. . The
integrated development environment allows debugging at run time.
After a project is completed, it may need to install it on the machines that will run the
applications. To do this VB provides the package and deployment wizards that creates the setup
programs. Then the setup program can run to install the application and all of the files it requires
on each of the client machines. Or the applications can be installed on the internet servers so the
client can access the information directly from the server.
1.3. Introduction to MS.Access database:

Microsoft Access is a database management system (DBMS) from Microsoft that
combines the relational Microsoft Jet Database Engine with a graphical user interface and
software-development tools. It is a member of the Microsoft Office suite of applications,
included in the Professional and higher editions or sold separately.
Microsoft Access stores data in its own format based on the Access Jet Database Engine.
It can also import or link directly to data stored in other applications and databases.
Software developers, data architects and power users can use Microsoft Access to
develop application software. Like other Microsoft Office applications, Access is supported
by Visual Basic for Applications (VBA), an object-based programming language that can
reference a variety of objects including DAO (Data Access Objects), ActiveX Data Objects, and
many other ActiveX components. Visual objects used in forms and reports expose their methods

Address Book
and properties in the VBA programming environment, and VBA code modules may declare and
call Windows operating system operations.
In addition to using its own database storage file, Microsoft Access also may be used as
the 'front-end' of a program while other products act as the 'back-end' tables, such as Microsoft
SQL Server and non-Microsoft products such as Oracle and Sybase. Multiple backend sources
can be used by a Microsoft Access Jet Database (ACCDB and MDB formats). Similarly, some
applications such as Visual Basic, ASP.NET, or Visual Studio .NET will use the Microsoft
Access database format for its tables and queries. Microsoft Access may also be part of a more
complex solution, where it may be integrated with other technologies such as Microsoft
Excel, Microsoft Outlook, Microsoft Word, Microsoft PowerPoint and ActiveX controls.
Access tables support a variety of standard field types, indices, and referential
integrity including cascading updates and deletes. Access also includes a query interface, forms
to display and enter data, and reports for printing. The underlying Jet database, which contains
these objects, is multi-user and handles record-locking.
Repetitive tasks can be automated through macros with point-and-click options. It is also
easy to place a database on a network and have multiple users share and update data without
overwriting each other's work. Data is locked at the record level which is significantly different
from Excel which locks the entire spreadsheet.
There are template databases within the program and for download from Microsoft's
website. These options are available upon starting Access and allow users to enhance a database

Address Book
with predefined tables, queries, forms, reports, and macros. Database templates
support VBA code but Microsoft's templates do not include VBA code.
A database scheme is defined by a set of definitions, which are expressed by Data
Definition Language (DDL). DDL statements are compiled into a set of tables, which are stored
in a special file called data dictionary, which contains the metadata.
Data Manipulation Language (DML) is a language which enables users to access or
manipulate such data. There are two types: Procedural DML’s, which require the user to specify
what the data is needed and how to get it. Non-Procedural DML which require the user to specify
what data is needed without specifying how to get it.

Address Book
Chapter 2
LITERATURE SURVEY
The software Address Book didn’t required much research or literature survey, because
the basic features are already present in every handset. but there is no any proper application
which is particularly build to keep the contacts securely and safely. The Gmail may be the best
security for all the contacts security but the chances of forgetting username or password is more.
Even if the device fails, there is no any alternatives to find it out rather than approaching a
technician, so we are aimed to develop an application which is capable of providing immense
security with the reusable database. Yes, the main intention of back end is to access the database
easily at the time of failures of software or at the time when the software is affected.
All the mobile contains their own Address Books, but not all the PC's contains the
address book, hence, there is no any advanced developed applications which can help the people
to withstand any types of the failures or bugs or something else. This leaded us for the
development of the software's in the windows environment.

Address Book
Chapter 3
SYSTEM ANALYSIS
3.1. Existing Systems:

The Existing systems of this project are the basic android of java applications, which can
also perform the similar functionality as our upcoming project. But, they don't have any facility
to withstand the system failures, they are just the project which can perform the addition display
and deletion of the contacts.
The Existing windows applications are available for the windows operating environment,
but this is very useless because of its complexity, they directly stored in core databases which
cause the loss of contacts at the time of system failures.
The windows applications for contact management are present but they are useless
because of heavy -unneccery coding and low performance even for the small applications. The
one of major drawbacks of the existing projects is: the contacts cannot be retrieved after
hardware or software failures and we are moved to develop an application which can give
performance, reliability and data recovery.

Address Book
3.2. Proposed System:

This is the very useful project because this can withstand all the error failures of the
computer. Even if the computer fails or the hard disk corrupts for some reason, only the extracted
database is enough for regenerating the database with few steps.
Our Address Book software is the software which are defined with the single module and
does contains only two user defined classes. The Address book is more efficient because of its
compact nature and compressed code. In this software, the care is taken not to loop itself more as
a result cause the performance degradation. This software is the best suited for the low level
applications because of its reduced coding.
3.2. Advantages of Proposed System:

 Simple, fast and secure.
 More Performance efficiency.
 Data reliability.
 Data recovery.
 Compressed code can cause more performance.
 simple and easy to sue.
 Enough graphical integration for user.
 Closed database connection.

Address Book
3.2. Feasibility Study:

Feasibility study is an assessment of the practicality of a proposed project or system,
here we can define feasibility study in three ways, they are:
 technical Feasibility.
 Economical Feasibility.
 Operational Feasibility.
- Technical Feasibility:
This assessment is based on an outline design of system requirements, to determine
whether the company has the technical expertise to handle completion of the project. When
writing a feasibility report, the following should be taken to consideration:
 A brief description of the business to assess more possible factors which could affect the
study
 The part of the business being examined
 The human and economic factor
 The possible solutions to the problem
In the part of technical feasibility, we has done analyzed the complete technical tasks to
be done. first, the technical architectural design has been done, such as the connection to
database, high level interface and much more.

Address Book
- Operational Feasibility:
Operational feasibility is the measure of how well a proposed system solves the
problems, and takes advantage of the opportunities identified during scope definition and how it
satisfies the requirements identified in the requirements analysis phase of system development.
The operational feasibility assessment focuses on the degree to which the proposed
development project fits in with the existing business environment and objectives with regard to
development schedule, delivery date, corporate culture and existing business processes.
To ensure success, desired operational outcomes must be imparted during design and
development. These include such design-dependent parameters as reliability, maintainability,
supportability, usability, reducibility, disposability, sustainability, affordability and others. These
parameters are required to be considered at the early stages of design if desired operational
behaviors are to be realized. A system design and development requires appropriate and timely
application of engineering and management efforts to meet the previously mentioned parameters.
A system may serve its intended purpose most effectively when its technical and
operating characteristics are engineered into the design. Therefore, operational feasibility is a
critical aspect of systems engineering that needs to be an integral part of the early design phases.
in this project, mainly the operational feasibility is done by the interface of database with
the applications, this is the main problem and challenge on which all the Business software
depends.

Address Book
Chapter 4
SYSTEM DEVELOPMENT STRATERGY
4.1. System Engineering:

As the information system requirements were predictable it was decided to follow the
classical System Development Life Cycle Method (Waterfall Model). It is one of the oldest and
most widely used paradigms for the software development.
This process demands a systematic, sequential approach to software development that begins at
the system level and process through the analysis, design, coding, testing and maintenance level.

Address Book
The step of the classical life cycle paradigm is very similar to the generic steps that are
applicable to all the software engineering paradigms. Modeled after the conventional engineering
cycle, the classic life-cycle approach encompasses the following activities.
 Requirements analysis and specification.

 Design.
 Implementation and unit testing.
 Verification.
 Operation and maintenance.
We have chosen this Waterfall Model because we have collected all the requirements
earlier and those requirements are fixed for the project of Library management and hence there
is no such necessity of changing or altering the requirements, secondly this is the one of the
simplest life cycle model of the Software Engineering.
In common practice, waterfall methodologies result in a project schedule with 20–40% of
the time invested for the first two phases, 30–40% of the time to coding, and the rest dedicated to
testing and implementation. The actual project organization needs to be highly structured. Most
medium and large projects will include a detailed set of procedures and controls, which regulate
every process on the project
A further argument for the waterfall model is that it places emphasis on documentation
(such as requirements documents and design documents) as well as source code. In less
thoroughly designed and documented methodologies, knowledge is lost if team members leave
before the project is completed, and it may be difficult for a project to recover from the loss. If a
fully working design document is present (as is the intent of Big Design Up Front and the

Address Book
waterfall model), new team members or even entirely new teams should be able to familiarise
themselves by reading the documents.
In response to the perceived problems with the "pure" waterfall model, many modified
waterfall models have been introduced. These models may address some or all of the criticisms
of the "pure" waterfall model.
These include the Rapid Development models that Steve McConnell calls "modified
waterfalls. Peter DeGrace's "sashimi model" (waterfall with overlapping phases), waterfall with
subprojects, and waterfall with risk reduction. Other software development model combinations
such as "incremental waterfall model" also exist.
4.2. System Development Environment:

The present project, the "Address Book" is the project is developed in the environement
of Visual Basic. This environment is provided by the Visual Basic but the platform is depended
on the .NET framework, the .NET is the abbrevation of .network enabled text.
The backend of this software which is called as ACCDB can be developed in the
environment of microsoft access software. this is the best database for the beginners. The ms
access database can be also work as the stand alone front end and back end, hence this is the best
application to define the back end. The ACCDB can be acced independently that’s why we can
recover it during the software or hardware failures. This will be much useful for the large
companies who has the necessary to access directly from the database and convery into hard
copy.

Address Book
The application can be run on the environment of Windows xp and above with the
minimum of 0.5 gb of ram and 2GB of hard disk memory. The recommended processor is
starting from windows atom, hence we can say that this is supported for any low grade machine
ranging from the windows vista, xp to windows 10.

Address Book
CHAPTER - 5
SYSTEM DESIGN
Systems design is the process of defining the architecture, modules, interfaces,
and data for a system to satisfy specified requirements. Systems design could be seen as the
application of systems theory to product development. There is some overlap with the disciplines
of systems analysis, systems architecture and systems engineering.
The design of the hardware is developed by using manual connections. The connections
are done by using Arduino as the heart of the Project. In the present project we need the two
types of designs, they are hardware design and software design. At present, the project design is
divided as two tyeps, they are:
 High level design.
 Low level design
5.1. High Level Design:
High-level design (HLD) explains the architecture that would be used for developing a
software product. The architecture diagram provides an overview of an entire system, identifying
the main components that would be developed for the product and their interfaces. The HLD
uses possibly nontechnical to mildly technical terms that should be understandable to the
administrators of the system. In present project we sue two types of architecture, they are
hardware and software architecture.

Address Book
The simple high level design algorithm is shown as below
5.2. Low Level Design:

Low-level design (LLD) is a component-level design process that follows a step-
by-step refinement process. This process can be used for designing data structures, required
software architecture, source code and ultimately, performance algorithms. Overall, the data
organization may be defined during requirement analysis and then refined during data design
work. Post-build, each component is specified in detail

Address Book
5.3. Flow Charts:
Fig: The Login form Flow chart

Address Book
Fig: The main form flowchart
5.4. Input Output Interface:

The input and output is just the contacts, and nothing else calculation part comes here,
only the part of security and provacy matters in this project. This project has to convert the
given input to access database format and when accessing it access as string. The application
itself converts while taking input or output but for some times we should declare and define these
parameters when necessary.

Address Book
The input is same as the output, hence no any logical calculations are done for the data
which are inputted to the contacts. This just converts the strings to input for the database and
when ever needed, it converts the database data into the string format then displays to the user.
5.5. Data table Design:

There are only two tables in the application which is running whoel project as shown
below:
1) Login Database table
COLUMN NAME TYPE

ID Int
UserName Varchar(50)
Password Varchar(50)
2) Contacts database Table.
COLUMN NAME TYPE

ID Int
FName Varchar(50)
LName Varchar(50)
Phone Numeric
Adderss Varchar(200)
Email Varchar(50)
Age Numeric(2)

Address Book
CHAPTER - 6
CODING
The coding is the major, most important and error prone part of the project development,
here most of the expectations go wrong, many of changes to be done and much more. The
Simple algorithm for the Software and Source codes are defined as shown below:
Pseudocode:
The below table consists the simple and brief pseudocode which can be understand by the
normal users:
The Login Form Pseudo Code
1) textbox1=username input
2) textbox2=password input
3) if (username!=database.Login.username or password!=database.login.password)
i) err.message("entered incorrect number")
b) else
i) message("you have successfully logged in")
ii) login.hide() and MainPage.show()
4) end if
The Main Form Pseudo Code
1. if button_cliked= add
2. if any text field is empty?

Address Book
3. err.message("Please fill all the text boxes")
4. else
5. database.table.Contact = add textbox.text
6. msg("Your data has been added successfully")
7. end if
8. end if
9. if button_clicked = Delete
10. if database.table.Contact(record)= textbox1.text
11. msg("the record is deleted")
12. delete(record)
13. else
14. err.msg("the record not found")
15. end if
16. end if
17. if button_clicked = Update
19. msg("the record is updated")
20. update(record)
21. else
23. end if
24. end if
25. if button_clicked = Search

Address Book
27. Datatable.show=searched record
28. else
30. end if
31. end if
32. if button_clicked = Show
33. DatabaseTable.GridView.show=true
34. if button_clicked = Exit
35. me.close()
The coding for the Login form is shown as below:
Public Class Login
Private Sub Login_Load(sender As Object, e As EventArgs) Handles MyBase.Load

Me.TbluserTableAdapter1.Fill(Me.DataDataSet1.tbluser)
End Sub
Private Sub Timer1_Tick(sender As Object, e As EventArgs) Handles Timer1.Tick

ProgressBar1.Increment(1)
If ProgressBar1.Value = 100 Then
Me.Hide()
Form2.Show()
Timer1.Stop()
End If
End Sub
_________________________________________________________________________________________
Private Sub Button2_Click(sender As Object, e As EventArgs) Handles Button2.Click

Dim user As String
Dim pass As String
user = TextBox1.Text
pass = TextBox2.Text
If TbluserTableAdapter1.ScalarQueryLogin(user, pass) Then
MsgBox("WelCam ! you are Successfully Logged In", MsgBoxStyle.Information,
user)
Timer1.Start()

Address Book
Else
MsgBox("Invalid Login Try Agin", MsgBoxStyle.Critical, "Login")
End If
End Sub
_________________________________________________________________________________________

End
End Sub
_________________________________________________________________________________________
Private Sub LinkLabel1_LinkClicked(sender As Object, e As

LinkLabelLinkClickedEventArgs) Handles LinkLabel1.LinkClicked
Me.Hide()
NewLog.Show()
End Sub
End Class
The coding for main form
Public Class Form2
Private Sub Form2_Load(sender As Object, e As EventArgs) Handles MyBase.Load

TextBox3.MaxLength = 2
'TODO: This line of code loads data into the 'DataDataSet.Table1' table. You can
move, or remove it, as needed.
Me.Table1TableAdapter.Fill(Me.DataDataSet.Table1)
Blanking()
End Sub
_________________________________________________________________________________________
Private Sub Button1_Click(sender As Object, e As EventArgs)
On Error GoTo ADDErr
If Button1.Text = "ADD" Then
Table1BindingSource.AddNew()
Blanking()
Button1.Text = "Save"
ElseIf Button1.Text = "Save" Then
Table1BindingSource.EndEdit()
Table1TableAdapter.Update(DataDataSet.Table1)
MessageBox.Show("Save Data")
Button1.Text = "ADD"
DataGridView1.Refresh()
End If
ADDErr:
Exit Sub
End Sub
_________________________________________________________________________________________

Address Book
On Error GoTo Saveerr

Dim Ask As MsgBoxResult
Ask = MsgBox("Are you Sur Update", MsgBoxStyle.YesNo)
If Ask = MsgBoxResult.Yes Then
MessageBox.Show("Update Data")
ElseIf Ask = MsgBoxResult.No Then
End If
Saveerr:
Exit Sub
End Sub
_________________________________________________________________________________________

Ask = MsgBox("Are you sure to Delete", MsgBoxStyle.YesNo)
Table1BindingSource.RemoveCurrent()
End If
End Sub
_________________________________________________________________________________________

Login.Close()
Me.Close()
End Sub
_________________________________________________________________________________________
Table1BindingSource.MovePrevious()
End Sub
_________________________________________________________________________________________
Table1BindingSource.MoveNext()
End Sub
_________________________________________________________________________________________
Blanking()
End Sub
_________________________________________________________________________________________
Me.Hide()
Me.Show()
End Sub
Private Sub TextBox7_TextChanged(sender As Object, e As EventArgs)
DataGridView1.DataSource = Me.DataDataSet.Table1.Select("FName LIKE '" &
TextBox7.Text & "'")
End Sub
Private Sub Blanking()
TextBox1.Text = ""
TextBox2.Text = ""
TextBox3.Text = ""
TextBox4.Text = ""
TextBox5.Text = ""

Address Book
TextBox6.Text = ""
ComboBox1.Text = ""
End Sub
_________________________________________________________________________________________
Private Sub Button7_Click_1(sender As Object, e As EventArgs) Handles Button7.Click
TabControl1.SelectedIndex = 1
End Sub
_________________________________________________________________________________________
End Sub
_________________________________________________________________________________________
Login.Show()
Me.Close()
End Sub
_________________________________________________________________________________________
End Sub
_________________________________________________________________________________________
MsgBox("Logged out successfully")
Login.Show()
Me.Close()
End Sub
_________________________________________________________________________________________
Login.Close()
Me.Close()
End Sub
_________________________________________________________________________________________
End Sub
_________________________________________________________________________________________
Login.Show()
Me.Close()
End Sub
_________________________________________________________________________________________
Login.Close()
Me.Close()
End Sub
_________________________________________________________________________________________
Private Sub DataGridView1_CellContentClick(sender As Object, e As
DataGridViewCellEventArgs) Handles DataGridView1.CellContentClick
End Sub
_________________________________________________________________________________________
On Error GoTo ADDErr
If TextBox1.Text = "" Or TextBox2.Text = "" Or TextBox3.Text = "" Or
TextBox4.Text = "" Or TextBox5.Text = "" Or TextBox6.Text = "" Then
MsgBox("Please fill all the field details in form")
Else

Address Book
If Button1.Text = "ADD" Then

Table1BindingSource.AddNew()
TextBox1.Text = ""
TextBox2.Text = ""
TextBox3.Text = ""
TextBox4.Text = ""
TextBox5.Text = ""
TextBox6.Text = ""
MsgBox("Data added successfully")
ElseIf Button1.Text = "Save" Then

MessageBox.Show("Save Data")
Button1.Text = "ADD"
DataGridView1.Refresh()
End If
End If
ADDErr:
Exit Sub
End Sub
_________________________________________________________________________________________
If TextBox1.Text = "" Or TextBox2.Text = "" Or TextBox3.Text = "" Or
TextBox4.Text = "" Or TextBox5.Text = "" Or TextBox6.Text = "" Then
MsgBox("Sorry few of the fields may be empty, Please fill them")
Else
On Error GoTo Saveerr
Ask = MsgBox("Are you sure to Update", MsgBoxStyle.YesNo)
MessageBox.Show("Update Data")
End If
End If
Saveerr:
Exit Sub
End Sub
_________________________________________________________________________________________

If Not TextBox1.Text = "" Then
Ask = MsgBox("Are you sure to Delete", MsgBoxStyle.YesNo)
Table1BindingSource.RemoveCurrent()
End If
Blanking()
Else
MsgBox("please give the first name of the contact")
End If
End Sub

Address Book
_________________________________________________________________________________________
Blanking()
MsgBox("Cleared")
End Sub
Private Sub TextBox1_Leave(sender As Object, e As EventArgs) Handles TextBox1.Leave

If IsNumeric(TextBox1.Text) Then
MsgBox("please enter proper first name")
TextBox1.Text = ""
End If
End Sub
_________________________________________________________________________________________
If IsNumeric(TextBox2.Text) Then
MsgBox("please enter proper last name")
TextBox2.Text = ""
End If
End Sub
_________________________________________________________________________________________
If Not IsNumeric(TextBox3.Text) Then
MsgBox("please enter proper age in numbers")
TextBox3.Text = ""
End If
End Sub
_________________________________________________________________________________________
If Not IsNumeric(TextBox4.Text) Then
MsgBox("please enter proper mobile number")
TextBox4.Text = ""
End If
End Sub
_________________________________________________________________________________________
Private Sub ComboBox1_SelectedIndexChanged(sender As Object, e As EventArgs) Handles
ComboBox1.SelectedIndexChanged
If IsNumeric(ComboBox1.Text) Then
MsgBox("please enter proper first name")
ComboBox1.Text = ""
End If
End Sub
End Class

Address Book
CHAPTER - 7
TESTING
Software testing is a process of executing a program or application with the intent of
finding the software bugs. Software testing is an investigation conducted to provide stakeholders
with information about the quality of the software product or service under test. Software testing
can also provide an objective, independent view of the software to allow the business to
appreciate and understand the risks of software implementation. Test techniques include the
process of executing a program or application with the intent of finding software bugs (errors or
other defects), and verifying that the software product is fit for use.
The software testing can also be done during execution, this process is called Dynamic
Testing. We ahve chosen dynamic software testing because this is very much effective and
powerful to determine the bugs or errors by the new Programmers. The Software testing can be
of three types, they are:
 Unit Testing
 Integration Testing
 System Testing

Address Book
7.1. Low level Testing:
Unit testing is a software testing method by which individual units of source code, sets of
one or more computer program modules together with associated control data, usage procedures,
and operating procedures, are tested to determine whether they are fit for use.
in this project, the low level testing is done by testing the individual component modules
of the software, since all of the components of the software has been completed, we are moving
to the Integration Testing.
7.2. Integration Testing:
The Integration testing (sometimes called integration and testing, abbreviated I&T) is
the phase in software testing in which individual software modules are combined and tested as a
group. It occurs after unit testing and before System testing. Integration testing takes as its
input modules that have been unit tested, groups them in larger aggregates, applies tests defined
in an integration test plan to those aggregates, and delivers as its output the integrated system
ready for system testing.
In the integration testing, the component modules are combined with a central stage and
then executed, all the errors while interface between the one to another module were understood
and removed, now the only one test is remaining, and that is the System test to find out the
performance and board compatibility.

Address Book
7.2. System Testing:
System testing of software or hardware is testing conducted on a complete, integrated
system to evaluate the system's compliance with its specified requirements. The system testing
includes the testing of Board compatibility, functionality, performance and much more.
In the system testing, we have given the first preference to the Board Diagnosis, this
board testing enabled us to solve the problem of inefficient power supply and caused the clean
and efficient power supply.
The system testing can be defined in many ways, but the simple definition is the
validation suceeds when the system model suceeds when the system function is in the manner is
reasonally expected by the user. Validation testing gives us the final assurance that the system
meets all the functional, personal and behavioral and performance requirements.
The project was tested with all its modules dn ensured that there were no errors, it has
been seen that the system is working perfectly, to the satisfaction of the user meeting all the
requirements of the user.
After performing the system testing, the next step is applied to the system is output
testing of the proposed system. Since no system could be useful, if it does not produce the
required output in the specific format. User acceptance of the system is the key factor for the
success of any system.

Address Book
CHAPTER - 8
SNAPSHOTS

Address Book

Address Book
CHAPTER - 9
CONCLUSION
The simple Address Book is a simple application which can keep contacts safe and
secure, this is the best application because this is the compact application with compressed code
which provides us the much performance and flexibility.The MS.ACCDB has made it still
efficient and powerful. The main feature of the software is if at any case any problem occurs in
software or operating system, we can retain our data by accessing the database directly.
This is the application with less weitage, hence it can be run on any platform of windows
ranging frm xp or lower application to windows 10 and windows server also. This contains one
of simplest user interface hence it is more userfriendly software than any other. The content of
this application can be both portable or non portable to enhance it's security.

Address Book
. CHAPTER - 10
BILIOGRAPHY
 www.codeproject.com
 wwww.youtube.com
 www.isntructables.com
 www.sourceforge.net

Documentations

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Documentations

Загружено:

Авторское право:

Доступные форматы

Address Book

1.1. Introduction To Project:

Statement of the Problem:

searching it spending the minutes together.

-Brief description of Project:

School of CSA, REVA University Page 1

1.2. Introduction to Visual Basic.NET:

also has third party controls for specialized task.

Fig: Visual Basic . NET

School of CSA, REVA University Page 2

fundamentally different from conventional programming.

help the procedure carry out its job.

School of CSA, REVA University Page 3

integrated development environment allows debugging at run time.

client can access the information directly from the server.

1.3. Introduction to MS.Access database:

software-development tools. It is a member of the Microsoft Office suite of applications,

included in the Professional and higher editions or sold separately.

School of CSA, REVA University Page 4

call Windows operating system operations.

these objects, is multi-user and handles record-locking.

from Excel which locks the entire spreadsheet.

School of CSA, REVA University Page 5

A database scheme is defined by a set of definitions, which are expressed by Data

in a special file called data dictionary, which contains the metadata.

Data Manipulation Language (DML) is a language which enables users to access or

what data is needed without specifying how to get it.

School of CSA, REVA University Page 6

technician, so we are aimed to develop an application which is capable of providing immense

development of the software's in the windows environment.

School of CSA, REVA University Page 7

3.1. Existing Systems:

and deletion of the contacts.

cause the loss of contacts at the time of system failures.

performance, reliability and data recovery.

School of CSA, REVA University Page 8

3.2. Proposed System:

database is enough for regenerating the database with few steps.

applications because of its reduced coding.

3.2. Advantages of Proposed System:

 More Performance efficiency.

 Compressed code can cause more performance.

 simple and easy to sue.

 Enough graphical integration for user.

 Closed database connection.

School of CSA, REVA University Page 9

3.2. Feasibility Study:

writing a feasibility report, the following should be taken to consideration:

database, high level interface and much more.

School of CSA, REVA University Page 10

development. These include such design-dependent parameters as reliability, maintainability,

supportability, usability, reducibility, disposability, sustainability, affordability and others. These

School of CSA, REVA University Page 11

SYSTEM DEVELOPMENT STRATERGY

4.1. System Engineering:

most widely used paradigms for the software development.

School of CSA, REVA University Page 12

cycle, the classic life-cycle approach encompasses the following activities.

 Requirements analysis and specification.

simplest life cycle model of the Software Engineering.

In common practice, waterfall methodologies result in a project schedule with 20–40% of

every process on the project

School of CSA, REVA University Page 13