Assesmment System - project report

Assessment System
A PROJECT REPORT
Submitted by
ARPIT M. PANDYA (110020107054)
PRAKASH M. PRABHAKAR (110020107051)
VIRAL A. PATEL (110020107058)
In fulfillment for the award of the degree
Of
BACHELOR OF ENGINEERING
In
COMPUTER ENGINEERING
AHMEDABAD INSTITUTE OF TECHNOLOGY
NR. VASANTNAGAR TOWNSHIP, GOTA - OGNAJ ROAD
Gujarat Technological University, Ahmedabad
December 2014

AHMEDABADINSTITUTEOFTECHNOLOGY
CE-ITDEPARTMENT 2014
CERTIFICATE
Date:
This is to certify that the project entitled“ASSESSMENT SYSTEM”has been carried out
by 110020107051, 110020107054, 110020107058 under my guidance in fulfillment of the degree
of Bachelor of Engineering COMPUTER ENGINEERING(7thSemester)of Gujarat
Technological University, Ahmedabad during the academic year 2014-15.
Guide: Head:
Prof. Styadev Vyas
Asst. Prof Sweety Patel Head ofDepartment:
Department ofCE/IT Department ofCE/IT
AIT, Ahmedabad AIT, Ahmedabad

AIT (CE) I
Acknowledgement
No task can be accomplished without proper support, guidance and appraisal.I am highly
thankful to many people who contributeted either directly or indirectly for this project and
provided their invaluable cooperation to us to complete it.
I would like to thank our Head Of Department and also Internal Guide Sweety Patel and our
faculty members of Computer Engineeringfor constantly guiding and showing us the correct
way to reach towards the desired goal.
Then We would like to thank our internal guide Sweety Patel who has helped us out in each
every phase of the project and without their support and guidance the project would not have
been completed successfully.
The wholehearted help and co-operation by our friends is gratefully acknowledged.
ARPIT PANDYA
PRAKASH PRABHAKAR
VIRAL PATEL

AIT (CE) II
Abstract
– ASSESSMENT SYSTEM is a web application where competitive online exams
are generated which is used in companies for placement purpose and also in
colleges. Assessment system mainly features the measurement of the difficulty
level of a question i.e. time consumed by the examiner decide the difficulty level
of the question.
– This site will provide user to check their Skills and how they improve their skills
on the specific topic by giving exams on the basis of our assessment process.
Admin can provide Different type of authority to subadmins to manage the data.
– The Sub-Admin can also add question as per his requirement and conduct the
test. There will be inbuilt question library in the website from which sub-Admin
can generate exams of different categories.
– At the end it will give you an overall graph to User with results showing student
lagging in weak section and leading in strong section.

AIT (CE) III
Appendix 3
LIST OF FIGURES
Figure No Figure Description Page No
Figure 1.1
Figure 2.1
Figure 4.1
Figure 4.2
Figure 4.3
Figure 4.4
Figure 4.5
Figure 4.6
Figure 4.7
Figure 4.8
Figure 4.9
Figure 4.10
Figure 4.11
Hibernate Framework
Incremental Waterfall Model
Use Case Diagram of Admin (Abstract)
Use Case Diagram of Sub-Admin
Use Case Diagram of Student
Class Diagram
Activity Diagram
Activity Diagram of Registration
Activity Diagram of Login
Activity Diagram of Admin
Activity Diagram of Generate Paper
Activity Diagram of View Paper
Activity Diagram of Student
6
7
23
24
25
26
27
27
28
29
30
30
31

AIT (CE) IV
Figure 4.12
Figure 4.13
Figure 4.14
Figure 4.15
Figure 4.16
Figure 4.17
Figure 4.18
Figure 4.19
Figure 4.20
Figure 4.21
Figure 4.22
Activity Diagram of Sub-Admin
Activity Diagram of Forgot Password
Activity Diagram of Change Password
Data Flow Diagram: Level 0
Sequence Diagram for Admin
Sequence Diagram for Sub-Admin
Sequence Diagram for User
32
32
33
37
38
39
40
40
41
41
42
Appendix 4
LIST OF TABLES
Table No Table Description Page No
Table 4.1
Table 4.2
Table 4.3
Table 4.4
Table 4.5
Table 4.6
Table 4.7
Table 4.8
Table 4.9
User
Paper
Section
Student_Exam_Registration
Question_Bank
Exams_Result
Exam_Result
Difficulty_Level
News
34
34
34
35
35
35
36
36
36

AIT (CE) V
Appendix 5
LIST OF NOMENCLATURE
IIS Internet Information Server
JSP Java Server Pages
GUI Graphical User Interface
UML Unified Modeling Language
LOC Line of Code
H/W Hardware
S/W Software

AIT (CE) VI
LIST OF SYMBOLS, ABBREVIATIONS AND NOMENCLATURE
SYMBOLE NAME NOTATION
Class
Top
Package::Class1
Association between classes with end
names
-End1
*
-End2
*
Generalization
Composition Aggregation with multiplicity
* 1

AIT (CE) VII
State
Initial State
Final State
Transition
Object flow ---------------
Decision
Action State
System Boundary
Actor
Use Case

AIT (CE) VIII
Attribute in e-r diagram
Relationship between entities

