1.

INTRODUCTION
Automated mobile results is a web application through which students can receive
their examination results through SMS without any type of cost and registration. We
have analyzed the needs of the students, and thus developed a web based application,
for providing examination results and associated services through SMS by using SMS
gateway. In existing system students view their examination results in university
websites which is time taking process as all the students will be trying to access the
results at a time which in turn leads to server crash. By considering all this issues
associated with the manual process we have developed a web application for the
students in viewing the results with less time consumption.Admin will control our
website.

With the growing number of mobile and embedded platforms coming to market, the
ability to upgrade a device in the field is a requirement found on increasing number of
business-buyer check lists.

1.1 Purpose

The main purpose of the project is to reduce the complexity of students in viewing
the examination results. Here the complexity means students viewing the results
through internet, which is a time taking process due to heavy server loads which in turn
leads to server crash. In order to overcome these limitations we are implementing this
system. By using this system the student receives the examination results in the form of
short message service to their respective mobile number without any type of cost and
registration by using SMS gateway.

1.2 Scope

The scope of the project involves sending the examination results of the students to
their respective mobiles in the form of short message service without any type of cost
and registration.

1.3 Goals

The aim of our application is to automate the existing system and provide user
friendly environment in which students can view the results through SMS. We have
analyzed the student needs and by considering all the issues associated with the manual
process we have developed a web application for the students in viewing the results
with less time consumption.

1.4 Features
1
  This system provides an easy view of results with free of cost and registration.

 This system does not need an internet connection, Personal computer.

 By using this system time consumption will be reduced.

 This system overcomes the limitations of the existing system by avoiding server
crashes when all the students are trying to access the results at a time.

 This system is globally applicable for any type of educational institutions.

2. SYSTEM ANALYSIS AND DECRIPTION

2.1 Existing system

In this system we view the exam results in universities official websites. It is a time
taking process due to heavy server loads. This system needs PC with internet
connection. In spite of uploading the results in the university official websites it takes
much time to display the results due to heavy server loads as all the students try to
access at a time which in turn leads to server crash of the respective university websites.
Once the results are sent to different college administrators by the respective university
the results will be displayed in the college notice boards.

2.2 Proposed system

Till now there is no such an application where in the student’s exam results will be
sent to their respective mobile phone numbers through SMS which is free of cost and
without any type of registration. In this system the university will send the database of
marks of all the students to different college administrators in form of excel sheets
according to branch wise. Then the application involves the administrator to send the
results of all students irrespective of all years and branches to respective mobile
numbers of students corresponding to their hall ticket numbers by making use of SMS
gateway. This system overcomes the disadvantages of existing system. A standard set of
procedures must be established for implementing any form of automated software
updates in order to minimize risks and maximize the potential of automated update
mechanisms

2.3 Overall description

In our application, we have two modules Student and Admin. Student is the one who
will use our website in order to use the facilities provided by our application. Admin
will maintain the whole site all the updations regarding the results, student profiles etc.

2.4 Module description

There are two modules in our system:

 Admin module
2
  Student module

Admin module: This module contains the total information about the student
examination results. Administrator receives the entire results of college according to
branch wise from respective university. Then this application involves the administrator
to send the results of all students irrespective of different branches to respective mobile
numbers by using SMS gateway.
Student module: This module contains the total student profiles (Student hall ticket
number, branch details and phone number details). If the student switch on to another
mobile number then the details must be updated.

2.5 Feasibility study

2.5.1 Technical feasibility

Evaluating the technical feasibility is the trickiest part of a feasibility study. This
is because, at this point in time, not too many detailed design of the system, making it
difficult to access issues like performance, costs on (on account of the kind of
technology to be deployed) etc.
A number of issues have to be considered while doing a technical analysis.
i) Understand the different technologies involved in the proposed system:
Before commencing the project, we have to be very clear about what are the
Technologies that are to be required for the development of the new system.
ii) Find out whether the organization currently possesses the required
technologies:
Is the required technology available with the organization?
If so is the capacity sufficient?
For instance –
“Will the current printer be able to handle the new reports and forms required for the
new system?”

2.5.2 Operational feasibility

Proposed projects are beneficial only if they can be turned into information systems
that will meet the organizations operating requirements. Simply stated, this test of
feasibility asks if the system will work when it is developed and installed. Are there
major barriers to Implementation? Here are questions that will help test the operational
feasibility of a project:
 Is there sufficient support for the project from management from users? If
the current system is well liked and used to the extent that persons will not be
able to see reasons for change, there may be resistance.
 Are the current business methods acceptable to the user? If they are not,

3
Users may welcome a change that will bring about a more operational and useful
systems.
 Have the user been involved in the planning and development of the project?
Early involvement reduces the chances of resistance to the system and in
General and increases the likelihood of successful project.
Since the proposed system was to help reduce the hardships encountered
In the existing manual system, the new system was considered to be operational
feasible.

2.5.3 Economic feasibility

Economic feasibility attempts 2 weigh the costs of developing and implementing

a new system, against the benefits that would accrue from having the new system in
place. This feasibility study gives the top management the economic justification for the
new system.
A simple economic analysis which gives the actual comparison of costs and
benefits are much more meaningful in this case. In addition, this proves to be a useful
point of reference to compare actual costs as the project progresses.
There could be various types of intangible benefits on account of automation. These
could include increased customer satisfaction, improvement in product quality better
decision making timeliness of information, expediting activities, improved accuracy of
operations.

2.6 SDLC Model

2.6.1 The incremental, iterative software engineering life cycle:

When we defining and constructing credit card validation systems will uncover
many requirements that may be difficult at outset. Instead knowledge of the system and
requirements will grow as work progress the whole software engineering process is
designed to uncover details and incompatibilities in the requirements that may not be
obvious to customer and bankers at outset.

Several cases or increments of software development additional increases will be

build and delivered in successive increment system normally involves as are deliver
successive new versions, the development of first version from sketch called green field
development is special case of incremental development the development of first
increment is an important activity series we establish the architectural base that must
last for the entire system’s life time.

2.6.2 Water fall life cycle model:

4
 Waterfall model states that the phases (analysis, design, and coding, testing, support)
are systematized in a linear order and each phase should accomplished entirely earlier of
the next phase begins.

In this way the step by step phase initially analysing phase is completed and that
output takes place at the end of analyze phase after that output will be given as input for
the design phase, depending on the inputs it generates all design steps ,like ways all
phases processed and produced all successful outputs, And will to find out whether the
project is pursuing on the exact path or not. If not the project may be discard or any
other action takes place to continue. The model is the most commonly used and also
known as linear sequential lifecycle model.

Advantages:

1. This model is very easy to use and implement.

2. Each phase is completed at a time and processed.
3. This model better works for smaller projects if only the requirements are well
understood.
4. In each phase have deliverables and that must be reviewed.

Disadvantages:

1. If the requirements are gathered are inaccurate then the final product is
inaccurate and the error is known in the final phase of the model. Any sort of
errors that cannot be detected in any previous phase.
2. For long, object-oriented, complex and ongoing projects it’s a poor model.
3. This model has high risks.

5
 Fig: Waterfall Lifecycle Model

2.6.3 Prototype model

In this model the requirements are gathered firstly, and the prototype is deployed
according to the requirements. This prototype is a quick design which goes through the
coding, design and testing. The phases are not done in detail. By seeing this prototype
the client feels like a real system, so that the client understands the entire requirements
of the systems.

Advantages:

1. During the development process the developers are interestingly engaged.

2. The prototype developed that is used by the users for well understanding of the
methodology
3. The user involvement is increased and improved.
4. The flaws and faults are identified early.
5. The user’s opinion about the product is known early which leads to an improved
system.

Disadvantages:
6
 1. This model focuses on design quite than functionality.
2. The model is implemented firstly and then errors are evaluated later which
becomes a complex process
3. The model is also known as throw-away prototype.

More time spent on development of the prototype that result in delay of the final
product.

Requirements

Gathering

Quick Design

Build
Refine
Prototype
Requiremen

Customer
Evaluation of
the prototype

Design

Implement

Test

Maintain
Fig: Prototyping Methodology

3.SOFTWARE REQUIREMENT SPECIFICATION

7
3.1 Software interfaces

 Microsoft .Net framework 4.0

 ASP.NETMicrosoft

 C#.Net languageMicrosoft

 SQL Server 2008

 ADO.NET

3.2 Hardware interfaces

Processor : Intel processors

Ram : 256 MB or more

Hard disk : 40 GB hard disk recommended for primary partition.

4. LANGUAGE IMPLEMENTATION
4.1 Microsoft .NET framework

8
 The .NET Framework is a new computing platform that simplifies application
development in the highly distributed environment of the Internet. The .NET
Framework is designed to fulfill the following objectives:

 To provide a consistent object-oriented programming environment whether

object code is stored and executed locally, executed locally but Internet-
distributed, or executed remotely.
 To provide a code-execution environment that minimizes software deployment
and versioning conflicts.

 To provide a code-execution environment that guarantees safe execution of

code, including code created by an unknown or semi-trusted third party.
 To provide a code-execution environment that eliminates the performance
problems of scripted or interpreted environments.

 To make the developer experience consistent across widely varying types of

applications, such as Windows-based applications and Web-based applications.

 To build all communication on industry standards to ensure that code based on

the .NET Framework can integrate with any other code.

The .NET Framework has two main components: the common language runtime and
the .NET Framework class library. The common language runtime is the foundation of
the .NET Framework. You can think of the runtime as an agent that manages code at
execution time, providing core services such as memory management, thread
management, and remoting, while also enforcing strict type safety and other forms of
code accuracy that ensure security and robustness. In fact, the concept of code
management is a fundamental principle of the runtime. Code that targets the runtime is
known as managed code, while code that does not target the runtime is known as
unmanaged code.

9
 The class library, the other main component of the .NET Framework, is a
comprehensive, object-oriented collection of reusable types that you can use to develop
applications ranging from traditional command-line or graphical user interface (GUI)
applications to applications based on the latest innovations provided by ASP.NET, such
as Web Forms and XML Web services.

The .NET Framework can be hosted by unmanaged components that load the
common language runtime into their processes and initiate the execution of managed
code, thereby creating a software environment that can exploit both managed and
unmanaged features. The .NET Framework not only provides several runtime hosts, but
also supports the development of third-party runtime hosts.

For example, ASP.NET hosts the runtime to provide a scalable, server-side

environment for managed code. ASP.NET works directly with the runtime to enable
Web Forms applications and XML Web services, both of which are discussed later in
this topic.

Internet Explorer is an example of an unmanaged application that hosts the runtime

(in the form of a MIME type extension). Using Internet Explorer to host the runtime
enables you to embed managed components or Windows Forms controls in HTML
documents. Hosting the runtime in this way makes managed mobile code (similar to
Microsoft® ActiveX® controls) possible, but with significant

The following illustration shows the relationship of the common language runtime
and the class library to your applications and to the overall system. The illustration also
shows how managed code operates within a larger architecture.

Features of the Common Language Runtime

The common language runtime manages memory, thread execution, code execution,
code safety verification, compilation, and other system services. These features are
intrinsic to the managed code that runs on the common language runtime.

With regards to security, managed components are awarded varying degrees of trust,
depending on a number of factors that include their origin (such as the Internet,
enterprise network, or local computer). This means that a managed component might or
might not be able to perform file-access operations, registry-access operations, or other
sensitive functions, even if it is being used in the same active application.

The runtime enforces code access security. For example, users can trust that an
executable embedded in a Web page can play an animation on screen or sing a song, but
cannot access their personal data, file system, or network.

The runtime also enforces code robustness by implementing a strict type- and
code-verification infrastructure called the common type system (CTS). The CTS
ensures that all managed code is self-describing. The various Microsoft and third-party

10
language compilers generate managed code that conforms to the CTS. This means that
managed code can consume other managed types and instances, while strictly enforcing
type fidelity and type safety.

In addition, the managed environment of the runtime eliminates many common

software issues. For example, the runtime automatically handles object layout and
manages references to objects, releasing them when they are no longer being used. This
automatic memory management resolves the two most common application errors,
memory leaks and invalid memory references.

