Is Agile methodology suitable for Firmware development? More generally, when Hardware and Software must be co-developed and manufactured, would Agile still be a good approach for the software development? Perhaps, Firmware can still be decomposed into an OTP (One Time Programmable) piece + a piece that can be updated "over the air", in which case the latter could still follow Agile. But what has been your experience with real Firmware projects? Thanks

I like the model organization structure that Harmony aMBSE is suggesting in Agile System Engineering, chapter 3.3 Organize Your Models Like It Matters. I have one question though: What is the reason that the Deployment View Pkg is in the subsystem models? That means that there is no holistic Deployment View (sometimes also called "technical context"), because the information is split over different subsystem models, right? I believe this view is especially important to integration and network guys. I also think that it is not a good idea to put a common Deployment View in the SE model as you do not want the dependencies to the physical interface packages there. I am wondering, does it make sense to keep a "complete" Deployment Package in the shared model? Please let me know what you think.

Dear Bruce, in Harmony ESW process you added User Stories as an additional starting point to the Microcycle. I think User Stories are usually used to describe the "problem" or "expectation" of a stakeholder regarding the "product". It is maybe something like a high level requirements elicitation approach, which differs from Use Cases. What are your experiences and best practices to work with User Stories (e.g. high level approach) and Use Cases (e.g. detailed approach) regarding high-fidelity modelling and requirements refinement? Do you have a taxonomy regarding requirements, use cases, user stories and modelling? Thank you. Best regards, Matthias