3.

SYSTEM DESIGN & DEVELOPMENT

3.1 File Design

The file design is used to view and edit information in the database record by
record .A form displays only the information we want to see in the way we want to see it. Forms
use the familiar controls such as textboxes and checkboxes. This makes viewing and entering
data easy.

To build or modify the structure of files, we work in file design view. We can
add control to the files that are bound to fields in a table or query, includes textboxes, option
buttons, graphs and pictures.

3.2 Input Design

Input design is the process of converting user-originated inputs to a computer-

based format. Input design is one of the most expensive phases of the operation of computerized
system and is often the major problem of a system.

In the project, the input design is made in various web forms with various
methods. For example, in the user creation form, the empty username and password is not
allowed. The username if exists in the database, the input is considered to be invalid and is not
accepted. Likewise, during the login process, the username is a must and must be available in the
user list in the database. Then only login is allowed. Likewise, during the data transmission the
null values cannot be sent to the destination.

3.3 Output Design

Output design generally refers to the results and information that are generated by
the system for many end-users; output is the main reason for developing the system and the basis
on which they evaluate the usefulness of the application.
 In the project, the intermediate node details, the destination details, packet
delivery details, are the forms in which the output is available.

3.4 Database Design

The database design is a must for any application developed

especially more for the data store projects. Since the chatting method involves storing the
message in the table and produced to the sender and receiver, proper handling of the table is a
must. In the project, login table is designed to be unique in accepting the username and the
length of the username and password should be greater than zero.

SYSTEM REQUIREMENTS:

HARDWARE REQUIREMENTS:

• System : Pentium IV 2.4 GHz.

• Hard Disk : 40 GB.
• Floppy Drive : 1.44 Mb.
• Monitor : 15 VGA Colour.
• Mouse : Logitech.
• Ram : 512 Mb.

SOFTWARE REQUIREMENTS:

• Operating system : - Windows XP.

• Coding Language : ASP.NET
• Data Base : MS SQL SERVER 2005
 SYSTEM STUDY

2.1 Feasibility System

The feasibility of the project is analyzed in this phase and business proposal is put forth with
a very general plan for the project and some cost estimates. During system analysis the feasibility
study of the proposed system is to be carried out. This is to ensure that the proposed system is not a
burden to the company. For feasibility analysis, some understanding of the major requirements for
the system is essential.

Three key considerations involved in the feasibility analysis are

 ECONOMICAL FEASIBILITY
 TECHNICAL FEASIBILITY
 SOCIAL FEASIBILITY

ECONOMICAL FEASIBILITY:

This study is carried out to check the economic impact that the system will have on
the organization. The amount of fund that the company can pour into the research and development of
the system is limited. The expenditures must be justified. Thus the developed system as well within the
budget and this was achieved because most of the technologies used are freely available. Only the
customized products had to be purchased.
TECHNICAL FEASIBILITY:

This study is carried out to check the technical feasibility, that is, the technical
requirements of the system. Any system developed must not have a high demand on the available
technical resources. This will lead to high demands on the available technical resources. This will lead to
high demands being placed on the client. The developed system must have a modest requirement, as
only minimal or null changes are required for implementing this system.

SOCIAL FEASIBILITY:

The aspect of study is to check the level of acceptance of the system by the user. This
includes the process of training the user to use the system efficiently. The user must not feel threatened
by the system, instead must accept it as a necessity. The level of acceptance by the users solely depends
on the methods that are employed to educate the user about the system and to make him familiar with
it. His level of confidence must be raised so that he is also able to make some constructive criticism,
which is welcomed, as he is the final user of the system.

SYSTEM TESTING

The purpose of testing is to discover errors. Testing is the process of trying

to discover every conceivable fault or weakness in a work product. It provides a
way to check the functionality of components, sub assemblies, assemblies and/or a
finished product It is the process of exercising software with the intent of ensuring
that the
Software system meets its requirements and user expectations and does not fail in
an unacceptable manner. There are various types of test. Each test type addresses a
specific testing requirement.

TYPES OF TESTS

Unit testing
Unit testing involves the design of test cases that validate that the internal
program logic is functioning properly, and that program inputs produce valid
outputs. All decision branches and internal code flow should be validated. It is the
testing of individual software units of the application .it is done after the
completion of an individual unit before integration. This is a structural testing, that
relies on knowledge of its construction and is invasive. Unit tests perform basic
tests at component level and test a specific business process, application, and/or
system configuration. Unit tests ensure that each unique path of a business process
performs accurately to the documented specifications and contains clearly defined
inputs and expected results.

Integration testing

Integration tests are designed to test integrated software components to

determine if they actually run as one program. Testing is event driven and is more
concerned with the basic outcome of screens or fields. Integration tests
demonstrate that although the components were individually satisfaction, as shown
by successfully unit testing, the combination of components is correct and
consistent. Integration testing is specifically aimed at exposing the problems that
arise from the combination of components.

Functional test

Functional tests provide systematic demonstrations that functions tested are

available as specified by the business and technical requirements, system
documentation, and user manuals.

Functional testing is centered on the following items:

Valid Input : identified classes of valid input must be accepted.

Invalid Input : identified classes of invalid input must be rejected.

Functions : identified functions must be exercised.

Output : identified classes of application outputs must be exercised.

Systems/Procedures: interfacing systems or procedures must be invoked.

Organization and preparation of functional tests is focused on requirements, key

