android manager

7/31/2019 Android Manager

1/40

1

CHAPTER 1

INTRODUCTION OF PROJECT

The project, Android Manager is basically designed to merge the different applications

available in android. The inspiration of the project is that there are many applications of

android in android market but still people are not satisfied and face problems in switching in

different applications. So the Android Manager provides solution to this problem and merge

many of those applications in one. The application contain :

1) Fast Bluetooth ON/OFF Button2) Wi-Fi Enable/Disable via Radio Button3) GPS Enable/Disable via Radio Button4) Network Data Enable/Disable via Radio Button5) Airplane Mode Enable/Disable via Radio Button6) To-Do List

These all are combined in one go and the problem of switching is overcomed.

A step towards Technology.


2/40

2

CHAPTER 2

METHODLOGY USED IN WEBSITE DEVELOPMENT

The general methodology in developing a system is involved in different phases which

describe the systems life cycle model for developing software project. The concept includes

not only forward motion but also have the possibility to return that is cycle back to an activity

previously completed. This cycle back or feedback may occur as a result of the failure with

the system to meet a performance objective or as a result of changes in redefinition of System

activities. The basic WATERFALL MODEL is being used that is its stages. Like most

systems the life cycle of the computer based system also exhibits distinct phases. These are as

follows.

1. Requirement Analysis Phase

2. Design Phase

3. Development Phase

4. Coding Phase

5. Testing Phase

6. Implementation Phase

7. Post Implementation Phase

2.1 REQUIREMENT ANALYSIS

This Phase includes the definition of the problem. In order to identify the problem: we have

to know information about the problem the purpose of the evaluation for the problem to be

known. We have to clearly know about the clients requirements and the objectives of the

project.

2.2 DESIGN

Software design is a process through which the requirements are translated into a

representation of an s/w. One of the software have been analyzed and specified, the s/w

design involves three technical activities: design, coding generation and testing. The design

of the system is in modular form i.e. the s/w is logically partitioned into components that

perform specific functions and sub functions. The Design Phase leads to modules those

exhibit independent functional characteristics .it even leads to interfaces that reduce the

complexity of the connections between modules and with that external environment. The

design phase is for main importance because in this activity decisions ultimately affects the

success of software implementation and maintains.


3/40

3

2.3 DEVELOPMENT

The development phase includes choosing of a suitable s/w to solve the particular problem

given the various facilities and the sophistication in the selected software gives a better

development of the problem.

2.4 CODING

The coding phase is for retranslating the design of the system produced during the design

phase into code in a given programming language. Which can be executed by a computer and

which performs the computation specified by the design?

2.5 TESTING

Testing is done in various ways such as testing the algorithm, programming code, sample

data debugging is one.

2.6 IMPLEMENTATION

After testing is over project is implemented by providing training to the users and providing

manuals so that they can be refreshed as and when needed

2.7 POST IMPLEMENTATION

If any problem occurs after the implemented they are removed from time to time so that so

that the users can work on the prepared system easily finally a satisfied user when all things

are almost right.


4/40

4

CHAPTER 3

SYSTEM IMPLEMENTATION AND

DETAILS OF HARDWARE AND SOFTWARE USED

3.1 INTRODUCTION TO .NET

.NET is the framework for which we develop applications. It sits in between our application

programs and operating system. Applications developed for .NET run inside .NET and are

controlled by .NET. It supports both Windows and web applications.

On November 19, 2007, Microsoft officially released the ASP.NET version 3.5 and Visual

Studio 2008. Like with the progression from ASP.NET 2.0 to 3.0, the features in ASP.NET

3.5 are additive, meaning that the core assemblies installed from the .NET Frameworkversion 2.0 are still used by the 3.0 and 3.5 versions. The In short, ASP.NET 3.5 doesn't

change or take away or break any functionality, concepts, or code present in 2.0 - it simply

adds new types and features and capabilities to the framework.

Visual Studio 2008 is the recommended tool for developing ASP.NET applications. Unlike

previous versions of Visual Studio, which were targeted to a specific framework version (i.e.,

Visual Studio .NET 2003 targeted ASP.NET 1.1 and Visual Studio 2005 targeted ASP.NET

2.0), Visual Studio 2008 is multi-targeted, meaning that you choose from a drop-down list

whether to have Visual Studio 2008 build applications against the ASP.NET 2.0, 3.0, or 3.5

frameworks.

A BRIEF HISTORY OF .NET

Microsoft started development on the .NET Framework in the late 1990s originally under the

name of Next Generation Windows Services (NGWS). By late 2000 the first beta versions of

.NET 1.0 were released.

Version 3.0 of the .NET Framework is included with Windows Server 2008 and WindowsVista. Version 3.5 is included with Windows 7, and can also be installed on Windows XP and

the Windows Server 2003 family of operating systems. On April 12, 2010, .NET Framework

4 was released alongside Visual Studio 2010.


5/40

5