AIT (CE) IX
TABLE OF CONTENTS
Title Page No:
Acknowledgement I
Abstract II
List of Figures III
List of Tables IV
List of Abbreviations V
Chapter 1 Introduction 1
1.1 Introduction 1
1.2 Project Summary 1
1.3 Scope 1
1.4 Features 2
1.5 Technology Specification 2
1.5.1 Server 2
1.5.2 Client 3
1.5.3 JAVA (Programming Language) 3
1.5.4 JSP (Java Server Pages) 3
1.5.5 Java Servlet 4
1.5.6 Hibernate Framework 4
1.5.7 Eclipse J2EE Toolkit 6
1.5.8 MySQL Back End Database 7

AIT (CE) X
1.5.9 Apache Tomcat Back End Server 7
Chapter 2 Project Management 2
2.1 Process Model 8
2.2 Project Planning 9
2.2.1 Project Development Approach and Justification 9
2.2.2 Project Plan 9
2.2.3 Milestone & Deliverables 9
2.2.4 Roles and Responsibility 10
2.3 Risk Management 10
2.3.1 Risk Identification 11
2.3.2. Risk Analysis 11
2.3.3 Risk Planning 11
Chapter 3 System Requirements
3.1 User Characteristics 13
3.2 Client Side Requirements 13
3.3 Developer side Requirements 14
3.4 Constraints 14
3.4.1 Parallel Operations 14
3.4.2 Reliability Requirements 15

AIT (CE) XI
3.4.3 Safety and Security Consideration 16
3.5 Assumption and Dependence 16
Chapter 4 System Analysis
4.1 Study of Current System 18
4.2 Problem and Weakness of Current System 19
4.3 Requirements of New System 19
4.4 Feasibility Study 20
4.5 Requirements Validation 22
4.6 Functions of System 23
4.6.1 Use Case Diagram 23
4.7 Data Modeling 26
4.7.1 Class Diagram 26
4.7.2 Activity Diagram 27
4.7.3 Data Dictionary 34
4.8 Functional and Behavioral Modeling 37
4.8.1 Data Flow Diagram 37
4.8.2 Sequence Diagram 41
Chapter 5: Implementation, planning and detail
5.1 Implementation Environment 43
5.2 Security Features 44

AIT (CE) XII
45
46
47
48
51
52
Limitation and Future Enhancement
Conclusion
References
Appendix 1:Canvas 1
Appendix 2:Canvas 2
Appendix 3:Canvas 3

TEAM ID: 12625 1: INTRODUCTION
1
AIT (CE)
CHAPTER – 1
INTRODUCTION
1.1 Introduction:
Assessment system is basically a web-site for helping people who wants to conduct exams for
the complete assessment of their examinee. This site allows educators to have access to test
items aligned to the state mandated curriculum to develop assessments that inform Examiner
and Examinee. Admin access allows district administrators to create tests using items that are
in a separate pool than those available to teachers and can be assigned to an entire district by
grade level. Companies can access reports of test that taken by Sub Admin, and can also view
reports. Online exams will be available for the students, GTU collage events, news will be
provided. There will be section of FAQ (Frequently Asked Questions) so that their question /
answer will be solved.
1.2 Project Summary:
"Assessment System” is a website which provide complete assessment of exam. .
Here students and Sub-Admin will be given with a separate username and password. An
accurate report based on the performance of student are Stored here which will be helpful for
company as well as student. To become a Sub-Admin he has to get authority from Admin
once and then Sub-Admin can conduct exam.
1.3 Scope
There are 4 modules in the system:
i)Admin:
The admin performs following tasks:
Admin will manage the questions and also manage the Sub-admin. He will also
perform the tasks like Manages exams, Manages question paper, Manage results, Views

2
AIT (CE)
difficulty level of the question as per the examiners, Manage Students, Provide information
regarding exams.
ii)Sub Admin:
Sub-Admin will manage the exams and also manage the questions and
questions papers. But the sub admin cannot manipulate the data entered by the admin.
iii)User:
They can give the exams. And also can manage their profile and view their results.
iv)Guest:
They can visit the site and are also allowed to give a sample exams and take the over
view of site.
1.4 Features
 This application would have great set of functionalities to users to stay alert of what’s
going outside the world.
 With each question there will be a timer attached to it in back end which will decide
the difficulty level of each question.
 If all student are spending more time on particular question then that question will be
automatically marked as difficult.
 The examiner can also add question as per his requirement and conduct the test.
1.5 Technology Specification
1.5.1 Server
 Tomcat Apache 6.x and Onwards
 MySQL server 5.x and Onwards

3
AIT (CE)
1.5.2 Client
 Window XP/Vista/7/8
 Browser : Mozilla Firefox , Google Chrome
1.5.3 JAVA (Programming Language)
 Java is an object oriented computer programming language, specifically designed
for the developers saying that “Write Once, Run Everywhere”, because the code
runs on every single platform ignoring the process of recompiling.
 Java is a programming language created by James Gosling from Sun
Microsystems (Sun) in 1991. The first publicly available version of Java (Java
1.0) was released in 1995.
 Sun Microsystems was acquired by the Oracle Corporation in 2010. Over time
new enhanced versions of Java have been released. The current version of Java is
Java 1.7 which is also known as Java 7.
 The original and reference implementation Java compilers, virtual machines, and
class libraries were developed by Sun from 1991 and first released in 1995. As of
May 2007, in compliance with the specifications of the Java Community Process,
Sun relicensed most of its Java technologies under the GNU General Public
License.
1.5.4 JSP (Java Server Pages)
 Java Server Page (JSP) is a web-scripting technology similar to Netscape server-
side JavaScript (SSJS) or Microsoft Active Server Pages (ASP). However, it's
more easily extensible than SSJS or ASP, and it isn't proprietary to any one
vendor or any particular web server. Although the JSP specification has been
managed by Sun Microsystems, any vendors can implement JSP in their own
systems.

4
AIT (CE)
 JSP is a presentation layer technology that sits on top of a Java servlets model and
makes working with HTML easier. Like SSJS, it allows you to mix static HTML
content with server-side scripting to produce dynamic output. By default, JSP uses
Java as its scripting language; however, the specification allows other languages
to be used, just as ASP can use other languages (such as JavaScript and
VBScript). While JSP with Java will be more flexible and robust than scripting
platforms based on simpler languages like JavaScript and VBScript, Java also has
a steeper learning curve than simple scripting languages.
1.5.5 JAVA Servlet
 In recent years, servlet technology has emerged as a powerful way to extend
Web server functionality through dynamic Web pages. A servlet is a Java
program that runs in a Web server, as opposed to an applet that runs in a client
browser. Typically, the servlet takes an HTTP request from a browser,
generates dynamic content (such as by querying a database), and provides an
HTTP response back to the browser. Alternatively, the servlet can be accessed
directly from another application component or send its output to another
component. Most servlets generate HTML text, but a servlet may instead
generate XML to encapsulate data.
 In the Java realm, servlet technology offers advantages over applet technology for
server-intensive applications, such as those accessing a database. One advantage
of running in the server is that the server is usually a robust machine with many
resources, making the program more scalable. Running in the server also results
in more direct access to the data. The Web server in which a servlet is running is
on the same side of the network firewall as the data being accessed.
1.5.6 Hibernate Framework
 Hibernate is an object-relational mapping library for the Java language,

5
AIT (CE)
providing a framework for mapping an object-oriented domain model to a
traditional relational database. Hibernate solves object-relational impedance
mismatch problems by replacing direct persistence-related database accesses
with high-level object handling functions.
What is Hibernate?
 Hibernate is an Object Relational Mapping Solution for JAVA.
 It maps the Java classes to the Database Tables.
 It is a powerful, high performance object/relational persistence and Query
service.
 Hibernate Provides 3 full featured query facilities :
1. Hibernate Query Language
2. Hibernate Criteria Query
3. Support for Query in native SQL dialect
 Take less development time
 Support Automatic key Generation
 XML Binding
 Has Eclipse support

6
AIT (CE)
Fig 1.1 Hibernate Framework
1.5.7 MySQL Back End Database
 MySQL is a popular choice of database for use in web applications, and is a
central component of the widely used LAMP web application software stack—
LAMP is an acronym for "Linux, Apache, MySQL and Pearl/PHP/Python".
 MySQL is written in C and C++. Its SQL parser is written in yacc, and a
homebrewed lexical analyzer named sql_lex.cc.
 MySQL works on many different system platforms. Many programming
