@inproceedings {RELAW2014,
	title = {Current and Necessary Insights Into SACM: an Analysis Based on Past Publications},
	journal = {IEEE 7th International Workshop on Requirements Engineering and Law (RELAW 2014)},
	year = {2014},
	month = {August},
	pages = {10-13},
	publisher = {IEEE Computer Society},
	type = {Workshop},
	abstract = {SACM (Structured Assurance Case Metamodel) is a standard for assurance case creation and exchange. Although it is a promising initiative towards providing common system assurance practices and improving them, the document of the standard provides little information about how to use SACM, its benefits, and its limitations. Consequently, it is difficult to determine what SACM can be used for and what needs to be investigated about the standard. This position paper aims to address this issue by reviewing 28 publications that have referred to SACM. Based on the insights gained, we propose a set of aspects that need to be further studied. This information can be valuable for anyone interested in the standard.},
	keywords = {Workshop},
	isbn = {978-1-4799-6325-6},
	author = {Jose Luis {de la Vara}},
	editor = {Amyot, Daniel and Ant{\'o}n, A.I. and Breaux, T. and Massey, A.K. and Siena, A.}
}
@inproceedings {Simula.simula.2820,
	title = {Insights on the Use of OCL in Diverse Industrial Applications},
	journal = {8th System Analysis and Modelling Conference (SAM{\textquoteright}14)},
	year = {2014},
	publisher = {Springer},
	type = {Conference},
	address = {Switzerland},
	abstract = {The Object Constraint Language (OCL) is a widely accepted language, standardized by OMG, for specifying constraints at various meta levels (e.g., meta-models and models). Despite its wide acceptance, there is a lack of understanding about terminology and purposes for which OCL can be used. In this paper, we aim to reduce this gap and provide guidance for applying OCL in practical contexts and we report our experience of applying OCL for different industrial projects in diverse domains: Communications and Control, Oil and Gas production, Energy Equipment and Services, and Recycling. Based on our experience, first, we unify the commonly used terminology in the literature for applying OCL in different ways for addressing diverse industrial problems. Second, we report the key results of the industrial application of OCL. Finally, we provide guidance to researchers and practitioners for choosing an appropriate meta-level and purpose for their specific industrial problem at hand.},
	keywords = {Conference},
	author = {Ali, Shaukat and Yue, Tao and Muhammad Zohaib {Iqbal} and Rajwinder Kaur {Panesar-Walawege}},
	editor = {Amyot, Daniel and Pau Fonseca i. {Casas} and Mussbacher, Gunter}
}
@inproceedings {Simula.simula.2822,
	title = {A Systematic Approach to Automatically Derive Test Cases From Use Cases Specified in Restricted Natural Languages},
	journal = {8th System Analysis and Modelling Conference (SAM{\textquoteright}14)},
	year = {2014},
	publisher = {Springer},
	type = {Conference},
	address = {Switzerland},
	abstract = {In many domains, such as avionics, oil and gas, and maritime, a common practice is to derive and execute test cases manually from requirements, where both requirements and test cases are specified in NL by domain experts. The manual execution of test cases is largely dependent on the domain experts who wrote the test cases. The process of manual writing of requirements and test cases introduce ambiguity in their description and in addition test cases may not be effective since they may not be derived by systematic applying coverage criteria. In this paper, we report a systematic approach to support automatic derivation of manually executable test cases from use cases. Both use cases and test cases are specified in restricted NLs along with carefully defined templates implemented in a tool. We evaluate our approach with four case studies (in total having 30 use cases and 579 steps of flow of events), two of which are industrial case studies from the oil and gas and avionics domains. Results show that our tool was able to correctly process all the case studies and systematically (by following the carefully defined structure coverage criterion) generate 30 TCSs and 389 test cases. Moreover our approach allows defining different test coverage criteria on requirements other than the one already implemented in our tool.},
	keywords = {Conference},
	author = {Zhang, Man and Yue, Tao and Ali, Shaukat and Zhang, Huihui and Wu, Ji},
	editor = {Amyot, Daniel and Pau Fonseca i. {Casas} and Mussbacher, Gunter}
}
