Subject

- COMP1640 Enterprise Web Software

Development
UOG No - 0009100283

1|P ag e

Session

- May 2015 (1st Semester)

Name

- K.A.M Ireni Hansika

I would like to express my special thanks of

gratitude to Dear Sir Mr.Madhawa Ranawaka
who gave me the golden opportunity to do this
Assignment on the topic "Enterprise web
Development", which also helped me in doing a lot
of Research and I came to know about so many
new things
We are really thankful to him.
Secondly I would also like to thank our parents
and friends who helped us a lot in finishing this
assignment within the limited time.
I make this assignment not only for marks but
to also increase my knowledge.
THANKS AGAIN TO ALL WHO HELPED Us

2|P ag e

Table of Contents
1.1

Introduction .............................................................................................................. 6

1.2 Proposed System............................................................................................................ 6

1.3 Benefits of the proposed system .................................................................................... 6
1.4 Conclusion ..................................................................................................................... 7
2.1 Description on Existing system at University of Edima ............................................... 9
2.2 systems used by other universities ............................................................................. 10
2.2 Existing systems used by other universities ................................................................ 10
3. Requirement Analysis ................................................................................................... 14
3.1 What is Requirements Gathering? ............................................................................. 14
3.2 What are the Requirements Gathering Methods? ..................................................... 14
4.1 Rich Picture Description ............................................................................................. 16
4.2 Rich Picture for current system at the University of Edima...................................... 16
4.3 Current conflicts which the University of Edima is facing ........................................ 16
4.4 Rich Picture of University of Edima ........................................................................... 17
4.5 Use case Diagram ........................................................................................................ 18
4.6 Primary Scenario of the Use Case .............................................................................. 19
4.7 Secondary Scenario of the Use Case ........................................................................... 23
4.8 Requirement Identification ......................................................................................... 27
4.8.1 Identify the requirement for the new system........................................................... 27
4.8.2 Requirement catalogues ........................................................................................... 27
4.5.3 Functional Requirements ......................................................................................... 27
4.8.4 Non Functional Requirements ................................................................................. 28
4.9 Requirement Catalogue Screen shots ......................................................................... 28
5.2 ER Diagram ................................................................................................................. 34
5.3 Class Diagram ............................................................................................................. 41
5.4 Sequence Diagrams ..................................................................................................... 42
5.5 Collaboration Diagrams .............................................................................................. 48
5.6 Activity Diagrams ........................................................................................................ 52
5.7 Component Diagram ................................................................................................... 60
3|P ag e

5.8 Wire Frames ................................................................................................................ 61

5.8.1 Wire Frames Mobile View ....................................................................................... 66
5.9 Site Map ....................................................................................................................... 69
6. 1 what kind of Methodologies used for System Development?.................................... 72
1.2

What is Scrum? ...................................................................................................... 72

Our Project Development Team ....................................................................................... 73

7. What is Testing? ............................................................................................................ 75
7.1 What is Verification, Validation, Defect finding? ...................................................... 75
7.2 Test Cases .................................................................................................................... 75
7.3 Sample Acceptance Test questions ............................................................................. 80
8. System Implementation................................................................................................. 82
8.1 System Implementation Strategies.............................................................................. 82
8.2 Implementation Diagram ............................................................................................ 83
9. Critical Appraisals ........................................................................................................ 85
9.1 Problems faced ............................................................................................................ 85
9.2 Lesson Learned............................................................................................................ 85
9.3 Future Enhancements ................................................................................................. 85
9.4 Weaknesses of the System ........................................................................................... 86
Appendix A - Gantt Chart ................................................................................................ 88
Appendix B ..................................................................................................................... 91
Meeting Minutes................................................................................................................ 94
Schedule of the Time Box.................................................................................................. 99
Appendix C - Additional Diagrams ................................................................................ 100
State Chart Diagrams ..................................................................................................... 100
Appendix D - Testing Screen Shorts............................................................................... 104
University web view on mobile device ............................................................................ 114
Appendix E - User Manual ............................................................................................. 117
Appendix F Table Creation Cording ........................................................................... 128
Conclusion ....................................................................................................................... 143

4|P ag e

Introduction

5|P ag e

1.1 Introduction
The University of Edima there is no any kind of web based system used at the moment.
Now Edima is using, totally a manual system. So it is very difficult to maintain data
methodically. To maintain a proper way, it is important to store Student Details, Lecture
Details, Lecture Rooms, Course Details and Payment details. And also specially University
of Edima has large number of students following many types of courses. Therefore it is really
difficult task to document each and every one of their information, hard to get and keep hard
copies of their projects, difficult to track students attendance and keep the staff information
and records. At the recent moment University need to implement system linked to a relational
database is required where all the students, supervisors and second markers to use a common
e supervision system handle by an authorize person that the based on the given criteria from
the assignment.

1.2 Proposed System

The proposed system is a secure web based application where you can get an overall idea
about the University of Edima. The system is to register all the students, supervisors, second
markers to the e supervision system authorized by an admin person to handle the system. The
system also should provide facilities to upload students projects, check their attendance,
marks, send emails and chat with their supervisors and second markers to clarify problems
and also to do some dump exam questions to practice before sitting for the actual exam.

1.3 Benefits of the proposed system

Web based applications have evolved significantly over recent years and with improvements
in security and technology there are plenty of scenarios where traditional software based
applications and systems could be improved by migrating them to a web based application.
Below are some of the core benefits of web based applications.

Cross platform compatibility

Most web based applications are far more compatible across platforms than traditional
installed software. Typically the minimum requirement would be a web browser of which
there are many. (Internet Explorer, Firefox, Dolphin, Opera, Android Web View, iPhone
Safari, to name but a few). These web browsers are available for a multitude of operating
systems and so whether users use Windows, Linux or Mac OS, Android phones & tablets,
iOS we can still run our application.

More manageable

Web based systems need only be installed on the server placing minimal requirements on the
end user workstation. This makes maintaining and updating the system much simpler as
usually it can all be done on the server. Any client updates can be deployed via the web
server with relative ease.

6|P ag e

Highly deployable

Due to the manageability and cross platform support deploying web applications to the end
user is far easier. They are also ideal where bandwidth is limited and the system and data is
remote to the user. At their most deployable you simply need to send the user a website
address to log in to and provide them with internet access.

Secure live data

Typically in larger more complex systems data is stored and moved around separate systems
and data sources. In web based systems these systems and processes can often be
consolidated reducing the need to move data around. Web based applications also provide an
added layer of security by removing the need for the user to have access to the data and back
end servers.

Reduced costs

Web based applications can dramatically lower costs due to reduced support and
maintenance, lower requirements on the end user system and simplified architecture.

1.4 Conclusion
In this chapter first explained about the Edima University and It Current System. Then
Explained about the Proposed System and Benefits of it. Finally think this Web based
applications have come a long way and now offer competitive advantages to traditional
software based systems allowing businesses to consolidate and streamline their systems and
processes and reduce costs.

7|P ag e

Description of Existing System

8|P ag e

2.1 Description on Existing system at University of Edima

In university current manual system environment exist some major problems identified at the
system analysis stage. Existing system situation identification and isolation of the issues
provide better framework to decide the initial functional requirements at the inaugural stage.
Following are some of the identified drawbacks of the existing system.
Consume time to search data and process, retrieve information
In the scenes of the current system environment, is a user need to find academic details then
the administrative staff need to search documents manually for submission required
information related to the inquiry. So the process need some time to go through the
documents.
If the management request to generate a report on current students that are not allocated then
the responsible staff need to gather required registers and documents in order to find the
allocated students and make the summarization. It required much time for the finding proper
details.
Lack of proper communication
If a supervisor or a second marker require student allocation details then they have go
through the documents or have to request it from the administration department. Sometimes
they do not know the student have been allocated so communication will take time within the
system.
If any person at academic need to unavoidable circumstances and need to cancel any
appointed work there are no proper massaging or notification mechanism on immediate
situation.
Complexity
In case of any update information regards to second marker. The staff needs to make the
updating on several places on documents but there may have human errors on manual
systems then there were in correct data that relay with some other place. There sometime it
may create collision.
In order to have summarized information on several sections there need to go through several
logs and recoding to gather information.
Wastage of resources use for the documentation and office work
To keep data on university academic related works it need keep most of the details on paper
works. Along with the requirement it needs to have facility with storing, protection,
consumable resources. Then after completion of the student academic process the data
sometimes no longer will have to be used and along with the time it need to be disposed
them.

9|P ag e

2.2 systems used by other universities

To have an idea on supervision system and about the university web page content are
need to be examine in order to gather knowledge on what are the basic functions and system
deliverables for the end user. According to the fact it make easy on identifying the
requirement of a university web base application.

2.2 Existing systems used by other universities

University College Dublin
The students of UCD uploads their projects and assignments.

Figure 1(Interface of University College Dublin Students upload their

projects and assignments.)

10 | P a g e

University of Moratuwa
Referred to the site to get an idea of the interface of the system.

Figure 2(Interface of University of Moratuwa)

11 | P a g e

University of Macquarie

Figure 3(Interface of University of Macquarie)

12 | P a g e

Requirement Annalysis

13 | P a g e

3. Requirement Analysis
System development can generally be thought of having two major components: systems
analysis and systems design. In System Analysis more emphasis is given to understanding the
details of an existing system or a proposed one and then deciding whether the proposed
system is desirable or not and whether the existing system needs improvements. Thus, system
analysis is the process of investigating a system, identifying problems, and using the
information to recommend improvements to the system. This chapter describes how to gather
requirements for the development of the system. Also categorize the functional and non
functional requirements from identified features that have to be in the system for university of
Edima.

3.1 What is Requirements Gathering?

Requirements gathering are an essential part of any project and project management. Understanding
fully what a project will deliver is critical to its success. This may sound like common sense, but
surprisingly it's an area that is often given far too little attention.
Many projects start with the barest headline list of requirements, only to find later the customers'
needs have not been properly understood.
One-way to avoid this problem is by producing a statement of requirements. This document is a guide
to the main requirements of the project. It provides:

A succinct requirement specification for management purposes.

A statement of key objectives - a "cardinal points" specification.
A description of the environment in which the system will work.
Background information and references to other relevant material.
Information on major design constraints.

