Sei sulla pagina 1di 60

1 INTRODUCTION

1.1 ORGANIZATION PROFILE

The TCPS was born in 2000 Nov 13. Now, within first year of its launch, more

than 19000 underprivileged people are being trained through our 388 centers which

are spread across South India and moving very fast and strong. The Director of TCPS

is Mr. J. James.

TCPS ALWAYS FIRST TCPS

TCPS is the First organization who Crossed 405 centers, also holds a record to

register more than 21,000 students again in it's every semester.

TCPS is the First organization who conduct public exam through out the

country on the same day with same question paper.

OUR MISSION:

GRASP THIS AMAZING OPPORTUNITY

Many companies have quickly grasped this huge opportunity of Training

People in the field of Computer (IT), but unfortunately most of them look at the elite

and concentrated only towards cream of the society with BIG PROFIT in their mind.

But here is the company with the difference, which want to serve the people

especially to the poor and the underprivileged to train and teach them computer at

their own language, at their own place, at their own style and at their own

affordability.

1
BENEFITS:

Every One Teach But Few Only Train

Leaders are not born but they are created at TCPS. Here in TCPS we not only

help the noble cause of training students in the field of computer but also make them

to be a good leader. We offer the following unbelievable benefits to our students.

CORRECT COUNSELING

A psychological orientated counseling is given before we select any student of

our existing Nine Diploma courses ranging from Basics to DOT Net courses.

FREE BOOKS

Every student has been provided excellent simple quality books for each

subject at Free of cost.

100% SCHOLARSHIP ON COURSE FEES

We don’t charge any thing as a course fee it is given totally free as a

Scholarship to the students.

REPUTED ORGANIZATION - BIGGEST NETWORK

Last but not the Least, our students has an opportunity to study under the BIG

BANNER, viz. one of the leading and fastest growing training Organization in the

South India with 388 study centers.

TOP RANKERS AWARD

Our council has constituted state level TOP RANKERS Award for the TOP

three students in each subject.

INTERNATIONAL SERVICE ORGANIZATION

We too get plenty of moral support for this selfless cause through International

Service Organization viz. ROTARY, LIONS, JCs etc to conduct Free Entrance

Examinations; Promotional activities; Scholarship etc.

2
For example, our Sep 8th Entrance exam in view of Literacy day was attended

by more than 80,000 people. This was possible through these Service Organization

supports only.

JOB SUPPORT

In association with “SYINERJY” HR Consultants group, we also help our

eligible students to get a good placement in reputed companies apart from

recommending them to the local Private / Public Ltd Companies.

Courses Offered:

COA: Certificate of Applications

DOA: Diploma in Office Automation

DDTP: Diploma in Desktop Publishing

DACP: Diploma in Advanced Computer Programming

DAJP: Diploma in Advanced Java Programming

HDCA: Higher Diploma in Computer Applications

DIT: Diploma in Information Technology

PGDCA: Post Graduate Dip. In Computer Applications

HDe-com: Higher Diploma in E-Commerce

PGDe-com: Post Graduate Diploma in E-Commerce

TCPS UNMATCHED MISSION STATEMENT

Our mission is to promote Computer Literacy to all the Citizens of this

country, especially to the underprivileged, by providing "REASONABLE,

AFFORDABLE and UNDERSTANDABLE Quality Computer Education" and help

them to become, a better-equipped good citizen and empower them to face this

competitive era of modernization, automation and computerization.

3
1.2 ORGANIZATION CHART

Figure 1: Organization Chart of TCPS

Director

etc
Branch1 Branch2

Branch Head Branch Head

Office Office

Clerk Students Lab Faculty Clerk Students Lab Faculty

4
1.3 ORGANIZATION OF THESIS

The thesis comprises eight chapters.

Chapter 1: Introduces Administrative Hierarchy of the system and about the

Organization.

Chapter 2: Looks at how the preliminary investigation is carried out.

What are the limitations of Existing System, Scope, and Objectives of the Proposed

System and how our Proposed System will help to overcome the drawbacks of

Existing System.

Chapter 3: Describes the Feasibility of the System i.e., Technical, Operational and

Economical Feasibility.

