The document describes a seminar report submitted by Saloni Bhargava and Sonal Bohra for their Bachelor of Engineering degree in fulfillment of their industrial defined project titled "Edu-Junction", which is a web-based application for practicing entrance exams. It includes certificates from their internal and external guides confirming the work is satisfactory. It also acknowledges the support received and provides an abstract describing the purpose and features of the Edu-Junction system.

1. EDU-JUNCTION
[Where Preparation And Hardwork Meet Success]
A SEMINAR REPORT
Submitted by
Saloni Bhargava (080240116002)
Sonal Bohra (080240116004)
In fulfillment for the award of the degree
Of
BACHELOR OF ENGINEERING
In
Information Technology
Hasmukh Goswami College of Engineering, Ahmedabad
Gujarat Technological University, Ahmedabad
December, 2011

2. CERTIFICATE
This is to certify that this work of Industrial Defined Project entitled “Edu-Junction” represents
the bonafide work of Saloni Bhargava, 080240116002 And Sonal Bohra,080240116004 for the
partial fulfillment of the degree of Bachelor of Engineering in Information Technology at the
Department of Information Technology, Hasmukh Goswami College Of Engineering, Vahelal,
Gujarat, during the academic year 20011-12 and her work is satisfactory.
Internal Guide, External Guide,
Mr. Manthan Khopkar Mr. Nirav Kansundra
lecturer
Information Technology Department
Indr Jeet Rajput,
Head of Department,
Information Technology Department.

3. CERTIFICATE
This is to certify that this work of Industrial Defined Project entitled “Edu-Junction” represents
the bonafide work of Sonal Bohra, 080240116004 for the partial fulfillment of the degree of
Bachelor of Engineering in Information Technology at the Department of Information
Technology, Hasmukh Goswami College Of Engineering, Vahelal, Gujarat, during the academic
year 20011-12 and her work is satisfactory.
Internal Guide, External Guide,
Mr. Manthan Khopkar Mr. Nirav Kansundra
lecturer
Information Technology Department
Indr Jeet Rajput,
Head of Department,
Information Technology Department.

4. ACKNOWLEDGEMENT
Though only our name appears on the cover of this Report, a great many people
have contributed to its production. We owe our gratitude to all those people who have
made this project analysis possible and because of whom our project making experience
has been one that I will cherish forever.
We are extremely grateful and remain indebted to our guide honorable Mr.
Manthan Khopkar for being a source of inspiration and for his constant support in the
Understanding and Analysis of the project. We are thankful to him for his constant
constructive criticism and invaluable suggestions, which benefits us a lot while
developing the project report on “Edu-Junction”. He has been a constant source of
inspiration and motivation for hard work. He has been very co-operative throughout this
project work. Through this column, it would be our utmost pleasure to express our warm
thanks to him for his encouragement, co-operation and consent without which we
mightn’t be able to accomplish this report.
We also express our gratitude to Mr. Indr Jeet Rajput (H.O.D., I.T. Department)
for providing us the infrastructure to carry out the project and to all staff members who
were directly and indirectly instrument in enabling us to stay committed for the project.
We are also thankful to the system staffs who maintain all the machines in our lab so
efficiently that we never have to worry about losing files, creating backups or installing
software.
Our grateful thanks go to our Department of INFORMATION TECHNOLOGY
which provides us an opportunity to sharpen our skills to develop a Project report in this
System analyzing by offering us such subjects in our final year of Graduation.

5. ABSTRACT
In recent times, technology has spurred a massive growth in Web
Technology. Now most of businesses are running in online mode, so why not
Education field? That is going to become true with Edu-Junction Project,
which is a means for people to practice online for various types of Entrances
Exams, like GATE, CAT, GCET, which are necessary to get admission in
Master Degree. Where exam papers are available to practice on it. Where
user can practice on specific categories of problems that are being asked in
exam, according to their strength and weakness. It includes result analysis
module, which gives idea to user about his/her strength and weakness in
particular types of problems related to exams. And a part of system provides
basic information and instruction about exams that makes user aware about
for what purpose the exam is, marking criteria and syllabus of exams.
User must register to access these facilities, where user is facilitated
to register according to resources s/he is willing to access. And some of
Demo tests available for free access. User will be updated with the new
exam papers and News Updates section. By means of Help & support, user
can make query to administration for any type of problems and feedbacks.

6. LIST OF FIGURES
Figure Figure Description Page No.
No
2(a) Project mode(WebE) 7
4(a) Feasibility Study Organization 17
5(a) Use Case Diagram 23
5(b) Class Diagram 26
5(c) System Activity Diagram 28
5(d) Sequence diagram of user registration 34
5(e) Sequence diagram for User Test 34
5(f) Admin 35
5(g) Context Diagram (Level 0) 37
5(h) Data Flow Diagram 38
5(i) Flow chart 41
5(j) State Transition For login+Registration 43
5(k) State Transition For Test Module 43
5(l) State Transition For Help and Support 44
5(m) State Transition For Admin 44

7. LIST OF TABLES
Table No Table Description Page No
Table 2.1 Risk Analysis 9
Table 2.2 Risk Planning 9
Table 2.3 Schedule Representation 10
Table 2.4 Gantt Chart 11
Table 3.1 Software Requirement 15
Table 3.2 Hardware Requirement 15
Table 5.1 Newsupdate 29
Table 5.2 Registration 30
Table 5.3 Confirmation 30
Table 5.4 Category 31
Table 5.5 Test 31
Table 5.6 Question 32
Table 5.7 Result 32

8. List of Symbols
SYMBOLS
1. Notation for Use Case:-
UseCase1
Usecase
Actor
Actor1
-End1 -End2
* * Association

9. 2. Notation for Class Diagram
Class Name
Attribute
Operation
Class
Aggregation
Z
1 and * Multiplicity

10. 3. Notation for Activity Diagram/State Transition Diagram
Intial State
Final State
Transition Fork/Transition Join
State1
State
Control Flow

11. 4. Notation for Sequence Diagram
Object1
Object Lifeline
Activation
Message1 Message/Function Call

12. 5. Notation for Data Flow Diagram and Context Diagram
Data Process
Data Store
Entity
Loop
Message1 Connector

13. 6. Notation for Flow Diagram
Process
Decision
Manual Input
Message1 Connector

14. TABLES OF CONTENT
Acknowledge ment I
Abstract II
List of Figures III
List of Tables IV
List of Symbol V
Table of Contents XI
Chapter : 1 Introduction 1
1.1 Project Profile 2
1.2 Scope Of System 2
1.3 Technological Review 2
1.4 Organizational Profile 4
Chapter : 2 Project Management 7
2.1 Project Model 8
2.2 Risk Management 9
2.3 Schedule Representation 11
Chapter : 3 System analysis 13
3.1 Problem Definition 14
3.2 Existing System Study 14
3.3 Problem & Weakness of Current System 14
3.4 Proposed New System 14
3.5 Requirement Analysis 15
3.6 Hardware & Software Requirements 16
Chapter :4 Feasibility Study 17
4.1 Technical Feasibility 19
4.2 Operational Feasibility 19
4.3 Schedule Feasibility 20
4.4 Economic Feasibility 20
Chapter:5 System Design 22
5.1 Functions of The System 23
5.1.1 Use Case Diagram 23
5.2 Data Modeling 25
5.2.1 Class diagram 25
5.2.2 System Activity Diagram 27
5.2.3 Data Dictionary 29
5.2.4 Sequence Diagram 34
5.3 Functional Modeling 36
5.3.1 Context Diagram 38
5.3.2 Data Flow Diagram 39
5.4 System Flow Diagram 39

15. Edu-Junction
5.5 State Transition Diagram 42
Chapter:6 Imple mentation 46
6.1 Implementation Environment 47
6.2 Program/Module Specification 47
6.3 Security Feature 48
6.4 Coding Standards 48
6.5 Sample Coding 48
Chapter:7 Testing 51
7.1 Testing Plan 52
7.2 Testing Strategy 52
7.3 Testing Method 53
7.4 Testing Cases 55
Chapter:8 Screenshots 56
Chapter:9 Conclusion and Future Work 63
9.1 Limitations 64
9.2 Future Enhancement 64
9.3 Conclusion 65
Reference 66

16. Edu-Junction
Chapter 1
INTRODUCTION
____________________________________________
 Project Profile
 Scope of System
 Technological Review
 Organizational Profile
- 1-

17. Edu-Junction
INTRODUCTION CHAPTER-1
1.1 PROJECT PROFILE:
The project which we are making is the live web based applications. EduJunction Project is a
means for people to practice online for various types of Entrance Exams, like GATE, CAT,
GCET, which are necessary to get admission in Master Degree. Where exam papers are available
to practice on it. Where user can practice on specific categories of problems that are being asked
in exams.
1.2 SCOPE OF THE SYSTEM:
The scope of the EDU-JUNCTION project includes:
 This can be used in educational institutions as well as in corporate world.
 Can be used anywhere at any time as it is web based application (user’s location doesn’t
matters).
 This gives instant feedback to students.
 This gives greater storage efficiency - tens of thousands of answer scripts can be stored on a
server compared to the physical space required for paper scripts.
 Enhanced question styles which incorporate interactivity and multimedia.
 Further, it can also be useful for anyone who requires feedback based on objective type
responses.
 Computerized marking is unbiased (fair for all individuals).
 Where user can practice on specific categories of problems that are being asked in exam,
according to their strength and weakness.
 It includes result analysis module, which gives idea to user about his/her strength and
weakness in particular types of problems related to exams.
 A part of system provides basic information and instruction about exams that makes user
aware about for what purpose the exam is, marking criteria and syllabus of exams.
1.3 TECHNOLOGICAL REVIEW:
 Tool Used: Net Beans
 Technology Used: Sun JAVA
- 2-

18. Edu-Junction
The Sun JAVA strategy was presented by Sun Microsystems officials to the rest of the world in
around1994.
1. What is Java?
-Java technology is both a programming language and a platform
-The Java is Sun’s comprehensive and consistent programming model for building applications
that have visually stunning user experiences, seamless and secure communication, and the ability
to model a range of business processes.
-The Java programming language is a high- level language that can be characterized by all of the
following buzzwords: Simple, Architecture neutral, Object oriented, Portable, Distributed, High
performance, Multithreaded, Robust, Dynamic and Secure
2. The Java platform has two components:
-The Java Virtual Machine:-It's the base for the Java platform and is ported onto various
hardware-based platforms.
-The Java Application Programming Interface (API) :- The API is a large collection of
ready-made software components that provide many useful capabilitie s.
Back-End: MySql DATABASE
MySQL, a product from Sun Microsystems is a relational database management
system combines the relational Database Engine with a graphical user interface and
software development tools. It is the core service for storing, processing, and securing
data. The Database Engine provides controlled access and rapid transaction processing to
meet the requirements of the most demanding data consuming applications within your
enterprise. The Database Engine also provides rich support for sustaining high
availability.
- 3-

19. Edu-Junction
MySQL:
 MySQL is a relational database management system (RDBMS) that runs as a server
providing multi- user access to a number of databases.
 Free-software-open source projects that require a full- featured database management
system often use MySQL.
 For commercial use, several paid editions are available, and offer additional functionality.
 Applications which use MySQL databases include Joomla, Word Process, MyBB, phpBB, Drupla
and other software built on the LAMP software stack. MySQL is also used in many high-profile,
large-scale Web products, including Wikipedia, Google (though not for searches) and Facebook.
Features of MySQL:
 Cross-platform support
 Stored procedures
 Updatable Views
 True Varchar support
 Information schema
 Independent storage engines
 SSL support
 Query caching
 Replication
 Embedded database library
 Partial Unicode support (UTF-8 and UCS-2 encoded strings are limited to the BMP)
 Hot backup (via mysqlhotcopy) under certain conditions.
1.4 ORGANIZATIONAL PROFILE:
 White Pearl IT Solution
White Pearl IT Solution has clear mission Providing Offshore Services & BPO Solutions
to US, UK, AUS & Middle East Markets. White Pearl IT Solution Is a software
development and information technology co mpany providing outsourcing solutions to
- 4-

20. Edu-Junction
enterprises worldwide? White Pearl IT Solution Offers you the ability to leverage high
quality software engineering and Software Programming talent. White Pearl IT Solution’
Software Development Center provides a scalable and cost effective solution to your IT
needs.
 Projects
White Pearl IT Solution Has built several large websites with critical business
requirements. White Pearl IT Solution have built content management sites, web-based
solutions for document collaboration and approval, and web-based search and reporting
systems to name a few. Expertise has helped companies meet the challenges of
exponential data growth, critical performance requirements and high usability
expectations.
 Service
 Technologies
- 5-

21. Edu-Junction
 Focuses
Clients who work with them do not need to juggle different suppliers on their web
project. In fact they offer world class solutions in the fields of:
-WebDesign
-WebApplicationDevelopment
-ContentManagementSystems
-eCommercesolutions
-SearchEngineOptimisation and SocialMediaConsultancy
- Multimedia Development including Virtual Tours and Interactive Presentations
 Company’s Global Presence
- India
- US
- UK
- Kenya
- 6-

22. Edu-Junction
Chapter 2
PROJECT MANAGEMENT
_____________________________________________
 Project Model
 Risk Management
 Schedule Representation
- 7-

23. Edu-Junction
PRODUCT MANAGEMENT CHAPTER-2
2.1 PROJECT MODEL:
Figure 2(a) WebE Process Model
The WebE process model
a) Formulation: An activity that identifies the goals and objectives of the webapp and
establishes the scope for the first increment.
b) Planning: It estimates overall project cost, evaluates risks associated with the
development effort and defines a finely granulated sched ule for subsequent increments.
c) Analysis: It establishes technical requirements for the Webapp and identifies the content
items that will be incorporated.
d) Engineering: It incorporates two parallel tasks illustrated on the right side in the fig.
Content Design and production are tasks performed by nontechnical members of the Web
- 8-

