@inproceedings {QUAMES2013,
	title = {Dealing With Software Model Quality in Practice: Experience in a Research Project},
	journal = {13th International Conference on Quality Software (QSIC 2013)},
	year = {2013},
	publisher = {IEEE},
	type = {Conference},
	address = {Najing},
	abstract = {Although past research has resulted in different means to deal with software model quality, creation of adequate software models remains challenging. Any modelling effort must be carefully analysed and planned before it starts, and definition or adoption of modelling guidelines is usually necessary. In addition, the amount of publications addressing model quality in practice is low, and the knowledge about others{\textquoteright} experience regarding model quality is limited. This paper reports on our experience in dealing with software model quality in the context of a project between industry and academia. Such a project corresponds to a large-scale research project in which modelling has been used both as part of the necessary work for executing the project and for creating project results. We present how we have dealt with model quality in requirements modelling and in conceptual model specification, as well as a set of lessons learned. The insights provided can help both researchers and practitioners when having to deal with software model quality.},
	author = {Jose Luis {de la Vara} and Espinoza, Huascar},
	editor = {Gotlieb, Arnaud}
}
@inproceedings {Simula.simula.1098,
	title = {Challenges for an Open and Evolutionary Approach to Safety Assurance and Certification of Safety-Critical Systems},
	journal = {1st International Workshop on Software Certification (WoSoCER{\textquoteright}11)},
	year = {2011},
	publisher = {IEEE},
	type = {Workshop},
	abstract = {Safety assurance and certification are amongst the most expensive and time-consuming tasks in the development of safety-critical embedded systems. The increasing complexity and size of this kind of systems combined with the growing market demand requires the industry to implement a coherent reuse strategy. A major problem arises as typically a safetycritical product and accompanying safety evidence is monolithic, based on the whole product, and evolutions to the product become costly and time consuming because they entail regenerating the entire evidence-set. Another key difficulty appears when trying to reuse products from one application domain in another, because they are constrained by different standards and the full safety assurance certification process is applied as for a new product, thus reducing the return on investment of such reuse decision.},
	isbn = {DOI:10.1109/WoSoCER.2011.15},
	author = {Espinoza, Huascar and Ruiz, Alejandra and Sabetzadeh, Mehrdad and Panoroni, Paolo},
	editor = {Pietrantuono, R. and Silva, N.}
}
