SIKKIM MANIPAL UNIVERSITY
PROJECT REPORT
ON
“ONLINE EXAMINATION”
Submitted in partial fulfillment of the requirements for qualifying
BSC(IT)
SUBMITTED BY
NAME :
ENROLLMENT NO :
UNDER SUPERVISION OF:
Declaration
I here by declare that the project report entitled “(Title of the Project)”
Submitted in partial fulfillment and requirement for the degree of “(Course Name)” to Sikkim Manipal University, India is my original work and not submitted for the award of any other degree, diploma, fellowship, or any similar title of prizes.
Place :……………………. (Name of Student)
Date :……………………. Reg. No.
Course-Semester
Examiner’s Certificate
This is to certify that project report submitted by “(Name of Student)” entitled “(Name of Project)” is approved and is acceptable in quality and form.
Internal Examiner External Examiner
Name of Examiner
Designation
College / Organization
Ref. No:___________ Date:_____________
Certificate of Guide
This is to certify that project report entitled “(Name of Project)”, Submitted in partial fulfillment and requirement for the degree of “(Course Name)” to Sikkim Manipal University, India by “(Name of the Student)” has worked under my supervision and guidance and that no part of this report has been submitted for the award of any other degree, diploma, fellowship, or any similar titles or prizes and the work has not been published in any journal or magazine.
Certified By-
Name of the Project Guide
Designation
College / Organization
CONTENTS Page No.
1. Introduction and objectives
1.1. Introduction 8
1.2. Objectives of the Project 9
1.3. Advantage 11
1.4. Proposed System 12
1.5. Drawbacks of Current Manual – System 13
1.6. Need of New System 14
2. Project Selection
2.1. Software & Hardware Requirements 16
2.2. Introduction to JSP 17
2.3. MySQL 25
2.4 Data type 27
3. System Study
3.1. Preliminary Investigation 32
3.2. System Development Life Cycle 33
3.3. System Life Cycle 33
4. System Analysis
4.1. Importance of Computerized System 47
4.2. Principles of System Analysis 48
4.3. System Analysis 49
4.4. Interview and Questionnaires 55
5. System Design
5.1 System Design 62
5.2 Physical Design 66
5.3 Data Flow Diagram 68
5.4 Data Modeling 74
5.5 E-R Diagram 79
5.6 Modules 80
5.7 Scheduling 83
6. System Development
6.1 Source Code 86
6.2 Code Efficiency 143
6.3 Optimization of Code 143
7. Testing 144
8. Verification & Validation (V&V) 153
9. Post Implementation Maintenance and Review 155
9.1 Hardware Evaluation Factors 156
9.2 Software Evaluation Factors 157
9.3 Conversion and Training 158
9.4 Training Needs 159
10. Cost Estimation of the Project 160
11. GANTT & PERT CHART 161
12. Security and Validations 164
13. Scope of Future Application 165
14. Conclusion 167
15. Bibliography 168
1.1 INTRODUCTION
This Project work is undertaken in context of partial fulfillment of the BCA. The Online Examination System has been initiated for many different reasons. The idea is to set up an on-line cost effective Test Engine. The examination department, the academy will maintain a question bank. The administrator will have the authority to modify the criteria for examinations according to the academy’s rules.
• Electronic evaluation is quick and easy.
• Questions are generated one after another through database.
• User name and password for each student are checked properly.
• Automatically checking of objective answers and descriptive answers are manually checked.
• Provide online declaration of results.
• Exam can be conducted at a specified time, which is configurable.
• Large question bank with a random selection of question set.
• Objective style questions.
• Store results of students.
• Students Administrator can view results.
• Enable/Disable exams.
• Up to four answer options are possible.
• Easy navigation from one question to another.
• Introductory message for students before Taking exam.
1.2 OBJECTIVES OF THE PROJECT:
This system will facilitate off-line evaluation of examinations and declaration of results. This system will allow experts to send in their questions to the questions bank through this system. In general this system has the following objectives:
• To design an on-line cost effective examination and evaluation system.
• Fetch the questions randomly according to specific criteria from a large question database.
• Provide on-line evaluation and result declaration system.
• Use latest IT tools and Internet/Intranet technology to make a on-line Examination and evaluation system.
• To save the time of students engaged in learning advanced tools and technologies.
• To create a multi user application for conducting examinations and evaluating results on-line for intranet.
• Measure your skills.
• Certify you abilities.
Online Examination & Result store is on line system having Graphical user interface, which has been specially developed for any Examination. It covers the majority of the function related to Online Examination System. It covers Question records, Students details. The various main modules included in this software are as follows:
1. Master detail entry, which captures all the information, related to the master tables.
2. Transaction data entry, which stores data regarding the transaction.
3. Reports printing which print all the reports related to the system.
The main objectives of the system are:
1. To provide the user facility to maintain the Exam and result store records.
2. To provide the user ease with which (s) he can record all the day-to-day records with minimum efforts.
3. To provide all the details of any student information and their result, and Fine expenditures.
4. To provide all information about Student and details of Performance.
5. To automate the complete process of Question and answer. This allows for automatic allotments to fresh students depending upon the categories and keeping in view even distribution criteria for Exam meant for a particular category. It also provides for manual alterations of Exam and date thus allotted and choice-based allotments to student.
6. To automate the complete process of orientation of new patients by assigning a small group of faculty of the same date. This is based on any standard Online Examination management system. Several criteria are applied to automatic allotments; also manual alterations are permitted to authorized users.
1.3 ADVANTAGES
Every organization activities are influenced by the ability to process quickly and efficiently. Online Examination System add capability in three ways.
• Improved Processing Speed: The inherent speed with which computers process
data is one reason why organizations seek the development of system projects.
• Increase Volume: Provide capacity to process a greater amount of activity over large volume of data.
• Faster Retrieval of Information: Locating and retrieving information from storage, the ability to conducting complex searches.
The system also adds Control in two ways.
• Greater Accuracy and Consistency: Carrying out computing steps, including arithmetic, correctly and consistently.
• Better Security: Safeguarding sensitive and important data in a form that is in MY SQL. The last and most important thing is about the cost.
• Reduce costs: Using computing capability to process data at a lower cost than possible with other methods, while maintaining accuracy and performance levels.
The above said points tells us that switching from manual activity to
computerization one are really beneficial for any Organization.
1.4 PROPOSED SYSTEM
I have designed the given proposed system in the JSP, SERVLETS to automate Online Examination System.
The following steps that give the detailed information of the need of proposed system are:
Performance: During past several decades, the records are supposed to be manually handled for all activities. The manual handling of the record is time consuming and highly prone to error. To improve the performance of the Eduaction system, the computerized system is to be undertaken. The computerized project is fully computerized and user friendly even that any of the members can see the report and status of the institutes.
Efficiency: The basic need of this website is efficiency. The website should be efficient so that whenever a new user submit his/her details the website is updated automatically. This record will be useful for other users instantly.
Control: The complete control of the project is under the hands of authorized person who has the password to access this project and illegal access is not supposed to deal with. All the control is under the administrator and the other members have the rights to just see the records not to change any transaction or entry.
Security: Security is the main criteria for the proposed system. Since illegal access may corrupt the database. So security has to be given in this project.
PROJECT CATEGORY
This Project is coupled with material on how to use the various tool, sub sets available JSP AND My Sql.
The need of today’s software development is competence in a GUI based front-end tool, which can connect to Relational Database engines. This gives the programmer the opportunity to develop client server based commercial applications.
These applications give users the power and ease of a GUI with the multi user capabilities of Novell, UNIX or WinNT based RDBMS engines such as My SQL.
All the important coding techniques used by programmers, in OOPS based coding is brought out in full and in great detail.
1.5 DRAWBACKS OF CURRENT MANUAL- SYSTEM
• The current manual system has a lot of paper work and it does not deal with online examination.
• To maintain the records of students, question manually, is a Time-consuming job.
• With the increase in database, it will become a massive job to maintain the database.
• Requires large quantities of file cabinets, which are huge and require quite a bit of space in the office, which can be used for storing records of previous claims.
• The retrieval of records of the marks, questions will be a tedious job.
• Lack of security for the records, anyone disarrange the records of your system.
1.6 THE NEED OF NEW SYSTEM
1. Problem of Reliability: Current system is not reliable. It seems to vary in quality from one month to the next. Some times it gives good output, but some times the output is worst.
2. Problem of Accuracy: There are too many mistakes in reports.
3. Problem of timeliness: In the current system the reports and output produced is mostly late and in most of the cases it is useless because it is not on time.
4. Problem of Validity: The output and reports mostly contains misleading information. The customer’s information is sometimes not valid.
5. Problem of Economy: The current system is very costly. We have to spend lots of money to keep the system up and going, but still not get the desired results.
6. Problem of Capacity: The current system is suffering from problem of capacity also. The staff for organization is very less and the workload is too much. Few peoples cannot handle all the work.
I have designed the given proposed system in the JSP,SERVLETS to automate the process The following steps that give the detailed information of the need of proposed system are:
• Performance: During past several decades, the records are supposed to be manually handled for all activities. The manual handling of the record is time consuming and highly prone to error. To improve the performance of the Company system, the computerized system is to be undertaken. The computerized project is fully computerized and user friendly even that any of the members can see the report and status of the company.
• Efficiency: The basic need of this website is efficiency. The website should be efficient so that whenever a new user submits his/her details the website is updated automatically. This record will be useful for other users instantly.
• Control: The complete control of the project is under the hands of authorized person who has the password to access this project and illegal access is not supposed to deal with. All the control is under the administrator and the other members have the rights to just see the records not to change any transaction or entry.
• Security: Security is the main criteria for the proposed system. Since illegal access may corrupt the database. So security has to be given in this project.
2.1 SOFTWARE & HARDWARE REQUIREMENTS
The need of today’s software development is competence in a GUI based front-end tool, which can connect to Relational Database engines. This gives the programmer the opportunity to develop client server based commercial applications.
FRONT END
JSP programming tools are complete programming environments. It allows programmers to build a GUI program using the various on-screen controls such as buttons, text, menus, boxes etc. These controls are placed on a form and then the processing details related with each control are filled in.
In the business world, competitive strategies have become the order of the day to improve quality, cut costs and provide a high response customer service base. Most organizations today need to be market driven and do a lot of value addition to their products and services. This naturally calls for rational decision making, which requires information. Information Technology or IT provides that effective channel to support and implement this strategy. Client/Server is the technology that empowers the desktop, thus setting a trend for the way successful organizations will use technology in the next decade.
2.2 INTRODUCTION TO JSP
Adding dynamic content via expressions
As we saw in the previous section, any HTML file can be turned into a JSP file by changing its extension to .jsp. Of course, what makes JSP useful is the ability to embed Java. Put the following text in a file with .jsp extension (let us call it hello.jsp), place it in your JSP directory, and view it in a browser.
Hello! The time is now <%= new java.util.Date() %>
Notice that each time you reload the page in the browser, it comes up with the current time.
The character sequences <%= and %> enclose Java expressions, which are evaluated at run time.
This is what makes it possible to use JSP to generate dyamic HTML pages that change in response to user actions or vary from user to user.
Exercise: Write a JSP to output the values returned by System.getProperty for various system properties such as java.version, java.home, os.name, user.name, user.home, user.dir etc.
Scriptlets
We have already seen how to embed Java expressions in JSP pages by putting them between the <%= and %> character sequences.
But it is difficult to do much programming just by putting Java expressions inside HTML.
JSP also allows you to write blocks of Java code inside the JSP. You do this by placing your Java code between <% and %> characters (just like expressions, but without the = sign at the start of the sequence.)
This block of code is known as a “scriptlet”. By itself, a scriptlet doesn’t contribute any HTML (though it can, as we will see down below.) A scriptlet contains Java code that is executed every time the JSP is invoked.
Here is a modified version of our JSP from previous section, adding in a scriptlet.
<% // This is a scriptlet. Notice that the “date” // variable we declare here is available in the // embedded expression later on. System.out.println( “Evaluating date now” ); java.util.Date date = new java.util.Date(); %>
Hello! The time is now <%= date %>
If you run the above example, you will notice the output from the “System.out.println” on the server log. This is a convenient way to do simple debugging (some servers also have techniques of debugging the JSP in the IDE. See your server’s documentation to see if it offers such a technique.)
By itself a scriptlet does not generate HTML. If a scriptlet wants to generate HTML, it can use a variable called “out”. This variable does not need to be declared. It is already predefined for scriptlets, along with some other variables. The following example shows how the scriptlet can generate HTML output.
<% // This scriptlet declares and initializes “date” System.out.println( “Evaluating date now” ); java.util.Date date = new java.util.Date(); %>
Hello! The time is now
<% // This scriptlet generates HTML output out.println( String.valueOf( date )); %>
Here, instead of using an expression, we are generating the HTML directly by printing to the “out” variable. The “out” variable is of type javax.servlet.jsp.JspWriter.
Another very useful pre-defined variable is “request”. It is of type javax.servlet.http.HttpServletRequest
A “request” in server-side processing refers to the transaction between a browser and the server. When someone clicks or enters a URL, the browser sends a “request” to the server for that URL, and shows the data returned. As a part of this “request”, various data is available, including the file the browser wants from the server, and if the request is coming from pressing a SUBMIT button, the information the user has entered in the form fields.
The JSP “request” variable is used to obtain information from the request as sent by the browser. For instance, you can find out the name of the client’s host (if available, otherwise the IP address will be returned.) Let us modify the code as shown:
<% // This scriptlet declares and initializes “date” System.out.println( “Evaluating date now” ); java.util.Date date = new java.util.Date(); %>
Hello! The time is now
<%
out.println( date );
out.println( ”
Your machine’s address is ” );
out.println( request.getRemoteHost());
%>
A similar variable is “response”. This can be used to affect the response being sent to the browser. For instance, you can call response.sendRedirect (anotherUrl); to send a response to the browser that it should load a different URL. This response will actualy go all the way to the browser. The browser will then send a different request, to “anotherUrl”. This is a little different from some other JSP mechanisms we will come across, for including another page or forwarding the browser to another page.
Exercise: Write a JSP to output the entire line, “Hello! The time is now …” but use a scriptlet for the complete string, including the HTML tags.
Mixing Scriptlets and HTML
We have already seen how to use the “out” variable to generate HTML output from within a scriptlet. For more complicated HTML, using the out variable all the time loses some of the advantages of JSP programming. It is simpler to mix scriptlets and HTML.
Suppose you have to generate a table in HTML. This is a common operation, and you may want to generate a table from a SQL table, or from the lines of a file. But to keep our example simple, we will generate a table containing the numbers from 1 to N. Not very useful, but it will show you the technique.
Here is the JSP fragment to do it:
<% for ( int i = 0; i < n; i++ ) { %><% } %>
| Number | <%= i+1 %> |
You would have to supply an int variable “n” before it will work, and then it will output a simple table with “n” rows.
The important things to notice are how the %> and <% characters appear in the middle of the “for” loop, to let you drop back into HTML and then to come back to the scriptlet.
The concepts are simple here — as you can see, you can drop out of the scriptlets, write normal HTML, and get back into the scriptlet. Any control expressions such as a “while” or a “for” loop or an “if” expression will control the HTML also. If the HTML is inside a loop, it will be emitted once for each iteration of the loop.
Another example of mixing scriptlets and HTML is shown below — here it is assumed that there is a boolean variable named “hello” available. If you set it to true, you will see one output, if you set it to false, you will see another output.
<% if ( hello ) { %>
Hello, world
<% } else { %>
Goodbye, world
<% } %>
It is a little difficult to keep track of all open braces and scriptlet start and ends, but with a little practice and some good formatting discipline, you will acquire competence in doing it.
Exercise: Make the above examples work. Write a JSP to output all the values returned by System.getProperties with ”
” embedded after each property name and value. Do not output the ”
” using the “out” variable.
JSP Directives
We have been fully qualifying the java.util.Date in the examples in the previous sections. Perhaps you wondered why we don’t just import java.util.*;
It is possible to use “import” statements in JSPs, but the syntax is a little different from normal Java. Try the following example:
<%@ page import=”java.util.*” %>
<% System.out.println( “Evaluating date now” ); Date date = new Date(); %>
Hello! The time is now <%= date %>
The first line in the above example is called a “directive”. A JSP “directive” starts with <%@ characters.
This one is a “page directive”. The page directive can contain the list of all imported packages. To import more than one item, separate the package names by commas, e.g.
<%@ page import=”java.util.*,java.text.*” %>
There are a number of JSP directives, besides the page directive. Besides the page directives, the other most useful directives are include and taglib. We will be covering taglib separately.
The include directive is used to physically include the contents of another file. The included file can be HTML or JSP or anything else — the result is as if the original JSP file actually contained the included text. To see this directive in action, create a new JSP
Going to include hello.jsp…
<%@ include file=”hello.jsp” %>
View this JSP in your browser, and you will see your original hello.jsp get included in the new JSP.
Exercise: Modify all your earlier exercises to import the java.util packages.
JSP Declarations
The JSP you write turns into a class definition. All the scriptlets you write are placed inside a single method of this class.
You can also add variable and method declarations to this class. You can then use these variables and methods from your scriptlets and expressions.
To add a declaration, you must use the <%! and %> sequences to enclose your declarations, as shown below.
<%@ page import=”java.util.*” %>
<%! Date theDate = new Date(); Date getDate() { System.out.println( “In getDate() method” ); return theDate; } %>
Hello! The time is now <%= getDate() %>
The example has been created a little contrived, to show variable and method declarations.
Here we are declaring a Date variable theDate, and the method getDate. Both of these are available now in our scriptlets and expressions.
But this example no longer works! The date will be the same, no matter how often you reload the page. This is because these are declarations, and will only be evaluated once when the page is loaded! (Just as if you were creating a class and had variable initialization declared in it.)
Exercise: Modify the above example to add another function computeDate which re-initializes theDate. Add a scriptlet that calls computeDate each time.
Note: Now that you know how to do this — it is in general not a good idea to use variables as shown here. The JSP usually will run as multiple threads of one single instance. Different threads would interfere with variable access, because it will be the same variable for all of them. If you do have to use variables in JSP, you should use synchronized access, but that hurts the performance. In general, any data you need should go either in the session object or the request object (these are introduced a little later) if passing data between different JSP pages. Variables you declare inside scriptlets are fine, e.g. <% int i = 45; %> because these are declared inside the local scope and are not shared.
JSP Tags
Another important syntax element of JSP are tags. JSP tags do not use <%, but just the < character. A JSP tag is somewhat like an HTML tag. JSP tags can have a “start tag”, a “tag body” and an “end tag”. The start and end tag both use the tag name, enclosed in < and > characters. The end starts with a / character after the < character. The tag names have an embedded colon character : in them, the part before the colon describes the type of the tag. For instance:
body
If the tag does not require a body, the start and end can be conveniently merged together, as
Here by closing the start tag with a /> instead of > character, we are ending the tag immediately, and without a body. (This syntax convention is the the same as XML.)
Tags can be of two types: loaded from an external tag library, or predefined tags. Predefined tags start with jsp: characters. For instance, jsp:include is a predefined tag that is used to include other pages.
We have already seen the include directive. jsp:include is similar. But instead of loading the text of the included file in the original file, it actually calls the included target at run-time (the way a browser would call the included target. In practice, this is actually a simulated request rather than a full round-trip between the browser and the server). Following is an example of jsp:include usage
Going to include hello.jsp…
Try it and see what you get. Now change the “jsp:include” to “jsp:forward” and see what is the difference. These two predefined tags are frequently very useful.
Exercise: Write a JSP to do either a forward or an include, depending upon a boolean variable (hint: The concepts of mixing HTML and scriptlets work with JSP tags also!)
JSP Sessions
On a typical web site, a visitor might visit several pages and perform several interactions.
If you are programming the site, it is very helpful to be able to associate some data with each visitor. For this purpose, “session”s can be used in JSP.
A session is an object associated with a visitor. Data can be put in the session and retrieved from it, much like a Hashtable. A different set of data is kept for each visitor to the site.
Here is a set of pages that put a user’s name in the session, and display it elsewhere. Try out installing and using these.
First we have a form, let us call it GetName.html
The target of the form is “SaveName.jsp”, which saves the user’s name in the session. Note the variable “session”. This is another variable that is normally made available in JSPs, just like out and request variables. (In the @page directive, you can indicate that you do not need sessions, in which case the “session” variable will not be made available.)
<% String name = request.getParameter( “username” ); session.setAttribute( “theName”, name ); %>
The SaveName.jsp saves the user’s name in the session, and puts a link to another page, NextPage.jsp.
NextPage.jsp shows how to retrieve the saved name.
Hello, <%= session.getAttribute( “theName” ) %>
If you bring up two different browsers (not different windows of the same browser), or run two browsers from two different machines, you can put one name in one browser and another name in another browser, and both names will be kept track of.
The session is kept around until a timeout period. Then it is assumed the user is no longer visiting the site, and the session is discarded.
2.3 My SQL
Introduction
My SQL is an application used to create computer databases for the Microsoft Windows family of server operating systems. It provides an environment used to generate databases that can be accessed from workstations, the web, or other media such as a personal digital assistant (PDA). MY SQL is probably the most accessible and the most documented enterprise database environment right now. This also means that you can learn it a little quicker than most other database environments on the market
.
To start, you must have a computer that runs an appropriate operating system like Microsoft Windows >= XP Home Edition: that includes Windows XP Home Edition, Windows XP Professional, Windows 2000 Professional, or any version of Windows Server 2003. In this case, you must install MY SQL Yog.
What is SQL Used for:
Using SQL one can create and maintain data manipulation objects such as table, views, sequence etc. These data manipulation objects will be created and stored on the server’s hard disk drive, in a tablespace, to which the user has been assigned.
Once these data manipulation objects are created, they are used extensively in commercial applications.
DML, DCL, DDL:
In addition to the creation of data manipulation objects, the actual manipulation of data within these objects is done using SQL.
The SQL sentences that are used to create these objects are called DDL’s or Data Definition Language. The SQL sentences used to manipulate data within these objects are called DML’s or Data Manipulation Language. The SQL sentences, which are used to control the behavior of these objects, are called DCL’s or Data Control Language.
2.4 DATA TYPE
Built-in data types
In My Sql, each object (such as column, variable, or parameter) has a related data type, which is an attribute that specifies the type of data that the object can hold.
My SQL ships with 27 built-in (system) data types. They are:
Data Types Description
bigint Integer data from -2^63 through 2^63-1
int Integer data from -2^31 through 2^31 – 1
Smallint Integer data from -2^15 through 2^15 – 1
tinyint Integer data from 0 through 255
bit Integer data with either a 1 or 0 value
Decimal Fixed precision and scale numeric data from -10^38 +1 through 10^38 -1
numeric Fixed precision and scale numeric data from -10^38 +1 through 10^38 -1
money Monetary data values from -2^63 through 2^63 – 1
smallmoney Monetary data values from -214,748.3648 through +214,748.3647
float Floating precision number data from -1.79E + 308 through 1.79E + 308
real Floating precision number data from -3.40E + 38 through 3.40E + 38
datetime Date and time data from January 1, 1753, through December 31, 9999,
with an accuracy of 3.33 milliseconds
smalldatetime Date and time data from January 1, 1900, through June 6, 2079,
with an accuracy of one minute
char Fixed-length character data with a maximum length of 8,000 characters
varchar Variable-length data with a maximum of 8,000 characters
text Variable-length data with a maximum length of 2^31 – 1 characters
nchar Fixed-length Unicode data with a maximum length of 4,000 characters
nvarchar Variable-length Unicode data with a maximum length of 4,000 characters
ntext Variable-length Unicode data with a maximum length of 2^30 – 1 characters
binary Fixed-length binary data with a maximum length of 8,000 bytes
varbinary Variable-length binary data with a maximum length of 8,000 bytes
image Variable-length binary data with a maximum length of 2^31 – 1 bytes
cursor A reference to a cursor
sql_variant A data type that stores values of various data types,
except text, ntext, timestamp, and sql_variant
table A special data type used to store a result set for later processing
timestamp A database-wide unique number that gets updated every time
a row gets updated
uniqueidentifier A globally unique identifier
Some of these data types (bigint, sql_variant, and table) are only available in MY SQL 0, while some were supported under the previous My SQL r versions.
User-defined data types
My SQL supports user-defined data types too. User-defined data types provide a mechanism for applying a name to a data type that is more descriptive of the types of values to be held in the object. Using user-defined data type can make it easier for a programmer or database administrator to understand the intended use of any object defined with the data type. The user-defined data types are based on the system data types and can be used to predefine several attributes of a column, such as its data type, length, and whether it supports NULL values. To create a user-defined data type, you can use the sp_addtype system stored procedure or you could add one using the Enterprise Manager. When you create a user-defined data type, you should specify the following three properties:
• Data type’s name.
• Built-in data type upon which the new data type is based.
• Whether it can contain NULL values.
The following example creates a user-defined data type based on money data type named cursale that cannot be NULL:
EXEC sp_addtype cursale, money, ‘NOT NULL’
GO
Both system and user-defined data types are used to enforce data integrity. It is very important that we put forth a lot of effort while designing tables: the better you design your tables, the more time you can work without any performance problems. In an ideal case, you never will update the structure of your tables.
ENVIRONMENT / OPERATING SYSTEM
The age of standalone computing is long gone and it is now a world of networks. In this context, it is imperative for users to understand issues involved in working in a multi-user environment. Windows NT today is the most sought after Multi-user Operating System in the world. This is a 32-bit, powerful, user friendly and robust network operating system from Microsoft.
Windows NT is a big step up from Windows 95 both in terms of price and in terms of capabilities. NT Server is a well-built, fully functional, multi-user, multitasking operating system.
The release of NT Server 4 adds the popular Windows 95 user interface, the Internet Information Server (IIS) – capable of running Web, FTP, and Gopher services – a search engine called Index Server, the FrontPage HTML authoring package, and the Internet Explorer, all of which make Windows NT server a tough act to beat as a robust, capable web server.
The suggested Operating System for the server computer is Windows NT Server and for client computer is Windows 95.
3.1 PRELIMINARY INVESTIGATION
System development, a process consisting of two major steps of system analysis and design, start when management or sometimes system development personnel feel that a new system or an improvement in the existing system is required. The system development life cycle is classically thought of as the set of activities that analysts, designers and users carry out to develop and implement an information system. The system development life cycle consists of the following activities:
Preliminary investigation
Determination of system requirements
Design of system
Development of software
System testing
Implementation, evaluation, and maintenance
A request to take assistance from information system can be made for many reasons, but in each case someone in the organization initiates the request is made, the first system activity the preliminary investigation begins. This activity has three parts:
1) Request clarification
2) Feasibility study
3) Request approval
Request clarification: Many requests from employees and users in the organizations are not clearly defined, therefore it becomes necessary that project request must be examined and clarified properly before considering systems investigation.
3.2 SYSTEM DEVELOPMENT LIFE CYCLE
Systems are created to solve problems. One can think of the systems approach as an organized way of dealing with a problem. In this dynamic world, the subject System Analysis and Design (SAD), mainly deals with the software development activities.
DEFINING A SYSTEM
A collection of components that work together to realize some objective forms a system. Basically there are three major components in every system, namely input, processing and output.
In a system the different components are connected with each other and they are interdependent. For example, human body represents a complete natural system. We are also bound by many national systems such as political system, economic system, educational system and so forth. The objective of the system demands that some output is produced as a result of processing the suitable inputs.
3.3 SYSTEM LIFE CYCLE
System life cycle is an organizational process of developing and maintaining systems. It helps in establishing a system project plan, because it gives overall list of processes and sub-processes required for developing a system.
System development life cycle means combination of various activities. In other words we can say that various activities put together are referred as system development life cycle. In the System Analysis and Design terminology, the system development life cycle means software development life cycle.
Following are the different phases of software development cycle:
System study
Feasibility study
System analysis
System design
Coding
Testing
Implementation
Maintenance
The Different Phases Of Software Development Life Cycle Are Shown Below.
A system analysis is a separation of a substance into parts for study and their implementation and detailed examination.
Before designing any system it is important that the nature of the business and the way it currently operates are clearly understood. The detailed examination provides the specific data required during designing in order to ensure that all the client’s requirements are fulfilled. The investigation or the study conducted during the analysis phase is largely based on the feasibility study. Rather it would not be wrong to say that the analysis and feasibility phases overlap. High-level analysis begins during the feasibility study. Though analysis is represented as one phase of the system development life cycle (SDLC), this is not true. Analysis begins with system initialization and continues until its maintenance. Even after successful implementation of the system, analysis may play its role for periodic maintenance and up gradation of the system.
One of the main causes of project failures is inadequate understanding, and one of the main causes of inadequate understanding of the requirements is the poor planning of system analysis.
Analysis requires us to recall the objectives of the project and consider following three questions:
What type of information is required?
What are the constraints on the investigation?
What are the potential problems that may make the task more difficult?
FEASIBILITY STUDY
The basic premise of system analysis is being done here. The primary goal of the system analysis stage is to identify problems and determine how they can be solved with the computer system. In formal SDLC methodologies, the first step in system analysis is feasibility study. A feasibility study is the quick examination of the problems, goals, expected cost of the system. The objective is to determine whether the problem can reasonably solved with a computer system. In some cases, may be there is a better alternative, or perhaps is simply short term annoyance and will gradually disappear. In other cases, the problem may turn out to be more complex than was thought and involves users across the company. Also, some problems may not be solvable with today’s technology. It might be better to wait for better technology. In any case, you need to determine the scope of the project to gain the better idea of cost, benefits, and objectives.
The feasibility study is typically written so that non- programmers can easily understand it. It is used to “sell” the to the upper management and as a starting point for the next step. Additionally it is used as a reference to keep the project on track, and to evaluate the progress of project team. Is the project cost effective or there is a cheaper solution? Will the proposed system improve the operation of the bank; will complicating factors prevent it from achieving its goals? Does the technology exist and does the firm have the staff to make the technology work?
When the proposal is determined to be feasible, the team leaders are appointed and a plan and schedule are created. The schedule contains a detailed listing of what parts of the project are completed at each time. Of course, it extremely difficult to estimate the true cost and completion dates. Nonetheless, the schedule is an important tool to evaluate the status of the project and the progress of the team.
Steps in feasibility Analysis are:
1. Identify deficiency by pinpointing, missing functions, unsatisfactory performance, Excessive cost of operations.
2. Set goals to remove these deficiencies.
3. Goals must be quantified, realizable within the constraints of an organization, broken down into sub goals agreeable to all concerned.
4. Set goals not only to remove deficiencies but also to effectively meet competition. For instance, goals must be based on what competitors do.
l.) ECONOMIC FEASIBILITY
Economic analysis is the most frequently used technique for evaluating the effectiveness of a proposed system. More commonly known as cost / benefit analysis; in this procedure we determine the benefits and savings that are expected from a proposed system and compare them with costs. We found the benefits outweigh the costs; we take a decision to design and implement the new proposed system.
During the feasibility phase, broad alternatives solutions are examined. For each alternate solution the cost and benefits have to be examined before designing one of the alternatives.
Broad solutions will consist of:
1. Specifications of information to be made available by the system.
2. Description of what will be done manually and what the computer will do.
3. Specification of new computing equipment needed or specification of expansion of an existing computer.
COST AND BENEFIT ANALYSIS
Developing an IT application is an investment. Since after developing that application it provided the organization with profits. Profits can be monetary or in the form of an improved working environment. However, it carries risks because in some cases an estimate can be wrong and the project might not actually turn out to be beneficial.
Cost benefit analysis helps to give management a picture of the cost, benefits and risks. It usually involves comparing alternate investments.
Cost benefit determines the benefits and savings that are expected from the system and compares them with the expected cost.
In performing cost and benefit analysis it is important to identify cost and benefits factors. Cost and benefits can be categorized into the following categories:
i. Development cost – Development costs is the cost that are incurred during the development of the system. It is one time investment.
ii. Operating cost – Operating cost are the expenses required for the day¬ to-day running of the system. As, operating cost are wages, supplies and overheads.
iii. Hardware/Software cost – It includes the cost of purchasing or leasing of computes and it’s peripherals. Software costs involves required software cost.
iv. Personnel cost – It is the money spent on the people involved in the development of the system.
v. Facility cost – Expenses that are incurred during the preparation of the physical site where the system will be operational. These can be wiring, flooring, acoustics, lighting, and air-conditioning.
vi. Supply cost – These are variable costs that are very proportionately with the amount of use of paper, ribbons, disks, and others.
BENEFITS
We can define benefits as
Profit or Benefit = Income – Cost
Benefits can be accrued by:
Increasing income or
Decreasing costs or
Both
ITEM COST (Rs.)
Computer 40,000 (depend upon the configuration)
Laser Printer 7,000
JSP
My SQL
Scanner 4,000
Project cost
Total 4,000 (approx.)
55,000
We should know that we need a person who can work with these software’s and so his training will cost around Rs 4,000. Here we see that the total price to get one computer up and running with the database management system is close to Rs.50, 000 as we don’t really need a very high performance computer as this project is entirely text based and requires only minimal processor speeds for computing. If the developer wants to have a computers then we have the total costs being:
55,000*1 = Rs.55000
TECHNICAL FEASIBILITY
Today, very little is technically impossible. Consequently, technical feasibility looks at what is practical and reasonable. Technical feasibility addresses three major issues:
1. Is the proposed technology or solution practical?
2. Do we currently possess the necessary technology?
3. Do we possess the necessary technical expertise, and is the schedule reasonable?
Is the Proposed Technology or Solution Practical?
The technology for any defined solution is normally available. The question whether that technology is mature enough to be easily applied to our problems. Some firms like to use state-of-the-are technology, but most firms prefer to use mature and proven technology. A mature technology has a larger customer base for obtaining advice concerning problems and improvements.
Do We Currently Possess the Necessary Technology?
Assuming the solution’s required technology is practical, we must next ask ourselves, is the technology available in our information systems shop? If the technology is available, we must ask if we have the capacity. For instance, will our current printer be able to handle the new reports and forms required of a new system?
If the answer to any of these questions is no, then we must ask ourselves, Can we get this technology? The technology may be practical and available, and, yes, we need it. But we simply may not be able to afford it at this time. Although this argument borders on economic feasibility, it is truly technical feasibility. If we can’t afford the technology, then the alternative that requires the technology is not practical and is technically infeasible!
Do We Possess the Necessary Technical Expertise, and Is the Schedule Reasonable?
This consideration of technical feasibility is often forgotten during feasibility analysis. We may have the technology, but that doesn’t mean we have the skills required to properly apply that technology. For instance, we may have a database management systems (DBMS). However, the analysis and programmers available for the project may not know that DBMS well enough to properly apply it. True, all information systems professionals can learn new technologies. However, that learning curve will impact the technical feasibility of the project; specifically, it will impact the schedule.
As mentioned earlier, the current operational state of Examination is very primitive as all records are maintained on hand written database. These files are then placed in drawers or cabinets and tagged in a sorted order. Each cabinet takes a large space. Other than this it uses many kind of papers to calculate and maintain different account works.
The software & hardware to run my project, and is it’s usage is given in the table below:
TOOLS/PLATFORMS, HARDWARE & SOFTWARE REQUIREMENTS
HARDWARE:
Processor : Pentium 2.4 GHz or above
Memory : 256 MB RAM or above
Cache Memory : 128 KB or above
Hard Disk : 3 GB or above [at least 3 MB free space required]
Pen Drive : 2 GB
Printer : Laser Printer
SOFTWARE:
Operating System : Windows 95/98, Win NT, Win 2000.
Font-End Tool : JSP, SERVLETS
Back End Tool : MY SQL
OPERATIONAL FEASIBILITY
It is mainly related to human organizational and political aspects. The points to be considered are:
o What changes will be brought with the system?
o What organizational structures are disturbed?
o What new skills will be required? Do the existing staff members have these skills?
o If not, can they be trained in due course of time?
Generally project will not be rejected simply because of operational infeasibility but such considerations are likely to critically affect the nature and scope of the eventual recommendations.
For operational feasibility study we appointed a small group of people who are familiar with information system techniques, who understand the parts of the business that are relevant to the project and are skilled in system analysis and design process.
FEASIBILITY REPORT
After studying the feasibility of the project we came to the following points, these results may change according to further analysis and design.
PROJECT NAME: ONLINE EXAMINATION SYSTEM
DEFINITION OF PROBLEM OR OPPOIRTUNITY: We have to make a computerized system (software) to make the working of Examination System easy and efficient so that software will replace the manual work with automated computerized process.
EXPECTED BENEFITS:
Reduce the number of employee.
Save money.
Increase the efficiency of workers.
Reduce the response time.
Improve the service quality.
Reduce the bulk of paper work.
Reduce the chance of error by human.
Increase the accuracy in result.
4.1 IMPORTANCE OF COMPUTERIZED
ONLINE EXAMINATION SYSTEM
There are several attributes in which the computer based information works. Broadly the working of computer system is divided into two main groups:
• Transaction System
• Decision Support System
Transaction System:
A transaction is a record of some well-defined single and usually small occurrence in a system. Transactions are input into the computer to update the database files. It checks the entering data for its accuracy. This means that numeric data appears in numeric field and character data in character field. Once all the checks are made, transaction is used to update the database. Transaction can be inputted in on-line mode or batch mode. In on-line mode, transactions are entered and updated into the database almost instantaneously. In batch mode, transactions are collected into batches, which may be held for a while and inputted later.
Decision Support System:
It assists the user to make analytical decision. It shows the various data in organized way called analysis. This analysis can be made to syrdy preferences and help in making decisions.
Computer system works out best with record maintenance. It will tell you which customer would get how much pending/reports statements. It will also help to search the information about a particular person by simply entering his telephone number. User can store information as per requirement, which can be used for comparison with other reports.
4.2 PRINCIPLES OF SYSTEM ANALYSIS
Principles:
1. Understand the problem before you begin to create the analysis model.
2. Develop prototypes that enable a user to understand how human machine interaction will occur.
3. Record the origin of and the reason for every requirement.
4. Use multiple views of requirements like building data, function and behavioral models.
5. Work to eliminate ambiguity.
A Complete Structure:
The limited time and resources have restricted us to incorporate, in this project, only the main activities that are performed in news sites, but utmost care has been taken to make the system efficient and user friendly.
For the optimum use of practical time it is necessary that every session is planned. Planning of this project will include the following things:
• Topic Understanding.
• Modular Break – Up of the Syst
• Processor Logic for Each Module.
• Database Requirements.
Topic Understanding:
It is vital that the field of application as introduced in the project may be totally a new field. So as soon as the project was allocated to me, I carefully went through the project to identify the requirements of the project.
Modular Break –Up of the System:
Identify The Various Modules In The System.
List Them In The Right Hierarchy.
Identify Their Priority Of Development
Description Of The Modules:
SYSTEM ANALYSIS
A system analysis is a separation of a substance into parts for study and their implementation and detailed examination.
Before designing any system it is important that the nature of the business and the way it currently operates are clearly understood. The detailed examination provides the specific data required during designing in order to ensure that all the client’s requirements are fulfilled. The investigation or the study conducted during the analysis phase is largely based on the feasibility study. Rather it would not be wrong to say that the analysis and feasibility phases overlap. High-level analysis begins during the feasibility study. Though analysis is represented as one phase of the system development life cycle (SDLC), this is not true. Analysis begins with system initialization and continues until its maintenance. Even after successful implementation of the system, analysis may play its role for periodic maintenance and up gradation of the system.
One of the main causes of project failures is inadequate understanding, and one of the main causes of inadequate understanding of the requirements is the poor planning of system analysis.
Analysis requires us to recall the objectives of the project and consider following three questions:
• What type of information is required?
• What are the constraints on the investigation?
• What are the potential problems that may make the task
more difficult?
Keeping the above questions in mind and considering the survey conducted to determine the need of the system, the total system was deigned and can be described as under:
The three major parts of the system are:
Providing Information:
The system is effectively used to provide large variety of information to the interested customer. The major purpose of the site is to easily provide access to records of various products with quick update to latest modifications in the records. This thing is not at all possible in printed material, which are updated only once a few weeks.
Alert when available: Through the survey it was clearly that there is a need to device an alternative way for providing alert facility to the user. Sometimes the product which customer demand is not available at that moment, user can register demand of customer and when its available, system gives an alert to the user that customer had registered a customer request with the same match.
Constraints: After the objectives were clear during the analysis phase, it was essential to understand the constraints in order to plan and avoid problems arising during detailed analysis.
Technology – the customer may be committed to a particular hardware or software solution. The software required in this case is: compete Java developer kit, Microsoft windows environment for MS – access.
Budget – if budget is a real constraint, the budget of the new system proposed would be constantly compared with that of the existing system or any Alternatives solution. In this case during the economic feasibility study it has been clearly proved that the new system is definitely more feasible than the alternative solution possible. Organization must implement a system which saves the effort, also its provide an easy method for customer who investigate each detail itself.
Scope – what is the area under investigation in this project? What are the boundaries of the system? What is the extent of possible usage of the new system?
More and more people are now having access to organization and watch independently Details of new upcoming Students. Hence the scope is constantly increasing. However its usage can be increased many folds with a little investment from the organization side by implanting touch screen computer kiosks at various convenient positions at the service station.
Environmental Analysis:¬
The external entities for an organization are its Supplier’s customers or any individual.
METHODS USED FOR GATHERING INFORMATION
The methods used for gathering information about the existing information system are as followed.
(a) Review of records.
(b) Observation of the functioning system.
(c) Interviews.
(d) Questionnaires.
In order to create an informative and practical system, a system analyst would have to have some kind of way to view the current system. Receiving feed back on what can be done to improve the current system, and how much the current system is acceptable to the users.
1) Requirement analysis: –
The main part of problem is to obtain a clear understanding of the needs of user and
what exactly are desired from the software. It is used for specifying the
requirement.
FACT FINDING TOOLS:
After obtaining the background knowledge, I began to collect data on the existing system’s output, input, and costs. The tools used in data collection / information gathering are:
Review of the written Documents
On-site Observation
Interviews
Questionnaries
Review of the written documents:
In this phase we analyzed all the documents like the day books, supply report, order generating forms, supply forms, account etc. All these things describe the format and functions of the current system included in most manuals are system requirement that help determine how III various objectives are met.
The form is one of the most important source through which ! draw some conclusion like:
1. Who use the form(s)? How important are they to the user?
2. Do the forms include all the necessary information? What item should be added
or deleted?
3. How readable and easy to follow is the form?
4. How does the information in the form help other user make better decision?
5. What other uses does the form offer the user area?
By analyzing all the details we draw a conclusion that what are the merit and De-merit of the current phase. Will the company contain all the back up of all the important document of not sales person contains all the information about the available vehicles or not. But above all there are some problems with the on site observations that one analyst must face during analysis like:
1. Take long time and get inefficient result
2. Attitude and motivation of subject cannot be readily observed
3. Observation are subject to error
4. In a complex situation it can be very time¬ consuming
So for this we switched towards the other fact finding tools like interviews and Questionnaires.
4.4INTERVIEWS AND QUESTIONNAIRES
The interviews is a face to face interpersonal role situation in which a person called The interview asks a person being interview questions designed to gather information about a problem area. The interview is the oldest and most often used device for gathering information in systems work. It has qualities that behavioral and on-site observations do not possess .it can be used for two main purposes:
(a) as an exploratory device to identify relations or verify Information
(b) to capture information as it exists
1. On site observation:
It is not the easy task to do. In the on site observation the main objective is to get
close as possible to the real system that are being studied. There are some questions
that can serve as a guide for the on site observations:
1. What kind of the system is it? What does it do?
2. Who runs the system? Who are the important people in it?
3. What is the history of the system? How it get to its present stage of the
Development first in this phase we more likely listened than talk and to and to
listen with a sympathetic and genuine interest when information is conveyed. We
have not to give any advice or passing moral judgment on what is observed. Not to
argue with anyone or not to show any hostility towards one person and undue
friendliness towards another.
So in the on site observation we first visited to the entire organization watched all the transactions, watched the way of taking orders by the sales executive. What types of forms are used in the entire place? Are all forms are written, printed or not.
There are four primary advantages of the interviews:
1. its flexibility
2. easy to validate the information gathered
3. effective technique for elicit information about complex subject
4 instance, goals must be based on what competitors do.
Questionnaires:
It is usually associated with the self-administrated tools with items of the closed or fixed alternative type. By this nature a questionnaires offer the following advantages:
(a) It is economical and requires less skill to administer than the interview
(b) Unlike the interview which generally questions one subject at time questionnaire can be administrated to large number of individuals simultaneously.
(c) The questionnaires place less pressure on the subjects for immediate responses. Respondents have to think the question over and do calculations to provide more accurate data.
Mainly interviews and questionnaires are divided into two categories.
1. The unstructured alternative
2. The structured alternative
The unstructured interview is a relatively nondirective information technique. The role of the analyst as an interviewer is to encourage the respondent to talk freely and serve as a catalyst to the expression of feeling and opinions.
In the structured alternative approach the question are presented with exactly the same wording and in the same order to all subjects. Questions may be closed or open ended. An open-ended question requires no response direction or the specific response.
An analyst asks the questions at each level of management either it is top level, middle level or bottom level and at each department in the client’s site and at the manufacturer.
Following are the sample questions which we asked in the form of questionnaires and interviews:¬
Samples Questions asked to Computer Operators
(of similar kind of Centers with automized billing systems)
1.) Are you satisfied with the current system?
i. YES ii. NO iii. Partially Satisfied
2.) On an average how much customers do you get daily?
i. >100 ii.
a. ) School Student b. ) Collage Student c.) Working Personal
1.) How do you like the facilities provided by the Center?
i. Good ii. Betters than others iii. Best
2.) Are you satisfied with the Quality of service?
i. Yes ii. No iii. Partially Satisfied.
3.) What do you think about the discount offered?
i. Too Less ii. Appropriate iii. Should be increased
4.) Is the Price of auto items adequate?
i. Yes ii. No iii. Can’t Say
6.) Does the organization need further improvements?
i. Yes ii. No iii. Can’t say
Answers we got from various computer operators
(i) 45% answered
(ii) 35% answered
(iii)20% answered
Answers we got from various administrators
(i) 42% answered
(ii) 34% answered
(iii) 26% answered
i – positive answers
ii – Average answers
iii – Negative Answers
Answers we got from various consumers
34% answered
36% answered
30% answered
Identifying Current System Requirements (Software and Hardware specifications)
Software and Hardware Specifications for implementation of the system
(These specifications have been verified by the manager, Deft Infosystems (P) Ltd., New Delhi, as far as the cost is concerned)
5.1 SYSTEM DESIGN
The design document that we will develop during this phase is the blueprint of the software. It describes how the solution to the customer problem is to be built. Since solution to complex problems isn’t usually found in the first try, iterations are most likely required. This is true for software design as well. For this reason, any design strategy, design method, or design language must be flexible and must easily accommodate changes due to iterations in the design. Any technique or design needs to support and guide the partitioning process in such a way that the resulting sub-problems are as independent as possible from each other and can be combined easily for the solution to the overall problem. Sub-problem independence and easy combination of their solutions reduces the complexity of the problem. This is the objective of the partitioning process. Partitioning or decomposition during design involves three types of decisions: –
Define the boundaries along which to break;
Determine into how money pieces to break; and
Identify the proper level of detail when design should stop and implementation should start.
Basic design principles that enable the software engineer to navigate the design process suggest a set of principles for software design, which have been adapted and extended in the following list:
Free from the suffer from “tunnel vision.” A good designer should consider alternative approaches, judging each based on the requirements of the problem, the resources available to do the job.
The design should be traceable to the analysis model. Because a single element of the design model often traces to multiple requirements, it is necessary to have a means for tracking how requirements have been satisfied by the design model.
The design should not repeat the same thing. Systems are constructed using a set of design patterns, many of which have likely been encountered before. These patterns should always be chosen as an alternative to reinvention. Time is short and resources are limited! Design time should be invested in representing truly new ideas and integrating those patterns that already exist.
The design should “minimize the intellectual distance” between the software and the problem as it exists in the real world. That is, the structure of the software design should (whenever possible) mimic the structure of the problem domain.
The design should exhibit uniformity and integration. A design is uniform if it appears that one person developed the entire thing. Rules of style and format should be defined for a design team before design work begins. A design is integrated if care is taken in defining interfaces between design components.
The design activity begins when the requirements document for the software to be developed is available. This may be the SRS for the complete system, as is the case if the waterfall model is being followed or the requirements for the next “iteration” if the iterative enhancement is being followed or the requirements for the prototype if the prototyping is being followed. While the requirements specification activity is entirely in the problem domain, design is the first step in moving from the problem domain toward the solution domain. Design is essentially the bridge between requirements specification and the final solution for satisfying the requirements.
The design of a system is essentially a blueprint or a plan for a solution for the system. We consider a system to be a set of components with clearly defined behavior that interacts with each other in a fixed defined manner to produce some behavior or services for its environment. A component of a system can be considered a system, with its own components. In a software system, a component is a software module.
The design process for software systems, often, has two levels. At the first level, the focus is on deciding which modules are needed for the system, the specifications of these modules, and how the modules should be interconnected. This is what is called the system design or top-level design. In the second level, the internal design of the modules, or how the specifications of the module can be satisfied, is decided. This design level is often called detailed design or logic design. Detailed design essentially expands the system design to contain a more detailed description of the processing logic and data structures so that the design is sufficiently complete for coding.
Because the detailed design is an extension of system design, the system design controls the major structural characteristics of the system. The system design has a major impact on the testability and modifiability of a system, and it impacts its efficiency. Much of the design effort for designing software is spent creating the system design.
The input to the design phase is the specifications for the system to be designed. Hence, reasonable entry criteria can be that the specifications are stable and have been approved, hoping that the approval mechanism will ensure that the specifications are complete, consistent, unambiguous, etc. The output of the top-level design phase is the architectural design or the system design for the software system to be built. This can be produced with or without using a design methodology. Reasonable exit criteria for the phase could be that the design has been verified against the input specifications and has been evaluated and approved for quality.
A design can be object-oriented or function-oriented. In function-oriented design, the design consists of module definitions, with each module supporting a functional abstraction. In object-oriented design, the modules in the design represent data abstraction (these abstractions are discussed in more detail later). In the function-oriented methods for design and describe one particular methodology the structured design methodology in some detail. In a function- oriented design approach, a system is viewed as a transformation function, transforming the inputs to the desired outputs. The purpose of the design phase is to specify the components for this transformation function, so that each component is also a transformation function. Hence, the basic output of the system design phase, when a function oriented design approach is being followed, is the definition of all the major data structures in the system, all the major modules of the system, and how the modules interact with each other.
Once the designer is satisfied with the design he has produced, the design is to be precisely specified in the form of a document. To specify the design, specification languages are used. Producing the design specification is the ultimate objective of the design phase. The purpose of this design document is quite different from that of the design notation. Whereas a design represented using the design notation is largely to be used by the designer, a design specification has to be so precise and complete that it can be used as a basis of further development by other programmers. Generally, design specification uses textual structures, with design notation helping in understanding.
5.2 PHYSICAL DESIGN
The design phase focuses on the detailed implementation of the system recommended in the feasibility. Emphasis is on translating performance specifications into design specifications. The design phase is a transition from user-oriented document to a programmer-oriented document.
a. Design Methodology:
Design Methodology is a way to transform the “art” of system analysis and design into an “engineering – type” discipline. It explains the relationship amongst various modules and programs with in the system. It standardizes the approach to analysis and design, simplifies design by segmentation, improves documentation and subsequent maintenance and enhancements.
The following structured diagram can appropriately represent the relationship between various modules .
b. Design Overview:
In analyzing the present system a great deal of information was collected during the investigation and feasibility phases through list of problems and requirements, interview reports, questionnaires, onsite observations, manuals and determining potential solutions.
It is important to record this information in an unambiguous, concise manner which will be clear and accessible to others, and which can be used by other analysts and designers involved in developing the system. Structured techniques help us to record the information in this way, using diagrams and minimum amount of the text.
Structured analysis is a set of techniques and graphical tools that allow the analyst to develop a new kind of system specification that are easily understandable to the user. The traditional approach of organizing data through flowcharts support future developments and simplify communication with the user but focus on the cost/benefit and feasibility analysis, project management, hardware and software selection, and personal considerations. In contrast, structured analysis considers new goals and structured tools for analysis, which provide the basis for design and implementation.
c. Process Modeling:
System design goes through two phases of development: logical and physical. Logical implementation represented by Data Flow Diagram shows the logical flow of a system and defines the boundaries of the system it describes the input (source), outputs (destinations), data bases (data stores), and procedures (data flows) – all in the format that meets the user’s requirements. The logical implementation of the whole project can be represented as under through Data Flow Diagrams (DFD).
5.3 DATA FLOW DIAGRAM
Data flow diagrams are the most commonly used way of documenting the processing of the candidate system. As their name suggest they are a pictorial way of representing the flow of data into, around, and out of the system. They are easily understandable and are less prone to misinterpretation than textual description. A complete set of DFDs provides a compact top – down representation of the system, which makes it easier for the user and the analyst to envisage the system as a whole.
DFDs are constructed using four major components:
• External entities – represents the sources of the data that enter the system or the recipients of the system that leave the system.
for example – passenger is the usual receiver of information and supplier of data during form filling.
• Data stores – represent the stores of the data within the system example: computer files, databases or in the manual system files, etc. data stores can not be linked directly by data flows either to each other or to external entities without an intervening process to transform them.
• Processes – represent activities in which data is manipulated by being stored or retrieved or transformed in some way.
Process names are generally unambiguous and convey as much meaning as possible without being too long. Example: verify data, acquired time schedule etc.
Data flows – represents the movement of data between other components.
CONTEXT LEVEL DFD FOR
DFD Context/0 Level diagram
DFD 1st LEVEL DIAGRAM
`
DFD 2ND LEVEL DIAGRAM
Verify Availability
DFD 2ND LEVEL DIAGRAM
ENROLMENT OF STUDENT
D3 Result D4 Paper Setter
IInd Level DFD For Adding Questions
`
DFD For Password
DFD for ACCOUNTS
Submit Fees
Receipts
Update payment mode
D2: ACCOUNT
5.4 DATA MODELING
Data modeling defines primary data objects, composition of each data object, and attributes of the object, relationships between each object and other objects and between objects and the processes.
Data Objects: A data object is a representation of almost any composite information that must be understood by the software. By composite information, we mean something that has a number of different properties or attributes. A data object encapsulates data only there is no reference within a data object to operations that act on the data.
Attributes: Attributes define the properties of a data object and take on one of three different characteristics. They can be used to:
1. Name an instance of data object.
2. Describe the instance.
3. Make reference to another instance in other table.
Data Modeling
Member_Login Table
Field Name Data Type Constraint
Member_id Varchar (50) Primary Key
Password Varchar (50) Not Null
Is_active Varchar (5) Not Null
Is_delete Varchar (5) Not Null
Member_Login_History Table
Field Name Data Type Constraint
Member_id Varchar (50) Not Null
Exam_id Varchar (50) Not Null
Subject_id Varchar (50) Not Null
Exam_date Date Not Null
Result Varchar (50) Not Null
Percent Number Not Null
Admin_Login Table
Field Name Data Type Constraint
Use_id Varchar (30) Not Null
Password Varchar (30) Not Null
Member_Question_Answer_History Table
Field Name Data Type Constraint
Member_id Varchar (50) Not Null
Exam_id Varchar (50) Not Null
Subject_id Varchar (50) Not Null
Question_no Varchar (50) Not Null
Question Varchar (50) Not Null
Your answer Varchar (100) Not Null
Correct answer Varchar (100) Not Null
Subject_Details Table
Name Char Not Null
Subject_id Varchar (50) Primary Key
Subject_name Varchar (50) Not Null
Is_active Varchar (50) Not Null
Is_delete Varchar (50) Not Null
Is_active date Varchar (50) Not Null
Is_delete date Varchar (50) Not Null
Question_Details Table
Field Name Data Type Constraint
Subject_id Varchar (50) Primary Key
Question_no Number Not Null
Question Varchar (50) Not Null
Option_one Varchar (100) Not Null
Option_two Varchar (100) Not Null
Option_three Varchar (100) Not Null
Option_four Varchar (100) Not Null
Answer Varchar (100) Not Null
Is_active Varchar (30) Not Null
Is_delete Varchar (30) Not Null
Is_active date Varchar (30) Not Null
Is_delete date Varchar (30) Not Null
Exam_info Table
Name Data Type Constraint
Member id Varchar (50) Primary Key
Category Varchar (50) Not Null
Exam Date Varchar (50) Not Null
Score Varchar (50) Not Null
Marks Varchar (50) Not Null
Question Table
Name Data Type Constraint
id Varchar (50) Primary Key
Question Varchar (50) Not Null
Op1 Varchar (50) Not Null
Op2 Varchar (50) Not Null
Op3 Varchar (50) Not Null
Correct ans Varchar (50) Not Null
Category Varchar(50) Not Null
Category Table
Name Data Type Constraint
id Varchar (50) Primary Key
Category Varchar (50) Not Null
Relationships: Data objects are connected to one another in a variety of different ways. We can define a set of object relationship pairs that define the relevant relationships.
CARDINALITY AND MODALITY:
Cardinality:
The data model must be capable of representing the number of occurrences of objects in a given relationship. The cardinality of an object relationship pair is
• One-T0-One (1:1): An occurrence of object ‘A’ can relate to one and only one occurrence of object ‘B’ and vice versa.
• One-To-Many (1:N): One occurrence of object ‘A’ can relate to one or may occurrences of object ‘B’ but an occurrence of object ‘B’ can relate to only one occurrence of object ‘A’.
• Many-To-Many (M:N): An occurrences of ‘B’ and an occurrence of ‘B’ can relate to one or many occurrence of ‘A’.
Modality:
The modality of a relationship is zero if there is no explicit need for the relationship to occur or the relationship is optional. The Modality is one if the occurrence of the relationship is mandatory.
ENTITY RELATIONSHIP DIAGRAMS:
The object relationship pair can be represented graphically using the Entity Relationship Diagrams. A set of primary components are identified for the Entity Relationship Diagram,
1. Attributes,
2. Relationships and
3. Various Type Indicators.
The primary purpose of the Entity Relationship Diagram is to represent data objects and their relationships.
E-R DIAGRAM
5.6 Modules
Module 1: Password Module
In this module, this website is for multiple users. If a User enters a password and the software checks its validity. If the password is valid then option is given to change the password, otherwise “Invalid User/Password” message is displayed. There is an option for password recovery, log out, login, new users sign in. The Administrator can also update changes in the site after login.
Module 2: Creating new Entities ( Users , Question Papers, Courses, Students , Administrator)In this module, whenever a new entity is required to be added the corresponding forms are opened and the database is manipulated to check whether the data is already existing or not. If it already exists, then it prompts that “Entry already existing” and if not than the data is entered with the various validation checks.
Module 3: Modifying / Updating Existing Entities
In this module, whenever an existing entity is required to be modified the corresponding forms are opened and the database is manipulated and the data is fetched. Now the administrator can made the required changes and then accordingly, he updates the data. Again, the checks are followed in case there is any invalid entry.
Module 4: Searching
In this module, whenever an existing entity is required to be searched the corresponding forms are opened and the database is manipulated and the data is fetched. Again, the checks are followed in case there is any invalid entry.
Module 5: Student
This module provides all information about Student and details of Performance and provide all the details of any student information and their result, and Fine expenditures.
Module 6: Examination
This module provides the user facility to maintain the online Exam and result store records.
Module 7: Validation of Data Entered by the User & Error Handling
In this module, the validity of data entered by the user during the various business processes is checked through various validation checks. For example, there should not be any characters entered in the numeric fields, likewise if there is any error occurs than it should handle that particular error and give the required messages.
Module 8: Feedback
This module keeps track of all the feedbacks given by the users for future records.
Module 9: Categories
In this module different categories are added by the administrator. These are dynamic. For each Category
• Admin adds
• Category_id
• Category_Name
Module 10: Dynamic Questions
In this module, New questions are added by the administrator. He can add questions. These questions are visible to the students at the time of examination. For each question admin adds:
• Question id
• Question
• Option 1
• Option 2
• Option 3
• Correct Answer
Module 11: Admin Module
Administrator Can
1. Add New questions
2. Add New Categories
3. View Categories
4. View Question
5. View Feedbacks
6. View user details
7. Payment details
8. Exam Registration
9. Add Circular details
Module 12: Mail
Results are mailed to the students after online exam. He/She can get the result and details about the wrong questions on the mail. We are using Gmail server for mail Facilities.
Module 13: Exam Information
User can get the information regarding previous exams after Login in his account. It shows details of the previous exams:
• Exam date and Time
• Category or Subject
• Store obtained
• Total Marks
Process Logic for Each Module:
In the first module, validity of password is checked against a particular user.
In the second module, whenever a new entity is entered it should be checked for the duplicate data.
In the third and fourth module, just like the first module it should have the proper checks for every entity being modified or updated.
In the fifth and sixth module, again the validation checks are made and the different reports are generated to ease the business processes and decision making.
5.7 SCHEDULING
Scheduling of a software project does not differ greatly from scheduling of any multi- task engineering effort. Therefore, generalized project scheduling tools and techniques can be applied with little modification to software projects.
Program evaluation and review technique (PERT) and critical path method (CPM) are two project scheduling methods that can be applied to software development. Both techniques are driven by information already developed in earlier project planning activities.
Estimates of Effort
A decomposition of the product function.
The selection of the appropriate process model and task set.
Decomposition of tasks.
Interdependencies among tasks may be defined using a task network. Tasks, sometimes called the project Work Breakdown Structure (WBS) are defined for the product as a whole or for individual functions.
Both PERT and CPM provide quantitative tools that allow the software planner to (1) determine the critical path-the chain of tasks that determines the duration of the project; (2) establish “most likely” time estimates for individual tasks by applying statistical models; and (3) calculate “boundary times” that define a time window” for a particular task.
Boundary time calculations can be very useful in software project scheduling. Slippage in the design of one function, for example, can retard further development of other functions. It describes important boundary times that may be discerned from a PERT or CPM network: (I) the earliest time that a task can begin when preceding tasks are completed in the shortest possible time, (2) the latest time for task initiation before the minimum project completion time is delayed, (3) the earliest finish-the sum of the earliest start and the task duration, (4) the latest finish- the latest start time added to task duration, and (5) the total float-the amount of surplus time or leeway allowed in scheduling tasks so that the network critical path maintained on schedule. Boundary time calculations lead to a determination of critical path and provide the manager with a quantitative method for evaluating progress as tasks are completed.
Both PERT and CPM have been implemented in a wide variety of automated tools that are available for the personal computer. Such tools are easy to use and take the scheduling methods described previously available to every software project manager.
6.1 Source Code
Index.jsp
<%@ page language=”java” %>
<%@ page session=”true” %>
Online Examination
| <%@ include file=”header1.jsp” %> | |
| <%@ include file=”menu.jsp”%> |
WELCOME TO ONLINE EXAMINATION The Online Examination System has been initiated for many different reasons. The idea is to set up an on-line cost effective Test Engine. The examination department, the academy will maintain a question bank. The administrator will have the authority to modify the criteria for examinations according to the academy’s rules.
What is an IQ Test ?Originally, IQ, or Intelligence Quotient, was used to detect persons of lower intelligence, and to detect children of lower intelligence in order to place them in special education programs. The first IQ tests were designed to compare a child’s intelligence to what his or her intelligence “should be” as compared to the child’s age. If the child was significantly “smarter” than a “normal” child of his or her age, the child was given a higher score, and if the child scored lower than expected for a child of his or her age, the child was given a lower IQ score. Today IQ testing is used not primarily for children, but for adults. Today we attempt to write tests that will determine an adult’s true mental potential, unbiased by culture, and compare scores to the scores of other adults who have taken the same test. So today we compare an adult’s objective results to the objective results of other adults, and determine how intelligent each test taker is compared to all other test takers, instead of comparing test takers to an arbitrary age related standard. Standard DeviationThe first step to understanding IQ testing is to understand standard deviation. Standard deviation is kind of the “avg of the avg,” and often can help you find the story behind the data. To understand this concept, it can help to learn about what statisticians call normal distribution of data. A normal distribution of data means that most of the examples in a set of data are close to the “average,” while relatively few examples tend to one extreme or the other. Let’s say you are writing a story about nutrition. You need to look at people’s typical daily calorie consumption. Like most data, the numbers for people’s typical consumption probably will turn out to be normally distributed. That is, for most people, their consumption will be close to the mean, while fewer people eat a lot more or a lot less than the mean. When you think about it, that’s just common sense. Not that many people are getting by on a single serving of kelp and rice. Or on eight meals of steak and milkshakes. Most people lie somewhere in between.
|
login.jsp
<%@ page language=”java” %>
<%@ page session=”true” %>
Online Examination
exam_reg.jsp
<%@ page language=”java” import=”java.sql.*”%>
<%@ page session=”true” %>
Online Examination
payment.jsp
<%@ page language=”java” import=”java.sql.*” %>
<%@ page session=”true” %>
Online Examination
exam.jsp
<%@ page language=”java” import=”java.sql.*”%>
<%@ page session=”true” %>
Online Examination
| <%@ include file=”header1.jsp” %> | |
| <%@ include file=”menu.jsp”%> |
Our original Examination test is the most scientifically valid IQ test available on the web today. Previously offered only to corporations, schools, and in certified professional applications, it is now available to you. In addition to measuring your general IQ, our exclusive test assesses your performance in 13 different areas of intelligence, revealing your key cognizant strengths and weaknesses. Developed by PhDs and statistically sound, our test reflects the best research available. Rules For Online Examination . Become a member of online Examination System.( ) . Register your self.( . Select payment mode.( . Now you are valid for online Examination. Enter your correct member ID |
contact%20us.jsp
<%@ page language=”java” %>
<%@ page session=”true” %>
Online Examination
| <%@ include file=”header1.jsp” %> | |
| <%@ include file=”menu.jsp”%> |
Contact Us For your Suggetions contact us at Email:[email protected] Phone : 985643458,98543354646
|
admin.jsp
<%@ page language=”java” %>
<%@ page session=”true” %>
Online Examination System
| <%@ include file=”header1.jsp” %> | ||
| <%@ include file=”menu.jsp”%> |
|
|
aboutus.jsp
<%@ page language=”java” %>
<%@ page session=”true” %>
<%@ page import=”java.sql.*” %>
Online Examination
<%@ include file=”connect.jsp”%>
new_user.jsp
<%@ page language=”java” %>
<%@ page session=”true” %>
<%@ page import=”java.sql.*” %>
Online Examination
<%@ include file=”connect.jsp”%>
repo_users.jsp
<%@ page contentType=”text/html; charset=iso-8859-1″ language=”java” import=”java.sql.*” errorPage=”” %>
<%@ page language=”java” %>
<%@ page session=”true” %>
Online Examination
<%@ include file=”connect.jsp”%>
<%@ include file=”header1.jsp” %>
|
|---|
/Apache Software Foundation/Program Files (x86)/Apache Software Foundation/Program Files (x86)/Apache Software Foundation/Program Files (x86)/Apache Software Foundation/Tomcat 5.5/webapps/onlineexam/images/pic3.jpg)
/Apache Software Foundation/Program Files (x86)/Apache Software Foundation/Program Files (x86)/Apache Software Foundation/Program Files (x86)/Apache Software Foundation/Tomcat 5.5/webapps/onlineexam/images/pic4.jpg)
/Apache Software Foundation/Program Files (x86)/Apache Software Foundation/Program Files (x86)/Apache Software Foundation/Program Files (x86)/Apache Software Foundation/Tomcat 5.5/webapps/onlineexam/images/pic9.jpg)
/Apache Software Foundation/Program Files (x86)/Apache Software Foundation/Program Files (x86)/Apache Software Foundation/Program Files (x86)/Apache Software Foundation/Tomcat 5.5/webapps/onlineexam/images/pic7.jpg)
/Apache Software Foundation/Program Files (x86)/Apache Software Foundation/Program Files (x86)/Apache Software Foundation/Program Files (x86)/Apache Software Foundation/Tomcat 5.5/webapps/onlineexam/images/pic8.jpg)
/Apache Software Foundation/Program Files (x86)/Apache Software Foundation/Program Files (x86)/Apache Software Foundation/Program Files (x86)/Apache Software Foundation/Tomcat 5.5/webapps/onlineexam/images/images2.jpg)
/Apache Software Foundation/Program Files (x86)/Apache Software Foundation/Program Files (x86)/Apache Software Foundation/Program Files (x86)/Apache Software Foundation/Tomcat 5.5/webapps/onlineexam/images/images4.jpg)
repo_exam.jsp
<%@ page contentType=”text/html; charset=iso-8859-1″ language=”java” import=”java.sql.*” errorPage=”” %>
<%@ page language=”java” %>
<%@ page session=”true” %>
Online Examination
<%@ include file=”connect.jsp”%>
<%@ include file=”header1.jsp” %>
|
|---|
/Apache Software Foundation/Tomcat 5.5/webapps/onlineexam/images/pic3.jpg)
/Apache Software Foundation/Tomcat 5.5/webapps/onlineexam/images/pic4.jpg)
/Apache Software Foundation/Tomcat 5.5/webapps/onlineexam/images/pic9.jpg)
/Apache Software Foundation/Tomcat 5.5/webapps/onlineexam/images/pic7.jpg)
/Apache Software Foundation/Tomcat 5.5/webapps/onlineexam/images/pic8.jpg)
/Apache Software Foundation/Tomcat 5.5/webapps/onlineexam/images/images2.jpg)
/Apache Software Foundation/Tomcat 5.5/webapps/onlineexam/images/images4.jpg)
repo_payment.jsp
<%@ page contentType=”text/html; charset=iso-8859-1″ language=”java” import=”java.sql.*” errorPage=”” %>
<%@ page language=”java” %>
<%@ page session=”true” %>
Online Examination
<%@ include file=”header1.jsp” %>
|
|---|
repo_feedback.jsp
<%@ page contentType=”text/html; charset=iso-8859-1″ language=”java” import=”java.sql.*” errorPage=”” %>
<%@ page language=”java” %>
<%@ page session=”true” %>
Online Examination
<%@ include file=”header1.jsp” %>
|
|---|
Reports
repo_users.jsp
<%@ page contentType=”text/html; charset=iso-8859-1″ language=”java” import=”java.sql.*” errorPage=”” %>
<%@ page language=”java” %>
<%@ page session=”true” %>
Online Examination
<%@ include file=”connect.jsp”%>
<%@ include file=”header1.jsp” %>
|
|---|
repo_exam.jsp
<%@ page contentType=”text/html; charset=iso-8859-1″ language=”java” import=”java.sql.*” errorPage=”” %>
<%@ page language=”java” %>
<%@ page session=”true” %>
Online Examination
<%@ include file=”connect.jsp”%>
<%@ include file=”header1.jsp” %>
|
|---|
repo_payment.jsp
<%@ page contentType=”text/html; charset=iso-8859-1″ language=”java” import=”java.sql.*” errorPage=”” %>
<%@ page language=”java” %>
<%@ page session=”true” %>
Online Examination
<%@ include file=”header1.jsp” %>
|
|---|
repo_feedback.jsp
<%@ page contentType=”text/html; charset=iso-8859-1″ language=”java” import=”java.sql.*” errorPage=”” %>
<%@ page language=”java” %>
<%@ page session=”true” %>
Online Examination
<%@ include file=”header1.jsp” %>
|
|---|
6.2 CODE EFFICIENCY
Reviewing of Code efficiency for a module is carried out after the module is successfully compiled and all the syntax errors eliminated. Code efficiency review is extremely cost-effective strategies for reduction in coding errors in order to produce high quality code. Normally, two types of efficiency are carried out on the code of a module – code optimization and code inspection. The procedure and final objective of these two efficiency techniques are very different as discussed below.
6.3 OPTIMIZATION OF CODE
Code optimization is an informal code analysis technique. In this technique, after a module has been coded, it is successfully compiled and all syntax errors are eliminated. Some members of the development team are given the code a few days before the optimization meeting to read and understand the code. Each member selects some test cases and simulates execution of the code by hand (i.e. trace execution through each statement and function execution). The main objectives of the optimization are to discover the algorithmic and logical errors in the code. The members note down their findings to discuss these in a optimization meeting where the coder of the module is also present.
Even though a code optimization is an informal analysis technique, several guidelines have evolved over the years for making this naïve technique more effective and useful. Of course, these guidelines are based on personal experience, common sense, and several subjective factors. Therefore are based on personal experience, common sense, and several subjective factors. Therefore, guidelines should be considered as examples rather than as rules to be applied dogmatically. Some of these guidelines are the following:
The team performing the code optimization should not be either too big or too small. Ideally, it should consist of three to seven members.
Software Testing is an empirical investigation conducted to provide stakeholders with information about the quality of the product or service under test , with respect to the context in which it is intended to operate. This includes, but is not limited to, the process of executing a program or application with the intent of finding software bugs. It can also be stated as the process of validating and verifying that a software program/application/product meets the business and technical requirements that guided its design and development, so that it works as expected and can be implemented with the same characteristics.
A primary purpose for testing is to detect software failures so that defects may be uncovered and corrected. This is a non-trivial pursuit. Testing cannot establish that a product functions properly under all conditions but can only establish that it does not function properly under specific conditions.[11] The scope of software testing often includes examination of code as well as execution of that code in various environments and conditions as well as examining the aspects of code: does it do what it is supposed to do and do what it needs to do. In the current culture of software development, a testing organization may be separate from the development team. There are various roles for testing team members. Information derived from software testing may be used to correct the process by which software is developed.
Defects and failures
Not all software defects are caused by coding errors. One common source of expensive defects is caused by requirements gaps, e.g., unrecognized requirements, that result in errors of omission by the program designer. A common source of requirements gaps is non-functional requirements such as testability, scalability, maintainability, usability, performance, and security.
Software faults occur through the following process. A programmer makes an error (mistake), which results in a defect (fault, bug) in the software source code. If this defect is executed, in certain situations the system will produce wrong results, causing a failure.[12] Not all defects will necessarily result in failures. For example, defects in dead code will never result in failures. A defect can turn into a failure when the environment is changed. Examples of these changes in environment include the software being run on a new hardware platform, alterations in source data or interacting with different software.[12] A single defect may result in a wide range of failure symptoms.
Compatibility
A frequent cause of software failure is compatibility with another application, a new operating system, or, increasingly, web browser version. In the case of lack of backward compatibility, this can occur (for example…) because the programmers have only considered coding their programs for, or testing the software upon, “the latest version of” this-or-that operating system. The unintended consequence of this fact is that: their latest work might not be fully compatible with earlier mixtures of software/hardware, or it might not be fully compatible with another important operating system. In any case, these differences, whatever they might be, may have resulted in (unintended…) software failures, as witnessed by some significant population of computer users.
This could be considered a “prevention oriented strategy” that fits well with the latest testing phase suggested by Dave Gelperin and William C. Hetzel, as cited below.
Input combinations and preconditions
A very fundamental problem with software testing is that testing under all combinations of inputs and preconditions (initial state) is not feasible, even with a simple product. This means that the number of defects in a software product can be very large and defects that occur infrequently are difficult to find in testing. More significantly, non-functional dimensions of quality (how it is supposed to be versus what it is supposed to do) — for example, usability, scalability, performance, compatibility, reliability — can be highly subjective; something that constitutes sufficient value to one person may be intolerable to another.
Static vs. dynamic testing
There are many approaches to software testing. Reviews, walkthroughs or inspections are considered as static testing, whereas actually executing programmed code with a given set of test cases is referred to as dynamic testing. The former can be, (and unfortunately in practice often is…) omitted, whereas the latter takes place when programs begin to be used for the first time – which is normally considered the beginning of the testing stage. This may actually begin before the program is 100% complete in order to test particular sections of code (modules or discrete functions). For example, Spreadsheet programs are, by their very nature, tested to a large extent “on the fly” during the build process as the result of some calculation or text manipulation is shown interactively immediately after each formula is entered
1. UNIT TESTING:
This is the smallest testable unit of a computer system and is normally tested using the white box testing. The author of the programs usually carries out unit tests.
2. INTEGRATION TESTING:
In integration testing, the different units of the system are integrated together to form the complete system and this type of testing checks the system as whole to ensure that it is doing what is supposed to do. The testing of an integrated system can be carried out top-down, bottom-up, or big-bang. In this type of testing, some parts will be tested with white box testing and some with black box testing techniques. This type of testing plays very important role in increasing the systems productivity. We have checked our system by using the integration testing techniques.
3. SYSTEM TESTING:
A part from testing the system to validate the functionality of software against the requirements, it is also necessary to test the non-functional aspect of the system. Some examples of non-functional tools include tests to check performance, data security, usability/user friendliness, volume, load/stress that we have used in our project to test the various modules.
System testing consists of the following steps:
1. Program(s) testing.
2. String testing.
3. System testing.
4. System documentation.
5. User acceptance testing.
4. FIELD TESTING:
This is a special type of testing that may be very important in some projects. Here the system is tested in the actual operational surroundings. The interfaces with other systems and the real world are checked. This type of testing is very rarely used. So far our project is concerned; we haven’t tested our project using the field testing.
5. ACCEPTANCE TESTING:
After the developer has completed all rounds of testing and he is satisfied with the system, then the user takes over and re-tests the system from his point of view to judge whether it is acceptable according to some previously identified criteria. This is almost always a tricky situation in the project because of the inherent conflict between the developer and the user. In this project, it is the job of the bookstores to check the system that whether the made system fulfills the goals or not.
WHY SYSTEM TESTING?
Testing is vital to the success of the system. System testing makes a logical assumption that if all the parts of the system are correct, the goal will be successfully achieved. Inadequate testing results in two types of problems:
1. The time lag between the cause and the appearance of the problem.
2. The effect of system errors on the files and records within the system.
ACTIVITY NETWORK FOR SYSTEM TESTING
The test plan entails the following activities:
1. Prepare test plan.
2. Specify conditions for user acceptance testing.
3. Prepare test data for program testing.
4. Prepare test data for transaction path testing.
5. Plan user training.
6. Compile/assemble programs.
7. Prepare job performance aids.
8. Prepare operational documents.
PREPARE TEST : A workable test plan must be prepared in accordance with established design specifications. It includes the following items:
• Outputs expected from the system.
• Criteria for evaluating outputs.
• A volume of test data.
• Procedure for using test data.
• Personnel and training requirements.
SPECIFY CONDITIONS FOR USER ACCEPTANCE TESTING
Planning for user acceptance testing calls for the analyst and the user to agree on conditions for the test.
PREPARE TEST DATA FOR PROGRAM TESTING
As each program is coded, test data are prepared and documented to ensure that all aspects of the program are properly tested.
PREPARE TEST DATA FOR TRANSACTION PATH TESTING
This activity develops the data required for testing every condition and transactions to be introduced into the system. The path of each transaction from origin to destination is carefully tested reliable results.
PLAN USER TRAINING
User training is designed to prepare the user for testing and converting the system. User involvement and training take place parallel with programming for three reasons:
• The system group has time available to spend on training while the programs are being written.
• Initiating a user-training program gives the systems group a clearer image of the user’s interest in the new system.
• A trained user participates more effectively in system testing.
The training plan is followed by preparation of the user training manual and other text materials.
COMPILE / ASSEMBLE PROGRAMS
All programs have to be compiled / assembled for testing.
PREPARE JOB PERFORMANCE AIDS
In this activity the materials to be used by personnel to run the system are specified and scheduled. This includes a display of materials.
PREPARE OPERATIONAL DOCUMENTS
During the test plan stage, all operational documents are finalized including copies of the operational formats required by the candidate system.
SYSTEMS TESTING
The computer department to ensure that the system functions as specified does this testing. This testing is important to ensure that a working system is handed over to the user for acceptance testing.
ACCEPTANCE TESTING
The user to ensure that the system functions, as the user actually wanted performs this testing. With prototyping techniques, this stage becomes very much a formality to check the accuracy and completeness of processing. The screen layouts and output should already have been tested during the prototyping phase.
An error in the program code can remain undetected indefinitely. To prevent this from happening the code was tested at various levels. To successfully test a system, each condition, and combinations of conditions had to be tested. Each program was tested and linked to other programs. This unit of program is tested and linked to other units and so on until the complete system has been tested.
The purpose of testing is to ensure that each program is fully tested. To do so a test plan had to be created. The test plan consists of a number of test runs such as the valid paths through the code, and the exception and error handling paths. For each test run there is a list of conditions tested, the test data used and the result expected. The test plan was then reviewed to check that each path through the code is tested correctly. It is the responsibility of the programmer to collect the data that will produce the required test condition.
TEST CASES
TEST DATA Specifications for Online Examination user form1
Test Date Programmer name: Online Examination
Tested By: Project ID: 11107686
Name
The fields are required. Can enter only letters, spaces, hyphens, and apostrophes. No numeric & special characters are allowed( Length upto 32 characters)
Phone Number
only 8 or 10 digit You may use numbers
Email
@yahoo.com Use 4 to 32 characters and start with a letter. You may use letters, numbers, underscores, and one dot(.)
Password password length > than 6 alphanumeric Don’t use your Name or ID
Security Question Select One Use 4 characters or more- not case sensitive
Answer
POSITIVE TEST CASES FOR REGISTRATION FORM
T.C ID PRE-CONDITION T.C DESCRIPTION T.C DATA EXPECTED ACTUAL RESULT
1 User should be on https:// OnlineExamination/registration? And is on Name Field Check the functionality of Name field Akhila Will accept only letters, spaces, hyphens, and apostrophes.Length upto 32 characters. name are required. Ok Pass
2 User should be on https:// OnlineExamination? And is on Name Field Check the functionality of Name field A S Will accept only letters, spaces, hyphens, and apostrophes.Length upto 32 characters. name are required. Ok Pass
3 User should be on https:// OnlineExamination /registration? And is on Name Field Check the functionality of Name field A Satish Will accept only letters, spaces, hyphens, and apostrophes.Length upto 32 characters. name are required. Ok Pass
4 User should be on https:// OnlineExamination /registration? And is on Name Field Check the functionality of Name field Akhila S Will accept only letters, spaces, hyphens, and apostrophes.Length upto 32 characters.name are required. Ok Pass
5 User should be on https:// OnlineExamination /registration?And is on Name Field Check the functionality of Name field pooja sharma Will accept only letters, spaces, hyphens, and apostrophes.Length upto 32 characters.name are required. Ok Pass
6 User should be on https:// OnlineExamination /registration?And is on Phone Number Field Check the functionality of Phone number 98574589 Will accept only numeric upto 8 digit . User ID is required Ok Pass
7 User should be on https:// OnlineExamination /registration? And is on Phone Number Field Check the functionality of Phone number 9990457035 Will accept only numeric upto 8 digit . User Id are required Ok Pass
8 User should be on https:// OnlineExamination /registration? And is on Email Field Check the functionality of ID of sign up option [email protected] Will accept only letters, numbers, underscores, and one dot (.) Ok pass
9 User should be on https:// OnlineExamination registration? And is on Email Field Check the functionality of ID of sign up option [email protected] Will accept only letters, numbers, underscores, and one dot (.) Ok Pass
10 User should be on https:// OnlineExamination /registration? And is on Email Field Check the functionality of ID of sign up option [email protected] Will accept only letters, numbers, underscores, and one dot (.) Ok Pass
User should be on https:// OnlineExamination /registration? And is on Email Field Check the functionality of ID of sign up option [email protected] Will accept only letters, numbers, underscores, and one dot (.) Ok Pass
11 User should be on https:// OnlineExamination /registration? And is on Password Field Check the functionality of password text box avhjklhm Will accept 6 to 32 characters.Capitalisation matters. and don’t use your name ID. Ok Pass
12 User should be on https:// OnlineExamination /registration? And is on Password Field Check the functionality of password text box 654321 Will accept 6 to 32 characters.Capitalisation matters. and don’t use your name or ID. Ok Pass
13 User should be on https:// OnlineExamination /registration?And is on Password Field Check the functionality of password text box 2207** Will accept 6 to 32 characters.Capitalisation matters. and don’t use your name or ID. Ok Pass
14 User should be on https:// OnlineExamination /registration? And is on Password Field Check the functionality of password text box Chinnu1312** Will accept 6 to 32 characters.Capitalisation matters. and don’t use your name or ID. Ok Pass
15 User should be on https:// OnlineExamination /registration? And is on SecurityQuestion field Check the functionality of Security Question What was the make of your first car? Either select one from drop list or type one Ok Pass
16 User should be on https:// OnlineExamination /registration? And is on Answer field Check the functionality of Answer text box Santro Will accept letters and a single space only Ok Pass
NEGATIVE TEST CASES FOR REGISTRATION FORM
T.C ID PRE-CONDITION T.C DESCRIPTION T.C DATA EXPECTED ACTUAL RESULT
1 User should be on https:// OnlineExamination /registration?And is on Name Field Check the functionality of Name field A Will accept only letters, spaces, hyphens, and apostrophes.Length upto 32 characters. name are required. Invalid Fail
2 User should be on https:// OnlineExamination /registration? And is on Name Field Check the functionality of Name field Akhila’s Will accept only letters, spaces, hyphens, and apostrophes.Length upto 32 characters. name are required. Invalid Fail
3 User should be on https:// OnlineExamination /registration?And is on Name Field Check the functionality of Name field Satish Will accept only letters, spaces, hyphens, and apostrophes.Length upto 32 characters.name are required. Invalid Fail
4 User should be on https:// OnlineExamination /registration?And is on Name Field Check the functionality of Name field ‘ Will accept only letters, spaces, hyphens, and apostrophes.Length upto 32 characters. name are required. Invalid Fail
5 User should be on https:// OnlineExamination /registration?And is on Phone Number Field Check the functionality of Phone number 45 456 Will accept only numeric upto 8 digit . User ID are required Invalid Fail
6 User should be on https:// OnlineExamination /registration? And is on Phone Number Field Check the functionality of Phone number Will accept only numeric upto 8 digit . user ID are required Invalid Fail
7 User should be on https:// OnlineExamination /registration? And is on Email Field Check the functionality of ID of sign up option blank Will accept only letters, numbers, underscores, and one dot (.) .The ID must be available. Invalid Fail
8 User should be on https:// OnlineExamination /registration? And is on Email Field Check the functionality of ID of sign up option [email protected] Will accept only letters, numbers, underscores, and one dot (.) .The ID must be available. Invalid Fail
9 User should be on https:// OnlineExamination /registration? And is on Email Field Check the functionality of ID of sign up option #[email protected] Will accept only letters, numbers, underscores, and one dot (.) .The ID must be available. Invalid Fail
10 User should be on https:// OnlineExamination /registration? And is on Password Field Check the functionality of password text box 2# Will accept 6 to 32 characters.Capitalisation matters. and don’t use your name or ID. Invalid Fail
11 User should be on https:// OnlineExamination /registration? And is on Password Field Check the functionality of password text box a123 Will accept 6 to 32 characters.Capitalisation matters. and don’t use your name or ID. Invalid Fail
12 User should be on https:// OnlineExamination /registration? And is on Security Question 2 field Check the functionality of Security Question Drop Down List -Select one- Either select one from drop list or type one Invalid Fail
13 User should be on https:// OnlineExamination /registration? And is onAnswer field Check the functionality of Answer text box blank Will accept anything.But not blank Invalid Fail
8. VERIFICATION AND VALIDATION (V&V)
The objectives of verification, validity activities are to assess and improve the quality of the work products generated during development and modification of the software. Quality depends upon the various attributes like correctness, completeness, consistency, reliability, usefulness, usability, efficiency and conformance to standards.
The terms verification and validation are used synonymously. These are defined as under: –
Verification: “Are we building the product right?”
Validation: “Are we building the right product?”
Verification activities include proving, testing, and reviews. Validation is the process of evaluating software at the end of the software development to ensure compliance with the software requirements. Testing is a common method of validation. Clearly, for high reliability we need to perform both activities. Together, they are often called V&V activities.
The major V&V activities for software development are inspection, reviews, and testing (both static and dynamic). The V&V plan identifies the different V&V tasks for the different phases and specifies how these tasks contribute to the project V&V goals. The methods to be used for performing these V&V activities, the responsibilities and milestones for each of these activities, inputs and outputs for each V&V task, and criteria for evaluating the outputs are also specified.
The two major V&V approaches are testing and inspections. Testing is an activity that can be generally performed only on code. It is an important activity and is discussed in detail in a later chapter. Inspection is a more general activity that can be applied to any work product, including code. Many of the V&V tasks are such that for them, an inspection type of activity is the only possible way to perform the tasks (e.g. trace ability and document evaluation). Due to this, inspections play a significant role in verification.
9. POST IMPLEMENTATION MAINTENANCE AND REVIEW
As we know, creating software is one thing and the implementation of the created software is another. The process of implementing software is much difficult as compared to the task of creating the project. First we have to implement the software on a small scale for removing the bugs and other errors in the project and after removing them we can implement the software on a large scale.
Before we think in terms of implementing the Software on a large basis, we must consider the Hardware requirements.
Whenever we develop software or project a certain hardware and software is being used by the programmer for developing the project. The hardware and software to be used by the programmer for developing the project should be such that it would result in the development of a project, which would satisfy all the basic needs for which the project has been created by the programmer. The Hardware should be such that cost constraints of the Client should also be taken into account without affecting the performance.
9.1 HARDWARE EVALUATION FACTORS
When we evaluate computer hardware, we should first investigate specific physical and performance characteristics for each hardware component to be acquired. These specific questions must be answered concerning many important factors. These hardware evaluation factors questions are summarized in the below figure.
Notice that there is much more to evaluating hardware than determining the fastest and cheapest computing device. For e.g. the question of possible obsolescence must be addressed by making a technology evaluation. The factor of ergonomics is also very important. Ergonomics is the science and technology that tries to ensure that computers and other technologies are “user-friendly”, that is safe, comfortable and easy to use. Connectivity is another important evaluation factor, since so many computer systems are now interconnected within wide area or local area telecommunications networks.
HARDWARE EVALUATION FACTORS
1) Performance
2) Cost
3) Reliability
4) Availability
5) Compatibility
6) Modularity
7) Technology
8) Ergonomics
9) Connectivity
10) Environmental requirements
11) Software
12) Support
9.2 SOFTWARE EVALUATION FACTORS
Software can be evaluated according to many factors similar to the hardware evaluation. Thus the factors of performance, cost, reliability, compatibility, modularity, technology, ergonomics, and support should be used to evaluate proposed software acquisitions. In addition, however, the software evaluation factors are summarized in below figure. For e.g. some software packages require too much memory capacity and are notoriously slow, hard to use, or poorly documented. They are not a good selection for most end users, even if offered at attractive prices.
SOFTWARE EVALUATION FACTORS:
1. EFFICIENCY: is the software a well-written system of computer instructions that does not use much memory capacity or CPU time?
2. FLEXIBILITY: can it handle its processing assignments easily without major modifications?
3. SECURITY: does it provide control procedures for errors, malfunctions and improper use?
4. LANGUAGE: do our computer programmers and users write it in a programming language that is used?
5. DOCUMENTATION: is the s/w well documented? Does it include helpful user instructions?
6. HARDWARE: does existing hardware have the features required to best use this software?
7. Other characteristics of hardware such as its performance, what about the cost, how much is reliable and etc.
9.3 CONVERSION AND TRAINING
An important aspect of is to make sure that the new design is implemented to establish standards. The term implementation has different meanings, ranging form the conversion of a basic application to a complete replacement of a computer system. Implementation is used here to mean the process of converting a new or revise system into an operational one. Conversion is one aspect of implementation. Conversion means changing form one system to another. The objective is to put the tested system into operation while holding costs, risks, and personnel irritation to a minimum. It involves creating computer-compatible files, training the operation staff, and installing terminal and hardware. A critical aspect of conversion is not disrupting the functioning of the organization.
When a new system is used over and old, existing and running one, there are always compatibility errors. These errors are caused because of the lack of equipment or personnel to work the new system. Running any specified system at an organization does require some or other hardware or, in this case, software requirement as well.
Conversion is one aspect of implementation review & software maintenance.
There are three types of implementation:
1. Implementation of a computer system to replace a manual system. The problems encountered are converting files, training users, creating accurate files and verifying printouts for integrity.
2. Implementation of a new computer system to replace an existing one. This is usually a difficult conversion. If not properly planned there can be many problems. Some large computer systems have taken as long as year to convert.
3. Implementation of a modified application to replace an existing one, using the same computer. This type of conversion is relatively easy to handle, provided there are no major changes in the files.
9.4 TRAINING NEEDS
Training needs refer to the gaining of knowledge required for running the system.
First of all the system is a computer based system therefore the person should have good knowledge about computer and its working.
He should know how to use software’s on the computer.
For a better usage and working of the software the organization should appoint a person who has good knowledge of all the required software. The organization gets a person trained through different institutes present in the market. The training should be as per the above requirements.
10. COST ESTIMATION OF THE PROJECT
Cost in a project is due to the requirements for software, hardware, and human resources. Hardware resources are computer time, terminal time and memory required for the project. Software resources include the tools and compilers needed during development. The bulk of cost of software development is due to human resources needed. Cost estimates are determined in terms of person-months (PM).
Total No. Of Persons Involved In This Project:
1. Administrator
2. Senior Programmer
3. Junior Programmers
4. On line Users.
Since this Project will complete in 4 months
COST ESTIMATE: (Salary of Project Manager + Salary of Senior Programmer + 2 * Salary of Junior Programmer) * 2
11. GANTT & PERT CHART
GANT CHART
Gantt charts mainly used to allocate resources to activities. The resources allocated to activities include staff, hardware, and software. Gantt charts (named after its developer Henry Gantt) are useful for resource planning. A Gantt chart is special type of bar chart where each bar represents an activity. The bars are drawn along a timeline. The length of each bar is proportional to the duration of the time planned for the corresponding activity.
Gantt chart is a project scheduling technique. Progress can be represented easily in a Gantt chart, by coloring each milestone when completed. The project will start in the month of June and end of July.
System Design
Detailed Design
Coding
Unit Testing
Test Plan
Testing
1st June 15th June 1st July 31st July
Pert Chart
PERT (Project Evaluation and Review Technique) charts consist of a network of boxes and arrows. The boxes represent activities and the arrows represent task dependencies.
PERT chart represents the statistical variations in the project estimates assuming a normal distribution. Thus in a PERT chart instead of making a single estimate for each task, pessimistic, likely, and optimistic estimates are also made. The boxes of PERT charts are usually annotated with the pessimistic, likely, and optimistic estimates for every task. Since all possible completion times between the minimum and maximum durations for every task have to be considered, there are many critical paths, depending on the permutations of the estimates for each task. This makes critical path analysis in PERT charts very complex. A critical path in a PERT chart is shown by using thicker arrows.
Task ES EF LS LF ST
Specification Part 0 15 0 15 0
Design Database Part 15 60 15 60 0
Design GUI Part 15 45 90 120 75
Code Database Part 60 165 60 165 0
Code GUI Part 45 90 120 165 75
Integrate and Test 165 285 165 285 0
Write User Manual 15 75 225 285 210
Figure A : Different Tasks for the ONLINE EXAMINATION SYSTEM are shown in above table.
FIGURE B : PERT chart representation of the online examination system.
PERT charts are a more sophisticated form of activity chart. In activity diagrams only the estimated task durations are represented. Since the actual durations might vary from the estimated durations, the utility of the activity diagrams is limited.
12. SECURITY AND VALIDATION CHECKS
In this project we have used following validation checks.
While entering the data into the form it will check for the name of the client is properly filled & it should not be null.
Whenever we enter the data for the new customer, company, or user will automatically check the details from the database tables and also generate the connection number automatically.
Similarly in the complaint table complaint number will generate automatically.
Entered text / number should not exceed the limit (width).
Almost for all fields we have used the validation for example if name of the fields requires the text type of data then it will check for the string and if the data is numeric then it will check if the number entered is proper numeric or not.
JSP Provides Security
• Evidence-based security (authentication)
• Based on user identity and code identity
• Configurable policies
• Imperative and declarative interfaces
13. SCOPE OF FUTURE APPLICATION
I am confident that this software package can be readily used by non-programming personal avoiding human handled chance of error. This project is used by two types of users
i. Online Users.
ii. Administrator .
Online users can see the required articles, give feedbacks, online examination without going to any other center.
Administrator can maintain daily updates in the questions etc.. Administrator is must be an authorized user.
The decision to automate generally depends on the needs to have accurate, consistent and timely data in a variety of reporting formats. But the most important factor that should be considered is –
Be sure to take future growth into consideration and evaluate whether the software package could be modified if the organization expands in the future or you need to revise the system.
The next generation of Windows-based computerized systems would be changing the way owners and management think about running their businesses. It would a powerful tool that gives them more ways to get their financial Information so that they can better manage and grow their business.
The next generation of systems would take advantage of the latest technologies, including Microsoft Windows XP and Orcale11i to offer access and integrate with all aspects of a business. Keeping this in view we could develop systems that would work efficiently and integrate seamlessly in virtually any industry setting, even up to mid-sized corporations and divisions of larger organizations.
Consider another setting, where the users are not comfortable on computers, for such users we can develop systems where the users can have their own personalized menu setup in the accounting software so that they no longer have to search around to find what they need.
Now consider the Internet. This wide open information exchange network comes with many benefits for businesses, including breaking down physical barriers as to where he/she can consult to the companies.
Adding other capabilities can be added time to time. These are
• Application may be installed client server.
• Application can upgraded according to user’s and administrator’s requirements with little changes made
• Application may be transferred to latest RDMBS like Oracle with little changes in current code. Use for Security purpose
NOTE: In a nutshell we have a lot of scope to further enhance the futures and functionalities of the proposed Solution.
14. CONCLUSION
This project is designed to meet the requirements of the users for online examination. It has been developed in JSP, SERVLETS, keeping in mind the specifications of the system.
For designing the system we have used simple data flow diagrams.
Overall the project teaches us the essential skills like:
Using system analysis and design techniques like data flow diagram in designing the system.
Understanding the database handling and query processing using My SQL .
15. Bibliography
1. Senn James A : Analysis and Design of Information Systems, McGraw Hill, International Ed, 1989.
2. O’Brien Jamea A : Management Information Systems, Galgotia Publications Pvt Ltd, New Delhi, 1998.
3. Laudon & Laudon : Management Information Systems, Organisation and Technology, PHI, New Delhi, 1998.
4. Wetherebe James : Systems Analysis and Design, Galgotia Publications Pvt Ltd, New Delhi, 1990