Documente Academic
Documente Profesional
Documente Cultură
Undertaken by:
MATEEN ASGHAR
CIIT/FA15-BS(SE)-014/WAH
USMAN KHALID
CIIT/FA15-BS(SE)-015/WAH
Supervised by:
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 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.
ii
PROJECT BRIEF
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
vii
LIST OF TABLES
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.
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.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.
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.
SYSTEM DESIGN
IQ AND INTERSEST FINDING SYSTEM
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.4.2 GUI
The Graphical User Design of our web applications are as follows.
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.
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.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.
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.
Comment IQ measured
Accuracy 100
33