Abstract
AbstractThis paper describes a visual and textual requirements representation based upon Model‐Based Systems Engineering (MBSE) requirements patterns. This underlying representation is a rethinking of the concepts behind systems requirements. It takes into account the subjective stakeholder value, the life cycle modes, objective technical behavior and it combines the best of agile User Stories with MBSE patterns.This underlying MBSE requirements pattern improves the quality of conversations between key stakeholders of the system. Agile User Stories begin the conversation by focusing on the problem domain, addressed by MBSE pattern features. MBSE patterns then continue the conversation for the technical requirements.The content and relationships between the key MBSE patterns capture the product learning of the organization for use on future applications of similar products. The complexity of re‐use and re‐application is reduced by configurability. Organizations re‐apply this product learning in new products resulting in lower costs and increased quality.
Sign-in/Register to access full text options 
Free) 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a call
