Report Orphanarium Ed

ORPHANARIUM PATRON SYSTEM 2017-18
Chapter 1
INTRODUCTION
1.1 Overview of the system:
Orphanarium Patron System is a web application, this project helps the user to donate
money and many more essential things to the orphans. Initially we are building this
project for a particular city. The main focus is on the middle class economy people.
1.2 Detailed Description:
The donors and the orphanages can register into this website, Donors can help the
orphans through this medium. Orphanages can receive the donations in different ways.
Donors will also get the detailed information about the orphanages, like when it has
started, the founder of the orphanage, number of children in the orphanage, their location
etc. Donors can donate money, feed orphans, can also educate children, provide clothes
etc.
As we have mentioned in overview, this project is for middle class economy people, they
can donate money wish to the certain limit. Here we are also setting a limit for donation.
There will be no fraud, because the status of payment will be seen by orphanages as well
as the donors.
The donors can also provide the clothes which can be pre-owned or if they are willing to
provide the new one or they may take the responsibility to educate the child if not they
may join their hand to server one day meal or certain days of meal for the children.
Department of MCA, NIE Mysuru Page 1

Chapter 2
LITERATURE SURVEY
2.1 Introduction
Literature survey is the most important step in software development process. Before
developing the tool it is necessary to determine the time factor, economy n company strength.
Once these things are satisfied, ten next steps are to determine which operating system and
language can be used for developing the tool. Once the programmers start building the tool
the programmers need lot of external support. This support can be obtained from senior
programmers, from book or from websites. Before building the system the above
consideration are taken into account for developing the proposed system.
Right now the problems facing by orphanages is the delivery of fund at right time, as well as
the education for orphans and care and many of the orphanages are still not getting fund.
2.2 Existing System
Many of the real world web applications exists throughout the world to overcome this
problem
examples :
Indian Orphanage.com, Charity and Orphanage for child,
Miracle Foundation etc.
In the above mentioned websites all are directly taking funds to NGO’s in the form of
dollars.
But by doing like this, fraud might not be possible because they are sending the bills
for donor’s home itself.
But no one knows how much amount is actually getting to the orphanages.
Because of huge transaction, there is a possibilities of corruption.

By doing like this, the small amount will be neglected and the donors who are willing
to donate small amount will be ignored.
Because of hesitation, and also because of fixed amount.
2.3 Proposed System

This is bit different from all websites which we have mentioned in previous
paragraph.
Because our system is only for middle class economy people.
As keeping the features of those websites, we are building this application.
Which provides a platform to donate a small amount as well many features which we
have mentioned above.

Chapter 3
REQUIREMENT SPECIFICATION
3.1 Introduction
Software Requirement Specification is the starting point of the software development
activity. It includes an introduction that gives the purpose, scope and an overview of the
system. This needs requirement by talking to the people and understanding their needs. It also
includes a general description of the product perspective, product function and certain user
characteristics of the system. It also specifies the overall functional requirements,
performance requirements and design constraints. The SRS is a means of translating the idea
in the mind of the clients (the input), into a formal document (the output of the requirement
phase). The Software Requirement Specification document is organized in such a manner it
aids validation and system design.
This section of the SRS describes all general factors of the system and its requirements.
3.2 System Requirements:

3.2.1 Hardware interfaces:
Server Side:
Processor : Pentium 4 onwards.
RAM : 2GB
Hard Disk : 40GB.
Client Side:
Processor : Pentium 4 onwards
RAM : 2GBMB.
Hard Disk : 40GB.

Development Side:
Processor : Pentium 4 onwards.
RAM : 2GB.
Hard Disk : 40GB.
3.2.2 Software interfaces-Server Side:
Operating System : Windows XP version & Higher
Design Tool : Visual Studio 2010.
Web Framework : ASP.NET 4.0
Back End : SQL Server
Language : PHP
Architectural design : 2 - Tier
Web Server : IIS

