Title:     Airavata Stakeholders
Notice:    Licensed to the Apache Software Foundation (ASF) under one
           or more contributor license agreements.  See the NOTICE file
           distributed with this work for additional information
           regarding copyright ownership.  The ASF licenses this file
           to you under the Apache License, Version 2.0 (the
           "License"); you may not use this file except in compliance
           with the License.  You may obtain a copy of the License at
           .
             http://www.apache.org/licenses/LICENSE-2.0
           .
           Unless required by applicable law or agreed to in writing,
           software distributed under the License is distributed on an
           "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
           KIND, either express or implied.  See the License for the
           specific language governing permissions and limitations
           under the License.

![Airavata Stakeholders](/architecture/user1.png "Airavata Stakeholders")

Airavata is a framework which enables a user to build Science Gateways. It is used to compose, manage, execute and
monitor distributed applications and workflows on computational resources. These computational resources can range
from local resources to computational grids and clouds. Therefore,  various users with different backgrounds either
contribute or use Airavata in their  applications. From the Airavata standpoint, three main users can be identified.

* End Users
* Gateway Developers
* Core Developers

Now let's focus on each user and how they fit into Airavata's big picture.

## End Users ##

![End Users](/architecture/user2.png "End Users")

End User is the one who will have a model code to do some scientific application. Sometimes this End User can be a
Research Scientist. He/She writes scripts to wrap the applications up and by executing those scripts, they run the
scientific workflows in Super Computers. This can be called a scientific experiment. Now the Scientist might have a
requirement to call multiple of these applications together and compose a workflow. That's where the Gateway Developer
comes into the picture.

## Gateway Developers ##

![Gateway Developers](/architecture/user3.png "Gateway Developers")

The Research Scientist is the one who comes up with requirement of bundling scientific applications together and
composing as a workflow.

The job of the Gateway Developer is to use Airavata and wrap the above mentioned model code and scripts together.
Then, scientific workflows are created out these.

Above diagram depicts how Gateway Developer fits into the picture.

## Core Developers ##

![Core Developers](/architecture/user4.png "Core Developers")

Core Developer is the one who develops and contributes to Airavata framework code-base. The Gateway Developers use
the software developed by the Core Developers to create science gateways.