languages with language-specific APIs include libraries for accessing MySQL
databases. These include MySQL Connector/Net for integration with Microsoft's
Visual Studio (languages such as C# and VB are most commonly used) and the
ODBC driver for Java.
 In addition, an ODBC interface called MyODBC allows additional programming
languages that support the ODBC interface to communicate with a MySQL
database, such as ASP or ColdFusion. The HTSQL - URL based query method

7
AIT (CE)
also ships with a MySQL adapter, allowing direct interaction between a MySQL
database and any web client via structured URLs. The MySQL server and official
libraries are mostly implemented in ANSI C/ANSI C++.
1.5.8 Apache Tomcat Back End Server
 Apache Tomcat (or Jakarta Tomcat or simply Tomcat) is an open source
servlet container developed by the Apache Software Foundation (ASF). Tomcat
implements the Java Servlet and the Java Server Pages (JSP) specifications from
Sun Microsystems, and provides a "pure Java" HTTP web server environment for
Java code to run.
 Tomcat should not be confused with the Apache web server, which is a C
implementation of an HTTP web server; these two web servers are not bundled
together. Apache Tomcat includes tools for configuration and management, but
can also be configured by editing XML configuration files.
1.5.9 Eclipse J2EE Toolkit:
 Eclipse is a toolkit which is designed for the creation of complex projects,
providing fully dynamic web application utilizing EJB’s. This consist of EJB tools ,
CMP ,data mapping tools & a universal test client that is designed to aid testing of
EJB’s.

TEAM ID: 12625 2: PROJECT MANAGEMENT
7
AIT (CE)
CHAPTER – 2
PROJECT MANAGEMENT
2.1 Process Model:
We have used Waterfall Model as Software Engineering life Cycle Process. It is the
simplest; oldest and most widely used process model for software development .This model
acquires its name from the fact that classic software life cycle is represented as a sequence of
descending steps.
Waterfall Model:
Fig 2.1: Water Fall Model

8
AIT (CE)
 Requirement Analysis:
This process is also known as feasibility study. In this phase, the development team
studied the site requirement. They investigate the need for possible dynamic
representation of the site and increase security features. By the end of feasibility study,
the team furnishes a document that holds the different specific recommendations for the
candidate system. It also includes personnel assignments, costs, project schedules, target
dates etc. the requirement gathering process is intensified and focused specially on
software. The essential purpose of this phase is to find the need and to define the problem
that needs to be solved. During this phase following facts were gathered.
 Determined the user need
 Identified the facts
 Establish the goals and objective for the proposed system
 Feasibility for the new system.
 System Analysis and Design:
In this phase the software’s overall structure and its nuances are defined. In terms of
client server technology the no of tiers needed for the package architecture, database
design, data structure design are defined in this phase. Analysis and Design are very
crucial in entire development cycle. Any glitch in this phase could be expensive to solve
in the later stage of software development. Hence following approach using designing.
 DFD
 Database Designing
 Form Designing
 Pseudo code for method
 Testing:
Once the code is generated, the website testing begins. Different testing
methodologies are done to unravel the bugs that were committed during the previous
phases. Different testing methodologies are used:

9
AIT (CE)
 Acceptance testing
 White Box Testing
 Black Box Testing
ADVANTAGES:
 Being a linear model, it is very simple to implement. The amount of resources
required to implement this model are minimal.
 Documentation is produced at every stage of the software’s development. This makes
understanding the product designing procedure, simpler.
 After every major stage of software coding, testing is done to check the correct
running of the code.
DISADVANTADES:
 Ironically, the biggest disadvantage is one of its greatest advantages. You cannot go
back a step; if the design phase has gone wrong, things can get very complicated in
the implementation phase.
 Often, the client is not very clear of what he exactly wants from the software. Any
changes that he mentions in between, may cause a lot of confusion.
 Small changes or errors that arise in the completed software may cause a lot of
problems.
 Until the final stage of the development cycle is complete, a working model of the
software does not lie in the hands of the client. Thus, he is hardly in a position to
inform the developers, if what has been designed is exactly what he had asked for.
2.3 Risk Management
Risk management is the identification, assessment, and prioritization of risks followed by
coordinated and economical application of resources to minimize, monitor, and control the
probability and/or impact of unfortunate events or to maximize the realization of
opportunities. Risks can come from uncertainty in financial markets, threats from project
failures legal liabilities, credit risk, accidents, natural causes and disasters as well as

10
AIT (CE)
deliberate attack from an adversary, or events of uncertain or unpredictable root-cause.The
risk management process involves:
1. Establishing Context: This includes an understanding of the current conditions in
which the organization operates on an internal, external and risk management
context.
2. Identifying Risks: This includes the documentation of the material threats to the
organization’s achievement of its objectives and the representation of areas that the
organization may exploit for competitive advantage.
3. Analyzing/Quantifying Risks: This includes the calibration and, if possible, creation
of probability distributions of outcomes for each material risk.
4. Integrating Risks: This includes the aggregation of all risk distributions, reflecting
correlations and portfolio effects, and the formulation of the results in terms of
impact on the organization’s key performance metrics.
5. Assessing/Prioritizing Risks: This includes the determination of the contribution of
each risk to the aggregate risk profile, and appropriate prioritization.
6. Treating/Exploiting Risks: This includes the development of strategies for
controlling and exploiting the various risks.
7. Monitoring and Reviewing: This includes the continual measurement and
monitoring of the risk environment and the performance of the risk management
strategies.
2.3.1 Risk Identification
Risk identification is a systematic attempt to specify threats to the project plan. By
identifying known and Predictable risks, the project manager takes a first step toward
avoiding them when possible and controlling them when necessary. There are two distinct
types of risks for each of the categories that are generic risks and product-specific risk.
Generic risks are a potential threat to every software project. Product-specific risks can only
be identified by those with a clear understanding of the technology, the people, and the
environment that is specific to the project at hand. Both generic and product-specific risks
should be identified systematically. The Checklist can be used for risk .
Identification and focuses on some subset of known and predictable risks in the following
generic subcategories.
 Product size – risks associated with the overall size of the software to be built or
modified.

11
AIT (CE)
 Business impact – risk associated with constraints imposed by management or the
marketplace.
 Customer characteristics – risks associated with the sophistication of the customer and
the developer’s ability to communicate with the customer in a timely manner.
 Process definition- risks associated with the degree to which the software process has
been defined and is followed by the development organization.
 Development environment – risks associated with the availability and quality of the tools
to be used to build the product.
 Technology to be built – risks associated with the complexity of the system to be built
and the “newness” of the technology that is packaged by the system.
 Staff size and experience – risks associated with the overall technical and project
experience of the engineers who will do the work.
2.3.2. Risk Analysis
Risk analysis is the science of risks and their probability and evaluation.
Risk analysis refers to the uncertainty of forecasted future cash flows streams, variance of
portfolio/stock returns, statistical analysis to determine the probability of a project's success
or failure, and possible future economic states.
2.3.3 Risk Planning
 Risk plan include a risk strategy. Broadly, there are four potential strategies, with numerous
variations. Projects may choose to:
 Avoid risk: Change plans to circumvent the problem;
 Control/Mitigate risk: Reduces impact or likelihood (or both) through intermediate
steps.
 Accept risk: Take the chance of negative impact (or auto-insurance), eventually
budget the cost (e.g. via a contingency budget line).
 Transfer risk: Outsource risk (or a portion of the risk - Share risk) to third party/ies
that can manage the outcome. This is done e.g. financially through insurance contracts
or hedging transactions, or operationally through outsourcing an activity.

TEAM ID: 12625 3: SYSTEM REQUIREMENT
AIT (CE) 13
CHAPTER – 3
SYSTEM REQUIREMENT
3.1 User Characteristics
The following characteristics are raised during the analysis of the needs of the users:
 A Person Should be able to login to the system through the first page of the Website.
 The Administrator can create Sub-Admin.
 Sub-Admin can upload the result of particular Exam. On successful completion of
upload, user can view their results.
 There will be a separate login for every user as his account in which he can get notices
for upcoming new exams.
 User can request sub-admin to give exam that sub-admin created.
 Sub-admin can restrict the exam to be given for particular group of user only.
 Each user can give number of exam he wanted to give.
 All the report of exam will be stored in the database till the date user had given exam.
 The Sub-Admin verifies all these reports and generates them for users to view them.
 After analyzing the requirements of the task to be performed, the next step is to analyze
the problem and understand its context. The first activity in the phase is studying the
existing system and other is to understand the requirements and domain of the new
system. Both the activities are equally important, but the first activity serves as a basis of
giving the functional specifications and then successful design of the proposed system.
Understanding the properties and requirements of a new system is more difficult and
requires creative thinking and understanding of existing running system is also difficult,
improper understanding of present system can lead diversion from solution.
3.2 Client Side Requirements
 This is designed in such a way that it is attractive, convenient and informative. Forms are
designed with various features, which make the console output more pleasing.

AIT (CE) 14
 As the most important sources of information to the users, better design should improve
the system’s relationships with us and also will help in decision making. Form design
elaborates the way output is presented and the layout available for capturing information
 One of the most important factors of the system is the output it produces. This system
refers to the results and information generated. Basically the output from a computer
system is used to communicate the result of processing to the user
3.3 Developer side Requirements
 Developer side requirement is part of overall system design that requires special attention
designing input data is to make the data entered easy and free from errors. The input
forms are designed using the controls available in Hibernate framework.
 A system user interacting through a workstation must be able to tell the system whether
to accept the input to produce reports. The collection of input data is considered to be
most expensive part of the system design. Since the input has to be planned in such a
manner so as to get relevant information, extreme care is taken to obtain pertinent
information.
3.4 Constraints
 The information of all the users must be stored in a database that is accessible
by the System.
 The System is connected to the server and is running 24*7.
 The users must have their correct usernames and passwords to enter into the
System to get the details of respective exams through the System.
3.4.1 Reliability Requirements
 Reliability is an important non-functional requirement for most software products so a
software requirements specification (SRS) should contain a reliability requirement, and
most do. But, one of our indicators of the quality of a ‘good’ requirement is that it is
testable, so it is reasonable to ask whether the reliability requirements in a SRS are
testable as written.

AIT (CE) 15
 For the users of a system it is the reliability of the system as a whole that is meaningful
but for analysts and testers it is important to separate the software requirements from the
hardware requirements as there are some significant differences.
 There is no question that any piece of hardware will eventually wear out and fail so
hardware product reliability can be stated and measured in terms of time to failure or
time between failures. The random component of the reliability forecast comes from the
fact that identical pieces of hardware will operate for various lengths of time before
failure.
 Software reliability can be a more difficult concept to grasp. A software product will fail
under certain conditions, with certain inputs, and given the same inputs and conditions
will fail every time until the cause of the failure is corrected. So, the reliability of a
software product is more about the random discovery of faults resulting from various
inputs with the system in various states. Although for small and simple systems it may be
theoretically possible to test every combination of states and inputs, for a system of any
size and complexity this is not feasible. The random nature of the fault discovery process
means we must use probabilities when we refer to software reliability requirements and
testing.
 Reliability test results should be stated in terms of measurements. Measurements are
taken during testing when we are collecting and analyzing data about the performance of
the software. In other words, we are tracking the occurrence of failures during testing.
But, a reliability requirement is a prediction or forecast of the performance of the product
in the future. What this means is that while we can measure the number of failures per
hour or per transaction in a system test environment we can only provide an estimate of
the actual performance of the system in a future production environment.
 Reliability is usually defined as the probability that a product will operate without failure
for a specified number of uses (transactions) or for a specified period of time. To be truly
testable a requirement for software reliability should be stated as a forecast and the test
results should indicate the confidence level associated with the forecast that the product
will meet the requirements.
3.4.2 Safety and Security Consideration
As software-intensive systems become more pervasive, a large number of safety-critical
systems are being developed and fielded.

AIT (CE) 16
To improve productivity, performance, and cost-effectiveness, we are developing more and
more safety-critical systems that are under computer control. And centralized computer
control is enabling many safety-critical systems to grow in size, complexity, and potential for
catastrophic failure. We use software to control our factories and refineries as well as power
generation and distribution. We also use software in our transportation systems including
airplanes, trains, ships, subways, and even in our family automobiles. Software is also a
major component of many medical systems in which safe functioning is critical to the safety
of patients and operators alike. Even when the software does not directly control safety-
critical hardware, software can provide operators and users with safety-critical data with
which they must make safety-critical decisions.
 The Software Engineering Institute developed the Team Software Process
(TSP) as a set of defined and measured best practices for use by individual software
developers and software development teams Teams using the TSP:
1) Use common sense software engineering practices
2) Manage defects throughout the developed life cycle
3) Control the process through measurement
4) Monitor the process
5) Address defect prevention as well as removal
6) Use predictive measures for reaming defects
Since schedule pressures and people issues get in the way of implementing best practices.
3.4.3 Criticality of the Application
The system can stop working on computers with very low internet connection. Other
than that there won’t be any issues. Apart from these the system should be able to make
updates at regular time intervals.
3.5 Assumption and Dependence
1. Assumptions
 Database transactions are assumed to be secure and reliable.
 User is the person having enough knowledge for the traversing operation.