Chapter 4
SYSTEM ANALYSIS
4.1 Defining a Problem
Defining a problem is one of the important activities of the project. The objective is to
define precisely the business problem to be solved & thereby determined the scope of the
new system. This phase consist of 2 main tasks. The 1st task within this activity is to review
the organization needs that originally initiated the project. The 2nd task is to identify, at an
abstract or general level, the expected capabilities of the new system. Thus, it helps us to
define the goal to be achieved & the boundary of the system. A clear understanding of the
problem will help us in building a better system & reduce the risk of project failure. It also
specifies the resources that have to be made available to the project. Three important factors
project goal, project bounds & the resource limits are sometimes called the project’s term of
reference.
4.2 Feasibility Study
The first study aspect is whether the current project is technically feasible i.e. whether the
project be carried out with the current equipment, existing software and available personnel.
If new technology is required than what is the likelihood that it can be developed? The
second study aspect is whether the project is economically feasible i.e. are there sufficient
benefits in creating the system to make the cost acceptable. Are the costs of not creating the
system so great that the project must be undertaken? The third study aspect is whether the
project is operationally feasible or not i.e. whether the system will be used if it is developed
and implemented? Project is worth developing only if it can meet institutions operating
requirements. The feasibility study proposes one or more conceptual solutions to the
problem set for the project. The objective in assessing feasibility is to determine
whether a development project has a reasonable chance of success. It helps us to
determine the input and output of the system. The following are the criteria that
are considered to confirm the project feasibility.

Three key considerations involved in the feasibility analysis are
 ECONOMICAL FEASIBILITY
 TECHNICAL FEASIBILITY
 SOCIAL FEASIBILITY
4.2.1 ECONOMICAL FEASIBILITY
This study is carried out to check the economic impact that the system will have on the
organization. The amount of fund that the company can pour into the research and
development of the system is limited. The expenditures must be justified. Thus the developed
system as well within the budget and this was achieved because most of the technologies
used are freely available. Only the customized products had to be purchased.
4.2.2 TECHNICAL FEASIBILITY
This study is carried out to check the technical feasibility, that is, the technical requirements
of the system. Any system developed must not have a high demand on the available technical
resources. This will lead to high demands on the available technical resources. This will lead
to high demands being placed on the client. The developed system must have a modest
requirement, as only minimal or null changes are required for implementing this system.
4.2.3 SOCIAL FEASIBILITY
The aspect of study is to check the level of acceptance of the system by the user. This
includes the process of training the user to use the system efficiently. The user must not feel
threatened by the system, instead must accept it as a necessity. The level of acceptance by the
users solely depends on the methods that are employed to educate the user about the system
and to make him familiar with it. His level of confidence must be raised so that he is also able
to make some constructive criticism, which is welcomed, as he is the final user of the system.

Chapter 5
SYSTEM DESIGN
5.1 INTRODUCTION
Design is the first step in the development phase for any engineering product or system. It
may be defined as “the process of applying various techniques and principles for the purpose
of defining a devise, a process or a system in sufficient detail to permit its physical
realization”. Computer software design like engineering design approaches in other
disciplines changes continually as new method, better analysis and broader understanding and
evolve. A System design is a description of the structure to be implemented, the data which is
a part of the system, the interfaces between system components and sometimes, the
algorithms used. Designers do not arrive at a finished design immediately but they develop
the design iteratively through a number of different versions. The iterations is done until the
final system design is not achieved which is close enough to the requirements specifications.
Iteration acts a feedback of the previous iteration which helps in the improvement of the
subsequent iteration. System design is a “how to” approach to the creation of a new system.
It provides the understanding and procedural details necessary for implementing the system
recommended in the feasibility study. Software design is starting with what is needed; design
takes us towards how to satisfy the needs. The design of a system is the most critical factor
affecting the quality of the software. The output of this phase is design document. The
document is used later during implementation, testing and maintenance.
Software design methodology changes continually as new methods; better analysis and
broader understanding evolve. Software design is at relatively early stage in its evolution.
Therefore, software design methodology lacks the depth, flexibility, and quantitative nature
that is normally associated with more classical engineering disciplines. However, techniques
for software design leads the three technical activities Design, Code, Testing that are required
to build and verify software. Each activity transforms information in a manner that results in
validation of the computer software. Using one of the numbers of design methods, the design
step produces a data design, an architectural design and a procedural design. Detail design
focus on refinement to architectural representations that lead to detailed data structure and