The runtime also accelerates developer productivity. For example, programmers can
write applications in their development language of choice, yet take full advantage of
the runtime, the class library, and components written in other languages by other
developers. Any compiler vendor who chooses to target the runtime can do so.
Language compilers that target the .NET Framework make the features of the .NET
Framework available to existing code written in that language, greatly easing the
migration process for existing applications.

While the runtime is designed for the software of the future, it also supports software
of today and yesterday. Interoperability between managed and unmanaged code enables
developers to continue to use necessary COM components and DLLs.

The runtime is designed to enhance performance. Although the common language

runtime provides many standard runtime services, managed code is never interpreted. A
feature called just-in-time (JIT) compiling enables all managed code to run in the native
machine language of the system on which it is executing. Meanwhile, the memory
manager removes the possibilities of fragmented memory and increases memory
locality-of-reference to further increase performance.

Finally, the runtime can be hosted by high-performance, server-side applications,

such as Microsoft® SQL Server™ and Internet Information Services (IIS). This
infrastructure enables you to use managed code to write your business logic, while still
enjoying the superior performance of the industry's best enterprise servers that support
runtime hosting.

.NET Framework Class Library

The .NET Framework class library is a collection of reusable types that tightly
integrate with the common language runtime. The class library is object oriented,
providing types from which your own managed code can derive functionality. This not
only makes the .NET Framework types easy to use, but also reduces the time associated
with learning new features of the .NET Framework. In addition, third-party components
can integrate seamlessly with classes in the .NET Framework.

For example, the .NET Framework collection classes implement a set of interfaces
that you can use to develop your own collection classes. Your collection classes will
blend seamlessly with the classes in the .NET Framework.
11
 As you would expect from an object-oriented class library, the .NET Framework
types enable you to accomplish a range of common programming tasks, including tasks
such as string management, data collection, database connectivity, and file access. In
addition to these common tasks, the class library includes types that support a variety of
specialized development scenarios. For example, you can use the .NET Framework to
develop the following types of applications and services:

 Console applications.
 Scripted or hosted applications.

 Windows GUI applications (Windows Forms).

 ASP.NET applications.

 XML Web services.

 Windows services.

For example, the Windows Forms classes are a comprehensive set of reusable types
that vastly simplify Windows GUI development. If you write an ASP.NET Web Form
application, you can use the Web Forms classes.

Client Application Development

Client applications are the closest to a traditional style of application in Windows-

based programming. These are the types of applications that display windows or forms
on the desktop, enabling a user to perform a task. Client applications include
applications such as word processors and spreadsheets, as well as custom business
applications such as data-entry tools, reporting tools, and so on. Client applications
usually employ windows, menus, buttons, and other GUI elements, and they likely
access local resources such as the file system and peripherals such as printers.

Another kind of client application is the traditional ActiveX control (now replaced by
the managed Windows Forms control) deployed over the Internet as a Web page. This
application is much like other client applications: it is executed natively, has access to
local resources, and includes graphical elements.

In the past, developers created such applications using C/C++ in conjunction with
the Microsoft Foundation Classes (MFC) or with a rapid application development
(RAD) environment such as Microsoft® Visual Basic®. The .NET Framework
incorporates aspects of these existing products into a single, consistent development
environment that drastically simplifies the development of client applications.

The Windows Forms classes contained in the .NET Framework are designed to be
used for GUI development. You can easily create command windows, buttons, menus,
toolbars, and other screen elements with the flexibility necessary to accommodate
shifting business needs.

12
 For example, the .NET Framework provides simple properties to adjust visual
attributes associated with forms. In some cases the underlying operating system does
not support changing these attributes directly, and in these cases the .NET Framework
automatically recreates the forms. This is one of many ways in which the .NET
Framework integrates the developer interface, making coding simpler and more
consistent.

Unlike ActiveX controls, Windows Forms controls have semi-trusted access to a

user's computer. This means that binary or natively executing code can access some of
the resources on the user's system (such as GUI elements and limited file access)
without being able to access or compromise other resources. Because of code access
security, many applications that once needed to be installed on a user's system can now
be safely deployed through the Web. Your applications can implement the features of a
local application while being deployed like a Web page.

Server Application Development

Server-side applications in the managed world are implemented through runtime

hosts. Unmanaged applications host the common language runtime, which allows your
custom managed code to control the behavior of the server. This model provides you
with all the features of the common language runtime and class library while gaining the
performance and scalability of the host server.

The following illustration shows a basic network schema with managed code running
in different server environments. Servers such as IIS and SQL Server can perform
standard operations while your application logic executes through the managed code.

Server-side managed code

ASP.NET is the hosting environment that enables developers to use the .NET
Framework to target Web-based applications. However, ASP.NET is more than just a
runtime host; it is a complete architecture for developing Web sites and Internet-
distributed objects using managed code. Both Web Forms and XML Web services use
IIS and ASP.NET as the publishing mechanism for applications, and both have a
collection of supporting classes in the .NET Framework.

XML Web services, an important evolution in Web-based technology, are

distributed, server-side application components similar to common Web sites. However,
unlike Web-based applications, XML Web services components have no UI and are not
targeted for browsers such as Internet Explorer and Netscape Navigator. Instead, XML
Web services consist of reusable software components designed to be consumed by
other applications, such as traditional client applications, Web-based applications, or
even other XML Web services. As a result, XML Web services technology is rapidly
moving application development and deployment into the highly distributed
environment of the Internet.

13
 If you have used earlier versions of ASP technology, you will immediately notice the
improvements that ASP.NET and Web Forms offers. For example, you can develop Web
Forms pages in any language that supports the .NET Framework. In addition, your code
no longer needs to share the same file with your HTTP text (although it can continue to
do so if you prefer). Web Forms pages execute in native machine language because, like
any other managed application, they take full advantage of the runtime. In contrast,
unmanaged ASP pages are always scripted and interpreted. ASP.NET pages are faster,
more functional, and easier to develop than unmanaged ASP pages because they interact
with the runtime like any managed application.

The .NET Framework also provides a collection of classes and tools to aid in
development and consumption of XML Web services applications. XML Web services
are built on standards such as SOAP (a remote procedure-call protocol), XML (an
extensible data format), and WSDL ( the Web Services Description Language). The
.NET Framework is built on these standards to promote interoperability with non-
Microsoft solutions.

