DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING

Project Report

Of

Question Bank

(Online CQ and MCQ Web Application)

Supervised By
Mrs. Nazmin Akter

Senior Lecturer

Department of CSE

Metropolitan University, Sylhet

Submitted By

Name: Mahbub Rahman Name: Mohammad. Ashraf Hossan Shovo

Batch: CSE 32nd Batch: CSE 32nd

ID: 141-115-018 ID: 141-115-056

 Acknowledgement

First of all we want to thanks to the almighty Allah for giving us the opportunity for
completing and submitting the final year project on time. We would not possible to submit
the final year project without the blessing of Almighty Allah.

We would like to thanks the Supervisor of the project Mrs. Nazmin Akter, Senior Lecturer,
Metropolitan University, Sylhet for giving us guidance and advices for completing our
project. Without her help and supervision this project may not be fulfilled. Her involvement
to this project can only be acknowledgement but never be rewarded.

Also we would like to thanks Head of the Department Mr. Fuad Ahmed and all of the faculty
members of Department of Computer Science and Engineering, Metropolitan University for
making us skilled and giving the knowledge of Computer Science and Engineering. Your
contribution can only be acknowledgement but never be rewarded.
 Certificate
The undersigned here by certify that they have read and recommend to the controller of
examination for acceptance of the project entitled- "QuestionBank" By Mahbub Rahman &
Mohammad. Ashraf Hossan Shovo. It has been defended in front of the following members
of the project committee on 2018. The members have accepted this project as the partial
fulfillment of the requirement for the degree of Bachelor of Science in Computer Science
and Engineering.

Nazmin Akter Shakhawat Hossain Saimon

Project Supervisor Member of the Committee

Senior Lecturer Lecturer

Department of CSE Department of CSE

Metropolitan University, Sylhet Metropolitan University, Sylhet

Akhlak Uz Zaman Ashik Jagoth Jyoti Dey

Member of the Committee Member of the Committee

Lecturer Lecturer

Department of CSE Department of CSE

Metropolitan University, Sylhet Metropolitan University, Sylhet

Candidate’s declaration:
It is hereby declared that this project reported here has been performed by us
and this project or any part of it has not been submitted elsewhere for the award of
any degree or diploma, does not contain any unlawful statements.

Mahbub Rahman Mohammad. Ashraf Hossan Shovo

Batch: 32nd Batch: 32nd

ID: 141-115-018 ID: 141-115-056

Department Of CSE Department of CSE

Metropolitan University, Sylhet Metropolitan University, Sylhet

Abstract:
Having a computer system now-a-days is very important. Education Information and
services in Bangladesh are a new concept. Gradually it is getting recognized. But due
to lack of adequate information, the people still could not reach this service well. In
this situation internet based education service can play an important role for the
people. Internet is widening its gateway to every day to day life increasingly. The
main purpose of our project is to create a web app through which any student can
easily acquire knowledge and verify his educational skills. A student can easily
prepare for any of his exams. This app will be able to collect the questions of
previous exams from various institutions. There will also be a community for
students where any student can discuss their different questions or opinions.

This system will also ensures the preservation of personal records and ensure the
accessibility only by the authorized personnel. To have a good and efficient records
web application should be able to incorporate specific aspects of the systems
mentioned above in order to provide and efficient means of record storage and
management.
 Table of Content

Chapter 1: Introduction

1. Introduction --------------------------------------------------------------------------------------------------------- 2

1.1 Purpose ------------------------------------------------------------------------------------------------------------- 2

1.2 Scope ---------------------------------------------------------------------------------------------------------------- 2

1.3 Justification -------------------------------------------------------------------------------------------------------- 3

1.4 Limitation of the System ---------------------------------------------------------------------------------------- 3

Chapter 2: Feasibility Study

2. Feasibility Study ---------------------------------------------------------------------------------------------------- 5

2.1 Technical Feasibility --------------------------------------------------------------------------------------------- 5

2.2 Operational Feasibility ------------------------------------------------------------------------------------------ 6

2.3 Economic Feasibility --------------------------------------------------------------------------------------------- 6

2.4 Schedule Feasibility ---------------------------------------------------------------------------------------------- 7

Chapter 3: Database and Tables

3. Database and Tables ---------------------------------------------------------------------------------------------- 9

3.1 Normalization Process ------------------------------------------------------------------------------------------ 9

3.1.1 First Normal Form ---------------------------------------------------------------------------------------- 9

3.1.2 Second Normal Form ----------------------------------------------------------------------------------- 10

3.1.3 Third Normal Form ------------------------------------------------------------------------------------ 10

3.1.4 Boyce-Codd Normal Form ---------------------------------------------------------------------------- 11

