Student Portal

1
S

T

I

Z

3

9

9

3

I

T

P

R

O

J

E

C

T

S

T

I

Z

3

9

9

3

I

T

P

R

O

J

E

C

T

STIZ3993

UNIVERSITY OF SCIENCE AND TECHNOLOGY

SEMESTER SPRING 2013
Student registration and result processing system
(SRRPS)

SUBMITTED TO:
Mrs. Bridget shakesy

PREPARED BY:

SUBMISSION DATE:

07 \ Feb\ 2013

STIZ3993

2

UNIVERSITY OF SCIENCE AND TECHNOLOGY

SEMESTER SPRING 2013

Student registration and result processing system (SRRPS)

Agreement Deed Reference: UUM-ITPRO-YA131-AD[009]
System Number: UUM-ITPRO-YA131-SYS[009]

Prepared For:
Mrs. Bridget shakesy

Faculty of Computing and IT,
University of Science and Technology, Yemen

Prepared By:

Shaima'a Ahmed Abdullah Almaswary

Accessed by : --------------------------------------------- -----------------
<IT Project Supervisor> (Signature)

AUTHENTICATED BY: _______________ ___________
<IT PROJECT COORDINATOR> (SIGNATURE)

APPROVED BY: _______________ ___________

<PROGRAM COORDINAT (SIGNATURE)

III

Acknowledgment

First of all I would like to thank Allah who blessed me with health and wealth to reach this
level of education. Secondly, I thank my parents, betrothed and friends for helping and
supporting me. At last but not least big thanks to my supervisor and coordinator for giving me
this chance and help me to achieve my project.

IV

LIST OF FIGURE
Figure 1: agile life cycle
Figure 1 2.2-1 use case diagram
Figure 2 2.2-2 use case diagram
Figure 3 : 2.2.3 use case diagram
Figure1: STD_101
Figure2: STD_102
Figure4: STD_201
Figure5: STD_202
Figure6: STD_203
Figure7: STD_204
Figure8: STD_205
Figure1 : run software
Figure2 : Welcome screen
Figure3 : Agreement screen
Figure4 : Choose Install Location Window
Figure5 : Select components window
Figure6 : wamp server 2 configuration window
Figure7 : Installation window
Figure8 : SMTP server
Figure9 : Complete installation windows
Figure10 : phpmyadmin window
Figure11: Tables of database
FIGURE 5.1: MAIN PAGE HOME.
FIGURE 5.2 COURSES PAGE
FIGURE 5.3 CALENDER PAGE
FIGURE 5.4 ABOUT US PAGE
FIGURE 5.5 CONTACT US
FIGURE 5.6 LOGIN
FIGURE 5.7 ERROR MESSAGE WHEN NAME FIELD IS EMPTY
FIGURE 5.8 ERROR MESSAGE WHEN PASSWORD FIELD IS EMPTY
FIGURE 5.9 SIGN UP (REGISTER)
FIGURE 5.10 ERROR MESSAGE NAME ALREADY IN USE
FIGURE 5.11 ERROR MESSAGE PASSWORD IS TOO SHORT
FIGURE 5.12 ERROR MESSAGE EMAIL IS ALREADY IN USE
FIGURE 5.13 REGISTER SUCCESSFULLY
FIGURE 5.14 ADMIN PAGE
FIGURE 5.15 VIEW ACCOUNT

V

FIGURE 5.16 EDIT ACCOUNT
FIGURE 5.17 MESSAGE EDITED SUCCESSFULLY
FIGURE 5.18 ADMIN CENTER
FIGURE 5.19 ADD ALBUM
FIGURE 5.20 DELETE ALBUM
FIGURE 5.21 MESSAGE ALBUM DELETED SUCCESSFULLY
FIGURE 5.22 ADD INFORMATION
FIGURE 5.23 DELETE INFORMATION
FIGURE 5.24 MESSAGE INFORMATION DELETED SUCCESSFULLY
FIGURE 5.25 CALENDER MANAGEMENT
FIGURE 5.26 SHOW CONTACT
FIGURE 5.27 STAFF PAGE
FIGURE 5.31 ADD LEVEL
FIGURE 5.33 DELETE LEVEL
FIGURE 5.34 MESSAGE LEVEL DELETED SUCCESSFULLY
FIGURE 5.35 ADD STUDENT
FIGURE 5.36 DELETE STUDENT
FIGURE 5.37 MESSAGE STUDENT DELETED SUCCESSFULLY
FIGURE 5.38 ADD SCORE
FIGURE 5.39 MESSAGE SCORE ADDED SUCCESSFULLY
FIGURE 5.40 STUDENT PAGE
FIGURE 5.43 VIEW RESULT

VI

List of tables
TABLE2 : TEST ACTIVITIES.
TABLE3 : OVERALL TESTS.
TABLE 3.1 : MANAGE RESULT
TABLE 3.2 : REGISTER

VII

LIST of Abbreviations
URL ( uniform recourse link)
SRRPS (Student registration and result processing system)

VIII

Contents
Acknowledgment ....................................................................................................................................... iii
LIST OF FIGURE...................................................................................................................................... iv
List of tables ............................................................................................................................................... vi
LIST of Abbreviations .............................................................................................................................. vii
Chapter 1 : PROJECT PROPOSAL ........................................................................................................... 2
1. 1 PROJECT TITLE ............................................................................................................................. 2
1.2 PROJECT DESCRIPTION ............................................................................................................... 2
1.3 Problem Statement ............................................................................................................................ 2
1.4 PROJECT OBJECTIVES ................................................................................................................. 3
1.5 PROJECT SCOPE ............................................................................................................................ 3
1.6 PROJECT feasibility ......................................................................................................................... 4
1.7 Budget ............................................................................................................................................... 4
1.8 PROJECT METHODOLOGY .......................................................................................................... 4
1.9 Gantt chart ......................................................................................................................................... 7
1.10 limitation ......................................................................................................................................... 9
1.11 REFERENCES ................................................................................................................................ 9
1.12 For Office Use Only ........................................................................................................................ 9
Chapter 2: Software Requirements Specification ..................................................................................... 12
2.1 Introduction ..................................................................................................................................... 12
2.1.1 Identification ............................................................................................................................. 12
2.1.2 System Overview ...................................................................................................................... 12
2.1.3 Document Overview ................................................................................................................. 12
2. 2 ENGINEERING REQUIREMENTS ............................................................................................. 13
2.2.1 Use CASE Diagrams ............................................................................................................... 13
2.2.1.1 USE CASE : MANAGE RESULT (SRRPS-900) ............................................................... 15
2.2.1.2 USE CASE : VIEW RESULT (SRRPS-1200) ...................................................................... 17
2.2.1.3 USE CASE : REGISTER (SRRPS-1300) ............................................................................. 19
2.3 Security Requirements ................................................................................................................... 22
2.4 Design Constraints .......................................................................................................................... 22
2.4.1 Programming language ............................................................................................................. 22

IX

2.4.2 Programming Practices ............................................................................................................. 23
2.5 Software Quality Factors ................................................................................................................. 23
2.6 Entity Relationship diagrams .......................................................................................................... 23
2.7 Activity Diagrams ........................................................................................................................... 24
2.7.1 Use case (SRRPS-903): (staff) ADD result .............................................................................. 24
2.7.2 Use case (SRRPS-1200): (student) view result ........................................................................ 25
2.7.3 Use case (SRRPS-1300): (user) register ................................................................................... 26
2.8 Sequence Diagrams ......................................................................................................................... 27
2.8.1 Use case (SRRPS-903): (staff) ADD result .............................................................................. 27
2.8.2 Use case (SRRPS-1200): (student) view result ........................................................................ 30
2.8.3 Use case (SRRPS-1300): (user) register ................................................................................... 31
Chapter 3: Software Test Description ....................................................................................................... 34
3.1 Introduction .................................................................................................................................... 34
3.2 Identification ................................................................................................................................... 34
3.3 Overview of the Documents ....................................................................................................... 34
3.4 Formal Qualification Test Preparation ........................................................................................... 34
3.4.1Test schedule ............................................................................................................................. 34
3.4.2 Hardware .................................................................................................................................. 34
3.4.3 Software .................................................................................................................................... 35
3.5 Formal Qualification test Documentation and Results ................................................................... 35
3.5.1 Test Case of STD_100 manage result ................................................................................... 35
3.5.2 Test Case of STD_200 Register ...................................................................................... 36
3.6 Evaluation and Recommendation.................................................................................................... 43
Chapter 4: Installation Guide ...................................................................................................................... 2
4.1 Application Installation steps ............................................................................................................ 2
Step 1: Start set up ............................................................................................................................... 2
Step 2: Welcome Screen/log in screen ................................................................................................ 2
Step 3: Installation complete .............................................................................................................. 8
Step 4: Installation path ....................................................................................................................... 9
4.2 After Installation ............................................................................................................................... 9
Chapter 5: User Manual ............................................................................................................................ 12