The contents of the statement of requirements should be stable or change relatively slowly. Once you
have created your statement of requirements, ensure the customer and all other stakeholders sign-up to
it and understand that this and only this will be delivered. Finally, ensure you have cross-referenced
the requirements in the statement of requirements with those in the project definition report to ensure
there is no mismatch.

There are different types of techniques used to gather requirements to develop the system for
university of Edima. Mainly identified the requirements by going through the scenario and
also referred to some similar portals and sites to collect information to develop the system.

3.2 What are the Requirements Gathering Methods?

Existing Web Sites

Virtually go to the Institute

Old Documentations

14 | P a g e

Rich Picture, use case Diagrams,

Requirement Catalogue and
System Specification

15 | P a g e

4.1 Rich Picture Description

Rich Picture is a method of approaching Soft Systems Methodology (SSM), and it
demonstrates the problematical circumstances and drawn in a diagram with pictures and
characters as symbols. The reason behind of the rich picture is drawing thorough
understanding on current system of an organization and a way to find problems in a
professional manner.

4.2 Rich Picture for current system at the University of Edima

According to the above rich picture it clearly demonstrates the existing system of the
University of Edima. Therefore we have point out some facts in terms of people who
involved and the structure of the University of Edima, based on the rich picture, there
areconflicts between Supervisor, Student, Second Marker and Authorized Member.

4.3 Current conflicts which the University of Edima is facing

Firstly, the existing System at the University of Edima does not meet the requirement
for staffs to accessing on Mobile, Tablet and PC devices. Therefore users find some
difficulties of accessing the system whenever they to get information from the
university. As a result of this, it is a good option for the new system to be supported to
access by any device.
Secondly, there will be a conflict between supervisor, student and second marker for
sending e-mails regarding project due to all students. Sending emails for every inquiry
taking so much time. Therefore introducing a chatting option in the system makes
easy to interact with everyone in the university.
Thirdly, there will be a conflict between authorized member and the student due to 10
students allocate from 1 supervisor and second marker.As each supervisor and second
marker are been assigned for 10 students and it is not send 10 separate email
notifications for 10 students. Sending 10 emails at once resolve this problem in the
new system.
16 | P a g e

4.4 Rich Picture of University of Edima

Sponsors

eSupervision
University of Edima

Suitable for all

device

Mobile Device

MIS System

Send emails related

to project

Send emails related

to project

Student
Second Marker

Supervisor

10 students allocate to
1 supervisor and
second marker

Allocate
supervisor and
second marker

17 | P a g e

Authorized
Member

Can access everyones

dashboard

Figure 4(Rich Picture of University of Edima)

4.5 Use case Diagram

Student
Second Marker
Supervisor

Registration

Create Credentials

Pay Fees
Supervisor
Project Details

Authorized User
Project Document
Project Comments

Results

Input Marks

Student Attendance

Second Marker
Attend for Meeting

Tutorial Videos

Dump Exams

View Reports

Figure 5(Use case Diagram)

18 | P a g e

Student

4.6 Primary Scenario of the Use Case

Use Case

Registration

Precondition

Register Supervisors, Second Markers and Students to the system

Flow of Events

1. Authorized user login to the system

2. Select Supervisors, Second Markers or Students to be registered
3. Fill in all the details
4. Click update

Post Condition

Successfully registered to the system

Use Case

Create Credentials

Precondition

Generate login credentials for users

Flow of Events

1. Authorized user login to the system

2. Create username
3. Create password
4. Generate the credentials

Post Condition

Successfully created the credentials

Use Case

Pay fees

Precondition

Make payments for the program follows

Flow of Events

1. Register with the university

2. Select the program to be followed
3. Make payments
4. Click update

Post Condition

19 | P a g e

Made payments for the program

Use Case

Project Details

Precondition

View the project information

Flow of Events

1. Login to the system

2. Upload comments
3. Upload document

Post Condition

Successfully uploaded

Use Case

Results

Precondition

View project results

Flow of Events

1. Login to the system

2. Navigate to the results tab
3. View results

Post Condition

Successfully view the results

Use Case

Student Attendance

Precondition

Record the attendance information

Flow of Events

1. Record the attendance at the machine

2. Download to the system
3. Generate the report

Post Condition

20 | P a g e

Track on students attendance

Use Case

Attend for meeting

Precondition

Interact with others

Flow of Events

1. Login to the system

2. Join for meeting
3. Input comments

Post Condition

Share information successfully

Use Case

Tutorial Video

Precondition

Guide users how to use the system

Flow of Events

1. Login to the system

2.Navigate to the tutorial video tab
3. Search for videos
4. Watch the videos

Post Condition

Successfully watched videos regarding the system

Use Case

Dump Exam

Precondition

Practice exam questions

Flow of Events

1. Login to the system

2. Select the subject
3. Run the exam paper
4. Select answers
5. Submit
6. Get the results

Post Condition

21 | P a g e

Successfully complete the dump exam paper

Use Case

View Reports

Precondition

Generate reports

Flow of Events

1. Login to the system

2. Select the report needed
4. Select the report type
5. Select the date range
6. Generate the report

Post Condition

22 | P a g e

Save or print the report

4.7 Secondary Scenario of the Use Case

Use Case

Registration

Precondition

Register Supervisors, Second Markers and Students to the system

Flow of Events

1. Authorized user login to the system

2. Select Supervisors, Second Markers or Students to be registered
3. Fill in all the details
4. Click update

Alternative Path

In step 2, If the type if the user is not selected, It will ask to select
the type.
In step 3, All the details have to be filled up before click update

Post Condition

Successfully registered to the system

Use Case

Create Credentials

Precondition

Generate login credentials for users

Flow of Events

1. Authorized user login to the system

2. Create username
3. Create password
4. Save the credentials

Alternative Path

In step 3, Password has to be minimum of 8 digits. If not it

doesnt allow to save

Post Condition

Successfully created the credentials

23 | P a g e

Use Case

Pay fees

Precondition

Make payments for the program follows

Flow of Events

1. Register with the university

2. Select the program to be followed
3. Make payments
4. Click update

Alternative Path

In step 2, If the program is not selected, gives an error message

when updating

Post Condition

Made payments for the program

Use Case

Project Details

Precondition

View the project information

Flow of Events

1. Login to the system

2. Upload comments
3. Upload document

Alternative Path

In step 3, The document has to be in PDF format

Post Condition

Successfully uploaded

Use Case

Results

Precondition

View project results

Flow of Events

1. Login to the system

2. Navigate to the results tab
3. View results

Alternative Path

In step 1,Students have to login with their username and password

to check the results

Post Condition

Successfully view the results

24 | P a g e

Use Case

Student Attendance

Precondition

Record the attendance information

Flow of Events

1. Record the attendance at the machine

2. Download to the system
3. Generate the report

Alternative Path

In step 2, The data has to be downloaded to the system to check

the attendance

Post Condition

Track on students attendance

Use Case

Attend for meeting

Precondition

Interact with others

Flow of Events

1. Login to the system

2. Join for meeting
3. Input comments

Alternative Path

In step 2, Need to join with the correct meeting

Post Condition

Share information successfully

Use Case

Tutorial Video

Precondition

Guide users how to use the system

Flow of Events

1. Login to the system

2.Navigate to the tutorial video tab
3. Search for videos
4. Watch the videos

Alternative Path

In step 3, If the entered keyword is not matched, shows a message

records not found

Post Condition

Successfully watched videos regarding the system

25 | P a g e

Use Case

Dump Exam

Precondition

Practice exam questions

Flow of Events

1. Login to the system

2. Select the subject
3. Run the exam paper
4. Select answers
5. Submit
6. Get the results

Alternative Path

In step 4, All the questions have to be answered

Post Condition

Successfully complete the dump exam paper

Use Case

View Reports

Precondition

Generate reports

Flow of Events

1. Login to the system

2. Select the report needed
4. Select the report type
5. Select the date range
6. Generate the report

Alternative Path

In step 4, Need to select the type of the report

Post Condition

Save or print the report

26 | P a g e

4.8 Requirement Identification

In order to identify the requirements analyst conduct a preliminary investigation to evaluate
the requirements that needs priority on system development. It is not subjected to the design
study only include the collection of the details that new system needs to satisfy the end user.
It can be done by the existing document review, by observing the current system process and
conducting interviews etc
Since the development adopt the agile scrum development practices it guide to analyse the
requirement up to current date and the advice to amend the changes at the later releases of the
system documentations.

4.8.1 Identify the requirement for the new system

eSupervision web application functionality need to satisfy the requirements and manage the
interaction between supervisors and second marker allocated for the students on their
academic process in university environment. Therefore system needs to be operating on
behalf of the end users and the administrative staff collaboration to serve better for the
existing problem domains.
On following section it describes the requirement catalogues identified and functional and
non functional activities along with the requirements of the system.

4.8.2 Requirement catalogues

The main objective of the requirement catalogue is to identify and evaluate the major system
requirements on user perspective, catalogue consist of separated entries depicted as on below
entries. Requirement/ Problem catalogue entry contain the details gather at the investigations
process. It has included the functional and non functional requirement that has been identified
in order to satisfy the user requirements. On each entry include the verification and validation
method that can be used for further references.
According to the requirement catalogue the development team can identify the initial
requirements to be develop when the start of the small set of development and if there were
time it can consider the system enhancement requirement that can adopt form the non
functional requirements.

4.5.3 Functional Requirements

Registration has to be done for all the students and for the staff by the authorized
staff
Students should be able to upload their projects to the system
Update feedbacks and comments to projects
Should have own dashboard
Ability to communicate through a chat
Ability to dump exam questions
Show the marks and the results of subjects
27 | P a g e

 Record students attendance

Send 10 emails for 10 students simultaneously

4.8.4 Non Functional Requirements

Should be accessible for number of users simultaneously
Compatible with all the mobile devices
Automatically logout after 1 minute if not working on the portal

4.9 Requirement Catalogue Screen shots

28 | P a g e

Figure 6 Requirement catalog-Register

Figure 7 Requirement catalog-Login

29 | P a g e

Figure 8 Requirement catalog-Projects

Figure 9 Requirement catalog-Dashboard and Profile manage

30 | P a g e

Figure 10 Requirement catalog-Scheduling students, supervisors and markers

Figure 11 Requirement catalog-Generate Reports

31 | P a g e

Figure 12 Requirement catalog-Email Notifications

