Project Report Sample
Project Report Sample
CERTIFICATE
This is to certify that the following students:
Name of students Roll No. Seat No.
1.
2.
3.
4.
(Project Name)
In the partial fulfillment of requirement as
prescribed by the B.T.E. Maharashtra State,
in the year 2005-2006.
INTERNAL EXTERNAL
EXAMINER EXAMINER
1
ACKNOWLEDGEMENT
Participates
2
INDEX
SERIAL PAGE
NO. NO.
CHAPTER NAME
1. INTRODUCTION
Introduction to Project
Introduction to Language
SYSTEM ANALYSIS
2. SYSTEM DESIGN
SDLC (System Development Life
3. Cycle)
DFD (Data Flow Diagram)
File Detail
Design Specification &
Requirement
IMPLEMENTAT
ION
7
Input Consideration
4.
Output Consideration
Processing Consideration
Testing & Installation
FEASIBILITY STUDY
Time Feasibility
5. Software Availability
Cost Effective
Sufficient Information
FUTURE DEVELOPMENT
Application Of Project
Future Development Of Project
6. BIBLIOGRAPHY
7.
3
4
Chapter 1
INTRODUCTION
5
INTRODUCTION OF PROJECT
NEED OF PROJECT
6
Features of Visual Basic:
⇒In Visual Basic you can quickly design the visual elements of
any new programming project.
7
The Programming Process:
8
testing. The debugger is an interactive monitoring system that you
turn on and off inside Visual Basic that helps you locate statements
that may contain bugs.
♦Programming Maintenance
Apart from the bugs, the programmer has to maintain the program
he /she has created. Program Maintainance is a term used for the
updating of a program after the program after the program is put
into use. This updating may be a result of the users request or a
change in the way the program needs to operate.
♦Project
9
It limits the application take on a window Explorer- like interface
with topic summaries in the left window an details for a selected
topic in the right pane.
Chapter 2
SYSTEM
ANALYSIS
10
Why is System Analysis Necessary?
11
The system analyst is the person who guides the analysis,
design and implementation and maintenance of a given system. In
performing these four tasks, the analyst must always match the
information system objectives with the goals of organization.
3. The system analyst must be a able to find out the details about
the system itself. To do this, the analyst will have to look at such
things as forms (input, output formats), data used by the
organization.
1. Change agent
2. Monitor
3. Architect
4. Psychologist
12
5. Sales person
6. Motivator
7. Politician.
Change agent:
The analyst finds out why user is not satisfied with the
not present system he is using. What are the drawbacks of
pitfall in the present system, that user wants to remove by
replacing it with new system.
Architect:
13
building. A system analyst also creates several plans and
develops or builds system according to that plan.
Psychologist:
Sales person:
Motivator:
Politician:
14
successful system analyst. While designing a new system, the
analyst should not only think about the technical side but also
keeping good relations, good control and good influences on
the people with and around him.
Chapter 3
SYSTEM DESIGN
15
3.1 SDLC (System Development Life Cycle)
Feasibility study: -
16
Feasibility study can be understood by giving the
answer/solution of these their requirements: -
Answer: -
Our new system covers all the basic of the user for e.g.: as
mentioned earlier that our database is Ms access, which does not
have any limitation to store data. And one of the major
advantages of new system is that it avoids redundancy means
there is no repetition of the data.
Answer: -
In the existing system the opera or has to learn all the
operation of the commands. Whichever is coming in light while
operating a particular form then one help called tool tip will
come if the mouse point comes on corresponding fields of
particular form.
17
The new system is well fitted in the office working
condition, because it covers all basic needs of the user working
in the office. It is less tedious and less time consuming.
System analysis: -
System design: -
Output: -
Input: -
18
are required for the system and prepare input format to give input
to the system according to the requirement. Considering the input
to the front end from the user we use the user-friendly visual basic
software so that the user can easily enter the data. In case operator
gate confuse then the by moving the cursor pointer on the
corresponding field data user can get one tool tip box as example.
Problem
Definition
User
Requirement
Feasibility
study
System Verify
analysis System model
Detailed system objectives
Verify
Broad System
design Design Validation
Verify Validation
Verify Broad
Develop- design
system implementation
ment
Broad
Impleme design
ntation
Validation
Working system
19
3.2 DATA FLOW DIAGRAM
20
1-processes
2-data stores
3-data flows
4-external entities
21
22
23
3.4 DESIGN SPECIFICATIONS & REQUIREMENT
24
Software & Hardware Specification: -
Specification must reflect the actual application to be
handled by the system and include system objective, flowchart,
input-output requirement, file structure and cost.
1) Reliability: -
Software reliability brings up the concept of
modularity. A package with a high degree of modularity has the
capacity to operate in many machine configurations and perhaps
across manufacture product lines.
This software with high potential can work or can be
operated in P1 based configuration computers.
2) Functionality: -
It is a definition of the facilities, performance and other
factors that the user requires in the finished product.
This software provides the facility of having the
complete infrastructure of the house, etc. The performance of the
software includes the flexibility of the software.
3) Flexibility: -
One feature of the flexibility is adaptability, which is of
the ease of extending the product. In the field of flexibility, the
software covers all factors to be considered. For example: knowing
the astrological sign, KUA number, and etc. of a particular person.
4) Usability: -
The points to be considered while thinking of usability
are portability and understandability.
While designing this software, we always try to make it
more portable, should not consume more space as well. As we are
using HTML s a front-end, which is very user friendly, so it scores
full marks in understanding.
5) Security: -
25
Security control and access of software or data file
should be maintained in this software.
6) Capacity: -
The software, when under development should be
developed in such a way that the number of files, data elements,
etc. and size of each of them should be considered. It should not
affect the users system, so that he/she can make up gradations or
degradations in the system hardware or software.
7) Performance: -
The language, in which the package is developed,
should be well known or say should be aware to the programmers.
The operating system may also affect its performance. These both
factors are important for consideration. This software should be
economical for buying and should be user friendly.
In our project, we have considered all above factors and
developed such a project hat can run in all environments but may
be supported by Apache server.
HARDWARE REQUIREMENTS: -
Min. 16 MB RAM.
Min 1 MB of Display Card.
Min. 100 MB free space on the Hard Disk.
At least Color Monitors.
SOFTWARE REQUIREMNETS: -
VISUAL BASIC
MS ACCESS
MINIMUM WINDOWS98AND ABOVE.
26
After the broad stages or modules for a system have been
define did this necessary to move to preparation of detailed
programming specification. The programs or modules are defined
according to the functions they perform, not by the size of the
program. The breakdown of programs into smaller modules makes
it easier to debug a system and modify it. Program Specification
must be developed fro each module, which involve program name,
purpose for the program, owner of the project and general
information about the program.
Program Analysis
Outlining program structure
Algorithm development
Selection of control structure
PROBLEM ANALYSIS: -
27
Before we are thinking of solution procedure to problem we
must fully understand the nature of the problem and what we want
to the program to do. Without the complementation the definition of
the problem at hand program design might turn into a hit is miss
approach. We must carefully decide following at this stage:
1) What kind of data will go in?
2) What kinds of outputs are needed?
3) What are the constraints and condition under which program
has to operate?
ALGORITHM DEVELOPEMENT: -
CONTROL STRUCTURES: -
28
A complex solution procedure may involve large number of
control statements to direct the flow of execution. In such situation
indiscriminate use of control statements such as go to may lead to
understand and incomprehensible programs. It has been
demonstrated that any algorithm can be structure denotes three
basic control structures namely, sequence structure, selection
structure and lopping structures.
PROGRAM CODING: -
29
(4)Use simple conditions test, if necessary break complicated
condition into simple condition.
(5)Use parenthesis to clarify logical and arithmetic expressions.
(6)Use space, whenever possible, to improve readability.
SUMMARY:
This chapter provides use with detail of program
design, analyses, algorithm development, and program coding
statement, constructional, internal documentation and different
input/output formats which are of importance, enough to be
considered before developing any program
30
Chapter 4
IMPLEMENTATION
31
Input & Output Consideration:
32
IN OUR PROJECT:
1. LOGIN FORM:
33
2. MAIN WINDOW:
34
3. ‘FLIGHT SEARCH’ WINDOW:
35
4. ‘BILL/INVOICE’ WINDOW:
36
5. ‘TICKET’:
37
6. ‘LOG OFF’ WINDOW:
38
7. ‘FLIGHT MAINTAINANCE’ WINDOW:
39
8. ‘PASSENGER MAINTAINANCE’ WINDOW:
This form is
used to enter the passenger details as well as to update the
passenger details. It is actually used at the time of reservation. This
form includes invoice no, passenger name, flight no, departure date
& time, seat no, ticket type, seat class & destination.
40
9. ‘TICKET MAINTAINANCE’ WINDOW:
41
10. ‘FLIGHT DETAILS REPORT’ WINDOW:
By this window
we can get all the reports of flights. That is it gives full details of
files.
42
11. ‘PASSENGER DETAILS REPORT’ WINDOW:
By this
window we can get all the details of passengers who are made
reservation. That means it gives full detail of all the passengers.
43
12. ‘DAILY REPORT’ WINDOW:
44
13. ‘TICKET PRICE’ WINDOW:
45
14. ‘CANCELLATION’ WINDOW:
46
15. ‘SEATS AVAILABLE’ WINDOW:
47
Chapter 5
FEASIBILITY
STUDY
48
FEASIBILITY STUDY
Introduction:
Cost Effectiveness :
49
(a) Assign a weighing factor to each evaluation criterion based on
the criteria’s effect on the success of the system.
1.Benefit-Cost-Analysis (BCA) :
50
Information sources :
Kind of Information:
51
to gather. Much of information we need to analyze relates to the
organization in general the user staff and workflow.
Categories of information :
52
achieving the goal. After policies and set, a organization is
organized to meet these goals.
Time Feasibility :
The CBA time period should match the system life cycle.
53
The system life cycle ends when the system is terminated or is
replaced by a system that has significant differences in processing,
operational capabilities, resource requirement, or system outputs.
Significant differences is a very subject term, and some
organization may feel that a 10% change is significant, while
others may be that the change must be over 30% to be significant.
54
months. The senior system analyst is appointed as project
leader.
55
5. Determine and evaluate performance and cost-
effectiveness of each candidate system:
56
(b) Assign a quantitative rating to each criterion qualitative
rating.
8. Feasibility report:
a. Cover letter.
b. Table of contents.
c. Overview.
d. Detailed findings.
e. Economic justification.
57
f. Recommendations and conclusions.
g. Appendixes.
Chapter 6
FUTURE
DEVELOPMENT
58
6. FUTURE DEVELOPMENT OF PROJECT
59
Chapter 7
BIBLOGRAPHY
60
7. BIBLIOGRAPHY
This section gives you the name of the books required for the
development of the project.
61