Iq and Interest Finding System: Undertaken by

IQ AND INTEREST FINDING SYSTEM
Undertaken by:
MATEEN ASGHAR
CIIT/FA15-BS(SE)-014/WAH
USMAN KHALID
CIIT/FA15-BS(SE)-015/WAH
Supervised by:
MAM SAMRA SIDDIQUI
DEPARTMENT OF COMPUTER SCIENCES
COMSATS UNIVERSITY ISLAMABAD, WAH CAMPUS
SESSION 2015-2019
i
ACKNOWLEDGEMENTS
All praises, thanks and acknowledgements to Almighty ALLAH, the most merciful
and beneficent, who is entire source of knowledge and wisdom endowed to
mankind, enabled me to carry out my research work. All praises to our Last
Prophet Hazrat MUHAMMAD (Peace Be upon Him), who is forever a torch of
guidance and knowledge for humanity as a whole.
I offer my sincerest gratitude to my supervisor, Mam Samra Siddiqui, Department

of Computer Science, COMSATS University Islamabad (Wah campus),for her
advice throughout my research work. Her observations and comments helped me
to establish the overall direction of the research and to move forward with
investigation in depth. She was always there to offer quite encouragement by her
own extraordinary kindness. I just cannot thank her enough for her unconditional
support.
I am forever grateful to my parents, for their continuous moral support and for
boosting my dedication towards the studies and knowledge. To my brother and
sister who gently offer counsel and unconditional support at each turn of the road.
Many of the acknowledgements of thesis are done at the last minute. My

acknowledgments are no exceptions. It is during this time that one often forgets to
mention some of the biggest inspiration, encouragement and support. Life is not
measured in the number of breaths we take, but in the moments that take our
breaths away; this thesis is a small tribute to all of those moments.
May ALLAH bless them.
ii
PROJECT BRIEF
PROJECT NAME: IQ AND INTERSEST FINDING SYSTEM
PROJECT OBJECTIVE: TO MEASURE IQ AND INTEREST OF USER.
UNDERTAKEN BY MATEEN ASGHAR

USMAN KHALID
SUPERVISED BY MAM SAMRA SIDDIQUI

LECTURAR
DEPARTMENT OF COMPUTER SCINECE
COMSATS UNIVERSTY ISLAMABAD- WAH
CANTT
STARTED ON July, 2018
COMPLETED ON June, 2019
COMPUTER USED Core i7
OPERATING SYSTEM WINDOWS 10
TOOLS USED MICROSOFT VISUAL STUDIO-2019, Microsoft

SQL Server Management Studio 17
iii
Table of Contents
Chapter 1: ...................................................................................................................................... 1
INTRODUCTION ........................................................................................................................ 1
1.1. Statement of the problem ................................................................................................. 2
1.2. Purpose ............................................................................................................................. 2
1.3. Scope of the system .......................................................................................................... 2
1.4. Projects function............................................................................................................... 2
1.5. Project features ................................................................................................................. 2
1.6. Aim and objectives ........................................................................................................... 3
Chapter 2: ...................................................................................................................................... 4
LITERATURE REVIEW ............................................................................................................ 4
2.1 Literature Review................................................................................................................. 5
2.2 Tools .................................................................................................................................... 5
2.2.1 Microsoft Visual Studio ................................................................................................. 5
2.2.2 Microsoft SQL Server Management .............................................................................. 5
2.2.3 Hardware Requiremnets ................................................................................................ 5
2.3 Functional Requirements ...................................................................................................... 6
2.4 Functional Requirements ...................................................................................................... 6
2.4.1 Serviceability: ................................................................................................................. 8
2.4.2 Reliability:....................................................................................................................... 8
2.4.3 Maintainability: ............................................................................................................... 8
2.4.4 Extensibility: ................................................................................................................... 8
2.4.5 Reuseability..................................................................................................................... 9
2.4.5 Performance .................................................................................................................... 9
2.4.5 Availability ..................................................................................................................... 9
2.4.5 Portability........................................................................................................................ 9
Chapter 3………………………………………………………………………………………..10
SYSTEM DESIGN ……………………………………………………………………….……10
3.1 Introduction…………………………………………………………………...……........10
3.2 Structure Analysis…………………………………………………………………….…10
3.3 Interface Design Strategy…………………………………………………………….….11
3.4 Interface design and Requirements……………………………………………………...11
iv
3.4.1 User interface…………………………………………………………………….……11
3.4.2 GUI……………………………………………………………………………………12
3.4.3 Hardware interface……………………………………………………………….…...19
3.4.4 Communication interfaces……………………………………………………….…...19
3.5 Interface Constraints……………………………………………………………….…....19
Chapter 4……………………………………………………………………………………….20
SYSTEM MODELING……………………………………………………………….….........20
4.1 Interface Constraints……………………………………………………….……………20
4.1.1 Actors in system………………………………………………………………...…. .20
4.1.2 Use Case Diagram................................................................................................…...21
4.1.3 Activity Diagram……………………………………………………………….…...23
4.1.4 Class Diagram……………………………………………………………….…........24
Chapter 5………………………………………………………………………………………26
IMPLEMENTATION………………………………………………………………………....26
5.1 Introduction……………………………………………………………………………..26
5.2 Pseudo code……………………………………………………………………………..26
5.3 Complexity Analysis……………………………………………………………………27
5.4 Feasibility Analysis…………………………………………..…………………………27
5.6 Coding……………………………………………………….……………………….....28
5.7 Testing……………………………………………………..……………………………28
Chapter 6……………………………………………………………………………………....29
TESTING……………………………………………………………………………...………29
6.1 Introduction………………………………………………………………………..……29
6.2 Types of testing………………………………………………………………………....29
6.2.1 Black box testing……………………………………………………………….…....29
6.2.2 White box testing…………………………………………………………….……...30
6.2.3 Unit testing……………………………………………………………….….............30
6.2.4 Incremental integration testing………………………………………………....……30
6.2.5 Integration testing……………………………………………………………….…...30
6.2.6 Functional testing……………………………………………………………….…....31
6.2.7 System testing……………………………………………………………….….........31
6.2.8 End to End testing……………………………………………………………...…….31
6.2.9 Regression testing……………………………………………………………….…...32
6.2.10 Acceptance testing……………………………………………………………….…32
6.2.11 Load testing………………………………………………………...….……………33
6.2.12 Stress testing……………………………………………………………….…..........33
6.2.13 Performance testing……………………………………………....…………………33
6.3 Testing Strategies……………………………………………………………….…........33
6.3.1 Test plan……………………………………………………………….…..................34
6.4 Test Cases….……………………………………………………………………………34
v
Chapter 7………………………………………………………………………………………36
7.1 CONCLUSION AND FUTURE WORK……………………………………………..36
Chapter 8……………………………………………………………………...……………….37
8.1 REFERENCES…………………………………………………………..…………….37
vi
LIST OF FIGURES
Figure 3.1 Splash Screen............................................................................................................... 12

Figure 3.2 User entry interface ..................................................................................................... 13
Figure 3.3 Questionnaires screen .................................................................................................. 14
Figure 3.4 Result screen 1 ............................................................................................................. 15
Figure 3.5 Result Screen 2 ............................................................................................................ 16
Figure 3,6 Contact screen ............................................................................................................. 17
Figure 4.1 Use case diagram ......................................................................................................... 20
Figure 4.2 Activity diagram .......................................................................................................... 21
Figure 4.3 class diagram ............................................................................................................... 22
vii
LIST OF TABLES
Table 2.1 Hardware requirements ................................................................................................... 5

Table 2.2 Collection of user data .................................................................................................... 6
Table 2.3 learning algorithms ......................................................................................................... 6
Table 2.4 learning datasets .............................................................................................................. 6
Table 2.5 Real time diagnose .......................................................................................................... 7
Table 2.6 Recommendation for patient ........................................................................................... 7
Table 6.1 Test case ........................................................................................................................ 32
viii
Chapter 1
INTRODUCTION
1.1. Statement of the Problem
In today’s world there are many ways of Entertainment, large number of systems is available for
relaxing but most of people want Entertainment and Learning together. So there is a need for an
online system, which can solve their problems in learning.
1.2. Purpose
The main purpose of this system is to provide IQ testing for people. In this software system, user
could be a student. And this system provides an IQ testing and interest checking. People will
learn about their IQ and interest. Peoples also get reports of his/her performance. Well this
system will provide a good way of learning.
1.3. Scope of the system

The name of our product will be “IQ ANDINTREST FINDING SYSTEM” and its function is to
check the IQ and interest of user. This product will provide the facility of checking the interest in
both entertainment and education catalogues. The targeted user groups are the remote students
who will be the main benefit bearer.
1.4. Projects function

The project functionalities are:
1. Login.
2. Create Account.
3. Catalogue Selection.
4. Select Difficulty Level.
5. Solve questionnaire.
6. View Results.
7. View Progress.
1.5. PROJECT FEATURES

We have tried to build a more precise and conclusive product which satisfies the current needs of
the users. To make it popular among the web users few advanced features have been added. The
IQ AND INTERSEST FINDING SYSTEM

2
proposed system will be helpful to those who want to examine or test IQ but can’t afford due to
shortage of money and time.
1.6. AIM AND OBJECTIVES

IQ is a unique key of success the one who is having low IQ or one who is having high IQ will
definitely matters. Students will be able to use this product to measures IQ now be able to make
this happen automatically. Everyone can access this site and using this he will be able to know
his IQ.

3
Chapter 2
Literature Review
2.1 Literature Review
The application has meant for measurement purpose, to measure IQ in users. The
project is software based with no hardware, being involved. Internet connection is the
must for a few features. The user interaction with the system and the processing done
within the system is supposed to well managed and fully organized.
2.2 Tools
The system will be developed using Microsoft Visual Studio, which includes
Microsoft SQL Server Management Studio 17.
2.2.1 Microsoft Visual Studio

Microsoft Visual Studio is the most well-known software for creating web
applications. Lots of web products are being produced using Microsoft Visual Studio.
It is one of the easiest ways to create a web product.
2.2.2 Microsoft SQL Server Management Studio

It is the built-in feature of Microsoft Visual Studio. Some other emulators are also
available on the internet which is compatible with Microsoft Visual Studio. Emulators
are used by developers for the simultaneous testing of Microsoft Visual Studio.
2.3 FUNCTIONAL REQUIREMENTS

Following are the functional requirements of the system:
 Register user can create account.
 Register user can select catalogue.
 Register user can select difficulty level.
 Register user can solve quizzes.
 Register user can solve puzzles.
 Register user can check result.

5
Table 2.1: Create Account
Title Login or signup

Description Login/signup makes a way to enter in the system.
Criticality Important Functionality
Technical Issues Requires internet connection
Cost and Schedule 1 week
Risks No
Dependent with other Nil
requirement
Table 2.2: Solve Quizzes
Title Solve Quizzes

Description Solve quizzes makes a way to enter in the respected catalogue.
Technical Issues Requires internet connection
Cost and Schedule 1 week
Risks No
Dependencies with other No
requirement
Table 2.3: Catalogue Selection
Title Catalogue Selection

Description Catalogue Selection makes a way to enter in the respected
catalogue.
Technical Issues Requires Internet Connection
Cost and Schedule 2 weeks
Risks No
Dependencies with another No
requirement

6
Table 2.4: Solve Puzzles
Title Select Difficulty

Description Select difficulty makes a way to enter in the respected
catalogue.
Risks No
requirement
Table 2.5: Check Result
Title Select Difficulty

Description Select difficulty makes a way to enter in the respected
catalogue.
Risks No
requirement

7
2.4 NON FUNCTIONAL REQUIREMENTS
Following are the nonfunctional requirements:
 Interactive interface
 Fast and instantaneous response
 Target latest browsers
2.4.1 SERVICEABILITY
Proper documentation should be provided so modifications can be made
efficiently.
2.4.2 RELIABILITY
 The system will not crash under any circumstances.
 It will always be available to the user end.
 If the system gets crashed, then it will be recover in minimum time
 The system will be more reliable than the manual system, due to its accurate,
secure and timely decision making.
2.4.3 MAINTAINABILITY
The system can go under changes and updating process in the future. The product will
have SDLC and can be fixed if any failures occur. There will be evaluations of the
system on quarterly basis and stringent performance enhancement measure will be
inducted.
This Project is maintainable that allows to have a window of debugging tool. So this
project is maintainable. This project involves software only and, it is always easy to
maintain projects which do not involve hardware.
2.4.4 EXTENSIBLITY
The system can be extended later with other functionalities required.
2.4.5 REUSABILITY
Reusability of levels for further efficiency of the product.

8
2.4.6 PERFORMANCE
 The application will be fault tolerant.
 Quick response to the user inputs.
 Error reporting will be efficient.
2.4.7 PORTABILITY:
The application can be used on any computer. Good internet connection is
compulsory for certain feature to work properly. Anyone can access the site on
computer in any corner of the world.

9
CHAPTER 3
SYSTEM DESIGN
10
3.1 INTRODUCTION
Design helps to analyze the working flow and architectural study of the system. Design act as a
base for proceeding activities in the development cycle. The robustness and efficiency of
software depends on its design. A good design leads to efficient software.
System Design is the phase of quality and effort estimation in software development. For the
better development of any project, clear and feasible design is required. Design helps to convert
the user requirements into graphical representation which helps to identify flaws and weakness.
Software without good design are always annoying to change and modify.
3.2 STRUCTURE ANALYSIS

We have used Incremental Prototyping for developing our web application. This approach
helped us to modify the application at any stage, it also made the testing and debugging easy.
The incremental approach helped us to add new modules and, to conduct their testing. Software
prototyping refers to the activity of creating prototypes of software applications, i.e., incomplete
or underdeveloped versions of the software being developed. A prototype typically simulates
only a few aspects of the final solution; it may differ from the final product.
Prototyping has several benefits:
 The designer and coder can get valuable feedback from the users in the early phase of the
project.
 It helps to check whether the software is according to the specified requirements or not.
 It helps to meet the deadlines.
3.3 INTERFACE DESIGN STRATEGY

Whiling designing the interface we have tried to create simple, attractive and user friendly
interface. The impact of Interface design is more critical and crucial. Many web users judge site
via its interface. We used Gold driven approach to make design and this approach is:
 Design then code
 Responsibilities are separated
 To achieve user satisfaction
 Know the target audience.
11
3.4 INTERFACE DESIGN & REQUIREMENTS
3.4.1 User Interface
The system will consist of interactive and easy to use GUI’s designed. User Interface reflects to
the first impression of user. User Interface is as important as functionalities and features. Many
web applications are famous only because of fine user interface.
3.4.2 GUI
The Graphical User Design of our web applications are as follows.
Fig 3.1 Login Page

12
Fig 3.2 Catalogue Page
Fig 3.3 Selection Page

13
Fig 3.4 Math Quiz

14
Fig 3.5 Entertainment Catalogue
Fig 3.6 Sudoku Game

15
Fig. 3.7 Word Search
Fig. 3.8 Result Page

16
3.4.3 Hardware Interfaces
This project is completely software based. There is no hardware involved in the project.
3.4.4 Communications Interfaces

