COMSATS University Islamabad (CUI)

MICROSOFT TEAMS

By

Rimsha Shakoor CIIT/FA19-BSE-007/ISB

Rubia Gulzar CIIT/FA19-BSE-008/ISB

Syeda Fiza Batool CIIT/FA19-BSE-017/ISB

Submitted to:
Mrs. Saira Baig

Bachelor of Science in Software Engineering (2019-2022)

The candidate confirms that the work submitted is their own and appropriate credit has
been given where reference has been made to the work of others.
Table of Contents
1 Introduction................................................................................................................................1

1.1 Brief Overview...............................................................................................................................1

1.2 Relevance to Course Modules.........................................................................................................2
1.3 Project Background........................................................................................................................2
1.4 Methodology and Software Lifecycle for this Project.....................................................................2
2 Problem Definition.....................................................................................................................3

2.1 Problem Statement..........................................................................................................................3

2.2 Deliverables and Development Requirements................................................................................3
2.3 Current System...............................................................................................................................4
3 Requirement Analysis................................................................................................................5

3.1 Event Table.....................................................................................................................................5

3.2 Detailed Use Case...........................................................................................................................6
3.2.1 Module 1: Activity....................................................................................................................7
3.2.2 Module 2: Chats........................................................................................................................8
3.2.3 Module 3: Teams......................................................................................................................9
3.2.4 Module 4: Assignment............................................................................................................10
3.2.5 Module 5: Files.......................................................................................................................11
3.2.6 Module 6: Calls.......................................................................................................................12
3.2.7 Module 7: Calendar................................................................................................................13
3.2.8 Module 8: Apps......................................................................................................................14
3.2.9 Module 9: Help.......................................................................................................................15
3.3 Functional Requirements..............................................................................................................16
3.4 Non-Functional Requirements......................................................................................................17
4 Design and Architecture...........................................................................................................18

4.1 Structural Diagrams..................................................................................................................19

4.2 Behavioral Diagrams................................................................................................................20
5 Implementation.........................................................................................................................36

5.1 User Interface...............................................................................................................................36

6 Testing and Evaluation.............................................................................................................45

6.1.1 Unit Testing............................................................................................................................45

7 Conclusion and Future Work....................................................................................................48

7.1 Conclusion....................................................................................................................................48
7.2 Future Work..................................................................................................................................48

1
Introduction

1.1 Brief Overview

The purpose of developing “Microsoft Teams” software is to keep the students and teachers
connected through a virtual platform even when they cannot reach to the physical platform. It will
combine the benefits of a physical classroom with the convenience of a ‘no-physical-bar’ virtual
learning environment, minus the change hazards and expenses. This will provide more flexibility
in the existing learning platform structures. It provides a means of collaborative learning for the
students and promotes the distance learning.
Following are the features of this system:

▪ Student Registration:
Admin can register a student for a specific program.

▪ Video Lectures:
Student can watch and listen the classroom session repeatedly which will be uploaded by
the teacher.

▪ Result:
Students can get the result via this web application

▪ Attendance:
It includes attendance of students for a specific class.

▪ Record Storage:
The user information files should be stored in centralized database which can be
maintained by the system.

▪ Authentication:
Authentication of this application will be provided for only registered members.

▪ Activities for Students:

The teacher can upload assignments to the students, multimedia which a student can
download and listen when required.

▪ Administration Access:
Administration would be able to keep an eye on the records of students.

▪ Library:
Student helping material would be available.
2
Advantages for the students are explained below:

• Time and Cost Saving: For students of virtual classrooms, advantages primarily concern
access, time, and cost factors compared to those incurred from attending the traditional,
physical classroom.

• Remove Traveling: Microsoft teams removes the need of travel to attend the lectures.

• Education at Doorstep: Our system is a platform to provide education at doorstep.

We believe that by using Microsoft teams, students can get an experience equal to or better than
they would find in a traditional classroom. There are obviously many advantages of the virtual
classroom to the student, as well as the teacher and the associated educational institution

1.2 Relevance to Course Modules

• CSE355: Introduction to Software Engineering

This course assisted in the documentation of the software.