algorithmic representation of software. The data design transforms the information domain
model created during analysis into the data structure that will be required to implement the
software. The architectural design defines the relationship among user structural components
into a procedural description of the software. The design of the system is essentially blue
print or a plan for a solution to the system. We consider the system to be a set of components
with clearly defined behaviour, which interact with each other in a fixed, defined manner to
produce some behaviour or services to its environment. The purpose of this document is to
provide design specifications for the system.
5.2 INPUT DESIGN AND OUTPUT DESIGN
5.2.1 INPUT DESIGN
The input design is the link between the information system and the user. It comprises the
developing specification and procedures for data preparation and those steps are necessary to
put transaction data in to a usable form for processing can be achieved by inspecting the
computer to read data from a written or printed document or it can occur by having people
keying the data directly into the system. The design of input focuses on controlling the
amount of input required, controlling the errors, avoiding delay, avoiding extra steps and
keeping the process simple. The input is designed in such a way so that it provides security
and ease of use with retaining the privacy. Input Design considered the following things;
 What data should be given as input?

 How the data should be arranged or coded?
 The dialog to guide the operating personnel in providing input.
 Methods for preparing input validations and steps to follow when error occur.

5.2.2 OBJECTIVES
 Input Design is the process of converting a user-oriented description of the input

into a computer-based system. This design is important to avoid errors in the data
input process and show the correct direction to the management for getting correct
information from the computerized system.
 It is achieved by creating user-friendly screens for the data entry to handle large
volume of data. The goal of designing input is to make data entry easier and to be
free from errors. The data entry screen is designed in such a way that all the data
manipulates can be performed.
the data is entered it will check for its validity. Data can be entered with the help of
screens. Appropriate messages are provided as when needed so that the user will
not be in maize of instant. Thus the objective of input design is to create an input
layout that is easy to follow.
5.2.3 Output Design
 A quality output is one, which meets the requirements of the end user and presents
the information clearly. In any system results of processing are communicated to
the users and to other system through outputs. In output design it is determined how
the information is to be displaced for immediate need and also the hard copy output.
It is the most important and direct source information to the user. Efficient and
intelligent output design improves the system’s relationship to help user decision-
making.
 Designing computer output should proceed in an organized, well thought out
manner; the right output must be developed while ensuring that each output element
is designed so that people will find the system can use easily and effectively. When
analysis design computer output, they should Identify the specific output that is
Create document, report, or other formats that contain information produced by the
system.
 The output form of an information system should accomplish one or more of the
following objectives.

 Convey information about past activities, current status or projections of

the Future
 Signal important events, opportunities, problems, or warnings
 Trigger an action
 Confirm an action
5.3 USE CASE DIAGRAM
5.3.1 Use case for Admin
Login
Add Orphanage
5.3.2 Use case for Orphanage:
Login
View payment
made by
Donors

5.3.2 Use case for Donor:
Login
View the list of

orphanages
Set the amount

to pay

Chapter 6
IMPLEMENTATION
6.1 Introduction
Implementation is the process of converting a new or a revised system design into an

operational one. The objective is to put the new or revised system that has been tested
into operation while holding costs, risks and personal irritation to the minimum. A
critical aspect of the implementation process is to ensure that there will be no
disrupting the functioning of the organization. The best method for gaining control
while implanting any new system would be to use well planned test for testing all new
programs. Before production files are used to test live data, test files must be created
on the old system, copied over to the new system, and used for the initial test of each
program.
Another factor to be considered in the implementation phase is the acquisition of the

hardware and software. Once the software is developed for the system and testing is
carried out, it is then the process of making a newly designed system fully operational
and consistent in performance.
Implementation is the most crucial stage in achieving a successful system and giving
the user’s confidence that the new system is workable and effective. Implementation
of a modified application is to replace an existing one. This type of conversation is
relatively easy to handle, provided there are no major changes in the system.
6.2 System Implementation: There are three major types of implementation are there
but the following are proposed for the project.

6.2.1 Parallel Conversion type of Implementation
In this type of implementation both the current system and the proposed system run in
parallel. This happens till the user gets the complete confidence on the proposed
system and hence cuts of the current system.
6.2.2 Phase – in method of implementation
In this type of implementation the proposed system is introduced phase-by-phase.

This reduces the risk of uncertainty of proposed system.
Each program is tested individually at the time of development using the data
and has verified that this program linked together in the way specified in the
program specification, the computer system and its environment is tested to
the satisfaction of the user. The system that has been developed is accepted
and proved to be satisfactory for the user. And so the system is going to be
implemented very soon. A simple operating procedure is included so that the
user can understand the different functions clearly and quickly.
Initially as a first step the executable form of the application is to be created and
loaded in the common server machine which is accessible to the entire user and the
server is to be connected to a network. The final stage is to document the entire
system which provides components and the operating procedures of the system.
Implementation is the stage of the project when the theoretical design is turned out
into a working system. Thus it can be considered to be the most critical stage in
achieving a successful new system and in giving the user, confidence that the new
system will work and be effective.
The implementation stage involves careful planning, investigation of the existing