3.1.5 Fourth Normal Form ----------------------------------------------------------------------------------- 11

 3.2 Tables -------------------------------------------------------------------------------------------------------------- 12

3.2.1 User Table ------------------------------------------------------------------------------------------------ 12

3.2.2 Admin Table ---------------------------------------------------------------------------------------------- 12

3.2.3 CreativeQuestionSet Table --------------------------------------------------------------------------- 13

3.2.4 McqQuestionSet Table -------------------------------------------------------------------------------- 13

3.2.5 BoardQuestion Table ----------------------------------------------------------------------------------- 14

3.2.6 ForumQuestion Table ---------------------------------------------------------------------------------- 14

3.2.7 ForumReply Table --------------------------------------------------------------------------------------- 14

3.2.8 Blog Table ------------------------------------------------------------------------------------------------- 15

3.2.9 Exam Table ------------------------------------------------------------------------------------------------ 15

3.2.10 Result Table --------------------------------------------------------------------------------------------- 15

Chapter 4: Software Requirement Specification

4. Software Requirement Specification ------------------------------------------------------------------------ 17

4.1 Use Case Diagram ---------------------------------------------------------------------------------------------- 18

4.1.1 Use Case Diagram of the System-------------------------------------------------------------------- 19

4.1.2 Use Case Diagram of the Super Admin ----------------------------------------------------------- 20

4.1.3 Use Case Diagram of the Registered User ------------------------------------------------------- 21

4.2 Activity Diagram ------------------------------------------------------------------------------------------------ 22

4.2.1 Activity Diagram of Super Admin ------------------------------------------------------------------- 22

4.2.2 Activity Diagram of Admin --------------------------------------------------------------------------- 23

4.2.3 Activity Diagram of Registered User -------------------------------------------------------------- 23

 4.2.4 Activity Diagram of Guest User ------------------------------------------------------------------ 24

4.3 Context Diagram ----------------------------------------------------------------------------------------------- 25

4.4 Sequence Diagram --------------------------------------------------------------------------------------------- 26

4.5.1 User’s Login Sequence Diagram -------------------------------------------------------------------- 26

4.5.2 Registered User’s Sequence Diagram ------------------------------------------------------------- 27

4.5 Class Diagram --------------------------------------------------------------------------------------------------- 28

4.6 Deployment Diagram ----------------------------------------------------------------------------------------- 29

4.7 Entity Relationship Diagram --------------------------------------------------------------------------------- 30

4.8 User Requirements -------------------------------------------------------------------------------------------- 31

4.8.1 Functional Requirements ---------------------------------------------------------------------------- 31

4.8.2 Nonfunctional Requirements ----------------------------------------------------------------------- 31

4.9 System Requirements ---------------------------------------------------------------------------------------- 32

4.9.1 Software Requirements -------------------------------------------------------------------------------32

4.9.2 Hardware Requirements ----------------------------------------------------------------------------- 32

Chapter 5: System Design

5. System Design --------------------------------------------------------------------------------------------------- 34

5.1 Guest User’s Activity ----------------------------------------------------------------------------------------- 34

5.2 Registered User’s Activity ---------------------------------------------------------------------------------- 34

5.3 Admin’s Activity ----------------------------------------------------------------------------------------------- 35

5.4 Super Admin’s Activity -------------------------------------------------------------------------------------- 35

Chapter 6: Testing

6. Testing ------------------------------------------------------------------------------------------------------------ 37

6.1 Requirement Traceability ---------------------------------------------------------------------------------- 37

Chapter 7: Implementation

7. Implementation ------------------------------------------------------------------------------------------------- 40

7.1 Education -------------------------------------------------------------------------------------------------------- 40

7.2 Training ----------------------------------------------------------------------------------------------------------- 41

Chapter 8: Maintenance

8. Maintenance ----------------------------------------------------------------------------------------------------- 43

8.1 Types of Maintenance ---------------------------------------------------------------------------------------- 43

Chapter 9: Software Interface or User Interface

9.1 Software Interface --------------------------------------------------------------------------------------------- 46

9.2 User Interface Design Activities ---------------------------------------------------------------------------- 46

9.3 Main Interface -------------------------------------------------------------------------------------------------- 48

9.4 Registration ------------------------------------------------------------------------------------------------------ 49

9.5 Login --------------------------------------------------------------------------------------------------------------- 50

9.6 Question Set ----------------------------------------------------------------------------------------------------- 51

9.7 Examination ------------------------------------------------------------------------------------------------------ 52

9.8 Review Questions Answer ------------------------------------------------------------------------------------ 53

9.9 Review Performance ------------------------------------------------------------------------------------------- 54

9.4 Admin Panel ------------------------------------------------------------------------------------------------------ 55

Chapter 10: Conclusion

10. Conclusion -------------------------------------------------------------------------------------------------------- 57

10.1 References ----------------------------------------------------------------------------------------------------- 58

10.2 Abbreviations -------------------------------------------------------------------------------------------------- 59

CHAPTER-1

Introduction

Page | 1
1. Introduction

This section gives a scope description and overview of everything included in this Report.
Also the purpose for this document is provided.

1.1 Purpose
Now-a-day’s internet becomes a popular medium to mass people. Especially students
are becoming more dependent on Internet. They are searching for new facilities from
internet. Education is a basic human need. As Bangladesh is getting digitalized day by
day, so we have decided to develop a creative web application on our education sector
for BCS and other board exam candidates including secondary school students, who can
make their MCQ along with Creative Question preparation and can get important
advices, proper guidelines & instructions through this website. In this application
student can verify his educational skills by participating their required exam. However,
this web app has also collection of previous exam question paper from various
Government & Non Government exam. There has also a community for students where
they can discuss their different questions or opinions.

1.2 Scope
Our project that we proposed is an online CQ and MCQ exam practicing website. It’s a
project for different types of public examinations like JSC, SSC, HSC, BCS & Admission
test. Where registered user can practice MCQ by selecting any subject, creates or
update own profile, can select exam categories, can attend in model test and contest,
user can ask for help regarding any issues in forum section, user can find any kind of
important information, notices, motivational speech etc. from blog section. A guest
user can view question set and also can download the question set, user can also access
discussion forum. Admin can view user details, insert a number of question with topics,
can set duration of exam, can delete and block users. On the other hand super admin
will maintenance full software system.

Page | 2
1.3 Justification

➢ To ensure the efficiency of the system by providing better services comparing to

previous technologies.
➢ To ensure the efficiency by giving access and visual confirmation.
➢ To reduce the time wasting by eliminating long queues.
➢ To ensure the easy maintenance for the Admin.

1.4 Limitation of The System

➢ The user of the system must be computer literate and familiar with web
application uses.
➢ Requires internet connection for using this project as it a web based
application.
➢ User need to appear physically in front of device for getting full access.
➢ Sufficient bandwidth and hosting space will be required for implementing the
system.

Page | 3
CHAPTER-2

Feasibility Study

Page | 4
2. Feasibility Study
Feasibility Study is the beginning investigation for any software development. Simply a
Feasibility Study is a sort focused study that will check whether the system can
contribute to overall objectives. It also justify whether the system can be developed
using current technology and schedule. Feasibility Study also checks the integration of
the system with other system that are already in place. It assesses the technical,
economic, schedule and operational merits of a project. From the perspective of
systems analyst feasibility analysis is a primary tool for recommending whether proceed
to the next phase or discontinue the project. In this chapter we will able to know the
feasibility of the proposed system.

2.1 Technical Feasibility

Technical Feasibility focused on present technical resources of the organization and

their applicability to the expected needs of the proposed system. Technical
Feasibility is an evaluation of the software and hardware and justify how it meets
the need of the proposed system. If the technical capacity of the proposed system is
sufficient to support the project requirements then the system will considered
technically feasible. Technical Feasibility aims to answer the following questions:

➢ Does the system fulfill the requirement of the hardware and the software?
➢ Are the current Technical resources sufficient for the new system?
➢ Is the project feasible within the limit of current technology?
➢ Does the technology exist?
➢ Is there enough man power like coder, tester and debugger?
➢ Is the system fulfilling practical criteria?
➢ Is it available within the resource constrains?
➢ Can the system be upgraded?
➢ Do we currently process the necessary technology?

Page | 5
 The answer of the above questions for the proposed system is yes. It fulfills all the
criteria of Technical Feasibility. So the proposed project is technically feasible.

2.2 Operational Feasibility

Operational Feasibility measures how well a proposed system solves the problems,
and takes advantage of the opportunities identified during scope definition and how
it satisfies the requirements identified in the requirements analysis phase of system
development. It also Justify how well the project will support the customer.

Operational Feasibility aims to answer the following questions:

➢ Is the project feasible to operate?

➢ Will the system affect the users in considerable way?
➢ Does the current mode of the operation provide adequate throughput and
response time?
➢ Does the current mode operation offers effective protection against accuracy
and security of system data?

The answer of the above questions for the proposed system is yes. It fulfills all the
criteria of Operational Feasibility. So the proposed project is operationally feasible.

2.3 Economic Feasibility

Economic Feasibility assesses the viability, cost and benefits of projects before
financial resources are allocated. Economic Feasibility also ensures the economic
benefits of the organization. Economic Feasibility involves benefits and evaluation
of effectiveness of the proposed system. Economic Feasibility aims to answer the
following questions:

➢ Is the system can be developed within the estimated cost?

➢ Is the system cost effective?
➢ Will the proposed system give economic benefits to the organization?

Page | 6
 The answer of the above question for the proposed system is yes. It fulfills all the
criteria of Economic Feasibility. So the proposed project is economically feasible.

2.4 Schedule Feasibility

Schedule Feasibility estimates how much time the system will take to complete. It
justify that if the project can be completed within time or not. Schedule Feasibility is
the most important term in Feasibility study. A project will not success if it fails
Schedule Feasibility. Schedule Feasibility aims to answer the following question:

➢ Can the project be completed within given time?

The answer of the above question for the proposed system is yes. It fulfills all
the criteria of Schedule Feasibility.

Finally from the above discussion it is clear that the proposed system is feasible for
proceeding into next phase as the proposed system fulfills all the criteria of
technical, operational, economic and schedule feasibility.

Page | 7
 CHAPTER-3

Database and Tables

Page | 8
3. Database and Tables
The database of the system is created by using MySQL. The database is designed by
applying the normalization processes and finally BCNF is also applied. After applying all
the process the database has divided into seven tables. By using foreign keys in the
tables joined in SQL queries for producing different data results.

3.1 Normalization Process

We use database so that we can store information in a systematic way. The

database are designed by following normalization process. Database Normalization
is the process of organizing the columns and tables of a relational database to
minimize data redundancy.

The proposed system is designed by following:

❖ First Normal Form

❖ Second Normal Form
❖ Third Normal Form
❖ Boyce-Codd Normal Form
❖ Fourth Normal Form

The example of Normalization is given below:

3.1.1 First Normal Form

An entity is in First Normal Form (1NF) when all tables are two dimensional
with no repeating groups. A row is in First Normal Form (1NF) if all underlying
domains contain atomic values only. 1NF eliminates repeating groups by
putting each into a separate table and connecting them with a one-to many
relationship. Make a separate table for each set of related attributes and
uniquely identify each record with a primary key.
❖ Eliminates duplicate column from same table.

Page | 9
 ❖ Create separate tables for each group of related data and identify
each row with a unique column or set of columns (the primary key).

3.1.2 Second Normal Form

An entity is in Second Normal Form (2NF) when it meets the requirements of
being in First Normal from and additionally:

❖ Does not have a primary key. Meaning that the primary key cannot be
subdivided into separate logical entities.
❖ All the non-key columns are functionally dependent on the entire
primary key.
❖ A row is in second normal form if and only if, it is in first normal form
and every non-key attributes is fully dependent on the key.
❖ 2NF eliminates functional dependencies on a partial key by putting
the fields in a separate table from those that are dependent on the
whole key. An example is resolving many relationships using an
intersecting entity.

3.1.3 Third Normal Form

An entity is in Third Normal Form (3NF) when it meets the requirements of
being Second Normal Form (2NF) and additionally:

❖ Functional dependencies on non-key fields are eliminated by putting

them in separate table. At this level, all non-key fields are dependent
on the primary key.
❖ A row is in Third Normal Form if and only if it is in Second Normal
Form and if attributes that do not contribute to a description of the
primary key are move into a separate table.

Page | 10
3.1.4 Boyce-Codd Normal Form
Boyce-Codd Normal Form (BCNF) is a further refinement of 3NF. A row is in
Boyce-Codd Normal Form if and only if every determinant is a candidate key.
Most entities in 3NF are already in BCNF.

BCNF covers very specific situations where 3NF misses inter-dependencies

between non-key attributes. Typically, any relation that is in 3NF is also in
BCNF. However, a 3NF relation won’t be in BCNF if:

❖ There are multiple candidate keys,

❖ The keys are composed of multiple attributes and
❖ There are common keys between the keys

3.1.5 Fourth Normal Form

An entity is in Fourth Normal Form (4NF) when it meets the requirements of
being in Third Normal Form (3NF) and additionally:

❖ Have no multiple sets of multi-valued dependencies. In other words,

4NF states that no entity can have more than single one-to-many
relationship within an entity if the one-to-many attributes are
independent of each other.
❖ Many relationships are resolved independently.

Page | 11
3.2 Tables
The database of the proposed system has many tables. We post here some of here
like:users, admins, creativequestionset, mcqquestionset, boardquestion,
forumquestion, forumreply, blog, exam and result.

3.2.1 Users Table

3.2.2 Admins Table

Page | 12
3.2.3 CreativeQuestsionSet Table

3.2.4 McqQuestionSet Table