24. Edu-Junction
team. The intend of these tasks it to design produce and acquire all text, graphics, audio,
video content that are to become integrated into the Webapp.
e) Page generation: It is a construction activity that makes heavy use of automated tools for
Webapp creation. The content defines the engineering activity is merged with the
architectural , navigation, and interface designs to produce executable web pages in
HTML,XML and other process oriented languages.
f) Custome r Evaluation: Each increment produced as part of the web-e process is reviewed
during customer evaluation. This is the point at which the changes are requested. These
changes are integrated into the next path through the increme ntal process flow.
2.2 RISK MANAGEMENT:
Risk analysis and management are the series of step that has software team to understand
and manage uncertain risk effects quality of software being develop and enhance proper
management for the same is needed.
2.2.1 Risk Identification
Risks pose a threat to all software systems in any organization. They always
involves two characteristics namely uncertainty and loss. Risks types are categorized
as requirement risks, project risks, technical risks, business risks, organizational risks,
tool risks, estimation risks and product risks. All the possible risks have been taken
into consideration and have been categorizes as per their level.
2.2.2 Risk Analysis and Risk Planning
During risk analysis process, each of the identified risk is considered and is
placed as per their probability of occurrence and the effect of the software. The table
below shows the details.
- 9-

25. Edu-Junction
Table 2.1:Risk Analysis
Sr. no Risk probability Effect
1 Very low (<10%) Insignificant
2 Low (10-25%) Tolerable
3 Moderate (25-50%) Serious
4 High (50-75%) Catastrophic
5 Very high (>75%) S/w not acceptable
The risk which might be encounter after setting up the server are shown as below
in the table or application concise different internal and external risk. Internal risk
basically comprises with hardware failure, server down, power interruption and is
solution is specified in the table given below. External risk associated with the application
comprise of virus, hacking and corruption of files. Solution for this is specie in the below
table.
Table 2.2: Risk Planning
Sr. no Risk Type Probability Impact of risk Solution
1 h/w failure Internal Low Serious Back up
2 Virus External High Serious Antivirus
3 Hacking External Low Moderate Firemall
4 File corruption External Moderate Serious Back up
5 Server down Internal High Serious Mirror site
6 Power interruption Internal Low Low Ups
- 10 -

26. Edu-Junction
2.3 SCHEDULE REPRESENTATION:
Scheduling is the activity of specifying milestones and assigning target dates to those
milestones to ensure that deadlines are adhered to.
2.3.1 Work Breakdown Structure
The WBS should be developed before the schedule, that is, it depicts the main parts of the
project. The WBS is a good way to show the scope of the job. Participants begin to see
responsibilities before getting into details, which are the main focus of the schedule.
Essentially, the WBS is a reflection of deliverables. It is not the activities or tasks, but what
the customer will get at various stages.
Table 2.3: Schedule Representation
Milestone:
The milestone is an event that represents a point of special significance in the project.
Usually it is the completion of a major phase. A milestone is characterized by
deliverables, that is, something we can see or touch
- 11 -

27. Edu-Junction
2.3.2 Activity Chart
Gantt chart is one type of bar chart which gives the visual representation of the activities done
in project development with the flow of time. Each activity in Gantt chart is shown in left side
and a bar on time scale is shown in right side.
Table 2.4: Gantt chart
- 12 -

28. Edu-Junction
Chapter 3
SYSTEM ANALYSIS
_____________________________________________
 Problem Definition
 Existing System Study
 Problem & Weaknesses of Current System
 Proposed New System
 Requirement Analysis
 Functional Requirements
 Non-Functional Requirements
 Hardware & software requirements
- 13 -

29. Edu-Junction
SYSTEMAnalysis
3. System ANALYSIS CHAPTER-3
3.1 PROBLEM DEFINITION:
Edu-Junction is the latest way of giving and conducting exams influenced by the
information technology. Examinations can be conducted from anywhere in the world
with the help of internet and in the same way they can be given from anywhere at any
time. There is no paper-pencil work.
3.2 EXISTING SYSTEM STUDY:
The first problem is that there are loads of hard copied documents being generated.
This brings us to the age-old discussion of keeping information in the form databases
versus keeping the same on sheets of paper. The whole process of assigning test and
evaluating their scores after the test, was done manually till date. Processing the test paper
i.e checking and distributing respective scores use to take time when the software was not
installed.
3.3 PROBLEM & WEAKNESS OF CURRENT SYSTEM:
Limitations of existing manual system:
 The existing system is time consuming.
 It consumes lot of manpower for better results.
 Lack of data security.
 Retrieval of data takes lot of time.
 Reports take time to produce.
 Lack of space for storage.
3.4 PROPOSED NEW SYSTEM:
 This Project will generate computerized reports.
 This Project will reduce the manual works and loads for student as well as institution.
 This Project will reduce the waiting time for getting the reports for both students and
institutions.
- 14 -

30. Edu-Junction
 This Project will improve student satisfaction with institutional services.
 This Project will be highly desirable for future execution.
3.5 REQUIREMENT ANALYSIS:
3.5.1 Functional Requirements
Analyzing the basic Requirement of the project we concluded that the website
should be such as that
 The candidate can register to give online exams.
 Student can choose multiple courses like GATE, CAT, GCET, etc. to give online
exams.
 There can be forums, blogs, etc to discuss various queries of the candidate.
 It includes result analysis module, which gives idea to user
about his/her strength and weakness in particular types of problems
related to exams.
 Administrator can generate reports, log files, back up/recovery of data at any time.
 Time limit of the test if provided.
 System should be able to notify the student about the exam’s rules and regulations.
 System should be capable of disabling the refresh, copy paste and backtracking of the
page.
 System provides basic information and instruction about exams that makes user aware
about exams.
3.5.2 Non-Functional Requirements
 Secure access of confidential data (user’s details). SSL can be used.
 24 X 7 availability.
 Better component design to get better performance at peak time.
 Flexible service based architecture will be highly desirable for future extension.
 System should be able to handle multiple users.
- 15 -

31. Edu-Junction
3.6 HARDWARE AND SOFTWARE REQUIREMENTS:
 SOFTWARE REQUIREMENT
Table 3.1: Software Requirement
Software Requirement
Ope rating System Window XP or more
Inte rnet Explorer (Front End) IE 6 +
Editor NetBeans 6.8 IDE
Technology Java
Programming Language Java
Database Specification MySQL
 HARDWARE REQUIREMENT
Table 3.2: Hardware Requirement
Hardware Minimum Requirement
CPU Speed 1 GHz
RAM 256 MB
Hard-disk Space 40 GB
Processor Pentium III
- 16 -

32. Edu-Junction
Chapter 4
FEASIBILITY STUDY
_____________________________________________
 Technical Feasibility
 Operational Feasibility
 Schedule Feasibility
 Economic Feasibility
- 17 -