For example, the Web Services Description Language tool included with the .NET
Framework SDK can query an XML Web service published on the Web, parse its
WSDL description, and produce C# or Visual Basic source code that your application
can use to become a client of the XML Web service. The source code can create classes
derived from classes in the class library that handle all the underlying communication
using SOAP and XML parsing. Although you can use the class library to consume XML
Web services directly, the Web Services Description Language tool and the other tools
contained in the SDK facilitate your development efforts with the .NET Framework.

If you develop and publish your own XML Web service, the .NET Framework
provides a set of classes that conform to all the underlying communication standards,
such as SOAP, WSDL, and XML. Using those classes enables you to focus on the logic
of your service, without concerning yourself with the communications infrastructure
required by distributed software development.

Finally, like Web Forms pages in the managed environment, your XML Web service
will run with the speed of native machine language using the scalable communication of
IIS.

4.2 Active Server Pages.NET

14
ASP.NET is a programming framework built on the common language runtime that can
be used on a server to build powerful Web applications. ASP.NET offers several
important advantages over previous Web development models:

 Enhanced Performance. ASP.NET is compiled common language

runtime code running on the server. Unlike its interpreted predecessors,
ASP.NET can take advantage of early binding, just-in-time compilation,
native optimization, and caching services right out of the box. This
amounts to dramatically better performance before you ever write a line
of code.

 World-Class Tool Support. The ASP.NET framework is complemented

by a rich toolbox and designer in the Visual Studio integrated
development environment. WYSIWYG editing, drag-and-drop server
controls, and automatic deployment are just a few of the features this
powerful tool provides.

 Power and Flexibility. Because ASP.NET is based on the common

language runtime, the power and flexibility of that entire platform is
available to Web application developers. The .NET Framework class
library, Messaging, and Data Access solutions are all seamlessly
accessible from the Web. ASP.NET is also language-independent, so you
can choose the language that best applies to your application or partition
your application across many languages. Further, common language
runtime interoperability guarantees that your existing investment in
COM-based development is preserved when migrating to ASP.NET.

 Simplicity. ASP.NET makes it easy to perform common tasks, from

simple form submission and client authentication to deployment and site
configuration. For example, the ASP.NET page framework allows you to
build user interfaces that cleanly separate application logic from
presentation code and to handle events in a simple, Visual Basic - like
forms processing model. Additionally, the common language runtime
simplifies development, with managed code services such as automatic
reference counting and garbage collection.

 Manageability. ASP.NET employs a text-based, hierarchical

configuration system, which simplifies applying settings to your server
environment and Web applications. Because configuration information is
stored as plain text, new settings may be applied without the aid of local
administration tools. This "zero local administration" philosophy extends
to deploying ASP.NET Framework applications as well. An ASP.NET
Framework application is deployed to a server simply by copying the
necessary files to the server. No server restart is required, even to deploy
or replace running compiled code.

 Scalability and Availability. ASP.NET has been designed with

scalability in mind, with features specifically tailored to improve
15
 performance in clustered and multiprocessor environments. Further,
processes are closely monitored and managed by the ASP.NET runtime,
so that if one misbehaves (leaks, deadlocks), a new process can be
created in its place, which helps keep your application constantly
available to handle requests.

 Customizability and Extensibility. ASP.NET delivers a well-factored

architecture that allows developers to "plug-in" their code at the
appropriate level. In fact, it is possible to extend or replace any
subcomponent of the ASP.NET runtime with your own custom-written
component. Implementing custom authentication or state services has
never been easier.

 Security. With built in Windows authentication and per-application

configuration, you can be assured that your applications are secure.

Language Support
The Microsoft .NET Platform currently offers built-in support for three
languages: C#, Visual Basic, and JScript.

What is ASP.NET Web Forms?

The ASP.NET Web Forms page framework is a scalable common language runtime
programming model that can be used on the server to dynamically generate Web pages.

Intended as a logical evolution of ASP (ASP.NET provides syntax compatibility with

existing pages), the ASP.NET Web Forms framework has been specifically designed to
address a number of key deficiencies in the previous model. In particular, it provides:

 The ability to create and use reusable UI controls that can encapsulate
common functionality and thus reduce the amount of code that a page
developer has to write.
 The ability for developers to cleanly structure their page logic in an
orderly fashion (not "spaghetti code").

 Theability for development tools to provide strong WYSIWYG design

support for pages (existing ASP code is opaque to tools)

ASP.NET Web Forms pages are text files with an .aspx file name extension. They
can be deployed throughout an IIS virtual root directory tree. When a browser client
requests .aspx resources, the ASP.NET runtime parses and compiles the target file into
a .NET Framework class. This class can then be used to dynamically process incoming
requests. (Note that the .aspx file is compiled only the first time it is accessed; the
compiled type instance is then reused across multiple requests).

An ASP.NET page can be created simply by taking an existing HTML file and
changing its file name extension to .aspx (no modification of code is required). For
example, the following sample demonstrates a simple HTML page that collects a user's

16
name and category preference and then performs a form postback to the originating
page when a button is clicked:

ASP.NET provides syntax compatibility with existing ASP pages. This includes
support for <% %> code render blocks that can be intermixed with HTML content
within an .aspx file. These code blocks execute in a top-down manner at page render
time.

Code-Behind Web Forms

ASP.NET supports two methods of authoring dynamic pages. The first is the method
shown in the preceding samples, where the page code is physically declared within the
originating .aspx file. An alternative approach--known as the code-behind method--
enables the page code to be more cleanly separated from the HTML content into an
entirely separate file.

Introduction to ASP.NET Server Controls

In addition to (or instead of) using <% %> code blocks to program dynamic content,
ASP.NET page developers can use ASP.NET server controls to program Web pages.
Server controls are declared within an .aspx file using custom tags or intrinsic HTML
tags that contain a runat="server" attribute value. Intrinsic HTML tags are handled by
one of the controls in the System.Web.UI.HtmlControls namespace. Any tag that
doesn't explicitly map to one of the controls is assigned the type of
System.Web.UI.HtmlControls.HtmlGenericControl.

Server controls automatically maintain any client-entered values between round

trips to the server. This control state is not stored on the server (it is instead stored
within an <input type="hidden"> form field that is round-tripped between requests).
Note also that no client-side script is required.