AIT (CE) 17
 We will provide a user friendly interface so that any user can easily
navigate through the system, but he/she should be capable of providing
valid credentials for successful login.
 The server used for data storing is always secured.
2. Dependence
 The system is dependent upon the user’s valid credentials. If user
inputs wrong username or password, he/she will not be allowed to
login to the system.
 This application depends on the server and internet as all the
information is collected and then stored in the server through secure
internet connection.
 All the users of the system will be assigned a specific role. According
to these roles each and every user will be allowed to access predefined
set of features.

TEAM ID: 12625 4: SYSTEM ANALYSIS
18
AIT (CE)
CHAPTER – 4
SYSTEM ANALYSIS
Systems analysis is the study of sets of interacting entities, including computer systems analysis.
According to the Merriam-Webster dictionary, systems analysis is "the process of studying a
procedure or business in order to identify its goals and purposes and create systems and procedures
that will achieve them in an efficient way". Analysis and synthesis, as scientific methods, always go
hand in hand; they complement one another. Every synthesis is built upon the results of a preceding
analysis, and every analysis requires a subsequent synthesis in order to verify and correct its results.
4.1 Study of Current System
 Graphical user interface
In the flexibility of the uses the interface has been developed a graphics concept in mind,
associated through a browser interface. The GUI’S at the top level have been categorized as
1. Administrative user interface
2. Sub-Administrative user interface
3. User interface
4. Guest interface
The administrative user interface concentrates on the consistent information that is
practically, part of the organizational activities and which needs proper authentication for the
data collection. The interfaces help the administrations with all the transactional states like
Data insertion, Data deletion and Date updating along with the extensive data search
capabilities.
The operational or generic user interface helps the users upon the system in transactions
through the existing data and required services. The operational user interface also helps the
ordinary users in managing their own information helps the ordinary users in managing their
own information in a customized manner as per the assisted flexibilities.

19
AIT (CE)
Number of Modules
The Assessment system mainly conducts online exams which measures the difficulty level of
the questions.
There are 3 modules in the system:
i)Admin:
The admin performs following tasks:
 Manages questions.
 Manages Sub-Admin
 Manages exams
 Manages question paper
 Manage results
 Views difficulty level of the question as per the examiners.
 Manage Students
 Provide information regarding exams
ii) Sub-Admin:
 Manages Question Bank
 Manages question paper
 Manages Exams
 The sub admin cannot manipulate the data entered by the admin.
iii) User:
 Gives exams
 Manage profile
 Views results
4.2 Problem and Weakness of Current System
 If internet connection is lost during exam then session won't be continue any
more.
 Problem occurs during management of question bank for different kind of exams.
 Authentic sub-Admin is required to generate Examination.
4.3 Requirements of New System

20
AIT (CE)
The development of the new system contains the following activities, which try to automate
the entire process keeping in view of the database integration approach.
User friendliness is provided in the Website with various controls.
The system makes the overall project management much easier and flexible.
It can be accessed over the Internet.
Various classes have been used to provide file upload and mail features.
There is no risk of data mismanagement at any level while the project development is under
process.
It provides high level of security using different protocols
4.4 FEASIBILITY STUDY:
The feasibility study is the important step in any software development process. This is
because it makes analysis of different aspects like cost required for developing and executing
the system, the time required for each phase of the system and so on.
Though the feasibility study cannot be focused on a single area some of the areas or analysis
made in feasibility study is given below. But all the steps given below would not be followed
by all system developed.
The feasibility study varies based on the system that would be developed. Feasibility study is
made on the system being developed to analyze whether the system development process
require training of personnel. This help in designing training sessions as required in later
stage.
 Does the system contribute to overall objective?
Yes, the system is feasible at different levels of requirements.
 Can be system can be integrated with others?
Yes. It can be integrated with others.
 Is the cost of developing the system high or does it meet the budgeted costs?
That is a cost benefit analysis is made. In other words an analysis is made on cost
feasibility of the project. This helps in identifying whether the organization would

21
AIT (CE)
meet the budgeted costs and also helps the organization in making earlier and
effective plans for meeting extra costs because of the system development.
 ECONOMICAL FEASIBILITY
Economic analysis is the most frequently used method for evaluating the
effectiveness of a client system. More commonly known as cost/benefit analysis, the
procedure is to determine the benefits and savings that are expecting from a client
system and compare them with cost, decisions is mad to design and implement the
system.
This part of feasibility study gives the top management the economic
justification for the new system. This is the important unit to the management,
because very often top management does not like to get confound by the various
technicalities that bound to be associated with the project of its kind. A simple
economic analysis that gives the actual comparisons of costs and benefits is much
more meaningful in some cases.
In the system, the organization is most satisfied by the economic feasibility,
because, if the organization implements the system.
 TECHNICAL FEASIBILITY
Technical feasibility centers the existing manual system of test management process
and to what extent it can support the system. According to the feasibility analysis
procedure the technical feasibility of the system is analyzed and the technical
requirements such as software facilities, procedure, inputs are identified. It is also one
of the important phases of the system development activities.
The system offers greater level of user friendliness combined with greater processing
speed. Therefore, the cost of maintenance is reduced. Since, processing speed is very
high and the work is reduced in the maintenance point of view management convince
the project is operationally feasibility.
 OPERATIONAL FEASIBILITY
Its purpose is to gain understanding of the degree to which proposed system will
likely solve the business problem or take advantages of the opportunities outlined in

22
AIT (CE)
the system service request or project identification study. For a project motivated
from information system plans. System having substantial widespread on an
organizations structure or procedures, and are typically riskier project to undertake.
Thus, it is important to have a clear understanding of how information system will fit
into the current day to day operations of the organization.
4.5 REQUIREMENTS VALIDATION:
Requirements validation is an iterative process which takes place throughout the lifecycle of
the project. During elicitation, analysis and specification you should constantly be
questioning and clarifying the data given to you in order to check its validity. You are also
testing to makes sure that the requirements statements themselves are complete, correct,
feasible, necessary, prioritized, unambiguous and verifiable.
The user requirements include the following things.
 The application should be collaborative and cost effective.
 The application should allow all user to login and use the websites. This application
is for open source user so website would create a platform for users.
 This must provide basic functionality like login, logout and use the services.

23
AIT (CE)
4.6 FUNCTIONS OF SYSTEM:
4.6.1 USE CASE DIAGRAM OF THE SYSTEM
4.6.1.1 Use Case For Admin:
Fig 4.1 Use Case Diagram of Admin (Abstract)

24
AIT (CE)
Fig 4.2 Use Case Diagram of Sub-Admin

25
AIT (CE)
Fig 4.3 Use Case Diagram of System

26
AIT (CE)
4.7 Data Modeling
4.7.1 Class Diagram
Fig 4.4 Use Class diagram

27
AIT (CE)
4.7.2 Activity Diagram
Fig 4.5 General Activity Diagram
Registration:
Fig 4.6 Activity Diagram of Registration
R
Registeration
Registration Details
All
Valid
Successfully Register
L
No
Yes

28
AIT (CE)
Login:
Fig 4.7 Activity Diagram of Login
L
Login
Check
Enter Username & Password
Check
Login Successfully
Admin Sub Admin Student
A SA S
F
Forgot Password
Valid
Invalid

29
AIT (CE)
Admin:
Fig 4.8 Activity Diagram of Admin

30
AIT (CE)
Generate Paper:
Fig 4.9 Activity Diagram of Generate Paper
View Paper:
Fig 4.10 Activity Diagram of View Paper
G
Generate paper
Standard Paper Custom paper
Select QuestionsSelect Sections
Enough
Question?
Enough
Question?
Paper
Generated
V
Y
N
Y
N
V
View Paper
Edit Paper Delete Paper

31
AIT (CE)
Student:
Fig 4.11 Activity Diagram of Student
Fig 4.10 Activity Diagram of Student
S
Student
Manage Profile View Exam View Results
Apply For Exam
If Today
is Exam
Date?
Give Exam
Immediate
Result?
Show Result
C
N
Y
Y
N

32
AIT (CE)
Sub-Admin:
Fig 4.12 Activity Diagram of Sub-Admin
Forgot Password:
Fig 4.13 Activity Diagram of Forgot password
F
Forgot Password
Enter UserName
Check
Display Security
Question
Enter Security
Answer
Check?
Send username
and password
L
N
Y
N
Y

33
AIT (CE)
Change Password:
Fig 4.14 Activity Diagram of Change password

34
AIT (CE)
4.7.3 Data Dictionary:
Field name Data type Size Allow null Reference Table
User_id Int 11 - -
First_name Text - - -
Last_name Text - - -
Address Varchar 255 - -
Mobile_no Long_int 20 - -
Gender Text - - -
Dob Date - - -
Email Varchar 255 - -
Password Varchar 255 - -
Security_que Varchar 255 - -
Security_ans Varchar 255 - -
Date_of_reg Date - - -
Status Int 1 - -
College Varchar 255 Yes -
Type Text - - -
Table 4.1 User
Paper_id Int 11 - -
Exam_id Int 11 - Exam
Section_id Int 11 - Section
Que_id Varchar 255 - Question_bank
Table 4.2 Paper
Section_id Int 5 -
Name Varchar 255 -
Added_by Int 11 - User
Table 4.3 Section

35
AIT (CE)
Ser_id Int 11 -
User_id Int 11 - User
Exam_id Int 11 - Exam
Presence Int 11 Yes
Username Varchar 255 -
Password Varchar 255 -
Email Varchar 255 -
Mobile no Long Int 20 -
Total marks Float - Yes
Total time Varchar 25 Yes
Exam reg date Date - -
Status Int 11 -
Table 4.4 Student_Exam_Registration
Que_id Int 5 -
Question LongText - -
Options LongText - -
Answers LongText - -
Sec_id Int 5 - Section
Dif_level Int 2 -
Que_added_by Int 5 - User
Marks Int 3 -
Table 4.5 Question_bank
Exam_Result_id Int 11 -
Ser_id Int 11 - Student_Exam_Reg
Section_id Int 11 - Section
Marks Varchar 255 -
Un_id Int 11 -
Wrong_ans Int 11 -
Sec_wise_time Varchar 255 -
Table 4.6 Exams_Result

36
AIT (CE)
Exam_id Int 11 -
Exam name Varchar 255 -
Org name Varchar 255 -
Total marks Float - -
Start date time Longint 20 -
End date time Longint 20
Wrong ans marks Float - -
Unans marks Float - -
Instruction Varchar 255 -
Difficulty level Int 11 -
Result date Longint 20 Yes
Last reg date Longint 20 -
Exam creation date Date - -
Approval Int 1 -
Visibility Int 1 -
Status Int 11 -
Added by Int 11 - User
Table 4.7 Exam_Result
DifficultyId Int 11 -
QueId Int 11 - Question_Bank
NoOfUser Int 11 -
avgDifficulty Int 11 -
Table 4.8 Difficulty_Level
newsId Int 11 -
Image Varchar 255 -
Title Varchar 255 -
Content LongText - -
Table 4.9 News