33. Edu-Junction
FEASIBLITY STUDY CHAPTER-4
For any project the feasibility analysis is very important. The feasibility analysis shows
the developers all the aspects of the project and they can know that whether the project is
practically possible to develop worth limited resources and time.
The Feasibility Study references and
summarizes the design planning and
work
STUDY
Other Documents:
Federal funding
requests, etc.
Requirements Definition,
General Design, Needs
Assessment, Prioritization
Project Management Methodology
Process
Business Requirements & Needs
Figure: 4(a) Feasibility Study Organization
- 18 -

34. Edu-Junction
4.1 TECHNICAL FEASIBILITY:
 The technical feasibility deals with the technology and the tools used to develop the
system. The requirement of the system when clearly known then a language or tool which
ever is selected must be capable of satisfying all the needs, following are some points
underlying the concept of technical feasibility.
 The organization has a well integrated MIS department with the technologies which may
satisfy all or almost all requirement of the current system the data running in the application.
 The proposed technology platform has the capacity to hold the interfaces and also have
the provision to include some of expected future requirement and features.
 For better operational situation the organization is constantly in touch with the technical
platform and updates the status of technology.
4.2 OPERATIONAL FEASIBILITY:
Any project or an application which is developed with a purpose to fulfill can be
beneficial only if it satisfies the organization requirements. In any MIS setup a new
system must not only be robust but also needs to work in tender with existing system to
he extent possible in order to reduce the work in the newer version of the system.
Following are some points underlying the concept of the operational feasibility.
 The system was well supported by the management with the part in development of the
system.
 The most important information regarding the requirements needed in the system can be
best achieved through conversation with the users of the system. With this the developer
can know about the exact problems which were faced in the order system so that they
can be eliminated from the new system.
 The end user of the system in majority of cases is a non-technical person so the
application itself and interfaces such as GUI must be simple enough that the application
can be easily operated by any one by a brief reading of the user manual.
 If the new system and older one can go shoulder to shoulder with each other still then a
lot of trimming of the existing system is needed for the complete e operational system.
- 19 -

35. Edu-Junction
 In many cases some problems are experienced after some time of implementing the
system so a timely testing/ debugging is necessary for a completely operational system.
 The users were involved with system right from the start and were constantly in touch
with the development team and every modification was observed by them.
 The proposed system makes a best effort to satisfy the requirement of the user, keeping
in mind certain infrastructural constraints.
4.3 SCHEDULE FEASIBILITY:
Time feasibility is the critical factor in deciding the amount of the benefits which
the organization can get from the system. The system should be developed takes too
much time, by the time it comes in to the use.
Many new features in the technology may have come in to the market and our
system may take dated comparison with an application built with all these new features.
So to get the maximum advantages from the system it should be developed within
deadlines and come in to use as early as possible.
4.4 ECONOMIC FEASIBILITY:
The cost involved in designing and developing a system should be a good
investment for the organization and the intangible returns which the company wick get
from. The system must be good enough that the investment be worthy. Before developing
a system the developer should give the estimate to the organization for t he cost of the
system and also the benefits that the company will get. This will help the management to
see that the investment that are making is beneficial to them or not. Some key points
related to cost benefits are given below.
 If the company decides to build the system then the cost is justified since the MIS
development is In-house.
 The hardware and the software which were to be used in the application were already
available with the company so development cost can be reduced significantly and it also
increases the gain from the system.
- 20 -

36. Edu-Junction
 If nothing was to be changed in the existing system then the cost would not increase much
but the performance of the system and the gain from the system decreases day by day due to
poor handling of the system.
 If the system is developed well before the deadline and comes in to use at early time then
it may reduce the cost of the entire system development by a good factor. So completing the
system in/ before schedule reduces the cost of system development.
- 21 -

37. Edu-Junction
Chapter 5
SYSTEM DESIGN
______________________________________________
 Functions of the system
 5.1.1 Use Case Diagram
 Data Modeling
 5.2.1Class /E-R Diagram
 5.2.2System Activity Diagram
 5.2.3Data Dictionary
 5.2.4Sequence Diagram
 Functional Modeling
 5.3.1Context Diagram
 5.3.2Data Flow Diagram
 System Flow Chart
 State Transition Diagram
- 22 -

38. Edu-Junction
SYSTEM DESIGN CHAPTER-5
5.1 FUNCTIONS OF THE SYSTEM:
5.1.1 Use Case Diagram
A use case diagram depicts actors, use cases, and the relationships among them.
Use case is a software engineering term that is equivalent to a social scientist's notion of
task. With some simple extensions, use case diagrams can be used to represent a usability
professional's task model. UML recognizes two kinds of actors, concrete actors and
abstract actors. A concrete actor represents one user population operationally defined as a
group of actors that share the same basic set of responsibilities. An abstract actor
represents a user role which is the set of responsibilities common to multiple user
populations. An abstract actor is used as a shorthand way to say, “Any concrete actor who
fulfills this role”. On a UML use case diagram, a generalization relationship (a line with
an open triangle pointing to the general case) shows which concrete actors fulfill which
abstract actor's role.
A use case represents a task. A Task is simply some piece of goal-directed work
performed by a user or organization (group of users). A task performed by an
organization is also sometimes referred to as a Process. Some modelers, this author
included, prefer to make a distinction between:
 Use case - a user task
 Business case - a business task performed by an organization (a group of users); also
sometimes called an organization case.
- 23 -

39. Edu-Junction
Login
Manage Test
Add & edit questions
Admin Manage News
Register
User
Give exam
Submit Query
Figure: 5(a) Use Case Diagram
- 24 -

40. Edu-Junction
Administrator:
 Administrator logs in with user id and password
 Administrator manages users who are registered and not registered.
 Administrator will register users and provide them id and password, so that if they want
to update/delete/edit their information they can easily do that.
 Administrator manages news section and gives the reply for queries which has been
posted by student.
 Administrator will log out from his/her account.
User:
 User login with user id and password.
 If he is not a registered user he will register himself and than admin will provide them
with id and password.
 User can update their information.
 User will log out from his/her account.
5.2 DATA MODELING:
5.2.1 Class Diagram
In software engineering, a class diagram in the Unified Modeling Language (UML) is a
type of static structure diagram that describes the structure of a system by showing the
system's classes, their attributes, operations (or methods), and the relationships among the
classes.
The class diagram is the main building block of object oriented modeling. It is used both
for general conceptual modeling of the systematic of the application, and for detailed
modeling translating the models into programming code. Class diagrams can also be used
for data modeling. The classes in a class diagram represent both the main objects and or
interactions in the application and the objects to be programmed. In the class diagram
these classes are represented with boxes which contain three parts:
 The upper part holds the name of the class
- 25 -

41. Edu-Junction
 The middle part contains the attributes of the class
 The bottom part gives the methods or operations the class can take or undertake.