3.2 PRINCIPAL DESIGN FEATURES

3.2.1 INTEROPERABILITY

Because interaction between new and older applications is commonly required, the .NET

Framework provides means to access functionality that is implemented in programs that

execute outside the .NET environment. Access to COM components is provided in the

System. Runtime. Interpose Services and System. Enterprise Services namespaces of the

framework; access to other functionality is provided using the P/Invoke feature.

3.2.2 COMMON RUNTIME ENGINE

The Common Language Runtime (CLR) is the virtual machine component of the .NET

framework. All .NET programs execute under the supervision of the CLR, guaranteeingcertain properties and behaviours in the areas of memory management, security, and

exception handling.

3.2.3 LANGUAGE INDEPENDENCE

The .NET Framework introduces a Common Type System, or CTS. The CTS specification

defines all possible data types and programming constructs supported by the CLR and how

they may or may not interact with each other. Because of this feature, the .NET Framework

supports the exchange of instances of types between programs written in any of the .NET

languages. This is discussed in more detail in Microsoft .NET Languages.

3.2.4 BASE CLASS LIBRARY

The Base Class Library (BCL), part of the Framework Class Library (FCL), is a library of

functionality available to all languages using the .NET Framework. The BCL provides

classes which encapsulate a number of common functions, including file reading and writing,

graphic rendering, database interaction and XML document manipulation.

3.2.5 SIMPLIFIED DEVELOPMENT

The .NET framework includes design features and tools that help manage the installation of

computer software to ensure that it does not interfere with previously installed software, and

that it conforms to security requirements.

3.2.6 SECURITY

The design is meant to address some of the vulnerabilities, such as buffer overflows, that

have been exploited by malicious software. Additionally, .NET provides a common security

model for all applications.


6/40

6

3.3 ASP.NET

To create dynamic web pages by using server side scripts, Microsoft has introduced ASP.

The .NET version of ASP is ASP.NET. AS.NET is a programming framework used to create

Enterprise class of efficient information management. ASP.NET allows you to build dynamicweb pages and tailors the HTML output to whatever browser you are using. It also comes

with a great set of reusable, predefined and ready to use control for your ASP.NET projects.

These reduce the amount the code you have to write, so you can be more productive while

programming. One of the most EYECATCHING things about the ASP.NET is the way you

can use any programming language based on the .NET framework, such as C#, Jscript.NET

or VB.NET to create your web application.

WHY ASP.NET?

Since 1995, Microsoft has been constantly working to shift its focus from Window based

platforms to the INTERNET. As a result, Microsoft introduced ASP ( Active Server Pages) in

November 1996. ASP offered the efficiency of ISAPI applications along with the new level

of simplicity that made it easy to understandable and use. However, ASP script was an

interpreted script and consisted unstructured code and was difficult to debug and maintain.

As the web consists of many different technologies, software integration for web

development was complicated and required to understand many different technologies. Also,

as applications grew bigger in the size and became more complex, the number of lines f

source code in ASP applications increase the dramatically and was hard to maintain.Therefore, an architecture was needed that would allow the development of a Web

application in structured and consisted way.

UNIQUE FEATURESReasons which make .NET different from other alternatives are:

Assemblies

An assembly is either a .DLL or .EXE that forms a part of an application. It contains MSILcode that is executed by CLR.

Common Type System (CTS)Common Type System (CTS) specifies the rules related to data types that languages must

follow. As programs written in all languages are ultimately converted to MSIL, data types in