In addition to supporting standard HTML input controls, ASP.NET enables

developers to utilize richer custom controls on their pages. For example, the following
sample demonstrates how the <asp:adrotator> control can be used to dynamically
display rotating ads on a page.

1. ASP.NET Web Forms provide an easy and powerful way to build

dynamic Web UI.
2. ASP.NET Web Forms pages can target any browser client (there are no
script library or cookie requirements).

3. ASP.NET Web Forms pages provide syntax compatibility with existing

ASP pages.

17
 4. ASP.NET server controls provide an easy way to encapsulate common
functionality.

5. ASP.NET ships with 45 built-in server controls. Developers can also

use controls built by third parties.

6. ASP.NET server controls can automatically project both uplevel and

downlevel HTML.

7. ASP.NET templates provide an easy way to customize the look and

feel of list server controls.

4.3 Active data object.NET

ADO.NET is an extension of the ADO data access model which consist of

only the connected architecture. The Microsoft organization has realized the data related
operations and have studied and analyzed different data related technologies among
which they found ADO to be interesting , later on they extended the features of the
ADO and defined own data related technology by refining the ADO and hence given the

18
name as ADO.Net. The Microsoft organization , grouped some set of namespaces
which can operates on data , and put together into technology called ADO.NET. The
ADO.Net technology enhances the features of the ADO, which consist of only
connected architecture where as in ADO.NET they have introduces a disconnected
architecture.

The connected architecture important feature is the data provider, which consists of
the four important objects namely connection, command, data reader and data adapter.
The connection object provides the connection to the data store nothing but to the back
end database servers. The connection class consists of default constructors and
parameterized constructors.

Command object consists of three methods namely execute non query, execute reader
and execute scalar. The execute non query will returns the integer values as an output
which indicates how many records have been updated, or modified etc. the second
method execute reader returns the complete records been affected by the operations ,
whereas execute scalar returns the first row first column value remaining will be
neglected.
The third object in the connected archecture is the datareader ,which reads the data in
a forward only mode , that’s means its retrieves the data from the data base server and
forwards it to the application. The another object is the dataadapter which acts like an
interface or bridge between the connected architecture and disconnected architecture.
In the disconnected architecture the important feature is the dataset. It’s a collection
of datatables and datarows and the datatables will be linked using the data relations .
when the dataset need to be filled ,its request to the data adapter which in turn fills the
dataset by making use of fill method of data adapter.

Features of ADO.NET are as follows:

1. ADO.NET is the next evolution of ADO for the .Net Framework.

2. ADO.NET was created with n-Tier, statelessness and XML in the forefront.
Two new objects, the DataSet and DataAdapter, are provided for these
scenarios.

3. ADO.NET can be used to get data from a stream, or to store data in a cache
for updates.

4. There is a lot more information about ADO.NET in the documentation.

5. Remember, you can execute a command directly against the database in order
to do inserts, updates, and deletes. You don't need to first put data into a
DataSet in order to insert, update, or delete it.

6. Also, you can use a DataSet to bind to the data, move through the data, and
navigate data relationships
19
4.4 Microsoft sql server

Microsoft SQL Server is a Structured Query Language (SQL) based, client/server

relational database. Each of these terms describes a fundamental part of the architecture
of SQL Server.
Database
A database is similar to a data file in that it is a storage place for data. Like a data
file, a database does not present information directly to a user; the user runs an
application that accesses data from the database and presents it to the user in an
understandable format.

A database typically has two components: the files holding the physical database and
the database management system (DBMS) software that applications use to access data.
The DBMS is responsible for enforcing the database structure, including:

 Maintaining the relationships between data in the database.

 Ensuring that data is stored correctly and that the rules defining data
relationships are not violated.

Client/Server

In a client/server system, the server is a relatively large computer in a central

location that manages a resource used by many people. When individuals need to use
the resource, they connect over the network from their computers, or clients, to the
server.
Examples of servers are: In a client/server database architecture, the database files
and DBMS software reside on a server. A communications component is provided so
applications can run on separate clients and communicate to the database server over a
network. The SQL Server communication component also allows communication
between an application running on the server and SQL Server.

Server applications are usually capable of working with several clients at the same
time. SQL Server can work with thousands of client applications simultaneously. The
server has features to prevent the logical problems that occur if a user tries to read or
modify data currently being used by others.

While SQL Server is designed to work as a server in a client/server network, it is

also capable of working as a stand-alone database directly on the client. The scalability
and ease-of-use features of SQL Server allow it to work efficiently on a client without
consuming too many resources.
Structured Query Language (SQL)

To work with data in a database, you must use a set of commands and statements
(language) defined by the DBMS software. There are several different languages that
can be used with relational databases; the most common is SQL. Both the American
National Standards Institute (ANSI) and the International Standards Organization (ISO)

20
have defined standards for SQL. Most modern DBMS products support the Entry Level
of SQL-92, the latest SQL standard (published in 1992).

SQL Server Features

Microsoft SQL Server supports a set of features that result in the following benefits:

Ease of installation, deployment, and use

SQL Server includes a set of administrative and development tools that improve your
ability to install, deploy, manage, and use SQL Server across several sites.

Scalability
The same database engine can be used across platforms ranging from laptop
computers running Microsoft Windows® 95/98 to large, multiprocessor servers running
Microsoft Windows NT®, Enterprise Edition.

Data warehousing
SQL Server includes tools for extracting and analyzing summary data for online
analytical processing (OLAP). SQL Server also includes tools for visually designing
databases and analyzing data using English-based questions.

System integration with other server software

SQL Server integrates with e-mail, the Internet, and Windows.

Databases
A database in Microsoft SQL Server consists of a collection of tables that contain
data, and other objects, such as views, indexes, stored procedures, and triggers, defined
to support activities performed with the data. The data stored in a database is usually
related to a particular subject or process, such as inventory information for a
manufacturing warehouse.
SQL Server can support many databases, and each database can store either
interrelated data or data unrelated to that in the other databases. For example, a server
can have one database that stores personnel data and another that stores product-related
data. Alternatively, one database can store current customer order data, and another;
related database can store historical customer orders that are used for yearly reporting.
Before you create a database, it is important

5. SOFTWARE DESIGN:

The design phase begins with the requirements specification for the software to be
developed. Design is the first step to moving from the problem domain towards the
solution domain. Design is essentially the bridge between requirement specification and
the final solution for satisfying the requirements. It is the most critical factor effecting
the quality of the software.

21
The design process for software system has two levels.
1. System Design or Top level design
2. Detailed Design or Logical Design

System Design:

In the system design the focus on the deciding which modules are needed for the
system, the specification of these modules and how these modules should be
interconnected.

Detailed Design:

In detailed design the interconnection of the modules or how the specifications of

the modules can be satisfied is decided. Some properties for a software system design
are

• Verifiability
• Completeness
• Consistency
• Traceability
• Simplicity / Understandability

Application architecture:

22
 The application which we are developing is using One-Tier or single Tier
application. Within the same tier we are going to include the business functionalities as
well the data access functionalities. The frontend which we are going to develop is
using the ASP.NET web application.

We will develop all the front end web forms or User interface forms using ASP.NET
web application of .NET environment. Once after developing the user interfaces we
need to write the code behind in order to specify the business logic as well the data
access logic. This coding will be done using the C# language in our application, where
will write all the necessary business logic code and data access code in order to access
the backend database server. The backend end database server which we are going to
use in our application is the MS SQL server 2005, where in all the operations will be
done in Data access logic of our applications. In our application will use necessary
functionalities such as insert during registration, update during updating the records,
select

Once database has been created in the database with all the necessary tables, will use
necessary objects of the ADO.NET such as connection object, command object, Data
Reader object, Data Adapter object and Dataset object as per the situation or the
requirement of our application.

In the above application diagram , in the User Interface block will include all the
necessary front end screens and in the BAL block will include all the necessary business
logic required for any business functionalities whereas in the DAL block will include all
the necessary data access functionalities , such as establishing the connection to the data
base server, than after connecting successfully will use the data manipulation commands
23
such as insert , delete, update ,select operations depending upon the needs of the
application. But in order to use the ADO.NET objects in our application we need to
include the respective namespace provided by the ADO.NET. that’s is in order to
connect to the MS SQL server2005 , we need to include the System.sqlclient namespace
in our application. The namespace sqlclient is to connect to the MS SQL server
database. If we want to connect to oracle database server we need to include oracleclient
namespace, if we want to connect to ACCESS database server we need to include odbc
namespace in our application

5.1 UML Diagrams

Introduction

Modeling is an activity that has been carried out over the years in software
development. When writing applications by using the simplest languages to the most
powerful and complex languages, you still need to model. Modeling can be as
straightforward as drawing a flowchart listing the steps carried out by an application.

Why do we use modeling?

Defining a model makes it easier to break up a complex application or a huge system

into simple, discrete pieces that can be individually studied. We can focus more easily
on the smaller parts of a system and then understand the "big picture." Hence, the
reasons behind modeling can be summed up in two words:

 Readability
 Reusability

Readability brings clarity—ease of understanding. Understanding a system is the first

step in either building or enhancing a system. This involves knowing what a system is
made up of, how it behaves, and so forth. Modeling a system ensures that it becomes
readable and, most importantly, easy to document. Depicting a system to make it
readable involves capturing the structure of a system and the behavior of the system.

Reusability is the byproduct of making a system readable. After a system has been
modeled to make it easy to understand, we tend to identify similarities or redundancy,
be they in terms of functionality, features, or structure.

The Unified Modeling Language, or UML, as it is popularly known by its TLA

(three-letter acronym!), is the language that can be used to model systems and make
them readable. This essentially means that UML provides the ability to capture the
characteristics of a system by using notations. UML provides a wide array of simple,
easy to understand notations for documenting systems based on the object-oriented
design principles. These notations are called the nine diagrams of UML.

Different languages have been used for depicting systems using object-oriented
methodology. The prominent among these were the Rumbaing methodology, the Brooch
24
methodology, and the Jacobson methodology. The problem was that, although each
methodology had its advantages, they were essentially disparate. Hence, if you had to
work on different projects that used any of these methodologies, you had to be well
versed with each of these methodologies. A very tall order indeed! The Unified
Modeling Language is just that. It "unifies" the design principles of each of these
methodologies into a single, standard, language that can be easily applied across the
board for all object-oriented systems. But, unlike the different methodologies that
tended more to the design and detailed design of systems, UML spans the realm of
requirements, analysis, and design and, uniquely, implementation as well. The beauty of
UML lies in the fact that any of the nine diagrams of UML can be used on an
incremental basis as the need arises. Considering all these reasons, it is no wonder that
UML is considered "the" language of choice.

UML does not have any dependencies with respect to any technologies or languages.
This implies that you can use UML to model applications and systems based on either
of the current hot technologies; for example, J2EE and .NET. Every effort has been
made to keep UML as a clear and concise modeling language without being tied down
to any technologies.

Introduction to UML:

The Unified Modeling Language (UML) is a standard language for specifying,

visualizing, constructing, and documenting the artifacts of software systems, as well as
for business modeling and other non-software systems. The UML represents a collection
of best engineering practices that have proven successful in the modeling of large and
complex systems. The UML is a very important part of developing objects oriented
software and the software development process. The UML uses mostly graphical
notations to express the design of software projects. Using the UML helps project
teams communicate, explore potential designs, and validate the architectural design of
the software.

Goals of UML:

The primary goals in the design of the UML were:

 Provide users with a ready-to-use, expressive visual modeling language so

they can develop and exchange meaningful models.
25
  Provide extensibility and specialization mechanisms to extend the core
concepts.

 Be independent of particular programming languages and development

processes.

 Provide a formal basis for understanding the modeling language.

 Encourage the growth of the OO tools market.

 Support higher-level development concepts such as collaborations,

frameworks, patterns and components.

 Integrate best practices.

Why we use UML?

As the strategic value of software increases for many companies, the industry looks
for techniques to automate the production of software and to improve quality and reduce
cost and time-to-market. These techniques include component technology, visual
programming, patterns and frameworks. Businesses also seek techniques to manage the
complexity of systems as they increase in scope and scale. In particular, they recognize
the need to solve recurring architectural problems, such as physical distribution,
concurrency, replication, security, load balancing and fault tolerance. Additionally, the
development for the World Wide Web, while making some things simpler, has
exacerbated these architectural problems. The Unified Modeling Language (UML) was
designed to respond to these needs.

