Artificial Viva Exam Scheduler Final Project Document

Final Project Report
Project Supervisor
Muhammad Adnan Ashraf
Submitted By
F12CS61904999
Sobia Sakhwat
Shamim Ghulam Ali
MC110401822
MC110402359
Software Projects & Research Section,

Department of Computer Sciences,
Virtual University of Pakistan
CERTIFICATE
This is to certify that Shamim Ghulam Ali (MC110402359), Sobia Sakhwat (MC110401822) have worked on
and completed their Software Project at Software & Research Projects Section, Department of Computer
Sciences, Virtual University of Pakistan in partial fulfillment of the requirement for the degree of Masters in
Information Technology and Masters of Computer Sciences under my guidance and supervision.
In our opinion, it is satisfactory and up to the mark and therefore fulfills the requirements of
Masters in Information Technology and Masters of Computer Sciences.
Supervisor / Internal Examiner

Muhammad Adnan Ashraf
Supervisor,
Software Projects & Research Section,
Department of Computer Sciences
Virtual University of Pakistan
___________________
(Signature)
External Examiner/Subject Specialist

<<External Supervisor Name>>
___________________
(Signature)
Accepted By:
____________
(For office use)
*this file is for final project of MIT students
EXORDIUM
In the name of Allah, the Compassionate, the Merciful.

Praise be to Allah, Lord of Creation,
The Compassionate, the Merciful,
King of Judgment-day!
You alone we worship, and to You alone we pray for help,
Guide us to the straight path
The path of those who You have favored,
Not of those who have incurred Your wrath,
Nor of those who have gone astray.
DEDICATION

We dedicate this project and our all efforts to our respective and beloved parents and
our teachers especially Mr. Zafar Iqbal and his encouraging response and training that have
been source of inspiration and motivating force behind us.
ACKNOWLEDGEMENT
We express our total submission and eternal gratitude to ALMIGHTY ALLAH, The
Most Gracious, The Most Merciful, without whose mercy and grace, this endeavor could not
been possible even in it is slightest. We bow before our compassionate endowments. Peace
Be upon HOLY PROPHET MUHAMMAD (S.A.W) who is ever a torch of guidance and
knowledge for humanity as a whole.
We deem it an honor and privilege to pay our heartfelt thanks and gratitude to our Project
Advisor, Mr. Zafar Iqbal for his guidance, advice and continuous encouragement and
inspiration, especially during hard and desperate phases of our development work. He helped
us every step of the way in completing this tedious task.
PREFACE
Table of contents
CHAPTER 1
Gathering & Analyzing Info
Chapter 1
1. Introduction
This Chapter will introduce the system requirements specification (SRS) for the
Artificial Viva Exam Scheduler to its students. That includes Scope of Application followed
by the functional and non-functional requirements of the intended system and use cases and
the usage scenarios of the application.
1.1 Purpose
Awareness
1.2 Scope
With the passage of time, we see that higher education is progressing.

Now our researchers are making new ways for exams. Viva is a good method of
measuring the skills of the student.
This system will play very important role in our viva system. It is the need of
our university like VU, where strength of students in increasing day by day.
It is very difficult to manage these students. Specially, it becomes so difficult
when the student requests for updating of viva schedule. It creates the problem
for administrator. Now this system provides the opportunity to the student and
administrator to overcome this problem.
Now student can easily selects and updates the schedule and administrator can
easily manage it.
Functional Requirements
Users registers :
The user registers himself for this course
Provides the basic informations
Login in the viva scheduler system:

Admin and user logins in the viva scheduler system.

They use the username and password that university allots to them
Selects the viva center:

User selects the viva center for the viva
Selects Date:
User selects Date for viva
Selects the Time slot:

User selects the Time slot for the viva
Request to Update the schedule:

The user can request again for the update of the viva schedule
Viva panel list:

The Administrator gets the viva panel list
And selects the viva panels members
Assign Schedule to User:

Administrator assigns the viva schedule to the users
Update the schedule:

If the viva schedule has not finalized then Administrator can updated the
viva schedule of the user
Send information:
System sends the information about viva to the user by emails.
Non-Functional Requirements
User Interfaces:
Interface should be user friendly.
Form should be easy and readable
Communication Interfaces:
interface allows to easy interaction for data transfer and information
it should be good in communication
Data protection:
All stored data shall be secure in the Application.
Accessibility:
The application interface shall be accessible to users.
Performance Requirements:
This application should perform with respective to its Operating
environments. Time taken for providing the results should be minimum.
System
Safety Requirements:
This Application should be installed on proper PC.
Security Requirements:
Admin should allot the ID and password to every user so that this
application my not misuse.
Quality requirements:
Quality has a number of attributes some of the important attributes for
this web application are as under:
o User Training:
We assume that the users already have some previous experience in working with
similar applications. So the users will not need any specific training for using this
application.
o Testability:
As a basic characteristic the application needs to be testable to ensure
correctness
Reusability:
This application is reusable.
Verification:
Only prescribed users can use this application. They have to enter their ID
and password
Platform:
The operating system may be
Window 7
Window XP
1.3 Definitions acronyms and abbreviations
2.
AVES
IEEE
3.
SRS
Software Requirements Specification.
4.
Android
A mobile Operating System developed by Google.
5.
SQLite
A Relational Database used for small Databases.
1.
Artificial Viva Exam Scheduler

Institute of Electrical and Electronics Engineers.
1.4 Use cases and usage scenarios
1.4.1 Use Case Diagrams
gets viva
panel list
Register in
course
gets list
students
<<
us
es
>
>
<<
ex
ex
te
te
nd
nd
>>
>>
login
application
selects <<
>
>
s
exte
clude time slot
nd>
<<in
>
selects
assign
<<in
clude
schedule
schedule
s >>
selects
center
<<
inc
lud
es
>>
Administrator
sends info
print
schedule
<<
update on
request
user
selects date
<<
ex
ten
ds
>
>
by email
Receives
email
Use Case Title

Use Case ID
Description
Artificial Intelligent Viva Exam Scheduler

01
The user register himself/herself in the course
Pre condition
Task sequence
User has registered in the university

The user requests for the course
Registers in the course

Post condition
Exception
Authority
The user has registered in the course

Violation of the rules may lead to registration cancelled.
user
Use Case Title

Use Case ID
Description
Pre condition
Task sequence
Login application
02
The administrator logins in the applications
Administrator has Registered.
The administrator enters username and password
Logins the system
Post condition
Exception
Authority
Administrator has login in the system

Invalid user name and password
Administrator
Use Case Title

Use Case ID
Description
Pre condition
Task sequence
Selects the schedule

03
The user selects the schedule
User has registered in application.
User selects the schedule
Selects the time slot
Selects the date
Selects the center
Saves it.
Post condition
Exception
Authority
The user has selected the schedule

Error in schedule
User
Use Case Title

Use Case ID
Description
Assigns the schedule

04
The Administrator assigns the schedule
Pre condition
Task sequence
Administrator has login and receives the requests form

user for schedule
The administrator gets the request.
Assigns the schedule
Saves it.
Post condition
Exception
Authority
The schedule has assigned.

The error in schedule
Administrator
Use Case Title

Use Case ID
Description
Update the schedule

05
The administrator updates the schedule on the request of
user if request is genuine
User has already scheduled the viva
The user requests to administrator
Update the schedule
Saves it.
The viva schedule has updated.
The error in schedule
User
Pre condition
Task sequence
Post condition
Exception
Authority
Use Case Title

Use Case ID
Description
Pre condition
Task sequence
Inform by email
06
The user receives the email for information.
User request has accepted and schedule has updated
The Administrator has updated the schedule
The system inform the user by email
Post condition
Exception
The user receives the email

The error in email sending

Authority
User
CHAPTER 2
Planning the Project
CHAPTER 2
2.0 Introduction
Planning Phase:
In this phase in which project translate its vision into planning phase i.e. how to achieve
scopes explanation into reality. Main purpose of it is to define the appropriate solutions in
details with references of accepted project. In it we include functional specifications,
architecture, designs, and estimated cost of this project. Each member create individual plan.
In it we include different project plans approved with different a highlight which shows a
complete description of each user in detail. We explained the adopted methodologies and at
the end we also explained the schedule and time frame of this project. Following tasks
include in.
2.1 Methodology
2. Methodologies:
A software application development methodology or system development methodology in
software engineering is a construction that is used to arrangement, plan, and control the
process of developing an information system.
2.2 Existing Methodologies

Following are Existing Methodologies are commonly used now days.
Waterfall Model
Build and Fix Model
Spiral Model
Prototyping Model
Increment Model
Extreme Programming Model
Rapid Application Development
V-Shaped Model
2.1.1 Available Methodologies

In order to organize the work efficiently and to build the product with the required
functionality within specific time and assigned budged Software Development process is
divided into several logical stages. These stages includes software requirements gathering,
Design, Implementations, integrations, maintenance and retirement stages. There are various

Software Development Models available each having its strengths and weaknesses and is
suitable in different environments and situations.
2.1.1.1 Water Fall Model
The classic waterfall Model was introduced in 1970 by Win Royce at Lockheed.
Its so name because it can be represented graphically Modeled.
The original Waterfall Model has little or no feedback between stages, just as water
does not reverse or flow uphill in a cascade but is drawn ever downward by
importance.
Waterfall Model might work satisfactory if design requirements could be perfect
addressed before design creation.
And if the design were perfect before program implementation, and if the code were
perfect before testing, and if the testing is guaranteed that no bugs remain in the code
before the users applied it so, users ever changed their mind about requirements.
2.1.1.2 Build and Fix Model:
The Build and Fix Model was adopted from earlier & simpler age of hardware product
development.
Testing is often ignored.
This always works greatest in a monopolistic or semi monopolistic environment, in
which the clientele has limited access to substitute vendors.
Unfortunately in the Build and Fix Model the products overall quality is never positive.
There is no way to feed back to the design procedure any practical improvement
approach.
2.1.1.3 Spiral
Model:
The Spiral Model was definite by the Barry Boehm in his article.
In the spiral Methodology a smaller amount of time is initially devoted to the four
stages like research, planning, implementation and testing.
The Spiral Model is referred as a risk-driven methodology.
Spiral Model was not the first model but it was the first model to explain why the
iteration matters.
Spiral Model is a software development process combines the elements of equally
design and prototyping stages.
Spiral Model is an effort to combine advantages of top-down & bottom-up concept.
2.1.1.4 Prototyping Model:
Rapid Prototyping model has long been used in the development of one-off
program which is based on the well-known model of the compound engineers
pilot plant.
Prototyping Model is not a procedure, however only a tool that can be used as a
part of process in order to enlarge response.
Users involved throughout these processes which increment the probability of the
user acceptance of the final implementation.
Small scales suggest systems are developed under an iterative modification
procedure until the prototype evolves to meet the users requirements.
2.1.1.5 Increment Model:
The Incremental Model recognizes that software development steps are not discrete.
Instead, build zero is improved and functionality is added until it becomes build one
which build two and so on
The primary purpose of this model is to reduce natural project risk by infringement a
project into smaller segments & providing more easy of change during the
development procedure.
Generally requirements are defined earlier than proceeding.
One of the biggest advantages of the Increment Model is that is it flexible enough to
response to critical change as development process.
A series of mini-Waterfalls are performed, where all phases of the Waterfall
development model are completed for a small part of the systems.
2.1.1.6 Extreme Programming Model:
Extreme Programming model is an approach to software engineering and the

mainly popular of several responsive software development mythologies.
Each feature or set of features of the ending product envision by the client & the
enlarge team is individually scoped for cost and development time.
Extreme Programming is a recent development of the Increment Model that puts
the customers in the driven seat.
The clients then selects features that will be included in the next build based on a
cost benefit analysis.
This development model is well-known by its flexibility because it can work
in the face of a elevated measure of measurement ambiguity on the users part.
2.1.1.7 V-Shaped Model:
The V-Shaped Model (Life Cycle) is a sequential path of implementation of

process.
Each phase must be complete before the subsequently phase begins.
Testing is emphasized in this V-Shaped Model more than the Waterfall Model
though. The test plan focuses on convention the functionality specified in the
requirements get-together.
The completion phase is where all coding takes place. Once coding is
completed the course of execution continues up the right side of the V-Shaped
where the test strategies developed earlier are now lay to use V-Shaped Life
Cycle Model.
2.1.1.8 Rapid Application Development Model:
RAD is a software development method which involves iterative development

and the construction of prototype.
The major aims are to create high value system quickly, primarily through the use
of iterative prototype.
A key objective is for rapid development and release of a higher quality system at
a relatively low speculation charge.
In RAD model key emphasis is on fulfilling the business need while technology
excellence is of lesser important.
Its documentation necessary to smooth the progress of development and
maintained.
2.1.2 Adopted Methodology:

A system development methodology refers to the structure that is used to configuration, plan,
and control the process of developing an information system. A broad selection of such
frameworks has evolved over the years, each with its own recognized strength and
weaknesses. One system development methodology is not essentially appropriate for use by
all projects. Each of the available methodologies is best suited to specific kinds of projects,
based on various technical, organizational, project and team consideration.
The adopted methodology for our project is the VU PROCESS MODEL which is a
combination of Waterfall and Spiral Models. This Model is very simple linear and well
recognized as Waterfall and each stage gives the prototype to user as Spiral Model. Waterfall
is a in order progress procedure, in which development is seen as flowing gradually
downwards (like a waterfall) through the phases of requirements analysis, design,
implementation, testing (justification), integration, and maintenance etc.
2.1.2.1 VU PROCESS MODEL/ VUs Software Development Life Cycle Model
VUs SDLC Model is a very comprehensive model for the students that are going to develop
an application for the first time. If I explain in very simple terms VUs Model is Waterfall
Model with feedback or backward iterations. It consists of four phases Gathering and
Analyzing the Requirements, Planning Phase, Analysis and Design Phase and Final
Deliverables and has five deliverables that include Software Requirements specifications
(SRS), Methodology and work plan, Design document I , Design Document II and Code and
Final Report

In Phase one Gathering and Analyzing the Requirements we will conduct surveys
interviews with Users, Management etc and try to develop a complete, correct and
consistent Software Requirements Specifications (SRS). In second phase Planning
Phase we plane for the development of different phases of development and allocate
resource and time and set their predecessors this phase will results in Deliverable
called Method and Work Plan. The third phase consists of two sub phases Analysis
and Design Phase I and Analysis and Design Phase II that will results in two
deliverables Design Documents I and Design Document II respectively. First Sub
phase include Activity Diagram, Sequence diagrams, Architecture Design Diagram,
DFD(s) and ERD if the project domain requires. The second Sub phase includes
Object model, class diagram, interface design, database design and if the project
domain requires database, test cases, Deployment Diagram, Component Diagram that
will be provided here. The last phase Final Deliverables will results in the
deliverable called Code and Final Report and it contains Complete Project coding and
final project report.
2.1.3 Reasons for choosing the Methodology:

We have selected vu process model because of a lot of reasons which appeals to our study
system in VU.
We should choose the correct type of the Model to apply based on the scope of the
software project Statistical Analyzer for Data management. This depends on a
number of factors, some of which are given below.
The Scope of the Project
The Project budge
The organizational environment
Available Resources
This model of development combines the features of the prototyping model, spiral
model and the waterfall model. So I selected it for my project.
The main strength of the Spiral Model comes from the fact that it is very sensitive to
the risk. Because of the spiral nature of development it is easy to judge how much to
test and there is no distinction between development and maintenance. It however can
only be used for large-scale software development and that too for internal (in-house)
software
2.2 Work Plan (Use MS Project to secrete Schedule/Work Plan)
2.3.1 Team Structure

Team Supervisor: Mohammad Adnan Ashraf
Responsibilities: Supervision, Guidance
Team Member: Shamim Ghulam Ali (MC110402359), Sobia Sakhwat (MC110401822)
Responsibilities: Requirement, Plan, Design, Develop, Test, and Deploy
2.3.2 Team Structure (Visual Representation)
Team Supervisor
Adnan Ashraf
Responsibilities
Guidance
Supervisio
n
Team Member
Responsibilities
2.4 Project Schedule (Submission Calendar)

NO
Phases
Gathering &
Analyzing
requirements
Deliverables
Description
Last Date Submission
CHAPTER 3
Designing the Project
CHAPTER 3
3.1 Introduction (of analysis and design phase)

Analysis Phase
Analysis phase defines the requirements of the system, self-determining of completion
details. This phase defines the problem that is being solved. Requirement article is
deliverable of this phase. It states in a apparent and specific fashion what is to be built.
The requirement article tries to imprison the requirements from customers viewpoint by
defining goals and communications at a level unconcerned from implementation details.
Design Phase

The software system design is shaped from the results of the requirement phase. In the
design phase the architecture is conventional. The document describes a plan to
implement the design of project. Architecture with software design, hardware and
software communication is deliverable of the design phase. In this document software
design is illustrate by following diagrams.
3.2 purpose
Overview (of proposed system)
Data Flow Diagram (DFD): A data flow diagram (DFD) is a graphical
demonstration of flow of data through an information system, model its process aspect. A
DFD shows what kind of data will be input to and output from the system, where the data
will come from and go to, and where the data will be stored.
Entity Relation Diagram (ERD): In software engineering model, an entity

relation diagram ER Diagram is an abstract and intangible illustration of data. Entity
relation modeling is a database modeling method, used to produce a type of conceptual
schema of a system, often a relational database and its requirement in a top-down design
fashion.
Activity Diagram: Activity diagram are graphical representation of workflows of

stepwise actions and achievement with support for choice, iteration and concurrency. In
the Unified Modeling Language (UML), activity diagrams can be used to describe the
business and operational step-by-step workflows of mechanism in a system. An activity
diagram shows the overall flow of organize.
Sequence Diagrams: A sequence diagram in a Unified Modeling Language (UML)

is a kind of interaction diagrams that shows how a process operates with one another and
in what order. A sequence diagram shows object interaction arranged in time sequence. It
depicts the classes and objects involved in the scenario and the sequence of messages
exchange between the objects carry out the functionality of scenario. Sequence diagrams
typically are associated with use case realization in the logical view of the system under
development.
Architectural Design Diagram: A hardware architectural diagram is a mid-level

architecture diagram work product that primarily documents the main physical hardware
components within one or more tires in the tire diagram.
3.3 Data Flow Diagrams

3.3.1 Context Level Diagram
3.3.2 Level-1 Diagram
3.4 Entity Relationship Diagram
3.5 Architectural Representation (Architecture Diagram)
3.6. Activity Diagram:

Login
Add user:
See Position of Schedule:
Check Page List:
Manage Users:
Edit & Delete User Account:
Communicate with Registered Users:
Schedule Submit:
Change Password:
Make Viva Date and Time:
Add Anonymous Users:
Visit to Scheduled List:
3.6.1 Sequence diagrams:

1. Login:
2. Select the Schedule
3. Assign the Schedule:
4. Inform by Email:
5. Update the Scheduled:
6. Artificial Viva exam Scheduled:
3.7 Object Model/Logical Model: Class Diagram
3.8 Database Design:
3.9 Interface Design:
3.10 Deployment Diagram:
CHAPTER 4
Development
CHAPTER 4
4.1 Architecture Diagram
CHAPTER 5
Test Cases
5.1 Test Cases:

Test Case 1
Main (asp.net) page
(Administrator Login Testing in Asp.net application)
Preconditions
The data of the administrator is must exists in the application

database.
Actions
Administrator enters his ID and pasward .
If the ID and pasward is official then it login into the application
Administrator enterd into the application of his main page .
Expected Results administrator has successfully login in application
MC110402359
Tested By:
MC110401822
Result
Yes(login in application on the admin page)
Test Case 2
Administrator (asp.net) page
( If the administrator enter incorrect ID or Password.)

Preconditions
Actions
Administrator clicks on the login by enter his ID and password.

Administrator enter his ID and pasward and the password is
incorrect
Application show youre ID or Password is incorrect .
Application show Try again

Expected Results administrator ID or Password is incorrect .
MC110402359
Tested By:
MC110401822
Result
Login again the incorrect ID or Password.
Test Case 3
Upload the students sheet in Artificial Intelligence Viva Exam Scheduler Application.
Preconditions
Actions
Login into the application an upload students sheet

administrator upload sheet on the GUI interface of the application.
Administrator upload the students sheet from the computer into
the application.
Application saves data.
Expected Results administrator has upload the student sheet
MC110402359
Tested By:
MC110401822
Result
Yes Admin has upload student sheet and also saved into the
application database.
Test Case 4
Enter Project in Artificial Intelligence Viva Exam Scheduler Application.

Preconditions
Actions
After login into the application. Administrator add manage projects

Administrator ads manage projects project info on the GUI interface
of the application.
Administrator add the information of the projects
Expected Results Administrator has added the project information.
MC110402359
Tested By:
MC110401822
Result
Yes Admin has added a project and also saved into the application
database.
Test Case 5
Enter Supervisor info information the Artificial Intelligence Viva Exam Scheduler
Application.
Preconditions
Actions
After login into the application then add supervisor information

