Comments (4)
I think it can be used as a framework for our current use case collecting activity.
(Domain - Scenario - Functional Building Block / Non-Functional Requirement)
For example:
- Domain/Scenario: (Industrial) Big Data, Fleet management
- Functional Building Block: Discovery, Multi-Vendor system integration, Accessibility, Cross-protocol integration
- Non-Functional Requirement:
Or, for example, IIRA has following four view point:
- Business viewpoint
- Usage viewpoint
- Functional viewpoint
- Implementation viewpoint.
We can also use these framework for collecting use cases.
from wot-usecases.
We agreed to split the work to review chapter 1 of the document on a section (Domain) basis:
Domain: Other - Toumura-san
Domain: Smart Cities: Michael McCool
Domain: Transportation: Zoltan
Domain: Manufacturing: Michael L.
Domain: Logistics: Michael L.
Domain: Smart Grids: <Siemens/Ege/Christian?>
Home Automation SmartThings
Healthcare and Medical <Siemens?>
Volunteers for names in < ... > need to be confirmed.
Please review to answer the questions:
Is this use case covered by the existing specs?
If not, what are the gaps?
from wot-usecases.
We reviewed the UC document and did the due diligence.
from wot-usecases.
No further work is expected here, otherwise a new issue should be filed.
from wot-usecases.
Related Issues (20)
- Update Privacy Requirements
- Review Discovery Requirements and Use Case Links HOT 3
- Update Status of each Discovery Requirement
- [Discuss] Focus on Functional Requirements HOT 11
- [Process] Not proceeding to feature definition if there is no gap HOT 1
- [Process] Not accepting Use Cases if there is no hint of a gap HOT 1
- [Process] Aligning with Relationship between groups document HOT 1
- Thoughts from the TD Use Case Discussions HOT 5
- How to extract information, e.g., about requirements, from the UC description? HOT 1
- When/which level of UC description to be generated? HOT 1
- Who/how to submit UCs? HOT 1
- How to deal with gap analysis? Ned clear definition for "gap analysis HOT 1
- How to deal with gap analysis? Need clear definition for "gap analysis" HOT 5
- The structure/category of the use case description HOT 1
- What level (technical, functional, business, etc.) to be described for use cases? HOT 1
- What would be the possible items for use case description?
- How to deal with the feedback from the TFs working on each specification HOT 1
- Expectations of the TD stakeholders from the Use Case process
- What we mean by "functional" and "technical"
- What we expect for "user stories" from the Use Case description HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from wot-usecases.