User dashboard

Chapter V............................................................................................................................................................................... 26

5.1. User Interface

5.1.8. User dashboard

This is the user dashboard. From this page user will able to perform their activity. By clicking

‘Add problem’ button user can added new problem and by clicking view problem list a user can see those problem that submitted by him.

Figure 20: User Dashboard

5.1.9. Add Problem

User will be able to add any problem by providing the necessary information.

Figure 21: Add Problem

5.1.10. User view problem

User can see the problem list that submitted by him. If the problem is solved then the admin remove from the list after that user can see the empty list.

Figure 22: User view problem list

Chapter VI

Development Tools & Technologies

6.1. User Interface Technologies

• XML

6.2. Implementation Technologies

• JAVA

• Firebase realtime database

6.3. Platform & Environment

6.3.1. Hardware

• Processor: Intel Core i3.

• RAM: 4GB.

• Hard drive: 1TB.

• Windows 10

6.3.2. Tools

• IDE/Editor: Android studio.

6.3.3. Version Control

• Github (a web based version control for software project)

https://github.com/iammizanur/Classroom-Problem-And-Solution

Chapter VII System Testing 7.1. Introduction

System testing is done to identify errors. The main objective of system testing are to ensure that the actual process done by the application is correct ad meets the requirements. By doing system testing the errors can be detected efficiently.

7.2. Test Plan Strategy

Test plan strategies are really important. The significance of the test plan strategies is to show how the application will be tested and also gives the steps to be followed during the test plans.

At first the data is identified and then tested thoroughly.

7.3. Test Case

Test cases are set of conditions in which a tester will determine whether an application under

the requirements works properly or not. The process of developing test cases can identify

problems in the requirements or design of an application.

7.3.1. Test case of Admin login

Test case #01 Test case name:Testing the admin

login phase System: Classroom Problem and Solution Subsystem: Login Designed By: Mizanur Rahman Design date:02-08-2019 Executed By: Mizanur Rahman Executed date:02-08-2019

Short Description: This field will test the login functionality of the application.

Precondition: Installing the application

Steps Action Action Result Expected System

Response Pass/Fail

01 Submit valid email

and valid password Get logged in. Logged in into the

system. Pass

02 Submit valid email

and invalid password Not logged in and error message.

Not logged in

and error message. Fail 03 Click login button

without any data Required

message Required message Fail

Table 27:Test case Admin login

7.3.2. Test case of User login

Test case #02 Test case name:Testing the user login

phase

System: Classroom Problem and Solution Subsystem: Login Designed By: Mizanur Rahman Design date:02-09-2019 Executed By: Mizanur Rahman Executed date:02-09-2019

Short Description: This field will test the login functionality of the application.

Precondition: Installing the application

Steps Action Action Result Expected System

Response Pass/Fail

01 Submit valid email

and valid password Get logged in. Logged in into the

system. Pass

02 Submit valid email

and invalid password Not logged in and error message.

Not logged in

and error message. Fail 03 Click login button

without any data Required

message Required message Fail

Table 28: Test case User login

7.3.3. Test case of User sign up

Test case #02 Test case name:Testing the user sign

up phase

System: Classroom Problem and Solution Subsystem: Login

Designed By: Mizanur Rahman Design date:02-010-2019 Executed By: Mizanur Rahman Executed date:02-10-2019

Short Description: This field will test the login functionality of the application.

Precondition: Installing the application

Steps Action Action Result Expected System

Response Pass/Fail

01 Click Register

without any data Required

message Required message Fail 02 Click Register after

filling some data Not signed up and required message

Not signed up and required message

Fail

03 Click Register with valid data and password less than 6 characters.

Signed up in and error message.

No Required

message Fail

04 Click Register with valid data and password not matching with confirm password.

Not Signed up in and error message.

Not signed up in

and error message Fail

05 Click Register with valid data and password

Signed up and redirected to main landing page

Signed up and redirected to main landing page.

Pass

Table 29:Test case User sign up

Chapter VIII Project Summary

8.1. GitHub Link

https://github.com/iammizanur/Classroom-Problem-And-Solution

8.2. Limitations

• The application is only for software engineering department of DIU.

• Required internet connection for user smart phone.

8.3. Obstacle & Achievements

Obstacle:

• Learning new technology and environment

• Limited time Achievements

• Learnt new technologies

• Successfully build a full project

8.4. Conclusion

The project was developed to help the software engineering department to manage the classroom related problem and solution. The objective was to help the teachers and students to use classroom problem free and.

8.5. Future Work

Key of Terms

A C

Abstract Conclusion

Acknowledgement Class Diagram

Approval Context Diagram

Activity Diagram D

Analysis Definition

E Data flow diagram

Entity Relationship Diagram Database

I S

Implementation Software Requirement Specification

T System Design

Testing System description

Test case System Overview

Tools System Specification

Technical writing F

N Functional requirements

Non Functional requirements Feasibility study

U

Use case Diagram