Smart Admission Management System: Section: C

Smart Admission Management System
Section: C
Ahmad Nawaz (i16-0020)

Taimoor Aftab (i16-0004)
Faraz Ahmad (i16-0305)
M. Hasnain (i16-0061)
Table of Contents
❏ Introduction
❏ Component Diagram, ERD for database design
❏ Architecture Styles
❏ Product Backlog
❏ Burn down Chart
❏ Screen Shots(Trello)
❏ Project Screen Shots
Smart Admission Management System
Introduction:
The Smart Admission Management System (SAMS) tends to provide a unified platform to
students looking to enroll in undergraduate, post graduate or doctorate programs and give
them the facility to search for Universities of their preference according to the area, merit or
favorability. The platform also recommends the top options based on the student’s previous
academic record, field and selected area. The users using this platform are further divided into
2 categories, registered users and non-registered users. Non-registered users can only search
for universities whereas registered users can register for the university and can view the
recommended universities as well.
Component Diagram:
MySQL Connector: I have used a MySQL connector to build a connection with my database i-e
MySQL driver for PHP.
Component Details:
1) User interface: An application’s user interface is composed of a number of elements
that allow a user to perform functions on the system. We have used a PHP and html
language to implement user friendly interface. Components/pages to implement user
interface are Frontpage.php, Loggedin.php , Login.php , signup.php.
2) Database: we have 1 database having the information of both universities and the
registered user as well. We have use MySQL tool(XAMP) to create and build a database.
Database component name is mydatabase.mysql.
3) Utility: In utility component we process the information/data coming from the database
and extracting the needed information from the available data i-e extraction and
refining of data using SQL queries. Components/pages to implement Utility is
daxkhla.sql.
4) Facilities: Retrieve/get the processed and refined information coming from the Utility
component using PHP language.
5) Admission management system Component: uses the processed data coming from
facilities and display it on the screen (user interface) using PHP and HTML language to
fulfil the user’s query.
Data base design:

Architecture for Our Project: we have used 2 architecture styles for our project because
our project is related to web and database application.
1) Client Server Architecture:

Client-server architecture is an architecture of a computer network in which many clients
request and receive service from a centralized server.
Reason for selecting this style: We use this architecture because it ensures high link ability,
centralization (of server), accessibility, and security.
2) 3 tier Data Base Architecture:

We have used a centralized 3 tier Data base architecture. In three tier database architecture we
have 3 layers Presentation layer, Application layer and Database tier.
Reason for selecting this style: Because 3-tier architecture separates its tiers from each other
based on the complexity level and it also enable us to implement a simple N layer architecture
(i-e close to MVC) which remove a lot of complexity.
Product Backlog:
Sprint 1
Sprint user Task Resource Resource Priority Status

Story Planned Utilized assigned
(Man (Man
Hours) Hours)
User stories: // tasks and
1: As a registered //other info
user(student), I are //written in
want to log in, so sub //user stories
that I can access
subscriber
content.
2: As an app
owner /
registered
universities, I
want to attain
student’s
application
information, so
that I can process
the student’s
registration
process later.
3: As a
user(student), I
want to visit your
site, so that I can
gather and
search for the
required
information of
respective
university.
Sub User stories: Making a web 5 4 4 Implemented
1.1: Setup a web based project.
based project.
Sign up and log 1 1 4 Implemented

1.2: Create Sign in page is made
Up and log in and activated
page/form using html and
php.
1.3: Design Designing, 3 3 5 Implemented

Database for Creating and
Storing Students maintaining the
Data data base.
Registration 1 1 4 Implemented
2.1: Gather form is made to
Student gather the
Information information from
the student using
html and PHP.
3.1: Search for Drop down 0.5 0.5 4 Implemented
appropriate search bar is
university. made to search
for universities.
Sprint 2
1: As a registered // tasks and