Chapter 4: Deals with System Requirement Analysis. Use cases capture the goal of

the users and responsibility of the system to its users, the flow of data from one

module to another are analyzed using interaction diagrams.

Chapter 5: Present the System Design. The different design techniques used in this

chapter.

Chapter 6: Presents System Testing strategies and techniques like Whitebox Testing,

Blackbox Testing and Unit testing.

Chapter 7: Presents the System Implementation i.e., Software requirements and

Hardware requirements and technologies used in developing the system.

Chapter 8: Represents the Conclusion.

Appendix: Contains the Screens.

5
2 PROBLEM DEFINITION

2.1 INTRODUCTION

Problem definition is the first step or state of any project for giving good

solution to the problem. It should be clearly stated. Problem definition is not an

imposed solution to the problem, but it is a clear understanding of the given problem.

The project entitled “TCPSINDIA.COM” is developed to extend the services

towards the TCPS Organization. This maintenance section includes the following

services:

 Branches Entry.

 Student Entry.

 Placement Entry.

 Course Entry.

 Waiting List Statement.

 Placement List Statement.

2.2 EXISTING SYSTEM

In Existing System, we maintain the Branch details, Course details, Student

details, Placement details and who are not getting a placement that students are to be

listed in separate statement as Waiting list. This statement describes how many

students are not getting the job. As it is a manual process, so while maintaining these

records we may do some mistakes and it is waste of valuable time.

6
Bottlenecks of the Existing System:

Time Delay:

In the Existing System, information related to all transactions is stored in

different registers. Since all the transactions are stored in different registers it takes lot

of time to prepare different reports.

Redundancy:

At present it is doing in manual method. Due to manual method it is liable of

the following problems. Preparing report requires for management is some what

difficult and time consuming. Maintaining huge amount of data in records is a

difficult process and result calculation is also a difficult and time consuming process.

Accuracy:

Since the same data is compiled at different sections, the possibility of

tabulating data wrongly increases. Also if data is more, validations become difficult.

These may result in loss of accuracy.

Storage Media:

In the existing system, data transactions are being stored in too large registers

it is very difficult to refer after some time.

Enquiry:

Enquiry for different level of information is much more difficult, finding or

producing records are difficult.

2.3 PROPOSED SYSTEM

Here the proposed system “TCPSINDIA.COM” is a window based software

application using we can easily manage the all transactional details regarding to the

Organization, with security by storing the data at a centralized location. The proposed

system will overcome all the limitations of the existing system.

7
The user attempts a home page of system that will display different types of menu

items.

Objectives of the Proposed System:

 The proposed system will provides the reliable data.

 If in case of data loss, we can restore the data easily and quickly without any

wastage of time.

8
3 FEASIBILITY STUDY

Preliminary investigation examines project feasibility; the likelihood the system

will be useful to the organization. The main objective of the feasibility, study is to test

the technical, operational and economical feasibility for adding new modules and

debugging old running system. All systems are feasible if they are given unlimited

resources and infinite time. There are aspects in the feasibility study portion of the

preliminary investigation:

• Technical Feasibility

• Operation Feasibility

• Economical Feasibility

3.1 TECHNICAL FEASIBILITY

The Technical issue usually raised during the feasibility stage of the

investigation includes the following:

 Does the necessary technology exist to do what is suggested?

 Do the proposed equipments have the technical capacity to hold the data

required to use the new system?

 Will the proposed systems provide adequate response to inquiries, regardless

of the number or location of users?

 Can the system be upgraded if developed?

 Are there technical guarantees of accuracy, reliability, ease of access and data

security?

9
3.2 OPERATIONAL FEASIBILITY

User-friendly

Customer will use the forms for their various transactions i.e. for adding new

routes, viewing the routes details. Also the Customer wants the reports to view the

various transactions based on the constraints. These forms and reports are generated

as user friendly to the Client.

Reliability

The packages will pick-up current transactions on line. Regarding the old

transactions, User will enter them in to the system.

Security

The web server and database server should be protected from hacking, virus etc..,

Portability

The application will be developed using standard open source software like

Java, tomcat web server, internet Explorer Browser etc these software will work both

on windows and Linux o/s. Hence portability problems neither will nor arise.