Internet connection is required to show pictures in icons
The interface are in one language i.e. English.
3.5 INTERFACE CONSTRAINTS

While making interface we kept in mind that there are different constraint and limitation in
interface design and these are listed below:
 Interface should be usable
 interface should be attractive
 easy to adopt changes
 Limited to web applications.

17
CHAPTER 4
SYSTEM MODELING
4.1 USE CASE MODELING
A diagram is a set of graphical representations of a set of arcs. This section presents the list of
the functional objects that are modeled within the system to satisfy its requirements. The
purpose is to provide alternative, “structural” views on the requirements stated above and, how
they might be satisfied in the system. The diagrams shave been developed in UML.
4.1.1 ACTORS IN SYSTEM

The actors in the system are
1. Test Case User.
2. Server.
4.1.2 USE CASE DIAGRAM
Fig 4.1: Use Case Diagram

19
4.1.4 ACTIVITY DIAGRAM
Fig 4.2: Activity Diagram

20
4.1.5 CLASS DIAGRAM
Fig4.3: Class Diagram

21
CHAPTER 5
IMPLEMENTATION
5.1 INTRODUCTION
The proposed system is to develop a web app covering the aspects related to IQ and Interest.
This application will use computations provided then afterward application will ask users with
the questionnaire and save the result set in the local repository. The answers we get after will let
us know that the relevant user is having how much IQ.
5.2 PSEUDOCODE
Pseudo code is the written form of a computations on a piece of paper and not in computer
language. It is written using graphical symbols to make it easy to understand.
After a successful analysis of the computations, we have carefully drafted pseudo code. Pseudo
code is quite similar to computations but differs technically. The computations helps to create a
logic whereas, pseudo code helps to convert the computations into code. Our pseudo code was
not only helpful in the development of good code but, also helped to modify and adopt changes
early in the development.
5.3 COMPLEXITY ANALYSIS

We have tried our best to keep the complexity of code easy. We have used comments to make it
easy to understand for the developers. The code is as easy as it can be. The algorithm is also easy
to understand.
Modification is the step that involves complete understanding and analysis of code. Our code is
easy to understand which, makes it easy to modify. The code has been written using extendable,
modifiable, flexible, portable, and reliable and many other such techniques. Thus, making the
code easy to debug and test.
5.4 FEASIBILITY ANALYSIS

Every point we have mentioned in the SRS document was feasible. We have carefully analyze
every feature and its feasibility. We have use Incremental Prototype model which makes the

23
feasibility analysis easy for every module. Our application is more than 90% as desired. Our
product is according to the requirements that were described thoroughly in the SRS document.
5.5 CODING
The coding has been done by using Microsoft Visual studio. C# and .net is the programming
language that visual studio supports.
Like many other web developers, we have used .net and C# for the coding and development of
our application. C# and .net makes it easy to create an application with tons of tutorials available
on the internet.
5.6 TESTING
We will discuss testing thoroughly in the next chapter.

24
CHAPTER 6
TESTING
6.1 INTRODUCTION
We have tested our application step by step. On the completion of each module, testing had been
performed by us. The development and testing were being run in parallel by us. This approach
allows us to build error and bugs free module.
This chapter includes some test cases for the app to check if the app works properly in various
situations.
Different testing techniques had been used to calculate the software cost and effort. Newer
development models, such as Agile, often employ test driven development and place an
increased portion of the testing in the hands of the developer, before it reaches a formal team of
testers. In a more traditional model, most of the test execution occurs after the requirements are
defined and the coding has done.
6.2 TYPES OF TESTING

Developers are using different software testing techniques according to the requirement and need
of the project.
6.2.1 BLACK BOX TESTING

It is based on the requirements and functionalities of the software. It has nothing to do with the
internal design and code of the software.
6.2.2 WHITE BOX TESTING

It is also known as Glass box testing. In this type of testing, the working and performance of the
code are tested. In white box testing the developer test the path flow, branches, loops, and other
perimeters of coding.

