ISARS Finale Report

i
ABSTRACT
This is a final year project report which is named as “Intelligent Student Admission
Recommendation System”. The goal of the document is to facilitate the reader with the thorough
description of the project in every aspect. The main part of this report includes Introduction, Idea
and Problem definition, Requirements gathering, Design and Implementations details and testing
details.
We have followed various research papers to develop this system. We have merged the
techniques and algorithms which are described in the research papers. We are developing this
project on Notepad++ & Visual Studio, a platform to code in Php & C# respectively. We are
developing an Educational based website that can help students to match the achieved scores
with various other ranked universities and also helps them to select path for their career. This
Project also includes web services having server in Php language and Client end in C#. Apart
from this student will be notified by email subscription and will see Top focused Trends as well.
ii
Table of Contents
1 Introduction to report.........................................................................................................................1
1.1 Existing System............................................................................................................................2
1.2 Literature Review.........................................................................................................................3
1.2.1 Research paper no1:............................................................................................................3
1.2.1.1 Abstract...............................................................................................................................3
1.2.2 Research paper no2:............................................................................................................4
1.2.3 Bench Marking:....................................................................................................................5
1.3 Problem definition.......................................................................................................................6
1.4 Deliverables and Development Requirements............................................................................6
1.4.1 Development Requirement.................................................................................................7
1.5 Context diagram..........................................................................................................................8
1.6 User Needs..................................................................................................................................8
2 Introduction.......................................................................................................................................10
2.1.1 Project Phases....................................................................................................................10
2.1.2 Requirement Engineering:.................................................................................................10
2.1.3 Object Oriented Analysis and Design:................................................................................11
2.1.4 Planning:............................................................................................................................11
2.1.5 Development:....................................................................................................................11
2.1.6 Software Quality Assurance and Testing:...........................................................................11
2.1.7 Project Management:........................................................................................................12
2.1.8 Integration:........................................................................................................................12
2.2 Project background or overview................................................................................................13
2.3 Problem description..................................................................................................................14
2.4 Project objectives......................................................................................................................15
2.5 Project scope.............................................................................................................................15
2.6 Product or project features.......................................................................................................16
2.6.1 Users and Characteristics...................................................................................................17
2.7 Use case diagram.......................................................................................................................18
3 Introduction.......................................................................................................................................19
3.1 Functional requirements or Full dress use cases.......................................................................19
iii
3.1.1 Functional Requirement 1 .................................................................................................19
3.1.2 Functional Requirement 2..................................................................................................23
3.1.3 Functional Requirement 3 (Admin)....................................................................................26
3.1.4 Fully Dressed Use-Case......................................................................................................27
3.2 System sequence diagram.........................................................................................................36
.............................................................................37
3.3.1 ...................................................................................................................37
3.3.2 Admin area:.......................................................................................................................38
3.3.3 :..........................................................................................................................................39
3.3.4 ...........................................................................................................................................39
:..........................................................................................................................................40
3.3.6 Sign in or Register..............................................................................................................41
3.3.7 ...........................................................................................................................................42
3.3.8 View Profile........................................................................................................................43
3.3.9 ISARS Logo.........................................................................................................................44
3.4 Data model (ERD).......................................................................................................................44
3.5 Activity diagram.........................................................................................................................45
3.6 State transition diagram............................................................................................................46
3.7 Non-functional Requirements...................................................................................................46
3.7.1 Performance requirements................................................................................................47
3.7.2 Security requirements.......................................................................................................47
4 Introduction.......................................................................................................................................48
4.1.1 4+1 View............................................................................................................................48
4.1.2 Block Diagram....................................................................................................................49
42 Design Methodology..................................................................................................................50
43 High Level design.......................................................................................................................50
44 Package diagram........................................................................................................................51
45 Detail design sequence Diagram................................................................................................51
46 Class diagram.............................................................................................................................52
47 Deployment diagram.................................................................................................................53
5 Introduction.......................................................................................................................................54
5.1 Test design.................................................................................................................................54
5.1.1 White-box Test cases.........................................................................................................54
iv
5.1.2 Black box Test Cases..........................................................................................................61
5.1.3 UI test cases.....................................................................................................................117
5.1.4 Other NFR Test Cases.......................................................................................................123
5.1.5 Acceptance test cases......................................................................................................127
5.2 Bug Sheet.................................................................................................................................128
5.3 Test Report..............................................................................................................................129
6 Introduction.....................................................................................................................................130
6.1 Conclusion...............................................................................................................................130
6.1.1 Practical Implementation methodology...........................................................................130
6.2 Future Work.............................................................................................................................131
6.3 Appendix..................................................................................................................................133
6.3.1 Data Dictionary................................................................................................................133
6.3.2 Bibliography.....................................................................................................................134
v
Chapter 1
INTRODUCTION
1 Introduction to Report
This report gives an overview about our project “ISARS”. The opening section of our project
report includes an overview of our project and its description. We have described the problem
that lead us towards this project. The problem was that users had to face difficulty while finding
different university eligible criteria because of scattered information on different websites. We
have tried to overcome this problem by creating a new Website. The middle section contains
details about the design, functionality of the product and the expected and actual deliverables of
the system. We have made our report effective by adding different diagrams which help a lay
man in understanding our project more easily and accurately. We have added user interface,
logo, design and architecture of our project in this report. In the last part of this report we have
provided conclusion including the benefits and limitations of our project along with some
innovative features of our project.
Nowadays students are more concerned for their future paths and waste their most of the time to
check the scattered eligibility criteria of universities. The goal of the project is to develop a
website that provides its users a better and easy platform to check eligibility and help them to
decide for their future career decision. This report presents the designs for the ISARS, which
includes the following components: Match Eligibility Criteria, Recommendation/Guide, Web
service, Trends Display, and subscription. A description of the design and an analysis of
efficiency for ISARS is given in the report.
1
“”Chapter 1: INTRODUCTION”””
This document will help the stakeholders to understand and develop a high quality and desired
product. It will provide an elaborated description of the features of the ISARS. It will cover
every system functionality alongside offering a basic idea of the developed ISARS’s UI (User
Interface). The software, hardware, and several other technical dependencies of the produced
system will also be gathered in this paper. It will also specify and help to analyze all the assorted
ideas that came up during the development of the said system.
1.1 Existing System
User
Open
Website
Check
Admission detail Result
Educational Scattered
Content (N/A Detail)
Figure 1.1: Existing system
2
The existing websites do not meet up the user’s requirements and lack the facility of
automatically matching criteria of universities. Users have to check for every University website
specifically, related to their departments. Sometimes users do not get notified about the updated
schedule or new admissions. Existed Systems also failed to provide Career guidance which is
important for students nowadays. They also do not have the ease of e-mail notification as well as
Present Focused Trends. There are increased spam emails which often offend the users. One
more addition in ISARS of ‘web services’ that allows third party to get facilitate. Advantages of
web service are discussed in coming sections below.
1.2 Literature Review

During the project development we reviewed some relevant research articles and books which
are as mentioned below:
1.2.1 Research paper no1:
A RESEARCH ON THE EDUCATIONAL COUNSELING AND CAREER GUIDANCE
1.2.1.1 Abstract:
In these times the young individuals require some sort of counseling and the guidance in order to
identify the abilities for their future. Counseling and guidance for career should be made
permanent from the primary and secondary phases of education. With the constant and reformed
educational system which does not consider the need of counseling and the vocational guidance
from the scholars, the Romanian educational infrastructure causes major impact. But the lack of
the counseling in the pre university phase of education identifies the increased rate of cluttering
of the potential individuals in selecting the institution that they want the degree from. The aim of
3
the paper is to highlight the outcome of the sociological research carried out in the areas of
Romania on the 900 students.
1.2.2 Research paper no2:
An automated system to match scientific students with their appropriate career pathway.
1.2.2.1 Abstract:
Selecting the most feasible arena is the critical action that has a great influence on one’s future.
In the same time, the simulation is carried out through an unreliable procedure in the country.
Generally, a student chooses a provided pathway while neglecting his personal interest and
skills. The cause is because affectation is done on the grounds of achieved score. With the higher
GPA, the chance is higher to choose the desired pathway. Due to this penalizing the students are
led to the missing of their careers. For this reason, we suggested a reliable model that will
provide the student with career guidance. Generalizing in abstract manner, this model will allow
the student of any age to obtain the career guidance.
1.2.3 Bench Marking:
System Ilmkidunya. Kitab.co Eduvision.edu. Ilm.com. ISAR

pk m pk pk S
Features
Match Criteria
    
Services
    
4
Recommendati
on
    
Trends
    
Subscription
    
Table 1.1: Bench Marking
1.3 Problem definition
Normally there are so many websites to be seen on the internet having no complete information of
any of the ranked university or related on any educational content because of which the
students/users then get disappointed. Number of websites guiding or providing wrong information of
same organization and the concerning user has no idea that exactly on which information exactly he
should believe. Main issue of today’s Educational Website is that they go through a long process of
finding the concerned topic/paths. This procedure was so hectic and confused to find eligibility
criteria of certain university. In order to avoid such complexity, the student usually conduct the
survey manually by having a visit of the universities. Concluding as, the existing system does not
facilitate with the feature of matching eligibility criteria can save huge amount of students’ time.
1.4 Deliverables and Development Requirements
 The drowse department, login, registration and check trends, match criteria, check career,
criteria and notifications are among the deliverables associated with student module.
 The deliverables related to third party module includes the check WSDL, check operation
and consume.
5
 The deliverables related to admin module includes the insert or update criteria, mail
management, and the Viewing Contacts.
1.4.1 “Development Requirement”
 The required Operating System is Windows.
 The application requirements include web browser, My SQL, Xampp, and a notepad++.
 A laptop and internet conectivity is required as hardware.
1.5 “ ”
1.6 “ ”
The most important resource for the students is an internet. Based on the performed research in
the regions of Romania to recognize the necessity of counseling it is required to know how
6
precious is time. In order to find and tally the obtained results of a student is quite a time taking
process which also ends up with inaccuracy in the gained information. Therefore, to resolve this
issue the platform named ISARS is recommended that promises to save the time of user and
facilitate the user with an easiest method of criteria matching with various ranked universities
and institutions.
7
“Chapter 2”
“INTRODUCTION TO PROPOSED SYSTEM ”
2 Introduction
“ ”
An outline of the project's phases, the system's history, and its operating environment are given in this
chapter. The learning includes the concepts about web development, webservices and regex
operations. The implementation of the project is through XAMPP and the visual studio. The
features of the system include matching criteria with universities, scrapping criteria from
universities. The major focus is on the individual who are facing the difficulty while searching
the right fit for their career.
Being a recommendation system, the suggested system makes sense. The project is an
educational website called "Intelligent Student Admission Recommendation System," and it is
web-based. It gives users/students the ability to search for the best university department to apply
to online by simultaneously verifying their eligibility with many departments. Our website is
able to register the users online. It recommends students to the best career decision for future.
Users will be facilitated by providing subscription. The student can easily check the focused area
of education/department in present days. The addition in our system is “Web Services”, which
makes it capable to interact with other websites by giving language independency.
2.1.1 Project Phases
Following are some phases included in our project:
2.1.2 Requirement Engineering:
10
“” Chapter 2: INTRODUCTION TO PROPOSED SYSTEM ””
In this phase the project requirements are elicited through critical thinking and build SRS based
on those specifications. This phase always plays a key role in every project by providing various
types of elicitation techniques prototyping, storyboarding through Analytic Models and through
Questionnaires.
2.1.3 Object Oriented Analysis and Design :

“ ”
UML and Visual Paradigm are used to model the system in the following phase.
2.1.4 Planning:
During this phase, we have decided the scope of our project and had detailed meetings with our
supervisor to finalize the features of our project. Through our literature review we had analyzed
that many applications were providing some of the features that we have included in our project
namely; ISARS, but our system is providing an everlasting solution for Eligibility Criteria and
lack of decisions for career. Friendly user interface will be provided for better interaction with
the system. This system will also maintain secrecy of its users.
2.1.5 Development:
In this phase we have decided the tools on which we developed our product. We decide the
programming languages for designing and coding of our product. Anyone having a computer and
an internet connection can use our application. Major tools used for development were Notepad+
+, Php My Admin (Website) and Visual Studio C# (Web Services).
2.1.6 Software Quality Assurance and Testing:
11
In this phase the teste cases are developed along with identification of test scenarios. Various
tools and techniques of software testing like Yslow, Selenium IDE, Black box testing and white
box texting ar adopted for testing.
2.1.7 Project Management:

“ ”
Various project management strategies are employed to tackle the difficulties associated to
project management during this phase. Additionally, we created a project charter, a project
matrix, Gantt charts, and a list of all the development tasks that would aid in resource estimation
throughout the project.
2.1.8 Integration:
In this phase we had integrated all the work done by our supervisor assigned to each of the group
member and all the work was then merged to make it a final product.
12
Figure 2.2: Block Diagram
2.2 Project Background or Overview
IlMkidunya.com and various popular websites were built in 2009-2011.They came up with the
roughly idea, then they started providing educational content which was not accurate too. They
have started to provide information about Universities, Scholarships and other different
categories. After the days past, now it is still difficult to find any specific topic due to scattered
information on web. They haven’t provided any module which give the best output and consume
less time of user.
“ISARS” is a web-based application that will help user to find a best path for career that
matches their skills and on the other hand it will also match the student criteria directly with the
eligibility criteria of different universities which is also accurate. This will further focus helping
each one of user to find best online matching criteria skills through this website. In addition, it
will work as a server and provide the language independency through web service. This system
will maintain the secrecy of its users as it uses the latest security algorithms. ISARS will also
help the users to view best department focused in present time by our Top Trends Bar.
2.3 Problem Description
Normally there are so many educational websites to be seen on the internet having no specific
and accurate information because of which the student/user get disappointed. The number of
websites giving the wrong eligible criteria which leads the student to miss the opportunity. The
websites are not been properly updated in their concerned way so that a person using that
information for any purpose can lead them for a wrong decision in future. Main problem for
student nowadays that they have to search a lot for a content or eligible criteria that also take
13
time but still comes up with wrong old data. In order to circumvent this intricacy, a student
would rather complete this task by hand, visiting several universities and verifying whether the
chosen department is accessible, as well as what the requirements are, before submitting an
application. This is long procedure, hectic and time taking.
2.4 Project Objectives
The main purpose of designing this Website named as ISARS is to give the user/student a stage
for finding a right and an agreed eligibility criteria of different universities in a minimum period
of time at once. It also introduces career path to choose best for their future guidance/decisions
according to their qualification and interest. It also provides the Web services for any third party
which can interact with this system having language independency. The graphical representation
will show the trending departments. The basic purpose of the website is to give a best experience
to the user to check his percentage with eligibility criteria against different ranked universities at
once.
2.5 Project Scope
The key goal is to give the user/student a raised area for finding a right and a reasonable
department of university in a minimum period of time according to their percentage. It also
introduces latest scrapped eligible criteria to the users according to their requirements and marks
which consume less amount of time. It will work automatically like a student provides his marks
in percentage and system will match his criteria against the departments of all university(scraped
by system) and display the result followed by a message that whether he is eligible or not.
 No duplication of Criteria.
 Easy way of checking
14
 No wastage of time
 Scraped Criteria from multiple universities
 Works automatically
 Accurate matching
 Show Career Path
 Allow interaction through Web service
 Trend bar showing the latest Focused area.
2.6 Product or Project features
The feature list of ISARS is listed as follows:
 Extraction of Eligibility Criteria:
It will scrap eligibility criteria from top ranked universities websites (data extraction)
using a Regex with 85% accuracy.
 Matching User Percentage with Eligibility of University:
Shows the department in which user is eligible to apply.
 Representation of Result:
Extracted criteria and matching result are represented in a proper visual format. It
includes Trends as well.
 Career Guidance:
Takes input in the form of questions and show them the focused or more likely/interested
area according to their answers.
 Web Service:
Allows other websites to interact with it.
15
No language dependency.
 subscription email:
An automatic email will be generated and sent to the users who subscribed on system.
 Trends:
Most focused department having popular hits will be showed in trends bar followed by
others having less.
2.6.1 Users and Characteristics
The users that interact with the ISARS are as following:
Any User Interaction with system
Students Students will login to our system and
checks the Eligibility Criteria.
Any website which will interact with
Third Party/Website ISARS system through web services.
Admin Manage Website including web service
area.
Table 2.2: Users
16
It is expected that every individual on the above list is familiar with computers and
internet browsing on a basic level. Additionally, each member requires a valid email
address that they may use to sign up for accounts on the website.
2.7 Use case diagram

“ ”
Figure 2.3: Use-Case Diagram
17
Chapter 3: REQUIREMENT SPECIFICATION OR BEHAVIORAL REQUIREMENTS
3 Introduction
We are developing a website that will provide a complete service to user/student. Our website
will help the user to match his criteria against different ranked universities and suggest him best
career path by choosing right domain as well. Moreover, it would provide services by which any
third party or website can interact by consuming in any language called web service.
3.1 Functional requirements or Full dress use cases
3.1.1 Functional Requirement 1 (student/user)

Requirement ID R1.01.01
Title Registration
Description The student will see a registration form after clicking the
"register now" option if he want to register for the Intelligent
Student Admission Recommendation System (ISARS). Once
the user has filled out the registration form completely,
meaning that all fields indicated with a '*' must be filled in,
they must click the submit button to complete the form.
Title Login
19
Description Only those who have registered are able to use the application.
The user must input their login information in the
designated username and password sections in order to
access the system. After clicking the login button and
confirming that their ID and password are valid, the user is
granted access to the programme and their profile is shown.
Title Edit Profile
Description Student will edit his profile.
Title Form Submission
Description To check eligibility criteria of multiple universities student has
to fill and submit form. He/she will click the form and will
provide the information regarding his/her previous standard
marks respectively and submit the form by clicking on submit
button.
Title Check Criteria
20
Description After providing the information in form, student will click the
submit button and result will be shown to him/her in which
he/she is eligible or not. Moreover, students have option for
medical criteria as well. Based on previous information which
he/she submitted in the form.
Title Level / Grade Suggestion
Description Students will be provided by a short questionnaire to fill. Thev
system will calculate and show results about user’s interest and
suggest him/her for better future decision.
Title Notification by email
Description If student subscribe, he/she will be notified for useful
information by Email.
Title ISARS WSDL
Description Users who wants to interact or get the ISARS services they can
get WSDL file by checking into the web service area.
Language independency makes it easy to consume the service
in any language.
21
Title Display Trends
Description This makes it easy for user to check latest more focused
area/department of university.
3.1.2 Functional Requirement 2 (Admin)
Title Manage Pages
Description Admin will manages pages of ISARS as per requirement.
Title Insert/Update data
Description Admin will insert or update the Eligibility criteria which has
been scraped from the website. One Button Click process.
Title Send Mails
Description Admin will send mails to registered user.
3.1.3 Fully Dressed Use-Case
3.1.3.1 Use Case UC1: Register User

“
Diagram: ”
22
Register User
User
Figure 3.4: Use Case UC1: Register User
Primary Actor: student
Secondary Actor:
Stakeholders and Interests:
Student: register by providing his credentials.
Preconditions: Internet and website must be in working condition.
Brief Description
Student will be able to register in ISARS.
3.1.3.2 Use Case UC2: Login User

“ ”
Diagram:
Login User
User
Figure 3.5: Use Case UC2: Login User
23
Primary Actor: User
Secondary Actor:
User: login by providing his credentials.
Preconditions:
Brief Description:
User access to the ISARS will be possible.
3.1.3.3 Use Case UC3: Match Criteria

Diagram:
Match Criteria
User
Crone Figure 3.6: Use Case UC3: Match Criteria
Primary Actor: user
User: match criteria by submitting Form.
Preconditions: User must be logged in before using this module.
Brief Description:
24
There will be a form to fill by user. After submitting form system will show the result matching
user’s Criteria.
3.1.3.4 Use Case UC4: Send Mails

Diagram:
Send Mails
Admin
Figure 3.7: Use Case UC4: Send Mails
Primary Actor: Admin
Admin will send mails to registered user. One button click process.
Preconditions: Before sending mails the admin must login.
Brief Description: an option will be available for selecting multiple users whom to send mails to
notify. Separately send option is available.
3.1.3.5 Use Case UC5: Insert/update Data
Diagram:
Insert / update
data
25
Admin
Primary Actor: admin
Admin: Admin will insert and update data/criteria which has been scraped from other websites.
Preconditions: Admin must be logged in.
Brief Description:
Admin will insert and update criteria to website.
3.1.3.6 Use Case UC6: Edit profile

“
Diagram: ”
Edit Profile
User
Figure 3.9: Use Case UC6: Edit profile
Preconditions: The user needs to be logged in.
Brief Description:
Users could update their profiles including passwords.
26
3.1.3.7 Use Case UC7: Suggest Future levels/Grades.

Diagram:
User: are suggested by system for further degree/grades/Fields which helps him/her to decide
better.
Preconditions: users login is necessary.
Brief Description:
A questionnaire is given when user visits the suggestion page. Once the form is filled out, the
system will provide a percentage to indicate the user's level of proficiency in particular field.
3.1.3.8
Display Trends
27
Figure 3.10: Use Case UC8: Display Trends

The top Focused area by recent users will be displayed on a Trend Bar that the user may observe .
3.1.3.9 Use Case UC9: Subscribe User

Diagram:
Subscribe User
User
Figure 3.11: Use Case UC9: Subscribe User
3.1.3.10
diagram:
View WSDL
third part /
website
28
Figure 3.12: Use Case UC10: View WSDL
29
3.2
Figure 3.11 System Sequence Diagram
30
3.3 “
3.3.1
31
Figure 3.12.b: Home Screen Client
3.3.2 Admin area:
Figure 3.13: Admin area
32
Figure 3.14: Admin area
3.3.3 Match Criteria:
Figure 3.15.a: Match Criteria
33
Figure 3.15.b: Match Criteria
Match Criteria (Web Service Client):-
34
Figure 3.15.c: Match Criteria
3.3.4 Recommendation
Figure 3.16: Recommendation
35
3.3.5 Web Service Area:
Figure 3.17.a: Web Service Area
Figure 3.17.b: Web Service area
36
Figure 3.17.c: Web service area
Figure 3.17.d: WSDL File
37
3.3.6 Sign in or Register
Figure 3.18.a: Sign in or Register
Figure 3.18.b: Sign in or Register
38
3.3.7 Website Logo
Figure 3.19: ISARS Logo
39
3.4 Data model (ERD)
Figure 3.20 ERD
40
3.5 Activity diagram
Figure 3.21 Activity Diagram
41
3.6 State transition diagram
Figure 3.22 State Transition Diagram
3.7 Non-functional requirements
 Interoperability
o The interfaces of ISARS must be completely understood to work with other products or
system at present or future in either implementation or access, without any restrictions.
 Usability
42
o The user must be able to use the ISARS with no training.
o The application must be organized in such a manner that it is both visually appealing and
provides great ease to the user to search and navigate.
o It must conform the Neilson, Schneider and ISO usability standard design rules.
 Availability
o ISARS must be available with 24/7/365 format.
 Maintainability
o The system will be implemented using object oriented paradigm that will help
development team in maintaining the system and its specific applications. In specification
portion, use case are shown so that any developer can maintain this project but they need
actual code.
 Reliability
o The system must perform its functions consistently without failure. The system must be
fault-tolerant.
3.7.1 Performance Requirements
 ISARS should load and respond in <3 seconds.
 ISARS must be available with 24/7/365 format.
3.7.2 Security Requirements
 This programme is designed to be safe for all users, since no one will be able to view a
user's profile without first logging in if a user logs out of a session.
43
 The student is ensured with no amendment of his/her data and no one else can access
anyone’s information because the student who logged into system is provided with a user
name and password.
 Scalability
The capabilities of the system must be expanded and upgraded easily in the future.
44
Chapter 4
Design Specifications
4 Introduction
“ ”
The ISARS design specifications are included in this section. It outlines the concept of ISARS
and its implementation strategy. The ISARS presumptions and constraints are also covered. UML
diagrams are created to help users comprehend the system.
System Architect
4.1.1 4+1 View

4+1 view model of this system allows to address the concerns of stakeholders separately such as
end user, developers, system engineers, and the project managers. The product will be explained
in each of the five views.
Figure 4.13: 4+1 view
4.1.2 Block Diagram
45
Chapter 4: DESIGN SPECIFICATION
Currently the workflow is that the User and Admin would be allowed to login into our system.
Admin can insert and update eligibility criteria by simply clicking Insert or update button, in
response Scraper will be executed again and extract the latest eligibility Criteria. That’s how our
system keeps data updated. Here all the data is gathered and assembled by Scraper in which
Regex filters/grab the useful data from extracted material. After all the data is updated next user
can match criteria by submitting his marks on given form then system will match. Similarly,
Trend bar will be shown to user which will have more focused area. And recommendation as
well. Where user will be suggested to choose field depending on their interest.
Figure 4.14: Block diagram
4.2 Design Methodology
46
This system will be restricted in the following ways:
1. User must know the English language, as the Website will be available only in English.
2. User have to register before using our recommendation and Eligibility Modules.
3. No one, except the admin, can manage the ISARS unless admin give responsibility.
4. Our Web service can be used/consumed by any user any language. No Restrictions.
5. Any computer with an internet connection and internet browsing skills can be used to
access ISARS by the user.
4.3 High Level Design
Web Scraper
Browser
I.S.A.R.S University
Websites
Local Host Database
Figure 4.15: High level design
47
4.4 Detail Design Sequence Diagram
Figure 4.4 Sequence Diagram
4.5 Class diagram
48
Figure 4.5 Class Diagram
4.6 Deployment diagram
Figure 4.6 Deployment Diagram
49
Chapter 5
Test Specification
5 Introduction
5.1 Test design
5.1.1 White-box test Cases

One method of verifying the system's internal functioning is called "white-box" testing.
50
Chapter 6: CONCLUSION
5.1.1.1 Web Service Method
Figure 5.16 Web service method
Test Input D1 D2 D3 D4 D5 Output

Case $uni $dept. $matric $inter
TC-01 Quaid-e- CS 80% 75% T T F F T All loops run

Azam successfully and
eligible for admission
TC-02 Comsats EE 59% 45% T T T F F All loops run
successfully but not
eligible for admission.
TC-03 FAST Pre- 70% 69% F F F F F No loops ran because
medical dept. entered is
invalid.
TC-04 CUST CS 80% 70% F F F F F No loops ran because
University name is
invalid
TC-05 SZABIST BBA 70% 39% T T F T T All loops run
successfully but not
eligible for admission
51
Table 5.3: web Service Table
CFG:
Figure 5.17: CFG
52
5.1.1.2 Criteria Matching Algorithm
Figure 5.18 Criteria Matching Algorithm
Test Input D1 D D3 D4 Output

Case $uni $dept. $matric 2
$inter
TC- Quaid- cs 60% 40% T T T T All loops run
01 e- successfully
Azam
TC- Quaid- ca 60% 40% F F F F No loops run because
02 e- dept. entered is invalid
Azam
TC- Quaid- bba 60% 35% T T T F All loops run
03 e- successfully but not
Azam eligible for admission
53
TC- UET ee 60% 40% F T T T No loops run because

04 uni name is invalid.
Table 5.4: Extract all information from document or pdf
CFG:
10
Figure 5.19: CFG
54
5.1.1.3 Recommendation (Bachelors Result)
Figure 5.20 PDF or Document to String
Test Case Input D1 D2 D3 Output

$ans
TC-01 right T T F Loop run successfully and ans is right
TC-02 wrong T F F Loop run successfully but else

condition executed and ans is wrong.
TC-03 no_answer T F T Loop run successfully and output is

no_answer.
TC-04 Null - - - No loops ran
55
Table 5.5: bachelors Answer
CFG:
Figure 5.6: CFG
56
5.1.1.4 Recommendation (Masters Answer)
Figure 5.21 Master Answers
Test Case Input D1 D2 D3 Output

$ans
TC-01 right T T F Loop run successfully and ans is right
TC-02 wrong T F F Loop run successfully but else

condition executed and ans is wrong.
TC-03 no_answer T F T Loop run successfully and output is

no_answer.
TC-04 Null - - - No loops ran
Table 5.6: Master Answers
57
CFG:
Figure 5.8: CFG
5.1.2 Black box test cases

“ ”
58
5.1.2.1 Use Case Diagram
Figure 5.9 Use case diagram
5.1.2.2 Domain Model Diagram
Figure 5.10 Domain Model Diagram
Domain Model
59
5.1.2.3 Test Cases for fully dressed UC-01 Login User
UC-01 Description
Description: To enter the system so that the user can check eligibility criteria and get
recommendations from system and can view trends as well.
Actor(s) : User / Student
Pre-Condition: User must be registered.
Post-Condition: Home screen appears. For the specified user.
Main Success
Scenario :
Data Captured: Login Account details
Common Details: Login credentials required.
User Name: User name of the registered account.
Password: Password
Exceptional None
Flow(s) :
60
Alternate
Flow(s):
External None
System
Dependencies:
Table 5.7: Test Cases for fully dressed UC-01 Login User
5.1.2.3.1 Flow Chart UC-01
Figure 5.11: Flow Chart UC-01
5.1.2.3.2 Sequence Diagram UC-01
61
Figure 5.12: Sequence Diagram UC-01
5.1.2.3.3 Basic Flow UC-01
B1: User (Student) opens login screen
B2: Login in account by providing Necessary information
B3:Verify information
B4:Show home screen for the specified user
Table 5.8: Basic Flow UC-01
5.1.2.3.4 Alternative Flow UC-01
Sr. No Alternative Flows
A1 Invalid information
A2 Incorrect input
62
Table 5.9: Alternative Flow UC-01
5.1.2.3.5
A1
B1 A2
5.1.2.3.6
01
TCUC01-01
For login into the system
None
User Action System Response
 User (Student) opens  Verify information
login screen  Show home screen for the
 Login in account by specified user
providing Necessary
information
Expected Output Successful login

Actual Output Logged In Successfully
Post-Condition(s) Go to the Index page after login
Author Ahsan Altaf
Execution History
63
June 3, 2018 Ahsan Altaf
5.1.2.3.7
02
TCUC01-02
For login into the system
None
 User (Student) opens  Invalid Information
login screen
 Login in account by
providing Necessary
information
Expected Output Invalid Information

Actual Output Invalid Information
Post-Condition(s) Stay on Login Page
Author Ahsan Altaf
Execution History Date Result Version Run By
June 3,2018 Ahsan Altaf
5.1.2.3.8
03
TCUC01-03
To login into the system
N/A
System Response
 Administrator/User opens  Incorrect Input
login screen
 Login in account by providing
Necessary information
Expected Output Incorrect Input

Actual Output Incorrect Input
Post-Condition(s) Stay on Login Page
Author Ahsan Altaf
Execution History
64
5.1.2.4
User / Student could match his Criteria with eligibility of

different universities at 1 time.
Actor(s) : User (Student).
Pre-Condition : User must be login first.
Post-Condition Criteria must be available in the database.

:
Main Success User go to the login page and login first

Then user will go to eligibility page where he will provide his
Scenario :
marks in given form and System will show the Result of
matched Criteria.
System displays Matched Criteria result.
Data Captured: Match the criteria
Common Details: Marks required and must be login.
User Name: User name and password of the registered account.
Exceptional None
Flow(s) :
65
Alternate System rejects the user's request if he put the wrong marks.
Flow(s):
None
Start
Submit Marks
No
Valid
Marks
Yes
Match Criteria
Display Result
66
End
5.1.2.4.2
5.1.2.4.3
B 1: login first
B 2: Check Eligibility
B 3: Submit Marks / Form.
B 4: Get Matched Criteria Result
5.1.2.4.4
Invalid Marks Message
67
5.1.2.4.5
5.1.2.4.6
01
TCUC02-01
Match Criteria
None
 Login First  System matched the Criteria
 Check eligibility  Show Results
 Submit Marks  Show successfully message
Expected Output Successful Checked

Actual Output Successfully checked
Post-Condition(s) Show Message of success
Author Ahsan Altaf
5.1.2.4.7
02
TCUC02-02
Match Criteria
None
68
 Login First  Invalid Input

 Check eligibility
 Submit Marks
Expected Output Show Message for wrong Input

Actual Output Message for wrong Input
Post-Condition(s) Stay on same page. No Need to login again.
Author Ahsan Altaf
Execution History
June 3 , 2018 Ahsan Altaf
5.1.2.5
Description
To enter the system so that the user can successfully register to

the system
Actor(s) : User.
Pre-Condition : None
Post-Condition Home screen appears.

:
Main Success User enters required detail.

Scenario :
System validates the information.
System creates a User account with above details and user is

registered.
System displays success Registered message.
69
Data Captured: Registration details
Common Details:
Email: Email to Register account.
Password: Password
Exceptional None
Flow(s) :
Alternate In the event that the user submits an invalid request, the system
Flow(s): rejects it and displays the relevant error message.
External None
None
Start
Request for
registration
70
Show registration
page
Figure 5.14 Flow Chart UC-03
71
5.1.2.5.2
B1: User opens Registration screen
B2: Register an account by providing Necessary information
B3: Verify information
B4: Display Success message
5.1.2.5.4
Invalid information
A2 Already Registered
72
5.1.2.5.5
A1
A2
Table 5.11: All Scenarios UC-02
5.1.2.5.6
01
TCUC03-01
For Registration
None
 User opens Registration  verify information
screen
 User Registered
 Register an account by
providing Necessary
information
Expected Output Successful Registered
Actual Output Successfully Registered
Post-Condition(s) Show Message after registration
Author Ahsan Altaf
73
5.1.2.5.7 Test Case 07UC-03
02
TCUC03-02
For Registration
None
 User opens Registration  Invalid information
screen
providing Necessary
information
Expected Output Invalid information
Actual Output Invalid information
Author Ahsan Altaf
5.1.2.5.8 Test Case 08 UC-03
03
TCUC03-03
For Registration of account
None
 User opens Registration  Already Registered
screen
providing Necessary
information
Expected Output Already Registered
Actual Output No error message
Author Ahsan Altaf
74
5.1.2.6
UC-04
To Check recommendation in which fields user wants to

proceed his career.
Actor(s) : User / Student
Pre-Condition : User must be logged in.
Post-Condition User will get recommended by system in particular field.

:
Main Success User checks for recommendation.

Scenario :
User select Grade / Level.
User submit Questionnaire.
System will Check the Result and Recommend Field depending

on system criteria.
System displays success message.
Data Captured: Questionnaire
Exceptional None
Flow(s) :
Alternate System fails to open the Questionnaire when user not selecting
Flow(s): category / grade / level.
System will display an appropriate error message when User

Check Recommendation without selecting Category.
75
None
Start
User No
Logged in
Yes
Select Category
Submit Questionnaire
Recommend
user
End
76
5.1.2.6.2
figure 5.16
B 1: User will first login & Go to Recommendation
B 2: Select Category
B 3: Submit Questionnaire
B 4: Display Recommendation Result/Message
5.1.2.6.4
Incorrect Input / Category
A2 Empty Questionnaire
77
5.1.2.6.5 All Scenarios UC-04
A1
B3 A2
5.1.2.6.6
01
TCUC04-01
To Check Recommendations
None
 User will login first  Display recommendation
Message.
 Go to recommendation
 Select category
 Submit Questionnaire
Expected Output Recommendation Message.
Actual Output Message Display successfully
Post-Condition(s) Will able to select another category.
Author Ahsan Altaf
Execution History run by
5.1.2.6.7
78
2
TCUC04-02
Purpose To Check Recommendation
Cross Reference
Pre-Condition None
Scenarios User Action System Response
 User will login first  Wrong Input
 Select Category
Expected Output Error message
Actual Output Error Message
Post-Condition(s) Uploaded cv
Author Ahsan Altaf
Execution History Date
5.1.2.6.8 Test Case 11UC-04
03
TCUC04-03
To check Recommendation
None
 User will login first  Empty Questionnaire
 Select category
 Submit Questionnaire
Expected Output Message Display for Empty.
Actual Output Message Display for Empty.
Post-Condition(s) Go back to Category Selection.
Author Ahsan Altaf
Execution History
June 03, 2018 Ahsan Altaf.
5.1.2.7
79
UC-05 Description
Description: Admin can add or delete different categories or Questions of

recommendations Fields.
Actor(s) : Admin
Pre-Condition : Admin must be logged in.
Post-Condition Categories Or Questions added

:
Main Success Admin will be logged in and then click on add categories or
add Questions.
Scenario :
Data Captured: Add Categories/Questions details
Common Details: Login required.
Exceptional None
Flow(s) :
Alternate System fails to Add categories

Flow(s):
System rejects the user's request by displaying an appropriate
error message in case there is nothing to add.
None
None
80
5.1.2.7.1
Start
Login
Add categories /
Questions
Categories / Questions
added
End
Figure 5.17: Flow Chart UC-04
81
5.1.2.7.2
figure 5.18 Add Categories / Questions
B 1: Admin will first login
B 2: Go to profile
B 3: Add categories / Questions.
B 4: Display Success message
82
Wrong Format Entered
Scenario 1 B1 B2 B3 B4
Scenario 2 B1 B2 B3 A1
Table 5.13: All Scenarios UC-04
5.1.2.7.5 Test Case 12 UC-05
Test Scenario No. 01

Test Case ID TCUC05-01
Purpose Add Categories / Questions
Cross Reference
Pre-Condition None
Scenarios User Action System Response
 Admin will login first  Display Success message
 Go to profile
 Add Categories /
Questions
Expected Output Category/ Questions Added.
Actual Output Category/Questions Added.
Post-Condition(s) Successfully added Category
Author Ahsan Altaf
83
5.1.2.7.6 Test Case 13 UC-05
5.1.2.8
User will Subscribe by giving his Email Address.
Actor(s) : User
Pre-Condition : Not necessary to be login.
Post-Condition User received the mail.

:
Main Success After visiting site user can subscribe to newsletter to be notified
in future by giving his Email without logging or registering.
Scenario :
84
Data Captured: User Email.
Common Details:
Input: Email.
Exceptional None
Flow(s) :
Alternate System is unable to verify the data

Flow(s): If the user submits a request with an invalid email format, the
system rejects it and displays the relevant error notice.
None
None
Submit Email to
Subscribe
Register Email
85
Successfully Subscribed.
5.1.2.8.2 Sequence Diagram UC-06
Figure 5.19 subscribe user
B1: User request to subscribe
B2: User Enter Email.
B3: Verification.
B4:Display Success message
86
Email Already created
5.1.2.8.6
5.1.2.8.7
02
TCUC06-02
87
Subscribe User
None
 User request to subscribe  Email already created
 Enter Email
Expected Output Email Already Exist
Actual Output Email Already Exist
Post-Condition(s) Email Already Exist
Author Ahsan Altaf
5.1.3
5.1.3.1 Sign In / Register
88
Following below are the UI and Usability test scenarios for the Sign in and Register page.
PROJECT : ISARS
Test Case ID TCUI-01
MODULE : Signup and Register
FUNCTIONAL
SPECIFICATION
: Software Requirement Specification
TEST
OBJECTIVES : Identify the bugs/issues in signup and registration
PREPARED BY : Ahsan Altaf
TIME TAKEN : 10 Minutes
S_NO GUI attributes Result
1 Signup & register header in a proper div. Success
2 Window opens in proper Screen div. when click on sign up. Success
3 Login Window Opens after clicking on Login. Success
89
4 After Sign Up Message displays if some Field Missing. Success
Login and Contact us buttons should be green and work

5 properly Success
6 All text fields should be empty by default Success

Table 5.44: UI and Usability test scenarios
5.1.3.2 Home Page / Index Page
90
Following below are the UI and Usability test scenarios for the home page.
PROJECT : ISARS
MODULE : Index Main page
FUNCTIONAL
SPECIFICATION
TEST
OBJECTIVES : Identify the bugs/issues in Index page
91
1 Logo is placed properly Success
Home, About us, Contact us, Sign In / Register Works

2 Properly Success
Client End Desktop Application should open and Close

3 without crashing. Success
4 Display alert message if not logged in before using modules. Success

5.1.3.3 Check Criteria
92
Following below are the UI and Usability test scenarios for external search page
PROJECT : ISARS
MODULE : Check/Match Criteria
FUNCTIONAL
SPECIFICATION: Software Requirement Specification
TEST
OBJECTIVES : Identify the bugs/issues.
1 Logo is placed properly Success
2 Home, About us, Contact us, Sign In / Register Works Properly Success
3 User must be logged in before using module. Success
4 Requested format for marks input should be mentioned. Success

93
5.1.3.4 Recommendation
Following below are the UI and Usability test scenarios for user profile
PROJECT : ISARS
MODULE : recommendation
FUNCTIONAL
SPECIFICATION
TEST
OBJECTIVES : Identify the bugs/issues.
User profile header with blue Color on Top right Corner with
1 working drop down. Success
2 Right Category should be open when button clicked. Success
3 Both Categories should be in-line. Success
94
4 There should be separate buttons for each field. Success

5.1.4 Other NFR test cases
5.1.4.1 Accuracy testing

Our Scraper runs when admin clicks the Scrap/Insert button and it extract eligibility criteria of given
universities and store into the Database. This process done <5 sec. User also can match the criteria by
giving his marks and system will show the result by matching his marks to scraped eligibility criteria.
And third process done in <2 sec due to our fast Algorithm and it gives more than 90% accuracy.
5.1.4.2 Software Performance Testing

After submitting Questionnaire of recommendation module process takes <5 to show the result. Same
goes for Matching Criteria Module but that will be done in <2 sec due to fast algorithm using.
Email sending performed within 2-4 seconds.
5.1.4.3 Usability Testing
Our system is usable as it is tested by a third party user who uses our system easily without any problem.
We perform usability testing as our all the functionality has been completed and merged with the user
interface.
5.1.4.4 Security Testing
Our ISARS is secure as we have sessions for multiple type of users. No user can access other user’s
account. All accounts are password protected.
Method Result
Authentication Pass
Authorization Pass
Confidentiality
95
Availability Pass
Prevention Direct Access bypass URl Pass
Table 5.48: Security Testing
5.1.4.5 Compatibility testing
5.1.4.5.1 Hardware:
Any hardware will be perfect for our Website and it is a web application as a pc must be more that
Pentium 4 to get better performance.
5.1.4.5.2 Operating Systems:
ISARS can run at any type of operating system windows, Mac or Linux etc.
5.1.4.5.3 Software:
We need a web browser to run our ISARS on local host and a local database is also needed and in this
case we use XAMPP as a local database and Google Chrome as our browser to run our website.
5.1.4.5.4 Network:
We simple need internet connection if we run our website on any server. SSL and HTTPS can also be
used to make our system more secure on internet.
5.1.4.5.5 Browser:
We are using google chrome but ISARS can be accessed from browsers like Mozilla, safari etc.
5.1.4.5.6 Mobile:
Our website can also accessed from any mobile phone having internet connection. And it’s responsive
too.
96
5.1.4.5.7 Versions of the software:
This is the Version 1.2 of our software after multiple revisions and removing of errors.
5.1.4.6 Load testing
Load Testing has been completed by using Chrome extension Yslow. It tells how much time will it took
to load our website. We test the index page for load testing and in the output it gives URL’s, no of HTTP
requests, size of each URL, images, file types etc.
97
5.1.4.7 Installation testing
Verifying the successful installation, upgrading, or removal of software is the goal of installation
testing.
The following variables will influence the kind of installation testing we carry out:
Which operating systems and platforms are supported?
Windows, Mac, Linux or any OS with an internet connection
 Who will perform the software installation?
Complete software is installed by Ahsan Altaf to check whether the installation testing is successful or
not.Our Web-Application is installed in C: /Xampp/htdocs/ISARS which is the location of local host
server.
5.1.4.7.1 Flow Chart of Installation:
Start
Yes
Already
Installed
No
Paste project in the local host
Run with valid URL
Successfully
run?
Yes
Installation Complete
98
Stop
5.1.5 Acceptance Test Cases
For acceptance testing we prefer our co-supervisor whose field is web development. All the test
cases was successful because all the results were matched with the accepted output. This was a
kind of black box testing. All functionalities were matching with initial requirements that were
mentioned in the SRS.
Some of the accepted test cases in black box testing:
Acceptance Testing For ISARS

Test Case Id Test Expected Pass / Retest Comments
Scenario Result Fail Date
TCUC01-01 User Should User logged Pass Success
login
in
successfully
successfully
TCUC02-01 User should User matched Pass Success
match criteria
Criteria successfully
TCUC03-01 User should User Pass Success
register registered
successfully
recommended recommende
d successfully
TCUC05-01 Admin Admin added Pass Success
should add questions /
categories / categories
Questions successfully
successfully
subscribe subscribed
successfully
99
TCUC07-01 User should Trends Pass Success

check trends
successfully
display
TCUC08-01 User should User changed Pass Success
change
password /
password /
name
Name
successfully
Table 5.49: Acceptance test cases
5.2 Bug Sheet
Bug Test Purpose Expected Actual Bug Description Testing Development

ID Case ID Result Result Status Status
BI-01 TCUC01 System Wrong System show Done Complete

-02 shows password or unexpected error
proper no such user in new window
invalid error
result
BI-02 TCUC01 System Wrong A new window Done Complete
-03 shows password or opens with wrong
proper no such user password or no
Incorrect error shown such user exists
input in by system in
same new window
window
BI-03 TCUC02 System Already When user again Done Complete
-02 show applied register his
already message account.
apply in shown in new Registered
same window already.
window
BI-04 TCUC03 System Duplication At the time of Done Complete
-03 must message by registration
shows user system duplication of
already user error is not
exists displayed by the
user.
Table 5.50: Bug Sheet
100
5.3 Test Report
101
Chapter 6
Conclusion
6 Introduction
We developed this product on the basis of the student needs. The database is secured using AES
encryption standards. First of all, ISARS offers its users to check eligibility criteria, then there
will be the option for its users to sign up. When a user wants to match criteria our system will
match the data in database and will show the eligible result. Data saved in our database will be
extracted from the top ranked university websites. Afterwards, once a user is signed up he can
match criteria and get recommendations as well.
6.1 Conclusion
6.1.1 Practical Implementation methodology

“ ”
1. Requirement engineering
We have ascertained the users' requirements at this phase.
2. Object Oriented Analysis and Design
We used object-oriented principles in the development of our system. UML diagrams
have helped us develop the behaviours and structure of our system.
3. Component Testing
We tested the components in various scenarios following the design's successful approval.
Components were tested by the QA team in which developers and users both tested the
components on their behalf.
4. Component Integration
The components were then integrated together, and developed to give the required product.
102
5. Integration Testing
After the components are integrated in the form of a system some integration tests were
performed to see if the system possesses any error or bug.
6. System Deployment and Testing
System deployment will be center of attention because product needs to work simultaneously on
cross platform smoothly in future. In the end system was again tested to make sure of its
functionality and usage at both the developers and users end.
6.2 Future Work

In Future we will launch our website. We are looking to change the Technology as Web
service is gaining attention in all over world and already taken over business. We will
expand our Weber vice area and provide more services. Before expanding Service we will
use NLP to recommendation module and we will use multi-threading for scrapping the
data from different websites as this is the fastest way to scrap data.. We also intend to
develop the android, iOS and windows application for our web application.
103
6.3 Appendix
6.3.1 Data Dictionary
Terms Description
SMTP In cases where email gets delivered via an email client, it uses the
Simple Mail Transfer Protocol (SMTP).
API Protocols, set of routines and tools for the purpose of creating software
applications are called Application programming interface (API).
User An individual who’s using our system.
Admin A person who is controlling the system by other end with different GUI.
WSDL Web Service Description Language.
“ HTML ” A standardised method for tagging text files to create hyperlink effects,
graphics, colours, and fonts on Web sites is called Hypertext Markup
Language.
“ HTTP ” An application protocol for collaborative, distributed, hypermedia

information systems is called the Hypertext Transfer Protocol (HTTP).
The World Wide Web's data transfer infrastructure is built on HTTP.
“ WAN ” A computer network that covers a substantial geographic region is

known as a wide area network. Two or more local area networks
(LANs) often make up a wide area network (WAN).
104
LAN A computer network that covers a comparatively limited region is called

a local-area network (LAN). A local area network (LAN) is often limited to
a single room, building, or collection of buildings; but, radio waves and
phone lines can be used to link a single LAN to another LAN at any
distance.
6.3.2 Bibliography
[1] M. Turland, Architect’s Guide to Web Scraping with PHP, 2014.
[2] K. S. Yesu Raju, A LANGUAGE INDEPENDENT WEB DATA EXTRACTION USING VISION BASED PAGE
SEGMENTATION ALGORITHM, 2015.
[3] J. Ward, PHP Web scrapping, Birmingham,UK: Packt Publishing Ltd, 2014.
[4] J. w. Robert breton, web scraped data, 2016.
[5] P. H. Cording, Algorithms for Web Scraping, Kongens Lyngby, 2011.
[6] M. A. E. D. Marcus P. Zillman, Web Data Extractors, Virtual Private Library , 2016.
[7] T. Flower, Research indices using web scraped data, Geneva, 2016.
[8] P. S. a. S. N. Vasudha Sarda, Relevance Ranking Algorithm for , Mumbai, 2014.
105

ISARS Finale Report

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

ISARS Finale Report

Uploaded by

Copyright:

Available Formats

i

different university eligible criteria because of scattered information on different websites. We

innovative features of our project.

includes the following components: Match Eligibility Criteria, Recommendation/Guide, Web

efficiency for ISARS is given in the report.

ideas that came up during the development of the said system.

1.1 Existing System

Admission detail Result

Figure 1.1: Existing system

web service are discussed in coming sections below.

1.2 Literature Review

are as mentioned below:

1.2.1 Research paper no1:

A RESEARCH ON THE EDUCATIONAL COUNSELING AND CAREER GUIDANCE

Romania on the 900 students.

1.2.2 Research paper no2:

the student of any age to obtain the career guidance.

1.2.3 Bench Marking:

System Ilmkidunya. Kitab.co Eduvision.edu. Ilm.com. ISAR

1.3 Problem definition

1.4 Deliverables and Development Requirements

management, and the Viewing Contacts.

1.4.1 “Development Requirement”

 The required Operating System is Windows.

 A laptop and internet conectivity is required as hardware.

“INTRODUCTION TO PROPOSED SYSTEM ”

the right fit for their career.

educational website called "Intelligent Student Admission Recommendation System," and it is

makes it capable to interact with other websites by giving language independency.

2.1.1 Project Phases

Following are some phases included in our project:

2.1.2 Requirement Engineering:

2.1.3 Object Oriented Analysis and Design :

+, Php My Admin (Website) and Visual Studio C# (Web Services).

2.1.6 Software Quality Assurance and Testing:

box texting ar adopted for testing.

2.1.7 Project Management:

throughout the project.

Figure 2.2: Block Diagram

2.2 Project Background or Overview

less time of user.

2.3 Problem Description

application. This is long procedure, hectic and time taking.

2.4 Project Objectives

2.5 Project Scope

department of university in a minimum period of time according to their percentage. It also

 Easy way of checking

 Scraped Criteria from multiple universities

 Show Career Path

 Allow interaction through Web service

 Trend bar showing the latest Focused area.

2.6 Product or Project features

The feature list of ISARS is listed as follows:

 Extraction of Eligibility Criteria:

using a Regex with 85% accuracy.

 Matching User Percentage with Eligibility of University:

Shows the department in which user is eligible to apply.

includes Trends as well.

area according to their answers.

Allows other websites to interact with it.

others having less.

2.6.1 Users and Characteristics

The users that interact with the ISARS are as following: