![]() |
Page History
...
Item | Information/Response |
---|---|
Date: | 12/15/2009 |
Requirement # unique id <SemCon Ops Initiative>.<analysts initials><requirement number> | Init3dbw7 |
Originator/Customer's Name: | Anand Basu |
Originator/Customer's Company: | CBIIT Application Engineering |
Summary of requirement pre-interview, by Reviewer: | Application developers covering a broad spectrum of disciplines need to be able to find data and services that can be integrated, without knowing much about the infrastructure. It should be easy to use, Taverna and caB2B are too difficult/awkward to use. A workflow authoring tool should leverage so that the end user (application developer and researcher) should not have easily use the infrastructure to create workflows without having to figure out how to integrate the data or services, the infrastructure should step them through it and just ask for things that are not already available - the infrastructure services and UIs, portals, need to go beyond just finding data or services based on search terms. Reuse of Platform need to be able to reuse stored Platform Independent Models (PIMs) to create Platform Specific Models needs to be almost (PSM) - almost transparent to the end user (application developers) . Like scratch.mit.edu, everything you need to know shoudl be easily accessible from the download page. This includes click through installation and setup for using the infrastructure, easy access to getting started instructions, release notes, frequently asked questions specific to each supported platform (PC, MAC, Linux etc), and links to submit trouble tickets or access the support desk. Ideally, the UIs would be intuitive, drag and drop - if the data does not 'fit' into the service, the system should do the analysis in the background and explain what is needed in order for the service to accept the data, if there is an existing service that could be used to pre-process the data, the system should discover that service and present it to the end user. If you have data that is of a particular type, the system could find the services that can take your data, then show you other services that take the result of the services you have executed. For example, the workflow tool should help users author sensible workflows be recognizign things that are processign raw data as input to another higher level service and try to automatically organize a workflow based on the data the user has access to- the metadata should be compared and possible integration points served up. |
Recommended Next Step Enter one: Follow-up interview, Observe, Use Case Template (text), Use Case Model (formalized/UML diagram), Group Discussion, Prototype, Waiting Room | Use case decomposition. |
...
Item | Description | Information/Response |
---|---|---|
Stakeholder Community: | Enter appropriate category of stakeholder from Primary Stakeholders:
| |
Requirement Type (required) | Analyst's assessement of the most appropriate category/type of requirement (no need to ask interviewee):
|
|
ConOp Initiative(s) |
|
|
High Level Use Case Summary) | Please write a short descriptive narrative use case; the steps or activities in this use case are usually the things the user wants to accomplish with the system (user/actor's goals). |
|
Use Case Linkage (required) | Which use case(s) is this requirement linked to? (should follow Use Case numbering scheme <SemCon Ops Initiative>.<analysts initials><requirement number>.<use case number>, for example Init1dbw1.1, Init1dbw1.2, Init2dbw2.1, 2.2, etc. | Use case Number(s): |
Conflicts / Dependencies(required) | Are there any conflicts with other requirements / use cases? | Yes OR No - If yes, what and why? |
Next Step (required) | After reviewing the results of the interview, the forum, and all other materials related to this requirement, the analyst should recommend the next step, then attach the Tiny Link (on the Info tab) for this page to the Master List table. | Enter one: Follow-up interview, Observe, Use Case Template (text), Use Case Model (formalized/UML diagram), Group Discussion, Prototype, Waiting Room |