To specify the visibility of a class member (i.e., any attribute or method) there are the
following notations that must be placed before the member's name:
+ Public
- Private
# Protected
~ Package
/ Derived
Class diagrams also display relationships such as containment, inheritance, associations
and others
The association relationship is the most common relationship in a class diagram. The
association shows the relationship between instances of classes. For example, the class
Order is associated with the class Customer. The multiplicity of the association denotes
the number of objects that can participate in then relationship.1 For example, an Order
object can be associated to only one customer, but a customer can be associated to many
orders.
Another common relationship in class diagrams is a generalization. A generalization is
used when two classes are similar, but have some differences.
Class diagrams are used in nearly all Object Oriented software designs. Use them to
describe the Classes of the system and their relationships to each other.
- 26 -

42. Edu-Junction
QUESTION TEST
CUSTOMER
-qid -tid
-tid * 1 -cid -uid
-question -name -fname
-options -duration -lname
-answer -total marks * 1 -address
-cid -criteria -mo.no
-dob
-designation
-mail
-password
+login()
+logout()
+viewResult()
ADMIN
STUDENT
+change_settings()
+managa_data() +giveTest()
Figure: 5(b) Class Diagram
5.2.2 System Activity Diagram
Activity diagrams are graphical representations of workflows of stepwise
activities and actions with support for choice, iteration and concurrency. In the Unified
Modeling Language, activity diagrams can be used to describe the business and
operational step-by-step workflows of components in a system. An activity diagram
shows the overall flow of control.
Activity diagrams are constructed from a limited repertoire of shapes, connected
with arrows. The most important shape types:
 rounded rectangles represent activities;
 diamonds represent decisions;
 bars represent the start (split) or end (join) of concurrent activities;
 a black circle represents the start (initial state) of the workflow;
- 27 -

43. Edu-Junction
 An encircled black circle represents the end (final state).
Arrows run from the start towards the end and represent the order in which
activities happen. Hence they can be regarded as a form of flowchart. Typical flowchart
techniques lack constructs for expressing concurrency. However, the join and split
symbols in activity diagrams only resolve this for simple cases; the meaning of the model
is not clear when they are arbitrarily combined with decisions or loops. While in UML
1.x, activity diagrams were a specialized form of state diagrams, in UML 2.x, the act ivity
diagrams were renormalized to be based on Petri net- like semantics, increasing the scope
of situations that can be modeled using activity diagrams. These changes cause many
UML 1.x activity diagrams to be interpreted differently in UML 2.x
Activity diagrams should be used in conjunction with other modeling techniques such
as interaction diagrams and state diagrams. The main reason to use activity diagrams is to
model the workflow behind the system being designed. Activity Diagrams are also useful
for: analyzing a use case by describing what actions need to take place and when they
should occur; describing a complicated sequential algorithm; and modeling applications
with parallel processes.
- 28 -

44. Edu-Junction
Registration Login Help Support Query
Invalid Login
Not Registered
Valid
Admin Login Student Login
Result
Manage Data Reply Queries
Test
Logout
Figure: 5(c) Activity Diagram
5.2.3 Data Dictionary
Data Dictionaries are an integral component of analysis, since data flow diagram
by him or she does not fully describe the subjects of the investigation.
- 29 -

45. Edu-Junction
A data dictionary is a catalog of the element in as system. This element centers on
data and the way are structured to meet user‘s requirements and needs. The major
elements are dataflow, data stores and processes. Data dictionary stores details and
description of these elements.
It is developed during data analysis and assists ana lysis involved in determining
the system. Four main reasons of analysis are:
 To manage the details in large system.
 To communicate a common meaning for all system elements.
 To document the features of the system.
 To locate the errors and omissions in the system.
The data dictionary contains two types of descriptions as following:
1. Data Elements: The most fundamental data level is the data element. Data element is
the building block for all others in the system.
2. Data Structure: A data structure is a set of items that are related to one another that
describes components in the system
Database tables:
1) News and Update:-
Table 5.1 News and Updates
Field Name Data Type Constraints
Id Varchar Primary key, Auto Increment
Description Text Not null
Title Varchar Not null
Primary Key: Id
Reference Key: No reference key.
Description: News and Update contains the details of News and Updates.
- 30 -

46. Edu-Junction
2) Registration:
Table 5.2 Registration
Field Name Data Type Constraints
User_name Varchar Not null
User_id Bigint Primary key
User_password Varchar Not null
User Address Varchar Not null
Email_id Varchar Not null
Phone_no Bigint Not null
Gender Boolean Not null
Date_of_birth Date –time Not null
Registration_date Date
Confirmation _code Boolean
Primary Key: User_id
Reference Key: No reference key.
Description:. This table contains all the information of the Users like First
name, Last name , Address, Contact number, Email Id, etc
3) Confirmation:-
Table 5.3 Confirmation
Field Name Data Type Constraints
Confirmation_id Bigint Primary key
User_id Varchar Reference key
Confirmation_code Varchar Not null
Primary Key: Confirmation_id
Reference Key: User_id from table Registration (User_id).
Description: This table contains user id and their confirmation code.
- 31 -

47. Edu-Junction
4) Category:-
Table 5.4 Category
Field Name Data Type Constraints
Cat_id Bigint Primary key
Cat_desc Varchar or Text -
Cat_name Varchar Not null
Parent_id Bigint Not null
Primary Key: Cat_id
Reference Key: No reference key.
Description: Category table contains all the category and subcategories of
entrance exams.
5) Test:-
Table 5.5 Test
Field Name Data Type Constraints
Cat_id Bigint Reference key
Test_id Bigint Primary key
Test_name Varchar Not null
Test_desc Text Not null
Test_total_marks Int Not null
Duration Int Not null
Test_category Varchar Not null
Primary Key: Test_id
Reference Key: Cat_id from Category(Cat_id) table.
Description: This table contains the all information of test like Test name, Test
duration, Total marks, Criteria, Category of test, etc.
- 32 -

48. Edu-Junction
6) Question:-
Table 5.6 Question
Field Name Data Type Constraints
Que_id Bigint Primary key
Test_id Bigint Reference key
Cat_id Bigint Reference key
Question Text Not null
Option1 Varchar Not null
Option2 Varchar Not null
Option3 Varchar Not null
Option4 Varchar Not null
Correct_answer Int Not null
Primary Key: Que_id
Reference Key: Test_id from Test(Test_id) table, Cat_id from
Category(Cat_id) table.
Description: This table contains all Questions, Options, Answer of test.
7) Result:-
Table 5.7 Result
Field Name Data Type Constraints
Result_id Bigint Primary key
User_id Bigint Reference key
Test_id Bigint Reference key
Marks Varchar Not null
(Category_id,
Marks_scored)
Primary Key: Result_id
Reference Key: Test_id from Test(Test_id) table, User_id from
Registration(User_id) table.
- 33 -

49. Edu-Junction
Description: This table contains information of Test Result.
5.2.4 Sequence Diagram
Usage scenarios:
A usage scenario is a description of a potential way your system is used.
The logic of a usage scenario may be part of a use case, perhaps an alternate
course. It may also be one entire pass through a use case, suc h as the logic
described by the basic course of action or a portion of the basic course of action,
plus one or more alternate scenarios. The logic of a usage scenario may also be a
pass through the logic contained in several use cases. For example, a stude nt
enrolls in the university, and then immediately enrolls in three seminars.
The logic of methods:
Sequence diagrams can be used to explore the logic of a complex
operation, function, or procedure. One way to think of sequence diagrams,
particularly highly detailed diagrams, is as visual object code.
The logic of services:
A service is effectively a high- level method, often one that can be invoked
by a wide variety of clients. This includes web-services as well as business
transactions implemented by a variety of technologies such as CICS/COBOL or
CORBA-compliant object request brokers (ORBs).
- 34 -