Page | 13
3.2.5 BoardQuestion Table

3.2.6 ForumQuestion Table

3.2.7 ForumReply Table

Page | 14
3.2.8 Blog Table

3.2.9 Exam Table

3.2.10 Result Table

Page | 15
 CHAPTER-4

Software Requirement Specification

Page | 16
4. Software Requirement Specification

Software Requirement Specification (SRS) is a process under software requirement

engineering process. This is the next phase after feasibility study in software
requirement engineering process. It is a comprehensive description of the intended
purpose and environment for software under development. Software requirement
specification laying out functional and non-functional requirements, and may include a
set of use cases that describe interactions the users will have with the software. The
Software Requirement Specification (SRS) fully describes what the software will do and
how it will be expected to perform.

The whole Software Requirement Specification for this project is described in the
chapter with the help of different diagrams, functional and nonfunctional
requirements. The following diagrams are described for the Software Requirement
Specification. They are Use Case Diagram, Activity Diagram, Context- Diagram,
Dataflow Diagrams, Sequence Diagrams, Class diagram, Deployment diagram and
Entity Relationship Diagram.

Page | 17
4.1 Use Case Diagram

Use case diagram is the most known diagram type. Use case diagrams gives a graphic
overview of the actors involved in a system, different functions needed by those actors
and how these different functions are interacted. We can say in word a use case
diagram is a simplest representation of a user's interaction with the system that
shows the relationship between the user and the different use cases in which the user
is involved. Use case diagram include use cases, actors, include relationship, extended
relationship and system boundary. A use case represents a function or an action
within the system. Actor in a use case diagram is any entity that performs a role in
one given system. The use case diagram of the system is given below.

Page | 18
4.1.1 Use Case Diagram of the System

Page | 19
4.1.2 Use Case Diagram of the Super Admin

Page | 20
4.1.3 Use Case Diagram of Registered User

Page | 21
4.2 Activity Diagram

Activity diagram is a type of diagram that represents workflows in a graphical way. It

can be used to describe business workflow or the operational workflow of any
component in a system. The following activity diagram shows the activity of user
that how a user create and update profile, take participate in different test and able
to show their performances. The activity diagram is given below:

4.2.1 Activity Diagram of Super Admin:

Page | 22
4.2.2 Activity Diagram of Admin:

4.2.3 Activity Diagram of Registered User:

Page | 23
4.2.4 Activity Diagram of Guest User:

The above activity diagram shows the activity of registered and unregistered user in
case in participating in practice, contest and model test. In the diagram user forward
to different from start. They need to satisfy condition if they have to forwarding next
activity. When they reach the end then they reach at have finished traversing.

Page | 24
4.3 Context Diagram

Context Diagram or System Context diagram is type of diagram that represent a

brief structure which depicts the environment in which a software system exist and
helps in communicating about what lies outside the system boundary. The following
context diagram of the system simply represents the system boundary and the
interaction of different level of users with the system. The Context diagram is given
below:

The context diagram of the proposed system shows the different user source
relationship with the software system. Direction towards the system shows
user command input to the system and Direction towards the user shows the
output. Thus the system represented in the diagram.

Page | 25
4.4 Sequence Diagram

The Sequence Diagram is a type of diagram that shows how object interact with
each other and the order those interactions occur. Sequence diagram also shows
the interactions for a particular scenario. The processes are represented vertically
and interactions are show as arrows. The Sequences Diagrams will show the guest
user and registered user processes and interactions.

4.4.1 User’s Login Sequence Diagram

Here the Sequence Diagram represents user’s login step by step process and
interactions in the system. User’s Login sequence diagram given below:

Page | 26
4.4.2 Registered User’s Sequence Diagram

Here the Sequence Diagram represents registered user’s step by step processes
and interactions in the system. Registered user’s processes and interaction are
given below:

Page | 27
4.5 Class Diagram
Class diagram is a type of diagram that shows the main building block of any object
oriented solution. It shows the classes in a system, attributes and operations of
each class and the relationship between each class. The class diagram of the system
is given below:

Page | 28
4.6 Deployment Diagram

Deployment Diagram is a type of diagram that shows the software will able to
interact with which type of devices and how. The Deployment Diagram for the
system shows its supported devices like pc, tab, mobile etc. The devices can be
interacting with the system with the help of internet.

Page | 29
4.7 Entity Relationship Diagram

Entity Relationship Diagram is a type of diagram that shows a system database

tables and its component relationship. The Entity Relationship Diagram has two
main categories of tables namely master and operational tables.
The Entity Relationship Diagram of the system is given below:

Page | 30
4.8 User Requirements

The user requirements of a system can be divided into two main categories namely
functional requirements and nonfunctional requirements.

