115
Page 87 ABSTRACT
| Date post: | 13-Apr-2016 |
| Category: |
Documents |
| Upload: | ramesh-reddy-gavva |
| View: | 32 times |
| Download: | 0 times |
P a g e 8 7
ABSTRACT
1. Abstract
Android Based Mobile Campus is developed to provide students with information
regarding library due dates, any placement activities, general notices, attendance and
marks details. This information should be provided to students in a cost effective way.
So to achieve the same, we have developed this application, wherein students can
access this information using their Android enabled mobiles. The mode of
communication is Android. Students need not queue up near notice board / log on to
college website for any of the above mentioned details. Just come into the proximity
limit of one of the many available Android points and explore the service.
Block Diagram:
Medium of communication: Android
Android
Enabled mobile
Android
USB adapter (D-Link)
P a g e 8 7
Internet PC withWindows XP Service Pack2
P a g e 8 7
INTRODUCTION
2. INTRODUCTION:
2.1GENERAL INFORMATION
With the advance in time and technology there is a need for faster dissemination
of information. Connected, personalized, intelligent information appliances are
becoming increasingly important in our business and private lives. These appliances
include devices such as cell phones, two-way pagers, personal organizers, screen
phones, and POS terminals.
In a real world scenario, such as college campus, information in the form of
notices, hand-written manuals, oral communication, is spread among the students.
Today it is imperative to not only use the traditional forms of communication, but also
newer forms such as mobile technology, for quicker and easier communication among
the students.
Student-Alumni Interaction
Students can query the server for alumni information by specifying either the
company name or the name and year of passing out through his mobile. Based
on the search criteria, the list of alumni names is displayed. The student can get
further information about the alumni on request.
Student Information
Students can query the server for student information by specifying the student
name, department, semester through his mobile. List of student names is
displayed. Further information about the student can be obtained on request.
General notices
These consist of general campus recruitment notices such as information
regarding the recruiting company, campus interview date and other placement
activities. The placement officer sends the notice to the students through the
server.
P a g e 8 7
Project/Seminar Information
The students can query the server for the project seminar information by
specifying the topic or platform or field.
A student can query for project/seminar information based on topic, field or
platform using his mobile. Based on the search criteria, the names of available
project/seminars are displayed. On further request, information about the
authors/participants is displayed.
2.2 STATEMENT OF THE PROBLEM
The focus of our project is on helping to students. Instead of manual notice broad
college can use the electronic flow of data . at the time of manual notice may occurs the
errors but in the electronic flow system low errors are occurs .
Now a days every body using high quality and Android supported mobiles . so in
this project we used Android to communication between college and students.
2.3 OBJECTIVE OF THE STUDY
The following lists of objectives must be completed with this in mind:
1. An application will need to be developed using the J2ME java platform for
programs running on mobile devices using the Java APIs for Android Wireless.
2. Create ad hoc Android network that is formed by interconnecting devices. This
allows every Android device to be reached by every other device. This is
P a g e 8 7
necessary due to Android’s short communication range (10m-100m). This will
enable the user to connect to all devices on the network without having to worry
about distance form the device.
3. Conduct Experiments and Analyse Data: Using the mobile device and the
antenna , conduct tests on usability and product range within a home
environment.
The user will require the following components:
Android enabled device
Client Software
Antenna
The application should be capable of running on several platforms. An application will
be created to run on devices such as mobile phones, PDA’s and Blackberry devices. To
make the software work on as many devices as possible, applications will also be
written to operate on Windows Mobile clients as well as Android enabled Windows PCs.
The goal for this application is to make it as robust as possible so that it can be run on
many different platforms.
Android wireless technology will be used which is a short range communications
network that was developed to replace cables that connect portable and fixed devices.
Android is capable of providing low power, low cost and robust communications
between devices. The Android standard has been globally accepted which allow almost
any Android enabled device to communicate with each other seamlessly. This makes
the Android standard best suited for this type of installation.
2.4 METHODOLOGY
Iterative and Incremental development is a cyclic software development process
developed in response to the weaknesses of the waterfall model. It starts with an initial
planning and ends with deployment with the cycleic interaction in between.
P a g e 8 7
The Basic idea
.The basic idea behind iterative enhancement is to develop a software system
incrementally, allowing the developer to take advantage of what was being learned
during the development of earlier, incremental, deliverable versions of the system.
Learning comes from both the development and use of the system, where possible key
steps in the process are to start with a simple implementation of a subset of the
software requirements and iteratively enhance the evolving sequence of versions until
the full system is implemented. At each iteration, design modifications are made and
new functional capabilities are added.
The procedure itself consists of the initialization step, the iteration step, and the Project
Control List. The initialization step creates a base version of the system. The goal for
this initial implementation is to create a product to which the user can react. It should
offer a sampling of the key aspects of the problem and provide a solution that is simple
enough to understand and implement easily. To guide the iteration process, a project
control list is created that contains a record of all tasks that need to be performed. It
includes such items as new features to be implemented and areas of redesign of the
existing solution. The control list is constantly being revised as a result of the analysis
phase.
The iteration involves the redesign and implementation of a task from the project control
list, and the analysis of the current version of the system. The goal for the design and
implementation of any iteration is to be simple, straightforward, and modular, supporting
redesign at that stage or as a task added to the project control list. The level of design
detail is not dictated by the interactive approach. In a light-weight iterative project the
code may represent the major source of documentation of the system; however, in a
mission-critical iterative project a foral Software Design Document may be used. The
analysis of an iteration is based upon user feedback, and the program analysis facilities
available. It involves analysis of the structure, modularity, usability, reliability, efficiency,
P a g e 8 7
& achievement of goals. The project control list is modified in light of the analysis
results.
Iterative development
Iterative development slices the deliverable business value (system functionality) into
iterations. In each iteration a slice of functionality is delivered through cross-discipline
work, starting from the model/requirements through to the testing/deployment. The
unified process groups iterations into phases: inception, elaboration, construction, and
transition.
Inception identifies project scope, risks, and requirements (functional and non-
functional) at a high level but in enough detail that work can be estimated.
Elaboration delivers a working architecture that mitigates the top risks and fulfills
the non-functional requirements.
Construction incrementally fills-in the architecture with production-ready code
produced from analysis, design, implementation, and testing of the functional
requirements.
Transition delivers the system into the production operating environment.
Each of the phases may be divided into 1 or more iterations, which are usually time-
boxed rather than feature-boxed. Architects and analysts work one iteration ahead of
developers and testers to keep their work-product backlog full.
P a g e 8 7
P a g e 8 7
P a g e 8 7
LITERATURE SURVEY
P a g e 8 7
P a g e 8 7
HARDWARE AND SOFTWARE REQUIREMENT
Software Requirements:
Software Configuration:
Operating System Windows 95/Above
Packages: Java(Jdk 1.6/ Above)
Microsoft Access 2008
Jakarta-Tomcat Server
Android 4.2.2
MS-Dos (Version 5.0/Above)
Report Build MS Word
Hardware Requirements:
Internet-conn1ection
Java-enabled cell phone with file transfer capability
Android enabled cell phone
PC with Android USB Adapter Connected.
P a g e 8 7
5. SOFTWARE REQUIREMENT SPECIFICATION
P a g e 8 7
SOFTWARE REQUIREMENT SPECIFICATION
Functional Requirements
Functions:
Polling
The college management will be able to poll the question to the
students and can view the results of the poll
The students will be able to respond to the question with the
options provided
Complaints and Suggestions
The students can lodge their complaints/suggestions to the college
management.
The college management can view the complaints lodged by the
students.
Student-Alumni interaction
The students can query for the alumni information by specifying
either the company or the name and year of passing.
Student Information
The students can query for the information of any student in the
college by specifying his/her department, semester.
Placement Cell
The students will be sent recruitment notices which consist of the
number of students recruited and contact information of the
recruited students.
The students will be sent general notices which consists
information of the placement activities.
Project/Seminar information
P a g e 8 7
The students can query the server for the project seminar
information by specifying the topic or platform or field.
System Administrator
The system administrator can enable/disable any of the
applications.
He/She can customize the applications according to the needs of
his/her college. For e.g.: USN number format.
In the complaints and suggestions section he/she can mention the
subject and the persons to whom complaints/suggestions are to go
and can set the number of messages after which the
complaints/suggestions have to be sent as a mail to the respective
persons.
Operational Scenarios and interface requirement:
Actor: Student
a) Scenario Student has to register himself to the
server
Interface Requirement an user interface with provisions for
enter the University seat number will be
provided.
b) Scenario Student has to answer to a poll.
Interface Requirement An user interface with the question and
options for selecting a answer are given.
P a g e 8 7
c) Scenario Student has to lodge a
complaint/suggestion.
Interface Requirement The student can do so by giving the details
such as the subject and the person to whom
the complaint/suggestion has to be address
and an text box for entering the
Complaint/suggestion
d) Scenario Student needs project/seminar information
Interface Requirement The student will be given an interface where
he can enter the platform or field or the title of
the project/seminar.
e) Scenario Student needs alumni information
Interface Requirement The student will be given an interface where
he can enter either the name of the company
or the name and year of passing out of the
alumni.
f) Scenario Student has to answer to quiz question.
Interface Requirement An user interface with the question and
options for selecting a answer are given.
Actor: College management
P a g e 8 7
a) Scenario Management wants to poll a question.
Interface Requirement An user interface to enter a question and
duration after which they need the results is
provided.
b) Scenario Placement officer wants to send a notice.
Interface Requirement An user interface for entering the notice
and selecting the group of students to
whom the notice is intended, is
provided.
Non-Functional Requirements
CompatibilityThe SMS service that is provided is compatible with the java enabled mobile
cellular phones.
Performance The server should be able to handle many requests at the same time.
This SMS service is dependent on the existing messaging service provided by
the different service providers hence the performance may decrease due to
the delays in the network.
On an average the server can send/receive 50 SMS per minute.
ScalabilityThe application is scalable in the sense that a new service can be added
without affecting the available service.
There are provisions to use an existing feature in a service in the new service.
P a g e 8 7
FlexibilityThe application is flexible such that the norms and rules of a particular
institution can be easily incorporated whenever required.
P a g e 8 7
6. SYSTEM ANALYSIS
P a g e 8 7
SYSTEM ANALYSIS
6.1 EXISTING SYSTEM
The Existing system for BTCC is a manual process. Taking existing system in
to consideration, we can find that the Student has to interact with the Office in
person, brief on the requirements they expect and so on. All these require more time
and labor. The data collected may be inconsistent, redundant and getting in touch
with a remote Student will become impossible.
More over there would happen lack of co-ordination and follow-ups. As the
system is manual, there are many chances for it to procure more errors. There may
be chances to happen selection process to occur at more than one place at a time,
with regard to the existing system it would be hilarious to maintain records on venue,
batches etc.
There are sections, which are restricted to be accessed by a specific user of
Activity Management Systems. That is some of the areas, which managers access
would be very confidential and it is not allowed to be accessed by users or
employees. If the system is manual it would be tedious to implement this separation.
This section deals with the concept of system analysis, which is the primary
phase of the software development. The purpose is to identify the new system and
establish what the new system is to accomplish. System analysis is an important
activity that takes place when new system is being build.
It is the central whole of system development and it includes gathering
necessary data and developing a plan to the new system.
It is not an easy task because many people need to be satisfied and many
conflicts resolved. System analysis should be creative and imaginative in producing
new solutions to meet the user requirements.
6.2 LIMITATION OF THE EXISTING SYSTEM
P a g e 8 7
The existing system has the following problems:
Requires many departments to handle variety of tasks.
Involves lot of paper work.
No proper assignment of responsibilities would be there.
No electronic workflow, processing and approvals.
No automation and centralization of records.
Low and dragging access to records and details on employees.
New changes cannot be easily implemented.
Loss of records is probable to occur, as it is paper works.
Difficulty in searching the records as no serialization is involved.
Accumulation of records as organization extends.
Becomes more complex as task becomes more functional.
Difficulty in establishing and developing organizational capabilities of
coordination, commitment and competence.
Incomplete alignment of various functions.
Inability in understanding the benefits of increased organizational and
managerial effectiveness.
6.3 PROPOSED SYSTEM
The proposed system for BTCC is fully an automated one using Wireless
Android. In the proposed system, the Student online can Register the details and
requirements put forward by them. Online registration is also possible with this the
proposed system. As the proposed system is a centralized one, redundancy can be
avoided; moreover the coordination of different departments becomes much easier.
Above all the system provides high security for all its data. The proposed
system is mainly required for the listed as:
Easy updating of information
Provides online registration facility
Status of processing can be verified and identified at any stage of process
Efficient allocation of resources
P a g e 8 7
Ensures timeline management
The proposed system bridges this gap between the end-users and
the contrivance planning managers by providing a centralized control over the
entire system. The different departments utilize the system for sequencing the
different processes that are isolated apart. In the proposed system Employee Self
Service will be available which allows employees to manage their own personal
and benefit information. The payroll system included is used to compute, certify
and create employee pay and disburse money.
Benefits of proposed system:
Improve business practices and streamline operations.
Reduce the need for departmental system.
Provide a single point of entry for information.
Provide electronic workflow, processing’s and approvals.
Automate audits and edits, and centralize rules administration.
Improve information access at the employee, user and administrative levels.
Provides new functionality.
Entry-level users have been provided with the facility to access and complete
online forms.
Automatic review of plans, policies and eligibility requirements.
Automatic identification of taxable wages.
The time keeping function included in the proposed system will supports the
capture of information based on an employee’s work schedule.
The Leave Management module maintains balances for leave benefits and
balances.
Non-technical users will be able to create and retrieve contrivance planning
management reports.
Electronic routing and approvals of attendance can be implemented.
Access and ability to change personal information such as contact address,
email address etc
P a g e 8 7
6.4 FEASIBILITY STUDY
It is necessary and prudent to evaluate the feasibility of the project at the earliest
possible time. There may be different ways of checking whether system is feasible or
not. The following feasibility studies were performed to gauge the feasibility of the
system.
Operational feasibility: In this test, the operational scope of the system is checked. The system
under consideration should have enough operational reach. It is observed that the
proposed system is very user friendly and since the system is built with enough help,
even persons with little knowledge of Windows can find the system very easy.
Technical feasibility: This test includes a study of function; performance and constraints that may
affect the ability to achieve an acceptable system. This test begins with an assessment
of the technical viability of the proposed system. One of the main fusers to be
accessed is the need of various kinds of resources for the successful implementation for
the proposed system.
Economical feasibility: An evaluation of development cost weighted against the ultimate income or
benefit derived from the development of the proposed system is made. Care must be
taken that incurred in the development of the proposed of the system should not exceed
from the system. The income can be in terms of money or goodwill, since the software
brings in both, the system is highly viable.
P a g e 8 7
7. SYSTEM DESIGN
System design provides an overall understanding and provides a detail procedural flow
of information. System design goes through two phases of development.
P a g e 8 7
SYSTEM DESIGN
Logical design
Physical design
Input design
A data flow diagram shows the logical flow of information within the system. It
describes the various sources of input, output, database and the procedure’s
needed to meet the end user’s requirements.
Logical design
Logic design of an information system is analogous to an engineering blue print
of an automobile. It outlines the major processes and how they are related to each
other. The system is been designed based on various users’ requirements. The
various inputs, outputs and databases are designed in this phase. In the logic design
the various sources of input needed to build the system are analyzed and the
databases are all pre-planned.
Physical design
Physical design is the output design, which is the most important feature of the
information system. When the output is not of good quality then the user will be
averse to use the new system. There are various types of output. The term “output”
in any information system may mean either printer or displayed information. So
during the design of the output careful investigation was made as to what type or
form or output is been expected from the system as to satisfy the end user.
Input design
The input design is the link that ties the information system into the user’s world.
Input design specifies what type of data is required to enter the system for
processing. Input is been decided based on the user requirements.
P a g e 8 7
Objectives of input design.
Five objectives of designing input are
Controlling the amount of input required.
Avoid delay.
Avoiding errors in data.
Avoiding extra steps.
Keeping the process simple.
Input design is aimed at reducing the chances of mistakes of errors. As human
beings are prone to errors there is always the possibility of occurrence of chance of
errors. Adequate validation checks are incorporated to ensure error free data
storage.
P a g e 8 7
7.1 SYSTEM ARCHITECTURE DIAGRAM
…………
FIG: system architecture
7.2 CONTEXT DIAGRAM
P a g e 8 7
ISDN TOWER
MOBILE-1 MOBILE-2 MOBILE-3 MOBILE-N
LOGIN
OPERATIONS
MAIN OPERATIONS
PROJECTS/SEMINARS
ALUMNI INFO COMPLENT/SUGGESTIONS
SEND ANS TO POLL
PLACEMENTDETAILS
SUB OPERATIONS
1. TOPIC NAME
2. PLATFORM
ENTER THE COMPANYANDPASSOUT YEAR
1. STAFF2. LIBRARY3. CANTEEN4. CAMPUS
ENTER THE QUESTION NO..
ENTER THE ANS
7.2 CONTEXT DIAGRAM
LOAD AND LOGIN RESPONSE UPDATE INFORMATION
LOGIN PROVIDE COMPLANTS/ INFORMATION SUGGESTION
P a g e 8 7
ADMINISTRATOR
COLLEGE INFORMATION
STUDENTS
7.3 TOP LEVEL DFD
Data Flow Diagram:
A Data Flow Diagram [DFD] is also known as “Bubble7Chart” is used to
clarify system requirement s and identifying major transformation that all become
program in system design
Symbols used in DFD
P a g e 8 7
P a g e 8 7
P a g e 8 7
DETAIL DESIGN
8.DETAIL DESIGN
8.1 DATABASE DESIGN
The data design transforms the information domain model created during
analysis into the table structures that will be required to implement the software’s
database. The data objects and relationships defined in the entity relationship diagram
and the detailed data content depicted in the data dictionary provided the basis for the
data design activity.
Login TableThe Login table. This table is designed to store the basic details of the user when
he/she initially signs up.
Login
Field Name Data Type Constraints
UserName Varchar(20) Primary Key
Password Varchar(10) Not Null
Admin TableThe Admin table is the master table with Admin-id as the Primary Key. This table is
designed to store the basic details of the user when he/she initially signs up.
Admin
Field Name Data Type Constraints
Admin-id Varchar(20) Primary Key
Name Varchar(15) Not Null
P a g e 8 7
Password Varchar(10) Not Null
Server Table
Server
Field Name Data Type Constraints
Server-id Varchar(20) Primary Key
Name Varchar(15) Not Null
Student Table
Student
Field Name Data Type Constraints
s-id Varchar(20) Primary Key
sName Varchar(15) Not Null
Usn Varchar(10) Not Null
Address Varchar(20) Not Null
Contactno int(20) Null
Alumini Table
Alumini
Field Name Data Type Constraints
s-id Varchar(20) Primary Key
sName Varchar(15) Not Null
Yearofpassing Varchar(10) Not Null
Email-id Varchar(20) Not Null
Contactno int(20) Null
P a g e 8 7
Placement Table
Placement
Field Name Data Type Constraints
Companyname Varchar(20) Primary Key
Cutoff int(3) Not Null
dateofvalidation Varchar(10) Not Null
Backlogs Varchar(20) Not Null
Venue Varchar(10) Not Null
Project/seminar Table
Project/seminar
Field Name Data Type Constraints
Sname Varchar(20) Not Null
Usn Varchar(20) Primary Key
P-title Varchar(10) Not Null
Date Date Not Null
Time int(5) Not Null
Platform Varchar(10) Null
P a g e 8 7
Complaints/Suggestion table
Complaints/Suggestion
Field Name Data Type Constraints
To Varchar(10) Not Null
Email Varchar(20) Not null
Complaints Varchar(20) Not Null
Subject Varchar(20) Not Null
Polling table
Polling
Field Name Data Type Constraints
Id Varchar(10) Primary key
Answer Varchar(10) Not null
Category Varchar(20) Not Null
P a g e 8 7
8.2 EXPLANATION NORMALIZATION
In the field of relational database design, normalization is a systematic way of
ensuring that a database structure is suitable for general-purpose querying and free of
certain undesirable characteristics—insertion, update, and deletion anomalies—that
could lead to a loss of data integrity.
Fourth normal form (4NF) is a Normal formused in database normalization .
Introduced by Ronald Fagin in 1977, 4NF is the next level of normalization after Boyce-
coded norma form (BCNF). Whereas the second,third and Boyce-coded normal forms
are concerned with functional dependencies, 4NF is concerned with a more general
type of dependency known as a multivalued dependency . A table is in 4NF if and only
if, for every one of its non-trivial multivalued dependencies X →→ Y, X is a super key—
that is, X is either a candidate key or a superset thereof.
Multivalued dependencies
If the column headings in a relational database table are divided into three disjoint
groupings X, Y, and Z, then, in the context of a particular row, we can refer to the data
beneath each group of headings as x, y, and z respectively. A multivalued dependency
X →→ Y signifies that if we choose any x actually occurring in the table (call this choice
xc), and compile a list of all the xcyz combinations that occur in the table, we will find that
xc is associated with the same y entries regardless of z.
A trivial multivalued dependency X →→ Y is one in which Y consists of all columns
not belonging to X. That is, a subset of attributes in a table has a trivial multivalued
dependency on the remaining subset of attributes.
A functional dependency is a special case of multivalued dependency. In a functional
dependency X → Y, every x determines exactly one y, never more than one.
P a g e 8 7
8.3 TABLESalumini
name yearofpassout phno email compnamesridhar 2004 9902148154 [email protected] honeywellaravinda 2000 9902148154 [email protected] wiptrochethan 2006 9902148154 [email protected] infosisprabhith 1999 9902148154 [email protected] capgemini
complaintsto email complaints subject
Principal [email protected] student should study well staffadmin [email protected] nothing staff
loginusername password Categoryadmin admin Administratorsridhara 1234 Studentaravinda prateek Parentprabhith aaa Studentpraveen praveen Student
placementnoticecompname cutoff date time backlogs venuePrateek 60 01/30/2007 10.30 no PlacementOfficeInfosys 85 10/12/2007 10:00 1 seminar hallInfosys 65 02/20/2001 10:00 0 Bangalore
P a g e 8 7
pollid answer category2 good student1 yes parent3 no parent1 yes student
Seminarsname usn ptitle semdate time platform
sridhara 23 MobileCampus 01/29/2007 10.30 Javaaravinda 999 os 4/05/2007 10:00 netvajida 1999 BT Campus 02/15/2001 11:15 JAVA
studentstudent name usn semester degreesridhara 23 2 mcaaravinda 999 8 bevajida 1999 8 BEvajida 1999 BE mca
studregsname
pword rdate us
n padd permadd
rpnumber mobno degr
eedept
semester emailid
sriahara
1234 07/27/1983
23 Prateek
Prateek
2222222222
9902148154
B.E EEE
college
1234 07/27/1983
23 Prateek
Prateek
2222222222
9902148154
B.E EEE
aravinda
aaa 12/12/2000
999
dollars dollars 1234567894
9902148154
BE CSE
praveen
praveen
12/12/2006
888
bangalore
bangalore
9876544321
9902148154
be ise 8 [email protected]
Vajida
1234 01/01/1999
1999
blr mlr 154666656
9902148154
BE CSE
P a g e 8 7
studregsname
pword rdate us
n padd permadd
rpnumber mobno degr
eedept
semester emailid
nafeesa
1234 07/10/1999
1998
hpt hpt 123456 9902148154
BE IS 8 [email protected]
8.4 ER DIAGRAM
It deals with identifying various entities involved in the designed system and
establishes the relationships among them.
An Entity relationship Diagram is a data modeling technique that creates a
graphical representation of the entities and the relationships between entities, with
information
EntityAn entity is an object or concept about
which you want to store information.
Weak EntityA weak entity is dependent on another
entity to exist.
Attribute Attribute are the properties or
characteristics of an entity
P a g e 8 7
Entity
Entity
Attribute
Key attributeA key attribute is the unique,
distinguishing characteristic of the entity.
For example an employee’s social
security number might be the employee’s
key attribute.
Multi-valued Attribute A Multi-valued attribute can have more
than one value. For example, an
employee entity can have multiple skill
values
Derived Attribute A derived attribute is based on another
attribute.
P a g e 8 7
Attribute
Attribute
DerivedAttribute
For example an employee’s monthly
salary is based on the employee’s
annual salary
Relationships Relationships illustrate how two entities
share information in the database
structure.
Weak RelationshipTo connect a weak entity with others, you
should use a weak relationship notation.
Entity-Relationship model is a high-level conceptual schema. ER model is
frequently used for the conceptual design of database applications. The diagrammatic
notation associated with the ER model is known as Entity-Relationship Diagram (ER
Diagram). The schema for a database application can be displayed by means of the
graphical notation known as ER diagrams.
P a g e 8 7
Relationship
WeakRelationship
ER diagram for college Android campus
P a g e 8 7
8.5 FUNCTIONAL LEVEL DFD’S
Login Module
Admin Module
Server Module
P a g e 8 7
LOGINCheckAuthenticationUsername & password
ADMIN
LOGINCheckauthenticationUsername & password
SERVER
SERVER ProvidesServices to
STUDENTS
Alumni Module
Complaint Suggestion
Library
Student Complain/Suggestion
Admin
Admin View student details
Student
P a g e 8 7
ADMINMaintains
ALUMINI STUDENTS DETAILS
STUDENTS
Read by
Polling
8.6 ACTIVITY DIAGRAM
Admin Polling Question
Student
Read
P a g e 8 7
Accept content from server admin
Detect the Bluetooth devices
Attempt to push the content into detected device
Send content to device
Reject
accept
Fig. No.: 7.5 Activity diagram (server side)
P a g e 8 7
Establish connection with server
Recieve content and display
Fig. No.: 7.6 Activity diagram (Client side)
8.7 CLASS DIAGRAM
P a g e 8 7
8.8 SEQUENCE DIAGRAM
P a g e 8 7
A sequence diagram represent the sequence and interaction of a given use case
or scenario. Sequence diagrams are among the most popular UML diagram and, and if
used with an object module or class diagram, can capture most of the information about
the system. Most object-to-object interactions and operations are considered event, and
event include signals, input, decision, interrupt, transitions and action to or from user or
external devices.
A sequence diagram of Students is interaction with the system, administrator and
employer. The arrow lines are representing the sequence of action performed by the
jobseeker.
8.9 DEPLOYMENT DIAGRAM
P a g e 8 7
P a g e 8 7
8.10 COMPONENT DIAGRAM
P a g e 8 7
P a g e 8 7
IMPLEMENTATION
9. IMPLEMENTATIONImplementation is the stage of the project where the theoretical design is turned
into a working system. At this stage the main work load, the greatest upheaval and the
major impact on the existing system shifts to the user department. If the implementation
is not carefully planned a controlled it can cause chaos and confusion.
Implementation includes all those activities that take place to convert from the old
system to the new one. The new system may be totally new, replacing an existing
manual or automated system or it may be a major modification to an existing system.
Proper implementation is essential to provide a reliable system to meet the organization
requirements. Successful implementation may not guarantee improvement in the
organization using the new system, but improper installation will prevent it.
The process of putting the developed system in actual use is called system
implementation. This includes all those activities that take place to convert from the old
system the new system. The system can be implemented only after thorough testing is
done and if it is found to be working according to the specifications. The system
personnel check the feasibility of the system.
The most crucial stage is achieving a new successful system and giving
confidence on the new system for the user that it will work efficiently and effectively. It
involves careful planning, investigation of the current system and it constraints on
implementation, design of methods to achieve the changeover. The more complex the
system being implemented, the more involved will be the system analysis the design
effort required just for implementation. The system implementation has three main
aspects. They are education and training, system testing and changeover.
The implementation stage involves fallowing tasks.
Careful planning.
Investigation of system and constraints.
Design of methods to achieve the changeover.
Training of the staff in the changeover phase.
P a g e 8 7
Evaluation of the changeover method.
The method of implementation and the time scale to be adopted are found
out initially. Next the system is tested properly and the same time users.
Conversion Conversion is the process of changing from the old system to the new or
modified one. Conversion should be accomplished quickly as delays and long
conversion periods cause frustration and the task of all involved including the analyst
and user becomes more difficult.
Conversion Plan This plan should be formulated in consultation with the users. The
conversion plan includes a description of all activities that must occur to
implement the new system and put it into operation. This includes identification of
people responsible and timetable for each activity that is to be carried out.
During the planning of conversion, the analyst should form a list containing
all tasks including the fallowing:-
List all file for conversion.
Identity all data required to build new file conversion.
Identity all controls to be used during conversion.
Verify conversion schedule.
P a g e 8 7
P a g e 8 7
TESTING
9. TESTING
SYSTEM TESTING:
The performance target is to produce a quality product with a
performance that is competitive in the market. This is going to be achieved by
first looking at the different areas that effect the performance of Qt Extended, on
actual devices, and then trying to measure these values to find out where
performance needs to be improved.
The focus areas are:
Binary sizes
Functional Performance
Application Startup times
Startup times
Memory usage
Testing Strategies:
Any software has to be tested with pre-planned strategies. As Roger
Pressman states, the preparation for testing should start as soon as the design of
the system starts. To carry out the testing in an efficient manner certain amount
of strategic planning has to be done. Any testing strategy must incorporate test
planning, test case design, test execution and the resultant data collection and
evaluation.
BAMS was tested with the help of the following testing strategies:
VALIDATION TESTING
P a g e 8 7
The main aim of this testing is to verify that the software system does what it was
designed for.
The system was tested to ensure that the purpose of automating the system
“Automation System for Post Graduate Department” was fulfilled.
Alpha testing was carried out to ensure the validity of the system.
SYSTEM TESTINGThe idea of applying this testing strategy was to put the system to a series of
tests to ensure that it performed well and exactly same under all conditions.
The tests that the system was put to were:
.
Performance TestingThe tests were made on each form for its correctness of accepting the data and
storing the data into the respective tables in the desired form of data type. The
algorithms were tested with the test data first and then with the real data. The tests were
made for all types of constraints. The tests were done in presence of the user so that
he/she is familiar with the system that is going to be introduced. During the testing each
objective of the system was tested and found to be working correctly.
Test Plan:
The test plan corresponds to the process that are used to test the application.
For a Java application, the plan that was followed is, First to test the screens that to
relate to the user interface which would be dine with the help of the unit test cases that
are prepared during the actual coding of the Java pages. The test cases would cover all
the possible errors that can occur when the user interacts with the system along with
the result that is expected. The system follows unit testing in the initial stages followed
by Integration with various modules of the application and then by the actually hosting
on the testing server of the Organization. This exhaustive testing procedure ensures the
quality of the system.
Unit testing:
P a g e 8 7
Unit testing is a test (often automated) that validate that unit of source code
working properly. A unit is the smallest testable part of an application. In procedure
programming a unit may be an individual program, function, procedure etc., while in
object-oriented programming the smallest units a method, which may belong to a
base/super class, abstract class or derived/child class.
Ideally each test case is independent from the others; Unit testing is typically
done by software developers to ensure that the code they have written meets software
requirements and behaves as the developer intended.
Integration testing: Integration testing (sometimes called integration and Testing, abbreviated
(I & T) is the phase of software testing in which individual software modules are
combined and tested as a group. It follows unit testing and precedes system testing.
Integration testing takes as its input modules that have been unit tested,
groups them in larger aggregates, applies tests defined in an integration test plan to
those aggregates, and delivers as its output the integrated system ready for system
testing.
Test Cases: During the development process as well as during the release phase, Test
Cases will be executed. The Test Cases are described in test documents which are
(depending on the license type) part of the source package. Each Test Case also
contains test specific criteria which decide upon Test Cases success of failure.
Test Case result
Each Test Case can have one of the following outcomes:
Passed: The Test Case is passed if the test specific test criteria are met;
Failed: This predicate is applicable if the test criteria are not met and a correction and/or workaround for the execution of the test cannot be given.
P a g e 8 7
S.NO Input Expected Result Passed/Failed Actual result
1 Input user Id & password
It allow to proceed to next
passed Same as expected result
2 Submitting library file
It allow to submit when form is completely filled
Passed Same as expected result
3 Submitting library file
It not allow to submit when form is completely filled
Failed Error report
4 Submitting alumni file
It allow to submit when form is completely filled
passed Same as expected result
5 Submitting alumni file
It not allow to submit when form is completely filled
Failed Error report
6 Submitting polling file
It allow to submit when form is completely filled
Passed Same as expected result
7 Submitting registration file
It allow to submit when form is completely filled
Passed Same as expected result
8 Submitting registration file
It not allow to submit when form is completely
Failed Error report
P a g e 8 7
P a g e 8 7
CONCLUSION
10. CONCLUSION
During my study at KRAYONS, I gained good knowledge as well as experience
about the organization, its structure, working environment, function, business, vision
and their goals. The study has helped me to understand how an Organization functions
on a day-to-day basis and how each department functions together so all the
employees work together in attaching the companies goals and at the same time their
personal goals as well.
I had good learning experience in Software development development
department. It is the blend of software and development department. This is the most
creative department of KRAYONS. The learning out come of this department is how it
woks and handles its processes for better results. The coordination of Marketing
Department with other departments especially with product department for producing
the sample of the products required. Finally, the problems of the company related with
marketing and publicizing in market.
This project mainly developed for the college as well as students. The main
theme was instead of manual notice broad student can use the electronic flow of data.
Android is the suitable for the network in the college campus.
Now a days all the students are used Android supported mobile using this mobile
we can access the data.
Administrator have hole control of the project. Load and update the information to
database then students are access the data in mobile.
P a g e 8 7
P a g e 8 7
FUTURE ENHANCEMENT
11. FUTURE ENHANCEMENT
The application developed is designed in such a way that any further
enhancements can be done with ease. The system has the capability for easy
integration with other systems. New modules can be added to the existing system
with less effort
P a g e 8 7
P a g e 8 7
ANNEXURE
12. ANNEXURE
A poorly designed interface will disappoint the potential user. A well-designed
interface improves the user perception of the content or services provided by the
system. It describes how the software communicates within itself, with systems that
interoperate with it, and with the humans who use it. Control Flow Diagrams (CFD)
provides the information required for interface design. Interface design for each module
is given below –
Admin form
P a g e 8 7
Student Registration
P a g e 8 7
After Clicking the “Launch” Button we will get the next screen as shown:
P a g e 8 7
After Selecting the “Login” Option from List we will get the login screen as shown:
After Login Checking, if the user is valid then the server will send the response as
“Valid User” Otherwise as “Invalid User”.
If the user is “Valid User” then the following screen is shown:
P a g e 8 7
After Selecting the Project/Seminar Option from the Mobile then Click the “Select” Button & the students can get details of that either by giving platform or topic name.
Then we get details like this as shown in next screen:
In Alumini option, by entering passout year or comp name, we can get list of alumi’s and
also their complete details.
P a g e 8 7
In Complaints/Suggestions Options the Student can select any one of the option and
post a complaints & message will be display on alert.
In Polling Option, the Students can send a answer for polling question by mentioning
qno & message will be display on alert.
P a g e 8 7
In Placement Option, the Student can get to know about his placement by giving his usn
& the message will be display on next screen by pressing “OK” Button which is as
shown below:
P a g e 8 7
BIBLIOGRAPHY
SLNO BOOKS AUTHORPUBLICATION
1 The Complete
Reference HTML
Kenny Chu
2 J2EE: The Complete
Reference
James Keogh & Jim.
Keogh
3 Java 2 Complete
Reference
(Tata McGraw Hill)
Herbert Schildt
4 Java Server Pages
Fast
& Easy Web
Development
Aneesha Bakharia
5 J2EE 1.4 Bible
(WILEY)
McGovern, et al.
P a g e 8 7
Appendix-A
ORGANIZATION PROFILESyslog has been in the web field for over 2 years, and we have earned the loyalty
and trust of customers spread across various fields and geographies with our quality,
timeliness and customer service.
We act as a part of our customers team, rather than just another vendor and add
value in various capacities:
Quality: Syslog have won the satisfaction and trust of our customers. We have the people,
the equipment and the attitude to much and exceed the quality requirements as well
as the timelines required by our clients.
Price-Performance Ratio: We firmly believe that the most important thing for a customer is the price-
performance ratio rather than just the price. The quality of the product, the value-
added through our interactions with the customer, the suitability of the end products
to its purpose, and the impression that the product makes on the end-user, all of
these are important considerations. As is customer service and transparency of the
entire process.
P a g e 8 7
We are a one-stop that can handle all your requirements from web development,
printing, interactive. We also handle all your needs from broachers, catalogs,
calendars, packing cartons, labels, gift boxes,seo,
e-commerce sites, shopping cart etc. You have a single point contact who interacts
with you right from the estimation stage to the time of delivery.
Appendix-B
TOOLS DESCRIPTION
Introduction to J2EE:
The Java 2 Platform, Enterprise Edition (J2EE), has rapidly established a new
model for developing distributed applications. This model is based on well-defined
components that can automatically take advantage of sophisticated platform services.
These components can be developed according to standard guidelines, combined into
applications, deployed on a variety of compatible server products, and reused for
maximum programmer productivity. This model is intended to both standardize and
simplify the kind of distributed applications required for today’s networked information
economy.
The success of the J2EE platform is in large part due to the success of this
model. Today, all leading application server and enterprise information system vendors
have adopted the J2EE standard and introduced products based on the J2EE platform
specification. Application architects and developers have come to rely on the J2EE
standard to help them solve the various design challenges that face them day-to-day.
P a g e 8 7
While the fundamentals of the J2EE platform are relatively easy to describe, mapping
these features to architectural issues in the design of distributed applications requires
deeper understanding and careful decision-making.
Although the J2EE standard offers a simplified programming model compared to
previous alternatives, the platform isn’t monolithic. Certain features require that
architects and developers weigh their options before making design decisions and be
prepared to re-think those decisions as they uncover new challenges. That, in turn,
requires some understanding of the design motivations behind the platform and of the
trade-offs involved in applying specific design features to a specific architectural
problem.
J2EE Platform Benefits
With features designed to expedite the process of developing distributed applications,
the J2EE platform offers several benefits:
Simplified architecture and development
Freedom of choice in servers, tools, and components
Integration with existing information systems
Scalability to meet demand variations
Flexible security model
Simplified Architecture and Development
The J2EE platform supports a simplified, component-based development
model. Because it is based on the Java programming language and the Java 2
Platform, Standard Edition (J2SETM platform), this model offers “Write-Once-Run-
Anywhere TM” portability, supported by any server product that conforms to the J2EE
standard. The component-based J2EE development model can enhance application
development productivity in a number of ways:
P a g e 8 7
Maps easily to application functionality—Component-based application models
map easily and flexibly to the functionality desired from an application. As the
examples presented throughout this book illustrate, the J2EE platform provides a
variety of ways to configure the architecture of an application, depending on such
things as client types required, level of access required to data sources, and other
considerations. Component-based design also simplifies application maintenance,
since components can be updated and replaced independently—new functionality can
be shimmed into existing applications simply by updating selected components.
Enables assembly- and deploy-time behaviors—Because of the high level of
service standardization, much of the code of a J2EE application can be generated
automatically by tools, with minimal developer intervention. In addition, components
can expect standard services to be available in the runtime environment and can
dynamically connect to other components by means of consistent interfaces. As a
result, many application behaviors can be configured at application assembly or
deployment time, without recoding. Component developers can communicate
requirements to application deployers through specific deployment descriptors and
settings. Tools can automate this process to further expedite development.
Supports division of labor—Components help divide the labor of application
development among specific skill sets, enabling each member of a development team
to focus on his or her ability. Web page authors can create JSP templates, Java
programming language coders can implement application behavior, domain experts
can develop business logic, and application developers and integrators can assemble
and deploy applications. This division of labor also expedites application maintenance.
For example, the user interface is the most dynamic part of many applications,
particularly on the Web. With the J2EE platform, Web page authors can tweak the look
and feel of JSP pages without programmer intervention. The J2EE specifications
define a number of roles, including application component provider, application
assembler, and application deployer.
P a g e 8 7
Integrating Existing Enterprise Information Systems-The J2EE platform,
together with the J2SE platform, includes a number of industry standard APIs for
accessing existing enterprise information systems. Basic access to these systems is
provided by the following APIs:
• The J2EE Connector architecture is the infrastructure for interacting with a variety of
Enterprise Information System types, including ERP, CRM, and other legacy systems.
• The JDBCTM API is used for accessing relational data from the Java programming
language.
• The Java Transaction API (JTA) is the API for managing and coordinating
transactions across heterogeneous enterprise information systems.
• The Java Naming and Directory Interface TM (JNDI) is the API for accessing
information in enterprise name and directory services.
• The Java Message Service (JMS) is the API for sending and receiving messages via
enterprise messaging systems such as IBM MQ Series and TIBCO Rendezvous. In
the J2EE platform version 1.3, message-driven beans provide a component-based
approach to encapsulating messaging functionality.
• The Java Mail TM API is used for sending and receiving e-mail.
• Java IDL provides the mechanism for calling CORBA services.
• Java APIs for XML provide support for integration with legacy systems and
applications, and for implementing Web services in the J2EE platform.
In addition, specialized access to enterprise resource planning and
mainframe systems such as IBM’s CICS and IMS is provided through the J2EE
Connector architecture. Since each of these systems is highly complex and
specialized, they require unique tools and support to ensure utmost simplicity to
application developers.
Choice of Servers, Tools, and Components
The J2EE standard and J2EE brand have created a huge marketplace for servers,
tools, and components. The J2EE brand on a server product ensures the consistent
level of service that is fundamental to the goals of the J2EE platform. At the same
time, J2EE standards ensure a lively marketplace for tools and components. Based on
P a g e 8 7
past experience and industry momentum, all leading enterprise software vendors are
expected to provide the marketplace for J2EE 1.3 products. The standardization and
branding of the J2EE platform provides many benefits, including:
• A range of server choices—Application development organizations can expect J2EE
branded platforms from a variety of vendors, providing a range of choices in hardware
platforms, operating systems, and server configurations. This ensures that businesses
get a choice of servers appropriate to their needs.
• Designed for tool support—Both enterprise beans and JSP page components are
designed to be manipulated by graphical development tools and to allow automating
many of the application development tasks traditionally requiring the ability to write
and debug code. Both J2EE server providers and third-party tool developers have
developed tools that conform to J2EE standards and support various application
development tasks and styles. Application developers have a choice of tools to
manipulate and assemble components, and individual team members may choose
tools that best suit their specific requirements.
• A marketplace for components—Component-based design ensures that many types
of behavior can be standardized, packaged, and reused by any J2EE application.
Component vendors will provide a variety of off-the-shelf component solutions,
including accounting beans, user interface templates, and even vertical market
functionality of interest in specific industries. Application architects get a choice of
standardized components to handle common or specialized tasks. The J2EE standard
and associated branding program ensures that solutions are compatible. By setting
the stage for freedom of choice, the J2EE platform makes it possible to develop with
confidence that the value of your investment will be protected.
Scales Easily-J2EE containers provide a mechanism that supports simplified
scaling of distributed applications, with no application development effort. Because
J2EE containers provide components with transaction support, database connections,
P a g e 8 7
life cycle management, and other features that influence performance, they can be
designed to provide scalability in these areas. For example, containers may pool
database connections, providing clients with quick, efficient access to data. Because
Containers may run on multiple systems, Web containers can automatically balance
load in response to fluctuating demand.
Simplified, Unified Security Model-The J2EE security model is designed to
support single sign on access to application services. Component developers can
specify the security requirements of a component at the method level to ensure that
only users with appropriate permissions can access specific data operations. While
both Enterprise JavaBeans technology and Java Servlet APIs provide
programmatic security control, the basic role-based security Mechanism (where
groups of users share specific permissions) is specified entirely at application
deployment time. This provides both greater flexibility and better security control.
Java Server Pages (JSP)
JSP is a dynamic scripting capability for web pages that allow Java as well
as a few special tags to be embedded into a web file (HTML/XML, etc). The suffix
traditionally ends with .jsp to indicate to the web server that the file is a JSP file. JSP is
a server side technology - you can't do any client side validation with it. JSP files
actually get compiled into Servlets.There other very powerful aspects that Java Server
Pages provides:
An object model: JSPs are Servlets and as such, they are able to participate
in delegation and inheritance models as well as all of the other OO things that are
available.
Servlets and JSP pages:
P a g e 8 7
JSP pages are focused around HTML (or XML) with Java codes and JSP
tags inside them. When a web server that has JSP support is asked for a JSP page, it
checks to see if it has already compiled the page into a servlet. Thus, JSP pages
become Servlets and are transformed into pure Java and then compiled, loaded into
the server and executed. Different JSP implementations do this in more or less
efficient ways.
Java Database Connectivity (JDBC)
Establishing a Connection with Database
The first thing you need to do is establish a connection with the DBMS you
want to use. This involves two steps:
(1) Loading the driver
(2) Making the connection.
Loading Drivers
Loading the driver or drivers you want to use is very simple and involves
just one line of code. If, for example, you want to use the JDBC-ODBC Bridge driver,
the following code will load it:
Class.forName ("sun.jdbc.odbc.JdbcOdbcDriver"); When you have loaded a driver, it is available for making a connection
with a DBMS.
Making the Connection
The second step in establishing a connection is to have the appropriate
driver connect to the DBMS. The following line of code illustrates the general idea:
Connection con = DriverManager.getConnection (URL,"MyLogin", "myPassword"); This step is also simple, with the hardest thing being what to supply for
URL. If you are using the JDBC-ODBC Bridge driver, the JDBC URL will start with
jdbc: odbc:
P a g e 8 7
Java Servlets
Servlets are generic extensions to Java-enabled servers. Their most
common use is to extend Web servers, providing very secure, portable, and easy to
use replacements for CGI. A Servlet is a dynamically loaded module that services
requests from a Web browser. It runs entirely inside the Java Virtual machine.
Because the Servlet is running on the server side, it does not depend on browser
compatibility.
Practical Applications
Servlets can be used for any number of Web-related applications. The
following are some of the most important applications.Developing e-commerce "store
fronts" will become one of the most common uses of Java Servlets. A Servlet can build
an online catalog based on the contents of a database. It can then present this catalog
to the customer using dynamic HTML. The customer can choose items and the Servlet
will carryall the related operations very efficiently.
Servlets can be used to deploy Web sites that open up large legacy
systems on the Internet. Many companies have massive amounts of data stored on
large mainframe systems.
When developing a distributed object application that will be deployed to
the web, we run into access issues. If we choose to use applets in our client browser,
we are only able to open a connection to the originating server, which might be behind
a firewall. If Servlets are employed, we can tunnel through the firewall using a Servlet
technology called HTTP Tunneling.
Reasons to use Java Servlets
Java Servlets are one of the most exciting new technologies. Servlets
solve many of the common problems we run into when using CGI and they have
proved to have a clear advantage over many of the other alternatives.
P a g e 8 7
Some of the advantages are:
Efficient
Persistent
Portable
Robust
Extensible
Secure
Widespread acceptance
The Java Servlet Architecture
Two packages make up the Servlet architecture: the javax.Servlet and
javax.Servlet.http. The javax.Servlet package contains the generic interfaces and
classes that are implemented and extended by all Servlets.
Session Tracking Session tracking is the capability of a server to maintain the current state of a
single client’s sequential requests. HTTP is a stateless protocol, which means that
each request is independent of the previous one. However in some applications, it is
necessary to save state information so that information can be collected from several
interactions between a browser and a server.
For example, an online video store must be able to determine each
visitor’s sequence of actions. Suppose a customer goes to your site to order a movie.
The first thing he does is look at the available titles. When he has found the title he is
interested in he makes his selection. The problem now is determining who made the
selection. Because each one of the client’s requests is independent of the previous
requests, we have no idea who actually made the final selection. We can solve this
problem using session tracking.
P a g e 8 7
A session can be created using get Session () method of
HttpServletRequest. An Http Session object is returned. The put Value(),get
Value(),getValueNames(),remove Value(),get Attribute(), set Attribute(),
getParameterValues() and getParameterNames() method of Http Session manage the
set of bindings that associates names with objects.
INTRODUCTION TO TOMCAT:
Apache Tomcat or Jakarta Tomcat or simply Tomcat is an open source
servlet container developed by the Apache Software Foundation (ASF). Tomcat
implements the Java Servlet and the JavaServerPages (JSP) specifications from Sun?
Microsystems, and provide a “pure Java” HTTP web server environment for java code
to run..
Tomcat should not be confused with the Apache web server, which is a C
implementation of an HTTP web server, these two web servers are not bundled
together. Apache Tomcat includes tools for configuration and management, but can
also be configured by editing XML configuration files.
The Jakarta Tomcat project has its origins in the earliest days of Java's
servlet technology. Servlets plug into special web servers, called servlet containers
(originally called servlet engines). Sun created the firstservlet container, called the Java
Web Server, which demonstrated the technology but wasn't terribly robust. Meanwhile,
the ASF folks created the JServ product, which was a servlet engine that integrated with
the Apache web server. In 1999, Sun donated their servlet container code to the ASF,
and the two projects were merged to create the Tomcat server. Today, Tomcat serves
as Sun's official reference implementation (RI), which means that Tomcat's first priority
is to be fully compliant with the Servlet and JSP specifications published by Sun. JSP
pages are simply an alternative, HTML-like way to write servlets. We will discuss all this
in more detail in the next chapter. A reference implementation also has the side benefit
of honing the specification. As developers seek to put in code that has been defined in
the specifications, problems in implementation requirements and conflicts within the
specifications are highlighted.
P a g e 8 7
A reference implementation is in principal completely specification-compliant and
therefore can be very valuable, especially for people who are using very advanced parts
of the specification. The reference implementation is available at the same time as the
public release of the specifications, which means that Tomcat is usually the first server
out there that provides the enhanced specification features when a new specification
version is completed. The first version of Tomcat was the 3.x series, and it served as
the reference implementation of the Servlet 2.2 and JSP 1.1 specifications. The Tomcat
3.x series was descended from the original code that Sun provided to the ASF in 1999.
In 2001, Tomcat 4.0 (codenamed Catalina) was released, and was a complete redesign
of the Tomcat architecture and had a new code base. The Tomcat 4.x series, which is
current as of this writing, is the reference implementation of the Servlet 2.3 and JSP 1.2
specifications. At the time of writing, the latest stable version is 4.0.4. Hints of
Tomcat 5.0 are on the horizon, as the new Servlet 2.4 and JSP 2.0 specifications are
nearing release and Tomcat 5.0 will need to implement those specifications.
Features:
Implements the Servlet 2.4 and JSP 2.0 specifications.
Reduced garbage collection, improved performance and scalability.
Native Windows and Unix wrappers for platform integration.
Faster JSP parsing.
P a g e 8 7
INTRODUCTION TO ANDROID:
MS ACCESS:
Microsoft Office Access, previously known as Microsoft Access, is a
relational database management system from Microsoft that combines the relational
Microsoft Jet Database Engine with a graphical user interface and software
development tools. It is a member of the 2007 Microsoft Office System.
Access can use data stored in Access/Jet, Microsoft SQL Server, Oracle, or
any ODBC-complaint data container (including MYSQL and PostgreSQL). Software
developers and data architects can use it to develop application software and non-
programmer “power users” can use it to build simple applications. It supports some
object-oriented techniques but falls short of being a fully object-oriented development
tool.
Access was also the name of a communications program from Microsoft, meant
to complete with ProComm and other programs. This proved a failure and was dropped.
Years later Microsoft reused the name for its database software.
Access version !.0 was released in November 1992, followed in May of 1993 by
an Access 1.1 release to improve compatibility with other Microsoft products.
Microsoft specified the minimum hardware requirements for Access v2.0:
P a g e 8 7
Microsoft Windows v3.0 with 4 MB of RAM required, 6 MB RAM recommended; 8 MB of
available hard disk space required, 14 MB hard disk space recommended. The product
was shipped on seven 1.44 MB diskettes. The manual shows a 1993 copyright date.
The software worked well with small recordsets but testing showed some circumstances
caused data corruption. For example, file sizes over 10 MB were problematic (note that
most hard disks were smaller than 500 MB at the time this was in wide use), and the
getting started manual warns about a number of circumstances where obsolete device
drivers or incorrect configurations can cause data loss. With the phasing out of
Windows 95, 98 and ME, improved network reliability, and Microsoft having released 8
service packs for the Jet Database Engine, the reliability of Access database has been
vastly improved.
Access’s initial codename was Cirus; the forms engine was called Ruby. This was
before Visual Basic – Bill Gates saw the prototypes and decided that the BASIC
language component should be co-developed as a separate expandable application, a
project called Thunder. The two projects were developed separately as the underlying
forms engines were incomplete with each other; however, these were merged together
again after VBA.
Uses: Microsoft has strongly recommended for the past decade that Jet
Database are inappropriate for basic web based applications hosted on Microsoft’s
Internet Information Services and utilizing Microsoft Active Server Pages.
Some professional application developers use Access for rapid application
development, especially for the creation of prototypes and standalone applications that
serve as tools for on-the-road salespeople.
Access applications generally do not scale well if data access is via a network,
but by moving an Access application to an Application Server such as Microsoft terminal
Services, the number of users that can be supported is substantially increased. Moving
P a g e 8 7
to an Application Server also has the benefit of allowing database use over a Wide Area
Network.
P a g e 8 7
