webinos Use Cases - Open Day

download webinos Use Cases - Open Day

If you can't read please download the document

description

An overview of the Use Case and requirements project driving the webinos technology. Presented By Andre Paul of Fraunhofer Institute

Transcript of webinos Use Cases - Open Day

  • 1. WebinosWP2 Andr Paul Future Applications and Media (FAME)Fraunhofer Institute for Open Communication [email protected]

2. Where we are D2.4 Updates on Scenarios and Use cases sendto EU beginning of may D2.5 is pending, final wrap up is waiting to beclosed According to DOW4 roughly only half of theresources used so far and 1/3 is not planned WP2 mostly done (one deliverable left) App competition is the only active activity (deliverable M36) VM will also create an update to last years open governanceindex Background activities expected for adapting and extendingexisting work over time until end of project life 3. D2.4 Scenarios revision re-written to better envisage webinos as we now understand it aligned the usability research of D2.7 and D2.8 incorporating context of use description incorporating personas scenarios which were subject to deletion were analyzed for elements that can be incorporated into other scenarios. A number of other EU projects were analyzedregarding use cases and requirements but did not findout major direct impact on the existing work (e.g,actuator API) First App Competition description 4. D2.4 Use cases were basically cleaned up re-grouped to match groups used for requirements (moreappropriate categorization, common scheme across WP2deliverables) Majority of deleted use cases were found as to be too applicationspecific Many of these use cases could be realized by implementingapplications (e.g., prior example section) Based on our revision of the scenarios, we concluded that additionalexample use cases were unnecessary. Also a number of general use cases were removed Duplications other similar use cases that were appropriately adapted 5. D2.5 requirements were improved in wording,comprehensibility and to better match to designdecisions made in the last couple of months Clean-up, roughly a third of existing requirements wereremoved superseding or duplications referring to application functionalities fit criteria like requirements were removed. Pending finalization of land scape update 6. Traceability / featureproposals Within webinos we need to create traceability for existing(phase I) features and also for new features For example if roadmap identifies features that are seento be new, WP2 should at least identify related usecases and requirements (better start with narrativescenario description) WP2 needs to state that the feature can be realized withX,Y,Z or WP2 may create new UC/Reqs or may decidethat the feature should not be considered as being partof webinos may be a demo app or completely out of scope Generic process:http://dev.webinos.org/redmine/projects/wp2-4/wiki/Proposed_external_functionality 7. Traceability: fromscenarios to back-logs Scenarios do have an identifier and a title,e.g., S-DA1: Smart Device Integration, andhave attached supporting use cases No use cases => no scenario Use cases stating related scenarios andrelated requirements No requirement => no use case 8. Traceability: fromscenarios to back-logs Use cases needto have attacheduse case mapsstating whereis/could bewebinos involved. No webinoscomponentinvolved => nouse case (but that most probably will be created by wp2peoples) 9. Traceability: fromscenarios to back-logs Requirements having attached scenarios,use cases and backlog items (but not all,non-functional reqs., supportingrequirements) Automatic build process creates related wiki pages creates concept maps 10. Traceability: fromscenarios to back-logs Proposals to be send to wp2 list or better to createa wiki page athttp://dev.webinos.org/redmine/projects/wp2-4/wiki/Proposed_Updates No traceability between wp2 and specs as well asspecs and WP4. How to deal with this? What about making WP2 content (and maybeother WP repositories) available to the public too? Transparency Same githhub? Having all together vs. separating code from text 11. App competitions 12. Thank you!Questions? Follow us:www.webinos.org Contact us: [email protected] Fork @ GitHub:https://github.com/webinos/Webinos-Platform Become affiliate: http://webinos.org/be-part-of-webinos/ Todays speaker:[email protected]