Professional Documents
Culture Documents
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 is the First organization who Crossed 405 centers, also holds a record to
TCPS is the First organization who conduct public exam through out the
OUR MISSION:
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:
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
CORRECT COUNSELING
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
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
Our council has constituted state level TOP RANKERS Award for the TOP
We too get plenty of moral support for this selfless cause through International
Service Organization viz. ROTARY, LIONS, JCs etc to conduct Free Entrance
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
Courses Offered:
them to become, a better-equipped good citizen and empower them to face this
3
1.2 ORGANIZATION CHART
Director
etc
Branch1 Branch2
Office Office
4
1.3 ORGANIZATION OF THESIS
Organization.
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
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,
5
2 PROBLEM DEFINITION
2.1 INTRODUCTION
Problem definition is the first step or state of any project for giving good
imposed solution to the problem, but it is a clear understanding of the given problem.
towards the TCPS Organization. This maintenance section includes the following
services:
Branches Entry.
Student Entry.
Placement Entry.
Course Entry.
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
6
Bottlenecks of the Existing System:
Time Delay:
different registers. Since all the transactions are stored in different registers it takes lot
Redundancy:
the following problems. Preparing report requires for management is some what
difficult process and result calculation is also a difficult and time consuming process.
Accuracy:
tabulating data wrongly increases. Also if data is more, validations become difficult.
Storage Media:
In the existing system, data transactions are being stored in too large registers
Enquiry:
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
7
The user attempts a home page of system that will display different types of menu
items.
If in case of data loss, we can restore the data easily and quickly without any
wastage of time.
8
3 FEASIBILITY STUDY
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
The Technical issue usually raised during the feasibility stage of the
Do the proposed equipments have the technical capacity to hold the data
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
Reliability
The packages will pick-up current transactions on line. Regarding the old
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
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-
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
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
Open Source software like Weblogic, JAVA, Ms-Access and Windows is used
11
4 REQUIREMENT SPECIFICATION
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 existing system is completely dependent on the user to perform all the
duties.
12
Software’s : J2SDK1.6.0, Web logic 8.1
Hardware Requirements:
Additional Tools:
13
5 SYSTEM ANALYSIS
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
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
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
Input design is a part of overall system design. The main objective during the
14
INPUT STAGES:
Data Recording
Data Transcription
Data Conversion
Data Verification
Data Control
Data Transmission
Data Validation
INPUT TYPES:
categorized as follows:
INPUT MEDIA:
At this stage choice has to be made about the input media. To conclude about
• Type of input
• Flexibility of format
• Speed
• Accuracy
• Verification methods
15
• Rejection rates
• Ease of correction
• 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
OUTPUT DESIGN:
In general are:
• 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
also used to provide a permanent copy of the results for later consultation. The
• Interface Outputs, which involve the user in communicating directly with the
system.
OUTPUT DEFINITION:
Type of output
16
Format of the output
For Example
OUTPUT MEDIA
In the next stage it is to be decided that which medium is the most appropriate
The main considerations when deciding about the output media are:
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:
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.
Stages in SDLC :
• Requirement Gathering
• Analysis
• Designing
• Coding
• Testing
• Maintenance
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.
18
High-Level Requirements
Definition
Stage
These requirements are fully described in the primary deliverables for this
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
stages.
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,
19
The outputs of the requirements definition stage include the requirements
case only modules are individual tasks will be assigned to employees who are
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
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
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
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
Design elements describe the desired software features in detail, and generally include
business process diagrams, with a full data dictionary. These design elements are
intended to describe the software in sufficient detail that skilled programmers may
Requirements
Design stage
Document
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
Stage
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
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
23
Implementation
Software Online Help Test plan
Map
Integration
& Test
Stage
Integration Implementation
Online Help
software Map
The outputs of the integration and test stage include an integrated set of
that describes reference data and production users, an acceptance plan which contains
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.
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
Production Integrated
Acceptance Plan Online Help
initiation Software
Implementation
Map
Installation
&Acceptance
Stage
Archived Project
Archived Software
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:
start with requirement study, on that particular assigned category. For this life cycle
Architecture Flow:
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
SERVER
DATABASE
26
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
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
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
interacts.
entity interacts.
An Actor can input or receive information to and from the system. The actors
Beachhead
Clerk
states are activities representing the performance of operations and transactions are
29
Figure 4 : Activity Diagram for TCPS
30
5.8 USE CASE DIAGRAM
Sequence Diagrams:
Sequence Diagram lies with in the behavioral view of a system and renders the
31
Figure 6: Sequence Diagram for BranchEntry
32
Figure 8: Sequence Diagram for BranchEnquiry
33
34
Figure 9: Sequence Diagram for Placements
35
Collaboration diagrams:
36
Figure 12: Collaboration Diagram for Branch Enquiry
37
5.10 STATIC UML CLASS DIAGRAM:
Figure 14: Association Diagram for Students, Courses, Branch and Placements
38
Figure 15: Association diagram for Students, Branch and Placements
39
6 SYSTEM DESIGN
40
6.2 DATABASE DESIGN
of a Branch
ContactNo Branch Contact no Varchar2(12)
HeadName Branch Head name Varchar2(20)
41
Table Name : PLACEMENTS
42
Table Name : WAITING
43
Figure 18: UML Class diagram for TCPS showing the relationship of the view classes, business
44
7 SYSTEM TESTING
7.1 INTRODUCTION
represents the ultimate review of specification, design and coding. Software testing
Testing objectives
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
Testing Principles
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.
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
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
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
TESTING.
Executive all loops at their boundaries and with in their operation bounds
LOOP 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
Interface errors.
Performance errors.
46
8 SYSTEM IMPLEMENTATION
8.1 INTRODUCTION
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
47
9 CONCLUSION
system is achieved and problems are solved. The package is developed in a manner
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
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.
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
48
BIBLIOGRAPHY
2. MSDN of microsoft
49
50
51
52
53
54
55
56
57
58
59
60