Online Community New

CONTENTS
S.NO. Name of the Topic Page No.

1 Introduction 2
Objective 3
Scope 3
2 System Analysis 4-9

Identification of Need 4
Feasibility Study 4
Work flow 5-7
Study of the System 8
Input & Output 8
Software Requirements Specification(SRS) 9-10
Software Engineering Paradigm Applied 11
3 System Design 12-25

Data Flow Diagram(DFD) 12-16
Entity-Relationship Diagram 17-20
Use-case Diagram 21-23
Modularization Details 24
Database Design 25
Data Dictionary 26-27
4 Output Screen 28-32

User Interface Design 28
Snapshots 29-31
5 Source Code 32-57
6 Implementation & Testing 58

Introduction 58
Page 1
Objectives of Testing 58-59
Test Cases 60
White Box Testing 63
Black Box Testing 63
Output Testing 64
Goal of Testing 64
Integration Test Reports 65-66
7 System Security Measures 68

Database security measures
System security measures 68
Limitations 68
8 Conclusion 68
9 Bibliography/References 68
INTRODUCTION
Online Student Information Management System is a system that manages the record of
students regarding admission, training and development and placement programs.
It can be used by any educational institutes or colleges to maintain the records of student
easily. This system provides a simple interface for the maintenance of student information
from the time of admission till the time of certification.
Student Management System deals with all kind of student details, course details, fees details
and other related details too. It tracks all the details of a student from the day one to the end
of the course which can be used for all reporting purpose, tracking of attendance, progress in
the course.
OBJECTIVE
Page 2
The objective of Online Student Management System is to allow the administrator and User
of any organization to edit and view each and every minute detail record of students, courses,
faculties, batches and payment structure of an institution easily.
Without using this system, the information remains scattered, can be redundant and collecting
relevant information may be time consuming. All this problems are solved by using this
website.
Throughout the project the focus has been on presenting information in an easy and
intelligent manner.
The website provides facilities like online registration and profile creation of students thus
reducing paperwork and automation the record generation process in an educational institute.
SCOPE
Without student management system, managing and maintaining details of the student,
faculty, branch, batch, course is a tedious job for any organization.
According to our website, role of admin is to insert and modify the details of course, faculty,
batch and payment structure after login process and the role of User is to insert and modify
the details of the student after login process.
IDENTIFICATION OF NEED
Page 3
System analysis is a process of gathering and interpreting facts, diagnosing problems and the
information to recommend improvements on the system. It is a problem solving activity that
requires intensive communication between the system users and system developers. System
analysis or study is an important phase of any system development process .The system
studies the minutest detail and gets analyzed. The system analysist plays the role of the
interrogator and dwells deep into the working of the present system. The System is viewed as
a whole and the input to the system are identified. The outputs from the organization are
traced to the various processes. System analysis is concerned with becoming aware of the
problem ,identifying the relevant and Decisional variables ,analysis and synthesizing the
various factors and determining an optimal or at least a satisfactory solution or program of
action.
A detailed study of the process must be made by various techniques like interviews,
questionnaires etc. The data collected by these sources must be scrutinized to arrive to a
conclusion. The conclusion is an understanding of how the system functions. This system is
called the existing system .Now the existing system is subjected to close study and problem
area are identified .The designer now function as a problem solver and tries to sort out the
difficulties that the enterprise faces. The solution are given as proposals .The proposal is then
weighed with the existing system analytically and the best one is selected .The proposal is
presented to the user for an endorsement by the user.
FEASIBILITY STUDY
Feasibility study is made to see if the project on completion will serve the purpose the
organization for the amount of work.
Effort and the time that spend on it. Feasibility study lets the developer foresee the future of
the project and the usefulness. A Feasibility study of a system proposal is according to its
workability, which is the impact on the organization, ability to meet their user needs and
effective use of resources .Thus when a new application is proposed it normally goes through
a feasibility study before it is approved for development.
The document provide the feasibility of the project that is being designed and lists various
area that were considered very carefully during the feasibility study of this project such as
Technical , Economic and operational feasibilities.
Page 4
WORK FLOW
This Document plays a vital role in the development life cycle (SDLC) as it describes the
complete requirement of the system. It is meant for use by the developers and will be the
basic during testing phase. Any changes made to the requirements in the future will have to
go through formal change approval process.
The Waterfall Model was first Process Model to be introduced. It is also referred to as a
linear-sequential life cycle model. It is very simple to understand and use. In a waterfall
model, each phase must be completed before the next phase can begin and there is no
overlapping in the phases.
Waterfall model is the earliest SDLC approach that was used for software development.
The waterfall Model illustrates the software development process in a linear sequential flow;
hence it is also referred to as a linear-sequential life cycle model. This means that any phase
in the development process begins only if the previous phase is complete. In waterfall model
phases do not overlap.
Waterfall Model design
Waterfall approach was first SDLC Model to be used widely in Software Engineering to
ensure success of the project. In "The Waterfall" approach, the whole process of software
development is divided into separate phases. In Waterfall model, typically, the outcome of
one phase acts as the input for the next phase sequentially.
Page 5
Following is a diagrammatic representation of different phases of waterfall model.
The sequential phases in Waterfall model are:
 Requirement Gathering and analysis: All possible requirements of the system to be

developed are captured in this phase and documented in a requirement specification
doc.
 System Design: The requirement specifications from first phase are studied in this
phase and system design is prepared. System Design helps in specifying hardware
and system requirements and also helps in defining overall system architecture.
 Implementation: With inputs from system design, the system is first developed in
small programs called units, which are integrated in the next phase. Each unit is
developed and tested for its functionality which is referred to as Unit Testing.
 Integration and Testing: All the units developed in the implementation phase are
integrated into a system after testing of each unit. Post integration the entire system
is tested for any faults and failures.
 Deployment of system: Once the functional and non functional testing is done, the
product is deployed in the customer environment or released into the market.
Page 6
 Maintenance: There are some issues which come up in the client environment. To fix
those issues patches are released. Also to enhance the product some better versions
are released. Maintenance is done to deliver these changes in the customer
environment.
All these phases are cascaded to each other in which progress is seen as flowing steadily
downwards (like a waterfall) through the phases. The next phase is started only after the
defined set of goals are achieved for previous phase and it is signed off, so the name
"Waterfall Model". In this model phases do not overlap.
Waterfall Model Application

Every software developed is different and requires a suitable SDLC approach to be followed
based on the internal and external factors. Some situations where the use of Waterfall model
is most appropriate are:
 Requirements are very well documented, clear and fixed.
 Product definition is stable.
 Technology is understood and is not dynamic.
 There are no ambiguous requirements.
 Ample resources with required expertise are available to support the product.
 The project is short.