50. Edu-Junction
Figure: 5(d) Sequence diagram of User Registration
Figure: 5(e) Sequence diagram of User Test
- 35 -

51. Edu-Junction
Figure: 5(f) Sequence diagram of Admin
5.3 FUNCTIONAL MODELING:
A data-flow diagram (DFD) is a graphical representation of the "flow" of
data through an information system. DFDs can also be used for the visualization of data
processing (structured design).
On a DFD, data items flow from an external data source or an internal data
store to an internal data store or an external data sink, via an internal process. A DFD
provides no information about the timing of processes, or about whether processes will
operate in sequence or in parallel. It is therefore quite different from a flowchart, which
shows the flow of control through an algorithm, allowing a reader to determine what
operations will be performed, in what order, and under what circumstances, but not what
kinds of data will be input to and output from the system, nor where the data will come
from and go to, nor where the data will be stored.
It is common practice to draw a context-level data flow diagram first, which
shows the interaction between the system and external agents which act as data sources
and data sinks. On the context diagram (also known as the Level 0 DFD) the system's
interactions with the outside world are modeled purely in terms of data flows across the
system boundary. The context diagram shows the entire system as a single process, and
gives no clues as to its internal organization.
- 36 -

52. Edu-Junction
This context- level DFD is next "exploded", to produce a Level 1 DFD that
shows some of the detail of the system being modeled. The Level 1 DFD shows how the
system is divided into sub-systems (processes), each of which deals with one or more of
the data flows to or from an external agent, and which together provide all of the
functionality of the system as a whole. It also identifies internal data stores that must be
present in order for the system to do its job, and shows the flow of data between the
various parts of the system.
Data- flow diagrams were invented by Larry Constantine, the original
developer of structured design, based on Martin and Estrin's "data-flow graph" model of
computation.
Data- flow diagrams (DFDs) are one of the three essential perspectives of the
structured-systems analysis and design method SSADM. The sponsor of a project and the
end users will need to be briefed and consulted throughout all stages of a system's
evolution. With a data- flow diagram, users are able to visualize how the system will
operate, what the system will accomplish, and how the system will be implemented. The
old system's dataflow diagrams can be drawn up and compared with the new system's
data-flow diagrams to draw comparisons to implement a more efficient system. Data- flow
diagrams can be used to provide the end user with a physical idea of where the data they
input ultimately has an effect upon the structure of the whole system from order to
dispatch to report. How any system is developed can be determined through a data- flow
diagram.
- 37 -

53. Edu-Junction
5.3.1 Context Diagram
Login, Register, Generated
Give Test Reports
User EduJunction Admin
Test
Question,Result Insert, Update,
Information Delete Data
Figure: 5(g) Context Diagram
5.3.2 Data Flow Diagram
- 38 -

54. Edu-Junction
UserID/Password
Admin UserID/Password
User
Reg. info
Add/ UserID/Password
Reg. info
Update
Data Login
View Data
Registration Request
Test,
selected
Ans
Registration
Add/Edit/
Delete
Category Category
Manage
Data Questions
Add/Edit/
Delete Test
Retrive
Price
Result
info Result Test
Result
info
Result store
Result info
Test
Figure: 5(h) Data Flow Diagram
5.4 SYSTEM FLOW CHART:
A flowchart is a common type of diagram, which represents an algorithm or
process, showing the steps as boxes of various kinds, and their order by connecting these
with arrows. This diagrammatic representation can give a step-by-step solution to a given
problem. Data is represented in these boxes, and arrows connecting them represent flow /
direction of flow of data. Flowcharts are used in analyzing, designing, documenting or
managing a process or program in various fields.
Symbols
A typical flowchart from older Computer Science textbooks may have the
following kinds of symbols:
- 39 -

55. Edu-Junction
Start and end symbols
Represented as circles, ovals or rounded rectangles, usually containing the
word "Start" or "End", or another phrase signalling the start or end of a process, such as
"submit enquiry" or "receive product".
Arrows
Showing what's called "flow of control" in computer science. An arrow coming
from one symbol and ending at another symbol represents that control passes to the
symbol the arrow points to.
Processing steps
Represented as rectangles (or oblongs). Examples: "Add 1 to X"; "replace
identified part"; "save changes" or similar.
Input/output
Represented as a parallelogram. Examples: Get X from the user;
display X.
Conditional or decision
Represented as a diamond (rhombus). These typically contain a Yes/No question
or True/False test. This symbol is unique in that it has two arrows coming out of it,
usually from the bottom point and right point, one corresponding to Yes or True, and one
corresponding to No or False. The arrows should always be labeled.A decision is
necessary in a flowchart. More than two arrows can be used, but this is normally a clear
indicator that a complex decision is being taken, in which case it may need to be broken-
down further, or replaced with the "pre-defined process" symbol. A number of other
symbols that have less universal currency, such as:
 A Document represented as a rectangle with a wavy base;
 A Manual input represented by parallelogram, with the top irregularly sloping up from
left to right. An example would be to signify data-entry from a form;
- 40 -

56. Edu-Junction
 A Manual operation represented by a trapezoid with the longest parallel side at the top, to
represent an operation or adjustment to process that can only be made manually.
 A Data File represented by a cylinder.
Flowcharts may contain other symbols, such as connectors, usually repres ented
as circles, to represent converging paths in the flowchart. Circles will have more than one
arrow coming into them but only one going out. Some flowcharts may just have an arrow
point to another arrow instead. These are useful to represent an iterative process (what in
Computer Science is called a loop). A loop may, for example, consist of a connector
where control first enters, processing steps, a conditional with one arrow exiting the loop,
and one going back to the connector. Off-page connectors are often used to signify a
connection to a (part of another) process held on another sheet or screen. It is important to
remember to keep these connections logical in order. All processes should flow from top
to bottom and left to right.
- 41 -

57. Edu-Junction
Registration Login
False
Authentication
true
Manage Admin
Login
Data Type
Student/User
View Result
History
Select Menu
Result
Analysis
For Test result
Test
Log out
Figure: 5(i) Flow Chart
5.5 STATE-TRANSITION DIAGRAM(STD):
A State-Transition Diagram is a way of describing the time-dependent behaviour
of a system. The basic consistency rule is: "A system's behaviour in any state must be the
same no matter by which path the state is arrived at".
States:
- 42 -

58. Edu-Junction
 A state is an observable mode of behaviour of the system.
 At any time a particular STD can only be in one state.
 A system's behaviour could be described by more than one state transition
diagram.
Transition conditions:
 Internal events or events external to the system.
Transition actions:
 Actions in response to the events.
 Triggering one-shot actions.
 Synchronizing between different STD's.
 Producing control outputs.