system and its constraints on implementation, designing of methods to achieve
changeover and evaluation of changeover methods.
Implementation is the process of converting a new system design into operation.
6.2.3 Implementation Methodology of the Project:

The project is implemented in modular approach. Each module is coded as per the
requirements and tested and this process is iterated till all the modules have been
thoroughly implemented.
Installation procedure
 Install Dreamweaver 2010 software.

 Run the executable project file.
6.3 System Security
Although our method is mainly thought for data tracing in collaborative environment,
we aim at demonstrating that it achieves also a good security level. In particular, we apply to
the images with increasing number of watermarks embedded the most dangerous attack
against asymmetric watermarking security namely the closest point or projection attack.

Screenshots:
Home Page:
About:

Login_Admin:
Admin_Profile:

Admin_Adding_Orphanage:
Login_Orphanage:

Profile_Orphanage:
Donors List:

Login_Donor:
Profile_Donor:

Donation_Page:

Chapter 7
SYSTEM TESTING
7.1 Introduction
Testing accomplishes a variety of things, but most importantly it measures the

quality of the software we are developing. This view presupposes there are defects in
the software waiting to be discovered and this view is rarely disproved or even
disputed.
Several factors contribute to the importance of making testing a high priority of any
software development effort. These include:
 Reducing the cost of developing the program.
 Ensuring that the application behaves exactly as we explain to the user for the vast
majority of programs, unpredictability is the least desirable consequences of using an
application.
 Reducing the total cost of ownership. By providing software that looks and behaves
as shown in the documentation, the customers require fewer hours of training and less
support from product experts.

7.2 Testing Concepts
7.2.1 Unit testing
Unit testing involves the design of test cases that validate that the internal program logic is
functioning properly, and that program inputs produce valid outputs. All decision branches
and internal code flow should be validated. It is the testing of individual software units of the
application .it is done after the completion of an individual unit before integration.
This is a structural testing, that relies on knowledge of its construction and is invasive. Unit
tests perform basic tests at component level and test a specific business process, application,
and/or system configuration. Unit tests ensure that each unique path of a business process
performs accurately to the documented specifications and contains clearly defined inputs and
expected results.
7.2.2 Integration testing
Integration tests are designed to test integrated software components to determine if they
actually run as one program. Testing is event driven and is more concerned with the basic
outcome of screens or fields. Integration tests demonstrate that although the components were
individually satisfaction, as shown by successfully unit testing, the combination of
components is correct and consistent. Integration testing is specifically aimed at exposing the
problems that arise from the combination of components.

7.2.3 Functional test
Functional tests provide systematic demonstrations that functions tested are available as
specified by the business and technical requirements, system documentation, and user
manuals.
Functional testing is centred on the following items:
Valid Input : Identified classes of valid input must be accepted.
Invalid Input : Identified classes of invalid input must be rejected.
Functions : Identified functions must be exercised.
Output : Identified classes of application outputs must be exercised.
Systems/Procedure : Interfacing systems or procedures must be invoked.
Organization and preparation of functional tests is focused on requirements, key functions, or

special test cases. In addition, systematic coverage pertaining to identify Business process
flows; data fields, predefined processes, and successive processes must be considered for
testing. Before functional testing is complete, additional tests are identified and the effective
value of current tests is determined.
7.2.4 System Test
System testing ensures that the entire integrated software system meets requirements. It tests
a configuration to ensure known and predictable results. An example of system testing is the
configuration oriented system integration test. System testing is based on process descriptions
and flows, emphasizing pre-driven process links and integration points.
7.2.5 White Box Testing
White Box Testing is a testing in which in which the software tester has knowledge of the
inner workings, structure and language of the software, or at least its purpose. It is purpose. It
is used to test areas that cannot be reached from a black box level.

