Web-based Seminar System

WEB-BASED SEMINAR SYSTEM PROJECT REPORT | WEB-BASED SEMINAR SYSTEM

Project Overview

1.1. Brief

This is the documentation of Final Year Project of BS (CS) degree. This document includes the detailed description of “Webinar (Web based seminar system)”. It covers all the phases of system development including requirement analysis, designing, and implementation and testing.

Firstly introduction of our SRS , This document is about the overall coverage of our project that which areas we cover and in which phases we work and how we use our techniques , when we deliver our project and what is main target of our doing effort.

Online trainings are now playing important part in learning and act as beneficial alternative to class room sessions. Through webinars, a large number of attendees can participate in interactive sessions facilitated by the T&D department. This should turn out extremely useful for PTCL having large number of employees at various locations. Webinars can thus act as catalyst for knowledge sharing addressing large numbers conveniently.

1.2. Relevance to Course Modules

The course of “Web Engineering” provides us the basic knowledge about Website development which is the basic requirement of our project. “Human Computer Interaction” helped us in designing user friendly GUI. “Data Structure and Algorithms”, “Object-oriented programming” and “Software Engineering” was also very beneficial during the course of the project.

1.3. Project Background

1.4. Literature Review

As such we have not reviewed any specific literature for the development of “PTCL Academy Management System” because the idea is new. Everything is managed on paper and files. We have gathered requirements and developed the entire system.

1.5. Methodology and Software Life Cycle

In this project, Waterfall method is used for the development as the output from the specific stage becomes the input of the next stage in development. During each stage, additional information is gathered or developed, combined with the inputs, and used to produce the stage deliverables. It is important to note that the additional information is restricted in scope. “New ideas” that would take the project in directions not anticipated in the initial set of high-level requirements are not incorporated into the project. Rather, ideas for new capabilities or features that are out-of-scope are preserved for later consideration.

Chapter 2

Problem definition

2.1. Purpose

Purpose of this document is to outline specifications of the solution for PTCL T&D department to deliver lectures to PTCL staff and external students via recorded sessions through a web portal. This is our first phase of this project.

In order to conduct and manage “Webinars” effectively, necessary arrangements are required by T& D department essentially. This encompasses a procedure of sending the webinar invitation to all the intended participants via an email containing all relevant details and information in this respect. Also, this arrangement needs to be completed in all respects including:

· Availability of all type of associated media/information sharing resources. This may include Audio & Video aids.

· The availability of statistics with reference to number of attendees during each session

2.2. Product Functions

Web based seminar system (Webinar) is an interactive application which is going to help out teachers to give lectures in PTCL academies. After the completion of this project the Teacher can easily deliver lectures, download, upload edit and delete videos, and user (attendees) can download and attend lectures.

In order to conduct and manage “Webinars” for PTCL effectively, necessary arrangements are required by T& D (Training and Development) department essentially. This encompasses a procedure of sending the Webinar invitation to all the intended participants via an email containing all relevant details and information in this respect. Also, this arrangement needs to be completed in all respects including:

· Availability of all type of associated media/information sharing resources. This may include Audio & Video aids.

· The availability of statistics with reference to number of attendees during each session

Server Side:

A key feature of a “Webinar” is its interactive elements -- the ability to give, receive and discuss information. Contrast with Webcast, in which the data transmission is one way and does not allow interaction between the presenter and the audience.

Main functionality required is as follow:

· host recorded session

· save webinars

· replay download

Client Side:

Client application will also provide an interactive User Interface to achieve its desired functionality which is as follows:

· Login/Logout

· Register

· Manage Registration, Sessions, Courses, Users(admin)

· Manage Own profiles(teacher, student)

· Manage Own Courses(teacher)

· View , Download , Replay

Every person who wants to use this web portal he/she must have to login .user can also edit his profile. This is for security purpose so that unauthorized person cannot login here.

· Add, delete , view & edit User

System Administrator can add, delete or view any user at any time.

· Add, delete , view & edit Course Content

System Administrator can add, delete or view any Course Content at any time.

· Control all sessions

System administrator can control all sessions. But he is not responsible of any system crash

· Control all Users rights

System administrator can give rights to user he might be teacher or student. He can also block the rights on company permission.

· Control Logs

System administrator can see all logs of user and sessions.

· Logout

Finally system administrator cans logout from his or her account.

2.3. Proposed Architecture

Chapter 3

Requirement Analysis

3.1. Functional Requirement

FR-1 The system shall provide the signup/sign in facility for users (Teacher / Student).

FR-2 The system shall provide the user authentication facility. \

FR-3 The system shall ensure the type of the user.

FR-4 The system shall allow user to post on discussion forums, blogs, site news or chat through messaging facility.

FR-5 The system shall provide the registration/enrolling facility for courses.

FR-6 The system shall provide the Download / replay / view facility of course data for Student.

FR-7 The system shall provide the Add/Delete/Upload/Edit/View facility for course data for Teacher.

FR-8 The system shall provide all right to the Admin.

FR-9 The system shall provide the facility to manage whole Site to Admin.

FR-10 The system shall provide the Reports, Session and logs controlling facility for Admin.

FR-11 The system shall provide the facility to manage Courses as well as Users to Admin.

FR-12 The system shall provide the facility Teacher and Student to manage their own profiles (edit profiles, change passwords).

FR-13 The system shall provide the facility to both Admin and Teacher to add, edit, delete, update and make backups and restores, view reports of the courses.

FR-14 The system shall provide the facility to both Admin and Teacher to assign front page roles to users.

FR-15 The system shall provide the facility to Admin only to add or upload (using excel/csv) new users.

FR-16The system shall provide the facility to Admin only to assign system roles to users.

FR-17 The system shall provide the facility to both Admin and Teacher to create, delete and update groups and groupings.

FR-18 The system shall provide the facility to all to add site news and blogs.

FR-19 The system shall provide the facility to Admin only to edit or delete any site news or forum post.

FR-20 The system shall provide the facility to Admin to create and manage events for their own selves and globally which will be called as user events and global events.

FR-21 The system shall provide the facility to all to create events for their on selves and globally which will be called as user events and global events.

3.2. Non Functional Requirement

3.2.1. Usability

· It is compulsory that the user is familiar with the usage of the Internet.He/she must have the knowledge of using GUI’s of the web portals.

· The system shall provide fast response

3.2.2 Performance Requirements

3.2.1.1 Response Time

· Less than 20 seconds for all non-database related functions.

· Less than 30 seconds for all database related functions.

3.2.1.2 Start Up Time

· Start Up time will be less than 30 seconds

3.2.1.3 Shut Down Time

· Shut Down time will be less than 30 seconds

3.2.3 Graphical User Interface Requirements

· User Interface will be consistent.

3.2.3 Availability

· The System shall be available and accessible 24/7.

3.2.4 Usability

· The System shall provide user friendly interfaces so that user is able to use the system. He should just have basic knowledge of computer for using the website.

3.2.5 Design Constraints

As this project is implemented in CMS version (Moodle 2.1), apache version 2.2.17, PHP version 5.3.5 and MySQL server version 5.5.8

So we need to fulfill all these requirements for server side implementation to run the system properly.

3.2.6. Licensing Requirements

There is no licensing requirement for this system.

3.3. Use Case Model

$Description: C:\Users\Naveed\Desktop\All Diagrams\Class diagram & Use Case Model\Use Case Model Diagram.png$

3.3.1. Actors Description

User: This is the primary actor for the system. This is the person who is using the Web application. He/she may be Manager, Teacher, Student or guest.

Manager: This is the primary actor for the system. This is the person who will manage whole web portal, In other words he is super user of the system

Teacher: This is the primary actor for the system. This is the person who will upload his course content manage his own course content, But he can only view other teachers courses.

Students: This is the primary actor for the system. This is the person who will only view his registered courses and can download course content and replay videos.

3.3.2. Use Case Description

3.3.2.1. Registration

Use case Name:

Registration

Actors:

User (primary)

Description:

This is used for registering users to the site.

References:

Typical Course of event:

Actor’s action

System response

Step1: user will open the site.

Step 2: user will create new account for registration.

Step 3: site will register the user.

Alternate courses:

No alternate

Preconditions:

Interface should be provided.

Post conditions:

User should be registered to site.

3.3.2.2. Login

Use case Name:

Actors:

User (primary)

Description:

This is used for Login in users to the site.

References:

Typical Course of event:

Actor’s action

System response

Step1: user will open the site.

Step 2: user will enter his username and password to login to the site.

Step 3: The user will be logged in.

Alternate courses:

No alternate

Preconditions:

Interface should be provided.

Post conditions:

The user must be logged in.

3.3.2.3. Logout

Use case Name:

Logout

Actors:

User (primary)

Description:

This is used for Logout users from the site.

References:

Typical Course of event:

Actor’s action

System response

Step1: user will click on logout button.

Step 3: The user will be logged out.

Alternate courses:

No alternate

Preconditions:

Interface should be provided.

Post conditions:

The user must be logged out.

3.3.2.4. Manage Own Profile

Use case Name:

Manage own profile

Actors:

User (primary)

Description:

This is used for managing own profiles of users of the site.

References:

Typical Course of event:

Actor’s action

System response

Step1: user will open the site.

Step2: user will enter his username and password to login to the site.

Step3: user will manage his/her profile (edit profile/change password).

Step 4: The user profile will be managed.

Alternate courses:

No alternate

Preconditions:

Interface should be provided.

Post conditions:

The user profile must be managed.

3.3.2.5. View Course Data

Use case Name:

View course data

Actors:

User (primary)

Description:

This is used for viewing course data in which user is enrolled.

References:

Typical Course of event:

Actor’s action

System response

Step1: user will open the site.

Step2: user will enter his username and password to login to the site.

Step3: user will view course data in which user is enrolled

Step 4: show the course data to user.

Alternate courses:

No alternate

Preconditions:

Interface should be provided.

Post conditions:

course data must be available

3.3.2.6. Download Course Data

Use case Name:

Download course data

Actors:

User (primary)

Description:

This is used for Download course data in which user is enrolled.

References:

Typical Course of event:

Actor’s action

System response

Step1: user will open the site.

Step2: user will enter his username and password to login to the site.

Step3: user will Download course data in which user is enrolled.

Step 4: show the course data to user for downloading.

Alternate courses:

No alternate

Preconditions:

Interface should be provided.

Post conditions:

course data must be available

3.3.2.7. Replay Course Video

Use case Name:

Replay course video

Actors:

User (primary)

Description:

This is used for Replay course video in which user is enrolled.

References:

Typical Course of event:

Actor’s action

System response

Step1: user will open the site.

Step2: user will enter his username and password to login to the site.

Step3: user will Replay course video in which user is enrolled

Step 4: show the course videos to user for replaying.

Alternate courses:

No alternate

Preconditions:

Interface should be provided.

Post conditions:

course data must be available

3.3.2.8. Manage Registrations

Use case Name:

Manage registrations

Actors:

Admin (primary)

Description:

This is used for manage registrations of users to the site.

References:

Typical Course of event:

Actor’s action

System response

Step1: user will open the site.

Step2: user will enter his username and password to login to the site.

Step3: user will manage all users accounts registrations

Step 4: registrations will be managed.

Alternate courses:

No alternate

Preconditions:

Interface should be provided.

Post conditions:

Registrations must be managed.

3.3.2.9. Manage Accounts

Use case Name:

Manage user accounts

Actors:

Admin (primary)

Description:

This is used for manage user accounts of users register to the site.

References:

Typical Course of event:

Actor’s action

System response

Step1: user will open the site.

Step2: user will enter his username and password to login to the site.

Step3: user will manage all users accounts

Step 4: all accounts will be managed.

Alternate courses:

No alternate

Preconditions:

Interface should be provided.

Post conditions:

Accounts must be managed.

3.3.2.10. Manage Permissions

Use case Name:

Manage user permission

Actors:

Admin (primary)

Description:

This is used for manage user permission of users register to the site.

References:

Typical Course of event:

Actor’s action

System response

Step1: user will open the site.

Step2: user will enter his username and password to login to the site.

Step3: user will manage all users permissions

Step 4: all permissions will be managed.

Alternate courses:

No alternate

Preconditions:

Interface should be provided.

Post conditions:

Permissions must be managed.

3.3.2.11. Manage Sessions

Use case Name:

Manage sessions

Actors:

Admin (primary)

Description:

This is used for manage sessions of site, courses and users registered to the site.

References:

Typical Course of event:

Actor’s action

System response

Step1: user will open the site.

Step2: user will enter his username and password to login to the site.

Step3: user will manage all sessions of site, courses and users registered to the site.

Step 4: all sessions of site, courses and registered users will be managed.

Alternate courses:

No alternate

Preconditions:

Interface should be provided.

Post conditions:

All sessions of site, courses and registered users must be managed.

3.3.2.12. Manage Logs

Use case Name:

Manage logs

Actors:

Admin (primary) , Teacher (primary)[with limited authority]

Description:

This is used for manage logs of site, courses and users registered to the site.

References:

Typical Course of event:

Actor’s action

System response

Step1: user will open the site.

Step2: user will enter his username and password to login to the site.

Step3: user will manage all logs of site, courses and users registered to the site.

Step 4: all logs of site, courses and registered users will be managed.

Alternate courses:

No alternate

Preconditions:

Interface should be provided.

Post conditions:

All logs of site, courses and registered users must be managed.

3.3.2.13. Manage Reports

Use case Name:

Manage reports

Actors:

Admin (primary) , Teacher (primary)[with limited authority]

Description:

This is used for manage reports of site, courses and users registered to the site.

References:

Typical Course of event:

Actor’s action

System response

Step1: user will open the site.

Step2: user will enter his username and password to login to the site.

Step3: user will manage all reports of site, courses and users registered to the site.

Step 4: all reports of site, courses and registered users will be managed.

Alternate courses:

No alternate

Preconditions:

Interface should be provided.

Post conditions:

All reports of site, courses and registered users must be managed.

3.3.2.14. Manage User Groups and Groupings

Use case Name:

Manage user groups and grouping

Actors:

Admin (primary) / Teacher (primary)

Description:

This is used for manage user groups and grouping for courses of users registered to the site.

References:

Typical Course of event:

Actor’s action

System response

Step1: user will open the site.

Step2: user will enter his username and password to login to the site.

Step3: user will manage all user groups and grouping users registered to the site. (create, edit, delete)

Step 4: all user groups and grouping registered users will be managed.

Alternate courses:

No alternate

Preconditions:

Interface should be provided.

Post conditions:

All user groups and grouping must be managed.

3.3.2.15. Manage Courses

Use case Name:

Manage all Courses

Actors:

Admin (primary)

Description:

This is used for manage all courses available on the site.

References:

Typical Course of event:

Actor’s action

System response

Step1: user will open the site.

Step2: user will enter his username and password to login to the site.

Step3: user will manage courses. (add, edit, delete)

Step 4: all courses will be managed.

Alternate courses:

No alternate

Preconditions:

Interface should be provided.

Post conditions:

All courses must be managed.

3.3.2.16. Manage Site News

Use case Name:

Manage all site news

Actors:

Admin (primary)

Description:

This is used for managing all news of the site and courses.

References:

Typical Course of event:

Actor’s action

System response

Step1: user will open the site.

Step2: user will enter his username and password to login to the site.

Step3: user will manage all news of the site and courses. (add, edit, delete)

Step 4: all news of the site and courses will be managed.

Alternate courses:

No alternate

Preconditions:

Interface should be provided.

Post conditions:

All news of the site and courses must be managed.

3.3.2.17. Manage Blogs

Use case Name:

Manage all blogs

Actors:

Admin (primary)

Description:

This is used for managing all blogs of the site and courses.

References:

Typical Course of event:

Actor’s action

System response

Step1: user will open the site.

Step2: user will enter his username and password to login to the site.

Step3: user will manage all blogs of the site and courses. (add, edit, delete)

Step 4: all blogs of the site and courses will be managed.

Alternate courses:

No alternate

Preconditions:

Interface should be provided.

Post conditions:

All blogs of the site and courses must be managed.

3.3.2.18. Manage Forums

Use case Name:

Manage all forums

Actors:

Admin (primary)

Description:

This is used for managing all forums of the site and courses.

References:

Typical Course of event:

Actor’s action

System response

Step1: user will open the site.

Step2: user will enter his username and password to login to the site.

Step3: user will manage all forums of the site and courses. (add, edit, delete)

Step 4: all forums of the site and courses will be managed.

Alternate courses:

No alternate

Preconditions:

Interface should be provided.

Post conditions:

All forums of the site and courses must be managed.

3.3.2.19. Manage Calendar Events

Use case Name:

Manage all calendar events

Actors:

Admin (primary)

Description:

This is used for managing all calendar events of the site and courses.

References:

Typical Course of event:

Actor’s action

System response

Step1: user will open the site.

Step2: user will enter his username and password to login to the site.

Step3: user will manage all calendar events of the site and courses. (add, edit, delete)

Step 4: all calendar events of the site and courses will be managed.

Alternate courses:

No alternate

Preconditions:

Interface should be provided.

Post conditions:

All calendar events of the site and courses must be managed.

3.3.2.20. Manage Own Site News

Use case Name:

Manage own site news

Actors:

User (primary)

Description:

This is used for managing own news of the site and courses.

References:

Typical Course of event:

Actor’s action

System response

Step1: user will open the site.

Step2: user will enter his username and password to login to the site.

Step3: user will manage his/her own news of the site and courses. (add, edit, delete)

Step 4: User’s own news of the site and courses will be managed.

Alternate courses:

No alternate

Preconditions:

Interface should be provided.

Post conditions:

User’s own news of the site and courses must be managed.

3.3.2.21. Manage Blogs

Use case Name:

Manage all blogs

Actors:

User (primary)

Description:

This is used for managing own blogs of the site and courses.

References:

Typical Course of event:

Actor’s action

System response

Step1: user will open the site.

Step2: user will enter his username and password to login to the site.

Step3: user will manage his/her own blogs of the site and courses. (add, edit, delete)

Step 4: User’s own blogs of the site and courses will be managed.

Alternate courses:

No alternate

Preconditions:

Interface should be provided.

Post conditions:

User’s own blogs of the site and courses must be managed.

3.3.2.22. Manage Forums

Use case Name:

Manage all forums

Actors:

User (primary)

Description:

This is used for managing user’s own forums of the site and courses.

References:

Typical Course of event:

Actor’s action

System response

Step1: user will open the site.

Step2: user will enter his username and password to login to the site.

Step3: user will manage his/her own forums of the site and courses. (add, edit, delete)

Step 4: User’s own forums of the site and courses will be managed.

Alternate courses:

No alternate

Preconditions:

Interface should be provided.

Post conditions:

User’s own forums of the site and courses must be managed.

3.3.2.23. Manage Calendar Events

Use case Name:

Manage all calendar events

Actors:

User(primary)

Description:

This is used for managing user’s own calendar events of the site and courses.

References:

Typical Course of event:

Actor’s action

System response

Step1: user will open the site.

Step2: user will enter his username and password to login to the site.

Step3: user will manage his/her own calendar events of the site and courses. (add, edit, delete)

Step 4: User’s own calendar events of the site and courses will be managed.

Alternate courses:

No alternate

Preconditions:

Interface should be provided.

Post conditions:

User’s own calendar events of the site and courses must be managed.

3.3.2.24. Manage Own Courses

Use case Name:

Manage own Courses

Actors:

Teacher (primary)

Description:

This is used for manage teacher’s own courses.

References:

Typical Course of event:

Actor’s action

System response

Step1: user will open the site.

Step2: user will enter his username and password to login to the site.

Step3: user will manage his/her own courses. (add, edit, delete)

Step 4: Teacher’s own courses will be managed.

Alternate courses:

No alternate

Preconditions:

Interface should be provided.

Post conditions:

Teacher’s own courses must be managed.

3.3.2.25. Manage Front Page

Use case Name:

Manage front page(settings, roles)

Actors:

Admin (primary) / Teacher (primary)

Description:

This is used for manage front page settings and roles.

References:

Typical Course of event:

Actor’s action

System response

Step1: user will open the site.

Step2: user will enter his username and password to login to the site.

Step3: user will manage front page settings and roles

Step 4: front page settings and roles will be managed.

Alternate courses:

No alternate

Preconditions:

Interface should be provided.

Post conditions:

Front page settings and roles must be managed.

Chapter 4

The Design

4.1. UML Structural Diagrams

4.1.1. Class Diagram

$Description: C:\Users\Naveed\Desktop\All Diagrams\Class diagram & Use Case Model\NewClassDiagram.png$

4.1.2. Package Diagram

$Description: C:\Users\Naveed\Desktop\All Diagrams\Package Diagram\pakage.png$

4.1.3. Deployment Diagram

$Description: C:\Users\Naveed\Desktop\All Diagrams\Deployment Diagram\Deployment Diagram.png$

4.1.4 Composite structure diagram

Site Manager:

$Description: C:\Users\Naveed\Desktop\All Diagrams\Composite Structure Diagram\admin.png$

Teacher: $Description: C:\Users\Naveed\Desktop\All Diagrams\Composite Structure Diagram\Teacher.png$

Student:

$Description: C:\Users\Naveed\Desktop\All Diagrams\Composite Structure Diagram\Student.png$

4.2. UML Behavioral Diagrams

4.2.1. Activity Diagrams

Activity diagrams are graphical representation of workflows of stepwise activities and actions with support for choice, iteration and concurrency. In this section different activities of the system will be shown with diagrams.

User Activity Diagram

Login:

$Description: C:\Users\Naveed\Desktop\All Diagrams\Activity Diagrams\Login.jpg$

Signup:

$Description: C:\Users\Naveed\Desktop\All Diagrams\Activity Diagrams\Sign Up.jpg$

Manage Courses:

$Description: C:\Users\Naveed\Desktop\All Diagrams\Activity Diagrams\manage courses.jpg$

Manage Sessions:

$Description: C:\Users\Naveed\Desktop\All Diagrams\Activity Diagrams\manage sessions.jpg$

Upload Course Video:

$Description: C:\Users\Naveed\Desktop\All Diagrams\Activity Diagrams\upload video.jpg$

Manage blogs:

$Description: C:\Users\Naveed\Desktop\All Diagrams\Activity Diagrams\manage blog.jpg$

Manage Events:

$Description: C:\Users\Naveed\Desktop\All Diagrams\Activity Diagrams\manage events.jpg$

Manage Forums:

$Description: C:\Users\Naveed\Desktop\All Diagrams\Activity Diagrams\manage forum.jpg$

Manage Reports:

$Description: C:\Users\Naveed\Desktop\All Diagrams\Activity Diagrams\manage reports.jpg$

Student:

$Description: C:\Users\Naveed\Desktop\All Diagrams\Activity Diagrams\student.jpg$

4.2.2. State Diagrams

A state diagram of the system describes the behavior of the system. In this section diagrams describe the different behaviors of the system.

$Description: C:\Users\Naveed\Desktop\All Diagrams\State Machine Diagrams\Login.png$

$Description: E:\7th semester\FYP\Our UML Diagrams\State Machine Diagrams\ManageAdmin.jpg$

Teacher:

$Description: C:\Users\Naveed\Desktop\All Diagrams\State Machine Diagrams\ManageTeacher.png$

Student:

$Description: C:\Users\Naveed\Desktop\All Diagrams\State Machine Diagrams\ManageStudent.png$

Site Manager:

$Description: C:\Users\Naveed\Desktop\All Diagrams\State Machine Diagrams\ManageAdmin.png$

4.3. UML Interaction Diagrams

4.3.1. Sequence Diagrams

A sequence diagram is a kind of interaction diagram that shows how processes operate with one another and in what order .In this section different process of the system are shown with the diagrams.

Register:

$Description: C:\Users\Naveed\Desktop\All Diagrams\System Sequnce Diagram\Register.jpg$ Description: Signup

Upload Course Video:

$Description: C:\Users\Naveed\Desktop\All Diagrams\System Sequnce Diagram\UploadVideo.jpg$

View Course Video:

$Description: C:\Users\Naveed\Desktop\All Diagrams\System Sequnce Diagram\VeiwVideo.jpg$

Replay Course Video:

$Description: C:\Users\Naveed\Desktop\All Diagrams\System Sequnce Diagram\ReplayVideo.jpg$

Download Course Video:

$Description: C:\Users\Naveed\Desktop\All Diagrams\System Sequnce Diagram\DownloadVideo.jpg$

Chapter 5

Implementation

5.1. System Implementation

This Chapter describes in detail the implementation of the Webinar. The implementation of the system is done in to following parts:

· Manager Panel

· Teacher Panel

· Student Panel

5.1.1. Manager Panel

In Manager Panel we give all rights to manager that he can manage whole site , because he is an authorized person that’s why we give him right to manage user , manage courses , manage site , and also manage others site contents .what manager can do:

· Manage site Pages(Participants, blogs, calendar )

· Manage own Profile(view, forum posts, discussions, blogs, messages, private files, Activity report, passwords, Roles)

· Manage Courses

· Manage Front pages

· Manage Backups & Restore

· Manage Question banks

· Manage Reports

· Manage Users

5.1.2 Teacher Panel

In Teacher panel we give some right so that he can also manage his own courses and groups.

· Manage own site Pages( blogs, calendar , view Reports )

· Manage own Profile(view, forum posts, discussions, blogs, messages, private files, Activity report, passwords, Roles)

· Manage own Courses

· Manage courses Backups & Restore

· Manage own Question banks

· Manage course Reports’

5.1.2 Student Panel

· Manage own blogs, calendar , view site news

· Manage own Profile(view forum posts, discussions, blogs, messages, private files, Activity report, passwords)

· View, download, replay own Courses videos

Chapter 6

Testing &Evaluation

6.1. Verification:

This is an activity to verify whether we have built the system right or not in the development life cycle.

6.1.1. Functional Testing

Below are some of the test cases, verifying the system functional abilities.

Test Case 1:

Test Case : Login (Server Side)

Description: The user enters the data in the required fields and enters into the PTCL Academy Management System

Data Requirements :

{User Name} The user must have a unique user name.

{User Password} It must be valid for given username.

Step No

Step

Description

Expected

Result

Transaction

Name

User Think

Time (in

Seconds)

User enters

username

Front page

Enter User

Name

User enters the

password

Front page

enters password

in secret form

Enter Password

User is

authenticated by

checking the

username and

Password

Validity

Approved

Validation

2-3

User enters into the

PTCL Academy Management System

The user gets

the option of

selection(According to user type either manager, teacher or student

)

PTCL Academy Management System

Test Case 2:

Test Case : Add new course
Description: The user starts new course, manager and teacher both can upload or start a course.
Data Requirements : User must assign role as teacher or manager.
Step No	Step Description	Expected Result	Transaction Name	User Think Time (in Seconds)
1	User select Parent category	Category show	Enter category	2
2	User enters the Category name	Display category name	Enter_ name	2
3	Click button Save Changes	Course menu page Display	Save changes	2-3
4	Click button Add new course	Edit course setting page displays	Edit course	2
5	Select category	Category show	Enter category	2
6	Enter Course full name	Display course name	Course name	2
7	Enter Course other required details	Display course details	Course other required details	2
8	Select save changes	Enrolment page display	Save changes	4

Test Case 3:

Test Case : Add course content
Description: site manager and teacher both can add content in a course.
Data Requirements : User must assigned role as teacher or manager.
Step No	Step Description	Expected Result	Transaction Name	User Think Time (in Seconds)
1	User select Course	Weekly outline show	Select course	2
2	Turn editing on	Editing panel show	Editing on	2
3	Add resource/ add activity	New resource /activity page show	resource activity	2-3
4	Enter Name	Display name	Name required data	2
5	Enter necessary details	All details entered	Necessary details	2
6	Save / return to course	Display course contents	Course return	2
7	Save & display	Display saved content	Save display	2

Test Case 4:

Test Case : delete course
Description: site manager and teacher both can delete course contents
Data Requirements : User must assigned role as teacher or manager.
Step No	Step Description	Expected Result	Transaction Name	User Think Time (in Seconds)
1	User select course	Weekly outline show	Select course	2
2	Turn editing on	Editing panel show	Editing on	2
3	delete resource/ add activity	resource / activity delete	resource activity	2-3

Test Case 5:

Test Case : Add new user
Description: site manager can add new user.
Data Requirements : User must assigned role as manager.
Step No	Step Description	Expected Result	Transaction Name	User Think Time (in Seconds)
1	Enter user name	Display user name	User-name	2
2	New password	Password shown in secret form	New_pasward	2
3	First name	Display first name	First name	2-3
4	Surname	Display surname	Surname	2
5	Official Email Address	Email address display	Official email	2
6	City/town	Display city/town	City town	2
7	Select a country	Display country	Country	2
8	Update profile	User created	Update profile	4

Test Case 6:

Test Case : delete user
Description: site manager and teacher both can delete user
Data Requirements : User must assigned role as teacher or manager.
Step No	Step Description	Expected Result	Transaction Name	User Think Time (in Seconds)
1	Delete	Pop up window open	Delete user	2
2	Confirm	User deleted	Confirm	2

Test Case 6:

Test Case : Create new account
Description: New users who come to site can register themselves to site by creating new account.
Data Requirements : Anyone can create an account but with restricted access.
Step No	Step Description	Expected Result	Transaction Name	User Think Time (in Seconds)
1	Enter user name	Display user name	User_name	2
2	New password	Password shown in secret form	New_pasward	2
3	First name	Display first name	First_name	2-3
4	Surname	Display surname	Sur_Name	2
5	Official Email Address	Email address display	Official_email	2
5	Email Address	Email address display	Email_adress	2
6	City/town	Display city/town	City_town	2
7	Select a country	Display country	Country	2
8	Create new account	User created	Account_creat	4

Test Case 7:

Test Case : Enroll User
Description: site manager and teacher both can enroll user
Data Requirements : User must assigned role as teacher or manager.
Step No	Step Description	Expected Result	Transaction Name	User Think Time (in Seconds)
1	Enroll user	Pop up apear	Enroll_user	2
2	Select User	Select enroll	User enroll	2

6.1.2. Static Testing