UML diagrams:

The underlying premise of UML is that no one diagram can capture the different
elements of a system in its entirety. Hence, UML is made up of nine diagrams that can
be used to model a system at different points of time in the software life cycle of a
system.

Types of UML diagrams used in this project is:

26
 Use case diagram

The use case diagram is used to identify the primary elements and processes that
form the system. The primary elements are termed as "actors" and the processes are
called "use cases." The use case diagram shows which actors interact with each use
case.

Maintains
student
profiles

checks
valid
student

if yes
retrieves
ph.no

uses
SMS
gateway
Admin

sends
the results to
students
mobile num
Mobile num
updations

FIG: UseCase Diagram

Class diagram:

27
 The class diagram is used to refine the use case diagram and define a detailed design
of the system. The class diagram classifies the actors defined in the use case diagram
into a set of interrelated classes. The relationship or association between the classes can
be either an "is-a" or "has-a" relationship. Each class in the class diagram may be
capable of providing certain functionalities. These functionalities provided by the class
are termed "methods" of the class. Apart from this, each class may have certain
"attributes" that uniquely identify the class.
AUTOMATED MOBILE
RESULTS

profiles,
mobile num,
updations

get student details()

get mobile num()
update()

STUDENT DETAILS

roll num,
mobile num

is a valid student()

RETRIEVES MOBILE NUM STUDENT UPDATIONS

mobile num new mobile num

get mobile num() update mobile num()

SENDING RESULTS
SMS GATEWAY

results
sms

send result to
student
use gateway() mobile num()

FIG: Class Diagram

State diagram:

28
 A state diagram, as the name suggests, represents the different states that objects in
the system undergo during their life cycle. Objects in the system change states in
response to events. In addition to this, a state diagram also captures the transition of the
object's state from an initial state to a final state in response to events affecting the
system.

Checks whether
Maintains Student
Admin valid student or
Profiles
not

If yes
Mobile num retrieves the
updations
phone num

Uses SMS
gate way

Sends the
results to
student mobiles

FIG: State Diagram

Sequence diagram:

29
 A sequence diagram represents the interaction between different objects in the
system. The important aspect of a sequence diagram is that it is time-ordered. This
means that the exact sequence of the interactions between the objects is represented step
by step. Different objects in the sequence diagram interact with each other by passing
"messages".

Student mobile
Admin Data base SMS gateway
numbers

maintains students
profiles

checks whether valid student or not

if yes sends mobile num

uses SMS gateway to send results

send results to student mobile num

if student changes mobile num informs to admin

update student new mobile num to database

FIG: Sequence Diagram

UML Diagram Classification—Static, Dynamic, and Implementation

A software system can be said to have two distinct characteristics: a structural,
"static" part and a behavioral, "dynamic" part. In addition to these two characteristics,
an additional characteristic that a software system possesses is related to

30
implementation. Before we categorize UML diagrams into each of these three
characteristics, let us take a quick look at exactly what these characteristics are.

 Static: The static characteristic of a system is essentially the structural aspect of

the system. The static characteristics define what parts the system is made up of.
 Dynamic:

The behavioral features of a system; for example, the ways a system behaves in
response to certain events or actions are the dynamic characteristics of a system.

 Implementation:

The implementation characteristic of a system is an entirely new feature that

describes the different elements required for deploying a system.

The UML diagrams that fall under each of these categories are:

1. Static

 Use case diagram

 Class diagram

2. Dynamic

 Sequence diagram

 Activity diagram

Views of UML Diagrams

Considering that the UML diagrams can be used in different stages in the life cycle
of a system, let us take a look at the "4+1 view" of UML diagrams. The 4+1 view offers
a different perspective to classify and apply UML diagrams. The 4+1 view is essentially
how a system can be viewed from a software life cycle perspective. Each of these views
represents how a system can be modeled. This will enable us to understand where
exactly the UML diagrams fit in and their applicability.

The different views are:

 Design View:

The design view of a system is the structural view of the system. This gives an
idea of what a given system is made up of. Class diagrams and object diagrams
form the design view of the system.

31
  Process View:

The dynamic behavior of a system can be seen using the process view. The
different diagrams such as the state diagram, activity diagram, sequence diagram,
and collaboration diagram are used in this view.

 Component View:

Component view shows the grouped modules of a given system modeled using the
component diagram.

 Deployment View:

The deployment diagram of UML is used to identify the deployment modules for
a given system.

 Use case View:

Finally, we have the use case view. Use case diagrams of UML are used to view a
system from this perspective as a set of discrete activities or transactions.

5.2 Database design

The data pertaining to proposed system is voluminous that a careful design of the
database must proceed before storing the data in the database. A database management
system provides flexibility in the storage and retrieval of data bad production of
information. The DBMS is a bridge between the application program, which
determines what data are needed and how they are processed, and the operating system
of the computer, which is responsible for placing data on the magnetic storage devices.
A schema defines the database and a subschema defines the portion of the database that
a specific program will use.

5.3 User interfaces and output screens

32
33
34
35
36
37
Student information page:

38
39
6.IMPLIMENTATION CODE:
For login page:

40
<%@ Page Language="C#" MasterPageFile="~/Admin/Admin.master"
AutoEventWireup="true" CodeFile="Login.aspx.cs" Inherits="Admin_Login"
Title="Untitled Page" %>

<asp:Content ID="Content1" ContentPlaceHolderID="head" Runat="Server">

<style type="text/css">
.style13
{
width: 142%;
height: 139px;
}
.style14
{
width: 165px;
}
.style15
{
width: 100%;
}
.style16
{
}
</style>
</asp:Content>
<asp:Content ID="Content2" ContentPlaceHolderID="ContentPlaceHolder1"
Runat="Server">

<table class="style13">
<tr>
<td class="style14" rowspan="2">
&nbsp;</td>
<td>
<table class="style15">
<tr>
<td class="style16">

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;

For student information:

<%@ Page Language="C#" AutoEventWireup="true" CodeFile="StudentsInfo.aspx.cs"

Inherits="StudentsInfo" %>