7.2.6 Black Box Testing
Black Box Testing is testing the software without any knowledge of the inner workings,
structure or language of the module being tested. Black box tests, as most other kinds of tests,
must be written from a definitive source document, such as specification or requirements
document, such as specification or requirements document. It is a testing in which the
software under test is treated, as a black box .you cannot “see” into it. The test provides
inputs and responds to outputs without considering how the software works.
7.2.7 Unit Testing:
Unit testing is usually conducted as part of a combined code and unit test phase of the
software lifecycle, although it is not uncommon for coding and unit testing to be conducted as
two distinct phases.
7.2.8 Test strategy and approach
Field testing will be performed manually and functional tests will be written in detail.
7.2.9 Test objectives
 All field entries must work properly.

 Pages must be activated from the identified link.
 The entry screen, messages and responses must not be delayed.
7.2.10 Features to be tested
 Verify that the entries are of the correct format

 No duplicate entries should be allowed
 All links should take the user to the correct page.
7.2.11 Integration Testing
Software integration testing is the incremental integration testing of two or more integrated
software components on a single platform to produce failures caused by interface defects.
The task of the integration test is to check that components or software applications, e.g.
components in a software system or – one step up – software applications at the company
level – interact without error.
Test Results: All the test cases mentioned above passed successfully. No defects encountered.

7.2.12 Acceptance Testing
User Acceptance Testing is a critical phase of any project and requires significant
participation by the end user. It also ensures that the system meets the functional
requirements.
Test Results: All the test cases mentioned above passed successfully. No defects encountered.

7.3 Test cases
TEST CASE ID DESCRIPTION EXPECTED RESULT

ACTUAL RESULT
Application should
TC#01 Execute/run the run without any Application is executing
application interrupts properly
TC#02 Verification of Enter User Name and Entered User Name and
Login Page Password. It should Password are successfully
verify with database. verifying with database.
If Admin Login Name Admin User Name &
TC#03 Verification of & Password is valid Password is valid then
Admin Page input then it should successfully navigating
User Name and navigate to respective respective home page.
password Admin home page. If If it is Invalid or wrong
invalid then show input then message box
message that Input shown that User Name or
Username & Password wrong.
Password is wrong.
Verification of if amount is donated to If it is donated

TC#04 donating amount to orphanage, then it successfully then it will to
orphanage should popup with redirected to profile page
donated successfully itself.
msg, otherwise it
should popup with

error msg
TC#05 Verification of If it is pressed, then it After it displaying Logged

Logout has to display popup out it will redirected to
message with appropriate Login Page.
successfully
loggedout.
Orelse with error
message.
Database:
Register_Admin:
Colmun Name Data Type

Id Int(10)
Email Varchar(30)
Password Varchar(30)
Mobile Int(10)
Register_Donor:

Id Int(10)
Mobile Int(10)

Register_Admin:

Id Int(10)
Email Varchar(30)
Mobile Int(10)
Orphan_name Varchar(30)
Donor_name Varchar(30)
Amount Int(10)

Chapter 8
SYSTEM MAINTAINANCE
8.1 Introduction
Once the software is delivered and deployed, it enters the maintenance phase. Software
needs to be maintained not because some of its components wear out and need to be
replaced, but because there are often some residual errors remaining in the system that
must be removed as they are discovered.
8.2 Objectives
The objectives of this maintenance work are to make sure that the system gets to work
all time without any bug. Provision must be for environmental changes which may affect
the computer or software system. This is called the maintenance of the system.
Nowadays there is the rapid change in the software world. Due to this rapid change, the
system should be capable of adapting these changes. In our project the process can be
added without affecting other parts of the system. Maintenance plays a vital role. The
system is said to be liable only to accept any modification after its implementation. This
system has been designed to favour all new changes. Doing this will not affect the
system’s performance or its accuracy. Maintenance covers a wide range of activities,
including correct coding and design errors, updating documents and test data also
upgrading user support.
8.3 Maintenance types
Maintenance can be classified as:
 Corrective maintenance
 Adaptive maintenance
 Preventive maintenance

8.3.1 Corrective maintenance
Almost all developed software has residual errors. Corrective maintenance means
repairing of processing or performance failures or making changes because of
previously uncorrected problems or false assumptions.
8.3.2 Adaptive maintenance
Even without bugs, software frequently undergoes change because it must be upgraded
and enhanced to include more features and provide services.
Once software is developed, the environment in which it operates changes with time.
This changing requires changing or modification in software, called Adaptive
maintenance.
8.3.3 Preventive maintenance
Preventive maintenance is used to ensure the risks of future are minimized. His is one of
the best ways to react to risk proactively. Many activities classified as maintenance are
actually enhancements. Maintenance means restoring something to its original
conditions. It is necessary to keep up with changing user needs and the operation
environment.