Availability

This software will be available always.

Maintainability

The system called the ewheelz uses the 2-tier architecture. The 1st tier is the

GUI, which is said to be front-end and the 2nd tier is the database, which uses MS-

Access or Oracle, which is the back-end.

The front-end can be run on different systems. The database will be running at

the server. Users access these forms by using the user-ids and the passwords.

10
Economic Feasibility

The computerized system takes care of the present existing systems data flow

and procedures completely and should generate all the reports of the manual system

besides a host of other management reports.

It should be built as a web based application with separate web server and

database server. This is required as the activities are spread through out the

organization customer Wants a centralized database. Further some of the linked

transactions take place different locations.

Open Source software like Weblogic, JAVA, Ms-Access and Windows is used

to minimize the cost for the customer.

11
4 REQUIREMENT SPECIFICATION

4.1 PERFORMANCE REQUIREMENTS

Performance is measured in terms of the output provided by the application.

Requirement specification plays an important part in the analysis of a system. Only

when the requirement specifications are properly given, it is possible to design a

system, which will fit into required environment. It rests largely with the users of the

existing system to give the requirement specification because they are the people who

finally use the system. This is because the requirements have to known during the

initial stages so that the system can be designed according to those requirements. It is

very difficult to change the system once it has been designed and on the other hand

designing a system, which does not cater to the requirements of the user, is of no use.

The requirements specification for any system can be broadly stated as given

below:

• The system should be able to interface with the existing system.

• The system should be accurate.

• The system should be better than existing system

• The existing system is completely dependent on the user to perform all the

duties.

4.2 SOFTWARE REQUIREMENTS:

Operating System : Windows

Technology : Servlets and JSP.

Web Server : Web Logic 8.1

Database : MS-Access or Oracle10g

12
Software’s : J2SDK1.6.0, Web logic 8.1

4.3 HARDWARE REQUIREMENTS:

Hardware Requirements:

Hardware : Pentium based system with a minimum of P4

RAM : 256MB (min)

Hard disk : 5GB

Additional Tools:

HTML Designing : Dream weaver Tool

Development Tool kit: Star UML

13
5 SYSTEM ANALYSIS

5.1 STUDY OF THE SYSTEM

To provide flexibility to the users, the interfaces have been developed that are

accessible through a browser. The GUI’s at the top level has been categorized as

1. Administrative user interface

2. The operational or generic user interface

The ‘administrative user interface’ concentrates on the consistent information

that is practically, part of the organizational activities and which needs proper

authentication for the data collection. These interfaces help the administrators

with all the transactional states like Data Insertion, Data Deletion and Data

Updating along with the extensive data search capabilities.

The ‘operational or generic user interface’ helps the end users of the system in

transactions through the existing data and required services. The operational user

interface also helps the ordinary users in managing their own information in a

customized manner as per the included flexibilities.

5.2 INPUT AND OUTPUT REPRESENTATION

Input design is a part of overall system design. The main objective during the

input design is as given below:

• To produce a cost-effective method of input.

• To achieve the highest possible level of accuracy.

• To ensure that the input is acceptable and understood by the user.

14
INPUT STAGES:

The main input stages can be listed as follows:

 Data Recording

 Data Transcription

 Data Conversion

 Data Verification

 Data Control

 Data Transmission

 Data Validation

INPUT TYPES:

It is necessary to determine the various types of inputs. Inputs can be

categorized as follows:

 External inputs, which are prime inputs for the system.

 Internal inputs, which are user communications with the system.

 Operational, which are computer department’s communications to the system.

 Interactive, which are inputs entered during a dialogue.

INPUT MEDIA:

At this stage choice has to be made about the input media. To conclude about

the input media consideration has to be given below

• Type of input

• Flexibility of format

• Speed

• Accuracy

• Verification methods

15
• Rejection rates

• Ease of correction

• Storage and handling requirements

• Security

• Easy to use

• Portability

Keeping in view the above description of the input types and input media, it can

be said that most of the inputs are of the form of internal and interactive. As input data

is to be the directly keyed in by the user, the keyboard can be considered to be the

most suitable input device.

OUTPUT DESIGN:

In general are:

• External Outputs whose destination is outside of the organization.