The advantage of waterfall development is that it allows for departmentalization and control.
A schedule can be set with deadlines for each stage of development and a product can
proceed through the development process model phases one by one.
Development moves from concept, through design, implementation, testing, installation,

troubleshooting, and ends up at operation and maintenance. Each phase of development
proceeds in strict order.
Page 7
STUDY OF THE SYSTEM
Modules: The modules used in this software are as follows:
 LOGIN: This module is for ADMIN and USER.

ADMIN has the authority to Insert, Update and Delete
User, branch, courses, images, Course details, installment. ADMINISTRATOR has
the authority to insert, Update, Delete student details.
 HOME: This page contains an overview of highlights for other Pages.
 ABOUT-US: This page contains the information about the details of the institute and
its disciples.
 CONTECTUS: This page contains the information about the institute address details.
 COURSES: This page contains the updated information about the courses that are
available.
 INSTALLMENT: This page contains the information about the installment part by
part.
 USER: This page contains minute details of the each and every details of student from
the time of admission till time of certification.
INPUT AND OUTPUT

The main inputs, outputs and the major function the details are: INPUT
 User can login using email-id and password.
 Admin can login using name and password.
 Admin insert and modify the images, and course details.
 User can make admission of a student by registering student details.
 User can modify student details searching them by Email-id only.
OUTPUT
 User can view the details gallery, courses, support centers,
 Admin can view the details of registered members, courses, and gallery.
SOFTWARE REQUIREMENT SPECIFICATIONS

Page 8
Software Requirements Specification provides an overview of the entire project. It is a
description of a software system to be developed, laying out functional and nonfunctional
requirements. The software requirements specification document enlists enough and
necessary requirements that are required for the project development. To derive the
requirements we need to have clear and thorough understanding of the project to be
developed. This is prepared after the detailed communication with project team and the
customer.
The developer is responsible for:-
 Developing the system, which meets the SRS and solving all the requirements of the
system?
 Demonstrating the system and installing the system at client’s location after
acceptance testing is successful.
 Submitting the required user manual describing the system interfaces to work on it
and also the documents of the system.
 Conducting any user training that might be needed for using the system.
 Maintain the system for a period of one year after installation.
Page 9
HARDWARE REQUIREMENTS:
• Computer that has a 1.6GHz or faster processor
• 1 GB (32 Bit) or 2 GB (64 Bit) RAM (Add 512 MB if running in a virtual

machine)
• HDD 20 GB Hard Disk Space and Above Hardware Requirements
• 5400 RPM hard disk drive
• DVD-ROM Drive
SOFTWARE REQUIREMENTS:
•WINDOWS OS (XP/2000/2003 or 2000 Server/Vista or 7)

•MySql (5.6.12)
•Wampserver
•Adobe Dreamweaver CS6
Page 10
SOFTWARE ENGINEERING PARADIGM APPLIED
Software paradigms refer to the methods and steps, which are taken while designing the software.
There are many methods proposed and are in work today, but we need to see where in the software
engineering these paradigms stand. These can be combined into various categories, though each of
them is contained in one another.
Programming
paradigm is a subset
of Software design
paradigm which is
further a subset of
Software
development
paradigm.
There are two levels of reliability. The first is meeting the right requirement. A carefully and
through systems study is needed to satisfy this aspect of reliability. The second level of
systems reliability involves the actual working delivered to the user. At this level, the systems
reliability is interwoven with software engineering and development.
There are three approaches to reliability.
1. Error avoidance: Prevents errors from occurring in software.
2. Error detection and correction: In this approach errors are recognized whenever they are
encountered and correcting the error by effect of error of the system does not fail.
3. Error tolerance: In this approach errors are recognized whenever they occur, but enables
the system to keep running through degraded perform or Appling values that instruct the
system to continue process.
Maintenance:
The key to reducing need for maintenance, while working, if possible to do essential tasks.
1. More accurately defining user requirement during system development.
2. Assembling better systems documents.
3. Using some effective methods for designing, processing, and login and communicating.
4. Making better use of existing tools and techniques.
DATA FLOW DIAGRAM
A data flow diagram (DFD) is a graphical representation of the "flow" of data through an
information system, modelling its process aspects. A DFD is often used as a preliminary step
to create an overview of the system, which can later be elaborated.
DFDs can also be used for the visualization of data processing (structured design).
Page 11
A DFD shows what kind of information will be input to and output from the system, where
the data will come from and go to, and where the data will be stored. It does not show
information about the timing of process or information about whether processes will operate
in sequence or in parallel (which is shown on a flowchart).
This context-level DFD is next "exploded", to produce a Level 1 DFD that shows some of the
detail of the system being modeled. The Level 1 DFD shows how the system is divided into
sub-systems (processes), each of whi1ch deals with one or more of the data flows to or from
an external agent, and which together provide all of the functionality of the system as a
whole. It also identifies internal data stores that must be present in order for the system to do
its job, and shows the flow of data between the various parts of the system.
Data flow diagrams are one of the three essential perspectives of the structured-systems
analysis and design method SSADM ﾧ. The sponsor of a project and the end users will need
to be briefed and consulted throughout all stages of a system's evolution. With a data flow
diagram, users are able to visualize how the system will operate, what the system will
accomplish, and how the system will be implemented. The old system's dataflow diagrams
can be drawn up and compared with the new system's data flow diagrams to draw
comparisons to implement a more efficient system. Data flow diagrams can be used to
provide the end user with a physical idea of where the data they input ultimately has an effect
upon the structure of the whole system from order to dispatch to report. How any system is
developed can be determined through a data flow diagram model.
In the course of developing a set of leveled data flow diagrams the analyst/designer is forced
to address how the system may be decomposed into component sub-systems, and to identify
the transaction data ﾧ in the data model ﾧ.
Data flow diagrams can be used in both Analysis and Design phase of the SDLC ﾧ.
There are different notations to draw data flow diagrams. defining different visual
representations for processes, data stores, data flow, and external entities.
DFD NOTATION
Page 12
DFD EXAMPLE
Steps to Construct Data Flow Diagram:-
Four Steps are generally used to construct a DFD.
 Process should be named and referred for easy reference. Each name should be
representative of the reference.
 The destination of flow is from top to bottom and from left to right.
 When a process is distributed into lower level details they are numbered.
 The names of data stores, sources and destinations are written in capital letters.
Rules for constructing a Data Flow Diagram:-
 Arrows should not cross each other.

 Squares, Circles, Files must bear a name.
 Decomposed data flow squares and circles can have same names.
 Draw all data flow around the outside of the diagram.
DATA FLOW DIAGRAM
LEVEL-0 DFD DIAGRAM
Page 13
LEVEL-1 DFD FOR ADMIN
LEVEL-1 DFD FOR USER
LEVEL-2 DFD FOR ADMIN
Page 14
Page 15
Page 16
ENTITY RELATIONSHIP DIAGRAM
In software engineering ﾧ , an entity–relationship model(ER model) is a data model for describing

the data or information aspects of a business domain or its process requirements, in an abstract way
that lends itself to ultimately being implemented in a database such as a relational. The main
components of ER models are entities (things) and the relationships that can exist among them.
An entity–relationship model is the result of using a systematic process to describe and define a
subject area of business data. It does not define business process; only visualize business data. The
data is represented as components (entities) that are linked with each other by relationships that
express the dependencies and requirements between them, such as: one building may be divided
into zero or more apartments, but one apartment can only be located in one building. Entities may
have various properties (attributes) that characterize them. Diagrams created to represent these
entities, attributes, and relationships graphically are called entity–relationship diagrams.
An ER model is typically implemented as a database. In the case of a relational database, which

stores data in tables, every row of each table represents one instance of an entity. Some data fields in
these tables point to indexes in other tables; such pointers are the physical implementation of the
relationships.
The three schema approach to software engineering uses three levels of ER models that may be
developed.
Conceptual data model

The conceptual ER model normally defines master reference data entities that are commonly used by
the organization. Developing an enterprise-wide conceptual ER model is useful to support
documenting the data architecture for an organization. A conceptual ER model may be used as the
foundation for one or more logical data models . The purpose of the conceptual ER model is then to
establish structural metadata commonality for the master data entities between the set of logical
ER models. The conceptual data model may be used to form commonality relationships between ER
models as a basis for data model integration.
Page 17
Logical data model
The logical ER model contains more detail than the conceptual ER model. In addition to master data
entities, operational and transactional data entities are now defined. The details of each data entity
are developed and the relationships between these data entities are established. The logical ER
model is however developed independent of technology into which it can be implemented.
Physical data model
One or more physical ER models may be developed from each logical ER model. The physical ER
model is normally developed to be instantiated as a database. Therefore, each physical ER model
must contain enough detail to produce a database and each physical ER model is technology
dependent since each database management system is somewhat different.
The physical model is normally instantiated in the structural metadata of a database
management system as relational database objects such as database tables, database
indexes such as key indexes, and database constraints such as a foreign key constraint or a
commonality constraint. The ER model is also normally used to design modifications to the
relational database objects and to maintain the structural metadata of the database.
The first stage of information system design uses these models during the requirements
analysis to describe information needs or the type of information that is to be stored in
a database. The modeling technique can be used to describe any ontology (i.e. an overview
and classifications of used terms and their relationships) for a certain area of interest. In the
case of the design of an information system that is based on a database, the conceptual data
model is, at a later stage (usually called logical design), mapped to a logical data model, such
as the relational model; this in turn is mapped to a physical model during physical design.
Note that sometimes, both of these phases are referred to as "physical design". It is also used
in database management system.
Entity–relationship modeling
Two related entities
An entity with an attribute
Page 18
A relationship with an attribute
Primary key ﾧ
Cardinality constraints are expressed as follows:
 A double line indicates a participation constraint, totality ﾧ or subjectivity ﾧ : all entities

in the entity set must participate in at least one relationship in the relationship set;
 an arrow from entity set to relationship set indicates a key constraint ﾧ , i.e. infectivity ﾧ :
each entity of the entity set can participate in at most one relationship in the relationship
set;
 A thick line indicates both, i.e. objectivity ﾧ : each entity in the entity set is involved
in exactly one relationship.
 An underlined name of an attribute indicates that it is a key ﾧ : two different entities or

relationships with this attribute always have different values for this attribute.
ER-DIAGRAM
Page 19
USE CASE DIAGRAM
A use case diagram at its simplest is a representation of a user's interaction with the system
that shows the relationship between the user and the different use cases ﾧ in which the
user is involved. A use case diagram can identify the different types of users of a system and
the different use cases and will often be accompanied by other types of diagrams as well.
So only static behavior is not sufficient to model a system rather dynamic behavior is more
important than static behavior. In UML there are five diagrams available to model dynamic
nature and use case diagram is one of them. Now as we have to discuss that the use case
diagram is dynamic in nature there should be some internal or external factors for making
the interaction.
These internal and external agents are known as actors. So use case diagrams are consists of
actors, use cases and their relationships. The diagram is used to model the
system/subsystem of an application. A single use case diagram captures a particular
functionality of a system.
So to model the entire system numbers of use case diagrams are used.
The purpose of use case diagram is to capture the dynamic aspect of a system. But this
definition is too generic to describe the purpose.
Page 20
Because other four diagrams (activity, sequence, collaboration and State chart) are also
having the same purpose. So we will look into some specific purpose which will distinguish it
from other four diagrams.
Use case diagrams are used to gather the requirements of a system including internal and
external influences. These requirements are mostly design requirements. So when a system
is analyzed to gather its functionalities use cases are prepared and actors are identified.
Now when the initial task is complete use case diagrams are modelled to present the
outside view.
So in brief, the purposes of use case diagrams can be as follows:
 Used to gather requirements of a system.
 Used to get an outside view of a system.
 Identify external and internal factors influencing the system.
 Show the interacting among the requirements are actors.
How to draw Use Case Diagram?

Use case diagrams are considered for high level requirement analysis of a system. So
when the requirements of a system are analyzed the functionalities are captured in use
cases.
So we can say that uses cases are nothing but the system functionalities written in an
organized manner. Now the second things which are relevant to the use cases are the
actors. Actors can be defined as something that interacts with the system.
The actors can be human user, some internal applications or may be some external
applications. So in a brief when we are planning to draw a use case diagram we
should have the following items identified.
 Functionalities to be represented as an use case
 Actors
 Relationships among the use cases and actors.
Page 21
Use case diagrams are drawn to capture the functional requirements of a system. So
after identifying the above items we have to follow the following guidelines to draw
an efficient use case diagram.
 The name of a use case is very important. So the name should be chosen in
such a way so that it can identify the functionalities performed.
 Give a suitable name for actors.
 Show relationships and dependencies clearly in the diagram.
 Do not try to include all types of relationships. Because the main purpose of
the diagram is to identify requirements.
 Use note whenever required to clarify some important points.
USE CASE DIAGRAM
Page 22
Page 23
MODULARIZATION DETAILS
As Modularization has gained increasing focus from companies outside its traditional industries of aircraft and
automotive, more and more companies turn to it as strategy and product development tool. I intend to explain the
importance aspects of modularization and how it should be initiated within a company. After determining the
theoretical steps of modularization success described in literature, I intend to conduct a multiple case study of
companies who have implemented modularization in order to find how real world modularization was initiated and
used to improve the company’s competitiveness. By combining theory and practical approach to modularization I
will derive at convergence and divergence between theoretical implementation to modularization and real world
implementation to modularization. This gives a valuable input for both implantations in companies as well as new
aspects to be further.
DATA INTEGRITY AND CONSTRAINTS
Data integrity is normally enforced in a database system ﾧ by a series of integrity constraints ﾧ or rules. Three types
of integrity constraints are an inherent part of the relational data model: entity integrity, referential integrity and
domain integrity:
 Entity integrity ﾧ concerns the concept of a primary key ﾧ. Entity integrity is an integrity rule which
states that every table must have a primary key and that the column or columns chosen to be the
Primary key should be unique and not null.
 Concerns the concept of a foreign key ﾧ. The referential integrity rule states that any foreign-key
Value can only be in one of two states. The usual state of affairs is that the foreign-key value
Refers to a primary key value of some table in the database. Occasionally, and this will depend
on the rules of the data owner, a foreign-key value can be null ﾧ. In this case we are explicitly
saying that either there is no relationship between the objects represented in the database
Or that this relationship is unknown.
 Domain integrity specifies that all columns in a relational database must be declared upon a defined
