+-------+-------+-------+-------+---------+------+--------------------+
| ***c  |       |       |       |         |      |                    |
| aGrid |       |       |       |         |      |                    |
| Po    |       |       |       |         |      |                    |
| rtal/ |       |       |       |         |      |                    |
| Brows |       |       |       |         |      |                    |
| er*** |       |       |       |         |      |                    |
|       |       |       |       |         |      |                    |
| ***J  |       |       |       |         |      |                    |
| oshua |       |       |       |         |      |                    |
| P     |       |       |       |         |      |                    |
| hilli |       |       |       |         |      |                    |
| ps*** |       |       |       |         |      |                    |
+-------+-------+-------+-------+---------+------+--------------------+
| *     | **U   | **I   | **G   | **Pri   | **L  | **Description**    |
| *Rele | ser** | terat | Forge | ority** | evel |                    |
| ase** |       | ion** | Task  |         | of   |                    |
|       |       |       | No.** |         | Ef   |                    |
|       |       |       |       |         | fort |                    |
|       |       |       |       |         | (Day |                    |
|       |       |       |       |         | s)** |                    |
+-------+-------+-------+-------+---------+------+--------------------+
| 1.1   | Int   | 1     |       | High    | 3    | Browser: Security  |
|       | ernal |       |       |         |      | Deferred Login     |
|       |       |       |       |         |      |                    |
|       |       |       |       |         |      | The user should be |
|       |       |       |       |         |      | prompted to login  |
|       |       |       |       |         |      | only when he       |
|       |       |       |       |         |      | attempts to        |
|       |       |       |       |         |      | interact with a    |
|       |       |       |       |         |      | secure service     |
+-------+-------+-------+-------+---------+------+--------------------+
| 1.1   | Int   | 1     |       | High    | 3    | Portal: Service    |
|       | ernal |       |       |         |      | Metadata Purge     |
|       |       |       |       |         |      | Retired Services   |
|       |       |       |       |         |      |                    |
|       |       |       |       |         |      | The portal should  |
|       |       |       |       |         |      | remove services    |
|       |       |       |       |         |      | that have been     |
|       |       |       |       |         |      | inactive for some  |
|       |       |       |       |         |      | period of time.    |
+-------+-------+-------+-------+---------+------+--------------------+
| 1.1   | Int   | 1     |       | High    | 3    | Portal: Map View   |
|       | ernal |       |       |         |      | Service Status     |
|       |       |       |       |         |      |                    |
|       |       |       |       |         |      | The portal map     |
|       |       |       |       |         |      | view should        |
|       |       |       |       |         |      | indicate if the    |
|       |       |       |       |         |      | service is up or   |
|       |       |       |       |         |      | down.              |
+-------+-------+-------+-------+---------+------+--------------------+
| 2.0   | CTMS  | 1     |       | High    | 5    | Web Tools:         |
|       |       |       |       |         |      | SSO/Credential     |
|       |       |       |       |         |      | Delegation         |
|       |       |       |       |         |      | Component          |
|       |       |       |       |         |      |                    |
|       |       |       |       |         |      | Web applications   |
|       |       |       |       |         |      | need an easily     |
|       |       |       |       |         |      | pluggable          |
|       |       |       |       |         |      | component that     |
|       |       |       |       |         |      | enables the web    |
|       |       |       |       |         |      | application to     |
|       |       |       |       |         |      | retrieve a user's  |
|       |       |       |       |         |      | grid credentials   |
|       |       |       |       |         |      | without requiring  |
|       |       |       |       |         |      | the user to give   |
|       |       |       |       |         |      | the application    |
|       |       |       |       |         |      | his primary        |
|       |       |       |       |         |      | credentials        |
|       |       |       |       |         |      | (username and      |
|       |       |       |       |         |      | password). Web     |
|       |       |       |       |         |      | applications need  |
|       |       |       |       |         |      | this so that they  |
|       |       |       |       |         |      | can act on the     |
|       |       |       |       |         |      | user's behalf when |
|       |       |       |       |         |      | interacting with   |
|       |       |       |       |         |      | grid services.     |
|       |       |       |       |         |      | This component     |
|       |       |       |       |         |      | must also enable   |
|       |       |       |       |         |      | secure single-sign |
|       |       |       |       |         |      | on among           |
|       |       |       |       |         |      | applications in an |
|       |       |       |       |         |      | application group. |
|       |       |       |       |         |      | The CTMS workspace |
|       |       |       |       |         |      | is in dire need of |
|       |       |       |       |         |      | such functionality |
|       |       |       |       |         |      | to enable secure   |
|       |       |       |       |         |      | integration of     |
|       |       |       |       |         |      | applications and   |
|       |       |       |       |         |      | services.          |
|       |       |       |       |         |      |                    |
|       |       |       |       |         |      | Dependencies:      |
|       |       |       |       |         |      |                    |
|       |       |       |       |         |      | This functionality |
|       |       |       |       |         |      | requires either an |
|       |       |       |       |         |      | extension of       |
|       |       |       |       |         |      | Dorian, or the     |
|       |       |       |       |         |      | creation of a      |
|       |       |       |       |         |      | separate           |
|       |       |       |       |         |      | Cr                 |
|       |       |       |       |         |      | edentialDelegation |
|       |       |       |       |         |      | service.           |
+-------+-------+-------+-------+---------+------+--------------------+
| 2.0   | CTMS  | 1     |       | High    | 10   | Web Tools:         |
|       |       |       |       |         |      | SSO/Credential     |
|       |       |       |       |         |      | Delegation         |
|       |       |       |       |         |      | Component --       |
|       |       |       |       |         |      | Design             |
|       |       |       |       |         |      |                    |
|       |       |       |       |         |      | Design of the      |
|       |       |       |       |         |      | web-specific       |
|       |       |       |       |         |      | portion of the     |
|       |       |       |       |         |      | credential         |
|       |       |       |       |         |      | delegation         |
|       |       |       |       |         |      | solution.          |
+-------+-------+-------+-------+---------+------+--------------------+
| 2.0   | CTMS  | 1     |       | High    | 5    | Web Tools:         |
|       |       |       |       |         |      | WAYF-like          |
|       |       |       |       |         |      | Interface          |
|       |       |       |       |         |      |                    |
|       |       |       |       |         |      | Dorian should      |
|       |       |       |       |         |      | provide a web      |
|       |       |       |       |         |      | interface that     |
|       |       |       |       |         |      | presents the user  |
|       |       |       |       |         |      | with the list of   |
|       |       |       |       |         |      | Aut                |
|       |       |       |       |         |      | henticationService |
|       |       |       |       |         |      | instances that     |
|       |       |       |       |         |      | Dorian trusts. A   |
|       |       |       |       |         |      | user can select    |
|       |       |       |       |         |      | the                |
|       |       |       |       |         |      | Aut                |
|       |       |       |       |         |      | henticationService |
|       |       |       |       |         |      | to which he should |
|       |       |       |       |         |      | be redirected.     |
|       |       |       |       |         |      |                    |
|       |       |       |       |         |      | Dependencies:      |
|       |       |       |       |         |      |                    |
|       |       |       |       |         |      | This functionality |
|       |       |       |       |         |      | requires either an |
|       |       |       |       |         |      | extension of       |
|       |       |       |       |         |      | Dorian, or the     |
|       |       |       |       |         |      | creation of a      |
|       |       |       |       |         |      | separate           |
|       |       |       |       |         |      | Cr                 |
|       |       |       |       |         |      | edentialDelegation |
|       |       |       |       |         |      | service.           |
+-------+-------+-------+-------+---------+------+--------------------+
| 2.0   | CTMS  | 1     |       | High    | 5    | WebTools:          |
|       |       |       |       |         |      | Aut                |
|       |       |       |       |         |      | henticationService |
|       |       |       |       |         |      | Interface          |
|       |       |       |       |         |      |                    |
|       |       |       |       |         |      | An                 |
|       |       |       |       |         |      | Aut                |
|       |       |       |       |         |      | henticationService |
|       |       |       |       |         |      | should provide a   |
|       |       |       |       |         |      | web interfaces     |
|       |       |       |       |         |      | that allows the    |
|       |       |       |       |         |      | user to login use  |
|       |       |       |       |         |      | his primary        |
|       |       |       |       |         |      | credentials. It    |
|       |       |       |       |         |      | should then set    |
|       |       |       |       |         |      | the SAML assertion |
|       |       |       |       |         |      | of his identity in |
|       |       |       |       |         |      | the browser.       |
|       |       |       |       |         |      |                    |
|       |       |       |       |         |      | Dependencies:      |
|       |       |       |       |         |      |                    |
|       |       |       |       |         |      | This functionality |
|       |       |       |       |         |      | requires either an |
|       |       |       |       |         |      | extension of       |
|       |       |       |       |         |      | Dorian, or the     |
|       |       |       |       |         |      | creation of a      |
|       |       |       |       |         |      | separate           |
|       |       |       |       |         |      | Cr                 |
|       |       |       |       |         |      | edentialDelegation |
|       |       |       |       |         |      | service.           |
+-------+-------+-------+-------+---------+------+--------------------+
| 2.0   | CTMS  | 1     |       | High    | 10   | WebTools:          |
|       |       |       |       |         |      | Delegation Policy  |
|       |       |       |       |         |      | Interface          |
|       |       |       |       |         |      |                    |
|       |       |       |       |         |      | Dorian should      |
|       |       |       |       |         |      | provide a web      |
|       |       |       |       |         |      | interface that     |
|       |       |       |       |         |      | lets the user      |
|       |       |       |       |         |      | select how and to  |
|       |       |       |       |         |      | whom his           |
|       |       |       |       |         |      | credentials may be |
|       |       |       |       |         |      | delegated.         |
|       |       |       |       |         |      |                    |
|       |       |       |       |         |      | Dependencies:      |
|       |       |       |       |         |      |                    |
|       |       |       |       |         |      | This functionality |
|       |       |       |       |         |      | requires either an |
|       |       |       |       |         |      | extension of       |
|       |       |       |       |         |      | Dorian, or the     |
|       |       |       |       |         |      | creation of a      |
|       |       |       |       |         |      | separate           |
|       |       |       |       |         |      | Cr                 |
|       |       |       |       |         |      | edentialDelegation |
|       |       |       |       |         |      | service.           |
+-------+-------+-------+-------+---------+------+--------------------+
| 1.1   | Int   | 1     |       | High    | 25   | Portal: Unified    |
|       | ernal |       |       |         |      | Framework          |
|       |       |       |       |         |      |                    |
|       |       |       |       |         |      | Combine the Portal |
|       |       |       |       |         |      | and Browser into a |
|       |       |       |       |         |      | unified framework, |
|       |       |       |       |         |      | e.g. a JSR-168     |
|       |       |       |       |         |      | (portal) compliant |
|       |       |       |       |         |      | container.         |
|       |       |       |       |         |      |                    |
|       |       |       |       |         |      | Also should        |
|       |       |       |       |         |      | include            |
|       |       |       |       |         |      | investigation of   |
|       |       |       |       |         |      | wiki-integration.  |
+-------+-------+-------+-------+---------+------+--------------------+
| 2.0   | Int   | 1     |       | Medium  | 5    | Portal: Security   |
|       | ernal |       |       |         |      | Basic Model        |
|       |       |       |       |         |      |                    |
|       |       |       |       |         |      | Implement a basic  |
|       |       |       |       |         |      | security model     |
|       |       |       |       |         |      | that provides      |
|       |       |       |       |         |      | authentication and |
|       |       |       |       |         |      | authorization.     |
+-------+-------+-------+-------+---------+------+--------------------+
| 2.0   | Int   | 1     |       | Medium  | 3    | Portal: Analytical |
|       | ernal |       |       |         |      | Service Invocation |
|       |       |       |       |         |      |                    |
|       |       |       |       |         |      | Expose the         |
|       |       |       |       |         |      | Dynam              |
|       |       |       |       |         |      | icInvocationClient |
|       |       |       |       |         |      | API in the portal. |
|       |       |       |       |         |      |                    |
|       |       |       |       |         |      | **NOTE**: This API |
|       |       |       |       |         |      | does not yet       |
|       |       |       |       |         |      | exist, and this    |
|       |       |       |       |         |      | task assumes the   |
|       |       |       |       |         |      | API will be        |
|       |       |       |       |         |      | developed          |
|       |       |       |       |         |      | separately.        |
|       |       |       |       |         |      |                    |
|       |       |       |       |         |      | Dependencies:      |
|       |       |       |       |         |      |                    |
|       |       |       |       |         |      | -   workflow       |
|       |       |       |       |         |      |                    |
|       |       |       |       |         |      | -   security       |
+-------+-------+-------+-------+---------+------+--------------------+
| 2.0   | Int   | 1     |       | high    | 3    | Portal: Data       |
|       | ernal |       |       |         |      | Service Query      |
|       |       |       |       |         |      |                    |
|       |       |       |       |         |      | Expose the generic |
|       |       |       |       |         |      | DataService client |
|       |       |       |       |         |      | API in the portal. |
|       |       |       |       |         |      |                    |
|       |       |       |       |         |      | Dependencies:      |
|       |       |       |       |         |      |                    |
|       |       |       |       |         |      | -   data services  |
|       |       |       |       |         |      |                    |
|       |       |       |       |         |      | -   security       |
+-------+-------+-------+-------+---------+------+--------------------+
| 2.0   | Int   | 1     |       | high    | 3    | Portal: Federated  |
|       | ernal |       |       |         |      | Query Service      |
|       |       |       |       |         |      |                    |
|       |       |       |       |         |      | Expose the FQP     |
|       |       |       |       |         |      | client API in the  |
|       |       |       |       |         |      | portal.            |
|       |       |       |       |         |      |                    |
|       |       |       |       |         |      | Dependencies:      |
|       |       |       |       |         |      |                    |
|       |       |       |       |         |      | -   FQP            |
|       |       |       |       |         |      |                    |
|       |       |       |       |         |      | -   Security       |
+-------+-------+-------+-------+---------+------+--------------------+
| 2.0   | Int   | 1     |       | high    | 10   | Portal: D/CQL      |
|       | ernal |       |       |         |      | Builder            |
|       |       |       |       |         |      |                    |
|       |       |       |       |         |      | Provide a          |
|       |       |       |       |         |      | graphical query    |
|       |       |       |       |         |      | builder.           |
|       |       |       |       |         |      |                    |
|       |       |       |       |         |      | Dependences:       |
|       |       |       |       |         |      |                    |
|       |       |       |       |         |      | -   FQP            |
|       |       |       |       |         |      |                    |
|       |       |       |       |         |      | -   Data services  |
|       |       |       |       |         |      |                    |
|       |       |       |       |         |      | -   Security       |
+-------+-------+-------+-------+---------+------+--------------------+
| 2.0   | Int   | 1     |       | Medium  | 3    | Portal:            |
|       | ernal |       |       |         |      | Intermediate       |
|       |       |       |       |         |      | Result Cache       |
|       |       |       |       |         |      |                    |
|       |       |       |       |         |      | In order to        |
|       |       |       |       |         |      | support the        |
|       |       |       |       |         |      | construction of    |
|       |       |       |       |         |      | simple workflows,  |
|       |       |       |       |         |      | it will be         |
|       |       |       |       |         |      | necessary to       |
|       |       |       |       |         |      | provide/expose     |
|       |       |       |       |         |      | services that can  |
|       |       |       |       |         |      | cache intermediate |
|       |       |       |       |         |      | results.           |
|       |       |       |       |         |      |                    |
|       |       |       |       |         |      | Expose the         |
|       |       |       |       |         |      | Inter              |
|       |       |       |       |         |      | mediateResultCache |
|       |       |       |       |         |      | client API in the  |
|       |       |       |       |         |      | portal.            |
|       |       |       |       |         |      |                    |
|       |       |       |       |         |      | **NOTE:** This API |
|       |       |       |       |         |      | doesn't exist, and |
|       |       |       |       |         |      | this task assumes  |
|       |       |       |       |         |      | that this API will |
|       |       |       |       |         |      | be developed       |
|       |       |       |       |         |      | separately.        |
|       |       |       |       |         |      |                    |
|       |       |       |       |         |      | Dependencies:      |
|       |       |       |       |         |      |                    |
|       |       |       |       |         |      | -   intermediate   |
|       |       |       |       |         |      |     cache          |
|       |       |       |       |         |      |                    |
|       |       |       |       |         |      | -   security       |
+-------+-------+-------+-------+---------+------+--------------------+
| 2.0   | Int   | 1     |       | Medium  | 15   | Portal: Simple     |
|       | ernal |       |       |         |      | Workflow           |
|       |       |       |       |         |      |                    |
|       |       |       |       |         |      | Provide an         |
|       |       |       |       |         |      | interface to allow |
|       |       |       |       |         |      | the user to        |
|       |       |       |       |         |      | construct simple   |
|       |       |       |       |         |      | workflows from     |
|       |       |       |       |         |      | discovered         |
|       |       |       |       |         |      | services.          |
|       |       |       |       |         |      |                    |
|       |       |       |       |         |      | Dependencies:      |
|       |       |       |       |         |      |                    |
|       |       |       |       |         |      | -   workflow       |
|       |       |       |       |         |      |                    |
|       |       |       |       |         |      | -   security       |
|       |       |       |       |         |      |                    |
|       |       |       |       |         |      | -   intermediate   |
|       |       |       |       |         |      |     cache          |
+-------+-------+-------+-------+---------+------+--------------------+
| 1.1   | Int   | 1     |       | High    | 2    | Portal: Active     |
|       | ernal |       |       |         |      | Service Metadata   |
|       |       |       |       |         |      | Augmentation       |
|       |       |       |       |         |      |                    |
|       |       |       |       |         |      | Allow the "owner"  |
|       |       |       |       |         |      | of a service to    |
|       |       |       |       |         |      | add/remove         |
|       |       |       |       |         |      | arbitrary          |
|       |       |       |       |         |      | **additional**     |
|       |       |       |       |         |      | content to the     |
|       |       |       |       |         |      | service metadata   |
|       |       |       |       |         |      | displayed in the   |
|       |       |       |       |         |      | portal.            |
|       |       |       |       |         |      |                    |
|       |       |       |       |         |      | Dependencies:      |
|       |       |       |       |         |      |                    |
|       |       |       |       |         |      | -   portal         |
|       |       |       |       |         |      |     security model |
+-------+-------+-------+-------+---------+------+--------------------+
| 2.0   | Int   | 1     |       | Medium  | 5    | Portal: Syndicated |
|       | ernal |       |       |         |      | Service Metadata   |
|       |       |       |       |         |      | Augmentation       |
|       |       |       |       |         |      |                    |
|       |       |       |       |         |      | Allow the "owner"  |
|       |       |       |       |         |      | of a service to    |
|       |       |       |       |         |      | specify a          |
|       |       |       |       |         |      | syndication feed   |
|       |       |       |       |         |      | (RSS, Atom, etc.)  |
|       |       |       |       |         |      | that will          |
|       |       |       |       |         |      | constantly update  |
|       |       |       |       |         |      | the service's      |
|       |       |       |       |         |      | metadata.          |
|       |       |       |       |         |      |                    |
|       |       |       |       |         |      | Dependencies:      |
|       |       |       |       |         |      |                    |
|       |       |       |       |         |      | \- portal security |
|       |       |       |       |         |      | model              |
+-------+-------+-------+-------+---------+------+--------------------+
| 2.0   | Int   | 1     |       | Medium  | 3    | Portal: User       |
|       | ernal |       |       |         |      | Comments           |
|       |       |       |       |         |      |                    |
|       |       |       |       |         |      | Enable users to    |
|       |       |       |       |         |      | add comments about |
|       |       |       |       |         |      | services or        |
|       |       |       |       |         |      | operations to the  |
|       |       |       |       |         |      | portal.            |
|       |       |       |       |         |      |                    |
|       |       |       |       |         |      | Dependencies:      |
|       |       |       |       |         |      |                    |
|       |       |       |       |         |      | \- portal security |
|       |       |       |       |         |      | model              |
+-------+-------+-------+-------+---------+------+--------------------+
| 2.0   | Int   | 1     |       | Medium  | 5    | Portal: Map View   |
|       | ernal |       |       |         |      | of Service         |
|       |       |       |       |         |      | Discovery Results  |
+-------+-------+-------+-------+---------+------+--------------------+
| 2.0   | Int   | 1     |       | Medium  | 3    | Portal: Map View   |
|       | ernal |       |       |         |      | of Workflow        |
|       |       |       |       |         |      |                    |
|       |       |       |       |         |      | Display the        |
|       |       |       |       |         |      | structure and      |
|       |       |       |       |         |      | status of a        |
|       |       |       |       |         |      | workflow on the    |
|       |       |       |       |         |      | map.               |
|       |       |       |       |         |      |                    |
|       |       |       |       |         |      | Dependencies:      |
|       |       |       |       |         |      |                    |
|       |       |       |       |         |      | \- workflow        |
+-------+-------+-------+-------+---------+------+--------------------+
| 2.0   | Int   | 1     |       | high    | 3    | Portal: Map View   |
|       | ernal |       |       |         |      | of Semantic        |
|       |       |       |       |         |      | Linkages           |
|       |       |       |       |         |      |                    |
|       |       |       |       |         |      | Display linkages   |
|       |       |       |       |         |      | among services     |
|       |       |       |       |         |      | based on supplied  |
|       |       |       |       |         |      | semantic criteria. |
|       |       |       |       |         |      |                    |
|       |       |       |       |         |      | Dependences:       |
|       |       |       |       |         |      |                    |
|       |       |       |       |         |      | \- metadata        |
|       |       |       |       |         |      | enhancements       |
+-------+-------+-------+-------+---------+------+--------------------+
| 2.0   | Int   | 1     |       | Medium  | 5    | Portal: Service    |
|       | ernal |       |       |         |      | Directory          |
|       |       |       |       |         |      | Categorized Views  |
|       |       |       |       |         |      |                    |
|       |       |       |       |         |      | Display services   |
|       |       |       |       |         |      | in browseable      |
|       |       |       |       |         |      | categories.        |
+-------+-------+-------+-------+---------+------+--------------------+
| 2.0   | Int   | 1     |       | Medium  | 3    | Portal: Admin      |
|       | ernal |       |       |         |      | Service Lifecylcle |
|       |       |       |       |         |      |                    |
|       |       |       |       |         |      | Allow one to       |
|       |       |       |       |         |      | specify a policy   |
|       |       |       |       |         |      | regarding how/when |
|       |       |       |       |         |      | services should be |
|       |       |       |       |         |      | purged from        |
|       |       |       |       |         |      | portal. This would |
|       |       |       |       |         |      | include cases in   |
|       |       |       |       |         |      | which services     |
|       |       |       |       |         |      | should be          |
|       |       |       |       |         |      | unconditionally    |
|       |       |       |       |         |      | banned.            |
|       |       |       |       |         |      |                    |
|       |       |       |       |         |      | Dependencies:      |
|       |       |       |       |         |      |                    |
|       |       |       |       |         |      | \- portal security |
+-------+-------+-------+-------+---------+------+--------------------+
| 2.0   | Int   | 1     |       | Medium  | 3    | Portal: Admin      |
|       | ernal |       |       |         |      | Participant Info   |
|       |       |       |       |         |      |                    |
|       |       |       |       |         |      | Allow the          |
|       |       |       |       |         |      | administrator to   |
|       |       |       |       |         |      | edit participant   |
|       |       |       |       |         |      | information.       |
|       |       |       |       |         |      |                    |
|       |       |       |       |         |      | Dependencies:      |
|       |       |       |       |         |      |                    |
|       |       |       |       |         |      | \- portal security |
+-------+-------+-------+-------+---------+------+--------------------+
| 2.0   | Int   | 1     |       | Medium  | 3    | Portal: Admin      |
|       | ernal |       |       |         |      | Participant Front  |
|       |       |       |       |         |      | Page               |
|       |       |       |       |         |      |                    |
|       |       |       |       |         |      | Allow the          |
|       |       |       |       |         |      | administrator to   |
|       |       |       |       |         |      | edit information   |
|       |       |       |       |         |      | on the front page  |
|       |       |       |       |         |      | of the portal,     |
|       |       |       |       |         |      | e.g. the "caGrid   |
|       |       |       |       |         |      | News" or "Did you  |
|       |       |       |       |         |      | know?" sections.   |
|       |       |       |       |         |      |                    |
|       |       |       |       |         |      | Dependencies:      |
|       |       |       |       |         |      |                    |
|       |       |       |       |         |      | \- portal security |
+-------+-------+-------+-------+---------+------+--------------------+
| 2.0   | Int   | 1     |       | Medium  | 10   | Portal: Security   |
|       | ernal |       |       |         |      | UI Dorian          |
+-------+-------+-------+-------+---------+------+--------------------+
| 2.0   | Int   | 1     |       | Medium  | 10   | Portal: Security   |
|       | ernal |       |       |         |      | UI Grid Grouper    |
+-------+-------+-------+-------+---------+------+--------------------+
| 2.0   | Int   | 1     |       | Medium  | 10   | Portal: Security   |
|       | ernal |       |       |         |      | UI GTS             |
+-------+-------+-------+-------+---------+------+--------------------+
| F     | Int   | 1     |       | Medium  | 3    | Portal: Discovery  |
| uture | ernal |       |       |         |      | Tag Cloud          |
+-------+-------+-------+-------+---------+------+--------------------+
| F     | Int   | 1     |       | Medium  | 5    | Portal: Discovery  |
| uture | ernal |       |       |         |      | EVS Browser        |
+-------+-------+-------+-------+---------+------+--------------------+
| F     | Int   | 1     |       | Medium  | 5    | Portal: Discovery  |
| uture | ernal |       |       |         |      | caDSR Browser      |
+-------+-------+-------+-------+---------+------+--------------------+

Where,

Release: caGrid 1.1, caGrid 2.0 or future (if not sure)

User: Specify the user project that has identified the specific feature
item. If there are multiple users, identify at least one project. If
this is an internal request (from developers), put the user as
"internal".

Iteration: Not filled as of yet. If the release is determined to be done
in multiple iterations, then the specific iteration during which the
feature will be implemented will be tracked by this field.

GForge: Every scope item needs to be added to the GForge task so that
its status can be tracked. Also, if there are dependent features, this
number is used in the description field to identify the dependency

Priority: High, Medium, Low

LOE: Average Estimate for design, implementation and unit testing

Description: Short description about the feature, including any
technical details deemed important. The idea is to convey the crux of
what the issue or feature is for the caGrid Management team.