26
6.2.3 UNIT TESTING
Testing of individual software components or modules. Typically it‘s done by the programmers
but not by the testers. As it requires detailed knowledge of the internal program design and code.
May requires developing test driver modules or test harnesses.
6.2.4 INCREMENTAL INTEGRATION TESTING

This approach is also known as a bottom-up. For the addition of every new functionality in the
module, the developer has to test it. Application functionality and modules should be
independent enough to test separately. It‘s done by programmers or by testers.
6.2.5 INTRETAGION TESTING

Testing of integrated modules to verify combined functionality after integration. Modules are
typically code modules, individual applications, client and server applications on a network, etc.
This type of testing is especially relevant to client/server and distributed systems.
6.2.6 FUNCTIONAL TESTING

This type of testing ignores the internal parts and focus on the output is as per requirement or not.
6.2.7 SYSTEM TESTING

It involves thorough system testing. Every module comprises of different functionalities. These
functionalities are checked by testers to ensure the overall correct working of the system. It is the
subtype of Black box testing which is responsible for the flawless working.
6.2.8 END TO END TESTING

Similar to system testing involves testing of a complete application environment in a situation
that mimics real-world use, such as interacting with a database, using network communications,
or interacting with other hardware, applications, or systems if appropriate.

27
6.2.9 REGRESSION TESTING
Testing the application as a whole for the modification in any module or functionality. It is
difficult to test all the system in regression testing so, automation tools used for it.
6.2.10 ACCEPTANCE TESTING

Normally this type of testing is done to verify if the system meets the customer specified
requirements. User or customers do this testing to determine whether to accept the application.
6.2.11 LOAD TESTING
It‘s a performance testing to check system behavior under load. Testing an application under
heavy loads, such as testing of a web site under a range of loads to determine at what point the
system‘s response time degrades or fails.
6.2.12 STRESS TESTING

The system is stressed beyond its specifications to check how and when it fails. It‘s performed
under heavy load like putting large number beyond storage capacity, complex database queries,
continuous input to system or database load.
6.2.13 PERFORMANCE TESTING

The term often used interchangeably with stresses and load testing. It checks whether the system
meets performance requirements. It‘s used different performance and load tools to do this.
6.3 TESTING STRATEGIES

A strategy for software testing integrates software test case design techniques into a well -
planned series of steps that result in the successful construction of software. Testing begins at
module level and ends with system integration. The developer of the software conducts testing
and, for large projects an independent test group conducts it. Testing and debugging are different
activities but, debugging must be accommodated in any testing strategy.
We have used Incremental Prototype Software development technique for the parallel testing of
our product.

28
6.3.1 TEST PLAN
A test plan is a document detailing a systematic approach to testing a system such as a machine
or software. The plan contains a detailed understanding of what the eventual workflow will be.
6.4 TEST CASES

Table 6.1
TEST CASE
Test Case Math Test
Test Procedure App questionnaire.
Expected Result False
Actual Result False
Comment IQ measured
Conditional Test Dump answers
Expected Result True
Actual Result True
Accuracy 100

29
30
CHAPTER 7
CONCLUSION AND FUTURE WORK

The IQ AND INTREST FINDING SYSTEM has been accomplished completely
and precisely. It is high speed app that generate result after solving questionnaire
within seconds and does not create memory lapse. It gives accurate answers
because we use linear computations to compare the answers.
User solves questionnaire and match the answers with our data set module and
generate the answers that the user have how much IQ.
This web app is basically for Children’s to measure IQ in future we will work on
its Adults IQ measuring version. In adult’s version web app includes game play for
they have to play game for measuring IQ.