Drawing STD's:
 Identify observable states of the system.
 Select the states with normal behaviour.
 Specify the conditions that mark a transition.
 Specify the actions to produce the observable behaviour in the destination state for
each transition.
 If the system is complex, partition the diagram in several STD's.
- 43 -

59. Edu-Junction
Figure: 5(j) Diagram for Login+Registration
User Selects Start Test Select Category
Load Questions and Randomize It
Time Up
Force Fully submit test Start Test
User Press Submit Button
Submit Test
Result Analysis
Figure: 5(k) Diagram for Test Module
- 44 -

60. Edu-Junction
Figure: 5(l) Help and Support
Figure: 5(m) Diagram for Admin
- 45 -

61. Edu-Junction
Chapter 6
IMPLEMENTATION
______________________________________________
 Implementation Environment
 Program/Modules Specification
 Security Features
 Coding Standards
 Sample Coding
- 46 -

62. Edu-Junction
IMPLEMENTATION CHAPTER-6
6.1 IMPLEMENTATION ENVIRONMENT:
1. Single vs. Multi User
The application Edu-Junction is now going to be developed is web application so,
at the time of implementation of this web site it should be kept in mind that system will
be used con currently by users. For the concurrent use of this web site the approach is
developed for the concurrent use.
2. GUI vs. Non-GUI
The system is completely GUI. This is because now-a-days users feel comfortable
while working with images or pictures. As the project is web based, it can be used by any
technical or non-technical user. Thus user should feel convenient while working with the
system.
6.2 PROGRAM/MODULES SPECIFICATION:
6.2.1 Outside modules
Functionalities of this module are following:
1. Login
2. Registration
3. Help & support
4. News & updates
5. Available Exams
6.2.2 User Modules
Functionalities of this module are following:
1. News & updates
2. Start Test
3. Test analysis
4. Result Analysis
5. Admin panel & Info desk
- 47 -

63. Edu-Junction
6.2.3 Admin panel Modules
Functionalities of this module are following:
1. Manage Categories (Add/Edit/View All/Delete)
2. Manage News And Updates (Add/Edit/View All/Delete)
3. Change Email settings
4. Add Test
5. Manage Test(Edit/Delete/View All)
6.3 SECURITY FEATURES:
This website has following features:
1. In this website we are providing best security so that no one can hack this site.
2. The admin site is password protected. Only authorized user can access the admin side.
3. Any user cannot make anyone’s fake account in our site since we are providing
confirmation mail facility without which no one can be registered or can use our site.
6.4 CODING STANDARDS:
We have strictly followed the coding standard throughout the whole Web
APPLICATION Traveling Agency. The coding standards which we have followed are
defined below.
1. Each table has the simple short name.
2. In that database name, method name, and variables names are related to the processes
and the behavior of the program me.
3. Method names are also given by process and behavior of the method.
4. We used Mail API to send confirmation code to users.
5. We have shown the assessment of student's result in graphical form.
6.5 SAMPLE CODING:
This code will verify whether the login id and password is valid or not. Also it will check
whether the user has activated account or not.
- 48 -