4.8.1 Functional Requirements

The system functional requirements are given below:

❖ The system shall enable users to create, update and view profile
❖ The system shall prompt user to fill up information correctly
❖ The system shall enable user to select desire fields
❖ The system shall enable user to read blog
❖ The system shall enable user to participate in contest, model test
❖ The system shall enable user to post a question for seeking help
❖ The system shall enable user to review answered questions
❖ The system shall enable user to review their performance
❖ The system shall enable admin to manage the system
❖ The system shall enable admin to select all categories
❖ The system shall enable admin to set time, questions and marks
❖ The system shall enable admin to delete any user account

4.8.2 Nonfunctional Requirements

The system nonfunctional requirements are given below:

❖ There should be sufficient network bandwidth

❖ Data should be backed up regularly
❖ The system should be easily maintainable
❖ The system should be easy to use
❖ The system should be upgrade and extendable
❖ The system should safe to use
❖ The system should ease to access
❖ The system should have user friendly environment

Page | 31
4.9 System Requirements

The system requirements can also be divided into two main categories they are
Software requirements and Hardware requirements.

4.9.1 Software Requirements

The system software requirements are given below:

❖ Operating System: Windows XP/ Windows 7/ Windows 8/ Windows

10/ Linux
❖ Technology: HTML, CSS, JavaScript, Bootstrap, JQuery,PHP, Laravel,
Vue.JS, Bulma CSS
❖ Database: MySQL
❖ Testing/ Running Platform: Firefox browser, Google Chrome, Safari
etc.
❖ Antivirus
❖ Backup and Data recovery software

4.9.2 Hardware Requirements

The system hardware requirements are given below:

❖ Processor: Intel Dual core or above

❖ RAM: 512MB or above
❖ Internet connection
❖ USB flash drive

Page | 32
CHAPTER-5

System Design

Page | 33
5. System Design
Systems design is simply the design of systems. It implies a systematic and rigorous
approach to design an approach demanded by the scale and complexity of many
systems problems. It gives a visual model of a system, its components, and their
interactions. With supporting documentation, it can capture all the essential
information of a system's design. There are many variations of diagramming style that
all fall under this rubric. The style presented here is intended to be optimally consistent
with the rest of this courseware. The objective of the system design is to deliver the
requirements as specified in the feasibility report. System design involves first logical
design and then physical construction of the system. The logical design describes the
structure and characteristics of features, such as the outputs, inputs, files, databases,
and procedures. The physical construction produces actual program software, files, and
a working system.
The different level of user has different activities in the system. On the basis of
activities this system can be divided into several main activities. They are guest user’s
activities, register user’s activities, admin’s activities. The activities with System and
Database are described as follows:

5.1 Guest User’s Activity

An unregistered user can practice questions from practice section by selecting

different subjects, s/he can also access for view question that has been posted in
forum section or blog.

5.2 Registered User’s Activity

A registered user can practice MCQ by selecting any subject, creats or update own
profile, can select exam categories, can attend in model test and contest, s/he can
post any kind of important information, notices, motivational speech etc. in forum
section. A registered user also can see his/her performance, can see and practice
question bank.

Page | 34
5.3 Admin’s Activity

Admin can view user details, select number of question with point, can set duration
of exam, can delete and block users. On the other hand admin also can schedule
specific date and time for an exam. Admin has the ability to add chapters, add
categories, add subjects, edit or delete every aspect.

5.4 Super Admin’s Activity

Super admin can view admin details, create admin, delete or block admin, user
details, select number of question with point, can set duration of exam, can delete
and block users. On the other hand super admin also can schedule specific date and
time for an exam with event. Super admin has the ability to add chapters, add
categories, add subjects, edit or delete every aspect.

Page | 35
CHAPTER-6

Testing

Page | 36
6. Testing

Software Testing is a process which tests whether the software meets the
requirements and fulfills all the criteria or not. System can be divided into two main
categories they are Integrated Testing and Release Testing. Software testing involves
the execution of a software component or system component to evaluate one or more
properties of interest. In general, these properties indicate the extent to which the
component or system under test:
➢ Meets the requirements
➢ Responds correctly
➢ Perform functions successfully
➢ Ensure usability
➢ Can be run in its intended environments
➢ Achieves the goals of requirements

The answer of the following question for this system is yes. All the functional works
have checked and tested. After completing the testing process it have ensured that the
software is running accurately and it have been fulfilled all the criteria of
requirements.

6.1 Requirement Traceability

From the requirement documentation all functional requirement have fulfilled.

They are given below:

Registered User:
➢ Registered user can view, download, print & saved question
➢ They will participate in exam
➢ They can update their profile
➢ They can ask question in the forum and also reply to a question