31
REFERENCES
[1]Smart Sheet URL: https://www.smartsheet.com/gantt-chart-software
[2]Sequence Diagram URL: https://creately.com/app/?tempID=hx5la1ky1&login_type=demo#
[3]Use Case Diagram URL: https://app.genmymodel.com/edit/fe33ab9b-0478-48a8-ba70-
d0004f97f3e5#access_token=6807fe57-d43b-4f45-b5f7-
e5764e19ea98&token_type=bearer&expires_in=160928&scope=read%20write
[4]Class Diagram URL: https://repository.genmymodel.com/Mateenasghar/SRSFYP
[5]Activity Diagram URL:
https://www.uml.com/search?q=activity+diagram&oq=act&aqs=chrome.2.69i57j69i60j69i59j69
i60l2j69i59.3384j0j7&sourceid=chrome&ie=UTF-8
33

Iq and Interest Finding System: Undertaken by

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Iq and Interest Finding System: Undertaken by

Загружено:

Авторское право:

Доступные форматы

IQ AND INTEREST FINDING SYSTEM

MAM SAMRA SIDDIQUI

DEPARTMENT OF COMPUTER SCIENCES

COMSATS UNIVERSITY ISLAMABAD, WAH CAMPUS

I offer my sincerest gratitude to my supervisor, Mam Samra Siddiqui, Department

Many of the acknowledgements of thesis are done at the last minute. My

May ALLAH bless them.

PROJECT NAME: IQ AND INTERSEST FINDING SYSTEM

PROJECT OBJECTIVE: TO MEASURE IQ AND INTEREST OF USER.

UNDERTAKEN BY MATEEN ASGHAR

SUPERVISED BY MAM SAMRA SIDDIQUI

STARTED ON July, 2018

COMPLETED ON June, 2019

COMPUTER USED Core i7

OPERATING SYSTEM WINDOWS 10

TOOLS USED MICROSOFT VISUAL STUDIO-2019, Microsoft

Figure 3.1 Splash Screen............................................................................................................... 12

Table 2.1 Hardware requirements ................................................................................................... 5

1.3. Scope of the system

1.4. Projects function

1.5. PROJECT FEATURES

IQ AND INTERSEST FINDING SYSTEM

1.6. AIM AND OBJECTIVES

IQ AND INTERSEST FINDING SYSTEM

2.2.1 Microsoft Visual Studio

2.2.2 Microsoft SQL Server Management Studio

2.3 FUNCTIONAL REQUIREMENTS

IQ AND INTERSEST FINDING SYSTEM

Title Login or signup

Table 2.2: Solve Quizzes

Title Solve Quizzes

Table 2.3: Catalogue Selection

Title Catalogue Selection

IQ AND INTERSEST FINDING SYSTEM

Title Select Difficulty

Table 2.5: Check Result

Title Select Difficulty

IQ AND INTERSEST FINDING SYSTEM

IQ AND INTERSEST FINDING SYSTEM

IQ AND INTERSEST FINDING SYSTEM

3.2 STRUCTURE ANALYSIS

3.3 INTERFACE DESIGN STRATEGY

Fig 3.1 Login Page

IQ AND INTERSEST FINDING SYSTEM

Fig 3.3 Selection Page

IQ AND INTERSEST FINDING SYSTEM

Fig 3.6 Sudoku Game

IQ AND INTERSEST FINDING SYSTEM

Fig. 3.8 Result Page

IQ AND INTERSEST FINDING SYSTEM

3.4.4 Communications Interfaces

3.5 INTERFACE CONSTRAINTS

IQ AND INTERSEST FINDING SYSTEM

4.1.1 ACTORS IN SYSTEM

Fig 4.1: Use Case Diagram

IQ AND INTERSEST FINDING SYSTEM

Fig 4.2: Activity Diagram

IQ AND INTERSEST FINDING SYSTEM

Fig4.3: Class Diagram

IQ AND INTERSEST FINDING SYSTEM

5.3 COMPLEXITY ANALYSIS

5.4 FEASIBILITY ANALYSIS

IQ AND INTERSEST FINDING SYSTEM