Domain. The primary unit of data in the relational data model is the data item. Such data items are said
Page 24
to be non-decomposable or atomic. A domain is a set of values of the same type.
DATABASE DESIGN
A database is an organized mechanism that has capability of storing information through which
a user can retrieve stored information in an effective and efficient manner. The data is the
purpose of any database and must be protected.
The database design is two level processes. In the first step, user requirements are gathered
together and a database is designed which will meet these requirements as clearly as possible.
This step is called information Level design and it is taken independent of any individual
DBMS.
In the following snapshots we display the way we have used MY SQL as the back-end RDBMS
for our project and the various entities that have been used along with their table definition and
table data.
Page 25
DATA DICTIONARY
Student registration table data
Page 26
Admin login table data
User login table
Page 27
USER INTERFACE DESIGN
User interface design (UID) or user interface engineering is the design ﾧ of user
interfaces ﾧ for machines ﾧ and software ﾧ , such as computers, home appliances ﾧ , mobile
devices ﾧ, and other electronic devices ﾧ, with the focus on maximizing the user experience ﾧ.
The goal of user interface design is to make the user's interaction as simple and efficient as
possible, in terms of accomplishing user goals (user-centered design ﾧ).
Good user interface design facilitates finishing the task at hand without drawing unnecessary
attention to it. Graphic design ﾧ and typography are utilized to support its usability ﾧ ,
influencing how the user performs certain interactions and improving the aesthetic appeal of
the design; design aesthetics may enhance or detract from the ability of users to use the
functions of the interface. The design process must balance technical functionality and visual
elements (e.g., mental model ﾧ) to create a system that is not only operational but also usable
and adaptable to changing user needs.
Interface design is involved in a wide range of projects from computer systems, to cars, to
commercial planes; all of these projects involve much of the same basic human interactions
yet also require some unique skills and knowledge. As a result, designers tend to specialize in
certain types of projects and have skills centered on their expertise, whether that be software
design ﾧ, user research, web design ﾧ, or industrial design ﾧ.
Page 28
SNAPSHOTS
Home page
Page 29
Admin login page
Page 30
Student Registration page
Page 31
SOURCE CODE
ADMIN LOGIN CODE
<?php
session_start();
error_reporting(0);
include("includes/config.php");
if(isset($_POST['submit']))
$username=$_POST['username'];
$password=($_POST['password']);
$query=mysql_query("SELECT * FROM admin WHERE username='$username' and password='$password'");
$num=mysql_fetch_array($query);
Page 32
if($num>0)
$extra="change-password.php";//
$_SESSION['alogin']=$_POST['username'];
$_SESSION['id']=$num['id'];
$host=$_SERVER['HTTP_HOST'];
$uri=rtrim(dirname($_SERVER['PHP_SELF']),'/\\');
header("location:http://$host$uri/$extra");
exit();
else
{ ?>
STUDENT REGISTRATION CODE
<body>

<link rel="stylesheet" href="http://mogulsdemo.com/html/pride-home/css/font-awesome.css">
<div class="jain_container">
<nav class="navbar navbar-default navbar-fixed-top" role="navigation">
<div class="container1 container-fluid">
<div class="navbar-header">
<button type="button" class="navbar-toggle" data-toggle="collapse" data-target="#bs-example-navbar-collapse-

1">
<span class="sr-only">Toggle navigation</span>
<i class="icon-menu"></i> Menu
Page 33
</button>
<a class="navbar-brand" href="#"> <img src="Images/logo-design-inspiration-12spet-2.jpg" width="160"

height="83"/></a>
</div>
<div class="col-md-8">
<div class="collapse navbar-collapse" id="bs-example-navbar-collapse-1">

<ul class="nav navbar-nav">

<li><a href="main.html">HOME</a></li>
<li><a href="About Us.html">ABOUT US</a></li>
<li><a href="includes/user_photo_show.php">GALLERY</a></li>
<li><a href="reg.php">SIGN UP</a></li>
<li><a href="log1.php">LOG IN</a></li>
<li><a href="contact Us.php">CONTACT US</a></li>
<li><a href="terms & conditons.php">TERMS & CONDITIONS</a></li>
<li><a href="index.php">ADMIN</a></li>
</ul>
</div>
<form class="form-horizontal form-horizontal_x">
<div class="form-group">
<div class="col-sm-4">
Page 34
<select name="hotel" id="hotel" required="" class="form-control"
onchange="changeFormaction2(this.value);">
<option value="" selected="">Select Courses</option>
<option value="67961">JAVA</option>
<option value="67964">PHP</option>
<option value="29191">MY-SQL</option>
<option value="67963">ASP.NET</option>
<option value="67580">Fortran</option>
<option value="8">VB.NET</option>
<option value="65728">Android</option>
<option value="60533">Python</option>
<option value="138227">J2EE</option>
</select>

</div>

<button type="submit" class="btn btn-primary">Search</button>
</div>
</div>
Page 35
</div>
</form>
</div>
</div>
</div>
<div class="col-md-2 medias">

<div class="classus" >
<p>Call us +919330144443</p>
</div>
<div class="why_bookonline">
<p> [email protected]</p>
</div>
</div>
</div>
</nav>
!-------
<div class="banner_home">
Page 36
<div id="myCarousel" class="carousel slide" data-ride="carousel">








Page 39
<div align="left" style="background-image:url(images/background-pictures-8.jpg)">
<form class="form-horizontal" action="insert_reg.php" method="post">
<fieldset>
<br />
<br />
<br />
<br />
<br /><br />
<br />
<br />

<center><legend><h3>Register Here......</h3></legend></center>

<label class="col-md-4 control-label" for="fn">Full Name</label>
<input id="fn" name="studentName" type="text" placeholder="Full Name" class="form-control input-md"

required="">
</div>
</div>

<label class="col-md-4 control-label" for="ln">Father Name</label>
<input id="ln" name="fname" type="text" placeholder="Father Name" class="form-control input-md"

required="">
</div>
Page 40
</div>

<label class="col-md-4 control-label" for="cmpny">Date of Birth</label>
<input id="Date of Birth" name="dob" type="date" placeholder="Date Of Birth" class="form-control input-

md" required="">
</div>
</div>
<label class="col-md-4 control-label" for="fn">Address</label>
<input id="address" name="address" type="text" placeholder="Address" class="form-control input-md"

required="">
</div>
</div>

<label class="col-md-4 control-label" for="email">Email</label>
<input id="email" name="email" type="email" placeholder="email" class="form-control input-md"

required="">
</div>
</div>

<label class="col-md-4 control-label" for="phone">Phone Number</label>
Page 41
<input id="mobile" name="mobile" type="text" placeholder="Phone" class="form-control input-md"
required="">
</div>
</div>

<label class="col-md-4 control-label" for="phone">Password</label>
<input id="password" name="password" type="password" placeholder="password" class="form-control input-

md" required="">
</div>
</div>

<label class="col-md-4 control-label" for="phone">Confirm Password</label>
<input id="cpassword" name="cpassword" type="password" placeholder="Confirm Password" class="form-

control input-md" required="">
</div>
</div>

<label class="col-md-4 control-label" for="submit"></label>
<button id="submit" name="submit" class="btn btn-primary">SUBMIT</button>
<button id="reset" type="reset" class="btn btn-primary">RESET</button>
<div align="center" style="color:#FFF;">
<a href="log1.php"><h4>Login</h4></a>
Page 42
</div>
</div>
</div>
</fieldset>
</form>
</html>
ADMIN PAGE CODE:
-----------------------------------------------------------------------------------------------
<body>
<?php include('includes/header.php');?>
<div class="content-wrapper">
<div class="container">
<div class="row">
<h4 class="page-head-line">Please Login To Enter </h4>
</div>
</div>
<span style="color:red;" ><?php echo htmlentities($_SESSION['errmsg']); ?><?php echo

htmlentities($_SESSION['errmsg']="");?></span>
<form name="admin" method="post">
<div class="row">
<label>Enter Username : </label>
<input type="text" name="username" class="form-control" required />
<label>Enter Password : </label>
Page 43
<input type="password" name="password" class="form-control" required />
<hr />
<button type="submit" name="submit" class="btn btn-info"><span class="glyphicon glyphicon-

user"></span> Log Me In </button>
</div>
</form>
<?php include('includes/footer.php');?>
<script src="assets/js/jquery-1.11.1.js"></script>
<script src="assets/js/index.js"></script>
</body>
</html>
----------------------------------------------------------------------------
HOME PAGE CODE
----------------------------------------------------------------------------------------------------
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>Main Page</title>
<link rel="shortcut icon" href="Images/creative-logo-design-ideas-3.jpg">
<link rel="stylesheet" type="text/css" href="brap-3.3.7-dist/css/brap.css" />
<link rel="stylesheet" type="text/css" href="brap-3.3.7-dist/css/brap.min.css" />
<link rel="stylesheet" type="text/css" href="brap-3.3.7-dist/css/brap-theme.css" />
<script src="min.js"></script>
<script src="brap-3.3.7-dist/js/brap.js"></script>
<link rel="stylesheet" type="text/css" href="Navbar.css">
<link rel="stylesheet" type="text/css" href="footer.css">
Page 44
<style>

.nav-tabs {
margin-bottom: 15px;
.sign-with {
margin-top: 25px;
padding: 20px;
div#OR {
height: 30px;
width: 30px;
border: 1px solid #C2C2C2;
border-radius: 50%;
font-weight: bold;
line-height: 28px;
text-align: center;
font-size: 12px;
float: right;
position: absolute;
right: -16px;
top: 40%;
z-index: 1;
background: #DFDFDF;

Page 45
</style>
<script>

// www.jquery2dotnet.com

</script>
</head>
<body>

<link rel="stylesheet" href="http://mogulsdemo.com/html/pride-home/css/font-awesome.css">
<div class="jain_container">
<nav class="navbar navbar-default navbar-fixed-top" role="navigation">
<div class="container1 container-fluid">
<div class="navbar-header">
<button type="button" class="navbar-toggle" data-toggle="collapse" data-target="#bs-example-navbar-collapse-

1">
<span class="sr-only">Toggle navigation</span>
<i class="icon-menu"></i> Menu
</button>
<a class="navbar-brand" href="#"> <img src="Images/logo-design-inspiration-12spet-2.jpg" width="160"

height="83"/></a>
</div>
<div class="collapse navbar-collapse" id="bs-example-navbar-collapse-1">

<ul class="nav navbar-nav">
Page 46
<li class="dropdown mega-dropdown">
</ul>
</li>
<li class="col-sm-4">
<ul>
<li class="dropdown-header">ONLY
PROJECT</li>
<li><a href="#">ANDROID</a></li>
<li><a href="#">JAVA</a></li>
<li><a href="#">Fonts</a></li>
<li><a href="#">Slide down on Hover</a></li>
</ul>
</li>
----->
</ul>
</li>

<li><a href="main.html">HOME</a></li>
<li><a href="About Us.html">ABOUT US</a></li>
<li><a href="admin/includes/user_photo_show.php">GALLERY</a></li>
<li><a href="admin/reg.php">SIGN UP</a></li>
<li><a href="contact Us.php">CONTACT US</a></li>
<li><a href="admin/index.php">ADMIN</a></li>
</ul>
</div>
<form class="form-horizontal form-horizontal_x">
Page 47

</div>

<button type="submit" class="btn btn-primary btn-sm">Search</button>
</div>
</div>
</div>
</form>
</div>
</div>
</div>
<div class="col-md-2 medias">

<div class="classus" >
<p>Call us +919330144443</p>
</div>
<div class="why_bookonline">
<a href="https://www.facebook.com/"><p>[email protected]</p></a>
</div>
</div>
</div>
</nav>
<div class="banner_home">
<div id="myCarousel" class="carousel slide" data-ride="carousel">

<ol class="carousel-indicators">
<li data-target="#myCarousel" data-slide-to="0" class="active"></li>

</ol>

<div class="carousel-inner" role="listbox">
<div class="item active">
<img src="Images/3UOnJ5.jpg" alt="Online Community"/>

</div>
<div class="item">

</div>
<div class="item">

Page 51
</div>


</div>
</div>
</div>



<footer class="footer1">
<div class="row">
<div class="col-lg-3 col-md-3">
<ul class="list-unstyled clear-margins">
<li class="widget-container widget_nav_menu">
<h1 class="title-widget">Useful links</h1>
<ul>
<li><a href="About Us.html"><i class="fa fa-angle-double-right"></i> About

Us</a></li>
Page 52
<li><a href="contact Us.php"><i class="fa fa-angle-double-right"></i> Contact
Us</a></li>
<li><a href="terms & conditons.php"><i class="fa fa-angle-double-right"></i>Terms

& Condition</a></li>
</ul>
</li>
</ul>
</div>
<ul>
<li><a href="#"><i class="fa fa-angle-

double-right"></i> Test Series Schedule</a></li>
<li><a href="#"><i class="fa fa-angle-double-right"></i>Coaching</a></li>
<li><a href="#"> <i class="fa fa-angle-double-right"></i>Books</a></li>
<li><a href="Test Centers.php"><i class="fa fa-angle-double-right"></i> Study

Centres</a></li>
</ul>
</li>
</ul>
<ul>
<li><a href="any querry.php"><i class="fa fa-angle-double-right"></i> Enquiry Form</a></li>
Page 53
<li><a href="Test Centers.php"><i class="fa fa-angle-double-right"></i>
Test Centres</a></li>
<li><a href="admin/reg.php"><i class="fa fa-angle-double-right"></i> Admission Form</a></li>
<li><a href="#"><i class="fa fa-angle-double-right"></i> Computer Live

Test</a></li>
</ul>
</li>
</ul>
<div class="col-lg-3 col-md-3">
<li class="widget-container widget_recent_news">
<h1 class="title-widget">Contact Detail </h1>
<div class="footerp">
<h2 class="title-median">Webenlance Pvt. Ltd.</h2>
<p><b>Email id:</b> <a

href="mailto:[email protected]">[email protected]</a></p>
<p><b>Helpline Numbers </b>
<b style="color:#ffc106;">(8AM to 10PM):</b> 03432271345,+9199330144443 </p>
<p><b>Corporation Office / Postal Address</b></p>
<p><b>Phone Numbers : </b>99335555000, </p>
<p> 0343-2758832, 180030002800</p>
</div>
<div class="social-icons">
<ul class="nomargin">
<a href="https://www.facebook.com"><i class="fa fa-facebook-square fa-3x social-fb"

id="social"></i></a>
<a href="https://twitter.com"><i class="fa fa-twitter-square fa-3x social-tw"

Page 54
<a href="https://plus.google.com"><i class="fa fa-google-plus-square fa-3x social-gp"
<a href="www.gmail.com"><i class="fa fa-envelope-square fa-3x social-em"

</ul>
</div>
</li>
</ul>
</div>
</div>
</div>
</footer>

<div class="footer-bottom">
<div class="row">
<div class="col-xs-12 col-sm-6 col-md-6 col-lg-6">
<div class="copyright">
</div>
</div>
<div class="col-xs-12 col-sm-6 col-md-6 col-lg-6">
<div class="design">
<a href="#">Ardent Collaboration </a> | <a target="_blank" href="http://www.online_community.com">Web

Design & Development by Ardent</a>
</div>
</div>
</div>
Page 55
</div>
</div>

<?php
?>
</body>
</html>
----------------------------------------------------------------------------------------------------
EMAIL CODE
<?php
include "db.php";
require_once("./PHPMailer_5.2.4/class.phpmailer.php");
$sid = base64_decode($_GET['sid']);
//$uid = base64_decode($_GET['uid']);
//$to = mysql_query("SELECT * FROM users WHERE uid = '$uid'");
//$fetch_info = mysql_fetch_array($to);
$sid = mysql_query("SELECT * FROM student WHERE s_id = '$sid'");
$fetch_sid = mysql_fetch_array($sid);
$FireForDeCode = mysql_query("SELECT pwd,email,phno FROM admin");
$DeCodeThis = mysql_fetch_array($FireForDeCode);
// require mailer class
$mail = new PHPMailer(); // Object created using class phpMailer
$mail->IsSMTP();
//$mail->IsSendmail(); // selecting smtp server
$mail->SMTPDebug = 1; // enabling debugging facility
$mail->SMTPAuth = true; // Simple Mail transfer protocol authorization activated
Page 56
$mail->SMTPSecure = 'ssl'; // using secured socket layer during mail for security purpose
$mail->Host = 'smtp.gmail.com'; // hosting from mail SMTP
$mail->Port = 465; // Port via which the mail gets sent
$mail->IsHTML(true); // Codes in HTML
$mail->Username = $DeCodeThis['email']; // From email
$mail->Password = base64_decode($DeCodeThis['pwd']); // From password for authorization
$mail->Subject = "Welcome to Ardent ! "; // subject
$mail->SetFrom($DeCodeThis['email'],"Joydeep",true); // From indicator
$mail->Body = "<html><body><div style='width:auto;
border:1px solid #FFC;
background-color:#FFC;
margin:0 auto;
padding:10px;
border-radius:5px;
height:auto;
font-size:14px;'>
<font face='Times New Roman, Times, serif'><h2>Welcome ".$fetch_sid['s_name'].", </h2>
<p>You have enrolled with us to learn.".$fetch_sid['course']." and we welcome you to our Center.</p>
<p>You will be informed about the commencement of summer training by end of March.</p>
<p>Web Developer</p>
<p><i><b><u>Joydeep Banerjee</u></b></i></p>
<font color='red'><p><strong>`Ardent is a team of young guys with passion in them`. Rajmohan De

Sarkar(Director)</strong></p></font></div></body></html>"; // body
$mail->AddAddress($fetch_sid['email'],$fetch_sid['s_name']); // To
$mail->AddAttachment($fetch_sid['pdf_path'],'Payment Acknowledged','base64','application/pdf');
if(!$mail -> send()) // send function checking if sent or not
{ echo 'Error';
Page 57
echo 'no'.$mail->ErrorInfo;
else
{ error_reporting(E_ALL);
ob_implicit_flush(true);
include_once "class.curl.php";
include_once "class.sms.php";
include_once "cprint.php";
$smsapp=new sms();
$smsapp->setGateway('way2sms');
$myno=$DeCodeThis['phno'];
$p=base64_decode($DeCodeThis['pwd']);
$tonum=$fetch_sid['contact'];
$_SESSION['student'] = $fetch_sid["s_name"];
$mess = "Hello ".$fetch_sid["s_name"].", Welcome to Ardent Team!!.\n
Your Reciept No - ".$fetch_sid["re_num"]."\nAmount Due : Rs. ".$fetch_sid["amt_due"];
//$mess=0;
//cprint("Logging in ..\n");
$ret=$smsapp->login($myno,$p);
if (!$ret) {
cprint("Error Logging In");
exit(1);}
//print("Logged in Successfully\n");
//print("Sending SMS ..\n");
$smsapp->send($tonum,$mess);
/*if (!$ret) {
Page 58
print("Error in sending message");
exit(1);
}*/
?><script>
window.location.href = "op_home.php";
alert('<?php echo $_SESSION["student"]?> we have sent you a mail regarding your enrollment please
check');
</script><?php
//print("Message sent"); //header('location:index_2.php'); }?>
------------------------------------------------------------------------------------------------
----
IMPLEMENTATION AND TESTING
A software system test plan is a document that describes the objectives, scope, approach and
focus of software testing effort. The process of preparing a test plan is a usual way to think
the efforts needed to validate the acceptability of a software product. The complete document
will help people outside the test group understand the "WHY" and "HOW" product
validation. It should be through enough to be useful but not so through that no one outside the
test group will read it.
INTRODUCTION
Page 59
Testing is the process of running a system with the intention of finding errors. Testing
enhances the integrity of a system by detecting deviations in design and errors in the system.
Testing aims at detecting error-prone areas. This helps in the prevention of errors in a system.
Testing also adds value to the product by conforming to the user requirements.
The main purpose of testing is to detect errors and error-prone areas in a system. Testing must
be thorough and well-planned. A partially tested system is as bad as an untested system.
And the price of an untested and under tested system is high. The implementation is the final
and important phase involves user-training, system testing in order to ensure successful
running of the proposed system. The user tests the system and changes are made according to
their needs. The testing involves the testing of the developed system using various kinds of
data. While testing errors are noted and correctness is the model.
OBJECTIVES OF TESTING:
The objective our test plan is to find and report as many bugs as possible to improve the
integrity of our program. Although exhaustive testing is not possible, we will exercise a broad
range of tests to achieve our goal. Our user interface to utilize these functions is designed to
be user-friendly and provide easy manipulation of the tree. The application will only be used
as a demonstration tool, but we would like to ensure that it could be run from a variety of
platforms with little impact on performance or usability.
Page 60
Process Overview
The following represents the overall flow of the testing process:
1. Identify the requirements to be tested. All test cases shall be derived using the current
Program Specification.
2. Identify which particular test(s) will be used to test each module.
3. Review the test data and test cases to ensure that the unit has been thoroughly verified and
that the test data and test cases are adequate to verify proper operation of the unit.
4. Identify the expected results for each test.
5. Document the test case configuration, test data, and expected results.
6. Perform the test(s).
7. Document the test data, test cases, and test configuration used during the testing process.
This information shall be submitted via the Unit/System Test Report (STR).
8. Successful unit testing is required before the unit is eligible for component
integration/system testing.
9. Unsuccessful testing requires a Bug Report Form to be generated. This document shall
describe the test case, the problem encountered, its possible cause, and the sequence of events
that led to the problem. It shall be used as a basis for later technical analysis.
10. Test documents and reports shall be submitted. Any specifications to be reviewed,
revised, or updated shall be handled immediately.
Page 61
TEST CASES
A test case is a document that describes an input, action, or event and expected response, to
determine if a feature of an application is working correctly. A test case should contain
particular such as test case identifier, test condition, input data
Requirement expected results. The process of developing test cases can help find problems in
the requirement or design of an application, since it requires completely thinking through the
operation of the application.
TESTING STEPS
Unit Testing:
Unit testing focuses efforts on the smallest unit of software design. This is known as module
testing. The modules are tested separately. The test is carried out during programming stage
itself. In this step, each module is found to be working satisfactory as regards to the expected
output from the module.
Integration Testing:
Data can be lost across an interface. One module can have an adverse effect on another, sub
functions, when combined, may not be linked in desired manner in major functions. Integration
testing is a systematic approach for constructing the program structure, while at the same time
conducting test to uncover errors associated within the interface. The objective is to take unit
tested modules and builds program structure. All the modules are combined and tested as a
whole.
Validation:
At the culmination of the integration testing, Software is completely assembled as a package.

Interfacing errors have been uncovered and corrected and a final series of software test begin in
validation testing. Validation testing can be defined in many ways, but a simple definition is
that the validation succeeds when the software functions in a manner that is expected by the
customer. After validation test has been conducted, one of the three possible conditions exists.
a) The function or performance characteristics confirm to specification and are accepted.
b) A deviation from specification is uncovered and a deficiency lists is created.

c) Proposed system under consideration has been tested by using validation test and found to be
working satisfactory.
Page 62
SNAPSHOT OF ADMIN LOGIN
Page 63
SNAPSHOTS OF STUDENT REGISTRATION
Page 64
WHITE BOX TESTING
In white box testing, the UI is bypassed. Inputs and outputs are tested directly at the code
level and the results are compared against specifications. This form of testing ignores the
function of the program under test and will focus only on its code and the structure of that
code. Test case designers shall generate cases that not only cause each condition to take on all
possible values at least once, but that cause each such condition to be executed at least once.
To ensure this happens, we will be applying Branch Testing. Because the functionality of the
program is relatively simple, this method will be feasible to apply.
Each function of the binary tree repository is executed independently; therefore, a program
flow for each function has been derived from the code.
BLACK BOX TESTING
Page 65
Black box testing typically involves running through every possible input to verify that it
results in the right outputs using the software as an end-user would. We have decided to
perform Equivalence Partitioning and Boundary Value Analysis testing on our application.
The goals of system testing are to detect faults that can only be exposed by testing the entire
integrated system or some major part of it. Generally, system testing is mainly concerned
with areas such as performance, security, validation, load/stress, and configuration sensitivity.
But in our case well focus only on function validation and performance. And in both cases we
will use the black-box testing.
Page 66
OUTPUT TESTING
After performing the validation testing, the next step is output testing of the proposed system,
since no system could be useful if it does not produce the required output in a specific format.
The output format on the screen is found to be correct. The format was designed in the
system design time according to the user needs. For the hard copy also; the output comes as
per the specified requirements by the user. Hence output testing did not result in any
correction for the system.
User Acceptance Testing:
User acceptance of a system is the key factor for the success of any system. The system under
consideration is tested for the user acceptance by constantly keeping in touch with the
prospective system users at the time of developing and making changes whenever required.
This is done in regard to the following point:

a) Input Screen Design
b) Output Screen Design
c) Format of reports and other outputs.
GOAL OF TESTING
"Program testing can be used to slow the presence of bug, but never to slow their absence." If
the results delivered by the system are different from the excepted ones then the system is
incorrect and these bugs should be fixed.
Page 67
INTEGRATION TEST REPORTS
Software testing is always used in association with verification and validation. In the testing
phase of this project our aim is to find the answer to following two questions.
 Whether the software matches with the specification (i.e. process base) to verify the