X

Chapter 6: Conclusion............................................................................................................................... 36
6.1 Conclusion ....................................................................................................................................... 36
6.2 NOTES ............................................................................................................................................ 36

1

PROJECT PROPOSAL

For the
Student registration & result processing system
SRRPS

Agreement Deed Number
UUM-ITPRO-YA131-AD[009]

Prepared For:
Mrs.Bridget shakesy

International College

Prepared By:
Shaima'a Ahmed Almaswary

2

Chapter 1 : PROJECT PROPOSAL

1. 1 PROJ ECT TI TLE

Student Registration & Result Processing System (SRRPS)
1.2 PROJ ECT DESCRIPTI ON
Nowadays, Student Registration & Result Processing in any Institute are used manually through
papers and unprofessional ways to save students, staffs and materials Information which may
cause unwanted problems such as:
Losing basic information related to center, students or staffs.
Damages of data storing materials such as papers, archives or any other manual materials.
Easily damages if there is danger such as fires, water or any disaster.
High Difficulty to make information backup.
Time wasting and efforts losing in registering students and processing results.

Our project is a web-based system that provides new tools in institutes' management that helps in
managing students, materials and staff information.

The website has four views, first is the admin side, second is the staff side , third is the student side
and fourth is the user

The admin could manage institute information easily and in flexible way by registering students,
processing results, manage courses' materials and managing accounts.

In the staff side, they could upload students' results in the website which is flexible to the students
and their teachers.

Student could view their results, registering online and view the result form the website.
Users can register and view the information about the institute.

1.3 Problem Statement
The current system has many problems such as:
- Losing basic information related to center, students or staffs.
- Damages of data storing materials such as papers, archives or any other manual materials.
- Easily damages if there is danger such as fires, water or any disaster.
- High Difficulty to make information backup.
- Time wasting and efforts losing in registering students and processing results.
- It is manual or desktop system without any interaction with the students or staff.

3

1.4 PROJ ECT OBJ ECTI VES
This project helps the institutes' administration in:
Saving basic information related to center, students or staffs in modern and safe way.
Avoiding damages of data storing materials such as papers, archives or any other manual materials
through using modern tools.
Avoiding damages if there is any danger such as fires, water or any disaster.
Easiest ways to make information backup.
Time and efforts saving in registering students and processing results through online and
developed system.
To make web-based system that provides flexible interacting with the students or staff.

1.5 PROJ ECT SCOPE
There are four users:
Functions of administration:-
Login
Logout
Create an account
Delete an account
Update system info
Edit account info
Add new advertisement

Functions of staff:-
Login
Logout
Edit account info
Add exams result
View no of student
Add levels
Add students
Delete levels
Delete students
Edit result

Functions of student:
Login
Logout
Edit account info
View account
View results

Functions of users:
View new announcement

4

Scan institute info
Register

1.6 PROJ ECT feasibility
I achieved all the goals I want.

1.7 Budget
None.

1.8 PROJ ECT METHODOLOGY

The best methodology that will help to accomplish the project within this short duration.
AGILE - Extreme programming (XP) which is a software development methodology that
intended to improve software quality and responsiveness to changing customer requirements. As a
type of agile software development, it advocates frequent "releases" in short development cycles
(time boxing), which is intended to improve productivity and introduce checkpoints where new
customer requirements can be adopted.
Extreme Programming (XP) is an intense, disciplined and agile software development
methodology focusing on coding within each software development life cycle (SDLC) stage.