all languages must be convertible to certain standard data types.
http://itxt.vibrantmedia.com/al.asp?ipid=111&cc=us&ai=15598777&di=64340&ts=20040122055531&redir=http://www61.overture.com/d/sr/?xargs=02u3hs9yoaj12POzCDhBDN%2F2iWg22LsXwtpDwpdI%2Bu8YyWSRDAUTDv8kHDj3FW1d2jb5m%2Ftv5mp%2BUW6Iff7%2FQw8AXnl0KBiJYjPCNwSLtwcIxLtX6KR6H26DTYDu729occtttvfr%2FvNuwfpGxWgwrAsqUP4oyeXOywFwBXZXRoxyWcHFONk7znnTghwpuPFNiC2WhdcqxJwWoDGy7DyuaMtLPp7%2FEzjzP1noyY8IjWqrpUlSw1CSu1LXSCBZlTdYL%2FcvWGJZ5ZrOnfLB8kRls%3Dhttp://itxt.vibrantmedia.com/al.asp?ipid=111&cc=us&ai=15598777&di=64376&ts=20040122055531&redir=http://www61.overture.com/d/sr/?xargs=02u3hs9yoaj1UOyzCCRRBm%2F2SWAPrF2sQsCbYWO03umKEAkBQqf6OWr3GFyzJ7k93Pw%2F7WhomvWUgRAkjaOgwS4kHhQ4KIFzQjiX6%2Fc2PQP2hxLcPqz%2BBpz2889%2Bt%2FQ9vxfxgSamkrc7WB1Zcb%2BZfG7ieShkNGhZ0Jr5%2Bd84%2BCrT6YqGyqS2FKVRpTYavS%2FKDKfLOVn73QNOQ9TDphEHdo5kaUywFCSloXrEGCb2vawXg3WsqfZkzLOhvlWpmhTQ%3D%3Dhttp://itxt.vibrantmedia.com/al.asp?ipid=111&cc=us&ai=15598777&di=64376&ts=20040122055531&redir=http://www61.overture.com/d/sr/?xargs=02u3hs9yoaj1UOyzCCRRBm%2F2SWAPrF2sQsCbYWO03umKEAkBQqf6OWr3GFyzJ7k93Pw%2F7WhomvWUgRAkjaOgwS4kHhQ4KIFzQjiX6%2Fc2PQP2hxLcPqz%2BBpz2889%2Bt%2FQ9vxfxgSamkrc7WB1Zcb%2BZfG7ieShkNGhZ0Jr5%2Bd84%2BCrT6YqGyqS2FKVRpTYavS%2FKDKfLOVn73QNOQ9TDphEHdo5kaUywFCSloXrEGCb2vawXg3WsqfZkzLOhvlWpmhTQ%3D%3Dhttp://itxt.vibrantmedia.com/al.asp?ipid=111&cc=us&ai=15598777&di=64340&ts=20040122055531&redir=http://www61.overture.com/d/sr/?xargs=02u3hs9yoaj12POzCDhBDN%2F2iWg22LsXwtpDwpdI%2Bu8YyWSRDAUTDv8kHDj3FW1d2jb5m%2Ftv5mp%2BUW6Iff7%2FQw8AXnl0KBiJYjPCNwSLtwcIxLtX6KR6H26DTYDu729occtttvfr%2FvNuwfpGxWgwrAsqUP4oyeXOywFwBXZXRoxyWcHFONk7znnTghwpuPFNiC2WhdcqxJwWoDGy7DyuaMtLPp7%2FEzjzP1noyY8IjWqrpUlSw1CSu1LXSCBZlTdYL%2FcvWGJZ5ZrOnfLB8kRls%3D


7/40

7

Cross-language Interoperability.NET provides support for language interoperability. However, it doesnt mean every

program written in a language can be used by another language. To enable a program to be

used with other languages, it must be created by following a set of rules called Cross

Language Specifications (CLS).

Cross-language inheritance is the ability to create a class in C# from a class created in

VB.NET.

When an exception is raised by a program written in C#, the exception can be handled by

VB.NET. This kind of exception handling is called cross-language exception handling.

3.4 THE ARCHITECTURE OF ASP.NET APPLICATION

FIG 3.1 ARCHITECTURE OF ASP.NET
http://itxt.vibrantmedia.com/al.asp?ipid=111&cc=us&ai=15598777&di=23269&ts=20040122055531&redir=http://www60.overture.com/d/sr/?xargs=02u3hs9yoaj1VuzTCDhBBm30Vvb2vgbAew1wduUvQ5AR4rdn4kMFJ5KBL7qVNq6qtOzNHrN7D%2F8nYr4W%2BMPbtTGa5kmhECyNZasIhJMT1ohEs9azHHvMzNdRZe4If6uxj22%2Fq8usPkvWfx9tCPkUgjk3Z9rPJwjKIHuEgIUgpUCQl62sac3m8Xmhp2TuTd4itIKbQirKCrn9%2BXlNSVWOpr%2BKo%2Buj4wIXOmbIaLZSqCF5hSpgWXy8S4nfyZlhOVy2YFrKcIzAB%2FaRzZUQ%3D%3Dhttp://itxt.vibrantmedia.com/al.asp?ipid=111&cc=us&ai=15598777&di=23269&ts=20040122055531&redir=http://www60.overture.com/d/sr/?xargs=02u3hs9yoaj1VuzTCDhBBm30Vvb2vgbAew1wduUvQ5AR4rdn4kMFJ5KBL7qVNq6qtOzNHrN7D%2F8nYr4W%2BMPbtTGa5kmhECyNZasIhJMT1ohEs9azHHvMzNdRZe4If6uxj22%2Fq8usPkvWfx9tCPkUgjk3Z9rPJwjKIHuEgIUgpUCQl62sac3m8Xmhp2TuTd4itIKbQirKCrn9%2BXlNSVWOpr%2BKo%2Buj4wIXOmbIaLZSqCF5hSpgWXy8S4nfyZlhOVy2YFrKcIzAB%2FaRzZUQ%3D%3D


8/40

8

3-Tier architecture generally contains UI or Presentation Layer, Business Access Layer

(BAL) or Business Logic Layer and Data Access Layer (DAL)

Presentation Layer (UI)

Presentation layer contains pages like .aspx or windows form where data is presented to theuser or input is taken from the user.

Business Access Layer (BAL) or Business Logic Layer

