Chapter I Introduction

1.1 Problem Defination : Online Aptitude Test is a used to make the test quite better and more feasible as we can do while comparing with others exam etc. This project will be done using C#.net as front end, and SQL SERVER as back end. It can used to develop such a great features like this project is mainly useful for college, institutes to make their students to be prepared to face for Aptitude Test from that age. This system will help to manage all the user record i.e. username and password. This application can also used in recruitment program by companies. The main objective of this software is update database directly, not manually. In existing system Administrator has to update question set manually by typing. But feature of this project is to support different types documents like (eg. .pdf). 1.2 Objective
1. This Web Application provides facility to conduct online examination . 2.

It saves time as it allows number of students to give the exam at time and displays the results as the test gets over, so no need to wait for the result. It is automatically generated by the server.

3. Administrator has a privilege to create, modify and delete the test papers and its

particular questions.
4. User can register, login and give the test with his specific id, and can see the

results as well. 1.3 SCOPE:

1. This can be used in educational institutions as well as in corporate world. 2. Can be used anywhere any time as it is a web based application (user Location

doesnt matter).
3. No restriction that examiner has to be present when the candidate takes the test.

Chapter II Requirement Analysis

1| Page

Requirement analysis is the important part of software life cycle. This forms the base for design and development. Here we are covering general aspect of requirement analysis first and then general software and hardware requirement. 2.1 Requirement Specification 2.1.1 Normal Requirement 1. Initially under project management a project is assigned 2. Creation of GUI which is user friendly with systematic and easy flow of control . 2.1.2 Expected Requirements 1. Successfully, the project with the user and uploaded with all it modules. 2. User friendly interface. 3. Easy way for creating Result of test. 2.1.3 Exciting Requirements 1. To support different types of files (eg. .pdf). 2. Update database automatically by reading pdf files and create database for Question set.

2.2 Specification of Requirements 2.2.1 System Interface

2| Page

Application would be a self-contained system. It will not access data of any other application nor will other application have access to its data. 2.2.2 User Interface Application will be accessed through a Browser Interface. The interface would be viewed best using 1024 x 768 and 800 x 600 pixels resolution setting. The software would be fully compatible with Microsoft Internet Explorer for version 6 and above. No user would be able to access any part of the application without logging on to the system. 2.3 Software Requirements (for Implementation) o For Server Windows 2000 Enterprise Edition SQL Server o For Client Windows 95/98/2000/NT Microsoft Internet Explorer 6 & above 2.4 Hardware Requirements (for Implementation) o For Server Intel Pentium III or above with 512 MB RAM 4 GB hard disk Network Interface o For Client PC With 256 MB RAM Network Interface

2.5 Breakdown Structure (Modules)

3| Page

Fi

Online Aptitude Test

Registratio n

Administrat ion

Test

g: Breakdown Structure (Modules) Online Aptitude Test Online Aptitude Test is the basic module. From that all Remaining modules are linked. Registration Module, Administration Module and Test Module are main modules after that online aptitude test module. Administrator has a privilege to create, modify and delete the test papers and its particular questions. User can register, login and give the test with his specific id, and can see the results as well.

2.6 Project Estimation:

4| Page