37
AIT (CE)
4.8 Functional and Behavioral Modeling
4.8.1 Data Flow
Diagram Level-0 DFD
Fig 4.15 Data Flow Diagram Level 0

38
AIT (CE)
Level-1

39
AIT (CE)
Level-2:

40
AIT (CE)

41
AIT (CE)
4.8.2 Sequence Diagram:
Admin:
Fig 4.20 Sequence Diagram for Admin
Sub-Admin:
Fig 4.21 Sequence Diagram for Sub-Admin

42
AIT (CE)
User:
Fig 4.22 Sequence Diagram for User

Team ID: 12625 5: IMPLEMENTATION, PLANNING AND DETAILS
AIT (CE) 42
CHAPTER – 5
IMPLEMENTATION, PLANNING AND DETAILS
5.1 Implementation Environment:-
(1) Multiple customers can be used
(2) Uniform & User friendly GUI design
(3)Internet support.
5.1.1 Implementation Planning:
Implementation phase requires precise and monitoring mechanism in order to ensure
schedule and completeness. We developed the website in various sub phases in
implementation phase. These steps are as follows:
5.1.1.1 Graphical design:
This phase involved graphical implementation of the whole website that gives the user
a very easy and friendly UI.
5.1.1.2 Core Class Implementation:
First we decided to implement the core system classes which will facilitate the further
implementation and makes it smoother.
Property/ Attribute Coding: Code for each property or attribute
Method Coding: Coding for each method
5.1.1.3 User Components Implementation
Motive behind this separate phase is to focus on the Reusability. In these phase we
have tried to develop reusable User Interface components like Instead of creating new
database user can modify the database which are no longer needed for the database space
purpose

Team ID: 12625 5: IMPLEMENTATION, PLANNING AND DETAILS
AIT (CE) 43
5.1.1.4 User Interface Implementation
This phase the actual GUI implementation of the website that only will appear to the user and
we tried our best making the GUI as simple as possible that user can easily use the website.
5.2 Security Features:-
 Click 2 Wizard provides very high level security of AMAZON EC2 Cloud
service that is highly secure now a days in the world.
 Database encryption.
 Automatic database backup for hacking and crashing purpose.
 User must enter his/her name & password to make any changes in the links or
the any pages in the website.
 Customer must be entering all the valid details according to data field.
 Only system have the authority for the user management like update, delete, or
add user.
 The user detail is checked on net from the server when users enter the detail.
5.3 Coding Standard:-
 Always use the extension .jsp and .java.
 The use of white space and simple comments is strongly encouraged.
 Comments can be added in number of ways.
 For single line put “//”.
 For multiple lines use “/* */”.
 Do not store large objects in session, it may consume lot of server memory
depending on the number of users.
 Always use style sheet to control the look and feel of the pages.

TEAM ID: 12625 LIMITATIONS AND FUTURE ENHANCEMENT
AIT (CE) 44
Limitation and Future Enhancement
Limitations:
 For this project internet connection is must.
 If there is an internet connection problem during the exam the site will not provide
you result.
Future Plan:
We think that not a single Project is ever considered as complete forever because our mind is
always thinking new and our necessities also are growing day by day. We always want
something more than what we have. Our Application also, if you see at the first glance that
you find it to be complete but we want to make it still mature and fully automatic.
 We can provide Different type of authority to Sub-Admins to manage the data
 The Difficulty level of Unanswered or wrong answer can also be measured if
required.
 The Examiner can view answer once exam is complete and method of deriving.
 Answers is also shown in calculative questions.

TEAM ID: 12625 CONCLUSION
AIT (CE) 45
Conclusion
It is concluded that the application works well and satisfy the company. The application is
tested very well and errors are properly debugged. The site is simultaneously accessed from
more than one computers.
The site works according to the restrictions provided in their respective browsers. Further
enhancements can be made to the application, so that the web site functions very interactive
and useful to existing application.

TEAM ID: 12625 REFRENCES
AIT (CE) 46
References:
 www.greguide.com
 www.indiabix.com
 www.IQtest.com

TEAM ID: 12625 CANVAS
AIT (CE) 47
APPENDIX 6
CANVAS
Canvas 1–Observation Matrix Canvas
 Observations
 Scouted Challenges
 Top 5 Problem on the basis of Desirability, Feasibility and Viability
 Final Problem: Select 1 from Top 5

AIT (CE) 48

AIT (CE) 49

AIT (CE) 50
Canvas 2–Idea Funnel Canvas
 People
 Activities
 Situation/Context/Location
 Props/Possible Solutions

AIT (CE) 51
Canvas 3 - Product Development Canvas
 Purpose
 People
 Product Experience
 Product Features
 Product Functions
 Components
 Customer Revalidation
 Reject, Redesign, Retain

AIT (CE) 52

AIT (CE) 53

AIT (CE) 54

Assesmment System - project report

Recommended

Recommended

More Related Content

What's hot

What's hot (19)

Viewers also liked

Viewers also liked (20)

Similar to Assesmment System - project report

Similar to Assesmment System - project report (20)

Assesmment System - project report