1. School Of Information Technology
Minor Project On
<Title Here>
In partial fulfillment for the award of the Bachelor of Engineering Degree of
the University Of Rajasthan, Jaipur.
Submitted to: Project Guide: Submitted By:
Ms. Manju Vyas <Guide Name> <Name, Branch>
(HOS, IT) <Designation> <Name, Branch>
JODHPUR ENGG COLLEGE AND RESEARCH CENTRE, BORANADA,
JODHPUR (RAJ).- 342001
JAN-2009
JODHPUR ENGG COLLEGE AND RESEARCH CENTRE
BORANADA, JODHPUR-342001

2. Affiliated to university of Rajasthan, Jaipur
BONAFIDE CERTIFICATE
This is to certify that the project (Minor) work entitled, “<Project Title>” submitted
by
<Name>,<Branch>
<Name>,<Branch>
<Name>,<Branch>
in partial fulfillment of the requirements of B.E./B.Tech in information Technology,
embodies the work done by them under my supervision.
Signature of the Guide Signature of HOD
Submitted for the Project Work Viva held on ______________.
Internal Examiner External Examiner
Format for your report:
Your report should follow the guidelines mentioned below or it will be summarily

3. Rejected.
General Guidelines:
- All the paragraph text should be in font: Times New Roman, Bold: false, Case: sentence
case, Size: 12, line spacing: normal, Align: Justify
- Main heading such as ABSTRACT, INTRODUCTION should be
in font: Times New Roman, Bold: true, Case: Upper case, Size: 16, Align: center
- Sub heading such as Project Objectives, Academic Objectives should be in
font: Times New Roman, Bold: false, Case: Title case, Size: 14, Align: left
- Entire Report should be in font: Times New Roman.
CONTENTS

4. ABSTRACT .....................................................................................................................................3
CONCLUSION.................................................................................................................................4
CONTENTS .....................................................................................................................................5
LIST OF TABLES............................................................................................................................6
LIST OF FIGURES ..........................................................................................................................7
1) INTRODUCTION.....................................................................................................................8
2) OBJECTIVES..........................................................................................................................9
2.1 PROJECT OBJECTIVES............................................................................................... 9
2.2 ACADEMIC OBJECTIVES.............................................................................................. 9
3) PROJECT OVERVIEW............................................................................................................10
3.3
OVERVIEW……………………………………………………………………………………..10
3.4 SDLC MODEL………………………………………………………………11
3.5 FEASIBILITY STUDY......................................................................................................12
3.6 PROJECT CHEDULING…………………………………………………………12
3.6.1 PERT/GHANTT CHART…………….………………………………………12
4) REQUIREMENT ANALYSIS ...................................................................................................11
4.1 SYSTEM / HARDWARE REQUIREMENTS ..................................................................11
4.2 SOFTWARE REQUIREMENTS......................................................................................11
4.3 FUNCTIONAL REQUIREMENTS....................................................................................11
4.3.1 USE CASE DIAGRAM (OPTIONAL)…………………………………..11
4.4 NON-FUNCTIONAL REQUIREMENTS .....................................................................12
5) APPLICATION DESIGN.......................................................................................................13
5.1 DESIGN OVERVIEW ................................................................................................ 13
5.2 DESIGN APPROACH................................................................................................ 14
5.3 DESIGN DESCRIPTIO.............................................................................................. 14
5.3.1 FLOW CHART………………………………………………………………………14
5.3.2 DATA FLOW DIAGRAM.................................................................................... 15
5.3.3 CONTROL FLOW DIAGRAM………………………………………………………..15
5.3.4 STATE TRANSITION DIAGRAM(OPTIONAL)....................................................15
5.3.5 UML DIAGRAM (OPTIONAL TO INCLUDE) ................................................... 15
5.4 DATABASE DESIGN............................................................. .................................... 15
5.4.1 ER DIAGRAM.................................................................................................. 15
5.4.2 TABLE RELATIONSHIP DIAGRAM(OPTIONAL)..................... .......................... 15
6) IMPLEMENTATION..............................................................................................................16
7) TESTING...............................................................................................................................17
8) FUTURE WORK ...................................................................................................................18
9) APPENDIX
APPENDIX I REFERENCES ..........................................................................................19
APPENDIX II PROJECT OUTPUT .................................................................................20
APPENDIX III CODE LISTINGS.....................................................................................21
NOTE: page numbers should be properly aligned.
SAMPLE REPORT

5. ABSTRACT

6. Design and develop a mobile phone application that will act as an interface for other
applications to connect to the Internet.

7. CONCLUSION
The mobile application to connect to the Internet is developed, and interfaced with other
applications to provide Internet access.
LIST OF TABLES

8. TABLE 1 DESIGN DETAILS ........................................................................................... 13

9. LIST OF FIGURES
FIGURE 1 MODULE DESIGN AND ORGANIZATION ......................................................... 13
FIGURE 2 DATABASE APPROACH ....................................................................................... 14
FIGURE 3 XML APPROACH .................................................................................................... 14

10. 1 INTRODUCTION
Internet is a large group of systems or networks connected across the world. Each
system or network provides access to all other systems or networks. The primary goal of
the Internet is information sharing.
Though we are able to access Internet all times we have to use a computer, it may be
our own or in some other café. But the requirement of the Internet access at anytime,
anywhere arises. To provide the anytime, anywhere Internet access in the move, we
have to enable the Internet access from the mobile phones itself. So the application that
provides the access to the Internet is need to be developed and deployed to the mobile
phones to provide the same.

11. 2 OBJECTIVES
2.1 Project Objectives
Develop an application for mobile phones, which enables the user to connect and
access the Internet server.
Etc .
2.2 Academic Objectives
Study Microsoft Visual studio .NET mobile toolkit.
Learn the process of the mobile application development.
Etc
3 PROJECT OVERVIEW

12. There are three modules in the project, they are
• Web browser module
• WAP module
• Data compression and decompression module
The web browser module is responsible for providing the web access through URL. It
supplies necessary requests/commands to the Internet server, and also handles the
replies/data from the server
The WAP module is responsible for providing wire less access and data transfer
between the server and mobile phones. It takes care of all the technical details or
parameters associated with transmission and reception of all wireless data.
The data compression and decompression module is responsible for compressing the
data, which is to be transferred, and decompressing the data, which is received. The
purpose of this compression and decompression is to reduce the amount of data
transfer.
4 REQUIREMENT ANALYSIS

13. 4.1 System / Hardware requirements
1. WAP Enabled Mobile Phone
4.2 Software requirements
None
4.3 Functional requirements
- Explain the functional requirements using the use case diagrams
- Refer the sample diagram
- Refer OOAD Ali Brahmi book and write use case scenarios
4.4 Non-functional requirements
The non-functional requirements are
• Good response time
• Reliable communication
5 APPLICATION DESIGN

14. 6 IMPLEMENTATION

15. 7 TESTING

16. 8 FUTURE WORK

17. 9 APPENDIX - I - REFERENCES

18. 10 APPENDIX - II - RESULTS

19. 11 APPENDIX - III - CODE LISTINGS

20. 11.1 Web browser module Wbrowse.aspx
Private sub Page_Load()
Initilization
End Sub
Etc .
11.2 Compression/Decompression module CompDecomp.aspx
Private sub Page_Load()
Initilization
End Sub
Etc ..