41
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head runat="server">
<title>Untitled Page</title>
<style type="text/css">
.style1
{
width: 100%;
}
.style2
{
width: 480px;
}
</style>
</head>
<body style="color: #0000FF; background-color: #FFCCCC">
<form id="form1" runat="server">
<table class="style1">
<tr>
<td class="style2">
&nbsp;</td>
</tr>
<tr>
<td class="style2">
<asp:Label ID="Label1" runat="server"
Text="StudentsInformation"></asp:Label>
&nbsp;
<asp:FileUpload ID="fpQuestions" runat="server" Width="251px" />

</td>
<td>
<asp:Button ID="btnupload" Text="Upload" runat="server"
onclick="btnupload_Click" />
</td>
</tr>
</table>
<asp:Label ID="lblErrorMessage" runat="server" Text="Label"></asp:Label>

7. TESTING
7.1 Introduction to testing:

42
 Software testing is a critical element of software quality assurance and represents the
ultimate review of specification, design and coding. The increasing visibility of
software as a system element and attendant costs associated with a software failure are
motivating factors for we planned, through testing. Testing is the process of executing a
program with the intent of finding an error. The design of tests for software and other
engineered products can be as challenging as the initial design of the product itself.

There of basically two types of testing approaches.

One is Black-Box testing-the specified function that a product has been designed to
perform, tests can be conducted that demonstrate each function is fully operated.

The other is White-Box testing knowing the internal workings of the product, tests
can be conducted to ensure that the internal operation of the product performs according
to specifications and all internal components have been adequately exercised.

White box and Black box testing methods have been used to test this package. All
the loop constructs have been tested for their boundary and intermediate conditions. The
test data was designed with a view to check for all the conditions and logical decisions.
Error handling has been taken care of by the use of exception handlers.

Testing Strategies:

Testing is a set of activities that can be planned in advanced and conducted

systematically. A strategy for software testing must accommodation low-level tests that
are necessary to verify that a small source code segment has been correctly
implemented as well as high-level tests that validate major system functions against
customer requirements.

7.2 Unit testing:

Unit testing focuses verification effort on the smallest unit of software design – the
module. The unit test is always white box oriented. The tests that occur as part of unit
testing are testing the module interface, examining the local data structures, testing the
boundary conditions, executing all the independent paths and testing error-handling
paths.

7.3 White box testing:

The purpose of any security testing method is to ensure the robustness of a system in
the face of malicious attacks or regular software failures. White box testing is performed
based on the knowledge of how the system is implemented. White box testing includes
analyzing data flow, control flow, information flow, coding practices, and exception and
43
error handling within the system, to test the intended and unintended software behavior.
White box testing can be performed to validate whether code implementation follows
intended design, to validate implemented security functionality, and to uncover
exploitable vulnerabilities.

White box testing requires access to the source code. Though white box testing can
be performed any time in the life cycle after the code is developed, it is a good practice
to perform white box testing during the unit testing phase.

White box testing requires knowing what makes software secure or insecure, how
to think like an attacker, and how to use different testing tools and techniques. The first
step in white box testing is to comprehend and analyze source code, so knowing what
makes software secure is a fundamental requirement. Second, to create tests that exploit
software, a tester must think like an attacker. Third, to perform testing effectively,
testers need to know the different tools and techniques available for white box testing.
The three requirements do not work in isolation, but together.

7.4 Black box testing:

Also known as functional testing. A software testing technique whereby the internal
workings of the item being tested are not known by the tester. For example, in a black
box test on software design the tester only knows the inputs and what the expected
outcomes should be and not how the program arrives at those outputs. The tester does
not ever examine the programming code and does not need any further knowledge of
the program other than its specifications.

The advantages of this type of testing include:

 The test is unbiased because the designer and the tester are independent of each
other.
 The tester does not need knowledge of any specific programming languages.
 The test is done from the point of view of the user, not the designer.

7.5 Integration testing:

Integration testing is a systematic technique for constructing the program

structure while at the same time conducting tests to uncover errors associated with
interfacing. Scope of testing summarizes the specific functional, performance, and
internal design characteristics that are to be tested. It employs top-down testing and
bottom-up testing methods for this case.

8. IMPLEMENTATION

8.1 Running application

44
In order to run the web application the steps we need to follow are listed below:

1) Open the visual studio IDE (Integrated Development Environment) that is Visual
Studio2008 or other version.

2) Click on file -> open -> browse the folder in which the project is there than select the
folder which consist of app_code or app_data folder that is select the immediate parent
of the app_data or app_code

45
3) Click on open option. Than in the solution explorer you will find web.config file,
open the web.config file (web.config is a file which is used to declare the connection
string globally) and reset the connection strings properties such as Data Source,
Database and security as per your system configuration.
46
4) After restoring the data base, run the application by pressing F5 or debugging button.

8.2 Configuring the database:

1) Open MS SQL SERVER 2005, Rclick on database and select restore database option.

47
2) Give the database name than click on add option and browse the folder which
consists of backup file of our database, than select the backup file .

48
49
 9.CONCLUSION

The project involves sending the examination results of the students to their
respective mobiles in the form of short message service without any type of cost and
registration. The aim of our application is to automate the existing system and
provide user friendly environment in which students can view the results through
SMS. We have analyzed the student needs and by considering all the issues
associated with the manual process we have developed a web application for the
students in viewing the results with less time consumption. The main purpose of the
project is to reduce the complexity of students in viewing the examination results.
Here the complexity means students viewing the results through internet, which is a
time taking process due to heavy server loads which in turn leads to server crash. In
order to overcome these limitations we are implementing this system. By using this
system the student receives the examination results in the form of short message
service to their respective mobile number without any type of cost and registration
by using SMS gateway.

50
 10.BIBILOGRAPHY

The following books were referred during the analysis and execution phase of the
project

Sl.No. Author (s) Book Publisher

1. Roger.S.Pressman SOFTWARE ENGINEERING PEARSON

2. WROX PROFESSIONAL ASP.NET MCGRAWHIL

3. MICROSOFT MSDN 2002 MICROSOFT

REFERENCES:

1. Jeff Poise (2002). Programming Microsoft .NET. Microsoft Press.

2. Asp.net general information and tutorials: http://www.asp.net
3. Building an ASP.NET Intranet, Wrox publication

51