Chapter 9
CONCLUSION AND FUTURE ENHANCEMENTS
CONCLUSION
 The website “Orphanarium Patron System” is aimed to Donate Orphanages.
 The goals that have been achieved by the developed system are:
 Any Middle economy people can view the Orphanages list and can pay small
amount of money to orphanages using Paytm.
 Orphanages can get the amount which may helps to their institution
FUTURE ENHANCEMENTS
 We can make this as Android Application, through this each user can install the
app in his mobile itself, we can add payment module, so that user can directly pay to
orphanages whenever they wish.
 We can add orphanages all over India in to this app, so the user can view all
orphanages and can pay amount directly to their Paytm numbers.
 We can also add a module which ask user to fix amount of donation for week, month
or year

Chapter 10
BIBLIOGRAPHY
References
[1] E.Balaguruswamy, Programming with c#, 5th Reprint, Tata McGraw Hill, 2004.
[2] Andrew Troelsem, Pro C# with .NET 3.0, Special Edition, Dream Tech Press, India,
2007
[3] Elmasri & B.Navathe “Fundamentals of Database Systems”, 5th Edition, Addision-
Wesley, 2007
Bibliography
 Referential URL’s:http://w3schools.com

Report Orphanarium Ed

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Report Orphanarium Ed

Hochgeladen von

Copyright:

Verfügbare Formate

ORPHANARIUM PATRON SYSTEM 2017-18

1.2 Detailed Description:

Department of MCA, NIE Mysuru Page 1

2.2 Existing System

Department of MCA, NIE Mysuru Page 2

2.3 Proposed System

Department of MCA, NIE Mysuru Page 3

3.2 System Requirements:

Processor : Pentium 4 onwards.

Hard Disk : 40GB.

Processor : Pentium 4 onwards

Hard Disk : 40GB.

Department of MCA, NIE Mysuru Page 4

Processor : Pentium 4 onwards.

Hard Disk : 40GB.

3.2.2 Software interfaces-Server Side:

Operating System : Windows XP version & Higher

Design Tool : Visual Studio 2010.

Web Framework : ASP.NET 4.0

Back End : SQL Server

Architectural design : 2 - Tier

Web Server : IIS

Department of MCA, NIE Mysuru Page 5

4.1 Defining a Problem

4.2 Feasibility Study

Department of MCA, NIE Mysuru Page 6

Three key considerations involved in the feasibility analysis are

4.2.1 ECONOMICAL FEASIBILITY

4.2.2 TECHNICAL FEASIBILITY

4.2.3 SOCIAL FEASIBILITY

Department of MCA, NIE Mysuru Page 7

Department of MCA, NIE Mysuru Page 8

5.2 INPUT DESIGN AND OUTPUT DESIGN

5.2.1 INPUT DESIGN

 What data should be given as input?

Department of MCA, NIE Mysuru Page 9

 Input Design is the process of converting a user-oriented description of the input

5.2.3 Output Design

Department of MCA, NIE Mysuru Page 10

 Convey information about past activities, current status or projections of

5.3 USE CASE DIAGRAM

5.3.1 Use case for Admin

5.3.2 Use case for Orphanage:

Department of MCA, NIE Mysuru Page 11

5.3.2 Use case for Donor:

View the list of

Set the amount

Department of MCA, NIE Mysuru Page 12

Implementation is the process of converting a new or a revised system design into an

Another factor to be considered in the implementation phase is the acquisition of the

Department of MCA, NIE Mysuru Page 13

6.2.1 Parallel Conversion type of Implementation

6.2.2 Phase – in method of implementation

In this type of implementation the proposed system is introduced phase-by-phase.

The implementation stage involves careful planning, investigation of the existing

Implementation is the process of converting a new system design into operation.

6.2.3 Implementation Methodology of the Project:

Department of MCA, NIE Mysuru Page 14

 Install Dreamweaver 2010 software.

6.3 System Security

Department of MCA, NIE Mysuru Page 15

Department of MCA, NIE Mysuru Page 16

Department of MCA, NIE Mysuru Page 17

Department of MCA, NIE Mysuru Page 18