Professional Documents
Culture Documents
The Islamia University of Bahawalpur: Muhammad Tayyab Roll NO 170250 Mcs 4 (Morning) Session 2017-2019
The Islamia University of Bahawalpur: Muhammad Tayyab Roll NO 170250 Mcs 4 (Morning) Session 2017-2019
The Islamia University of Bahawalpur: Muhammad Tayyab Roll NO 170250 Mcs 4 (Morning) Session 2017-2019
Muhammad Tayyab
Roll NO 170250
MCS 4th(Morning)
Session 2017-2019
Affiliated with
The Islamia University of Bahawalpur
Project Brief
Project Name:
Online Education and Job Information System.
Objective:
The main objective of this system to change the traditional information provider system.
This system provides easy way to get information of jobs, Admitions and many things at
one place.
Undertaken BY:
Muhammad Tayyab
Roll NO 170250
MCS 4th(Morning)
Session 2017-2019
Supervised By:
Windows 7/8/10(64/32bit)
Project Stared:
June-19-2019
Project Finished:
Decmber-22-2019
Source Language:
PHP/MYSQL Server
CERTIFICATE
It is hereby ceretified that work presented by Muhammad Tayyab the ptoject title
“Online Education and Job Information System” has successfully presented
/defended and is accepted in its present form as satisfying the requirement for the degree
of (MCS & 2017-2019)in the Allama Iqbal Science College Bahawalpur affiliated with
Islamia University of Bahawalpur.
Supervisor _______________________________
Coordinator of Department
Umar Shafi _______________________________
Date: ____________________
DEDICATION
My Loving Parents
Who’s Support
Give me Strength
And determination
To Accomplish my Goal
Acknowledgement
Up and above everything, we are grateful almighty ALLAH,
The beneficent, the merciful, and his Holy Prophet Hazrat MUHAMMAD
(peace be upon him) who is forever true light of guidance for whole
humanity. We are greatly obliged “ALLAH” by whom grace we have been
able to complete this project successfully.
We feel much obliged to our families, whom prayers and good wishes have
enabled us to reached at this stage.
Our success is the result of the Technical Guidance, invaluable
comments and moral support of our supervisor
SIR UMER SHAFI SB. whose efforts and for the students are not only
for projects but also throughout the session. We are very thankful to
her for talking such a pain for us. We extend our thanks to all our
teachers from whom we have learnt a lot during the session and their
nice behavior and attitude is always encouraging us for learning.
Muhammad Tayyab
ABSTRACT
The main objective of this system to change the traditional information
provider system.
This system provides easy way to get information of jobs, Admitions and
many things at one place.
The project has been designed in PHP technology and consists of a My SQL
server which acts as the database for the project.
My motivation for the project came from my enthusiasm and strong urge to
learn PHP, HTML and CSS which is one of the fastest growing technologies
in today’s world.
The Online Education and Job Information System project mainly consists
of two types of users. The customers who access the information provided
by the website and the administrator who modifies and updates the
information.
All the data needed for the application is stored in the form of tables in the
My SQL server.
The report contains the details of all the tasks carried out during the entire
software Development life cycle of the Airline Reservation Project. This
document depicts all the details of the project.
Table Of Contents
Serial No. Chapter Details Page No.
Chapter No 1
1.1 Project Feasibility 11
Chapter No 2
2.1 System Specification 17
Chapter No 3
3.1 High Level Use-Case Diagram 22
Chapter No 4
4.1 Introduction to Database 28
4.8 Attributes 34
4.9 Normalization 35
Chapter No 5
5.1 Testing 47
Chapter No 6
6.1 Home Page 50
References 54
Chapter 1 INTRODUCTION
The system which I am going to develop as my final project is the Online Education
and Job Information System . This document is developed to serve as a starting point
of the software development process.
In this chapter I have discussed requirements engineering process, which provides the
appropriate mechanism for understanding what the customer wants, analyzing needs,
assessing feasibility, negotiating a reasonable solution, specifying the solution
unambiguously, validating the specification and managing the requirements as they are
transformed into an operational system.
1. Requirements elicitation
2. Requirements analysis and negotiation
3. Requirements specification
4. System modeling
5. Requirements validation
6. Requirements management
Here, requirements specification is to be discussed. Requirements specification would
lead to the following steps:
1. Identify external interfaces
2. Development of context diagram
3. User characteristics
4. Allocate requirements
5. Prioritize requirements
6. Development of requirements traceability matrix
The objective of Object Oriented Analysis and Design is to develop a model that
describes computer software as it works to satisfy a set of requirements. After
understanding the current situation of the problem domain the team is ready to strive for
the solution by using OOAD approach.
Actors:
Following are the actors that interact with info.com System of Administrator
User
Info.com Website
Admin
Figure:
User:
Administrator:
Info.com Website:
Admin:
Administrator:-
Step1:- Login admin
Step2:- View user
Step3:- insert Data
Step4:- perform database operations
Step5:- Logout
3.4. Sequence Diagram:
A Sequence diagram depicts the sequence of actions that occur in a system. The
invocation of methods in each object, and the order in which the invocation occurs is
captured in a Sequence diagram. This makes the Sequence diagram a very useful tool to
easily represent the dynamic behavior of a system. A Sequence diagram is two-
dimensional in nature. On the horizontal axis, it shows the life of the object that it
represents, while on the vertical axis, it shows the sequence of the creation or invocation
of these objects.
The sequence diagrams of the Online Education and Job Information System are shown
below:
3.4.1.User Registration:
3.4.4. Comment:
3.4.5. Logout:
DBMS:
Separation of data and metadata
Flexibility of changing metadata
Program-data independence
Data access language:
Standardized –SQL
Ad-hoc query formulation –easy
System development:
Less effort required
Concentration on logical level design is enough
Components to organize data storage
Process queries, manage concurrent access, recovery from failures,
manage access control are all available.
4.2.4. Data:
Data is information that has been organized and categorized for a pre determined
purpose. The term data is often used to distinguish binary machine-readable
information from textual human-readable information. For example, some
applications make a distinction between data files (files that contain binary data) and
text files (files that contain ASCII data).
4.2.5. Hardware:
Hardware is a machine which we use to store access manipulates and manages the
data it consist of following two things
1. The secondary storage volumes typically moving head magnetic tapes.
2. The processor and associated main memory that are used to support the
execution of the database system software.
4.2.6. Software:
All the request form users for access to the database are handled by DBMS.
4.2.7. Users:
a) Application programmer:
An Application programmer is someone who works in many different programming
languages to create the source code, which is responsible for creating small or large
parts of a piece of software in concert with others. Applications programming is the
meat and potatoes of programming, and requires a very creative mind, as well as one
that can retain lots of information about the requirements of the software, the
requirements of their teammates and the code itself.
b) End user:
The second class of user is end user. End-users use the software to assist with some
task. This may be flying an aircraft managing insurance policies, writing a books etc.
They want to know how the software can help them. They are not interested in
computer or administration details. These were final or ultimate user of a computer
system. The end user is the individual who uses the product after it has been fully
developed and marketed
c) Database administrator:
Data Independence
Consistency of Data
Control Over Redundancy
Integrity of Data
Greater Security of Data
Centralized Control of Data
Increased Productivity
Minimal Data Redundancy
Data Sharing
Ease of application development
Enforcement of standards
Data can be shared
Data independence is the type of data transparency that matters for a centralized DBMS.
It refers to the immunity of user applications to make changes in the definition and
organization of data. Physical data independence deals with hiding the details of the
storage structure from user applications. The application should not be involved with
these issues, since there is no difference in the operation carried out against the data. The
data independence and operation independence together gives the feature of data
abstraction.
Data integrity is data that has a complete or whole structure. All characteristics of the
data including business rules, rules for how pieces of data relate dates, definitions and
lineage must be correct for data to be complete. Data that has integrity is identically
maintained during any operation (such as transfer, storage or retrieval). Put simply in
business terms, data integrity is the assurance that data is consistent, certified and can be
reconciled.
rules of the business, 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.
Entity is a basic data object in database modeling. Entity can be person, a place, an event
or a thing about which we have to save data in the database. If we assume that our
database is a language then we can say that entities are nouns. Database is a collection of
entities. The first step in database modeling is to identify entities of database. This is of
the major parts in conceptual database modeling. Following are some characteristics of
an entity and it is very important to consider these while identifying entities.
a) Significant:
List only entities that are important to your database users and that are worth the
trouble and expense of computer tabulation.
b) Generic:
List only types of things, not individual instances. For instance, symphony might be
an entity, but Beethoven's Fifth would be an entity instance or entity occurrence
C) Fundamental:
List only entities that were exist independently and do not need something else to
explain them. Anything you might call a trait, a feature, or a description is not an
entity. For example, a part number is a feature of the fundamental entity called part.
d) Unitary:
Be sure that each entity you name represents a single class. It cannot be separated into
subcategories, each with its own features. In the telephone directory example, the
telephone number, an apparently simple entity, actually consists of three categories,
each with different features.
e) Weak entity:
A weak entity is an entity that exists only if is related to a set of uniquely determined
entities, which are called the owners of the weak entity. For instance, we could extend
our library with a weak entity type edition; each book has several editions, and
certainly it is nonsense to speak about an edition if this does not happen in the context
of a specific book. From a user interface viewpoint, weak entities are usually edited in
the context of (one of) their owners. When an entity is deleted from a schema
instance, all owned weak entities are deleted, too. We shall call the type of a weak
entity a weak entity type.
4.8. Attribute:
Entity contains a set of attributes. We can call attributes as properties, features or quality
of the entity. An attributes is smallest information that can’t be divided further. If we say
that entity is a table then columns would be attributes.
The primary key of a relational table uniquely identifies each record in the table. It
can either be a normal attribute that is guaranteed to be unique (such as Social
Security Number in a table with no more than one record per person) or it can be
generated by the DBMS (such as a globally unique identifier, or GUID, in
Microsoft SQL Server). Primary keys may consist of a single attribute or multiple
attributes in combination.
4.9. Normalization:
Normalization is a process to organize the data in an efficient manner. There are two
basic results which we expect from normalization. First is to remove redundant data
and second is avoid duplicate date to be recorded in database.For example
Through this example we explain different problems that might occur if the table is not
normalized.
a) Redundant Data:
Just consider that if we want to add a new entry of Maintenance then we has to enter all
the information regarding item again, in the above table, there are only a few records. Just
imagine what will happen where we have to store thousands of records.
b) Modification Anomaly:
Now consider another situation where we have to update the record of maintenance item
then we have to update it at many places, now what would happen when we will have
millions of records.
c) Deletion Anomaly:
What if we want to delete any record of any item from above mentioned table, then we
will also lose the information about slip no so what if we want to keep the record of thesis
maintenance information but still want to delete some information ?
d) Insertion Anomaly:
Suppose another situation where we have to insert a new record of thesis maintenance
information but we do not want insert data about vehicle.
To avoid such situations which are described above, we have to normalize the database.
We can divide the whole normalization process into four steps; until and unless, we are
done with first step we cannot move to next step.
These four steps are given below:
First Normal Form
Second Normal Form
Third Normal Form
Boyce-Codd Normal Form
4.9.1. First Normal Form:
First normal form enforce that the value of each column in table should be atomic
which means there should not be a group of data for one column. To understand the
concept of first normal form just considers the following example where we want to
store the record of suppliers.
1 C++ X/Y/Z
2 Java X/Y/Z
Some time, it can make things too complex while implementing these normal form so
best way is to find a balance as when it gets too complex then many DBMS requires
more resource or it can decrease the performance.
A carefully thought-out database design forms the foundation for future success. These
links will help you plan your database designs to maintain performance and integrity
through future growth. Ddatabase design is the process of producing a detailed data
model of a database. This logical data model contains all the needed logical and physical
design choices and physical storage parameters needed to generate a design in a Data
Definition Language, which can then be used to create a database. A fully attributed data
model contains detailed attributes for each entity.
After creating conceptual database design, you have to represent that by using any
modeling techniques. Currently, there are many modeling tools and techniques are
available which are given below:
Here in this document, we are going to discuss entity relationship diagram and
UML as this is the most widely used technique in he world.
Identify Entities
Define relationships
Define Cardinality of relationships
Identify Attributes and Primary Keys
Map all Attribute
a) Basic Objects:
_______________
Us e to mention primary key attribute
c) Developing ERD:
To understand the core concept of ERD, consider the Book Wholesale System.There are
following steps for Developing ERD.
o User or passenger
o Train
o Train status
o Route
o Station
One to
Many and cardinality will be 1: M.
Attributes of User:
Attributes of info.com:
4.12.3.Admission Table
Chapter 5 TESTING
1.1. Testing
5.2. Testing Strategy
5.3. Test Cases
5.1. Testing:
It is the process used to help identify the correctness, completeness, security, and quality
of developed computer software. Testing is a process of technical investigation,
performed on behalf of stakeholders, that is intended to reveal quality-related information
about the product with respect to the context in which it is intended to operate.
This Strategy used for testing is Black Box Testing. Every module is tested and after the
integration of all modules again individually testing is done.
• Incorrect Input:
Wrong format entered in the input fields for the registration page.
• Pass Criteria:
An appropriate message should be generated to the user saying that he has
entered the wrong format in the specific input field.
• Correct Input:
The correct input would a correct format entered by the customer into the
input fields of the registration page.
• Pass Criteria:
The pass criteria for this test case would be a successful registration for Tickets.
TEST CASE 3 – SEARCH AND BOOK SITES
• Incorrect Input:
Incorrect input in this case, would be incorrect search criteria entered or
incorrect format of data entered into the data entry fields of the flight search and booking
page.
• Pass criteria:
A message has to be generated to the user indicating the wrong entry that
he has made in the fields.
• Correct Input:
A correct input would be entering the data into the data entry fields in a
Correct format.
• Pass Criteria:
The pass criteria for this test case would be that the search would return
Valid results and then when the customer made the booking, the system has to generate a
Confirmation to the customer by displaying the message.
REFRENCES
Website References:
www.google.com
www.wikipedia.com
www.yahoo.com
www.ilmkidunya.com
jobsalert.pk
Book References:
Object Oriented Software Engineering by Craig Larman
Html and CSS design and build website by JON DUCKTT
UML in 24 Hours