Software coding is checked for any type of syntax errors and other logical ones. It is verified that system is in a stable condition and, will alert the user if he/she is performing any action whose prerequisite is not performed and will not fail in any process.

6.2. Validation

This is the activity to validate that we have built the right product, in scope and according to the requirements. It is validated that all the system functions are in scope and are same as defined in the requirements analysis phase. Furthermore we have implemented a few extra features in our system which was not listed in our project requirements.

6.3. Usability Testing

Usability testing is a technique for ensuring that the intended users of a system can carry out the intended tasks efficiently, effectively and satisfactorily. The system is tested in terms of usability and results have shown complete success.

6.4. Unit Testing

Every module of the code either it is server side or client is tested separately after specifying some real world scenarios. We have tested almost each part of the system continuously either it is big or small. After doing unit testing we can safely state that all the units of the whole system are in working condition.

6.5. Integration Testing

After the success of unit testing, we integrated each and every module together and made the final shape of the system. Then again we started testing the system over some real time scenarios and meet success in every scenario.

6.6. System Testing

We implemented and tested our PTCL Academy Management System. System is completely stable and operational. It is also tested by applying real world scenarios. It stable has generated correct results. The performance, functionality and the design layout remains same in frequently used web browsers.

Future Work

PTCL Academy Management system is currently hosting recoded sessions but in future work of this product in phase II and phase III are

· Deliver Live and Interactive Webinar (add voice chat)

Chapter 8

GUI

Main Page:

$Description: C:\Users\Naveed\Desktop\ptcl\pics\front page.png$

Manager Front Page:

$Description: C:\Users\Naveed\Desktop\ptcl\pics\manager front page.png$

Manager Add new Course

$Description: C:\Users\Naveed\Desktop\ptcl\pics\manager add new course.png$

Manager Add new user

$Description: C:\Users\Naveed\Desktop\ptcl\pics\manager add new user.png$

Manager Add site news

$Description: C:\Users\Naveed\Desktop\ptcl\pics\manager add site news.png$

Manager create backup

$Description: C:\Users\Naveed\Desktop\ptcl\pics\manager backup.png$

Manager Change password

$Description: C:\Users\Naveed\Desktop\ptcl\pics\manager change pasward.png$

Manager message panel

$Description: C:\Users\Naveed\Desktop\ptcl\pics\manager massege panel.png$

Manager restores

$Description: C:\Users\Naveed\Desktop\ptcl\pics\manager restore.png$

Manager Site Page settings

$Description: C:\Users\Naveed\Desktop\ptcl\pics\manager site page settings.png$

Manager Logout

$Description: C:\Users\Naveed\Desktop\ptcl\pics\manager logout.png$

Teacher Front page

$Description: C:\Users\Naveed\Desktop\ptcl\pics\teacher front page.png$

Teacher Add new course

$Description: C:\Users\Naveed\Desktop\ptcl\pics\teacher add new course.png$

Teacher Front page settings

$Description: C:\Users\Naveed\Desktop\ptcl\pics\teacher front page settings.png$

Teacher Add new site news

$Description: C:\Users\Naveed\Desktop\ptcl\pics\teacher site news.png$

Teacher Create new events

$Description: C:\Users\Naveed\Desktop\ptcl\pics\teacher creat new events.png$

Teacher Logout

$Description: C:\Users\Naveed\Desktop\ptcl\pics\teacher logout.png$

Student front page

$Description: C:\Users\Naveed\Desktop\ptcl\pics\student front page.png$

Student view course video

$Description: C:\Users\Naveed\Desktop\ptcl\pics\student view video.png$

Student site news

$Description: C:\Users\Naveed\Desktop\ptcl\pics\student site news.png$

Student feedback form

$Description: C:\Users\Naveed\Desktop\ptcl\pics\student feed back form.png$

Student change password

$Description: C:\Users\Naveed\Desktop\ptcl\pics\student change passward.png$

Student calendar

$Description: C:\Users\Naveed\Desktop\ptcl\pics\student calender.png$

Student Logout

$Description: C:\Users\Naveed\Desktop\ptcl\pics\student logout.png$

FREE DOWNLOAD BCA MCA MANAGEMENT SYSTEM PROJECT SYNOPSIS REPORT WITH SOURCE CODE (ASP.NET PHP JAVA)

FREE DOWNLOAD IGNOU BCA MCA PROJECT, SYNOPSIS AND FINAL REPORT WITH SOURCE CODE

Friday, May 15, 2020