{"department":[{"_id":"241"},{"_id":"662"}],"user_id":"8472","citation":{"mla":"Fockel, Markus, et al. Model-Based Requirement Pattern Catalog. 2017.","apa":"Fockel, M., Holtmann, J., Koch, T., & Schmelter, D. (2017). Model-based Requirement Pattern Catalog. Paderborn, Germany.","ieee":"M. Fockel, J. Holtmann, T. Koch, and D. Schmelter, Model-based Requirement Pattern Catalog. Paderborn, Germany, 2017.","short":"M. Fockel, J. Holtmann, T. Koch, D. Schmelter, Model-Based Requirement Pattern Catalog, Paderborn, Germany, 2017.","ama":"Fockel M, Holtmann J, Koch T, Schmelter D. Model-Based Requirement Pattern Catalog. Paderborn, Germany; 2017.","bibtex":"@book{Fockel_Holtmann_Koch_Schmelter_2017, place={Paderborn, Germany}, title={Model-based Requirement Pattern Catalog}, author={Fockel, Markus and Holtmann, Jörg and Koch, Thorsten and Schmelter, David}, year={2017} }","chicago":"Fockel, Markus, Jörg Holtmann, Thorsten Koch, and David Schmelter. Model-Based Requirement Pattern Catalog. Paderborn, Germany, 2017."},"place":"Paderborn, Germany","abstract":[{"lang":"eng","text":"Scenario-based requirements engineering addresses the message-based coordination of software-intensive systems and enables, if underpinned with formal languages, automatic requirements validation techniques for improving the quality of a requirements specification. One of such requirements engineering approaches bases on a recent visual Live Sequence Chart variant compliant to the Unified Modeling Language, so-called Modal Sequence Diagrams (MSDs). The usage of patterns is known to be constructive thanks to assembling solutions by means of reusable building blocks that are proven in practice, so that recurring problems do not need to be solved over and over again. Thus, patterns also gained momentum in the area of requirements documentation. In this technical report, we introduce a model- and scenario-based pattern catalog for MSD requirements. Our MSD requirement pattern catalog consolidates and unifies 86 requirement patterns from three well-known, practice-oriented requirement pattern catalogs, each covering different aspects."}],"date_updated":"2022-01-06T06:54:38Z","status":"public","author":[{"first_name":"Markus","id":"8472","orcid":"0000-0002-1269-0702","last_name":"Fockel","full_name":"Fockel, Markus"},{"full_name":"Holtmann, Jörg","last_name":"Holtmann","id":"3875","orcid":"0000-0001-6141-4571","first_name":"Jörg"},{"full_name":"Koch, Thorsten","last_name":"Koch","id":"13616","first_name":"Thorsten"},{"id":"40982","first_name":"David","orcid":"0000-0001-7787-5380","full_name":"Schmelter, David","last_name":"Schmelter"}],"year":"2017","language":[{"iso":"eng"}],"_id":"20793","report_number":"tr-ri-17-354","type":"report","date_created":"2020-12-17T13:31:36Z","title":"Model-based Requirement Pattern Catalog"}