BAL contains business logic, validation or calculation related with the data, if needed.

Data Access Layer (DAL)

DAL contains methods that helps business layer to connect the data and perform required

action, might be returning data or manipulating data (insert, update, delete etc).

FIG 3.2 DATA ACCESS LAYER

3.5 INTRODUCTION TO HTML

HTML is Hyper-Text Markup Language, is a system of codes that is used to createinteractive, online pages.

An HTML file can be created by using a Simple text editor(eg. notepad) HTML works as WYSIWYG environment, which means What You See Is What You

Get.

An HTML file is a text file containing markup tags. And its file is saved as .html or.htm extension.


9/40

9

3.6 MICROSOFT SQL SERVER 2008

Microsoft SQL Server 2008 is a relational database system that is scalable from single user

database running on a single user system such as Laptop to enterprise-wide networks and

global dotcom websites. SQL server 2008 is the eighth SQL Server release making a feature-

rich, mature and stable platform? SQL Server is a comprehensive, integrated, end-to-end data

solution that empowers people by providing a more secure, reliable and productive platform

for enterprise data applications. SQL Server 2008 also includes support for structured and

semi-structured data, including digital media formats for pictures, audio, video and other

multimedia data. The SQL Server data platform includes the following tools:

Relational Database Replication Services Notification Services Integration Services Analysis Services Reporting Services Management Tools Development Tools Increase Productivity

3.7SYSTEM IMPLEMENTATION

System implementation covers a broad spectrum of activities from a detailed workflow

analysis to the formal go-live of the new system. During system implementationorganizations may refine the initial workflow analysis that had been completed as part of the

requirements analysis phase. With the aid of the vendor they may also start mapping out the

proposed new workflow.

In addition to the workflow analysis it is during this phase that full system testing is

completed. Other key activities that would occur during this phase include piloting of the new

system, formal go-live and the immediate post implementation period during which any

application issues are resolved.


10/40

10

PURPOSEThe purpose of System Implementation can be summarized as follows: making the new

system available to a prepared set of users (the deployment), and positioning on-going

support and maintenance of the system within the Performing Organization (the transition).

At a finer level of detail, deploying the system consists of executing all steps necessary to

educate the Consumers on the use of the new system, placing the newly developed system

into production, confirming that all data required at the start of operations is available and

accurate, and validating that business functions that interact with the system are functioning

properly. Transitioning the system support responsibilities involves changing from a system

development to a system support and maintenance mode of operation, with ownership of the

new system moving from the Project Team to the Performing Organization.

A key difference between System Implementation and all other phases of the lifecycle is that

all project activities up to this point have been performed in safe, protected, and secureenvironments, where project issues that arise have little or no impact on day-to-day business

operations. Once the system goes live, however, this is no longer the case.

3.8 SYSTEM REQUIREMENTS

1. Server - A Pentium 4 or its equivalent with 1 Gb Ram, 100 Gb Hard disk (IDE or SCSI),

CD-ROM drive, LAN, Uninterruptible power supply and display monitor.

2. Client - A Pentium 3 or equivalent PC with 64mb Ram, 1 Gb Hard disk, with Windows 98

or above, IE Explorer 5 or above and display monitor.


11/40

11

CHAPTER 4

FEASIBILITY ANALYSIS

Feasibility analysis is the procedure for identifying the candidate system, evaluating andelecting the most feasible system. This is done by investigating the existing system in the area

under investigation or generally ideas about a new system. It is a test of a system proposal

according to its workability, impact on the organization, ability to meet user needs, and

effective use of resources. The objective of feasibility study is not to solve the problem but to

acquire a sense of its scope. Feasibility analysis involves 8 steps:

1 Form a project team and appoint a project leader.2 Prepare system flow charts.3 Enumerate potential candidate system.4 Describe and identify characteristics of candidate systems.5 Determine and evaluate performance and cost effectiveness of each candidate

system.

6 Weigh system performance and cost data.7 Select the best candidate system.8 Repair and report final project directive to management. Three key

Considerations are involved in the feasibility analysis: economic, technical and

behavioural.

4.1 ECONOMIC FEASIBILITY

Economic analysis is the most frequently used method for evaluating the effectiveness of a

candidate system. It is more commonly known as cost benefit analysis, the procedure to

determine the benefits and saving that are expected from a candidate system and compare

them with costs.

If the benefits outweigh costs then a decision is made to design and implement the system.

Otherwise make alterations in the proposed system.

4.2 TECHNICAL FEASIBILITY

The assessments of technical feasibility centres on the existing system and to what extent it

can support the proposed addition. This was based on an outline design of system

requirements in turns of inputs, files, programs, procedures, and staff. It involves financial

considerations to accommodate technical enhancements.

4.3 BEHAVIORAL FEASIBILITY

People are inherently resistant to change, and computers have been known to facilitate

change. An estimate should be made about the reaction of the user staff towards the

development of a computerized system. Computer installations have something to do with