product.
 Whether this software in one client what wants (i.e. product base) to validate the
product.
Unit testing and integration testing has been carried out to find the answer to above
questions. In unit testing each individual module was test to find any unexpected
behaviour if exists. Later all the module was integrated and flat file was generated.
FUNCTIONAL TESTING
These are the points concerned during the stress test:
 Nominal input: character is in putted in the place of digits and the system has to
flash the message "Data error".
 Boundary value analysis: exhaustive test cases have designed to create an output
report that produces the maximum (and minimum) allowable number of table
entries.
Testing Method Used
We have adopted a testing method which is a mix of both (structural) and black box
(functional) testing. For modules we have adopted white box testing. Then we integrated the
module into sub systems and further into the system. These we adopted black box testing for
checking the correctness of the system.
Requirements Validated and Verified:
 The data is getting entered properly into database.

 The Screens are being loaded correctly
 The Various functions specified are being performed completely.
Page 68
S.No Input Description Expected Actual Status
Email Password Output Output
1 ajay ajay Please enter Please enter Error
Valid email Valid email
id id
2 ajaymaji51 1234567 Login Login Success
@gmail.com Successful Successfull
3 Ajay2222@gmail 1234 Email id or Email id or Success

password password
invalid invalid
4 555534234 jdsfnsnnd Please enter Please enter Error