Page | 37
 Guest User:
➢ Guest user can view, download, print question
➢ View forum question
➢ Show blog post

Super Admin:
➢ Control full software
➢ Super admin can add, update & delete admin
➢ They can add question set
➢ Customized site option
➢ They can add, update & delete event

Admin:
➢ Add question set
➢ Admin can view event with details
➢ Admin can add, update & delete blog post
➢ Customized site option

The above functional requirements have tested and they are working properly as
required.

Page | 38
CHAPTER-7

Implementation

Page | 39
7. Implementation

Implementation is next after testing. After long explanation and building phases the
system is developed and tested. Implementation is the stage of system development
life cycle. The system is implemented into operation in real environment. A formal
acceptance typically terminates the implementation stage. After the implementation
phase software development lifecycle is the most expensive and time consuming.

There are many ways of implementation. It must be decided which way to adopt prior
to implementation. This phase required many things for consideration because a
wrong approach could bring unexpected result. The risk associate with this phase
should be sorted out. The typical advantages and disadvantages are also the important
factor for implementation.

For front desk implementation method will be parallel and the new system will run
parallel to old one. Implementation is expensive because too many people are
associated with the process, it’s also time consuming as the works are completed
during implementation. Backup should be used. Then if any problem occurs and the
system would not affected badly.

7.1 Education
It is essential for any system that the users of the system must know the context of
the organization need. User must be influenced of the benefits of a new system to
them. The first and foremost decision in education and training must be about the
operator to be educated and trained.

Page | 40
7.2 Training
The training phase is a phase where the user of the system are trained. In training the
following methods can be used:
➢ Observation
➢ Informal Discussion
➢ Computer Assisted Training
➢ User Manual

Page | 41
CHAPTER-8

Maintenance

Page | 42
8. Maintenance
Software maintenance is widely accepted part of SDLC now a days. It stands for all the
modifications and updating done after the delivery of software product. There are
number of reasons, why modifications are required, some of them are briefly
mentioned below:
➢ Market Conditions: Policies, which changes over the time, such as taxation and
newly introduced constrains like, how to maintain bookkeeping, may trigger
need for modification.

➢ Client Requirements: Over the time, instruction may ask for new features or
functions in the software.

➢ Host Modification: If any of the hardware and/or platform (such as operating

system) of the host changes, software changes are needed to keep adaptability.

➢ Organization Changes: If there any business level change at client end, such as
reduction of organization strength, acquiring another company, organization
venturing into new business, need to modify in the original software may arise.

8.1 Types of maintenance

In a software lifetime, type of maintenance may vary based on its nature. It may be
just a routine maintenance tasks as some bug discovered by some user or it may be a
large event in itself based on maintenance size or nature. Following are some types of
maintenance based on their characteristics:

• Corrective Maintenance: This includes modifications and updates done

in order to correct or fix problems, which are either discovered by user
or concluded by user error reports.

• Adaptive Maintenance: This includes modifications and updates done in

order to keep the software product up to date and tuned to the ever
changing world of technology and business environment.

Page | 43
• Perfective maintenance: This includes modifications and updates done
in order to keep the software usable over a long period of time. It
includes new features, new user requirements for refining the software
and improve its reliability and performance.

• Preventive Maintenance: This includes modifications and updates to

prevent future problems of the software. It aims to attend problems,
which are not significant at this moment but may cause serious issues in
future.

Page | 44
 CHAPTER-9

Software Interface
Or
User Interface

Page | 45
9.1 Software Interface

Software Interface or User Interface is the front-end application view to which user
interacts in order to use the software. User can manipulate and control the software
as well as hardware by means of user interface. Today, user interface is found at
almost every place where digital technology exists, right from computers, mobile
phones, cars, music players, airplanes, ships etc.

User interface is part of software and is designed such a way that it is expected to
provide the user insight of the software. UI provides fundamental platform for human-
computer interaction.

UI can be graphical, text-based, audio-video based, depending upon the underlying

hardware and software combination. UI can be hardware or software or a combination
of both. The software becomes more popular if its user interface is:
• Attractive
• Simple to use
• Responsive in short time
• Clear to understand
• Consistent on all interfacing screens

9.2 User Interface Design Activities

There are a number of activities performed for designing user interface. The process
of GUI design and implementation is alike SDLC. Any model can be used for GUI
implementation among Waterfall, Iterative or Spiral Model.
A model used for GUI design and development should fulfill these GUI specific steps.

Page | 46
• GUI Requirement Gathering - The designers may like to have list of all
functional and non-functional requirements of GUI. This can be taken from user
and their existing software solution.

• User Analysis - The designer studies who is going to use the software GUI. The
target audience matters as the design details change according to the knowledge
and competency level of the user. If user is technical savvy, advanced and
complex GUI can be incorporated. For a novice user, more information is included

on how-to of software.

• Task Analysis - Designers have to analyses what task is to be done by the

software solution. Here in GUI, it does not matter how it will be done. Tasks can
be represented in hierarchical manner taking one major task and dividing it
further into smaller sub-tasks. Tasks provide goals for GUI presentation. Flow of
information among sub-tasks determines the flow of GUI contents in the
software.

• GUI Design & implementation - Designers after having information about

requirements, tasks and user environment, design the GUI and implements into
code and embed the GUI with working or dummy software in the background. It is
then self-tested by the developers.

• Testing - GUI testing can be done in various ways. Organization can have in
house inspection, direct involvement of users and release of beta version are few
of them. Testing may include usability, compatibility, user acceptance etc. Our
application is an android application. So, Software Interface is the most important
part here. We have several android activities in this project which are like several
pages.

Page | 47
9.3 Main Interface

Figure: Home page

This home page allows user to get login by clicking on login button. It allows user to full
access of this site. User can select their desire field like view school/madrasha, bcs,
university and other question. Also user can select their desired subject and categories to
participate in a test.

Page | 48
9.4 Registration

Figure: Registration

This page allow the new user to get register by using this registration form.

Page | 49
9.5 Login

Figure: Login

Registered user will get full access to the site by valid login. They can login by email and
password or can login with social app.

Page | 50
9.6 Question Set

Figure: Question Set

This pages allow users to view creative/mcq question. User can view question by category
like School, Madrasha, University, BCS etc.

Page | 51
9.7 Examination

Figure: Examination

This page allows user to participate in exam with a given time. Here user can also able to see
remaining time of the exam and the number of question.

Page | 52
9.8 Review Question Answer

Figure: Reviewed Answer

This page allows a user to see after participating in a test his or her total number of correct
answers, no answers and wrong answers. He or she also able to get the all correct answers
of a given question set.

Page | 53
9.9 Review Performance

Figure: Performance pie and bar chart

This page allows a user to review his performance after participating in exam.

Page | 54
9.10 Admin Panel

Figure: Admin Panel

The whole system will be maintain from this admin panel. Admin can add, update and
delete question set. Also they will maintenance users, forum, blog etc. Super Admin can add
new admin with specific role.

Page | 55
CHAPTER-10

Conclusion

Page | 56
10. Conclusion
We have tried our best for making this system user friendly as well as usable. The
system is developed under responsive frame work and upgraded technologies so
that the system can run from any devices like PC, Tab, Laptop, Mobile etc. We have
tried our best for making this project cost-effective and flexible. During development
of the software all phases have completed carefully. A sin case of any system
development process there might be few shortcomings. So this project is still under
modification. Future up gradation and enhancement will be continued for keeping
the system up to date.

Page | 57
10.1 References:

Type Source

1. Software Engineering, 8th Edition by Sommerville

2. Database System Concepts, 6th Edition by Avi

Silberchatz, Henry F. Kroth, S. Sudarshan. Published by
Mcgraw-Hill, ISBN: 0-07-352332-1
3. লারাভেল পিএইচপি ওভেব ফ্রেমওোর্ক – নুরুজ্জামান
পমলন

Books 4. System Analysis and Design, 4th Edition by John W.

Satzinger, Robert B. Stephen, D. Burd, ISBN:
10:1305117204

5. First Course in Database Systems, 3rd Edition by Jeffery

D. Ullman and Jennifer Widom, ISBN: 0-13-861337-0

1. http://www.w3schools.com

2. http://www.tutorialspoint.com

3. http://www.laravel.com

Website 3. http://www.nctb.gov.bd/

6. https://bulma.io

7. https://vuejs.org/

7. http://www.laravel.howtocode.com.bd/

Page | 58
10.3 Abbreviations:

Admin Short Form of Administrator

Bootstrap Designing Framework combination of HTML, CSS and JavaScript

BCNF Short Form of Boyce and Codd Normal Form

CSS Short Form of Cascading Style Sheet

HTML Short Form of Hyper Text Markup Language

JavaScript Lightweight, Interpreted programming language

Bulma A Modern CSS Framework Based on Flexbox

TinyMCE Tiny Moxicode Content Editor

MySQL Is an open source relation database management system

(RDBMS)

PHP Is a server side scripting language designed for web

development but also used as general purpose programming
language

Laravel A PHP Framework

JQuery JQuery is a fast and console JavaScript Library

Ajax AJAX stands for Asynchronous JavaScript and XML

Vue.js A JavaScript Framework

Page | 59