12/40

12

turnover, transfers and changes in job status. The introduction of a candidate system requires

special effort to educate, sell and train the staff for conducting the business.

FEASIBILITY STUDY STEPS

BudgetingInclude all costs incurred for the project including the cost of the feasibilitystudy.

Project Description Identify the project name and purpose. Include details includingstakeholders, and end result expected.

GoalsList long and short-term goals and what processes will be needed to achieve thosegoals.

TimelineWhat will be the estimated time until project completion? Costs and itself. PurposeWhat purpose does the project have and whom will it benefit? Market AnalysisIf applicable, will the market or market environment benefit from the

project. If so, list why.

Resources Identify all the resources both IT, technical, inventory, and human that willbe needed to complete the project.

Project ProcessHow will the project flow? Include flow charts showing project stages. Management and Teams Who will manage and who will work on scheduled tasks?

Will project management outsourcing be needed?

ObservationsStatements that do or dont support the project should be included here. Iffor a client, does the client have the finances to complete the project or are there

alternatives? If for a project or process, will it work and will it be beneficial?
http://www.brighthub.com/office/project-management/articles/36786.aspxhttp://www.brighthub.com/office/project-management/articles/36786.aspx


13/40

13

CHAPTER 5

SYSTEM ANALYSIS AND DESIGN

5.1 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 in 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.

FIG.5.1 SYSTEM DEVELOPMENT LIFE CYCLE


14/40

14

5.2 SYSTEM ANALYSIS

Assuming that a new system is to be developed, the next phase is system analysis. Analysis

involved a detailed study of the current system, leading to specifications of a new system.

Analysis is a detailed study of various operations performed by a system and theirrelationships within and outside the system. During analysis, data are collected on the

available files, decision points and transactions handled by the present system. Interviews,

on-site observation and questionnaire are the tools used for system analysis.

The main points to be discussed in system analysis are:

1. Specification of what the new system is to accomplish based on the user requirements.

2. Functional hierarchy showing the functions to be performed by the new system and their

relationship with each other.

3. Function network which are similar to function hierarchy but they highlight those functions

which are common to more than one procedure.

4. List of attributes of the entities - these are the data items which need to be held about each

entity (record).

5.3 SYSTEM DESIGN

Based on the user requirements and the detailed analysis of a new system, the new system

must be designed. This is the phase of system designing. It is a most crucial phase in the

development of a system. Normally, the design proceeds in two stages:

1. Preliminary or general design

2. Structure or detailed design

PRELIMINARY OR GENERAL DESIGN:In the preliminary or general design, the features of the new system are specified. The costs

of implementing these features and the benefits to be derived are estimated. If the project is

still considered to be feasible, we move to the detailed design stage.

STRUCTURE OR DETAILED DESIGN:In the detailed design stage, computer oriented work begins in earnest. At this stage, the

design of the system becomes more structured. Structure design is a blue print of a computer

system solution to a given problem having the same components and inter-relationship

among the same components as the original problem. Input, output and processing


15/40

15

specifications are drawn up in detail. In the design stage, the programming language and the

platform in which the new system will run are also decided.

5.4 STEPS OF DESIGN PROCESS

Logical design (DFD)In the DFD, the inputs (source), outputs (destination), Databases (data stores), procedures

(Data Flow) and boundaries of the system are described that needs the user requirement. It

specifies the user need at a level of detail that virtually determines the information flow into

and out of the system and the required data resources.

Physical design (Database design)This activity deals with the design of the physical database. A key is to determine how the

access paths are to be implemented. A physical path is derived from the logical path. The

relationships existing among the entities like one-to-one, one-to-many, many-to-many are

considered while designing the database. Relational structured database is used in this

system.

Program DesignIn conjunction with database design is a decision on the programming language to be used

and the flowcharting, coding and debugging procedure prior to conversion.In this application, ASP.Net is used as server side scripting while JavaScript and HTML are

used as client side scripting, which are supported by the browsers like Internet Explorer.

Visual Web Developer 2008 is used for coding.

Database DesignThe Database (collection of data) is at the core of any information system. The nature of data

stored in the database as well as the organization of the data has wide implications on the

performance of the system. A good database design should hold all the data, which may berequired by the users of the system, but at the same time, avoid any harmful or unnecessary

redundancy. The database should also be flexible so that any future change in requirements

can be incorporated with minimum changes.


16/40

16

CHAPTER 6

SYSTEM MAINTENANCE AND EVALUATION

FIG.6.1 SYSTEM EVALUATION

6.1 SYSTEM MAINTENANCE

Maintenance is the act of keeping an entity in an existing state of efficiency, validity, to

preserve from failure or decline.

System maintenance is the modification of the software product after delivery in order to

improve performance, correct faults, and adapt the product to the modified environment.

System maintenance is a catchall term used to describe various forms of computer or server

maintenance required to keep a computer system running properly. It can describe network

maintenance which could mean that servers are being physically repaired, replaced, or

moved.

Network maintenance can also mean that the software for a server is being updated, changed,

or repaired. This sort of maintenance is typically performed on a regular or semi-regular

schedule, often during non-peak usage hours, and keeps servers running smoothly.
http://www.wisegeek.com/what-is-server-maintenance.htmhttp://www.wisegeek.com/what-is-server-maintenance.htmhttp://www.wisegeek.com/what-is-server-maintenance.htmhttp://www.wisegeek.com/what-is-server-maintenance.htm


17/40

17

FIG.6.2 SYSTEM MAINTENANCE

Maintenance :After the system was installed it was continuously analyzed for defects, errors

& compatibility problems. In case of an error or problem, it was rectified on the spot

or within an acceptable time frame

Evaluation :

In todays world, none of the system is completely perfect. As the various

requirements of user keeps on changing, the software needs to be further

modified. Evolution is a report generation tool which used to represent data in

different formats.

Also, our proposed system can be further enhanced. Our system has following

limitations as follows:-


18/40

18

All the various generated reports are in form of a file which is stored on themachines disk consuming some about of space.

This system does not supports multi- table queries in which more than onetable is used.

Also this system does not perform any of the summary query operations. The

new features can be added in our system to overcome the above limitations.

These are:

We would like to reduce the disk space occupied by our systems report file. The proposed system should support various multi-tables queries as well as sub-

queries operations.

6.2 TESTING

Software Testing is a process that consists of all test life cycle activities like static and

dynamic testing concerned with planning, preparation and evaluation of software products to

determine that the software products satisfy customers requirements and are fit for customers

use. Software Testing is done to find software defects or failures in advance.

Unit Testing Integration Testing System Testing Acceptance Testing

UNIT TESTINGUnit is the smallest testable part of the software system. Unit testing is done to verify that the

lowest independent entities in any software are working fine. The smallest testable part is

isolated from the remainder code and tested to determine whether it works correctly.

INTEGRATION TESTINGIn integration testing the individual tested units are grouped as one and the interface between

them is tested. Integration testing identifies the problems that occur when the individual units

are combined i.e it detects the problem in interface of the two units. Integration testing is

done after unit testing.
http://www.softwaretestingmentor.com/test-levels/unit-testing.phphttp://www.softwaretestingmentor.com/test-levels/integration-testing.phphttp://www.softwaretestingmentor.com/test-levels/system-testing.phphttp://www.softwaretestingmentor.com/test-levels/acceptance-testing.phphttp://www.softwaretestingmentor.com/test-levels/acceptance-testing.phphttp://www.softwaretestingmentor.com/test-levels/system-testing.phphttp://www.softwaretestingmentor.com/test-levels/integration-testing.phphttp://www.softwaretestingmentor.com/test-levels/unit-testing.php


19/40

19

SYSTEM TESTINGTesting the behaviour of the whole software/system as defined in software requirements

specification (SRS) is known as system testing, its main focus is to verify that the customer

requirements are fulfilled.System testing is done after integration testing is complete. System testing should test

functional and non functional requirements of the software.

Following types of testing should be considered during system testing cycle. The test types

followed in system testing differ from organization to organization however this list covers

some of the main testing types which need to be covered in system testing.

ACCEPTANCE TESTINGAcceptance testing is performed after system testing is done and all or most of the major

defects have been fixed. The goal of acceptance testing is to establish confidence in the

delivered software/system that it meets the end user/customers requirements and is fit for use

Acceptance testing is done by user/customer and some of the project stakeholders.

FIG.6.3 TESTING OF SYSTEM


20/40

20

CHAPTER 7

DETAILED LIFE CYCLE OF THE PROJECT

The System Development Life Cycle (SDLC), or Software Development Life

Cycle in systems engineering and software engineering, is the process of creating or altering

systems, and the models and methodologies that people use to develop these systems. The

concept generally refers to computer or information systems.

7.1 OVERVIEW

Systems Development Life Cycle (SDLC) is a process used by a systems analyst to develop

an information system, including requirements, validation, training, and user (stakeholder)

ownership. Any SDLC should result in a high quality system that meets or exceeds customer

expectations, reaches completion within time and cost estimates, works effectively and

efficiently in the current and planned Information Technology infrastructure, and is

inexpensive to maintain and cost-effective to enhance.

7.2 SYSTEM DEVELOPMENT PHASES

Systems Development Life Cycle (SDLC) adheres to important phases that are essential for

developers, such as planning, analysis, design, and implementation. There are several

Systems Development Life Cycle Models in existence. The oldest model, that was originallyregarded as "the Systems Development Life Cycle" is the waterfall model: a sequence of

stages in which the output of each stage becomes the input for the next. These stages

generally follow the same basic steps but many different waterfall methodologies give the

steps different names and the numbers of steps seem to vary between 4 and 7. The steps can

be characterized and divided in several steps

