![]() Nejati, S., Sabetzadeh, M., Chechik, M., Easterbrook, S., Zave, P.: Matching and merging of statecharts specifications. Méndez Fernández, D., Wagner, S., Lochmann, K., Baumann, A., de Carne, H.: Field study on requirements engineering: investigation of artefacts, project parameters, and execution strategies. In: Proceedings of the 13th International Conference on Model Driven Engineering Languages and Systems (MoDELS 2010) Méndez Fernández, D., Penzenstadler, B., Kuhrmann, M., Broy, M.: A meta model for artefact-orientation: fundamentals and lessons learned in requirements engineering. Lindland, O.I., Sindre, G., Sølverg, A.: Understanding quality in conceptual modelling. In: Proceedings of the 153h of the 8th International Conference on on Global Software Engineering (ICGSE 2013) (2013) Kuhrmann, M., Méndez Fernández, D., Groeber, M.: Towards artifact models as process interfaces in distributed software projects. Kuhrmann, M., Méndez Fernández, D.: From pragmatic to systematic software process improvement: an evaluated approach. Kathleen, C., Palmquist, M.: Extracting, representing, and analyzing mental models. In: Proceedings of the International Workshop on Global Integrated Model Management (2006)īutting, A., Greifenberg, T., Rumpe, B., Wortmann, A.: On the Need for Artifact Models in Model-Driven Systems Engineering Projects. Model 60, 1 (2018)īrunet, G., Chechik, M., Easterbrook, S., Nejati, S., Niu, N., Sabetzadeh, M.: A manifesto for model merging. ![]() 29, 21–43 (2010)īroy, M.: A logical approach to systems engineering artifacts: semantic relationships and dependencies beyond traceability-from requirements to functional and architectural views. In: Proceedings of the 20th ACM Symposium on Applied Computing (2005)īraun, P., Broy, M., Houdek, F., Kirchmayr, M., Müller, M., Penzenstadler, B., Pohl, K., Weyer, T.: Guiding requirements engineering for software-intensive embedded systems in the automotive industry. In: Dritter Workshop zur Zukunft der Entwicklung softwareintensiver eingebetteter Systeme (2013)īraun, C., Wortmann, F., Hafner, M., Winter, R.: Method construction: a core approach to organizational engineering. Int J Web Inf Syst 5, 271 (2009)īöhm, W., Vogelsang, A.: An artifact-oriented framework for the seamless development of embedded systems. Our contribution shall foster the long overdue and too often underestimated terminological discussion on what artefacts are to provide a common ground with clearer concepts and principles for future software engineering contributions, such as the design of artefact-oriented development processes and tools.Īltmanninger, K., Seidl, M., Wimmer, M.: A survey on model versioning approaches. Abstraction and refinement relations between these levels allow correlating artefacts to each other and defining the notion of related, refined, and equivalent artefacts. This metamodel defines artefacts at three levels. ![]() We further contribute a metamodel that provides a description of an artefact that is independent from any underlying process model. In this position paper, we provide a positioning and critical reflection upon the notion of artefacts in software engineering at different levels of perception and how these relate to each other. Therefore, it is our goal that the term artefact be standardised so that researchers and practitioners have a common understanding for discussions and contributions. In fact, there does not exist a common terminology. This often leads to approaches being grounded in a fuzzy, unclear understanding of the essential concepts involved. Despite its relevance, the exact denotation of the term ‘artefact’ is still not clear due to a variety of different understandings of the term and to a careless negligent usage. In the following, we use the term ‘artefact’ including all these other terms. Other terms like documents, deliverables, or work products are widely used in software development communities instead of the term artefact. Artefacts play a vital role in software and systems development processes.
0 Comments
Leave a Reply. |