functions, or special test cases. In addition, systematic coverage pertaining to
identify Business process flows; data fields, predefined processes, and successive
processes must be considered for testing. Before functional testing is complete,
additional tests are identified and the effective value of current tests is determined.

System Test
System testing ensures that the entire integrated software system meets
requirements. It tests a configuration to ensure known and predictable results. An
example of system testing is the configuration oriented system integration test.
System testing is based on process descriptions and flows, emphasizing pre-driven
process links and integration points.

White Box Testing

White Box Testing is a testing in which in which the software tester has
knowledge of the inner workings, structure and language of the software, or at least
its purpose. It is purpose. It is used to test areas that cannot be reached from a black
box level.

Black Box Testing

Black Box Testing is testing the software without any knowledge of the inner
workings, structure or language of the module being tested. Black box tests, as
most other kinds of tests, must be written from a definitive source document, such
as specification or requirements document, such as specification or requirements
document. It is a testing in which the software under test is treated, as a black box
.you cannot “see” into it. The test provides inputs and responds to outputs without
considering how the software works.
6.1 Unit Testing:

Unit testing is usually conducted as part of a combined code and unit test
phase of the software lifecycle, although it is not uncommon for coding and unit
testing to be conducted as two distinct phases.

Test strategy and approach

Field testing will be performed manually and functional tests will be written
in detail.

Test objectives
 All field entries must work properly.
 Pages must be activated from the identified link.
 The entry screen, messages and responses must not be delayed.

Features to be tested
 Verify that the entries are of the correct format
 No duplicate entries should be allowed
 All links should take the user to the correct page.

6.2 Integration Testing

 Software integration testing is the incremental integration testing of two or
more integrated software components on a single platform to produce failures
caused by interface defects.

The task of the integration test is to check that components or software

applications, e.g. components in a software system or – one step up – software
applications at the company level – interact without error.

Test Results: All the test cases mentioned above passed successfully. No defects
encountered.

6.3 Acceptance Testing

User Acceptance Testing is a critical phase of any project and requires

significant participation by the end user. It also ensures that the system meets the
functional requirements.

Test Results: All the test cases mentioned above passed successfully. No defects
encountered.
Testing:

Introduction

The most important phase in system development life cycle is system testing. The
number and nature of errors in a newly designed system depends on the system specifications
and the time frame given for the design.

A newly designed system should have all the subsystems working together, but in reality
each subsystems work independently. During this phase, all the subsystems are gathered into
one pool and tested to determine whether it meets the user requirements.

Testing is done at two level -Testing of individual modules and testing the entire system.
During the system testing, the system is used experimentally to ensure that the software will run
according to the specifications and in the way the user expects. Each test case is designed with
the intent of finding errors in the way the system will process it.

Testing plays a very critical role in determining the reliability and efficiency of software
and hence is a very important stage in software development. Software testing is done at
different levels. They are the unit testing and system testing which comprises of integration
testing and acceptance testing.

TYPES OF TESTING

Unit Testing

This is the first level of testing. The different modules are tested against the
specifications produced during the integration. This is done to test the internal logic of each
module. Those resulting from the interaction between modules are initially avoided. The input
received and output generated is also tested to see whether it falls in the expected range of
values. Unit testing is performed from the bottom up, starting with the smallest and lowest
modules and proceeding one at a time.

The units in a system are the modules and routines that are assembled and integrated to
perform a specific function. The programs are tested for correctness of logic applied and
detection of errors in coding. Each of the modules was tested and errors are rectified. They were
then found to function properly.

Integration Testing

In integration testing, the tested modules are combined into sub-systems, which are then
tested. The goal of integration testing to check whether the modules can be integrated properly
emphasizing on the interfaces between modules. The different modules were linked together and
integration testing done on them.

Validation Testing

The objective of the validation test is to tell the user about the validity and reliability of
the system. It verifies whether the system operates as specified and the integrity of
important data is maintained. User motivation is very important for the successful performance
of the system.

All the modules were tested individually using both test data and live data. After each
module was ascertained that it was working correctly and it had been "integrated" with the
system. Again the system was tested as a whole. We hold the system tested with different types
of users. The System Design, Data Flow Diagrams, procedures etc. were well documented so
that the system can be easily maintained and upgraded by any computer professional at a later

System Testing

The integration of each module in the system is checked during this level of testing. The
objective of system testing is to check if the software meets its requirements. System testing is
done to uncover errors that were not found in earlier tests. This includes forced system failures
and validation of total system as the user in the operational environment implements it. Under
this testing, low volumes of transactions are generally based on live data. This volume is
increased until the maximum level for each transactions type is reached. The total system is also
tested for recovery after various major failures to ensure that no data are lost during the
breakdown.
Future Scope

The future scope of this project, Intranet mail system is very wide. There are many
additional features, which are planned to be incorporated during the future enhancements of this
project. Although all the main objectives according to SRS document have been achieved but still there
is for enhancement. This software can be easily upgraded in the future. And also include many more
features for existing system. It is connected to the network for easy retrieval of data and many more
location or many districts or cities in different states. All the information can be easily accessed by the
employee like their details, mails, departments. It can be modified and the other details can be easily
provided to customer. If anyone wants to combine all the departments of organization through internet
then he can easily do this with the help of this technology called .net Providing the SMS alerts facility to
users to remove the dependency on email account (web). As the project is flexible, so in future
document attached can be added in the project.