id id
5 Expement1@ 67 Login Login Success
gmail.com Successfull Successfull
6 13232331233 734272 Please enter Please enter Error

id id
TEST CASE REPORT
Page 69
DATABASE SECURITY
System security measure is meant to be provided to make your system reliable and secured
from unauthorized user may create threats to the system. So you should follow some security
measures. We have used security levels in database level at system level.
SYSTEM SECURITY
If we talk about the system security in our proposed system we have implemented with the
help of maintain the session throughout the system’s use. Once a user has logged out than
he/she will not be able to perform any task before signing back again.
A high level of authentic login is given to the system so this is a very tedious task to enter
without authorization and authentication.
LIMITATIONS
 Since it is an online project, customers need internet connection to use it.

 People who are not familiar with computers can’t use this software.
 Customer must have debit card or credit card to book tickets.
CONCLUSION
This project has been appreciated by all the users in the organization. It is easy to use, since it
uses the GUI provided in the user dialog. User friendly screens are provided. The usage of
software increases the efficiency, decreases the effort. It has been efficiently employed as a
Site management mechanism. It has been thoroughly tested and implemented.
Page 70
BIBLIOGRAPHY
 https://www.w3schools.com
 https://www.slideshare.com
 https://www.scribd.com
 https://www.tutorialspoint.com
 https://www.youtube.com