• Internal Outputs whose destination is with in the organization and they are the

User’s main interface with the computer. Outputs form computer systems are

required primarily to communicate the results of processing to users. They are

also used to provide a permanent copy of the results for later consultation. The

various types of outputs are

• Operational outputs whose use is purely with in the computer department.

• Interface Outputs, which involve the user in communicating directly with the

system.

OUTPUT DEFINITION:

The outputs should be defined in terms of the following points:

 Type of output

 Content of the output

16
 Format of the output

 Location of the output

 Frequency of the output

 Volume of the output

 Sequence of the output

It is not always desirable to print or display data as it is held on a computer. It

should be decided as which form of the output is the most suitable.

For Example

 Will decimal points need to be inserted.

 Should leading zeros be suppressed.

OUTPUT MEDIA

In the next stage it is to be decided that which medium is the most appropriate

for the output.

The main considerations when deciding about the output media are:

• The suitability for the device to the particular application.

• The need for a hard copy.

• The response time required.

• The location of the users.

• The software and hardware available.

Keeping in view the above description the project is to have outputs mainly

coming under the category of internal outputs. Desired according to the requirement

specification are:

The output where needed to be generated as a hard copy as well as queries to be

viewed on the screen. Keeping in view these outputs in the format for the output is

17
taken from the outputs, which are currently being obtained after manual processing.

The standard printer is to be used as output media for hard copies.

5.3 PROCESS MODEL USED WITH JUSTIFICATION

SDLC is nothing but software development life cycle. It is a standard which is

used by software industry to develop good software.

Stages in SDLC :

• Requirement Gathering

• Analysis

• Designing

• Coding

• Testing

• Maintenance

Requirements Gathering stage:

The requirements gathering process takes as its input the goals identified in the

high-level requirements section of the project plan. Each goal will be refined into a set

of one or more requirements. These requirements define the major functions of the

intended application, define operational data areas and reference data areas, and

define the initial data entities. Major functions include critical processes to be

managed, as well as mission critical inputs, outputs and reports. A user class hierarchy

is developed and associated with these major function, data areas, and data entities.

Each of these definitions is termed a requirement identifiers and at minimum contain

a requirement title and textual description.

18
High-Level Requirements

(project Plan) Requirements

Definition

Stage

Requirements Updated Project plan and Requirements

Document Schedule Traceability Matrix

These requirements are fully described in the primary deliverables for this

stage. The Requirements Document and the Requirements Traceability Matrix

(RTM).The requirements document contains complete descriptions of each

requirement, including diagrams and references to external documents as necessary.

Note that detailed listings of database tables and fields are not included in the

requirements document.

The title of each requirement is also placed into the first version of the RTM,

along with the title of each goal from the project plan. The purpose of the RTM is to

show that the product components developed during each stage of the software

development lifecycle are formally connected to the components developed in prior

stages.

In the requirements stage the RTM Consists of a list of high-level

requirements, or goals, by title with a listing of associated requirements for each goal,

listed by requirement title. In this hierarchical listing, the RTM shows that each

requirement developed during this stage is formally linked to a specific product goal,

hence the term requirements traceability.

19
The outputs of the requirements definition stage include the requirements

document, the RTM, and an updated project plan.

• Feasibility study is all about identification of problems in a project.

• No of staff required to handle a projects represented as team formation, In this

case only modules are individual tasks will be assigned to employees who are

working for that project.

• Project specifications are all about representing of various possible inputs

submitting to the server and corresponding outputs along with reports

maintained by administrator.

Analysis stage:

The planning stage establishes a birds eye view of the intended software

product, and uses this to establish the basic project structure, evaluate feasibility and

risks associated with the project, and describe appropriate management and technical

approaches.

Application Lifecycle

Goals Model

Planning

Stage

Software
Software quality Project Plan and
Configuration
Assurance Plan Schedule
Management Plan

The most critical section of the project plan is a listing of high-level product

requirements, also referred to as goals. All of the software product requirements to be

20
developed during the requirements definition stage flow from one or more of these

goals. The minimum information for each goal consists of a title and textual

description, although additional information and references to external documents

may be included. The outputs of the project planning stage are the configuration