INITIATION/PLANNINGTo generate a high-level view of the intended project and determine the goals of the project.

The feasibility study is sometimes used to present the project to upper management in an

attempt to gain funding. Projects are typically evaluated in three areas of feasibility:

economical, operational or organizational, and technical. Furthermore, it is also used as a

reference to keep the project on track and to evaluate the progress of the MIS team. The MIS

is also a complement of those phases. This phase is also called as analysis phase.


21/40

21

FIG.7.1 SYSTEM DEVELOPMENT LIFE CYCLE

REQUIREMENTS GATHERING AND ANALYSISThe goal of systems analysis is to determine where the problem is in an attempt to fix the

system. This step involves Decomposition computer science breaking down the system in

different pieces to analyze the situation, analyzing project goals, breaking down what needs

to be created and attempting to engage users so that definite requirements can be defined.

Requirements Gathering sometimes requires individuals/teams from client as well as serviceprovider sides to get detailed and accurate requirements.

DESIGNIn systems design functions and operations are described in detail, including screen layouts,

business rules, process diagrams and other documentation. The output of this stage will

describe the new system as a collection of modules or subsystems.

The design stage takes as its initial input the requirements identified in the approved

requirements document. For each requirement, a set of one or more design elements will be

produced as a result of interviews, workshops, and/or prototype efforts. Design elements

describe the desired software features in detail, and generally include functional hierarchy


22/40

22

diagrams, screen layout diagrams, tables of business rules, business process diagrams, pseudo

code, and a complete entity-relationship diagram with a full data dictionary. These design

elements are intended to describe the software in sufficient detail that skilled programmers

may develop the software with minimal additional input.

BUILD OR CODINGModular design| Modular and subsystem programming code will be accomplished during this

stage. Unit testing and module testing are done in this stage by the developers. This stage is

intermingled with the next in that individual modules will need testing before integration to

the main project.

TESTINGThe code is tested at various levels in software testing. Unit, system and user acceptance

testing are often performed. This is a grey area as many different opinions exist as to what the

stages of testing are and how much if any iteration occurs. Iteration is not generally part ofthe waterfall model, but usually some occur at this stage.

Below are the following types of testing:

Data set testing. Unit testing System testing Integration testing Black box testing White box testing Regression testing

OPERATIONS AND MAINTENANCEThe deployment of the system includes changes and enhancements before the

decommissioning or sunset of the system. Maintaining the system is an important aspect of

SDLC. As key personnel change positions in the organization, new changes will be

implemented, which will require system updates.


23/40

23

7.3 ENTITY-RELATIONSHIP DIAGRAM

Valid user

Valid user

account

Valid

passwor

Login

Registration

Conf.

password

Password

Add email

account

Add name


24/40

24

7.4 DFD DIAGRAM

0 LEVEL

1 LEVEL

user

History

Attraction

Homepage

Tour & Travel

About Rajasthan

Photo gallery

Login

Sign inNew account

Registration

Login user Website

pages

Manage database


25/40

25

2 LEVEL

Customer

Web pages

Sign in page

Help

Other links

Web page


26/40

26

CHAPTER 8

CODING

1. REGISTRATION MODULE

Public partial class Default6

{

SqlConnection con = new SqlConnection();

SqlCommand cmd;

SqlDataReader dr;

protected void Page_Load(object sender, EventArgs e)

{

}

protected void Button1_Click(object sender, EventArgs e)

{

cmd = new SqlCommand("select * from raj where email='" + TextBox2.Text + "'", con);

con.Open();

dr = cmd.ExecuteReader();

if (dr.Read())

{

Label1.Visible = true;Label1.Text = "User Name Not Available";

}

else

{

try

{

cmd = new SqlCommand("insert into raj values('" + TextBox1.Text + "','" +

TextBox2.Text + "','" + TextBox3.Text + "','" + TextBox4.Text + "')", con);

//cmd.Parameters.AddWithValue("field1", SqlDbType.VarChar).Value =

TextBox1.Text;


TextBox2.Text;


TextBox3.Text;


TextBox4.Text;

con.Open();cmd.ExecuteNonQuery();


27/40

27

con.Close();

}

catch (Exception ex)

{

Response.Write(ex.Message);}

Response.Redirect("login.aspx");

}

}

}

2. LOGIN MODULE

Public partial class Default7{

SqlConnection con = new SqlConnection();

SqlCommand cmd;

protected void Page_Load(object sender, EventArgs e)

{

}

protected void Button3_Click(object sender, EventArgs e){

Response.Redirect("registration.aspx");

}

protected void Button2_Click(object sender, EventArgs e)

{

try

{

con.Open();

string s = "select * from raj where email='" + TextBox2.Text + "'";

SqlCommand cmd = new SqlCommand(s, con);//dr for a particular column values

SqlDataReader dr = cmd.ExecuteReader();

if (dr.Read())

{

if (TextBox3.Text != dr["pasw"].ToString())

{

Label2.Visible = true;

Label2.Text = "invalid password";

}

else{


28/40

28

Session.Add("email", TextBox2.Text);

Response.Redirect("photog.aspx");

}

}

else{

Label1.Visible = true;

Label1.Text = "user id is wrong";

}

con.Close();

}

// con.Open();

// cmd.ExecuteNonQuery();

// con.Close();

catch (Exception ex)

{

Response.Write(ex.Message)

}

}

}