Embedded mode: Project size: Over 300KLOC Team size: Large Nature of Project: Complex Deadline: Tight E=a (KLOC) ^b.EAF D=c (E) ^d Here, E is effort D is development time a, b, c, d are coefficient For Embedded mode: a=3.6, b=1.20, c=2.5, d=0.3 The effort Adjustment factor in effort equation is simply the product of the effort multipliers corresponding to each of the cost drivers for your project. For eg. If our project is rated very high for complexity (effort multiplier of 1.34 and low for language and tool experience (effort multiplier of 1.09) and all of the other cost drivers are rated by to be nominal (effort multiplier of 1.00), the EAF is the product of 1.34 and 1.09.[3] For our project, effort Adjustment Factor = EAF =1.34*1.09=1.46

2.6.1 Estimation in KLOC

5| Page

5000 lines of code 2.6.2 Efforts Effort =3.6*(5) ^1.20*1.46=36.259 person month 2.6.3 Development Time D=2.5*(36.259) ^0.32=7.88 months 2.6.4 No of Persons = Effort /Development time = 36.259 person month/7.88 month =4.6 people

Chapter III System Analysis

6| Page

3.1 Project Scheduling and Tracking

3.1.1 Project Work Breakdown Structure (Analysis)

Online Aptitude Test

Registratio n

Administrat ion

Test

Studen t

Fresher for job

Read PDF

Update Database

Confirm Registrati on

Aptitude Test

Checking

Result

Fig: Project Work Breakdown Structure

Online Aptitude Test Online Aptitude Test is the basic module. From that all Remaining modules are linked. Registration Module, Administration Module and Test Module are main modules after that online aptitude test module.
7| Page

Registration There are two parts of registration 1) Student 2) Freshers for job Students are register for various exams or checking and increasing their performance. And freshers are register for participate in recruitment program of company. Administration Administrator has a privilege to create, modify and delete the test papers and its particular questions. Read pdf and update database and confirm the user registration are the work perform by the administrator. Test There are three modules in Test. 1) 2) 3) Aptitude Test Checking Result

3.2 Project Schedule& Time Line Chart The table 4.1 describes the schedule for project development. It also highlights all the tasks to be carried out along with their duration, dependencies and developers assigned to accomplish those tasks.
8| Page

Table 4.1 Task Schedule Days Task T1 T2 T3 T4 T5 Total 27 14 10 15 9 T1 T1 T2,T3 T4 Dependencies Developers Assigned D1,D2,D3,D4 D1,D2,D3,D4 D1,D2,D3,D4 D1,D3 D2,D4

15/ 07 T 1 T 2 3 T 4 T 5 T 6 T 7 T 8 T

20/0 7

2/08

19/0 8

M 1

23/0 8

12/0 9

22/0 9

01/10

06/10

M 2

Fig 4.2: Time Line Chart (1)

: Indicate the milestones M1: Finalization of project definition M2: Presentation and submission of project report
9| Page

3.2 Behavioral Modeling: 3.2.1 Use Case Diagram A use case involves a sequence of interactions between the initiator and the system, possibly involving other actors. In given use case diagram we have shown various scenarios interacting with each other to form system overview. In given use case diagram we have behavioral diagram defined by and created from a Use-case analysis. Its purpose is to present a graphical overview of the functionality provided by a system in terms of actors, their goals (represented as use cases), and any dependencies between those use cases. The main purpose of a use case diagram is to show what system functions are performed for which actor. Roles of the actors in the system can be depicted. Interaction among actors is not shown on the use case diagram. If this interaction is essential to a coherent description of the desired behavior, perhaps the system or use case boundaries should be re-examined. Alternatively, interaction among actors can be part of the assumptions used in the use case.

10 | P a g e

Registration

Usre

Login

Aptitude Test

Time limit

Result

Administrator

Usecase Diagram : Online Aptitude Test

3.2.2 Class Diagram In design specification it can be used to specify interfaces and classes that will be implemented in an object oriented program. Here we have used various advance class notation for different attributes and so this class diagram is representing a system overview with attributes and operations necessary for project flow.

11 | P a g e

Registration name address phoneno e-mail id username()

LoginName username password openID()

Final Apti Test Question Time answer() timeDisp()

reslt Database Marks calmarks()

3.3 Functional Modeling 3.3.1 Data Flow Diagram Data flow diagram (DFD) is also called as Bubble Chart, is a graphical technique, which is used to represent information flow, and transformers those are applied when data moves from input to output.DFD may further partitioned into different levels to show detailed information flow.

12 | P a g e

Registrati on Aptitude
User Result

Test Demo

DFD : Level 0

DFD : Level 1

13 | P a g e

USER
us er lo gi n

User Database
v er u se r i f ic a ti o n

User Registration user registration

get result

Login 1.0

user registration

Result 5.0

give exam give exam Examination 3.0

Registration 2.0

featch result
rm p e r fo te s t

pe rf o rm te st

Exam Result

MBA 3.1.1 fetch question

ENGG 3.2.2 fetch question

DFD: Level 2

s to re re s u lt

MBA

ENGG

check

check

Calculate Result 4.0

14 | P a g e

3.3.2 Control Flow Diagram In Control Flow Diagram we are considering various events related with control flow. It is also called as Bubble Chart. Transformers are applied when control moves from input to output represented by dotted circle.
Test System

User Login

Student

Administra tor

Choose Test

Give authority to user

Perform test

Provide Questions for test

Submit test

Calculate Marks

Result Display

Fig: CFD

Chapter IV
15 | P a g e

System Design
4.1 The Spiral Model The spiral model, originally proposed by Boehm [BOE88], is an evolutionary software process model that couples the iterative nature of prototyping with the controlled and systematic aspects of the linear sequential model. It provides the potential for rapid development of incremental versions of the software. Using the spiral model, software is developed in a series of incremental releases. During early iterations, the incremental release might be a paper model or prototype. During later iterations, increasingly more complete versions of the engineered system are produced. A spiral model is divided into a number of framework activities, also called task regions. Typically, there are between three and six task regions. Figure 3.1 depicts a spiral model that contains six task regions: Customer communicationtasks required to establish effective communication between developer and customer. Planning: tasks required defining resources, timelines, and other project related information. Risk analysis: tasks required to assess both technical and management risks. Engineering: tasks required to build one or more representations of the application. Construction and release: tasks required to construct, test, install, and provide user support (e.g., documentation and training)

16 | P a g e

Fig 3.1: Spiral model Customer evaluation Tasks required to obtain customer feedback based on evaluation of the software representations created during the engineering stage and implemented during the installation stage. Each of the regions is populated by a set of work tasks, called a task set, that are adapted to the characteristics of the project to be undertaken. For small projects, the number of work tasks and their formality is low. For larger, more critical projects, each task region contains more work tasks that are defined to achieve a higher level of formality. In all cases, the umbrella activities (e.g., software configuration management and software quality assurance) are applied. As this evolutionary process begins, the software engineering team moves around the spiral in a clockwise direction, beginning at the center. The first circuit around the spiral might result in the development of a product specification; subsequent passes around the spiral might be used to develop a prototype and then progressively more sophisticated versions of the software. Each pass through the planning region results in adjustments to the project plan. Cost and schedule are adjusted based on feedback derived from customer evaluation. In addition, the project manager adjusts the planned number of iterations required to complete the software. Unlike classical process
17 | P a g e

models that end when software is delivered, the spiral model can be adapted to apply throughout the life of the computer software. An alternative view of the spiral model can be considered by examining the project entry point axis. Each cube placed along the axis can be used to represent the starting point for different types of projects. A concept development project starts at the core of the spiral and will continue (multiple iterations occur along the spiral path that bounds the central shaded region) until concept development is complete. If the concept is to be developed into an actual product, the process proceeds through the next cube (new product development project entry point) and a new development project is initiated. The new product will evolve through a number of iterations around the spiral, following the path that bounds the region that has somewhat lighter shading than the core. In essence, the spiral, when characterized in this way, remains operative until the software is retired. There are times when the process is dormant, but whenever a change is initiated, the process starts at the appropriate entry point (e.g., product enhancement). The spiral model is a realistic approach to the development of large-scale systems and software. Because software evolves as the process progresses, the developer and customer better understand and react to risks at each evolutionary level. The spiral model uses prototyping as a risk reduction mechanism but, more important, enables the developer to apply the prototyping approach at any stage in the evolution of the product. It maintains the systematic stepwise approach suggested by the classic life cycle but incorporates it into an iterative framework that more realistically reflects the real world. The spiral model demands a direct consideration of technical risks at all stages of the project and, if properly applied, should reduce risks before they become problematic. But like other paradigms, the spiral model is not a panacea. It may be difficult to convince customers (particularly in contract situations) that the evolutionary approach is controllable. It demands considerable risk assessment expertise and relies on this expertise for success. If a major risk is not uncovered and managed, problems will undoubtedly occur. Finally, the model has not been used as widely as the linear sequential or prototyping paradigms.

