A PROJECT REPORT ON
Online time table
Submitted in Academic Minor Project-I of the requirement
For the BCA sem-5 in Computer Science
AKS UNIVERSITY,SATNA(M.P.)
Submitted By: Narendra singh thskur
vishal singh
Under the Guidance: H.O.D
Submitted To
AKS UNIVERSITY,SATNA(M.P.)
CERTIFICATE
This is to certify that group bearing have developed Software project
titled Online time table for A.K.S University, Satna as a Academic Minor
Project-I for the BCA sem-5th.
HEAD OF DEPARTMENT
C.S & I.T.
CERTIFICATE
This is to certify that group bearing have developed Software project
titled online time table for A.K.S University, Satna as a Academic Minor
Project-I for the BCA sem-5th.
Internal EXTERNAL
PROJECT EVALUATION SHEET
1. Candidates Roll No.…………………………………………………………
2. Candidates Name……………………………………………………………
3. E-mail ………..……………………………………………………………
………………………………………………………………………………
4. Project Title…………………………………………………………………
5. Software Base………………………………………………………………
6. Sponsoring Institute & address………………………………………………
7. Submitted for course & Year:
8. Detail Evolution
Roll No. Enrollment No. Marks Awarded Signature of External
Out Of Examiner
1.
2.
3.
4.
DECLARATION
We affirm here project Online time table Submitted by us in AKS UNIVERSITY,Satna
(M.P.).For consideration of award of “BACHELOR OF COMPUTER APPLICATION”
embodies our own works, accept guidence and suggestion received during the work, which has
been duly acknowledge.
CERTIFICATE
This is to certify that this project entitled “online time table”
Submitted in Academic Major Project-I of the requirement For the BCA sem-5 in
Computer Science AKS UNIVERSITY, SATNA(M.P.). Done by Group NO: …………is
an is an authentic work carried out by them at
A.K.S University,Satna under the my guidance. The matter embodied in this
project work has not been submitted earlier for award of any degree or diploma to
the best of my knowledge and belief.
Signature of the student
Signature of Guide
……………….. ………………….
ACKNOWLEDGEMENT
We take this opportunity to express our profound sense of gratitude and respect to all those
who have helped us throughout the duration of this project. This has been very special
project brought to fruition through the enthusiasm of our guides and those who supported
us.
We express our heartfelt thanks to:-
To Pro. Akhilesh A. Waoo, head of the department and co coordinator [Link] Mishra
,AKS UNIVERSITY for giving us opportunity to undertake this project in his highly
reputed organization.
To our revered teacher and guide [Link] Mishra for their personal interest in the
activities of project right from its beginning.
To Dean of university for his constant encouragement and support at every moment.
ABSTRACT
CONTENTS
1) INTRODUCTION
● INTRODUCTION TO Project
● ORGANIZATION PROFILE
● PURPOSE OF THE PROJECT
● PROBLEM IN EXISTING SYSTEM
PROBLEM DEFINITION
PROJECT OBJECTIVE
● SOLUTION OF THESE PROBLEMS
2) PROJECT ANALYSIS
● STUDY OF THE SYSTEM
● HARDWARE & SOFTWARE SPECIFICATIONS
● INPUT & OUTPUT
● PROCESS MODELS USED WITH JUSTIFICATION
3) FEASIBILITY REPORT
● FEASIBILITY
TECHNICAL FEASIBILITY
OPERATIONAL FEASIBILITY
ECONOMIC FEASIBILITY
● ANALYSIS MODEL
● DETAILS OF EXISTING SYSTEM
4) SOFTWARE REQUIRMENT SPECIFICATION
● FUNCIONAL REQUIREMENTS
● PERFORMANCE REQUIREMENTS
● TECHNICAL ARCHITECTURE AND ENVIRONMENT
● PHP INTRODUCTION
● NEED FOR PHP
● NEW APPLICATION MODEL
● STRUCTURE OF PHP PAGE
CODE BLOCKS
SUPPORTED LANGUAGES
● EARLY BINDING
● CLIENT SIDE SCRIPTING
● SERVER SIDE SCRIPTING
● Back End
● SQL INJECTION
● CROSS SITE SCRIPTING (XSS) ATTACKS
● BUFFER OVERFLOW ATTACKS
● FEATURES OF PHP
● SESSIONS
IDENTIFYING A SESSION
LIFETIME OF A SESSION
SESSION VARIABLES
STORING DATA IN A SESSION
OBJECT
● INTERNET INFORMATION
SERVICE or Local host.
5) SELECTED SOFTWARE
6) PROJECT DESIGN
● INTRODUCTION
● SYSTEM WORKFLOW
● DATA FLOW DIAGRAM
● DATA DICTIONARY
DESIGNING DATABASE
7) OUTPUT SCREENS
● OVERVIEW
● SCREEN SNAPSHOTS
8) PROJECT TESTING
● INTRODUCTION
● STRATEGIC APPROACH of SOFTWARE TESTING
● UNIT TESTING
WHITE BOX TESTING
BASIC PATH TESTING
CONDITIONAL TESTING
DATA FLOW TESTING
5 LOOP TESTING
● TEST 1.1
9) CONCLUSION
10) FUTURE ENHANCEMENT
11) BIBLOGRAPHY
TITLE OF PROJECT
We give name “ONLINE TIME TABLE” to our website, we are developing this
site for purpose for entrepreneurship. making registration and submitting request
is not much faster work then actually when you call to service provider and he
will make you assured that request you asked will fulfilled and you make
yourself clear that satisfied. By making call also you services will give you total
satisfaction through can openly chat with owner or service provider. So this site
is not limited to only surfing of site like all.
TECHNOLOGY TO BE USED
FRONT END
What is [Link]?
[Link] is a new ASP generation. It is not compatible with Classic ASP, but [Link] may
include Classic ASP.
[Link] pages are compiled, which makes them faster than Classic ASP.
[Link] has better language support, a large set of user controls, XML-based components, and
integrated user authentication.
[Link] pages have the extension .aspx, and are normally written in VB (Visual Basic) or C# (C
sharp).
User controls in [Link] can be written in different languages, including C++ and Java.
When a browser requests an [Link] file, the [Link] engine reads the file, compiles and
executes the scripts in the file, and returns the result to the browser as plain HTML.
BACK END (SQL Server 2008)
SQL Server Management Studio is an integrated environment for managing your SQL Server
infrastructure.
Management Studio provides tools to configure, monitor, and administer instances of SQL
Server.
It also provides tools to deploy, monitor, and upgrade the data-tier components, such as
databases and data warehouses used by your applications, and to build queries and scripts.
Benefit of SQL Server.
[Link] Server Management Studio is a comprehensive utility for managing SQL Server objects
that combines an easy-to-use graphical interface with rich scripting capabilities.
2. Management Studio can be used to manage Database Engine, Analysis Services, Integration
Services, and Reporting Services.
[Link] most administrative tasks for SQL Server.
4.A single, integrated environment for SQL Server Database Engine management and authoring.
[Link] for managing objects in the SQL Server Database Engine, Analysis Services, and
Reporting Services, that allows you to execute your actions immediately, send them to a Code
Editor, or script them for later execution.
[Link]-modal and resizable dialogs allow access to multiple tools while a dialog is open.
7.A common scheduling dialog that allows you to perform action of the management dialogs at a
later time.
[Link] and importing SQL Server Management Studio server registration from one
Management Studio environment to another.
[Link] or print XML Showplan or Deadlock files generated by SQL Server Profiler, review them
later, or send them to administrators for analysis.
10. new error and informational message box that presents much more information, allows you
to send Microsoft a comment about the messages, allows you to copy messages to the clipboard,
and allows you to easily e-mail the messages to your support team.
SDLC MODEL
The Systems development life cycle (SDLC), or Software development process in systems
engineering, information systems and software engineering, is a process of creating or
altering information systems, and the models and methodologies that people use to develop
these systems. In software engineering, the SDLC concept underpins many kinds of
software development methodologies. These methodologies form the framework for
planning and controlling the creation of an information system. the software development
process
Overview
A Systems Development Life Cycle (SDLC) adheres to important phases that are essential
for developers, such as planning, analysis, design, and implementation, and are explained
in the section below. A number of system development life cycle (SDLC) models have been
created: waterfall, fountain, spiral, build and fix, rapid prototyping, incremental, and
synchronize and stabilize. The oldest of these, and the best known, is the waterfall model: a
sequence of stages in which the output of each stage becomes the input for the next. These
stages can be characterized and divided up in different ways, including the following
SDLC (System Development Life Cycle):-
System flow is a process consisting of the life cycle
1. RECOGNIZATION OF NEED’S:
The requirement gathering process is Intensified and focused especially on s/w. To
understand the nature of the programs to be built, the s/w engineer must understand
the information domain as well as required function, behaviors, performance and
interface after the user requirements are fulfilled and stabilized.
2. FEASIBILITY STUDY:
Feasibility study is high level version of the entire system analysis and design a process.
The purpose of feasibility is a not to solve the problem, but to determine if the problem is a not
to solve the problem is worth solving. It is conduct performance is defined by the identification
of specific system object and descriptive of output.
Three key consideration that are consideration that are involved in feasibility analysis are-
Economic feasibility
Technical feasibility
Operational feasibility
ECONOMIC FEASIBILITY:-
Economic feasibility is the most frequently used method for evaluating the effectiveness
of the proposed system. This is an on going effort that improves in accuracy at each phase of the
system life cycle. As the necessary software and hardware is nil. The proposed system is
minimizes the time and effort of the data collection, answering queries and generate reports
which results significant saving of the operating cost. Thus, the proposed system is economically
feasible.
TECHNICAL FEASIBILITY:-
It centers around the existing computer system (h/w, s/w…) and to what extent it can
support the proposed system. The necessary H/W and S/W tools available in the organization
and the software recommended support the system objects. Thus, it is technically feasible to and
develop the proposed system.
Our project is technically feasible, as we have taken [Link] as our front end.
Advantages of language are achieved as:-
Good interface for user.
Allow changes as when required.
It is Rapid Action development tool, which makes processing fast.
Coding make technical processing easy.
OPERATIONAL FEASIBILTY:-
Users are inherently resistant to change and computers have been known to facilitate
change. An estimate should be made of how strong a reaction the user is likely to words the
development of a new system. As the proposed system is user is almost negligible. Therefore,
resistance to the proposed system is nil. Based on the above analysis the recommended system is
feasible.
3. ANALYSIS:
It is detailed study of various operations performed by a system and their Relation
Ship within and outside of system. It is the logical model of the system as data dictionary,
data flow diagram etc. Also identifies the boundaries of the system and also determines
whether or not a candidate system should considered other related system.
COST AND BENEFIT ANALYSIS
In the early days of computing, software costs computed small percentage of the
overall computer based system cost. An order of magnitude error in estimates of software
costs had relatively impact. Today, software is the most expensive element of virtually
all computer- based system. For complex custom systems a large cost estimation error
can make the difference between profit and loss. Cost overrun can be disastrous for the
developer.
To achieve reliable cost and effort estimates a number of options arise.
1. Delay estimation until late in the project.
2. Base estimate on similar projects that have already been completed.
3. Use relatively simple decomposition technique to generate project cost and efforts
estimates.
4. Use one or more empirical models for software costs and efforts estimation
RISK ANALYSIS
Risk analysis and management are a series of steps that help a software team to
Understand and manage uncertainty. Many problems can infected a software project.
A risk is a potential problem- it might happen , it might not. But regardless of the
outcome, it’s a really good idea of identity it, assess its probability of occurrence , estimate
its impact, and establish a possibility plan should the problem actually occur For Risk Analysis
firstly recognizing what can go wrong that is established , risks Are ranked, by probability
and impact.
Finally a plan is developed to manage Those risks with high probability and high impact
4. Design
The design must be translated into a machine readable form. The code generation step
perform this task. It has follows
[Link] and DEUGGING :-
“It is said that nothing is complete in itself. "
After programming, we find many logical errors in the program. We test our system program
when our system does not run successfully and we dose not find our system up to the user's
requirements. Thus we can say that testing is must. If the user's requirements cannot fulfill, we
use the Debugging Tools in our project and debug our project statement by statements, found our
error and correct it. The testing process focuses on logic internal of the s/w, ensuring that all
statements have been tested ,Dummy accounts can be used with varying access levels to make
sure everyone has access to the right function and information and cannot access what they
should not.
In our project we too have gone through some problems but after testing and debugging, we
found them and made them correct. Here we are mentioning some of our problems and the way
we solve them. We were facing difficulty in connecting server, as we were not aware of the exact
port of server. If port can correct Thus at last we start the server & client. We can say that testing
& debugging is must because it improves the quality of our work and if same problem arise in
future one can easily be guided rough these " TESTING AND DEBUGGING "
PROJECT SCHEDULING
PROJECT july august sep oct nov
INFORMATION
COLLECTION
FORM
DESIGNING
CODING
DOCUMENTATION
HARDCOPY
PREPARATION
RECQUIREMENT ANALYSIS:-
HARDWARE CONFIGURATION:
CPU Intel Core2Dual Processor
RAM 256 MB
HDD 80 GB
SOFTWARE CONFIGURATION:
OPERATING SYSTEM WINDOWS-XP
FRONT END Netbeans 8.1.2
BACK END Mysql
PACKAGE MS-Word
DATAFLOW DIAGRAM
A data flow diagram (DFD) is used to described the logical operation of system i.e. what a
system does, DFD shows the flow through a system and the work or processing performed by
that system. DFD only represent the flow of data through the system and to don’t describe the
physical functioning of the system.
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.
DIFFERENT LEVEL OF DFD:-
data-flow diagram - Top-down approach
The system designer makes a context level DFD or Level 0, which shows the "interaction" (data
flows) between "the system" (represented by one process) and "the system environment"
(represented by terminators).
The system is "decomposed in lower-level DFD (Level 1)" into a set of "processes, data stores,
and the data flows between these processes and data stores".
Each process is then decomposed into an "even-lower-level diagram containing its
subprocesses".
This approach "then continues on the subsequent subprocesses", until a necessary and sufficient
level of detail is reached which is called the primitive process (aka chewable in one bite).
DFD is also a virtually designable diagram that technically or diagrammatically describes the
inflow and outflow of data or information that is provided by the external entity.
In Level0 the diagram does not contain any Datastores
O level DFD
0 level DFD
2 level DFD
Flow Chart
FACULTY INFORMATION TABLE
SUBJECT INFORMATION TABLE
TIME TABLE
TESTING
Testability:-
Software testability is simply how easily a computer program can be tested. Since testing
is so profoundly difficult, it pays to know can be done to streamline it. Sometimes programs are
willing to do things that will help the testing process, and a checklist of possible design points,
features, and so on can be useful in negotiating with them. The checklist provides a set of
characteristics that leads to testable software are:
● Operability.
● Operability.
● Controllability.
● Decomposability.
● Simplicity.
● Stability.
● Understandability.
White Box Testing:-
White box testing sometimes called glass-box testing is a test case
design method that uses the control structure of the procedural design to d rive test cases. Using
white-box testing methods,
The software engineer can drive test cases that:
● Guarantee that all independent paths within a module have been exercised at least once.
● Exercise all logical decisions on there true and false sides
● Execute all loops at their boundaries and within their operational bounds.
● Exercise internal data structure to assure their validity.
Basic Path Testing:-
Basic path testing is a white box testing technique. The basic path method
enables the test case designer to device a logical complexity measure of a procedural design
and uses this measure as a guide for defining a basic set of execution paths. Test cases
derived to exercise the basis set are guaranteed to execute every state in the program at least
one time during testing. Some points about which some information is necessary before basis
path testing are:
● Flow graph notation.
● Cycloramic complexity
● Deriving test cases
● Graph matrices.
Black Box Testing:-
Black box testing, focus on the functional requirements of the software.
That is, black box testing enables the software engineer to drive sets of input condition that
will fully exercise all functional requirements for a program. Black box testing is not an
alternative to white-box techniques. Rather, it is complementary approach that is likely to
uncover a different class of errors than white-box methods.
Black box testing attempts to finds errors in the following categories:
● Incorrect or missing function.
● Interface errors.
● Errors in data structures or external data-base access
● Performance errors.
● Initialization and termination errors.
Unlike white box testing, which is performed early in the testing process, black box testing tends
to be applied during later stages of testing.
Validation Testing:-
Validation succeed when software function in a manner that can be
reasonably expected by the customer. The software has been validation to successfully the
requirements.
TESTING MEDHODOLOGY
We follow linear sequential model: the linear sequential model suggest a systematic ,
sequential approach to S/W development that been at the system level and progresses through
analysis , design, coding ,testing and support.
Once code has been generated, program testing begins. The testing process focused on the
logical internals of the software’s, ensuring that all statements have been tested ,and on the
functional externals, that is conducting tests to uncover error and ensure that a define input will
produce actual results that agree with required result.
TESTING TECHNOLOGIES USED
.
LOOP TESTING:
Loop testing is a technique that focuses exclusively on the validity of loop construct.
TESTING GUIs:
Graphical user interface present interesting challenges for S/W engineers because of reusable
components provided as part of GUI development environment.
UNIT TESTING:
The module interface is testing to ensure at information properly follows into an out of the
program unit under test.
INTEGRATION TESTING:
Once all modules have been unit tested “if they all work individually, why do you doubt that
they ll work, when they we put them together?”
VALIDATION TESTING:
A final series a S/W tests validation testing may being . validation can be defined in many
ways , but a simple definition is that validation succeeds when S/W in a manner that can be
reasonably expected by the customer
FUTURE WORK
Today we are living in the age of breakneck environment and the world revolutionizing in very
short span of time.
It is important to have some future enhancement in our project.
We would like to make our project more user friendly more authentic more flexible.
Some of our future expectation is as follow.
Firstly, we for see that in the future every person (customer) can get good things through our
website(project)
● The web browser wants to view and download the latest and updated data so every now
and then our downloading section data has to be updated to avoid letting it become old.
● To have more exciting features and interactive service so that more and more internet
surfers browser our portals is also a corner.
..
We would also like to add flexibility by providing this information in the internet.
CONCLUSION
This is an achievement in the area of managing Organization designation from
Different implementation through our single project. Timing is the main preference given
as to make the user feel easy and comfort .This project will certainly established itself as
one of the important “guide” for the user to get to their Requirements.
References
1. References Books:-
HTML,CSS,PHP…………………………………………..Steven Holzner
Peter Norton Guide to visual basic 2005……………………………Peter Norton
2. Other Documentation and Resources:-
● [Link]