management plan, the quality assurance plan, and the project plan and schedule, with

a detailed listing of scheduled activities for the upcoming requirements stage, and

high level estimates of effort for the out stages.

Designing stages:

The design stage takes as its initial input the requirements identified in the

approved requirements document. For each requirement, a set of one or more design

elements will be produced as a result of interviews, workshop, and prototype efforts.

Design elements describe the desired software features in detail, and generally include

functional hierarchy diagrams, screen layout diagrams, tables of business rules,

business process diagrams, with a full data dictionary. These design elements are

intended to describe the software in sufficient detail that skilled programmers may

develop the software with minimal additional input.

Requirements
Design stage
Document

Design Updated project Updated requirements

Document plan & schedule Traceability Matrix

21
When the design document is finalized and accepted, the RTM is updated to show

that the each design element is formally associated with a specific requirement. The

outputs of the design stage are the design document, updated RTM, and updated

project plan.

Development stage:

The development stage takes as its primary input the design elements

described in the approved design document. For each design elements, a set of one or

more software artifacts will be produced. Software artifacts include but are not limited

to menus, dialogues, and data reporting formats, and specialized procedures and

functions. Appropriate test cases will be developed for each set of functionally related

software artifacts, and an online help system will be developed to guide users in their

interactions with the software.

Design Document Development

Stage

Online Help Updated project plan


Software
& schedule

Updated Requirements
Implementation Map Test Plan
Traceability Matrix

The RTM will be updated to show that each developed artifact is linked to a

specific design element, and that each developed artifact has one or more

corresponding test case items. At this point, the RTM is in its final configuration. The

outputs of the development stage include a fully functional set of software that

22
satisfies the requirements and design elements previously documented, an online help

system that describes the operation of the software, an implementation map that

identifies the primary code entry points for all major system functions, a test plan that

describes the test cases to be used to validate the correctness and completeness of the

software, an updated RTM, and an updated project plan.

Integration & Test Stage:

During the integration and test stage, the software artifacts, online help, and

test data are migrated from the development environment to a separate test

environment. At this point, all test cases are run to verify the correctness and

completeness of the software. Successful execution of the rest suit confirms a robust

and complete migration capability. During this stage the reference data is finalized for

production use and production users are identified and linked to their appropriate

roles. The final reference data and production user list are compiled into the

production initiation plan.

23
Implementation
Software Online Help Test plan
Map

Integration

& Test

Stage

Integration Implementation
Online Help
software Map

Production Updated project


Acceptance
Initiation Plan & schedule

The outputs of the integration and test stage include an integrated set of

software, an online help system, an implementation map, a production initiation plan

that describes reference data and production users, an acceptance plan which contains

the final suite of test cases, and an updated project plan.

Installation & Acceptance Test:

During the installation and acceptance stage, the software artifacts, online

help, and initial production data are loaded onto the production server. At this point,

all test cases are run to verify the correctness and completeness of the software.

Successful execution of the test suite is a prerequisite to acceptance of the software by

the customer.

24
After customer personnel have verified that the initial production data load is

correct and the test suit has been executed with satisfaction results, the customer

formally accepts the delivery of the software.

Production Integrated
Acceptance Plan Online Help
initiation Software

Implementation

Map

Installation

&Acceptance

Stage

Production Completed Customer

Software Acceptance Test Acceptance

Archived Project
Archived Software

Artifacts Plan & Schedule

The primary outputs of the installation and acceptance stage include a

production application, a completed acceptance test suit, and a memorandum of

customer acceptance of the software. Finally, the PDR enters the last of the actual

labor data into the project schedule and licks the project as a permanent project

record. At this point the PDR “locks “the project by archiving all software items, the

implementation map, the source code, and the documentation for future reference.

25
Maintenance:

Outer rectangle represents maintenance of a project; Maintenance team will

start with requirement study, on that particular assigned category. For this life cycle

there is no end, it will be continued so on like an umbrella.

5.4 SYSTEM ARCHITECTURE

Architecture Flow:

Below architecture diagram represents mainly flow of requests from users to

database through servers. In this scenario overall system is designed in three tires

separately using three layers called presentation layer, business logic layer and data