user(student), I //other info
want to register, are //written in
so that I can apply sub //user
for the stories
registration in
the respective
university.
2: As a registered
university(user),
I want an analysis
of entry test, so
that I can evaluate
and view the
performance of
students and
difficulty level of
entry test.
3: As a registered
user(Student), I
want to view
recommendation
s, so that I can
make a decision
of registration in
any of the
recommended
university.
1.1: Capturing Maintaining and 1 1 5 Implemented

Student’s adding the
registration record of
student’s
registration for
universities in
database.
2.1 Generation of Generating the 1 0.5 5 Implemented
entry test entry test by
selecting the
questions from
the database.
2.2: Analysis of Generated entry 0.5 0.5 2 Implemented
entry test.
test’s difficulty
level is
measured and
displayed on the
screen.
3.1: Aggregate Aggregate of 15 15 2 Implemented
calculation. student is minute Minutes
calculated from s
its matric, FSC
etc. marks.
Implemented
3.2: Generate Recommendation 1.5 4
recommendations of universities on 1.5
the basis of
student’s
aggregate, area,
field of interest
are made by
running a SQL
query on the
database.
Implemented
3.3: View 0.5 3
recommendation Making html 0.5
s. form to display
all the
recommended
universities.
Sprint 3
1: As a user (student or // tasks
university), I want a and //other
user friendly interface, info //are
so that I can perform my written //in
tasks (for e.g. sub user
registration, searching //stories
etc.) in easier, simper
and friendlier way.
2: As a
user(Student/University
), I want an optimized
search, so that I would
be able to reach the
required/requested
page in a small amount
of time.
1.1: user friendly User friendly 4 4 4 Implemented

interface. interface is achieved
by using attractive
graphics (using CSS
and JS) and easy to
use options
2.1: capturing the Extracting/gatherin 0.5 0.5 4 Implemented
data. g the useful and
needed data of
different
universities.
2.2: Optimized Implemented

and powerful Running the 0.5 0.5 2
searches. specific search
queries on the
database to obtain
the optimized
results. To make
search process fast
we used a
dropdown menu.
2.3: Displaying Search results are 0.5 0.5 3 Implemented
the search results. displayed on the
screen using html
form.
2.4: Reaching the Along with the 0.5 0.5 3 Implemented

respective university’ data, its
university. official page’ link is
also stored in the
database and are
displayed on the
screen when the
respective
university is
searched.
Burn Down Chart:
Y: Effort
120
100 Actual> Remaining>
100 100 90
91 80 80
80 85 80 70 78
60 68
60 50 45
52 48 40
40 40 30 25
35
25 15 10 18
20 20
0
0 0
1 2 3 4 5 6 7 8 9 10 11 12 13 14
X: Days
Trello Screen Shots:
Sprint 1 screen shot:
Sprint 2 Screen Shot:

Sprint 3 Screen Shot:
Final Project trello’s Screen Shot:

Final Project Screen Shots:
Login (Popup)
Sign Up
View Registered Universities
Student Account (Logged in)

(i)
When Student already has Registration form filled, he/she doesn’t get the option to refill the
form and gets an additional Recommended Universities button.
Entry Test

Smart Admission Management System: Section: C

Uploaded by

Copyright:

Available Formats

Smart Admission Management System: Section: C

Uploaded by

Document Information

Original Title

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

Smart Admission Management System: Section: C

Uploaded by

Copyright:

Available Formats

Smart Admission Management System

Ahmad Nawaz (i16-0020)

Data base design:

1) Client Server Architecture:

2) 3 tier Data Base Architecture:

Sprint user Task Resource Resource Priority Status

Sign up and log 1 1 4 Implemented

1.3: Design Designing, 3 3 5 Implemented

1: As a registered // tasks and

1.1: Capturing Maintaining and 1 1 5 Implemented

1.1: user friendly User friendly 4 4 4 Implemented

2.2: Optimized Implemented

2.4: Reaching the Along with the 0.5 0.5 3 Implemented

Burn Down Chart:

Sprint 1 screen shot:

Sprint 2 Screen Shot:

Final Project trello’s Screen Shot:

Student Account (Logged in)

You might also like