29/40

29

CHAPTER 9

OUTPUT OF PROJECT

Forms are the parts that create GUI for the project it contain text box, button, combo box,

check box, and all HTML controls. This entire combine form a GUI for a user of an

application. Form are the part through which data is entered into the database we can say that

these are the front-end of the application and Education Groom contains more than 8 forms in

all to give user friendly environment to the end user.

FIG.9.1 HOME PAGE


30/40

30

FIG.9.2 HISTORY PAGE


31/40

31

FIG 9.3 ABOUT RAJASTHAN PAGE


32/40

32

FIG 9.4 ATTRACTION PAGE


33/40

33

FIG 9.5 RAJASTHAN DISTRICT


34/40

34

FIG 9.6 TOUR & TRAVELS


35/40

35

FIG 9.7 LOGIN PAGE


36/40

36

FIG 9.8 REGISTRATION PAGE

FIG 9.9 WHEN ENTER IN LOG IN PAGE


37/40


38/40

38

RESULT

I have studied all the details and specification of ASP.NET and I have done small projects

successfully with the help of respected trainers. .NET project gives us very useful and

practical knowledge.

For designing project first design UML diagram:

As the UML design approach was used previously in the

project, the decision was made to continue with its use in designing the revised functionality

of the system.

DATABASE:

The database is split, for the purposes of efficiency, portability and convenience, into tables.

Content is held in one or more table(s), for table size management reasons. The decision was

made to limit the table size to 2GB[3] (we have disregarded compatibility to the FAT12 and

MINIX filesystems, which have a file size limit of32MB and 64MB respectively, for obvious

reasons). This limitation means that only 32,000 comments can be fit into one table, so a new

table should be created every 32,000 comments.


39/40

39

CONCLUSION

Working on the project was good experience. I understand the importance of Planning and

designing as a part of software development. But its very difficult to complete the program

for single person. Developing the project has helped us some experience on real-time

development Procedures.

The goal of this project is to give information about state RAJASTHAN. It is useful in

guideline or gathering knowledge about history useful in to write articles.

The use of the technology plays a key part in institutional podcasting. However, depending

on the technologies chosen, these can both enable and stifle. It is important to draw on

experiences of others, and to apply those experiences intelligently within one's own

institution.

The system is highly flexible and is well efficient to make easy interaction with the client.

The project is developed in .NET as a front-end and SQL as a back-end it can be modified

easily and used for a long period.


40/40

REFERENCES

BOOKS

[1] SOFTWARE ENGINEERING A Practitioners Approach: PRESSMAN, TATAMcGralHill

[2] SOFTWARE ENGINEERING-I, Shalini Puri[3] SOFTWARE ENGINEERING By K.K. Agarwal,New Age International Publishers[4] Case Studies in Systematic Software Development By Cliff B. Jones and Robert C. F.

Shaw - Prentice Hall , 1990

[5] The .NET Framework by Julian Temple man[6] Database management system by silberschatz, korth, McGraw-Hill[7] Database Management System by Santander Bal Gupta Shree Mhavir book Depot

(Publishers) Books In India

[8] The Book Of Visual Studio .net by Robert B. dun away Published by William Pollock[9] Introducing .net 4.0 with visual studio by Alex Mackey Published by Paul Manning[10] Pro Visual Studio .net by Donald Xie Published by Springer India pvt Ltd[11] Bob Hughes & Mike Cottrell ,"Software Project Management", McGraw-Hill, Fourth

Edition

[12] Darrel Ince, Helen Sharp and Mark Woodman, Introduction to Software ProjectManagement and Quality Assurance, McGraw Hill

[13] E. M. Benn tan. Software Project Management: A Practitioners Approach,McGraw Hill,2nd Edition

[14] Tom DeMarco and Timothy Lister, People ware - Productive Projects and Teams,Dorset House Publishing Company, 2nd Edition

[15] Mastering visual studio .net by Jon Flanders Published by O Reilly[16] Programming Microsoft Visual C# 2008 by Donis Marshall Published by WP

publishers and distributors (P) Ltd

[17] http://www.codeproject.com/KB/miscctrl/OnlineExam.aspx[18] http://msdn.microsoft.com/en-us/library/dd831853.aspx[19] http://www.dotnetspider.com/tutorials/AspNet-Tutorials.aspx[20] http://www.csharpcorner.com[21] http://www.rajasthantourism.com
http://www.e-booksdirectory.com/details.php?ebook=1084http://www.e-booksdirectory.com/details.php?ebook=1084

android manager

Documents