link layer. This project was developed using 3-tire architecture.

SERVER

DATABASE

Figure 2: System Architecture

26
URL Pattern:

Figure 3: URL Pattern

URL Pattern represents how the requests are flowing through one layer to

another layer and how the responses are getting by other layers to presentation layer

through server in architecture diagram.

27
5.5 INTRODUCTION

System analysis is an important activity that takes place when we are building a

new system or changing existing one. Analysis helps to understand the existing

system and the requirements necessary for building the new system. If there is no

existing system then analysis defines only the requirements. One of the most

important factors in system enables designer to identify and correct problems. Based

on the drawbacks of the existing system the system is being planned. So the total

definition of the given problem has to be analyzed.

28
Unified Modeling Language:

Use case gives an overall system behavior and will give the analyst and

designer how to proceed further. The following are the notations used in development

of use cases has been referred from the book [1].

Dashed direct line Represents dependency.


Actor Match stick diagram Represents an external

entity, actors that interact

with the system.


An ellipse Contains the process that

the entities initiates or

interacts.

A rectangle Contains the grouped

process that the external

entity interacts.

5.6 ACTORS LIST

An Actor can input or receive information to and from the system. The actors

found for this project are:

 Beachhead

 Clerk

5.7 ACTIVITY DIAGRAM

An activity diagram is a variation or special case of a state machine in which the

states are activities representing the performance of operations and transactions are

triggered by the completion of the operation.

29
Figure 4 : Activity Diagram for TCPS

30
5.8 USE CASE DIAGRAM

Figure 5: Use Case Diagram for TCPS

5.9 INTERACTION DIAGRAM

Sequence Diagrams:

Sequence Diagram lies with in the behavioral view of a system and renders the

specification of behavior. These diagrams describe the behavior provided by a system

to interactions. These diagrams contain classes that exchange messages with in an

interaction arranged in a time sequence.

31
Figure 6: Sequence Diagram for BranchEntry

Figure 7: Sequence Diagram for Course Entry

32
Figure 8: Sequence Diagram for BranchEnquiry

33
34
Figure 9: Sequence Diagram for Placements

35
Collaboration diagrams:

Figure 10: Collaboration Diagram for BranchEntry

Figure 11: Collaboration Diagram for Courses

36
Figure 12: Collaboration Diagram for Branch Enquiry

Figure 13: Collaboration Diagram for Placement

37
5.10 STATIC UML CLASS DIAGRAM:

Classes, relationships, attributes, methods

Figure 14: Association Diagram for Students, Courses, Branch and Placements

38
Figure 15: Association diagram for Students, Branch and Placements

Figure 16: Static UML Diagram for TCPS

39
6 SYSTEM DESIGN

6.1 COMPLETE UML CLASS DIAGRAM FOR TCPS

Figure 17: Complete UML Class Diagram for TCPS

40
6.2 DATABASE DESIGN

Table Name: BRANCH

Table 1: To store Branch Details


FIELD NAME DESCRIPTION DATA TYPE CONSTRAINT
City City name Varchar2(10) NOT NULL
Address Complete Address Varchar2(30)

of a Branch
ContactNo Branch Contact no Varchar2(12)
HeadName Branch Head name Varchar2(20)

Table Name : COURSES

FIELD NAME DESCRIPTION DATA TYPE CONSTRAINT


Cno Course Number Number(5) NOT NULL
Cname Course Name Varchar2(10)
Fee Course Fee Number(10,2)
Table 2: To store Course Details

41
Table Name : PLACEMENTS

FIELD NAME DESCRIPTION DATA TYPE CONSTRAINT


Sno Student Number Number(10) NOT NULL
Sname Student Name Varchar2(20)
ContactNo Contact Number Varchar2(12)
Cname Company Name Varchar2(10)
Marks Marks Percentage Number(3)
Table 3: To store Placements Details

Table Name : STUDENTS

FIELD NAME DESCRIPTION DATA TYPE CONSTRAINT


Sno Student Number Number(10) NOT NULL
Sname Student Name Varchar2(20)
ContactNo Contact Number Varchar2(12)
Email Email Id Varchar2(30)
Address Student address Varchar2(30)
Course Course Name Varchar2(10)
Fee Course Fee Number(10,2)
Table 4: To Store Student Details