Page 71

Online Community New

Uploaded by

Copyright:

Available Formats

Online Community New

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Online Community New

Uploaded by

Copyright:

Available Formats

CONTENTS

S.NO. Name of the Topic Page No.

2 System Analysis 4-9

3 System Design 12-25

4 Output Screen 28-32

5 Source Code 32-57

6 Implementation & Testing 58

7 System Security Measures 68

The sequential phases in Waterfall model are:

 Requirement Gathering and analysis: All possible requirements of the system to be

Waterfall Model Application

 Requirements are very well documented, clear and fixed.

 Product definition is stable.

 Technology is understood and is not dynamic.

 There are no ambiguous requirements.

 The project is short.

Development moves from concept, through design, implementation, testing, installation,

Modules: The modules used in this software are as follows:

 LOGIN: This module is for ADMIN and USER.

INPUT AND OUTPUT

SOFTWARE REQUIREMENT SPECIFICATIONS

• Computer that has a 1.6GHz or faster processor

• 1 GB (32 Bit) or 2 GB (64 Bit) RAM (Add 512 MB if running in a virtual

• HDD 20 GB Hard Disk Space and Above Hardware Requirements

• 5400 RPM hard disk drive

•WINDOWS OS (XP/2000/2003 or 2000 Server/Vista or 7)

•Adobe Dreamweaver CS6

DATA FLOW DIAGRAM

Steps to Construct Data Flow Diagram:-

Four Steps are generally used to construct a DFD.

Rules for constructing a Data Flow Diagram:-

 Arrows should not cross each other.

DATA FLOW DIAGRAM

LEVEL-0 DFD DIAGRAM

LEVEL-1 DFD FOR USER

LEVEL-2 DFD FOR ADMIN

In software engineering ﾧ , an entity–relationship model(ER model) is a data model for describing

An ER model is typically implemented as a database. In the case of a relational database, which

Conceptual data model

Physical data model

Two related entities

An entity with an attribute

Cardinality constraints are expressed as follows:

 A double line indicates a participation constraint, totality ﾧ or subjectivity ﾧ : all entities

in exactly one relationship.

 An underlined name of an attribute indicates that it is a key ﾧ : two different entities or

So in brief, the purposes of use case diagrams can be as follows:

 Used to gather requirements of a system.

 Used to get an outside view of a system.

 Identify external and internal factors influencing the system.

 Show the interacting among the requirements are actors.

How to draw Use Case Diagram?

 Functionalities to be represented as an use case

 Relationships among the use cases and actors.

 Give a suitable name for actors.

 Show relationships and dependencies clearly in the diagram.

 Use note whenever required to clarify some important points.

USE CASE DIAGRAM

DATA INTEGRITY AND CONSTRAINTS

Primary key should be unique and not null.