These stages are:
Code review
Testing
Planning
Architecture refactoring and refining
Ongoing design and redesign
Continuous integration to discover and repair problems early in the development process
Customer involvement and rapid feedback
These XP methodology disciplines are derived from the following four key values of Kent Beck,
XPs originator:
Communication: Communication between team members and customers must occur on a
frequent basis and result in open project discussion without fear of reprisal.
Simplicity: This involves using the simplest design, technology, algorithms and techniques to
satisfy the customers needs for the current project iteration.
Feedback: Feedback must be obtained at multiple, distinct levels, e.g., unit tests, code review and
integration.
Courage: Implement difficult but required decisions.
Techopedia explains Extreme Programming (XP) In addition to the key values, XP methodology
implementation also requires the support of the three principles of incremental change, embracing
change and quality work

5

Figure 1: agile life cycle
Twelve key practices also must be followed:
Planning
Short release
Metaphor
Simple design
Test-driven development
Design improvement
Pair programming
Collective ownership
Continuous integration
Sustainable pace
On-site customers
Coding standards
Iterations.
XP Methodology

The Extreme Programming life cycle consists of the following phases:
Exploration Phase .
Planning Phase .
Iterations to Release Phase .
Product ionizing Phase .
Maintenance Phase.

Exploration Phase
Project Initiation:

6

In this phase I set up and justify the project. Determine the name of the system and collect the
main requirements and define project vision.
Elaborate Requirements:
In this phase I will meet and interview the client to gather and specify opportunities, problems and
directions for the solution.

Planning Phase:
Project Plan :
In this phase I focuses primarily on identifying and Plan out the project, provides a preliminary
roles and responsibilities, outlines the project objectives, and identifies the main users.
Requirement Analysis:
In this phase start after client/supervisor approve the project proposal.
Brainstorm what the automated solution for project.
Collecting data from different resources and read more about project solution.
Design:
In this phase the following is prepared a hand-drawn sketch representing what needs to be built
for the web pages.
A sketch representing the logic of a task.
I terations to Release Phase:

Iteration (1) :
Planning: Estimating how long it will take this Iteration and secluding the work.
Analysis :
specifying DB schema and use cases specification to achieve the requirement.
Designing :
Designing a quick Diagrams Model and interface for web pages.
Coding:
writing basic code for the static web pages and creating Database.
Testing: check code and see any error to repair.

Iteration (2) :
Iteration (1) Feedback.
Planning:
Planning how long an iteration should be and how to control Unpredictable Process or changes .
Analysis:
trying to breakdown processes and listing more detailed information for each specific process.
Designing:
transforming the logical description and sketches in parallel with analyzing and designed detailed
use cases for instance : Entity relationship diagram (ERD), object diagrams, Normalization .. , etc.
which based on that Database will be designed.
Coding:
Improve the static pages and start writing the dynamic web pages, also full the database tables.
Try to concatenate the Database with dynamic web pages
Testing:
use the system and check code during construction iteration to see any error to repair.

7

Iteration (3) :
Iteration (2) Feedback.
Planning:
reworking with previous iteration and measure project completion.
Analysis:
communicate with customer and Respond to change over following a plan
Designing:
The system architecture, the database design, the diagrams and charts, the data types and
structure design clarified at this stage.
Coding:
write code and perform the unit testing.
Testing:
Independent testing for system, user testing and function (Software Validation).

Product ionizing Phase: testing and checking the performance of the system before the system can
be released to the client. The postponed ideas and suggestions are documented for later
implementation during the maintenance phase.

Maintenance Phase: Product Deployment and customer support with continuing programming
and error correction.

1.9 Gantt chart

8

9

1.10 limitation
it's not online courses.

1.11 REFERENCES
Wysocki, R. K. (2008). Effective Project Management: Traditional, Agile, Extreme. Wiley.