Figure 13 Requirement catalog-Comments

32 | P a g e

System Design

33 | P a g e

5.2 ER Diagram

Sup_ID

M_ID
1

A_Date

Play

Supervisor

Meeting

Attendance
1

Record

Conduct
Role_ID
1
1

Play
1

Role
M

Has

Has

User

T_ID

St_ID

User_ID
1

Student

Watch

Tutorial

Play
Submit
1
S_Marker
Write

N
Comment

Add

1
Update Document

Upload

M
Project

S_Marker_ID
Com_ID

Figure 14(ER Diagram Of Proposed System)

34 | P a g e

Doc_ID

Project_ID

Database Designs
Attendance

Figure 15 Attendance Table

Comment

Figure 16 Comment Table

35 | P a g e

Meeting

Figure 17(Meeting Table)

Message

Figure 18 Message Table

36 | P a g e

Project

Figure 19 Project Table

Role

Figure 20 Role Table

37 | P a g e

Second_Marker

Figure 21 Second Marker Table

Student

Figure 22 Student table

38 | P a g e

Supervisor

Figure 23 Supervisor Table

University_Blog

Figure 24 University Blog Table

39 | P a g e

Upload_document

Figure 25 Upload Document Table

Users

Figure 26 Users Table

40 | P a g e

5.3 Class Diagram

Figure 27(Class Diagram)

41 | P a g e

5.4 Sequence Diagrams

User Login Process

Figure 28(Sequence Diagram for User Login Process)

42 | P a g e

Upload Document Process

Figure 29(Sequence Diagram for Upload Document Process)

43 | P a g e

Meeting Process

Figure 30(Sequence Diagram for Meeting Process)

44 | P a g e

Project Comment process

Figure 31(Sequence Diagram for Project Comment process)

45 | P a g e

Attendance process

Figure 32(Sequence Diagram for Attendance process)

46 | P a g e

Allocate Staff Process

Figure 33(Sequence Diagram for Allocate Staff Process)

47 | P a g e

5.5 Collaboration Diagrams

User Login Process

Figure 34(Collaboration Diagram for User Login Process)

Upload Document Process

Figure 35(Collaboration Diagram for Upload Document Process)

48 | P a g e

Meeting process

Figure 36(Collaboration Diagram for Meeting process)

Project Comment Process

Figure 37(Collaboration Diagram for Project Comment Process)

49 | P a g e

Attendance Process

Figure 38(Collaboration Diagram for Attendance Process)

Allocate Staff Process

50 | P a g e

Figure 39(Collaboration Diagram for Allocate Staff Process)

51 | P a g e

5.6 Activity Diagrams

Login Process

Figure 40(Activity Diagram for Login Process)

52 | P a g e

Meeting process

Figure 41(Activity Diagram for Meeting process)

53 | P a g e

Mail Process

Figure 42(Activity Diagram for Mail process )

54 | P a g e

File List Process

Figure 43(Activity Diagram for File List process)

55 | P a g e

Reports Process

Figure 44(Activity Diagram for Report process )

56 | P a g e

User Allocation Process

Figure 45(Activity Diagram For User Allocation Process)

57 | P a g e

Blog

Figure 46(Activity Diagram For Blog)

58 | P a g e

Upload Process

Figure 47(Activity Diagram For Upload Process)

59 | P a g e

5.7 Component Diagram

Registration

Upload
Upload documents

Student Registration

Upload Assignments

Staff Registration

Figure 49(Upload Component)

Reports
Exception Report

Figure 48 (Registration Component)

Allocation
Allocate by second marker

Managing Report

Figure 51(Reports Component)

Meetings
Meetings with student and supervisor

Figure 50(Allocation Component)

E-mail of Students
Email notification for student

Meetings with student and second

marker

Figure 52(Meetings Component)

Blogging
Discussion with supervisor and
student
Discussion with second marker and
student
Figure 54(Blogging Component)
60 | P a g e

Figure 53(Email of Students Component)

5.8 Wire Frames

Meeting of Students

Logo
Link1

New Meeting

Link2

Link3

List of Meeting

Allocated Lectures

Meeting

Meeting

Meeting

Figure 55(Wire Frame for Meeting of Students)

61 | P a g e

Link4

Link5

Mail of Students

Logo

Link1

Link2

New Mail

Link3

Link4

Link5

Link4

Link5

Mail List

Figure 56(Wire Frame for Mail of Students)

Upload Project Process

Logo
Link1

Link2

Links

Upload New File

View Uploaded
Files

Select Document

Upload

Figure 57(Wire Frame for Upload Project)

62 | P a g e

Link3

Choose File

Online Registration Process

Logo
Link1

Link2

Link3

New User
User Name
User Type
Password
Confirm
First Name
Last Name
Email
Tel-No

Register

Figure 58(Wire Frame for Registration Process)

63 | P a g e

Link4

Link5

Allocation Process

Logo
Link1

Link2

Link3

Allocate

Active
Student ID
Supervisor ID
Second Marker ID

Active
Student ID
Supervisor ID
Second Marker ID

Allocate

Figure 59(Wire Frame for Allocation Process)

64 | P a g e

Link4

Link5

Questions

Logo
Link1

Link2

Link3

Create Sample MCQ exam

MCQ Title
Question 1
Answers
1.
2.
3.
4.

Correct Answer

Submit

Choice 1

Clear

Figure 60(Wire Frame for Questions)

65 | P a g e

Link4

Link5

5.8.1 Wire Frames Mobile View

User Registration

Logo

Link 1
Link 6

Link 2

Link 3

Link 4

Link 5

Link 7
New User
User ID

User Type

Password

Confirm

Figure 61(User Registration Form Mobile View)

66 | P a g e

Allocation Process

Figure 62(Allocation Process Mobile View)

67 | P a g e

Upload Project Process

Figure 63(Upload Project Process Mobile View)

68 | P a g e

5.9 Site Map

Admin Panel

Figure 64(Site Map For Admin Panel)

Student Panel

Figure 65(Site Map for Student Panel)

69 | P a g e

Second Marker

Figure 66(Site Map for Second Maker Panel)

Supervisor

Figure 67(Ste map for Supervisor panel)

70 | P a g e

Development Methodologies

71 | P a g e

6. 1 what kind of Methodologies used for System Development?

Agile software development refers to a group of software development methodologies based
on iterative development, where requirements and solutions evolve through collaboration
between self-organizing cross-functional teams.
Agile methods or Agile processes generally promote a disciplined project management
process that encourages frequent inspection and adaptation, a leadership philosophy that
encourages teamwork, self-organization and accountability, a set of engineering best
practices intended to allow for rapid delivery of high-quality software, and a business
approach that aligns development with anybodies goals.

1.2 What is Scrum?

Scrum is an agile methodology that can be applied to nearly any project; however, the Scrum
methodology is most commonly used in software development. The Scrum process is suited
for projects with rapidly changing or highly emergent requirements. Scrum software
development progresses via a series of iterations called sprints, which last from one to four
weeks. The Scrum model suggests each sprint begins with a brief planning meeting and
concludes with a review.
Scrum meeting is a technique of developing software product with a team. The development
divides into small portions and assign to the team members. This is a good technique when
developing complex systems.
Scrum Roles
Scrum has three roles: Product Owner, Scrum Master, and Development Team.
Product Owner
The Product Owner should be a person with vision, authority, and availability. The
Product Owner is responsible for continuously communicating the vision and
priorities to the development team.
Its sometimes hard for Product Owners to strike the right balance of involvement.
Because Scrum values self-organization among teams, a Product Owner must fight
the urge to micro-manage. At the same time, Product Owners must be available to
answer questions from the team.
Scrum Master
The Scrum Master acts as a facilitator for the Product Owner and the team. The
Scrum Master does not manage the team. The Scrum Master works to remove any
impediments that are obstructing the team from achieving its sprint goals. This helps
the team remain creative and productive while making sure its successes are visible to
the Product Owner. The Scrum Master also works to advise the Product Owner about
how to maximize ROI for the team.
72 | P a g e

 Development Team
According to Scrums founder, the team is utterly self managing. The development
team is responsible for self organizing to complete work. A Scrum development team
contains about seven fully dedicated members, ideally in one team room protected from
outside distractions.
An agile Scrum process benefits the organization by helping it to

Increase the quality of the deliverables

Cope better with change (and expect the changes)
Provide better estimates while spending less time creating them
Be more in control of the project schedule and state

Our Project Development Team

Figure 68(Our Team)

73 | P a g e

System Testing

74 | P a g e

7. What is Testing?
Testing is a process to find whether the provided solution satisfies its requirements. Testing
used to find the gaps between solution and requirement and do the necessary arrangements to
minimize those gaps. During testing errors and missing requirements are found and have to
correct these issues. University of Edima, there are requirements and have to identify gaps
and errors and must correct those errors.
Software Testers, Software Developers, Project Managers and End Users are involved for
testing. Early involvement of testing reduces cost. Testing is a never ending process. No one
can say testing 100% completed. To finalize testing must declare testing deadlines,
completion of test case, high priority bugs are identified and bug rate falls below a certain
level etc.

7.1 What is Verification, Validation, Defect finding?

Software testing has three main purposes There are Verification, Validation and Defect
finding.
The verification process confirms software meets technical specifications. We can ask are
you building it right. It checks all the functions are working properly. Verification done by
developers.
The validation process confirms software meets the business requirements. We can ask are
you building the right thing. It checks the functions match with the requirements. Validation
done by testers.
A defect is a variance between the expected and actual result.

7.2 Test Cases

Student Login Page
Step
NO

STEP

EXPECTED RESULT

Status

1.1

Enter web address

http://dwguilder.byethost7.com/edima/

Load login page

OK

2.1

Enter Valid Username & Valid

Password & click Login

Home page must be

displayed

OK

2.2

Enter Valid Username & Invalid

Password & Click Login

Error message must be

displayed

OK

2.3

Enter Invalid Username & valid

Password & Click Login

Error message must be

displayed

OK

2.4

Enter Invalid Username & Invalid

Error message must be

OK

75 | P a g e

Password & Click Login

displayed

3.1

Click Meetings Tab

Display scheduled
Meetings & Supervisor
& Second marker
allocated

OK

3.2

Click New Meeting Link

Display create new

meeting window

OK

3.3

Enter Meeting Date, Time & Description Meeting created &

and Click on Create
automatically mail sent
to allocated supervisor
and second marker

OK

4.1

Click Mail Tab

Display Received mails

OK

4.2

Click New Mail & enter To, Title and

Message & Click Send

Message sent and

displayed in sent items

OK

5.1

Click on Uploads

Display upload new file

screen

OK

5.2

Select a Document & Click Upload

Uploaded document

OK

5.3

Click on View Uploaded Files

Display Document id,

document name &
uploader

OK

6.1

Click on Attendance Tab & Select Mark

in Time & Mark out time

Show the previous

meetings attended and
about to be attended

OK

7.1

Click on Blog Tab

Display blog

OK

8.1

Click on Contact Us

Display contact details

of the university

OK

9.1

Click on Logout

Log out from University OK

website

Figure 69(Test Case for Student Login Page)

76 | P a g e

Supervisor Login Page

Step
NO

STEP

EXPECTED RESULT

Status

1.1

Enter web address

http://dwguilder.byethost7.com/edima/

Load login page

OK

2.1

Enter Valid Username & Valid

Password & click Login

Home page must be

displayed

OK

2.2

Enter Valid Username & Invalid

Password & Click Login

Error message must be

displayed

OK

2.3

Enter Invalid Username & valid

Password & Click Login

Error message must be

displayed

OK

2.4

Enter invalid Username & Invalid

Password & Click Login

Error message must be

displayed

OK

3.1

Click Meetings Tab

Display scheduled
Meetings & Supervisor
& Second marker
allocated

OK

4.1

Click Mail Tab

Display Received mails

OK

4.2

Click New Mail & enter To, Title and

Message & Click Send

Message sent and

displayed in sent items

OK

5.1

Click on Uploads

Display upload new file

screen

OK

5.2

Select a Document & Click Upload

Uploaded document

OK

5.3

Click on View Uploaded Files

Display Document id,

document name &
uploader

OK

61

Click on Blog Tab

Display blog

OK

7.1

Click on Contact Us

Display contact details

of the university

OK

8.1

Click on Logout

Log out from University OK

website

Figure 70(Test Case for Supervisor Login Pag

77 | P a g e

Second Marker Login Page

Step
NO

STEP

EXPECTED RESULT

Status

1.1

Enter web address

http://dwguilder.byethost7.com/edima/

Load login page

OK

2.1

Enter Valid Username & Valid

Password & click Login

Home page must be

displayed

OK

2.2

Enter Valid Username & Invalid

Password & Click Login

Error message must be

displayed

OK

2.3

Enter invalid Username & valid

Password & Click Login

Error message must be

displayed

OK

2.4

Enter Invalid Username & Invalid

Password & Click Login

Error message must be

displayed

OK

3.1

Click Meetings Tab

Display scheduled
Meetings & Supervisor
& Second marker
allocated

OK

4.1

Click Mail Tab

Display Received mails

OK

4.2

Click New Mail & enter To, Title and

Message & Click Send

Message sent and

displayed in sent items

OK

5.1

Click on Uploads

Display upload new file

screen

OK

5.2

Select a Document & Click Upload

Uploaded document

OK

5.3

Click on View Uploaded Files

Display Document id,

document name &
uploader

OK

61

Click on Blog Tab

Display blog

OK

7.1

Click on Contact Us

Display contact details

of the university

OK

8.1

Click on Logout

Log out from University OK

website

Figure 71(Test Case for Second Marker Login Page)

78 | P a g e

Admin User Login Page

Step
NO

STEP

EXPECTED RESULT

Status

1.1

Enter web address

http://dwguilder.byethost7.com/edima/

Load login page

OK

2.1

Enter Valid Username & Valid

Password & click Login

Home page must be

displayed

OK

2.2

Enter Valid Username & Invalid

Password & Click Login

Error message must be

displayed

OK

2.3

Enter invalid Username & valid

Password & Click Login

Error message must be

displayed

OK

2.4

Enter invalid Username & Invalid

Password & Click Login

Error message must be

displayed

OK

3.1

Click Meetings Tab

Display scheduled
Meetings & Supervisor
& Second marker
allocated

OK

4.1

Click Mail Tab

Display Received mails

OK

4.2

Click New Mail & enter To, Title and

Message & Click Send

Message sent and

displayed in sent items

OK

5.1

Click on Uploads

Display upload new file

screen

OK

5.2

Select a Document & Click Upload

Uploaded document

OK

5.3

Click on View Uploaded Files

Display Document id,

document name &
uploader

OK

61

Click on Blog Tab

Display blog

OK

7.1

Click on Allocate Tab & Enter Student

id, supervisor id and second marker id
Click Allocate

Successfully Allocated
Message Appear

OK

7.1

Click on Contact Us

Display contact details

of the university

OK

8.1

Click on Logout

Log out from University OK

website

Figure 72(Test Case for Admin Login Page)

79 | P a g e

7.3 Sample Acceptance Test questions

1. Do you Satisfied using this System?
Not at all
No, not much
A little bit
Fairly complicated
Yes, Very much

2. What do you feel that the system is user friendly?

Yes of course
Yes, but not all
Not much
Not at all
A little
3. Do you satisfy about our site interface designs?
Not much
Yes, but not all
Yes, Very much
Not at all
A little bit

4. What is your opinion regarding reports of the system?

Yes, Very Useful
Yes, Enough
Need Improvements

80 | P a g e

System Implementation

81 | P a g e

8. System Implementation
8.1 System Implementation Strategies
There are four strategies for implementing a new system
1. Parallel
2. Phased
3. Pilot
4. Direct
Phased is an useful strategy for systems that are made up of smaller sub-systems. The idea is
to introduce each sub-system one at a time.
Pilot is a popular approach when they want to evaluate the performance and qualities of the
system before committing to it throughout the organization.
Direct Implement approach, the system is implemented and tested to ensure it performs
properly. Then the old system is removed and the new one put in its place without any
overlap or limited roll out. And also
This is a risky strategy as any issues with the new system may have an immediate impact on
the day to day activity of the organization.
Among these four strategies we selected parallel for implementing our system. This is a very
popular method as it is relatively low risk. The idea is to run the old system alongside the
new system for a while. With this approach, the outputs or behavior of each system can be
compared to make sure that the new system is performing as expected. If a serious problem is
found, then the Edima can just carry on using the existing system until a fix has been put in
place.

82 | P a g e

8.2 Implementation Diagram

Figure 73 (Implementation Diagram)

83 | P a g e

Critical Appraisals

84 | P a g e

9. Critical Appraisals
9.1 Problems faced
When implementing this system I faced different problem. We run this web site firefox browser
but when sometimes We used google chrome for running the web site completely different the
design such as appearance, font size, colors And also ActiveX disable in firefox so we designed
pages in ActiveX not working. And we used pixels to web page(not using Percentage)completely
design will changed.

Therere lot of web browsers and browser versions using by employees. So the biggest
Problem we faced is producing a same user experience for each users. It was very hard
to support for old technologies.
The Web Socket technology is a great technology to synchronize data between server
and users browser with using only one static connection. This is solves unnecessary
issues and connection latency.

9.2 Lesson Learned

In this task We implement a web site and database system. Now I know about the creation of web
sites deeply. How to design a web site how to make a system from web site. And also get a
knowledge about php cording. For create a data base for my designing website. So I get a many
knowledge about database side. Besides improve a knowledge about sql queries and how error
handling when query writing.

we identified a great open source HTML5 framework maintained by thousands of developers

called Twitter bootstrap. That framework allows designers to cross browser responsive web
application. Cross browser means it can support large range of browsers to design same
looking web interfaces and responsive means its can support to auto resize web pages by
users Screen resolution. So weve chosen this tool to implement our user interfaces.

9.3 Future Enhancements

The computerized system introduced to Edima is has proven to function successfully.
Although the system is new, in time with to keep with website and its processes the system
will have to be upgraded in the future. New features and functions will have to be added to
the website
Email Notification System:
Students & staff would like to get their system notifications via email. Since theyre always
connected with email clients, they can easily catch new notification Without opening our
application. And also students assignment deadline inform by sending e mail Notification

85 | P a g e

Allow admins to create custom form types dynamically

Currently the system is only supporting for pre-defined form types only. So, I Edima
wants to add a new form type to the system, weve write new codes. To avoid this, we
can create this system to create new form types dynamically. Then system admin can
create new form types visually and enter to exchange.
Allow students to chat with Lecturers
In some cases when doing projects students face many problems. So in that time its
better if a student can chat through the website with lecturers. That chat facility should
only accessible by current students.

9.4 Weaknesses of the System

Necessitates a redesign of your website
With the intention of implementing Responsive Website Design (RWD) on a website
we have to use a simple adaptive website layout and that usually requires going through
major redesign of existing web site.
It takes time
If you want your website to be launched at an earlier period of time, responsive web
design cannot be the best choice as it takes additional time as well as effort. The usual
time of creating a responsive web design is usually 10% more than the time required
for a typical website. Yet when using Content Management System (CMS) and
frameworks the development of a responsive website will be finish earlier but still it
depends to the developer.
Your mobile traffic is less than 5%
If your website is receiving less than 5%of mobile traffic, then going for a responsive
Web design is not a wise choice; it is better to utilize your budget somewhere else.

86 | P a g e

10. References
Impementation Strategies [online]. (2015). Available from: <http://www.teachict.com/as_a2_ict_new/ocr/A2_G063/335_implementing_systems/methods/miniweb/pg6.
htm>. [Accessed 10 April 2015].

Moratuwa University site [online]. (2015). Available from: <http://www.mrt.ac.lk/web/>.

[Accessed 20 March 2015].
University of Dublin Web site [online]. (2015). Available from: <http://www.ucd.ie/>.
[Accessed 18 March 2015].

University of macquarie Web site [online]. (2015). Available from:

<https://www.google.lk/?gws_rd=cr>. [Accessed 20 Apil 2015].

87 | P a g e

Appendix A - Gantt Chart

88 | P a g e

89 | P a g e

Figure 74(Gantt Chart of a Proposed System)

90 | P a g e

Appendix B
Project Management

Figure 75 (Project management Stages)

In the management stage it decide the way that the project need to be handle and the featured
functions that are need to implemented on eSupervision system is finalized according to
DSDM development technique define as MoSCoW prioritization. According to the technique
the functional high level requirements categorizes as Must have, Could have, Should have,
Could have categorization. Those requirements need to be divided into smaller modules and
perform on development with a timebox. After each deliverable it expect have feedbacks on
completed module that can be run and if there were any changes over requirement it is
acceptable by the approach without affecting the completed modules.
On each stages there were planned scrum meeting sessions regard to the development with
team members to analyze the progress and then discuss the changes on requirement. On
scrum meetings team members discuss about the future developments and decide the next
meeting and the things need to be completed, problems associated with previous development
stages. This practice will help to avoid conflicts on the development.

Development Project Team

In order to deliver a successful system there must be team with proper collaboration. This
constrain will be the foundation for a perfect development and to accomplish this task team
need to have proper understand on roles and responsibilities of the assigned role and each
member must put their best effort on development as guided by the agile scrum methodology.

91 | P a g e

Figure 76 (Project Development Life Cycle)

As depicted on above all team members assigned for the each allocated job must contribute
their best effort on the development and all roles are depending on each other. There may be
several roles are allocated for the same person. Because the development divided in small
modules and one person can participate in separate processes.
For the Edima university web application development were five members of a team
in order to achieve intended target within two months of a time period. This process includes
planning to execution of the development in to live environment. The following are the team
member details participate for the development.

Figure 77 (Our Team Members Job Roles Table)

92 | P a g e

Roles and responsibility of the team

Project Coordinator
In the Edima University web development team guidance person was the project coordinator
and responsible on planning, directing the team members time to time with related to the
development process and project activities. This role not only includes the corporation with
project team it also required to continue coordination with the end users and the stakeholders
in the university.
The person need to ensure the development was going on the right direction and coordination
has to be made throughout the project.
Database designer
Role of the database designer include the present the requirements of the users in a
convenient approach with the data stored on database. It needs to concentrate on database
development activities and the architecture of the database.
Web Designer
Responsible on designing the web interfaces and need to consider the way of the system look
like to the user. This is the only way that can user of the system can understand and they
might not needed to know the internal process. They were response to the external
appearance of the Edima web application.
System Designer
Consider on the design specification and the documents that provide basement for the
development. Need to have proper idea on the system operation along with the end user
requirement. If the correct designs are not been finalized then the whole system drags in to a
failure.
Programmer
According to the specification and the diagrams, person was responsible on building the
source codes for the application. In this system uses PHP, SQL etc
Tester
Test and evaluates the possible outcome of the system operations in order to satisfy the high
level requirements of the users. Person need to find the errors on the system and identify the
occurrences and inform to the team.

User Trainer
End users or the operational staff in the university needs to know about how the operations
need to be handled. Therefore it need to conduct training sessions on user level and
university system need to create recording of functionality of the system and a user manual.
93 | P a g e

Meeting Minutes
Minutes of meeting
Meeting Number: 001
Date: 8/2/2015

Time: 2.00pm-3.30pm

Participants:
1. Mr. J.L.T Manjula De Silva
2. Mr. Yasiru Edirisingha
3. Mr. Dilan
4. Ms.Ireni Hansika
5. Mr.Indika Rathnayaka
Main things had been focused:

Discuss on the main requirements of the system

Discuss on the main functionalities of the system

Task responsibilities until next meeting:

Mr. Manjula Identify the main functionalities of the system

Mr. Yasiru Identify the entities and the attributes for the database

Mr. Dilan Refer to other university esupervision systems

Ms.Ireni _ Requirement Annalysis

Mr.Indika _ Identify how

Milestones havent been met and problems arisen:

Solution agreed:

Date for next meeting: 15/2/2015

Figure 78 (Meeting Number: 001)

94 | P a g e

Minutes of meeting
Meeting Number: 002
Date: 15/2/2015

Time: 4.00pm-4.30pm

Participants:
1. Mr. J.L.T Manjula De Silva
2. Mr. Yasiru Edirisingha
3. Mr. Dilan
4. Ms.Ireni Hansika
5. Mr.Indika Rathnayaka
Main things had been focused:

Finalize the functional and non functional requirements

Finalize the entities of the database

Task responsibilities until next meeting:

Mr. Manjula Prepare the use case diagram

Mr. Yasiru Prepare the ER diagram

Mr. Dilan Prepare the prototype for the system

Ms. Ireni _ Create Primary & Secondary scenario of the System

Mr. Indika _ Draw Wireframes

Milestones havent been met and problems arisen:

There were some arguments on some of the functional requirements

whether to include or not.

Number of tables of the database

To proceed with including the other functional requirements

To use many tables

Solution agreed:

Date for next meeting: 22/2/2015

Figure 79(Meeting Number: 002)

95 | P a g e

Minutes of meeting
Meeting Number: 003
Date: 22/2/2015

Time: 8.30am-9.00am

Participants:
1. Mr. J.L.T Manjula De Silva
2. Mr. Yasiru Edirisingha
3. Mr. Dilan
4. Ms.Ireni Hansika
5. Mr.Indika Rathnayaka
Main things had been focused:

Discuss the use case diagram base on the functional requirements

Finalize the ER diagram

Discuss on the prototype of the system

Task responsibilities until next meeting:

Mr. Manjula & Dilan Discuss on the interface of the system

Mr. Yasiru Finalize the entities, attributes and data type

Ms.Ireni _ Draw Component Diagram

Mr. Indika _ Draw Sequence Diagram

Milestones havent been met and problems arisen:

Solution agreed:

Date for next meeting: 1/3/2015

Figure 80(Meeting Number: 003)

96 | P a g e

Minutes of meeting
Meeting Number: 004
Date: 1/3/2015

Time: 8.00am-9.00am

Participants:
1. Mr. J.L.T Manjula De Silva
2. Mr. Yasiru Edirisingha
3. Mr. Dilan
4. Ms.Ireni Hansika
5. Mr.Indika Rathnayaka
Main things had been focused:

Finalize the design of the system

Discuss on the diagrams

Task responsibilities until next meeting:

Mr. Manjula Develop the database and draw use case and ER
diagram

Mr. Yasiru & Dilan Develop the system

Ms.Ireni Draw State Chart Diagram

Mr.Indika Create Requirement Catalogue

Milestones havent been met and problems arisen:

Solution agreed:

Date for next meeting: 8/3/2015

Figure 81(Meeting Number: 004)

97 | P a g e

Minutes of meeting
Meeting Number: 005
Date: 8/3/2015

Time: 4.00pm-4.30pm

Participants:
1. Mr. J.L.T Manjula De Silva
2. Mr. Yasiru Edirisingha
3. Mr. Dilan
4. Ms.Ireni Hansika
5. Mr.Indika Rathnayaka
Main things had been focused:

Progress of developing the site

Discuss on the diagrams

Task responsibilities until next meeting:

Mr. Manjula & Dilan Continue developing the system and draw
sequence diagram

Mr. Yasiru Draw the activity diagrams

Ms.Ireni _ Create a User Manual

Mr.Indika Draw Implementation Diagram

Milestones havent been met and problems arisen:

Solution agreed:

Date for next meeting: 15/3/2015

Figure 82 (Meeting Number: 005)

98 | P a g e

Schedule of the Time Box

Time box Start Date

End Date

Deliverables

8/2/2015

14/2/2015

Discuss on the main requirements of the system,

Discuss on the main functionalities of the system,
Identify the main functionalities of the system,
Identify the entities and the attributes for the
database, Refer to other university esupervision
systems

15/2/2015

21/2/2015

Finalize the functional and non functional

requirements, Finalize the entities of the database,
Prepare the use case diagram, Prepare the ER
diagram, Prepare the prototype for the system

22/2/2015

28/2/2015

Discuss the use case diagram base on the functional

requirements, Finalize the ER diagram, Discuss on
the prototype of the system, Discuss on the interface
of the system, Finalize the entities, attributes and
data type

1/3/2015

7/3/2015

Finalize the design of the system, Discuss on the

diagrams, Develop the database and draw use case
and ER diagram, Develop the system

8/3/2015

14/3/2015

Progress of developing the site, Discuss on the

diagrams, Continue developing the system and draw
sequence diagram, Draw the activity diagrams

Figure 83 Schedule of the Time Boxing

99 | P a g e

Appendix C - Additional Diagrams

State Chart Diagrams
Registration Process

Figure 84 State Chart Diagram for (Registration Process)

100 | P a g e

Meeting Process

Figure 85(State chart Diagram for Meeting Process)

Allocation Process

Figure 86(State Chart Diagram For Allocation Process)

101 | P a g e

Mail Process

Enter User Confirmation Details

Check Valid
User

Dispaly Inbox

Request Date
Compose
Send mail

Figure 87(State Chart Diagram for Mail process)

102 | P a g e

Blog

Figure 88(State Chart Diagram for Blog)

103 | P a g e

Appendix D - Testing Screen Shorts

Testing Screen Shorts
Below link is to the Webside ot Edima University
http://dwguilder.byethost7.com/edima/student/index.php

Admin Credentials-: Username: a212

Password: 1111

Sample login credentials for Student-: Username: s1001

Password: 12345678

Note-: A student account can be created by entering valid user ID with integer value along
with other relevant information. When logging into the system the student has to add s in
front of the integer user ID
Example
User ID, When creating the account: 1001
User ID, When login to the website: s1001

Sample login credentials for Second Marker-: Username: m101

Password: 12345678
Note-: A Second Marker account can be created by entering valid user ID with integer value
along with other relevant information. When logging into the system the Second Marker has
to add m in front of the integer user ID
Example
User ID, When creating the account: 101
User ID, When login to the website: m101

Sample login credentials for Supervisor-: Username: p50

Password: 12345678

Note-: A supervisor account can be created by entering valid user ID with integer value along
with other relevant information. When logging into the system the supervisor has to add p
in front of the integer user ID
Example
User ID, When creating the account: 50
User ID, When login to the website: p50
Every user should have unique user ID and email address when creating an account

104 | P a g e

1.

Valid username and password must be provided for the login

a.

Ex: For student : Username : s111

Password : 1111

Figure 89(Student Login Page)

2.
After entering valid login details user allows to log in to the website of University of
Edima.

Figure 90(Type user Name & Password)

3.

Home page will show as below

105 | P a g e

Figure 91(Home Page)

4.
Click on Meetings tab to view the meetings scheduled to the user and allocated
lecturers.
a.
Click on New Meeting Link

Figure 92(Meetings Page)

a.
User can add new meeting by entering meeting date, meeting time and description and
click on create.
b.
This will automatically send a mail to the supervisors allocated for student.

106 | P a g e

Figure 93(Create New Meeting page)

5.
a.

Click on mail to view mails received

Click on New Mail to send a mail.

Figure 94(Upload page)

a.

Enter mail address for To field, then enter title and Message and click on send.

107 | P a g e

Figure 95(New Mail Page)

6.
a.
b.

Click on Uploads to upload a file.

Click on choose file then browse and select file and click on upload
Click on View Uploaded Files

Figure 96(Upload Page)

c. Under document list shows all the uploaded files.

108 | P a g e

Figure 97(View Upload Files Page)

7.

Click on Exam tab to view available Mock Exams

Figure 98(Exam Page)

8.

Click on Attendance tab to set in time for scheduled lecture.

109 | P a g e

Figure 99(Attendance Page)

9.
Select Blog and New article then enter Blog Title & Blog Content then click on
Create
a.
Operation was successful message show on red color

Figure 100(Blog Page)

a.

Blog Home Will show available blogs

110 | P a g e

Figure 101(Available Blog Page)

10.

Click on contact will show contact details of the university

Figure 102(Contact Details Page)

a.
Enter Name, E-mail, Mobile, & subject and click Submit will register a student to
receive new updates and activities.

111 | P a g e

Figure 103(Student Filling Area)

11.

Clicking About Edima to see description about the university.

Figure 104 Description about the university

12.

Click on Staff to see the details of staff

112 | P a g e

Figure 105(Staff Details Page)

13.

Click Services to show services provided by the university

Figure 106 (Services page)

113 | P a g e

University web view on mobile device

Login Page

Figure 107(Login Page Mobile View)

Student meeting page

Figure 108 (Student Page Mobile View)

114 | P a g e

Online registration

Figure 109 (Online Registration Page Mobile View)

Upload document page

Figure 110 (Upload Document Page Mobile View)

115 | P a g e

Allocation process view

Figure 111 (Allocation Page Mobile View)

Question page

Figure 112 (Question Page Mobile View)

116 | P a g e

Appendix E - User Manual

There are four types of System Users handle this System. Admin, Supervisor, Second Maker
and
1. Logon to the system
-

Enter user name and password on Edima University Login

Press Login button

Figure 113 university login

-

Sucessfully login to the system.

If he username and password incorrect it will popup following messege.

Figure 114 password error message

-

Enter correct username and password again.

System view home page of the user.

2. Register a New Student

-

Login to the system with admin username and password.

Click on Register Button

117 | P a g e

Figure 115 Registration Button

Click
-

Fill the text fields

Press register button

Figure 116 User Registration page.

3. Allocation of the Details

-

Authorized person need to log on to the system

Click on Allocation Button

Figure 117 Allocation Button Click

118 | P a g e

Fill the details of the students need to be allocated

Press Allocate button

Figure 118 Student allocation page

4. View sample Question paper

-

Login to the system with username & Password

Click on Questions link

Figure 119 Questions Button Click

View the sample question page

119 | P a g e

Figure 120 Sample question page

5.View reports
-

Ener to the system with authorized cridentials.

Click Report Button

Figure 121 Report Button Click

Select the report that you want to generate.

View the report.

120 | P a g e

Figure 122 Display University Statistics

6. View staff details

-

Login to the system

Click on Staff button

Figure 123 Staff Button Click

-

View the staff details

Figure 124 University staff details

121 | P a g e

7.0 View Meetings conducted

-

Login to the system

Click on Meeting button

Figure 125 Meetings Button Click

View the meeting details.

If you want you can arrange a New Meeting on the link

Can view the allocated lectures.

Figure 126 View of the meeting page

8.0 View details on about, services, contact us links
-

Login to the system

Use links to navigate on site

Click on each link

122 | P a g e

View details as follows

Figure 127 Contact us link

Figure 128 About Edima page

123 | P a g e

Figure 129 Our services page

9.0 View Mails and Messages
-

Login to the system

Click on MAIL link

Figure 130 Click Mail Button

-

Can make a new mail by cliking the New Mail

Figure 131 Mail page

124 | P a g e

Figure 132 New Messages

10. View Upload File
-

If Student want to know about the Uploaded files

click View Uploaded file Link

Figure 133 Click Upload Button

select the file to upload

click on upload button

11. View attendance details

-

Click ATTENDANCE Button,

Display below Area

125 | P a g e

Figure 134 Attendance details

12. View student Blog details
-

Click BLOG Button

Display below Area

Figure 135 Blog details

-

If Student wants to New Article Click New Article link

Then Display Below Page

Figure 136 Blog Page

126 | P a g e

After Click the View Uploaded File Link Then Display This Section

Then You can get more details such as Doc ID, Doc Name and who are the uploaded
relevant one as follows

Figure 137 Document List

13.Ending the Sessions

-

After compleating all the application works

Click on LOGOFF Tab

14. URL of the Video Cast

https://www.youtube.com/watch?v=3cpNuJJRkJA&feature=youtu.be
15 .Video Cast of the System

127 | P a g e

Figure 138(Video Cast of the System)

Appendix F Table Creation Cording

Create Tables
CREATE TABLE IF NOT EXISTS `attendance` (
`A_Date` date NOT NULL,
`St_ID` varchar(10) NOT NULL,
`In_Time` datetime DEFAULT NULL,
`Out_Time` datetime DEFAULT NULL,
PRIMARY KEY (`A_Date`,`St_ID`)
);

CREATE TABLE IF NOT EXISTS `meeting` (

`M_ID` int(11) NOT NULL AUTO_INCREMENT,
`St_ID` varchar(10) NOT NULL,
`Sup_ID` varchar(10) NOT NULL,
`S_Marker_ID` varchar(10) NOT NULL,
`M_Date` datetime NOT NULL,
`Description` varchar(200) NOT NULL,
PRIMARY KEY (`M_ID`)
);

CREATE TABLE IF NOT EXISTS `uni_blog` (

`Blog_ID` int(11) NOT NULL AUTO_INCREMENT,
`Blog_Title` varchar(100) NOT NULL,
`Blog_Content` text NOT NULL,
`Blog_User` varchar(10) NOT NULL,
`Blog_DateTime` datetime NOT NULL DEFAULT CURRENT_TIMESTAMP,
PRIMARY KEY (`Blog_ID`)
);

128 | P a g e

Query for New meeting

<?php
include 'top.inc';
$error = "";
//Create a new meeting
function create_meeting()
{
global $con,$error;
extract($_POST);
$id = $_SESSION['user_id'];
$sql = "SELECT S_Marker_ID,St_ID,Sup_ID FROM student WHERE St_ID='$id'
LIMIT 1";
$result = $con->query($sql);
if(!$result || $result->num_rows == 0)
return false;
$student = $result->fetch_array();
$date = "$year-$month-$day $hour:$minute";
$student_id = $student['St_ID'] ;
$Sup_ID = $student['Sup_ID'] ;
$S_Marker_ID = $student['S_Marker_ID'];
$Description = addslashes($Description);
$result = $con->query("INSERT INTO
meeting(St_ID,Sup_ID,S_Marker_ID,M_Date,Description)
VALUES('$student_id','$Sup_ID','$S_Marker_ID','$date' , '$Description')");
if(!$result)
{
$error = "Error creating the meeting";
return false;
}
//Notify All users
sendMail($student_id , 'a212' , 'New Meeting' , 'New meeting scheduled around ' .
$date);
sendMail($Sup_ID , 'a212' , 'New Meeting' , 'New meeting scheduled around ' . $date);
sendMail($S_Marker_ID , 'a212' , 'New Meeting' , 'New meeting scheduled around ' .
$date);
return true;
}
if(isset($_POST['submit']))
{
129 | P a g e

if( create_meeting())
{
$report = "Meeting was scheduled.";
}
}
?>
<div class="wrap"><div class="wrapper">

<div style="margin-left: 10%;" class="form">

<?php if($error != ""){ ?>
<div class="error-message">
<?php echo $error ?>
</div>
<?php } ?>
<?php if(isset($report)){ ?>
<div class="info-message">
<?php echo $report ?>
</div>
<?php } ?>
<h2>Create a new meeting</h2>
<form method="post" name="meeting" action="">
<div class="row">
<label>Meeting Date</label>
<select name="year">
<?php for($i = date('Y') ; $i < date('Y') + 3 ; $i++ ){ ?>
<option value="<?php echo $i?>"><?php echo $i ?></option>
<?php }?>
</select>
<select name="month">
<?php for($i = 1 ; $i < 13 ; $i++ ){ ?>
<option value="<?php echo $i?>"><?php printf( "%02d", $i); ?></option>
<?php }?>
</select>
<select name="day">
<?php for($i = 1 ; $i < 32; $i++ ){ ?>
<option value="<?php echo $i?>"><?php printf( "%02d", $i); ?></option>
<?php }?>
130 | P a g e

</select>
</div>
<div class="row">
<label>Meeting Time</label>
<select name="hour">
<?php for($i = 0 ; $i < 24; $i++ ){ ?>
<option value="<?php echo $i?>"><?php printf( "%02d", $i); ?></option>
<?php }?>
</select>
<select name="minute">
<?php for($i = 0 ; $i < 60; $i++ ){ ?>
<option value="<?php echo $i?>"><?php printf( "%02d", $i); ?></option>
<?php }?>
</select>
</div>
<div class="row">
<label>Description</label>
<textarea required="true" name="Description" rows="8"
maxlength="200"></textarea>
</div>
<div class="row">
<input type="submit" name="submit" value="Create" />
</div>
</form>
</div>
<br style="clear:both" />
</div></div>
<?php
include 'bottom.inc';
?>

131 | P a g e

Query for Questions

<?php
require 'top.inc';
//We have this much questions
$num_qs =5;
//WE have received post data
if( isset($_POST['submit']))
{
function addQuestions($con, $q_id)
{

global $num_qs;
for($q = 1 ; $q <= $num_qs ; $q++)
{
$question = addslashes( strip_tags($_POST['question' . $q]));
$answers = $_POST['answer' . $q];
$correct = $_POST['correct_' . $q];
//Stripping all answers
foreach($answers as $k => $v)
{
$answers[$k] = addslashes(strip_tags($v));
}
if(empty($question) || empty($correct) || empty($answers[0]) ||
empty($answers[1]) || empty($answers[2]) || empty($answers[3]) )
{
return false ; // Empty values sent
}
$sql = "INSERT INTO mcq_list(mcq_id,idx,question,ans1,ans2,ans3,ans4,correct)
VALUES('$q_id','$q','$question','{$answers[0]}' ,'{$answers[1]}'
,'{$answers[2]}' ,'{$answers[3]}'
,'$correct')";
$results = $con->query($sql);
if(!$results || $con->affected_rows ==0 )
return false;
}
return true;
}
132 | P a g e

//Trying to create question header

$title = addslashes(strip_tags($_POST['title']));
$sql = "INSERT INTO mcq_head(mcq_title) VALUES('$title')";
$con->autocommit(false);
$results = $con->query($sql);
if($results && $con->affected_rows > 0 )
{
if(addQuestions($con , $con->insert_id))
{
$_SESSION['report'] = "Operation successful";
$con->commit();
//Trying to redirect
?>
<script>window.location="<?php echo $_SERVER['PHP_SELF']; ?>";</script>
<?php
die();
}
else
{
$error = "Error occured." ;
$con->rollback();
}
}
else
{
$error = "Error creating the questions";
}

}
?>
<style>
.form
{
width:60%;
margin-left: 10% !important;
}
.mcq textarea
{
width:80%;
}
133 | P a g e

.mcq div
{
padding:5px;
margin-top:10px;
}
.mcq h6
{
font-weight: bold;
}
.mcq span
{
font-weight: bold;
}
.mcq .answers
{
line-height: 2;
}
.mcq .answers input
{
display: inline-block;
width: 80%;
}
</style>
<div class="wrap">
<div class="wrapper questions form">
<?php
//Display error messages
if(isset($error)){ ?>
<div class="error-message"><?php echo $error ?></div>
<?php } ?>
<?php
//Sucess message
if(isset($_SESSION['report'])){ ?>
<div class="info-message"><?php echo $_SESSION['report'];
unset($_SESSION['report']); ?></div>
<?php } ?>

<h2>Create simple MCQ exam</h2>

<form method="post" name="questions" action="" onsubmit="return onSubmit();" >
134 | P a g e

<h6>MCQ Title</h6>
<input type='text' id="title" required='required' value="<?php echo @$_POST['title']
?>" style="width: 80%;" name="title" />
<?php for($i = 1 ; $i <= $num_qs ; $i++) {
?>
<div class="mcq row">
<p><span>Question <?php echo $i?>.</span><br />
<textarea required="required" name="question<?php echo $i ?>"
id="question_<?php echo $i?>"><?php
echo @$_POST['question' . $i]?></textarea>
</p>
<div class="answers">
<h6>Answers</h6>
1. <input required="required"
value='<?php echo @$_POST['answer'.$i][0] ?>' type="text"
name="answer<?php echo $i?>[]" id="answer_<?php echo $i?>_1" /><br />
2. <input required="required"
value='<?php echo @$_POST['answer'.$i][1] ?>' type="text"
name="answer<?php echo $i?>[]" id="answer_<?php echo $i?>_2" /><br />
3. <input required="required"
value='<?php echo @$_POST['answer'.$i][2] ?>' type="text"
name="answer<?php echo $i?>[]" id="answer_<?php echo $i?>_3" /><br />
4. <input required="required"
value='<?php echo @$_POST['answer'.$i][3] ?>' type="text"
name="answer<?php echo $i?>[]" id="answer_<?php echo $i?>_4" /><br />
</div>
<div>
<span>Correct Answer</span>
<select name="correct_<?php echo $i ?>">
<?php for($j = 1 ; $j <=4 ; $j++) { ?>
<option <?php if(@$_POST['correct'] == $j) echo "selected='selected'"; ?>
value="<?php echo $j?>">Choice <?php echo $j?></option>
<?php }?>
</select>
</div>
</div>
<?php
}?>
<div class="row">
<input type="submit" name="submit" value="Submit" />
<input type="reset" value="Clear" />
</div>
</form>
</div>
135 | P a g e

</div>
<script>

function onSubmit()
{
try
{
var e = document.getElementById('title');
if(e.value.trim() == "")
{
alert('Title is empty');
return false;
}

for(var i = 1; i <= <?php echo $num_qs ?> ; i++)

{
e = document.getElementById('question_' + i)
if(e.value.trim() == 0)
{
alert('Question cannot be empty');
e.focus();
return false;
}
for(var j= 1 ; j <=4 ; j++)
{
e = document.getElementById('answer_' + i + '_' + j);
if(e.value.trim() == "")
{
alert("Answer cannot be empty");
e.focus();
return false;
}
}
}
}
catch(ex)
{
alert('An error occured');
return false;
}
return true;
136 | P a g e

}
</script>
<br class="clear" />
<?php require 'bottom.inc' ; ?>

137 | P a g e

Sample coding
Lecturer
<?php
require 'top.inc';
?>
<script>
jQuery(function(){
jQuery('#camera_wrap_4').camera({
height: 'auto',
loader: 'bar',
pagination: false,
thumbnails: true,
hover: false,
opacityOnGrid: false,
imagePath: '../images/'
});
});
</script>
<script type='text/javascript' src="../js/camera.min.js"></script>
<link property='stylesheet' href="../css/camera.css" rel="stylesheet" type="text/css"
media="all" />
<div class="fluid_container">
<div class="camera_wrap camera_emboss pattern_1" id="camera_wrap_4">
<div data-src="../images/slider1.jpg"> </div>
<div data-src="../images/slider2.jpg"> </div>
<div data-src="../images/slider3.jpg"> </div>
</div>
</div>
<div class="clear"></div>

<div class="wrap">
<div class="wrapper">
<h3>Meetings</h3>
<div class="section group">
<?php //Load most recent meetings , 4 Max
$user_id = $_SESSION['user_id'];
$sql = " SELECT A.* , U.Full_Name FROM (SELECT * FROM meeting
WHERE Sup_ID='$user_id' OR
138 | P a g e

S_Marker_ID='$user_id' ORDER BY M_Date DESC LIMIT 4)

A INNER JOIN
users U ON U.User_ID = A.St_ID ORDER BY A.M_Date DESC";
$meetings = $con->query($sql);
if($meetings && $meetings->num_rows > 0)
{
while($row = $meetings->fetch_array())
{
?>
<div class="col_1_of_4 span_1_of_4">
<h3 style="font-size: 0.9em;" >Meeting (<?php
echo substr($row['M_Date'],0, -3)?>)</h3>
<p><?php echo $row['Description'] ?> <br />
<span style="font-weight: bold;font-style: italic;">With <?php echo
$row['Full_Name'] ?></span>
</p>
</div>
<?php
}
} ?>
<div class="clear"></div>
</div>
</div>
</div>
<?php
require 'bottom.inc';
?>

139 | P a g e

Staff
<?php
include 'top.inc';
?>
<script>
jQuery(function(){
jQuery('#camera_wrap_4').camera({
height: 'auto',
loader: 'bar',
pagination: false,
thumbnails: true,
hover: false,
opacityOnGrid: false,
imagePath: '../images/'
});
});
</script>
<script type='text/javascript' src="../js/camera.min.js"></script>
<link property='stylesheet' href="../css/camera.css" rel="stylesheet" type="text/css"
media="all" />
<div class="fluid_container">
<div class="camera_wrap camera_emboss pattern_1" id="camera_wrap_4">
<div data-src="../images/slider1.jpg"> </div>
<div data-src="../images/slider2.jpg"> </div>
<div data-src="../images/slider3.jpg"> </div>
</div>
</div>
<div class="clear"></div>
<?php
include 'bottom.inc';
?>

140 | P a g e

Student
<?php
include 'top.inc'
?>
<script>
jQuery(function(){
jQuery('#camera_wrap_4').camera({
height: 'auto',
loader: 'bar',
pagination: false,
thumbnails: true,
hover: false,
opacityOnGrid: false,
imagePath: '../images/'
});
});
</script>
<script type='text/javascript' src="../js/camera.min.js"></script>
<link property='stylesheet' href="../css/camera.css" rel="stylesheet" type="text/css"
media="all" />
<div class="fluid_container">
<div class="camera_wrap camera_emboss pattern_1" id="camera_wrap_4">
<div data-src="../images/slider1.jpg"> </div>
<div data-src="../images/slider2.jpg"> </div>
<div data-src="../images/slider3.jpg"> </div>
</div>
</div>
<div class="clear"></div>
<div class="wrap">
<div class="wrapper">
<div class="main_text">
<h2>A place of light, of liberty, and learning</h2>
<h3>we provide leading intensive courses</h3>
</div>
</div>
</div>
<div class="wrap">
<div class="wrapper">
<h2>Meetings</h2>
<div class="section group">
141 | P a g e

<?php //Load most recent meetings , 4 Max

$user_id = $_SESSION['user_id'];
$sql = "SELECT * FROM meeting WHERE St_ID='$user_id' ORDER BY
M_Date DESC LIMIT 4";
$meetings = $con->query($sql);
if($meetings && $meetings->num_rows > 0)
{
while($row = $meetings->fetch_array())
{
?>
<div class="col_1_of_4 span_1_of_4">
<h3 style="font-size: 0.9em;color:#777"
>Meeting (<?php echo substr($row['M_Date'],0, -3)?>)</h3>
<p><?php echo $row['Description'] ?></p>
</div>
<?php
}
} ?>
<div class="clear"></div>
</div>
</div>
</div>

<?php
include 'bottom.inc';
?>

142 | P a g e

Conclusion
In the first chapter weve basically talked about the project how were going to develop.
Also weve identified the requirement of a new system, organization status and achieving
objectives. Second chapter we discussed about the problems of current system and what kind
of system weve to develop to overcome those issues. In the third chapter, we discussed about
the requirement Catalogue. Requirements Definition is probably the most important
technique in Structured Analysis. It is the only technique that Permeates every step of the
method. In the fourth step, a software requirements specification (SRS) is a comprehensive
description of the intended purpose and environment for software under development. Weve
drawn use-case diagrams of the current system to clearly visualize the processes identified.
In the chapter 5, weve done Data modeling, System modeling. First we identified system
developed methodologies needed and coding architectures and structures available to develop
a maintainable and scalable web based application. According to architectures weve select,
weve drawn architecture diagrams for our application. Then weve normalized the data
analyzed in the previous chapter for create a relation database model. According with
normalized data, weve drawn the Entity Relationship Diagram, data dictionaries & relation
templates for the system. Class diagrams, activity diagrams, sequence diagrams & state
transition diagrams are drawn to plan the flow of our system. In the sixth chapter,
weve prototyped our web pages with story board, wireframes & GUI to show our customer
for feedback. The system development phase discussed in the chapter 6. There we have list
down all the sprints description, sprint plan & development issues. In the chapter 7, weve
done our user interface coding and back-end/front-end development parts along with testing.
Weve also discussed about the software testing and testing types and showed the strategy to
test our application. In the chapter 8, we discussed about the implementation part. We chose
an implementation method for our new system from among 04 system implementation
strategies. Then we talked about the system configuration and installation processes. Finally,
we given a maintain tasks to keep our system healthy and risk free. Finally in chapter 9,
weve evaluate our whole process and product weve developed. Identified weakness of our
system. Talked about problems we got and how to face them. Through that we have
discussed the lessons we learned. Future enhancements also suggested to improving the
application and making it more usable.
In conclusion this document provides the overall knowledge about the web based system. So
this gave a clear impression that web based system is more important than a manual system.

143 | P a g e

Figure 1(Interface of University College Dublin Students upload their ........................ 10

Figure 2(Interface of University of Moratuwa)................................................................ 11
Figure 3(Interface of University of Macquarie) ............................................................... 12
Figure 4(Rich Picture of University of Edima) ................................................................ 17
Figure 5(Use case Diagram) .............................................................................................. 18
Figure 6 Requirement catalog-Register ........................................................................... 29
Figure 7 Requirement catalog-Login................................................................................ 29
Figure 8 Requirement catalog-Projects ............................................................................ 30
Figure 9 Requirement catalog-Dashboard and Profile manage ...................................... 30
Figure 10 Requirement catalog-Scheduling students, supervisors and markers ............ 31
Figure 11 Requirement catalog-Generate Reports .......................................................... 31
Figure 12 Requirement catalog-Email Notifications....................................................... 32
Figure 13 Requirement catalog-Comments...................................................................... 32
Figure 14(ER Diagram Of Proposed System) .................................................................. 34
Figure 15 Attendance Table.............................................................................................. 35
Figure 16 Comment Table ................................................................................................ 35
Figure 17(Meeting Table) ................................................................................................. 36
Figure 18 Message Table................................................................................................... 36
Figure 19 Project Table .................................................................................................... 37
Figure 20 Role Table ......................................................................................................... 37
Figure 21 Second Marker Table ....................................................................................... 38
Figure 22 Student table ..................................................................................................... 38
Figure 23 Supervisor Table .............................................................................................. 39
Figure 24 University Blog Table ....................................................................................... 39
Figure 25 Upload Document Table................................................................................... 40
Figure 26 Users Table ....................................................................................................... 40
Figure 27(Class Diagram) ................................................................................................. 41
Figure 28(Sequence Diagram for User Login Process) .................................................... 42
144 | P a g e

Figure 29(Sequence Diagram for Upload Document Process) ........................................ 43

Figure 30(Sequence Diagram for Meeting Process) ......................................................... 44
Figure 31(Sequence Diagram for Project Comment process) ......................................... 45
Figure 32(Sequence Diagram for Attendance process).................................................... 46
Figure 33(Sequence Diagram for Allocate Staff Process) ................................................ 47
Figure 34(Collaboration Diagram for User Login Process) ............................................ 48
Figure 35(Collaboration Diagram for Upload Document Process) ................................. 48
Figure 36(Collaboration Diagram for Meeting process) ................................................. 49
Figure 37(Collaboration Diagram for Project Comment Process).................................. 49
Figure 38(Collaboration Diagram for Attendance Process) ............................................ 50
Figure 39(Collaboration Diagram for Allocate Staff Process) ........................................ 51
Figure 40(Activity Diagram for Login Process) ............................................................... 52
Figure 41(Activity Diagram for Meeting process) ........................................................... 53
Figure 42(Activity Diagram for Mail process ) ................................................................ 54
Figure 43(Activity Diagram for File List process) ........................................................... 55
Figure 44(Activity Diagram for Report process ) ............................................................ 56
Figure 45(Activity Diagram For User Allocation Process) .............................................. 57
Figure 46(Activity Diagram For Blog) ............................................................................. 58
Figure 47(Activity Diagram For Upload Process) ........................................................... 59
Figure 48 (Registration Component) ................................................................................ 60
Figure 49(Upload Component) ......................................................................................... 60
Figure 50(Allocation Component) .................................................................................... 60
Figure 51(Reports Component) ........................................................................................ 60
Figure 52(Meetings Component) ...................................................................................... 60
Figure 53(Email of Students Component) ........................................................................ 60
Figure 54(Blogging Component) ...................................................................................... 60
Figure 55(Wire Frame for Meeting of Students) ............................................................. 61
Figure 56(Wire Frame for Mail of Students) ................................................................... 62
Figure 57(Wire Frame for Upload Project) ..................................................................... 62
Figure 58(Wire Frame for Registration Process)............................................................. 63
145 | P a g e

Figure 59(Wire Frame for Allocation Process) ................................................................ 64

Figure 60(Wire Frame for Questions) .............................................................................. 65
Figure 61(User Registration Form Mobile View) ............................................................ 66
Figure 62(Allocation Process Mobile View) ..................................................................... 67
Figure 63(Upload Project Process Mobile View) ............................................................. 68
Figure 64(Site Map For Admin Panel) ............................................................................. 69
Figure 65(Site Map for Student Panel)............................................................................. 69
Figure 66(Site Map for Second Maker Panel).................................................................. 70
Figure 67(Ste map for Supervisor panel) ......................................................................... 70
Figure 68(Our Team) ........................................................................................................ 73
Figure 69(Test Case for Student Login Page) .................................................................. 76
Figure 70(Test Case for Supervisor Login Page) ............................................................. 77
Figure 71(Test Case for Second Marker Login Page)...................................................... 78
Figure 72(Test Case for Admin Login Page) .................................................................... 79
Figure 73 (Implementation Diagram) .............................................................................. 83
Figure 74(Gantt Chart of a Proposed System) ................................................................. 90
Figure 75 (Project management Stages) ........................................................................... 91
Figure 76 (Project Development Life Cycle) .................................................................... 92
Figure 77 (Our Team Members Job Roles Table) ........................................................... 92
Figure 78 (Meeting Number: 001) .................................................................................... 94
Figure 79(Meeting Number: 002) ..................................................................................... 95
Figure 80(Meeting Number: 003) ..................................................................................... 96
Figure 81(Meeting Number: 004) ..................................................................................... 97
Figure 82 (Meeting Number: 005) .................................................................................... 98
Figure 83 Schedule of the Time Boxing ............................................................................ 99
Figure 84 State Chart Diagram for (Registration Process) ........................................... 100
Figure 85(State chart Diagram for Meeting Process) .................................................... 101
Figure 86(State Chart Diagram For Allocation Process) .............................................. 101
Figure 87(State Chart Diagram for Mail process) ......................................................... 102
Figure 88(State Chart Diagram for Blog) ...................................................................... 103
146 | P a g e

Figure 89(Student Login Page) ....................................................................................... 105

Figure 90(Type user Name & Password) ....................................................................... 105
Figure 91(Home Page)..................................................................................................... 106
Figure 92(Meetings Page) ............................................................................................... 106
Figure 93(Create New Meeting page) ............................................................................. 107
Figure 94(Upload page)................................................................................................... 107
Figure 95(New Mail Page) .............................................................................................. 108
Figure 96(Upload Page) .................................................................................................. 108
Figure 97(View Upload Files Page) ................................................................................ 109
Figure 98(Exam Page) ..................................................................................................... 109
Figure 99(Attendance Page)............................................................................................ 110
Figure 100(Blog Page) ..................................................................................................... 110
Figure 101(Available Blog Page) .................................................................................... 111
Figure 102(Contact Details Page) ................................................................................... 111
Figure 103(Student Filling Area) .................................................................................... 112
Figure 104 Description about the university .................................................................. 112
Figure 105(Staff Details Page) ........................................................................................ 113
Figure 106 (Services page) .............................................................................................. 113
Figure 107(Login Page Mobile View) ............................................................................. 114
Figure 108 (Student Page Mobile View) ......................................................................... 114
Figure 109 (Online Registration Page Mobile View) ..................................................... 115
Figure 110 (Upload Document Page Mobile View) ........................................................ 115
Figure 111 (Allocation Page Mobile View) .................................................................... 116
Figure 112 (Question Page Mobile View) ....................................................................... 116
Figure 113 university login ............................................................................................. 117
Figure 114 password error message ............................................................................... 117
Figure 115 Registration Button Click............................................................................. 118
Figure 116 User Registration page. ................................................................................ 118
Figure 117 Allocation Button Click ................................................................................ 118
Figure 118 Student allocation page ................................................................................ 119
147 | P a g e

Figure 119 Questions Button Click................................................................................. 119

Figure 120 Sample question page ................................................................................... 120
Figure 121 Report Button Click ..................................................................................... 120
Figure 122 Display University Statistics......................................................................... 121
Figure 123 Staff Button Click ......................................................................................... 121
Figure 124 University staff details .................................................................................. 121
Figure 125 Meetings Button Click .................................................................................. 122
Figure 126 View of the meeting page.............................................................................. 122
Figure 127 Contact us link .............................................................................................. 123
Figure 128 About Edima page ........................................................................................ 123
Figure 129 Our services page.......................................................................................... 124
Figure 130 Click Mail Button ......................................................................................... 124
Figure 131 Mail page....................................................................................................... 124
Figure 132 New Messages .............................................................................................. 125
Figure 133 Click Upload Button ..................................................................................... 125
Figure 134 Attendance details ........................................................................................ 126
Figure 135 Blog details .................................................................................................... 126
Figure 136 Blog Page....................................................................................................... 126
Figure 137 Document List............................................................................................... 127
Figure 138(Video Cast of the System) ............................................................................ 127

148 | P a g e

149 | P a g e