Administrator Add supervisor information on the GUI interface of
the application.
Administrator add the information of the projects supervisors
Expected Results administrator has added the information of the projects supervisors.
MC110402359
Tested By:
MC110401822
Result
Yes Admin has entered supervisor and also saved information into
the application database.
Test Case 6
Add/Manage Viva Station Into the Artificial Intelligence Viva Exam Scheduler Application.
Preconditions
After login into the application then Add/Manage Viva Station into
the application.
Actions
administrator Add/Manage Viva Station on the GUI interface of
the application.
Administrator Add and Manage Viva Station
Expected Results administrator has Add and Manage Viva Station
MC110402359
Tested By:
MC110401822
Result
Yes Admin has added/manage viva station and also saved
information into the application database.
Test Case 7
Assign Starting/Ending into the Artificial Intelligence Viva Exam Scheduler Application.
Preconditions
After login into the application then he assign the start and the end date
of viva.
Actions
administrator Assign Starting/Ending date on the GUI interface of

the application.
Administrator Assign Starting/Ending date of the viva
Expected Results
Tested By:
Result
administrator has Assign Starting/Ending date

MC110402359
MC110401822
Yes Admin has Assign Starting/Ending date and also saved information
into the application database.
Test Case 8
Include/Exclude Weekends from Viva dates Into the Artificial Intelligence Viva Exam
Scheduler Application.
Preconditions
Actions
After login into the application then data about the Include/Exclude
Weekends from Viva dates which have already enter into the
application.
administrator Include/Exclude Weekends to from Viva dates
Administrator Include/Exclude Weekends from Viva dates

Expected Results administrator has Include/Exclude Weekends from Viva dates
MC110402359
Tested By:
MC110401822
Yes Admin has Include/Exclude Weekends from Viva dates in to the
Result
application and also saved information into the application database.
Test Case 9
Assign Slots for Viva Each Day to students into the Artificial Intelligence Viva Exam
Scheduler Application.
Preconditions
After login into the application Then Assign Slots for Viva Each Day
to all the students.
administrator Assign Slots to each student on the GUI interface of
Actions
the application.
Administrator Assign Slots for Viva Each Day
Expected Results Administrator has Assign Slots for Viva Each Day to each students.
MC110402359
Tested By:
MC110401822
Result
Yes Admin has completed assign viva slots for each student and also
saved information into the application database.
Test Case 10
Assign Viva Panels for Each Day into the Artificial Intelligence Viva Exam Scheduler
Application.
Preconditions
After login into the application then assign viva panels is must exists
into the application.
Administrator Assign Viva Panels on the GUI interface of the
Actions
application.
Administrator Assign Viva Panels for Each Day
Expected Results administrator has Assigned Viva Panels for Each Day
MC110402359
Tested By:
MC110401822
Result
Yes Admin has done Assign Viva Panels for Each Day and also saved
Test Case 11
Fix/Extend Deadlines of viva into the Artificial Intelligence Viva Exam Scheduler
Application.
Preconditions
After login into the application then Fix/Extend Deadlines is must

exists into the application.
Administrator Fix/Extend Deadlines on the GUI interface of the
Actions
application.
Administrator insert or Fix/Extend Deadlines of the viva
Expected Results Administrator has Fixed or Extend Deadlines.
MC110402359
Tested By:
MC110401822
Yes Admin has done Fix/Extend Deadlines and also saved
Result
Test Case 12
Rescheduled student viva of viva into the Artificial Intelligence Viva Exam Scheduler
Application.
Preconditions
After login into the application then Rescheduled student viva is must
exists into the application.
Administrator Rescheduled student viva on the GUI interface of the
Actions
application.
Administrator insert Rescheduled student viva of the viva exam
Expected Results Administrator has Rescheduled student viva.
MC110402359
Tested By:
MC110401822

Result
Yes Admin has done Rescheduled student viva and also saved

Artificial Viva Exam Scheduler Final Project Document

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Artificial Viva Exam Scheduler Final Project Document

Hochgeladen von

Copyright:

Verfügbare Formate

Final Project Report

Software Projects & Research Section,

Supervisor / Internal Examiner

External Examiner/Subject Specialist

*this file is for final project of MIT students

In the name of Allah, the Compassionate, the Merciful.

*this file is for final project of MIT students

*this file is for final project of MIT students

With the passage of time, we see that higher education is progressing.

Login in the viva scheduler system:

Admin and user logins in the viva scheduler system.

Selects the viva center:

Selects the Time slot:

Request to Update the schedule:

Viva panel list:

Assign Schedule to User:

Update the schedule:

*this file is for final project of MIT students

1.3 Definitions acronyms and abbreviations

Software Requirements Specification.

A mobile Operating System developed by Google.

A Relational Database used for small Databases.