42
Table Name : WAITING

FIELD NAME DESCRIPTION DATA TYPE CONSTRAINT


Sno Student Number Number(10) NOT NULL
Sname Student Name Varchar2(20)
ContactNo Contact Number Varchar2(12)
Email Email Id Varchar2(30)
Address Student address Varchar2(30)
Table 5: To Store Waiting list of Student Details

Table Name : LOGIN

FIELD NAME DESCRIPTION DATA TYPE CONSTRAINT


Uname UserName Varchar2(20) NOT NULL
Psw Password Varchar2(20)
Table 6: To Store Login Details

43
Figure 18: UML Class diagram for TCPS showing the relationship of the view classes, business

classes and access classes

44
7 SYSTEM TESTING

7.1 INTRODUCTION

Software testing is a critical element of software quality assurance and

represents the ultimate review of specification, design and coding. Software testing

fundamentals define the overriding objectives for software testing.

Testing objectives

Testing is a process of execution a program with the intend to finding an error,

a good test case is one that has high probability of finding a yet undiscovered error,

tests are designed systematically so that they uncover different classes of errors and

do so with a minimum amount of time and effort.

Testing Principles

Before applying methods to design effective test cases, a software engineer

must understand the basic principles that guide software testing, all tests should be

traceable to customer requirements, and tests should be planned long before testing

begins.

Test case design

Any engineering product tested in one of the following two ways. Knowing

the specified function that products have been designed to perform, testing is

conducted for each function fully and the same time searching for errors in each

function.

Knowing the internal working of the product, tests are conducted to ensure

that an internal operation performs according to specification.

The testing is carried as follows

45
7.2 WHITEBOX TESTING

Knowing the internal working of the product, tests can be conducted that the

internal operation performs according the specification and all internal components

have been adequately exercised.

Using white box testing methods, the software engineer can derive test cases that

Guarantee that all independent paths with In a module has been exercised at least once

BASIS PATH TESTING.

 Exercise all logical decisions on their true false sides CONDITION

TESTING.

 Exercise internal data structures to assure validity DATA FLOW TESTING

 Executive all loops at their boundaries and with in their operation bounds

LOOP TESTING

7.3 BLACKBOX TESTING

Knowing the specified function that a product has been designed to perform,

test can be conducted that demonstrates each function is fully operational, at the same

time searching for errors in each function.

Black box attempts to find errors in the following categories

 Incorrect or missing functions.

 Interface errors.

 Errors in data structures or external database access.

 Performance errors.

 Initialization and termination errors.

46
8 SYSTEM IMPLEMENTATION

8.1 INTRODUCTION

Implementation literally means to put into effect or to carryout. The system

implementation phase if the software deals with the translation of the design

specifications into the source code. The ultimate goal of the implementation is to

write the source code and the internal documentation so that it can be verified easily.

The code and documentation should be written in a manner that eases debugging,

testing and modification. System flow charts, sample run on packages, sample output

etc., is part of the implementation.

An effort was made to satisfy the following goals in order

 Clarity and simplicity of the code.

 Minimization of hard coding.

 Minimization of the amount of memory used.

 Through phased implementation we can use our proposed system

47
9 CONCLUSION

The “TCPSINDIA.COM” has been successfully completed. The goal of the

system is achieved and problems are solved. The package is developed in a manner

that it is user friendly and required help is provided at different levels.

The project can be easily used to generate different type of reports through which

the management can take correct decisions, so indirectly this project may involve in

the decision making process.

This project will reduce the time which automatically increases the company’s

work standard as well as the economical state of company. The system never

decreases the manpower but helps the development of available manpower and

optimizes the manpower by which company’s standard and capabilities can be scaled

to higher dimensions.

Future Scope of the Project:

The project has met the standards required to work. If the business logic

remains same the project can be ported to any Examination Maintenance System

application with minor changes in the working procedure of the project.

48
BIBLIOGRAPHY

Books and Manuals

1. System Analysis and Designing

Author: Ali Baharami

Publisher: Tata McGraw Hill

2. MSDN of microsoft

49
50
51
52
53
54
55
56
57
58
59
60