31-07-2012, 12:06 PM
TELEPHONE DIRECTORY MANAGEMENT
TELEPHONE DIRECTORY MANAGEMENT.pdf (Size: 483.95 KB / Downloads: 99)
INTRODUCTION
Telephone directory Application is used to manage and search the telephonic
details with regard to users name and address. The user can search all recorded
details of telephone user. This document is meant to delineate the features of
telephone directory application, so as to serve as guidelines to the developers on
first hand and the software validation document for the client on the other.
Project Scope:
The telephone directory application is developed for users who wish to access,
edit, search or modify the telephonic details of the user by knowing only single
thing out of first name, middle name or last name and address of the user about
whom the information is to be accessed.
The Application provides functionality on following platforms
- Windows XP
Benefits:
The benefit of this Telephone directory application is very normal, it can be used
anytime when user wants to add, remove, edit, search or modify telephone
directory details.
Scope:
The scope of this application cannot be considered too wide or too narrow the
factor defining its scope is its volume of data storage and as the way to use this
application is very easy and understandable therefore anyone can use it without
any problem.
Purpose/objective
The purpose of this telephone directory application is to add, modify, delete, search
telephonic details of the various users and to provide them anytime just by taking
any single detail key out of address, phone no., first middle or last name of the
telephone user.
Limitations:
The only limitation of this application is the feature of taking or say requirement of
any single detail key without which no further function can be done in the
application.
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. System testing falls within the scope of black
box testing, and as such, should require no knowledge of the inner
design of the code or logic.
As a rule, system testing takes, as its input, all of the "integrated"
software components that have successfully passed integration testing
and also the software system itself integrated with any applicable
hardware system(s). The purpose of integration testing is to detect any
inconsistencies between the software units that are integrated together
(called assemblages) or between any of the assemblages and the
hardware. System testing is a more limiting type of testing; it seeks to
detect defects both within the "inter-assemblages" and also within the
system as a whole.
Testing the whole system
System testing is performed on the entire system in the context of
Functional Requirement Specification(s) (FRS) and/or a System
Requirement Specification (SRS). System testing is an investigatory
testing phase, where the focus is to have almost a destructive
attitude[citation needed] and tests not only the design, but also the behavior and
even the believed expectations of the customer. It is also intended to test
up to and beyond the bounds defined in the software/hardware
requirements specification(s)
Types of system testing
The development process involves various types of testing. Each test
type addresses a specific testing requirement. The most common types
of testing involved in the development process are: