Project Report

Smart Report Web

Application
Muhammad Ali Khan – Roll No
Nouman Akram - Roll No
Sher Afghan - Roll No
Manpreet Singh Dhillon - Roll No
Contents
Executive Summary.....................................................................................................................................2
1. Introduction.........................................................................................................................................3
1.1 Problem Statement.......................................................................................................................3
1.2 Highlight on Problem..................................................................................................................3
1.3 Vision Statement..........................................................................................................................3
1.4 User Stories and Acceptance Criteria..........................................................................................4
1.5 Stakeholder Analysis and Identification......................................................................................6
2. Project Objectives................................................................................................................................7
3. Literature Review................................................................................................................................7
4. Project Methodologies.........................................................................................................................8
4.1 Agile Methodology......................................................................................................................8
4.2 SDLC...........................................................................................................................................9
5. Wireframes........................................................................................................................................10
5.1 Frameworks...............................................................................................................................12
Back-end Development:....................................................................................................................12
Front-end Development:....................................................................................................................13
6. Storyboards and Timeline of Project Development...........................................................................13
7. Solution to the Project Problem.........................................................................................................14
8. Project Plan........................................................................................................................................15
9. Testing...............................................................................................................................................16
10. Product Overview..........................................................................................................................17
11. Demonstration of Project Development.........................................................................................17
User Manual..........................................................................................................................................17
Lecturer:............................................................................................................................................17
Project Manager:...............................................................................................................................25
Students:............................................................................................................................................35
12. Results and Findings of the Product Testing..................................................................................41
12.1 Objective of Testing..................................................................................................................41
12.2 Testing Approach.......................................................................................................................41
12.3 Testing Process..........................................................................................................................42
12.4 Test Cases..................................................................................................................................43
12.5 Tools and Environment for Testing...........................................................................................49
 12.6 Testing Scope............................................................................................................................50
Functional Requirements...................................................................................................................50
Non-functional Requirements............................................................................................................51
12.7 Procured Results........................................................................................................................51
13. Summary, Limitations and Areas of Improvement........................................................................51
13.1 Limitations of Application.........................................................................................................52
13.2 Areas of Improvement...............................................................................................................53
References.................................................................................................................................................54
Executive Summary
The aim of this project is to create an application that will make the assignment submission
process easier for both students and lecturers. In this project, separate dashboards have been
created for lecturers and students that cater to their needs. The application has login and signup
functionalities. The user can regain his lost password. After signing up, the lecturer can assign
tasks to the students and appoint a Project Manager. He can view the tasks and progress of his
students and give his feedback on it. The project manager will be managing the group of students
and assigning tasks to them. The students can perform their assignments, submit them, and get
their grades. Use of databases is also included in this project to save all the information of the
users. This report has the complete outline of the assigned tasks and has been structured for
better understanding accordingly. The aim and objectives of the project are also included. It also
has a detailed description of the functionalities and operations that were involved in the project.
appropriate tests have also been applied to the project to finalize the approach, tools, processes,
requirements, and results of the application. The project deliverables have been defined which
include the problem statement supported by a research background. Lastly, a comprehensive
discussion on the limitations, uses and improvements on the application have been included.
 1. Introduction
This application has the title of Smart Report Web Application and has been designed for
lecturers and students to give them a platform where they can submit and grade their
assignments. An application like this is useful since both students and lecturer can manage their
assignments. This application is focused on providing a systematic method to submit, assign and
grade assignments. It provides a common place for both lecturer and students where they can
come together and easily deal with their projects without getting confused on their deadlines and
submission criteria. Students will be able to view their previous assignments and lecturers will be
able to track the students’ progress. The main aim of this project is to create a responsive
application design that is functional on various platforms. All the methodologies and roadblocks
while using them in this project are clearly explained.
The application has been divided into three parts: lecturer, student, and project manager. All
these users have their own jobs in the application. The methodologies and frameworks adopted
for this project are discussed in detail in this report. The report also explains the stakeholder’s
involvement and issues related to the project. A detailed summary of the benefits and setbacks of
the application have also been given. This report also sheds light on how it is a solution to
different problems.
1.1 Problem Statement
Students mostly hand in their projects and assignments as groups. The main issue was that when
the assignment was submitted, the lecturer graded it as a whole. This led to all of the members
getting the same grade no matter how much hard work they’ve put in it. Students who had
worked more felt unfairness as their grade was similar to the members who hadn’t done any
work [ CITATION Cha10 \l 1033 ].

1.2 Highlight on Problem

It has been observed that lecturers face a lot of problems while assigning tasks to their students,
especially if they are group projects. They must assign individual and group assignments and
award grades. Lectures find it difficult to keep students in check regarding what they are doing.
Students also find it hard to know what their tasks are and in some cases under extreme pressure,
they might forget their deadlines as well. Another issue is that the grades are assigned as a group
rather than on individual basis, which is unfair for the students who have worked harder or more
efficiently in the group as compared to others [ CITATION Cha10 \l 1033 ].
An application is needed which will allow the students to easily view their assigned tasks, submit
them and view their grades. For lecturers, they need a platform where they can check the
students’ progress and easily give them grades according to group and individual efforts.
Lecturers also can assign Project Managers for each group so the group can have a representative
who will manage everything and be responsible for sending the final report to the lecturer.
1.3 Vision Statement
The aim of this project is to create a fully functional application for online and smart report
applications. It will provide ease to students and lecturers who must deal with assignments
during their academic years. It will make sure that the completed and pending assignments are all
stored in one place so that students and lecturers can access it at any time. [ CITATION Jos21 \l 1033
] This will save the extra time of arranging assignments and keeping lists of students in various
files. Students will also never forget any deadlines of their assignments. Aiding the education
department is the main objective of this project.
1.4 User Stories and Acceptance Criteria
User stories are explained in detail in this section. The application was programmed using many
languages and advanced coding techniques. The user stories are always influenced by the
opinions and requests of the clients. This application has three main users: Student, lecturer, and
project manager.
ID As a I want to So that I can Acceptance Criteria
1 Project Create a team Assign and divide sub- Have to be assigned project
Manager tasks among them manager by the lecturer.
Should be logged in and
registered at the portal
2 Perform role management For efficient completion of Should be logged in and
tasks registered at the portal.
Have to be assigned project
manager by the Lecturer.
3 Send request to Lecturer Get feedback on individual Should be logged in and
and group progress registered at the portal.
Have to assign work to the
members first and make
sure they are making a
progress.
4 See the progress in Urge my teammates to Have to assign work to
percentage complete their assigned team members and set
tasks. deadlines.
5 Set deadlines Make sure everyone has Have to receive task from
completed work on time lecturer
Have to assign work to
team mates.
6 Generate individual and Make sure everyone has Assign work to all team
group assessment given their proper input members
Check the progress
7 Only generate final report Make sure that no sub- Should be logged in and
when the whole project is tasks are left before proper registered at the portal.
completed submission.
Have to assign tasks to
 students.
Have to make sure that the
work is completed.
8 Student Get email invitation Register in the portal -
9 View group profile Know who my group Have to be registered in the
mates and project manager portal
are.
10 View assigned tasks Work on their completion Should be logged in and
registered at the portal
11 Edit tasks Add or remove any Must have a task assigned
additional information in to him.
the assignment.
Must have done some work
on it.
12 Submit tasks Get more tasks or finish Must have a task assigned
my portion of the work. to it,
Should have completed the
work.
13 View progress See how my members are Should be assigned a task
working by the project manager.
Should be working on it.
Should be a part of the
team.
14 View feedback Know about the Should have done
shortcomings in the part of some/complete work on the
the assignment I have assignment.
done
Should be a part of the
team.
The lecturer must be
invited by the project
manager.
15 View grades Know about the result of Must have completed my
my hard work. assignment.
Must be part of the team
16 Lecturer Send emails to students Login and register in the Must be invited by the
application project manager.
Should be logged in and
 registered at the portal
17 Assign a project manager Assign the task to him to Should be logged in and
assign to his members registered at the portal.
Send an email to the
student
18 Create tasks Assign them to teams Should be logged in and
registered at the portal.
Should have assigned
project manager
19 View the progress of Keep in check how the Should be logged in and
assignment students are doing registered at the portal.
Must be invited by the
project manager.
20 Give feedback Point out the mistakes and Must be invited by the
shortcomings of the project manager
assignment
21 Receive invitation form Give feedback to the Should be logged in and
project manager assignments. registered at the portal.
22 Grade assignments Evaluate the students Should be logged in and
individually and within a registered at the portal.
group
23 Add and remove students Keep the discipline in Should be logged in and
check registered at the portal.

1.5 Stakeholder Analysis and Identification

Stakeholders include all the people who are directly or indirectly involved in the development of
the project [ CITATION Fer21 \l 1033 ]. It is very important to decide the priority of the stakeholders
and their involvement in the project’s development. The application is not developed by a single
person but requires the involvement of many people such as front-end and back-end developers,
database administrators, project managers, testers, etc. They all are given the name of
stakeholders.
Stakeholder Role Organizatio Contact Expectations Influenc Interest
s n Details e
Muhammad Front-end Application Users can High High
Ali Khan Developer navigate
through their
dashboard
 easily.
Sher Afghan Back-end Application Users can High High
Developer easily get their
required data
from the
database and
manipulate it
according to
their wishes.
Nouman Database Application Users can store High High
Akram Administrator their data
seamlessly in
the database.
Manpreet Tester and Application Users can High High
Singh Designer easily navigate
Dhillon through the
user-friendly
website.

2. Project Objectives
The main objective of creating this project is to make sure that users can have a user-friendly and
responsive application for their use. This project aims to provide a joint platform for its users
where they can conveniently upload and submit their assignments and increase efficiency of their
course work. The project meets the criteria of all its users including the Lecturer, Student and
Project Manager login [ CITATION Jos21 \l 1033 ]. All the users have been given their own
credentials for logging in the portal. The application is compatible with all kinds of browsers.
The application has been tested multiple times to ensure that it is bug-free. Lecturers can easily
keep an eye on their students’ progress and students can also keep track of their ongoing and
completed assignments. Nowadays, everything is being digitized, including assignments and
paperwork is declining. This application has been created to keep up with the trends and ease the
users. This project is expected to increase the student satisfaction and involvement with their
course work.
In other words, this report aims to enhance the student and lecturer experience. Having proper
communication and guidance is the best way to ensure that the students are improving and
learning and this project helps to do just that.

3. Literature Review
With the advent of technology, many new applications are being adopted for making everyday
tasks easier. Everyday new technologies and techniques are being introduced for improved
functionalities. Nowadays, almost every task is being done online. Almost all the books being
published have an online format and the old books are being converted online as well so that
they can be distributed and are easily accessible to students all over the world. Online education
system has rapidly become popular because of the advancing technologies and the ever-changing
situations of the world.
In their article, Geri and Naor-Eliza (2008) discussed about 284 users who were enrolled in a
university that was using an online submission, but they later abandoned it. This was because
even though their main aim of launching this technology was the same as ours, providing ease of
use, enhancing functionality and adopting new technologies, it was not adopted because students
felt a communication gap with the lecturers and felt more comfortable with speaking with the
teachers in person.
Naor-Elaiza and Geri (2009) stated in another article that the reason lecturers were not
comfortable with using the online submission system was because checking the assignments and
grading them was not easy. Many lecturers could not comfortably use the new system and it was
difficult for them to grasp the functionality of the application.
Another reason why students stopped using the online submission system was because they were
not sure about the grading system. They were also skeptical about the confirmation that they got
after they had submitted the assignment since they had issues with it sometimes. Also, many
students did not like the fact that they had to upload images for their assignments. Sometimes the
pictures could be blurred and their grades could drop just because the lecturer misunderstood the
concept because of the distorted image. (Bridge and Appleyard (2008))
Much research was done to find out how to overcome the challenges explained above. One of
them was to implement the TAM (Technology Acceptance Model) so that many users can find it
easy to adapt to the new changes that the technology brings. This was done by showing many
advantages of the technology and their positive effects that the application will have on their
lives. by showing them the end point and the ease of use of the Smart Report Web Application.
Some of these issues were also solved by using the Smart Report Web Application. Great care
was given in the planning phase so that the application is user-friendly and has a design that
students and lecturers both can use comfortably. great effort was put in for lecturers as well so
that they can effectively grade the individual and group assignments and have no problem
navigating around the application.
For students, uploading documents was made possible so that they don't have to put up pictures
of their assignment. The application allowed students to edit their work and upload it as they
wished.
Other than this, other requirements of the application were obtained through interview questions.
Many potential users were interviewed and their results were recorded. different open-ended
questions were also asked by the researchers. all of these answers were then used to extract
important information for increasing the functionality of the application. all of this information
and its extraction method comes within the realm of literature review.
Even though the information related to the uses of the application are being documented, they are
no doubt really different to the implementation. A functional software is more powerful than a
documented plan. To ensure that the documented plan smoothly transitions to the ideal
application with all the important functionalities, several project methodologies are used.

4. Project Methodologies
There are some project methodologies that are accepted for the development of the project that
we are working on. The details of some of them are given below.
4.1 Agile Methodology
It was discovered that in the previous years, there were traditional software development
methods such as waterfall methodology that had many issues with it and wasn’t very reliable for
effective software and application development. This gave rise to the development of Agile
methodology which mainly focuses on agile development. This means that the whole
development phase is flexible and can cope with the requirement and schedule changes.
[ CITATION Ill04 \l 1033 ].

Agile model renders on different values which enhances its value as a software development
model. They include strong individual and team collaboration, functional software over a well-
written document, collaboration between developer and customer, and flexible behavior towards
change of requirements. [ CITATION Ham21 \l 1033 ].
There are five main steps that make up the agile model that we are following for this project. first
is the planning phase in which all the requirements are collected and a plan is made for the
application. The flow of the application, all the functionalities, the risks, the errors and the
methodologies and technologies used are discussed in this phase for a rough outline.
In the design phase, the stakeholders, mainly the development team is selected for the
application. The team leader checks the profiles of the available members and choses the one that
is closer to the requirements he is looking for. The plan is laid in front of them and is improved
as they input their own ideas.
The Development phase is the longest and major phase of the whole plan. In this, the application
is developed. All functionalities are enabled and the application is connected to the database. The
first version of the application is created which can be improved in other iterations after taking
feedback from the clients.
In the Testing phase, the application is tested by developers for any bugs and errors. Also,
contingency methods are deployed in case of any crashes and the application is ready for release
for the customers.

In the deployment phase, the application is released to the customers for use. The customers
may use the application and also give their review to the developers. The developer may make
necessary changes so that the application is up-to-date with the current trends.
4.2 SDLC
System Development Life Cycle is almost similar to Agile methodology that is why it is
included in the development of the application. With an exception of a few minor differences,
the two methodologies are practically similar.
SDLC is a process that can be used to handle the projects smoothly and develop high quality
software efficiently. The main reason of adopting this model is that it is adjustable for all project
sizes whereas Agile model is only for small scale projects. It is very flexible at the development
phase, although making changes in the initial phases become harder as go towards the ending
stages. [ CITATION Ped \l 1033 ]

5. Wireframes
The wireframes for the Project Manager, the Lecturer and the Student is given below.
The Project Manager can receive assignments from the lecturer, convert it into sub-tasks and
assign them to his group members. He can also set deadlines for the tasks that he has assigned.
PM can also request the lecturer to give feedback to the tasks he and his group members are
doing. He can also check his members’ progress. After the task has been completed, PM can
download and send the individual or group report to the lecturer.
Lecturer can perform many tasks from his dashboard. He can create team from the list of his
students. He can assign them tasks, set up a Project Manager and set deadlines for the
assignment. He can check the individual and group progress of each group and also give
feedback. He can accept/reject the PM’s feedback request as well. He can also remove students if
he wants. He can also grade the assignments and upload them for the students to view.
Student can login to his dashboard through the email request the lecturer has sent. He can view
his team members and the task that he has been assigned. He can edit and create the assignment.
He can also delete his work and start over. He can submit his assignment and also view his and
his team members grades.
5.1 Frameworks

Back-end Development:
Just like the name suggests, the back-end framework is the backbone of the whole project. if
there is no back-end, the application is only for show and has no interactive abilities [ CITATION
Mar21 \l 1033 ]. The back-end functionality depends on a number of API and servers. It is widely
known that the design in itself is ineffective if the back-end functionality is not working
properly.
For this application, the main language for the back-end development is the core PHP. All the
libraries have been imported from Composer. This language has given strong functionality to the
whole application. The database used for this project is driven by the SQL language. This
database has effectively stored all the data and is also linked with the design of the application.
Using PHP for connectivity has proved to be very effective since many simple codes are
included in the library that allow easy connection of the application with the database.

Front-end Development:
The front-end refers to the design and visual aspect of the application. All the information and
interactive buttons are displayed on the screen for the users to view and work with. Mostly users
don’t want to use websites or applications that aren’t attractive or easy to navigate. That is why it
is necessary that the websites have a visually appealing front other than this, ease of use is also
an important factor. If the users are not able to go to the pages they are looking for, they will
leave the website and look for something else. That is why the designers ensure that the menu
bar and the pages are positioned in an easy to navigate place.
For design, the programmers mostly use the languages of HTML, CSS and JavaScript [ CITATION
Ste21 \l 1033 ]. However, for enhanced functionality and interactivity Bootstrap is also commonly
used. This is because PHP and Bootstrap work hand -in-hand for an enhanced interactive
experience. These two languages are compatible with each other. The application is given visual
effects through CSS, but it is truly given its dynamic nature when Bootstrap is added.
It is also very important for websites to be compatible with all kinds of devices, since nowadays,
people use laptops, tablets and mobile phones. The application should be adjustable for all these
screen types so that the users can easily access the website and have a very good interactive
experience.

6. Storyboards and Timeline of Project Development

After gathering related requirements to the application from the client, the work related to the
project was divided among the team members according to their abilities and the timeline was
also decided.
A storyboard consists of the project outline, user stories and sprints [ CITATION Mai20 \l 1033 ].
The project outline was set according to the methodologies mentioned above. All the
requirements for user stories, and their acceptance criteria was also selected. Our team consists
of four team members which includes, a front-end developer, a back-end developer, a database
administrator and a tester.
The project was divided into three Sprints. These three sprints were connected to each other with
the intent of development. In the 1st Sprint, initial work on the development of the application,
the creation of database and linking both of them had started. In the 2nd sprint, the dashboards
were created and linked and the testing on them started. In the final sprint, final touches of the
developments such as creating login and signup pages and completing the design were done.
To set the timeline of the project, the Gantt chart was used. The Gantt chart was created while
keeping the deadline in mind. It had various milestones set that had to be achieved on set times.
The milestones included the following points.
Milestone 1: Starting the development of the project after completing the planning process.
Milestone 2: Creating the dashboard for Project Manager, Lecturer and Student.
Milestone 3: Testing all the functionalities of the project.

7. Solution to the Project Problem

This application is actually a solution of the list of problems that was mentioned above. The most
important one being that lecturer was not able to individually access the students on group
assignments and the whole group received the same grade no matter who had actually worked on
it [ CITATION Jos21 \l 1033 ]. In the application, the lecturer can access the group’s work at any
time and check what the members are doing. The lecturer was also able to assign separate grades
to each of the student.
The lecturer also assigns a Project Manager that manages the team members so that everyone can
do their work on time. The deadlines for each of the task is also set and reminders can be given
to the students. Dividing the tasks creates a sense of responsibility and allows all the members to
work fairly on the whole project.
It is also easier for the lecturer to manage teams and assignments in this manner. The lecturer can
view the dashboard of his students and look at his progress at any time. He can also give
feedback to the students so that they can improve their work before submission.
 8. Project Plan
Planning is a very important aspect of project development. A good plan entails more than half
of the work done. In the planning process, the project workflow is maintained and all the
functionalities of the project are connected to each other [ CITATION Lut21 \l 1033 ]. This is done to
ensure that no effort is wasted and all attributes are functioning as per the requirements. The
project plan also outlines the main tasks that need to be completed in first priority.
The project is defined in the table as follows.
ID Tasks Est. hours Status
1. Gathering requirements 50 Completed
2. Designing the application 45 Completed
3. Creating the application 72 Completed
4. Creating the database 48 Completed
5. Linking the database with the application 30 Completed
6. Completing the functionalities of the dashboard 150 Completed
7. Creating the signup and login pages 50 Completed
8. Linking the application with email 30 Completed
9. Testing the functionalities of the application 25 Completed
10. Writing the report for the application. 20 Completed

The project plan was also created against the Gantt chart which showed the tasks to be done, the
number of days it will take, the starting date of each task and so on. The major milestones are
also mentioned. The diagram also shows the dependent and independent tasks of the project.

9. Testing
Testing of the project is a crucial aspect of the whole process. This is because during
development, many hidden bugs and errors can occur that don’t show themselves until the
application is running. It is also used for quality assurance [ CITATION Zaf21 \l 1033 ].
There are many functionalities that need to be tested in this application. Starting from receiving
the email invitation from the lecturer, signing up and logging in the portal. Other than that,
receiving tasks and uploading assignments is also important. The application can edit, update,
delete and create new tasks and deadlines as well. Checking, giving feedback and grades is also
essential.
For testing, unit testing and integrated testing was done in this project. in unit testing, all the
modules were individually tested [CITATION Ham211 \t \l 1033 ] and in integrated testing, the
migration and sending of data from one dashboard to another was checked [CITATION Ham212
\t \l 1033 ]. All in all, the entire process consists of debugging issues, removing errors and fixing
connectivity issues. The bugs that are fixed are reported.
The application can only run once the user has access to the portal through logging in. the
lecturer manages the portal and can add and delete users any time he wants. Specific login
credentials are necessary for the students and the project manager to login. An active internet is
also needed at all times. The database is accessed through PHP MyAdmin with the help of SQL
language.
 10. Product Overview
The main purpose of this application is to aid students and lecturers during the submission and
assignment of projects. Because of this, the application has been made while catering the
distinguishable sprints which mainly revolved around the Lecturer, Project Manager and
Students. The development team has made many efforts on the interactive design of the
application while keeping all the functionalities in mind. They also catered the needs of the users
and added modules that would ease the use of the application as a whole.

11. Demonstration of Project Development

User Manual
 Lecturer
 Project manager
 Students

Lecturer:
The development phase starts with the Lecturer. This is because the lecturer has the main job in
the whole project. It starts with the lecturer creating the team by selecting the members and the
topics. That is why his role is the main role out of all three participants.
The lecturer can also do the following tasks.
1. Create teams by selecting members.
2. Choosing topics and setting deadlines
3. Assigning project manager
4. Giving feedback on tasks/accepting requests from Project Manager
5. Giving grades on submitted assignments
The pages are given as below.
 Figure 1: Lecturer Signup

The lecturer will sign up in his dashboard though the page that is shown above. He will be then
redirected to the dashboard where he will start creating teams.

Figure 2: Lecturer Dashboard

In the dashboard, he will be able to view all the pending and completed assignments. He will
also be given notifications regarding all the activities that the students are doing.
 Figure No.3: Create New Project

From the menu bar given at the side, click on the Projects and the lecturer will be redirected into
creating the projects. He can write the project names and upload the list of projects that he will
later assign his students.

Figure No. 4: Assign Teams

When the name is entered to the list, an option for inviting team will be given. Once you click on
the button, you will be redirected to the list of students to choose for teams.
 Figure No.5: Invite team and assign Project Manager

from the list of team members, the members for the team are selected. After that, the lecturer will
select the project manager. Once done, the invitation is sent by clicking on the Send Invitation
button.

Figure No. 6: Team updated

 Figure No. 7: Email Invitation sent

The email invitation is sent which can be seen on the student’s email addresses. The students can
click on the Join Team button to get the credentials for the portal and start working.

Figure No. 8: Receiving Feedback Request

Lecturer can receive feedback request from the Project Manager of any group. After he accepts
the request, he is navigated to the tasks of each member on which he can give comments as
shown below.
Figure No. 9: Redirected to Task

Figure No.10: Writing feedback

 Figure No. 11: Feedback updated successfully

After the task has been completed and submitted to the lecturer, the lecturer can assign grades to
the students as well.

Figure No. 12: Assigning Grades

 Figure No. 13: Grade Marked Successfully

At the end, the lecturer will also receive individual report of all the members of the group from
the project manager which he can save and view.
 Figure No. 14: Viewing Individual Report

Project Manager:
After the lecturer assigns the topic, the next main job is of the Project Manager. Project Manager
uploads the assignment related to the topic that the lecturer has assigned and divides it into tasks
for each of the members.
The Project Manager has the following tasks and responsibilities in his team.
1. Upload and distribute tasks among members and set deadlines.
2. Check the progress of the work in progress.
3. Create and delete tasks.
4. Send feedback request to the Lecturer.
5. Submit assignment to the Lecturer.
6. Submit final report to the lecturer.
The details of the project are given below.
The Project Manager will get his credentials from the email invitation and then sign up and log
in the portal.
 Figure No. 15: PM Login

Once login is successfully done, the Project Manager is directed to the dashboard from where he
can do all the required tasks.

Figure No. 16: Dashboard

From the menu bar, the PM goes to the Assignments option to create a new assignment for his
group members.
 Figure No. 17: Assignments

From there he will create a new assignment for his members to view and work on. He will also
set the deadline and then click on Publish.
 Figure No. 18: Create New Assignment

Once the Project Manager has created the assignment, he will view the assignment and all of its
details.

Figure no. 19: View Task

After that, he will click on the Create Task button to create individual tasks for all his members.
 Figure no. 20: Assign Tasks

The Project Manager, after updating, can view and delete the tasks that he has assigned to the
members.
 Figure No. 21: Task List

After the task has been completed and submitted, the Project Manager receives a notification
with which he can supervise on who has completed his work on time.

Figure No. 22: Notification from student

With the completion of task, the progress bar is also updated dynamically which the Project
Manager can view at any time to see the progress of his members.
 Figure No. 23: View Progress

The progress bar for individual tasks can also be viewed by the Project Manager/

Figure No. 24: View Individual Progress

After the project is completed, the button for Create Report is enabled which allows the Project
Manager to get the report and send to the Lecturer for evaluation.
 Figure no. 25: Create and View Report

Other than this, the student can also send feedback request to the Project Manager for
confirmation or review regarding his tasks.
 Figure No. 26: Receiving Feedback Request from Student

Project manager can also ask the Lecturer for giving feedback by sending him a feedback
request.
 Figure no. 27: Feedback Request to Lecturer

The Project Manager can also view the member’s list and get any information that he wants.
 Figure no. 28: View Members’ List

Students:
Even though the Project Manager is also a student, his responsibilities are more than the group
members. Students each have their own dashboard as well, from where they can do the tasks
assigned to them and view their grades as well.
Some of the main tasks of Students are given below.
1. Receive tasks from Project Manager
2. Edit and View on the tasks
3. Submit the tasks
4. View grades
5. Request for feedback from Project Manager and Lecturer
The details of these tasks are given below.
First of all, the Student will sign up and login the portal from the email invitation that was sent to
him by the Lecturer.
 Figure No. 29: Sign up and Login

From there, Student will be directed towards the dashboard where he will have any notifications
regarding the task that he has been assigned for the assignment by the Project Manager.

Figure No. 30: Student Dashboard

From the task list, the student can view his task and then start working on it.
 Figure No. 31: View and Working on Tasks

After completing the tasks, the edit is updated and the notification is popped up as well.
 Figure No. 32: Completing Tasks

Other than this, the student can also ask for feedback from the Lecturer.
 Figure no. 33: Sending Feedback Request.

A notification pops up that tells the Student that the Lecturer has given the feedback. The student
can click on the notification and view the feedback that the Lecturer has given.
 Figure No. 34: Receiving Feedback Notification and Feedback

Students can also view the grades that have been assigned to them by the Lecturer.

Figure No. 35: View Grades

This will be the last operation that the student will perform. After that, the procedure will again
start with the Lecturer assigning tasks and creating teams and will go on. The sprints have been
created while carefully considering all the operations being performed by the Lecturer, the
Student and the Project Manager.
 12. Results and Findings of the Product Testing
After the development of the project has been completed, the last but not the least step is the
Testing of the product. It is an essential step that ensures that the application is working the way
it is supposed to and no aspect has any bugs or errors. Many developers ignore this aspect of the
project and face overflowing complaints after giving the project over to the client.
There are several aspects of the project that need to be tested before handing it over the client.
They make sure that each and every step of the project is covered and nothing is missed.
Following are some of the points that need to checked properly.
1. Objective of testing
2. Approach of the application
3. Process of development of the application
4. Scope of the project
5. Tools for testing the project.
The details of the all the testing aspects are given in detail below. With the help of these tests, the
testers determine the quality of the application and its range of functionalities.
12.1 Objective of Testing
The main objective of the testing should be clear before we start the process. The main objective
for creating this application is to ensure that the working conditions and environment for the
project are in accordance with the clients’ demands and requirements. Testing the application
also confirms that the application is of high quality as promised to the users and all the functional
and non-functional requirements of the application are completely met. The main job of the
tester is to weed out any small-scale errors or bugs that may cause long term or drastic effects on
the project in the future.
The mindset with which the tester should conduct the tests is to obtain the following results.
1. A user-friendly and interactive website for the Students and Lectures.
2. Summary of all the tests conducted on the application that covers the functional and non-
functional requirements of the application which might be needed for future references.
3. Ensuring that all the objectives and requirements of the application are completed
according to the client’s wishes.

12.2 Testing Approach

The most effective way of testing any application is finding the best and the most related testing
approach for it. In this project, the testing approach that was selected for checking the
functionalities of the application is the Proactive Approach. The main reason for selecting the
approach was because this approach allows the testers to start the testing procedure even before
the development of the application is completed. Because of this, the errors are found early on
and can be easily fixed during the development phase. This saves a lot of time and is also energy
conservative for the developers. the creation of the application has limited time and in this
specific time, testers can do a lot more while following this approach. They can find the bugs
early on during the design phase and find faults while keeping the client’s and application’s
requirements in focus.
12.3 Testing Process
After selecting the testing approach, the procedure for the testing needs to be selected. For this,
all the aspects of the application need to be considered. After careful consideration the process
selected for the testing is Manual Testing [ CITATION Naz18 \l 1033 ]. In manual testing, the testers
need to manually check all the aspects of the application without using any automatic tools to
find any errors or bugs that may show up.
There are six main steps that are involved with the manual testing process. They are listed below.
1. Requirement analysis
2. Test plan creation
3. Test case creation
4. Test case execution
5. Defect Logging
6. Defect fix and re-verification

Even though the process in itself is time consuming, all the steps are done one by one to ensure
that effective testing procedure is initiated. All the steps are explained in detail below.
1. Requirement Analysis: All the documents in which the requirements were specified
such as storyboards, road maps, etc. are collected and analyzed. The main features and
specification sin each of the document is recorded and classified according to the priority.
Then the testing is done according to priority defined.
 2. Test Plan Creation: while keeping the requirements in mind, the test plan is created
which covers the systemic way of creating the plan and the schedule of all the activities
that will be performed.
3. Test Case Creation: The specified criteria are kept in focus while creating the test cases.
The test cases are made according to the three sprints thar are listed below.
a. Sprint 1 (test cases for the Lecturers).
b. Sprint 2 (test cases for the Project Manager)
c. Sprint 3 (test cases for the Student)
to develop the test cases, the considered tasks include recording the design preconditions,
post conditions, decision priority, selecting templates for test cases and expected result
from the testing process.
4. Test Case Execution: The developer needs to provide the tester with all the
functionalities for him to start the process. The testers follow the procedure set in the test
cases and perform the mentioned operations to confirm their smooth functionality. The
tester compares the received outcome of the test with the expected results and records it.
In the end, a report is created that defines the complete, incomplete and defective status
of the modules.
5. Defect Logging: in this step, the tester informs the developers of all the missing and
defective requirements of the application. The manager and team members then discuss
the plan of action to fulfill the requirements. The report is also shared with the rest of the
team so that they can fix the aspects of the applications that they are in charge of.
6. Defect Fix and Re-Verification: The developers fix all the errors and bugs as mentioned
by the testers and then send them the application again for re-verification. The testers
check the functionalities and update the report which is shared with the team again.
12.4 Test Cases

Test case: US01

User story: US01

Pre-conditions
As a lecturer, I want to log in my dashboard.
Test Steps Expected Result Actual Result Status (Pass/Fail)
Lecturer can log in the dashboard The website Lecturer can log in Pass
with his credentials. allows the and check his
Lecturer to log in. dashboard.

Test case: US02

User story: US0

Pre-conditions
As a lecturer, I want to create projects for the students.
Test Steps Expected Result Actual Result Status (Pass/Fail)
Lecturer can navigate the menu A new project is Lecturer has created Pass
bar and create a new project and created and the the project and set
set deadlines for the students. deadline is set. the deadline.

Test case: US03

User story: US03

Pre-conditions
As a lecturer, I want to select student and assign a project manager in each team.
Test Steps Expected Result Actual Result Status (Pass/Fail)
The lecturer selects the names of A team is created The team along with Pass
students he wants to be in a team and the project the project manager
and assigns one of them the task manager is was finalized.
of being a project manager. assigned.

Test case: US04

User story: US04

Pre-conditions
As a lecturer, I want to send invitation link to the students.
Test Steps Expected Result Actual Result Status (Pass/Fail)
After setting the team members, The invitation The email invitation Pass
the lecturer clicks on the button to link is sent was sent
send the invitation link. through email. successfully.
Test case: US05
User story: US05

Pre-conditions
As a student, I want to receive the email invitation from the lecturer.
Test Steps Expected Result Actual Result Status (Pass/Fail)
Students can view the inbox of An email Students received Pass
their email accounts for the invitation is the email invitation
invitation. received to the on their accounts.
students.

Test case: US06

User story: US06

Pre-conditions
As a student, I want to sign up and log in the portal using the email invitation.
Test Steps Expected Result Actual Result Status (Pass/Fail)
Click on the email invitation link Students log in Students were able Pass
sent by the lecturer and direct to and sign up in the to sign up and log in
the portal. From there sign up and portal. the portal using the
then log in. invitation.

Test case: US07

User story: US07

Pre-conditions
As a project manager, I want to create assignment from the project received by the manager.
Test Steps Expected Result Actual Result Status (Pass/Fail)
Project manager will create a new The assignment is The assignment, Pass
assignment and set the deadline uploaded on the along with the
for the other members. portal and all the deadline was set and
members can see the members could
it. view it.
Test case: US08
User story: US08

Pre-conditions
As a project manager, I want to create tasks and distribute them among the team members.
Test Steps Expected Result Actual Result Status (Pass/Fail)
Create the tasks and assign them All the members the project manager Pass
to the members. should receive the created the tasks
tasks that they successfully and the
have to do. members received it.

Test case: US09

User story: US09

Pre-conditions
As a student, I want to receive tasks from the project manager.
Test Steps Expected Result Actual Result Status (Pass/Fail)
Student will view his dashboard Students should Students got the Pass
for the task notification sent by receive the notification for their
the project manager. created tasks. assigned tasks.

Test case: US10

User story: US10

Pre-conditions
As a student, I want to delete or edit my tasks and then submit them after completion.
Test Steps Expected Result Actual Result Status (Pass/Fail)
Students can work on their tasks Students should Students could edit, Pass
and save them whenever they work on their update and delete
want. After completing the tasks, tasks and then their tasks and after
they can submit it. submit them. completing them,
could submit.
Test case: US011
User story: US011

Pre-conditions
As a project manager, I want to check the work progress and download individual report.
Test Steps Expected Result Actual Result Status (Pass/Fail)
After all the members have Project manager The project manager Pass
completed their work, the project can view the viewed his
manager can download the individual members’ progress
individual report. progress and after and when they were
completion can done, downloaded
download the the final report.
report.

Test case: US12

User story: US12

Pre-conditions
As a student, I want to request the lecturer for feedback.
Test Steps Expected Result Actual Result Status (Pass/Fail)
Students can send the feedback Students should Students were able Pass
request to the lecturer after be able to send to successfully send
completing their tasks. feedback request the request for
to the lecturer. feedback to the
lecturer.

Test case: US13

User story: US13

Pre-conditions
As a lecturer, I want to receive feedback requests and give feedback.
Test Steps Expected Result Actual Result Status (Pass/Fail)
Lecturer will receive feedback Lecturer can Lecturer received the Pass
requests and will know through receive feedback feedback request
notifications. After clicking on it, requests and notification and from
he will be redirected to give the given feedback to there, he was able to
feedback to the specific student. the students. give feedback.

Test case: US14

User story: US14

Pre-conditions
As a student, I want to view feedback from the lecturer.
Test Steps Expected Result Actual Result Status (Pass/Fail)
Student will receive feedback Students should Student received Pass
from the lecturer which he can be able to view feedback from
view under the specific task. the feedback. lecturer and was able
to view it.

Test case: US15

User story: US15

Pre-conditions
As a project manager, I want to submit the completed project and report to the lecturer.
Test Steps Expected Result Actual Result Status (Pass/Fail)
After completion, the project Project manager Project manager was Pass
manager sent the project and should submit able to send the
individual report to the lecturer. project and report. completed project
and individual report
to the lecturer.

Test case: US16

User story: US16

Pre-conditions
As a lecturer, I want to receive the report and project and assign grades.
Test Steps Expected Result Actual Result Status (Pass/Fail)
The lecturer will receive the The lecturer The lecturer received Pass
project and the report and after should be able to the project and
evaluating it, he will give grades. receive project report from the
and assign grades, project manager and
awarded them
individual grades.

Test case: US17

User story: US17

Pre-conditions
As a student, I want to view the grades that have been given to me by the lecturer.
Test Steps Expected Result Actual Result Status (Pass/Fail)
Students can go to the dashboard Student should be Student could see his Pass
and view their grades given by the able to view grades from the
lecturer. completed project dashboard.
and assigned
grades.

12.5 Tools and Environment for Testing

Testers need an appropriate environment and tools that will clearly access the application and
make sure that all the functionalities are fully operational. Depending upon the results, the tests
are classified as positive and negative. The storage of the application, response speed, location
supporting hardware and software, internet access and smooth transition are all tested and
evaluated.
This section explores the criteria that is required for testing. An example would be a standard
setup with a friendly environment where the user can access all the features with ease. The other
criteria are given below.
1. Testing Environment: the testing environment includes the standard hardware and
software used for running applications. the application is executed while using the server
software.
2. Testing Tool: The testing was set to be done in the most realistic situation possible. That
is why it was run on the developer’s browser for the best results. The application was run
on localhost so that other stakeholders could also access and use the website on their
own. After testing, they all gave their valuable input for the improvements that the
developers can make with the application.
 3. Testing Data: the test data is basically dummy data that was used by the testers while
surfing through the application. The tests were run based on test cases that have been
discussed in the previous section.
4. Web Browsers: after the completion of all the sprints and functional modules, the testing
is done on web browsers such as Chrome, Safari, Opera, Firefox, etc.
5. Operating System: the operating system for the developed application is the Windows
operating system. All the testing and actual running of the application is done through
this OS.
12.6 Testing Scope
analyzing the entire scope of the project is very essential. That is why the tester needs to make
sure that all the necessary features and functionalities are tested properly. The scope analysis is
also very necessary for the testers. The entire scope consists of the functional and non-functional
requirements that are evaluated by the team

Functional Requirements
The functional requirements are the necessary requirements in any project. to ensure smooth
testing, the tester has divided the testing phase into three separate sprints. This ensures effective
testing.
Sprint 1 Sprint 2 Sprint 3
Lecturer was able to create Project manager could Lecturer could receive
teams and set project receive projects from lecturer. feedback requests and give
manager. feedback.
Data from lecturer’s Project manager can create Lecturer could receive
dashboard was saved in the assignments and tasks and assignment and assign grades.
database. distribute them among
members.
Lecturer could send email Project manager could Student could download
invitation. update, delete and edit tasks. reports.
Lecturer could set deadlines. Students can receive email
invitation from the lecturer
and sign up in the dashboard.
Students can view tasks.
Students can update, delete
and edit tasks.
Students can submit the
completed tasks.
Project manager can check
the progress of his members.

Non-functional Requirements
The non-functional requirements of the application are given below.
 Requirements Criteria
Compatibility Compatible with laptops, mobile phones and tablets
Network Connection Connected with applicable internet
Easy Navigation Smooth navigation among tabs, options and pages
User-friendly Interface Simple and interactive interface with ease of use guaranteed
for all users.

12.7 Procured Results

For an effective testing experience, the application was tested by 20 different testers. At first, out
of 16 test cases, they showed complete satisfaction with 14 test cases while pointing out some
errors in 2 test cases. However, the issues were minor and were quickly fixed with no lasting
effects.
Similarly, the testers were made to check the Lecturer, Student and Project Manager’s
dashboards separately. No major issues were found and the modules were all working according
to functionalities and requirements of the client. The minor issues and errors were fixed during
development.
All the 20 testers were also made to test the application at once so that the load on the application
could be checked. It was found that there was no noticeable difference in the operationability of
the system as well.

13. Summary, Limitations and Areas of Improvement

There are many applications of products, the details of which are explained in the report. When
the users successfully log in and enter the portal, they are allowed to have access to the following
applications.
Applications for Lecturer:
1. Create teams and assign project managers.
2. Create project topics and assign them to students.
3. Set deadlines and send email invitation.
4. Receive feedback request and give feedback.
5. Receive student’s completed project and report.
6. View projects and assign grades.
Applications for Project Manager:
1. Receive email invitation from lecturer.
2. Sign up and log in the portal.
3. Receive project from lecturer.
4. Create assignment and set deadlines.
5. Create tasks for the members of the group.
6. Edit and delete the tasks that have been created.
7. View progress of each member.
 8. Receive submitted tasks from members.
9. Receive feedback request and give feedback to members.
10. Send feedback request to lecturer.
11. View the information of the team members.
12. Download individual report and submit it alongside the report to the lecturer.
Applications of Students:
1. Receive email invitation form lecturer.
2. Sign up and log in the portal.
3. Receive assignment and tasks from the project manager.
4. Edit, update and delete tasks.
5. Submit tasks.
6. Request feedback from project manager and lecturer.
7. View feedback given from project manager and lecturer.
8. View grades assigned by the lecturer.
13.1 Limitations of Application
Like every application that has been created in the world, this application has some limitations as
well. One of them is that there is no process introduced that would train the users on how to use
the application. A user manual is given that just gives instructions and no practical
demonstration. For this, it is the responsibility of the team members to ensure that the users are
getting proper training and online materials.
Also, there is no community available that will address that issues or queries that the users face.
The process of deployment for this application is not addressed as well. The marked assignments
are not uploaded as well. The students can only see their grades and not their mistakes. A student
cannot directly contact the lecturer and has to go through the project manager for everything.
Some of the other limitations of the application are given below.
1. An active internet connection is needed at all times even during typing the assignment.
2. The database MySQL needs to be connected with all the devices within a single network
at all times.
3. Any issue with the progress bar will stop the whole process and there is no replacement
way for this.
4. There is a chance that the application faces shutdown because of heavy load or failed
server.
13.2 Areas of Improvement
As there are limitations in an application, there are ways of improving it as well. To ensure that
all the users can swiftly learn the application, the development team can create a Help section in
the application. Users can go to that section to figure out how a particular module works. They
can also ask questions and have a help team that will guide them through the issues that they
face.
The application can also be deployed for public use. This will allow the application to expand
and help several users around. Many different improvements to enhance the system can also be
adopted.
Some of the features can also be enhanced so that they can work even without an active internet
connection at all times. The database can also be distributed so that the application can work
remotely at all times.
Changes and improvements in the design can also be added. The application is in light mode
right now, it can be enhanced to dark mode so that students can work for longer ties without
hurting their eyesight. The design can also be enhanced in such a way that if you hover over a
particular module, a notification pop-up shows all the related instructions.

References
Bridge, P., & Appleyard, R. (2008). A comparison of electronic and paper-based assignment submission
and feedback. British Journal of Educational Technology, 39(4), 644-650. Retrieved from BERA:
https://bera-journals.onlinelibrary.wiley.com/doi/10.1111/j.1467-8535.2007.00753.x

Chan, C. (2010). Assessing Group Work. Retrieved from Assessment Resources@HKU:

https://ar.cetl.hku.hk/group.htm

Fernando, J. (2021, August 19). Investopedia. Retrieved from Stakeholder:

https://www.investopedia.com/terms/s/stakeholder.asp
Geri, N., & Naor-Eliza, O. (2008). Beyond Adoption: Barriers to an Online Assignment Submission System
Continued Use. Interdisciplinary Journal of E-Learning and Learning Objects, 4(1), 225-241.
Retrieved from LearnTech U: https://www.learntechlib.org/p/44857/

Hamilton, T. (2021, September 24). Agile Methodology: What is Agile Software Development Model &
Process in Testing? Retrieved from Guru99: https://www.guru99.com/agile-scrum-extreme-
testing.html

Hamilton, T. (2021, October 8). Integration Testing: What is, Types, Top Down & Bottom Up Example.
Retrieved from Guru99: https://www.guru99.com/integration-testing.html

Hamilton, T. (2021, October 8). Unit Testing Tutorial: What is, Types, Tools & Test EXAMPLE. Retrieved
from Guru 99: https://www.guru99.com/unit-testing-guide.html

Illieva, S., Ivanov, P., & Stefanova, E. (2004). Analyses of an Agile Methodolgy Implementation.
Proceedings. 30th Euromicro Conference, 2004. (pp. 326-333). Rennes, France: IEEE.

Josep, G. (2021, September 15). 5 Reasons Why Online Learning is the Future of Education. Retrieved
from educations.com: https://www.educations.com/articles-and-advice/5-reasons-online-
learning-is-future-of-education-17146

Lutkevich, B. (2021, September). Project planning: What is it and 5 steps to create a plan. Retrieved from
TechTarget: https://searchcio.techtarget.com/definition/project-planning

Maio, A. (2020, March 5). What is a Storyboard? The Fundamentals to Get You Started. Retrieved from
studiobinder: https://www.studiobinder.com/blog/what-is-a-storyboard/

Martin, M. (2021, October 7). What is Backend Developer? Skills Need for Web Development. Retrieved
from Guru99: https://www.guru99.com/what-is-backend-developer.html

Naor-Elaiza, O., & Geri, N. (2009). Not as Easy as E-Mail: Tutors' Perspective of an Online Assignment
Submission System. Interdisciplinary Journal of E-Learning and Learning Objects, 5(1), 345-358.
Retrieved from LearnTech U: https://www.learntechlib.org/p/44840/

Naznin, T. (2018, January 1). Manual testing process. Retrieved from Oceanize Geeks:
https://medium.com/oceanize-geeks/manual-testing-process-340173d40141

Pedamkar, P. (n.d.). SDLC vs Agile. Retrieved from Educba: https://www.educba.com/sdlc-vs-agile/

Stewart, L. (2021, July 22). Front End Development vs Back End Development: Where to Start? Retrieved
from Course Report: https://www.coursereport.com/blog/front-end-development-vs-back-end-
development-where-to-start

Zafar, R. (2021, March 20). What is software testing? What are the different types of testing? Retrieved
from Code Project: https://www.codeproject.com/Tips/351122/What-is-software-testing-What-
are-the-different-ty