1.3 Project Background

Microsoft Teams is a web-based desktop app which provides the facility of a virtual classroom. It
was developed on top of the Electron framework from GitHub which combines the Chromium
rendering engine and the Node. js JavaScript platform.

1.4 Methodology and Software Lifecycle for this Project

• Software Process Model:

Incremental Model
• Design Methodology:
Object Oriented Methodology

3
Problem Definition

2.1 Problem Statement

The present system of classrooms is a manual system or a semi-automated system. It involves
paperwork in the form of maintaining various files and manuals. Maintaining critical information
in the files and manuals is a risky and tedious process.
It has the following disadvantages:
 It’s a limited system and fewer users friendly.
 Searching of information is critical it takes lot of time.
 Students are bound to learn course in the classroom only.
 Students need a lot of time and cost in the existing system.
 The existing system requires students to travel from one place to
 another in order participate in the course.
 Conduct of examination and compilation of result is a tedious process.
 It stores the information in the form of files.
 Limited sharing is possible if the data is in the form of paper or disk drives.
 The manual system gives us less security for saving data, some data may be lost due to
mismanagement.

2.2 Deliverables and Development Requirements

Following are the deliverables of our project:

• Scope
• Software Requirement Specification (SRS)
• Software Design Specification (SDS)
• Software Test Case Specification (STS)
• Final Report
• Source Code
• Demo Video

4
2.3 Current System

Table 2.1: Current System

Application Name Weakness Proposed Project Solution
Skype App is limited to video -Microsoft teams have all the facilities of
meetings and chat system a proper classroom. Assignments, calls,
only. The facilities of a chats, quizzes, grading, attendance,
proper classroom are not everything can be done easily.
present.

Zoom - App is limited to video -Microsoft teams have all the facilities
meetings and chat system of a proper classroom. Assignments,
only. The facilities of a calls, chats, quizzes, grading,
proper classroom are not attendance, everything can be done
present. easily.

Requirement Analysis

3.1 Event Table

Table 3.1: Event Table

5
Event Table
Event Trigger Source Action
User signs up User taps the signup End user Signup
button
System verifies System receives user data System Verify Credentials
credentials
User signs in User taps the Sign In End user Sign In
button
System Verifies System receives user data System Verify Credentials
email and
password
User view User taps view Activity End user View Current
Activity (Feed) button Activities
User view my User taps view my End user View recent activities
Activity activity button
User view User taps the setting End user View Setting
Setting button
User view Chats User taps chats button End User Start new chat
User view teams User taps the teams button End User All teams show
User create a User taps the create team System Teams created
new team button
User hide/ User taps the selected End User Hide/ Unhide teams
unhide a team teams
User view User taps the assignment End User View Assigned
assignment button Assignments
User submit User taps the turn in End User Turned In
Assignments button
User View Call User taps the call history End User View User Call
History button History
User Add User taps the button to End User Added and Call
Contacts to Call add contacts
User View User taps the button of End User Open Voicemail
Voicemail voicemail
User view recent User taps the button of End User Open File
files files
User download a User taps the download End User Downloaded
file file button
User Upload a User taps the upload file End User Uploaded
file button
User Schedule a User taps the calendar End User Schedule
meeting button
User edit User taps the edit meeting End User Display Meeting
meeting button
User cancel a User taps the cancel End User Cancel Meeting
meeting meeting button

6
User added more User taps the Apps button End User View Apps
Apps
User download User taps the download End User Downloaded
App app button
User Submit an User taps the submit app End User Submitted
App Catalog button
User view help User taps the help button End User Help Information
User Signs Out User taps the sign out End User Sign Out
button

3.2 Detailed Use Case

Table 3.2: Module Use Cases

M1-UC1 Activity
M1-UC2 Chats
M1-UC3 Teams
M1-UC4 Assignment
M1-UC5 Files
M1-UC8 Apps
M1-UC9 Help

3.2.1 M1-UC1: Activity

Table 3.1: ActivityUse Case

Use Case ID: UC-01

Use Case Name: Activity
Actors: User (Person, Admin)
Description: The Teams user activity report gives a view of the most common activities that

7
 users perform in Teams. This includes how many people engage in a chat in a
channel, how many communicate via private chat message, and how many
participate in calls or meetings.
Trigger: When user clicks on the “Activity” button.
Preconditions: 1. User must have one or more existing network.
2. User must have registered account.
3. User must have logged into their account.
4. The homepage must be loaded.
Postconditions: User can see all the recent activities and reply all the notifications which user
wants.
Normal Flow: 1. The user will have to register an account if not registered by filing the
certain fields and submit the response.
2. The user will need to verify the account and then log in to the account
according to the data registered.
3. The homepage will be loaded which will contain Activity Button along
with other buttons.
4. After clicking the button, the list pane shows an activity feed that
contains a summary of everything that's happened in the team
channels user follows.
5. When user select an activity feed in the list pane, its contents are
shown in the content pane.
6. User can find the messages which user has sent in My Activity.
7. When user has an interesting notification, he/she can navigate to the
action and participate. For example, if a teammate has @mentioned
user, go to the message with the @mention in the Post tab, see what
it's all about, and reply to the message.
8. User can fine-tune what sort of notifications users receive in the
Activity feed, in users’ email, or in the banners.

Alternative Flows: N/A

Exceptions: N/A
Business Rules: N/A
Assumptions: N/A

3.2.2 M1-UC2: Chats

Table 3.2: Chats Use Case

Use Case ID: UC-02

Use Case Name: Chats
Actors: User (Student, Admin)
Description: Chat is the core messaging functionality of Microsoft Teams. When having a
private chat, you can message, call, screen share, and add other people to the
conversation all from a single interface. Conversations in chats, either with one
person or a group, are all linear.

8
Trigger: When user clicks on the “Chats” button.
Preconditions: 1. User must have one or more existing network.
2. User must have registered account.
3. User must have logged into their account.
4. The homepage must be loaded.
Postconditions: 1. The contact will be available if user started old chats.
2. If user wants to start a new chat, he/she must have the name of the
contact followed by their availability information.
Normal Flow: 1. The user clicks “Chats” tab.
2. When user selects this view, the list pane shows a list of recent
conversations. The most recent conversation is opened in the content
pane.
3. User can browse the list of conversations and select one to display it in
the content pane.
4. If user can start a new conversation either group or private chat, the
focus moves to the message compose box.
5. Type the message, user can also add attachments or even emoji,
stickers, or memes to spice up the message and send a message.
6. User can pin a chat, which puts it at the top of the Recent tab.
7. User can pop out a private or group chat into a separate window. This
lets user do something else in the main Microsoft Teams window and
quickly switch when user want to.
8. User can mute a chat to stop receiving notifications. To start receiving
notifications again, unmute it.
9. User can filter the messages in the chat view in Microsoft Teams by the
name of a person to show only group chats, meeting, or private chats
where that person is a participant. User can also filter the list to show
only unread chats, meeting, or muted chats.
10. Particularly important private chat messages can be marked as urgent.
Urgent message will send an alert to the recipient every two minutes
for a period of twenty minutes.
Alternative Flows: N/A
Exceptions: When admin user will be restricted the notifications and filters of participants
chat.
Business Rules: N/A
Assumptions: The user must have an idea how to add and filter the chats.

3.2.3 M1-UC3: Teams

Table 3.3: Teams Use Case

Use Case ID: UC-03
Use Case Name: Teams
Actors: User (Person, Admin)
Description: In Microsoft Teams, teams are groups of people brought together for work,
projects, or common interests. Teams are made up of two types of channels —

9
 standard (available and visible to everyone) and private (focused, private
conversations with a specific audience).
Trigger: When user clicks on the “Teams” button.
Preconditions: 1. User must have one or more existing network.
2. User must have registered account.
3. User must have logged into their account.
4. The homepage must be loaded.
Postconditions: User must have to create a team or will be added in a team channel.
Normal Flow: 1. The user clicks “Teams” tab.
2. When you select this view, the list pane shows a hierarchical list of all
teams you are a member of, and the channels created under each
team.
3. The most recently viewed channel is opened in the content pane. In this
view you can join, create, or manage teams, add members to teams, or
create and follow channels.
4. User can hide teams to unclutter user’s teams list and focus on the
teams you're using actively. Hiding a team moves it to the Hidden
team’s menu at the bottom of user team’s lists where user can access it
as usual. User can always unhide a team and return it to the teams list.
5. If user is a team admin, he/she can edit the team details which include
the team name, description, and privacy setting.
6. If user is team admin, he can modify the team setting which include
team members and guest permissions, team picture and code,
@mention permissions, settings for fun such as emoji’s and GIFs and
team expiration information.
7. If user is a team admin, he can delete a team. When user delete a team,
team activity in channels, files and chats is also deleted.
Alternative Flows: N/A
Exceptions: User cannot be able to reply the notifications in teams if admin user can disable
it.
Business Rules: N/A
Assumptions: User must have an idea how to join or create a team.

3.2.4 M1-UC4: Assignment

Table 3.4: Assignment Use Case

Use Case ID: UC-04
Use Case Name: Assignment
Actors: User (Person, Admin)
Description: Assignments can be used to assign different tasks to students. The students have
to upload their solutions within a deadline.

Trigger: When user clicks on the ‘Assignments’ button.

10
Pre-conditions: 1. User must have registered account
2. User must have logged in to their account.
3. The homepage must be loaded
Post-conditions: 1. Solutions must be turned in for completion once the student uploads
them.
2. If an assignment is not submitted within the deadline and the teacher has
not kept the “turn in late” option, it won’t be possible to turn in.
Normal Flow: 1. The user will have to register an account if not registered by filing
the certain fields and submit the response.
2. The user will need to verify the account and then log in to the
account according to the data registered.
3. The homepage will be loaded which will contain “Assignments”
button along with the other buttons.
4. After clicking the button, the user will be redirected to the
assignments page.
5. If the user is a teacher, clicking on the “create” button will allow
them to upload an assignment for the students.
6. If the user is a teacher, any assignments they have sent to
students or scheduled to assign later will display by order of due date
under the Assigned arrow. They will select Load previous and Load
more to browse the list. 
7. By clicking on the drafts button, they can view the assignments
they have as draft and by clicking on the returned button, they can view
the assignments that they have returned to the students.
8. If the user is a student, they will be able to view all the assigned,
returned and completed assignments.
9. Clicking on any specific assignment will show them that
assignment and by clicking on “add work” followed by “turn in”, they can
submit their assignment.
Alternative Flows: N/A

Exceptions: 1. The student will not be able to turn in an assignment if it has

passed its due date.
Business Rules N/A
Assumptions: 1. User understands English.
2. User is either a person/participants or Admin.
3. User understands the concept of assignments.

3.2.5 M1-UC5: Files

Table 3.5: Files Use Case

Use Case ID: UC-05

11
Use Case Name: Files
Actors: Users (Person, Admin)
Description: Files are used to exchange different study related material. Teachers can send
lectures, books, and notes in the form of files and the students can also
upload anything as required.
Trigger: When user clicks the “Files” button.
Preconditions: 1. User must have registered account.
2. User must have logged in to their account.
3. The homepage must be loaded.
Postconditions: 1. There must be a file present in order to open it.
2. User can upload any file saved in his system.

Normal Flow: 1. The user will have to register an account if not registered by filing the
certain fields and submit the response.
2. The user will need to verify the account and then log in to the account
according to the data registered.
3. The homepage will be loaded which will contain “Files” button along
with the other buttons.
4. After clicking the button, the user will be redirected to the Files page.
5. Here he can view all the files uploaded along with their names, date,
uploaded by whom and on which channel.
6. By clicking on a file, the user will be able to view or download it.
7. By clicking on a folder, the user will be able to view the contents of
that folder and access files from there.
8. By clicking on upload button, he can upload a file.
9. By clicking on the “create folder” button, a folder will be created in
which multiple files can be uploaded.
Alternative Flows: 1. After logging in to the account and the loading of the homepage, click
on the team’s button where multiple channels will be available.
2. Select any specific channel and once its page is loaded, click on the
files button on top.
3. Here the user can view all the files uploaded in that specific channel.
4. By clicking on the download button, he can download a file.
5. By clicking on a folder, the user will be able to view the contents of
that folder and access files from there.
6. By clicking on the upload button, he can upload a file.
7. By clicking on the “create folder” button, a folder will be created in
which multiple files can be uploaded.
Exceptions: 1. User might not be able to access a file or the system might give an
error due to security issues or some problem in that file.

Business Rules N/A

12
Assumptions: 1. User must be familiar with English.
2. User must be familiar with the concept of files, folders, and
documents.

3.2.6 M1-UC6: Calls

Table 3.6: Calls Use Case

Use Case ID: UC-06
Use Case Name: Calls
Actors: User (Person, Admin)
Description: Calls can be used to make a call to anyone and speak to them. Group calls can
be made, voicemails can be sent or received, and the user can view his
contacts and call history.
Trigger: When user clicks on the “Calls” button
Preconditions: 1. User must have registered account
2. User must have logged in to their account.
3. The homepage must be loaded
Postconditions: 1. The other user must be available in order to receive call.
Normal Flow: 1. The user will have to register an account if not registered by filing the
certain fields and submit the response.
2. The user will need to verify the account and then log in to the account
according to the data registered.
3. The homepage will be loaded which will contain “calls” button along
with the other buttons.
4. After clicking the button, the user will be redirected to the calls page.
5. User will be able to call anyone by clicking on “make a call” button and
by searching the name of the person they wish to call.
6. User can view their contacts by clicking on the contacts button and
add any new contacts by clicking on the “add contact” button.
7. User can view the history of his calls by clicking on the “history”
button.
8. Any ongoing call can be muted, hung up or put-on speaker.

Alternative Flows: After logging in and being on any channel where the user can view different
profiles, he can call any of them by bringing the cursor to that profile and
clicking on the “voice call” button from the list of options that appear.
Exceptions: The other user might not be available or have their internet connection so
they might not receive the call.
Business Rules N/A

13
Assumptions: 1. User has the ability of speaking and listening.
2. User can understand English.

3.2.7 M1-UC7: Calendar

Table 3.7: Calendar Use Case

Use Case ID: UC-07

Use Case Name: Calendar
Actors: User (Person, Admin)
Description: The Calendar can be used to schedule and coordinate appointments, meetings,
and events with members of the Team that automatically show up in the
calendar for other members.
Trigger: When user clicks on the “Calendar” button.
Preconditions: 1. The user must have registered account.
2. The user must have logged into their account.
3. The homepage must be loaded.
Postconditions: The meetings, events will be scheduled which could be modified or cancelled
later.
Normal Flow: 1. The user will have to register an account if not registered by filing the
certain fields and submit the response.
2. The user will need to verify the account and then login into the account
according to the data required.
3. The Homepage will be loaded which will contain Calendar Button along
with other Buttons.
4. After clicking the buttons, the user will be redirected to the page where
the meetings will be scheduled by filling out Title field, Required
Attendee’s field, starting date and time, ending date and time, Add
Channels field and details of the meeting.
Alternative Flows: N/A
Exceptions: N/A
Business Rules: N/A
Assumptions: N/A

3.2.8 M1-UC8: Apps

Table 3.8: Apps Use Case

Use Case ID: UC-08

14
Use Case Name: Apps
Actors: User (Person, Admin)
Description: The Apps feature can be used to manage apps via a “Manage Apps” page. This
allows us to view all of the available apps in the tenant, plus gives information
to assist with decisions surrounding which apps would be best for the
organization. The app catalogue also gives the ability to streamline the testing
and distributing line-of-business applications process. The Teams App Bar lets
you pin personal apps to the Teams app bar (on the left-hand rail). All we have
to do is locate the app you’d like to pin for easy access, right click on the app
icon, and choose “pin.” The app icon will remain in your Teams app bar so that
you can access it easily. Microsoft Teams also lets you pin apps to relevant
channels or chats for Simply find the app, right-click the app icon, and select
“pin”.
Trigger: When user clicks on the “Apps” button.
Preconditions: 1. The user must have registered account.
2. The user must have logged into their account.
3. The homepage must be loaded.
Postconditions: The user must have strong internet connection.
Normal Flow: 1. The user will have to register an account if not registered by filing the
certain fields and submit the response.
2. The user will need to verify the account and then login into the account
according to the data required.
3. The Homepage will be loaded which will contain App Button along with
other Buttons.
4. After clicking the App button, drop down menu of different apps will be
displayed where user can select any app from the list, user can also
search any app using search bar.
5. More Apps will be shown after clicking on the option present at the
bottom of the drop-down menu.
6. Drop-down list of different categories of the app will be displayed on
the right sidebar while the left side will show the grid view of apps
along with their pictures and description.
Alternative Flows: N/A
Exceptions: 1. The Apps will not work in case of poor internet connection.
2. The app will only be unpin when pin feature is enabled.
Business Rules: N/A
Assumptions: N/A

3.2.9 M1-UC9: Help

Table 3.9: Help Use Case

Use Case ID: UC-09
Use Case Name: Help
Actors: User (Person, Admin)
Description: The Help Button will help users in answering any of their queries. It will also let

15
 user have a tour guide of the whole teams.
Trigger: When user clicks on the “Help” button.
Preconditions: 1. The user must have registered account.
2. The user must have logged into their account.
3. The homepage must be loaded.
Postconditions: N/A
Normal Flow: 1. The user will have to register an account if not registered by filing the
certain fields and submit the response.
2. The user will need to verify the account and then login into the account
according to the data required.
3. The Homepage will be loaded which will contain Help Button at the
bottom with question mark icon along with other Buttons.
4. After clicking the Help Button, a drop-down menu will be displayed
which will contain topic, training, what’s new, Ask the community and
suggest the feature options.
5. The user can learn more about the team’s app on clicking any related
topics from the topic button.
6. Microsoft Teams also provide the feature of training where user can
have all the information of how to use teams.
7. The about option contain the information of Teams such as its version.
8. The latest updates notification and other information will be displayed
on the page of what’s new.
9. Teams apps have their own refresh button at the top right corner of the
window.
Alternative Flows: N/A
Exceptions: N/A
Business Rules: N/A
Assumptions: N/A

3.3 Functional Requirements

Functional requirements of our system are explained below.

 Users must have valid User ID and password to login thus creating their individual
profiles.
 Administration can register new teachers.
 Students can choose courses.
 Attend lectures either at the scheduled time or view lecture later.
 Video lectures facility can also be available for the students.
 Students can check attendance, result, and assignments.

16
  Faculties can take lectures, upload assignments, announcements, compile results and can
upload lectures and other discussions in various formats as in videos, power point
presentation etc.
 Notice board facility can also be available for the students from administration and
teachers.
 Notice board can also be available for the teachers from administration.
 Forms and guidance can also be available for the students regarding any query.
 There can be platform to discuss various queries and to put up suggestions posted both by
students and teachers.
 Documents and media library that can help in active learning of a student.
 Student can send any application to the administration for any query.
 Administration can post upcoming events banner.

3.4 Non-Functional Requirements

Non-functional requirements of our system are mentioned below:

 Secure access of confidential data (user’s details).

 Maximum time availability

 Better component design to get efficiency at peak time.

 Flexible service-based architecture will be highly desirable for future extension.

 Teacher registration facility is accessible by administration only.

Design and Architecture

17
4.1 Design Models

4.3.1 Structural Diagrams

4.3.1.1 Class diagram

18
4.3.2 Behavioural Diagrams

4.3.2.1 Use Case diagram

Figure 4.1: Use Case Diagram

19
Figure 4.2: Use Case Diagram

20
 Figure 4.3: Use Case Diagram

4.3.2.1 Activity diagram

21
22
23
24
4.3.2.2 Sequence diagram

Figure 4.10: Chat Diagram

25
26
27
 Figure 4.11: Teams Diagram

Figure 4.13 Assignment Sequence Diagram

28
Figure 4.14 Call Sequence Diagram

29
Figure 4.15: Call Sequence Diagram

30
Figure 4.16: Files Sequence Diagram

31
32
Figure 4.16: Calendar Sequence Diagram

33
Figure 4.17: App Sequence Diagram

34
Figure 4.18: Help Sequence Diagram

35
Implementation

5.1 User Interface

Figure 5.1: Main Screen

36
Figure 5.2: User Activity

37
Figure 5.3: User Chat

38
 Figure 5.4: Teams

Figure 5.5: Assignment

39
Figure 5.6: call

Figure 5.7: Files

40
Figure 5.8: Calendar

Figure 5.9: Apps

41
Figure 5.10: More Apps

Figure 5.11: Help

42
Figure 5.12: Profile

43
Figure 5.12: Settings

44
Testing and Evaluation

Unit Testing

6.1.1.1 Unit Testing 1: Signup

Testing Objective: To ensure the signup form is working properly and user gets registered on valid
username and password.
Test Case Id: TC_U1
Test Case Description: Test the signup functionality.
Table 6.1: Test Cases for Signup
No. Test Case/Test Test Data Expected Result Actual Result Pass/Fail
Script /Not
Executed
/
Suspended

TC-01 Email and Email: User newsfeed User newsfeed Pass

password valid [email protected] appears. appears.
Password:
google36@
TC-02 Email format Email: mail Message Message Pass
invalid Password: displayed “email displayed “email
google0336 badly formatted” badly formatted”

45
 6.1.1.2 Unit Testing 2: Login

Testing Objective: To ensure the login form is working properly and user is logged into his
profile.
Test Case Id: TC_U2
Test Case Description: Test the Login functionality.
Table 6.2: Test Cases for Login
No. Test Case/Test Test Data Expected Actual Result Pass/Fail/Not
Script Result Executed/
Suspended

TC-01 Email and Email: User newsfeed User newsfeed Pass

password valid [email protected] appears appears
Password:
google36@
TC-02 Email Invalid Username: Message Message Pass
[email protected] displayed displayed
Password: “username “username does
google36@ does not exist” not exist”
TC-03 Password Username: Message Message Pass
invalid [email protected] displayed displayed “invalid
Password: “invalid password”
gogle36 password”

6.1.1.3 Unit Testing 3: Assignment

Testing Objective: To ensure the Assignment either successfully submitted or Created.

Test Case Id: TC_U3
Test Case Description: Test the Assignment functionality.
Table 6.3: Test Cases for Assignment
No. Test Case/Test Test Data Expected Result Actual Result Pass/Fail/Not
Script Executed/
Suspended

TC-01 Create Instructions Assignment Created. Assignment Created. Pass

Assignment
TC-02 Submit Files Message displayed Message displayed Pass
Assignment “Turned in at” date “Turned in at” date
+time. +time.

46
 6.1.1.4 Unit Testing 4: Schedule meeting

Testing Objective: To ensure that Meeting is Scheduled.

Test Case Id: TC_U4
Test Case Description: Test the Schedule Meeting functionality.
Table 6.4: Test Cases for meeting
No. Test Case/Test Test Data Expected Result Actual Result Pass/Fail/
Script Not
Executed/
Suspended

TC-01 Schedule Date, time, Meeting Meeting Pass

Meeting Sharing link Scheduled. Scheduled.

6.1.1.5 Unit Testing 5: View Files

Testing Objective: To ensure that user can view all the files.
Test Case Id: TC_U5
Test Case Description: Test the Files functionality.
Table 6.5: Test Cases for Files
No. Test Case/Test Test Data Expected Result Actual Result Pass/Fail/
Script Not
Executed/
Suspended

TC-01 Files Button: Files Displayed All Displayed All Pass

files files

47
Conclusion and Future Work

7.1 Conclusion
In conclusion, our project will combine the benefits of a physical classroom with the
convenience of a ‘no-physical-bar’ virtual learning environment, minus the change hazards and
expenses. This will provide more flexibility in the existing learning platform structures. It
provides a means of collaborative learning for the students and promotes the distance learning.

7.2 Future Work

The application currently supports all devices whether it be cellphone, tablet, or computer.
However, in the future we aim to provide upgraded features of the applications to ensure user’s
ease.

48
49