64. Edu-Junction
import java.io.IOException;
import java.io.PrintWriter;
import javax.servlet.ServletException;
import javax.servlet.annotation.WebServlet;
import javax.servlet.http.HttpServlet;
import javax.servlet.http.HttpServletRequest;
import javax.servlet.http.HttpServletResponse;
import java.sql.*;
import javax.servlet.http.HttpSession;
import db.*;
/**
*
* @author p
*/
@WebServlet(name = "verifylogin", urlPatterns = {"/verifylogin"})
public class verifylogin extends HttpServlet {
@Override
protected void doPost(HttpServletRequest request, HttpServletResponse response)
throws ServletException, IOException {
response.setContentType("text/html;charset=UTF-8");
PrintWriter out = response.getWriter();
HttpSession session = request.getSession();
Statement stmt = null;
String user_name = request.getParameter("username");
String user_password = request.getParameter("pwd");
if (user_name == null) {
user_name = "";
}
if (user_password == null) {
user_password = "";
}
try {
Connection conn = manager.connection();
stmt = conn.createStatement();
ResultSet rs = stmt.executeQuery("select * from registration where
user_name='" + user_name + "' and user_password='" + user_password + "' and
isactive=1");
if (!user_name.equals("") && !user_password.equals("")) {
- 49 -

65. Edu-Junction
if (rs.next()) {
session.setAttribute("SessionUser", user_name);
Long user_id =rs.getLong("user_id");
session.setAttribute("SessionUserId",user_id );
if (rs.getInt("login_type") == 0) {
response.sendRedirect("admin/home.jsp");
System.out.println("hello admin");
}
else {
response.sendRedirect("newjsp.jsp");
}
}
} else if (user_name.equals("")) {
out.println("User name required");
out.println("<br/><a href=index.jsp>Go back!</a>");
} else if (user_password.equals("")) {
out.println("Password required.");
out.println("<br/><a href=index.jsp>Go back!</a>");
} else {
out.println("invalid " + user_name + "!");
return;
}
} catch (Exception e) {
System.out.print("e" + e);
e.printStackTrace();
}
}
}
- 50 -

66. Edu-Junction
Chapter 7
TESTING
______________________________________________
 Testing
 7.1 Testing Plan
 7.2 Testing Strategy
 7.3 Testing Method
 7.4 Testing Cases
- 51 -

67. Edu-Junction
TESTING CHAPTER-7
7.1 TESTING PLAN:
Testing was done on a regular basis during the coding phase itself. Also a separate session
was kept for testing. Some errors were uncovered and the code was modified to ensure
the removal of the error. Extensive testing was done to ensure the correctness of the
project Also a list of desired outputs was made and the code was tested to see if the
outputs are consistent. A large amount of situations were simulated and the inputs
generated were provided to the project to see whether the desired output is available or
not.
Requirement of Test Planning:
One of the roles of software testing is to ensure that the product meets the requirements of
the customer. Capturing the requirements therefore becomes an essential part not only to
help developed product is likely to meet customer needs. Often times in smaller
development organization, the task of requirements management falls prey to conjectures
of what ought to be developed as opposed to what is needed in the market. Therefore,
requirements management and its translation to produce test plans is an impor tant step.
7.2 TESTING STRATEGY:
The testing strategy which we have used to test our system is Black-box testing. In the
black-box approach, test cases are designed using only functional specification of the
software, i.e. without any knowledge of the internal structure of the software. For this
reason, black-box testing is also known as functional testing.
In black-box testing, test cases are designed from an examination of the input/output
values only and no knowledge of design or code is required. The following are two main
approaches to design black-box test cases:
1. Equivalence class partitioning
In this approach, the domain of input values to a program is partitioned into a set
of equivalence classes. This partitioning is done such that the behavior of the
program is similar to every input data belonging to the same equivalence class.
Equivalence classes can be designed by examining both the input and the output
data.
- 52 -

68. Edu-Junction
2. Boundary value analysis
A type of programming error frequently occurs at the boundaries of the different
equivalence classes of input. For example, programmers may improperly use
< instead of <=, or conversely <= instead of <. Boundary value analysis leads to
selection of test case at the boundary of the different equivalence classes.
The strategy for black-box testing is intuitive and simple. The most important step is the
identification of equivalence classes.
7.3 TESTING METHODS:
Web based applications need intensive testing, as the applications will always
function as a multi- user system with bandwidth limitations. Some of the testing to be
done are Integration testing, Stress testing, resolution testing, Scalability testing, Cross-
browser compatibility testing etc. Both automated testing and manual testing should be
done without fail.
1. Unit Testing
Unit testing focuses verification effort on the smallest unit of Website
design that is the module. Unit testing exercises specific paths in a module’s
control structure to ensure complete coverage and maximum error detection. This
test focuses on each module individually, ensuring that it functions properly as a
unit. Hence, the naming is Unit Testing.
2. Integration Testing
Integration testing addresses the issues associated with the dual problems
of verification and program construction. After the software has been integrated a
set of high order tests are conducted. The main objective in this testing process is
to take unit tested modules and builds a program structure that has been dictated
by design.
3. Task Testing
Task testing helps my system to test whether all the task are carried out
properly or not. It also solves logical errors. Thus all processing in my system is
appropriate.
- 53 -

69. Edu-Junction
4. Behavioral Testing
This testing is useful to determine the behavior of the real- time systems.
This testing helped to develop the test case for the particular system. This testing
helps to test the different events associated with the system.
5. Inte r task Testing
There Are Several Processes Or Tasks Which Are Carried Simultaneously.
Moreover This Testing Also Helps To Test The Errors Associated With The Data
Storage Activities. This Testing Helped My Project To Solve The Error While
Data Designing Which Is Important In Developing The Successful Project.
6. Final Testing
After The Integration Of The All Modules, We Deploy Whole Application
On The Demo Server. One Of The Member Of The Development Team Will
Done The Testing Of The Whole Website And Then Create Excel Sheet Of The
Bugs. After The Completion Of This Testing, Respective Team Member Will
Solve Bugs And Upload New Version Of The Project. Again, Member Who
Initially Test Again.
7. Alpha Testing
It is done by the person who is not involved in development team. He/She
will test the system from the user perspective. That person tests the system and
generates the bug’s reports, and then the development team solve those bugs.
Developer updates those listed axles sheet bugs with details.
8. Black-Box Testing
Black box testing is implementing our project by testing each and every
independent module in System for dependent module. We check the dependency
and interface after integrating all modules. For behavior or performance testing
we first made demo give it to our project guide and some customers to use and
check performance and also check the performance how the project act for input
and gives what the output To check for missing function or incorrect function as
part of this testing we have check all the functionality and check for all the output
- 54 -

70. Edu-Junction
that ire run perfectly. As per our project we also have check the shape files as
external data.
9. White- Box Testing
Also called 'Glass Box' or 'Structural' testing Tester has access to the
system design. As per our project we have used also white Box Testing Model
because independent paths of modules and loops are the cornerstones of majority
of all algorithms implemented in the software. There are five deferent classes of the
loops, which can be defined as follows.
1. Simple Loops
2. Nested Loops
3. Concatenated Loops
4. Unstructured Loops
5. Continuous Loops
7.4 TEST CASES:
In software engineering, the most common definition of a test case is set of conditions or
variables under which a tester will determine if a requirement or use case upon an
application is partially or fully satisfied. In that situation each sub requirement must have
at least one test case.
- 55 -

71. Edu-Junction
Chapter 8
SCREENSHOTS
______________________________________________
 Screenshot
- 56 -

72. Edu-Junction
Login:-
-User need to login with valid username and password and admin need to login with
admin id and password.
Registration:-
- The interested visitor need to register.
- 57 -

73. Edu-Junction
Admin:
1) Admin HomePage
2)Admin Functions:
Admin can perform add, edit, update and delete.
Add Category:
- 58 -

74. Edu-Junction
Manage Test:
Edit Test :
User:
 User checks for available exams for specific category and can select from these
test and perform it.
- 59 -

75. Edu-Junction
 After the completion of the test result will be displayed.
 User can also check previously given test results.
Select Test(Specific category)
Instruction Of Selected Test:
- 60 -

76. Edu-Junction
Give Test :
Result Analysis:
- 61 -

77. Edu-Junction
Previous Records:
- 62 -

78. Edu-Junction
Chapter 9
CONCLUSION AND FUTURTE WORK
______________________________________________
 Limitations
 Future Enhancement
 Conclusion
- 63 -

79. Edu-Junction
CONCLUSION AND FUTURE WORK CHAPTER-9
Every project work, doesn’t matter software project or any other project, could not be the
result of sole effort. I think success of any project doesn’t depend only on better software
development skills, but also, zeal to listen and help the users. Only user interaction at
development phase can give you an idea to fulfill their requirements. Because, software
belongs to the developer up to the development or the installation phase and then after it
belongs to the user. It has been a long and an untiring effort from my side in the overall
training and development of my project. Before beginning of project I had undertook a
very vigorous training where I was imparted both the Technical and Non-Technical skills.
On the technical side, I had gone through the JAVA and MYSQL. In project specific
training I had undergone through JAVA programming basic training. This training gave
me more in-depth knowledge and also cleared many of my assumptions and doubts. I
finally completed the web application. On the non-technical side, I was imparted various
soft skills such as GUI, Ownership, communication and many more. On the whole I was
able to complete my Application successfully.
9.1 LIMITATIONS:
i. Admin cannot make package for test/lectures
ii. This system contain multiple choice question with only one answer but there are
many questions which have more than one correct answers. So, facility is missing.
iii. Admin cannot add images as options in questions.
9.2 FUTURE ENHANCEMENT:
i. In future I would like to add multiple answers for a each question where its needed
in multiple choice question.
ii. In future, I would like to give admin one more facility to add packages of
test/lectures.
iii. I am thinking to provide facility for admin to add images as questions.
iv. Because of time limit I am not able to complete Lecture module, so I would like to
setup a lecture facility in this project.
- 64 -

80. Edu-Junction
9.3 CONCLUSION:
At the end of my work I conclude that………..
I have developed an online Examination System. The system was proposed during title
selection of projects. The system is developed to manage the problems faced during the
manual examination which was very much time consuming and which gives less accurate
result
During this project, I got a chance to sharpen my skills on technical, analysis or
interpersonal skills. This project is finished according to Web E Process model approach
and through this approach I was able to learn more on practically how to work in a project
individually.
On the early stage, I developed the problem project scope and objective to determine
requirements to make the project successfully. There are a few types of modeling I used
such as, Data Flow Diagrams for others to visualize how the system is going to be.
- 65 -

81. Edu-Junction
REFERENCES
References:
1. Oriented Modeling and Design with UML second edition by Michael Blaha and
James Rambaugh.
2. Pressman R.S., Software Engineering: A Practitioner's Approach, TMH.
3. www.w3schools.com
- 66 -