Introduction to Science Gateways and Science Gateway Frameworks - Science Gateways for Distributed Computing Infrastructures - page 13

Fig. 1.3

Collaboration-based SG instance development methodology and required services

Step 2: An SG instance developer downloads several domain-speci c portlets

from the SCI-BUS Portlet Repository that are needed for the target user com-
munity. At this stage, without any development the community already has a
domain-speci

￿

c gateway. Although it may not be perfectly what they want, the
users can start to work with it.

Step 3: An SG instance developer downloads several domain-speci c work-

￿

flows from the SHIWA Work ow repository and develops new domain-speci c

portlets on top of them. At this stage, without any work ow development the

community already has an improved domain-speci c gateway; although it is not

perfectly what they want, the users can have more portlets to work with. For the
sake of mutual collaboration, the SG instance developer uploads the new
portlets into the SCI-BUS Portlet Repository so other communities can take
advantage of using these new portlets.

￿ Step 4: The work ow developer develops new domain-speci c work ows and

uploads them to the SHIWA Work ow Repository. She might download other

work ows from the SHIWA Repository and use them to develop new work ows.

￿ Step 5: An SG instance developer develops new domain-speci c portlets on top

of the work ows developed in step 4. At this stage the domain-speci c gateway

is extended with new portlets speci cally designed according to the needs of this

community. For the sake of mutual collaboration, the SG instance developer
uploads the new portlets into the SCI-BUS Portlet Repository so other com-
munities can take advantage of using these new portlets.