"Engineering Agile Requirements: Epics, Use Cases & User Stories" - Session 3 of INCOSE Agile MBSE Lunch & Series with Bruce Powel Douglass
- Shared screen with speaker view

28:14
How to sign up for an INCOSE associate membership: https://www.incose.org/docs/default-source/default-document-library/howto_createa_cab_associateaccountfb56038572db67488e78ff000036190a.pdf?sfvrsn=768d64c7_0

58:52
What's the difference between "HIgh Level" use cases and Epics?

01:00:05
@Marco - you may be referring to SAFe vs LeSS/Scrum

01:04:56
Slide 10(?) Other SysML methods suggest against including (via include relationship) many use cases against one to avoid decomposing use cases. This seems to conflict what you are proposing. Is this a correct interpretation? Would the high level use cases have a set of other behavioral or structural elements or requirements against them or only on the leaf use cases, or undefined?

01:07:56
In a complex products (system of systems), how do Epics, Use cases and user stories relate to System, subsystem and component requirements in the hierarchy of requirements?Can Epics,Use Cases and User stories be used for systems/subsystems at each level of hierarchy (when a complex product is being decomposed)?

01:13:56
Slide 11: I understand that user stories are focussed on the user goals. What is the equivalent of user stories for stakeholders needs? And how these relate with stakeholders requirements?

01:22:38
Hello Dr Bruce! The best content as always! Can you share how SysML fits with SAFe? How SAFe suggest to capture and manage rest of the artifacts which are not system engineering specific or can all be in SysML?

01:23:51
Hi, where can one access the recordings of these seminars?

01:26:24
Thank you Bruce, excellent presentation

01:28:46
Can you give your view on similarities or differences between Capella MBSE / Arcadia method Vs Sysml/Agile MBSE in this context (Epic, Use case and Scenarios)?

01:36:54
Can I "+1" Dr Bruce's interpretation of SAFe? :-)

01:37:20
yes you can 😀

01:37:27
Thanks, it answers my question and it triggers more reflections. If user stories relates to a sub set of stakeholders requirements, and assuming that use cases relates to systems requirements, I wonder how we can maintain the classical hierarchy where systems requirements derive from stakeholder requirements, which seems to contradict your hierarchy where user stories are components of use cases?

01:38:36
👍

01:38:57
👍👍👍

01:41:29
Inspiring answer! Thank you very much!

01:44:35
Thank you!!!

01:44:38
Where can we access the recordings?

01:44:41
Thank you!!