(Signature)
__________Shaima'a_________________
(Student's Name)

Date: 15/10/2012
1.12 For Office Use Only

Proposal Approved:

10

Conditions:

Comments:

___________________________

(IT Project Coordinator / Facilitator)

Date:

YES

NO

11

SOFTWARE REQUIREMENT SPECIFICATION
SRS

For the
SRRPS


Prepared For:
Mrs.Bridget shakesy


Prepared By:

12

Chapter 2: Software Requirements Specification
2.1 I ntroduction

2.1.1 Identification
System Number: UUM-ITPRO-YA131-009
System Name: Student Registration & Result Processing System
System Abbreviation : SRRPS

2.1.2 System Overview
In the student registration system is difficult task as well as the process of managing the students
information because of the manual system. Many student come to the institute, there is a lot of
student document and its difficult to get the history of specific student. International language
center oriented to solve the student problem .There will be four type of user in the system
Receptionist(admin), staff, student and user in addition receptionist can manage users level, manage
student information . staff can view student history and upload the result. The student can view the
result and view the brief history. And the user can only register.

2.1.3 Document Overview
The purpose of this document is to provide a full description of the system's contents for easy
understanding of how the system functions and how it can be manipulated. This document will give
a complete overview of the system. It specifies the analysis and design that has been planned to
develop the system. It will contain the use case diagram , ERD . The user interfaces along with the
activity, sequence and class diagrams.

13

2. 2 ENGI NEERI NG REQUI REMENTS

2.2.1 Use CASE Diagrams

Figure 2.2.1: use case diagram

14

Figure 2.2.2: main page

15

2.2.1.1 USE CASE : MANAGE RESULT (SRRPS-900)

2.2.1.1 .1 Description
This use case is used by the staff to manage result

2.2.1.1.2 Characteristic of Activation
Execution depends on staff demand

2.2.1.1.3 Pre-Condition (S)

the staff must login to the system successfully.
2.2.1.1.4 Description

a. Basic Flows (SRRPS 901)
This use case begins when the staff logs into the system to edit some contents of the result.
1.the staff successfully logs into the system.
2. the staff will click the add result button.
3. the system will display the add result page.

b. Alternative Flows (SRRPS 902)
Not applied.
c. Exception Flows (SRRPS 903)
Not applied.
2.2.1.1.5 Post-Condition

Staff will be able to add result

2.2.1.1.6 Limitation (S)
the staff must go online and open the SRRPS web site.

16

2.2.1.1.7 User Interface (S)

Figure 2.2.3 Add exams result

17

2.2.1.2 USE CASE : VIEW RESULT (SRRPS-1200)

This use case is used by the student to enable him to view result.

2.2.1.2 .2 Characteristic of Activation
Execution depends on student demand

The student must login to the system successfully.


This use case begins when the student wants to view result
1. The student should go online and open the SRRPS web site
2. The system displays the result.
3. The use case ends.

Not applied.
Not applied.

Student interact with the system


The student must go online and open the SRRPS web site.

18


Figure 2.2.4 view result

19

2.2.1.3 USE CASE : REGISTER (SRRPS-1300)

This use case is used by the user to register

2.2.1.3.2 Characteristic of Activation

Execution depends on user demand


None
This use case begins when the user wants to register
1. The user should go online and open the SRRPS web site
2. The system displays the register page.
3. The use case ends.

Not applied.
Not applied.

user interact with the system

the user must go online and open the SRRPS web site.


20

Figure 2.2.5 Register

Figure 2.2.6 Register successfully

21

Figure 2.2.7 user name already in use

Figure 2.2.8 Password is too short

22

Figure 2.2.9 Register field (same email)

2.3 Security Requirements
1-Login successfully to the system (provide authorization and authentication through creating
sessions for each user
2-using post action to hide information in( uniform recourse link) URL page form outsider

2.4 Design Constraints
2.4.1 Programming language
HTML
PHP
JAVASCRIPT
SQL

23

2.4.2 Programming Practices
I used programming using PHP, html and JAVASCRIPT. In addition I used MySQL as
the basis for my database and SQL commands to interact with the database.

2.5 Software Quality Factors
The evaluation of document quality and development process quality will be accordance with
the criteria DoD-Std-2167A, DoD-Std-2168 and parts of Rational conventions are the
responsibility of the ordering agency.

2.6 Entity Relationship diagrams

Figure 2.6.1 ERD

24

2.7 Activity Diagrams

2.7.1 Use case (SRRPS-903): (staff) ADD result

25

2.7.2 Use case (SRRPS-1200): (student) view result

26

2.7.3 Use case (SRRPS-1300): (user) register

27

2.8 Sequence Diagrams
2.8.1 Use case (SRRPS-903): (staff) ADD result

28

2.8.1.1 E: Empty field

29

2.8.1.2 A: result info not valid

30

2.8.2 Use case (SRRPS-1200): (student) view result

31

2.8.3 Use case (SRRPS-1300): (user) register

32

2.8.3.1 E: Empty field

33

SOFTWARE TEST DESCRIPTION
STD

For the
SRRPS


Prepared For:
Mrs.Bridget shakesy


Prepared By:

34

Chapter 3: Software Test Description
3.1 I ntroduction
3.2 I dentification

System Number : UUM-ITPRO-YA131-[009]
System Name : Student Registration & Result Processing System
System Abbreviation : SRRPS

3.3 Overview of the Documents
In the Student Registration & Result Processing
is difficult task as well as the process of managing the students information because of the manual
system. Many student come to the institute, there is a lot of student document and its difficult to get
the history of specific student. International language center oriented to solve the student problem
.There will be four type of user in the system Receptionist(admin), staff, student and user in addition
receptionist can manage users level, manage student information . staff can view student history and
upload the result. The student can view the result and view the brief history. And the user can only
register.

3.4 Formal Qualification Test Preparation
3.4.1Test schedule
The testing was conducted on 6 june 2013 at Lab 2, International College, University of Science and
Technology, Yemen. The details as below:
TIME ACTIVITIES
Manage result
Register
Table 2: Test activities.

3.4.2 Hardware
The test will be run on computer, with:

Intel(R) Pentium(R) Dual-Core CPU 2.20 GHz M processor
360 GB hard disk
2.00 GB of RAM

35

3.4.3 Software
The test will be executed using Windows 7 operating system.

3.5 Formal Qualification test Documentation and Results
The tests in this chapter are described in the table below:

No. Test
Descriptions
Description
1 STD_100 Manage result
2 STD_200 Register
Table 3: Overall tests

3.5.1 Test Case of STD_100 manage result

The goal of this test is to provide the capability of staff to manage result.

This test contains the following test cases:

Table 3.1: Mange result

36

Figure1: STD_101

Figure2: STD_102

3.5.2 Test Case of STD_200 Register

The goal of this test is to provide the capability of user to register.

37

This test contains the following test case:

Table 3.2 Register.

38

Figure3: STD_201

39

Figure4: STD_202

40

Figure5: STD_203

41

Figure6: STD_204

42

Figure7: STD_205

43

3.6 Evaluation and Recommendation
- based on the test results the recommendations are forwarded:
1. Allow users register online.
2. Allow student to view their results .
3. Allow students to edit their accounts
PROJECT PROPOSAL FORM ________________________________________________________________________STIZ3993-001

INSTALLATION GUIDE

For the
SRRPS


Prepared For:
Mrs.Bridget shakesy


Prepared By:

PROPOSAL PROJECT FORM_______________________________________________________________________ STIZ3993-001

CONFIDENTIAL

PAGE 2

Chapter 4: Installation Guide

4.1 Application Installation steps

1. Double click wampserver2.2e-php5.4.3-httpd2.2.22-mysql5.5.24-32b
2. The following window will be displayed.

Step 1: Start set up

Figure1 : run software

Step 2: Welcome Screen/log in screen


CONFIDENTIAL

PAGE 3

Figure 2: welcome screen

3.click the NEXT button
4. The following screen will be displayed containing the License Agreement


CONFIDENTIAL

PAGE 4

Figure 3: License Agreement screen

4. after click <I agree> button . The following screen will be displayed showing
where the software will be saved .

Figure4: Choose Install Location Window

6. Click <NEXT> to continue the installation of the wamp software.


CONFIDENTIAL

PAGE 5

Figure 5 : Select components window

8. Choose if you want
9. Click <NEXT>


CONFIDENTIAL

PAGE 6

Figure6: wamp server 2 configuration window

11. Click <Install> Button

12. wampserver software will stert to install.


CONFIDENTIAL

PAGE 7

Figure 7 : installation window


CONFIDENTIAL

PAGE 8

Figure 8 : SMTP server

13. wait until the installation finish and completing window display.

Step 3: Installation complete


CONFIDENTIAL

PAGE 9

Figure 9 : Complete installation windows

14. wampserver software is ready now to use.

Step 4: Installation path
C:\wamp\www

4.2 After I nstallation
Starting Application/Project
First Run sample


CONFIDENTIAL

PAGE 10

Figure 10 : phpmyadmin window

Figure 11 : tables of data base


CONFIDENTIAL

PAGE 11

USER MANUAL

For the
SRRPS


Prepared For:
Mrs.Bridget shakesy


Prepared By:


CONFIDENTIAL

PAGE 12

Chapter 5: User Manual

Figure 5.1 : Homepage

Figure 5.2 : Courses page


CONFIDENTIAL

PAGE 13

Figure 5.3 : Calender page

Figure 5.4 : About us page


CONFIDENTIAL

PAGE 14

Figure 5.5 : Contact us


CONFIDENTIAL

PAGE 15

Figure 5.6 : Login

Figure 5.7 : Error message name field is empty


CONFIDENTIAL

PAGE 16

Figure 5.8 : Error message password field is empty

Figure 5.9 : Register


CONFIDENTIAL

PAGE 17

Figure 5.10 : Register successfully

Figure 5.11 : user name already in use


CONFIDENTIAL

PAGE 18

Figure 5.12 : Password is too short

Figure 5.13 : Register field (same email)


CONFIDENTIAL

PAGE 19

Figure 5.14 : Admin page


CONFIDENTIAL

PAGE 20

Figure 5.15 : Admin (view account)

Figure 5.16 : Admin (edit account)

CONFIDENTIAL

PAGE 21

Figure 5.17 : Account Edited Successfully

Figure 5.18 : Admin (Admin center)


CONFIDENTIAL

PAGE 22

Figure 5.19 : Admin (Add photo)

Figure 5.20 : Admin (delete photo)


CONFIDENTIAL

PAGE 23

Figure 5.21 : Message delete album

Figure 5.22 : Admin (Add information)


CONFIDENTIAL

PAGE 24

Figure 5.23 : Admin (delete information)

Figure 5.24 : Message delete information


CONFIDENTIAL

PAGE 25

Figure 5.25 : Admin (manage calender)

Figure 5.26 : Admin (show contact)


CONFIDENTIAL

PAGE 26

Figure 5.27 : staff (staff page)

Figure 5.28 : staff view account


CONFIDENTIAL

PAGE 27

Figure 5.29 : Edit account



CONFIDENTIAL

PAGE 28

Figure 5.31 : staff (staff center)

Figure 5.32 : staff (add level)


CONFIDENTIAL

PAGE 29

Figure 5.33 : Message information added successfully

Figure 5.34 : delete level

Figure 5.35 : Message information deleted successfully


CONFIDENTIAL

PAGE 30

Figure 5.36 : staff (add student)

Figure 5.38 : staff (add score)


CONFIDENTIAL

PAGE 31

Figure 5.39 : message score added successfully

Figure 5.40 : staff (delete student)


CONFIDENTIAL

PAGE 32

Figure 5.41 : Message level deleted successfully

Figure 5.42: student (student page)


CONFIDENTIAL

PAGE 33

Figure 5.43: student (view account)

Figure 5.44: student (edit account)


CONFIDENTIAL

PAGE 34



CONFIDENTIAL

PAGE 35

Conclusion

For the
SRRPS


Prepared For:
Mrs.Bridget shakesy


Prepared By:


CONFIDENTIAL

PAGE 36

Chapter 6: Conclusion

6.1 Conclusion
I achieved all the goals I want and they can used it at the institute that help them
to register online and also to get the result online and It also doesn't repeat the
name and email for more security and It's not online courses and in the future I
prefer to add courses to the system because it is extendable system
Sometimes I have difficulty when I did the coding because I study from the
internet.
My advice is to study well and to ask your lectures about everything that you
didn't understand .

6.2 NOTES
Database name / version
wampserver2.2e-php5.4.3-httpd2.2.22-mysql5.5.24-32b
Phpmyadmin
Sql server

Student Portal

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

Student Portal

Uploaded by

Copyright:

Available Formats

1

You might also like