4.1.1 Advantages: It is the most realistic model for software development.

18 | P a g e

Invalid

It reduces the number of risk in software development before they become serious problem.

4.2 Architectural Modeling 4.2.1 Component Diagram Component diagrams provide a physical view of current model. A component diagram shows organization and dependencies among software components, including source code components, binary code components and executable components. These diagrams also show externally visible behavior of components by displaying interfaces of the components.

Ques tions S erver

hom e

Profile

Us er D etail S n in ig

Ans wer

D B_Interface

Com ponent D ram : Online Aptitude Tes iag t

4.2.2 Deployment Diagram

19 | P a g e

A deployment diagram shows the allocation of process to processors in the physical design of a system. A deployment diagram may represent all or part of the process architecture of a system.

Update datbase Maintain all test program Administrator read pdf convert unmodifiable file in modifiable form

authenticate user

User

Perform Test

Deployment Diagram:Online Aptitude Test

4.3 Procedural Modelling

20 | P a g e

4.3.1 Activity Diagram

Register and get user ID pasword

User enter the Given Website for exam password not Valid Answer the question within given time

Log-out automatically after time expires Display result to user

Activity Diagram: Online aptitude Test

2.6.3 Sequence Diagram

21 | P a g e

A p titu d e T e s t U ser S y s te m A d m in is tra to r

lo g in R e -e n te r if in c o rre c t L o g in S u c c e s s fu l Q u e s tio n p a p e r D is p la y w ith tim e A n s w e r w ith tim e R e s u lt D is p la y

2.6.4 Collaboration Diagram

22 | P a g e

U ser

1 : lo g in 6 : A n s w e r w it h t im e 2 : R e - e n t e r if in c o r r e c t 5 : D is p la y w it h tim e 8 : D is p la y

S y s te m

4 : Q u e s t io n p a p e 3 : L o g in S u c c e s s fu l r 7 : R e s u lt

A d m in is tr a to r

Chapter V Applications & Future Scope

23 | P a g e

5.1 Application Student can give trial aptitude test for their practice and can increase their performance. Companies can use this software in their recruitment process for taking aptitude test of Freshers. Various institutions can use this software for taking aptitude test of their students. This online aptitude test software can be use by many Exams. Eg. GATE 2012. This is online application hence it is used in broad area of application. 5.2 Future Scope Scope of this project is very broad in terms of other manually taking exams. And it gives mechanism of convert file ( eg. .pdf ) into modifiable question set then admin can directly update database. This is the extra new feature is not yet developed. Hence in future it has huge scope
This can be used in educational institutions as well as in corporate world. Can be used anywhere any time as it is a web based application (user location

doesnt matter).
No restriction that examiner has to be present when the candidate takes the test. This Web Application provides facility to conduct online examination

worldwide. It saves time as it allows number of students to give the exam at a time and displays the results as the test gets over, so no need to wait for the result. It is automatically generated by the server.
Administrator has a privilege to create, modify and delete the test papers and its

particular questions. User can register, login and give the test with his specific id, and can see the results as well.

Chapter VI Conclusion

24 | P a g e

The On line test System is developed using .net Framework (C# and ASP) and SQL fully meets the objectives of the system for which it has been developed. The system has reached a steady state where all bugs have been eliminated. The system is operated at a high level of efficiency and all the teachers and user associated with the system understands its advantage. The system solves the problem. It was intended to solve as requirement specification.

25 | P a g e

Chapter VII References

1) C# 2005 Black Book by Matt Telles 2) 3) ASP.NET black book by Belmaks Solution Content Team http://www.softwaremetrics.com

26 | P a g e