A Structured Approach for Eliciting, Modeling, and Using Quality-Related Domain Knowledge

In requirements engineering, properties of the environment and assumptions about it, called domain knowledge, need to be captured in addition to exploring the requirements. Despite the recognition of the significance of capturing and using the required domain knowledge, it might be missing, left implicit, or be captured inadequately during the software development. This results in an incorrect specification. Moreover, the software might fail to achieve its quality objectives because of ignored required constraints and assumptions. In order to analyze software quality properly, we propose a structured approach for eliciting, modeling, and using domain knowledge. We investigate what kind of quality-related domain knowledge is required for the early phases of quality-driven software development and how such domain knowledge can be systematically elicited and explicitly modeled to be used for the analysis of quality requirements. Our method aims at improving the quality of the requirements engineering process by facilitating the capturing and using of implicit domain knowledge.

[1]  Axel van Lamsweerde,et al.  Reasoning About Alternative Requirements Options , 2009, Conceptual Modeling: Foundations and Applications.

[2]  Jaap-Henk Hoepman,et al.  Privacy and Identity Management for Emerging Services and Technologies , 2013, IFIP Advances in Information and Communication Technology.

[3]  Daniel M. Berry,et al.  The impact of domain knowledge on the effectiveness of requirements idea generation during requirements elicitation , 2012, 2012 20th IEEE International Requirements Engineering Conference (RE).

[4]  Michael Jackson,et al.  Four dark corners of requirements engineering , 1997, TSEM.

[5]  John Mylopoulos,et al.  Non-Functional Requirements in Software Engineering , 2000, International Series in Software Engineering.

[6]  G. Deconinck,et al.  An evaluation of two-way communication means for advanced metering in Flanders (Belgium) , 2008, 2008 IEEE Instrumentation and Measurement Technology Conference.

[7]  Rubén Prieto-Díaz,et al.  DARE: Domain analysis and reuse environment , 1998, Ann. Softw. Eng..

[8]  Aybüke Aurum,et al.  Capturing implicit software engineering knowledge , 2001, Proceedings 2001 Australian Software Engineering Conference.

[9]  Kyo Chul Kang,et al.  Feature-Oriented Domain Analysis (FODA) Feasibility Study , 1990 .

[10]  Bran Selic,et al.  Modeling and Analysis of Real-Time and Embedded Systems with UML and MARTE: Developing Cyber-Physical Systems , 2013 .

[11]  Ian F. Alexander,et al.  Understanding project sociology by modeling stakeholders , 2004, IEEE Software.

[12]  Felix Bachmann,et al.  Quality Attribute Design Primitives , 2000 .

[13]  Rubén Prieto-Díaz,et al.  Domain analysis: an introduction , 1990, SOEN.

[14]  Maritta Heisel,et al.  A UML Profile for Requirements Analysis of Dependable Software , 2010, SAFECOMP.

[15]  David Clark,et al.  Safety and Security Analysis of Object-Oriented Models , 2002, SAFECOMP.

[16]  Galal H. Galal-Edeen,et al.  Stakeholder identification in the requirements engineering process , 1999, Proceedings. Tenth International Workshop on Database and Expert Systems Applications. DEXA 99.

[17]  Nancy G. Leveson,et al.  Integrated safety analysis of requirements specifications , 1997, Proceedings of ISRE '97: 3rd IEEE International Symposium on Requirements Engineering.

[18]  Stephan Faßbender,et al.  Optimizing Functional and Quality Requirements According to Stakeholders' Goals , 2014, Relating System Quality and Software Architecture.

[19]  Lawrence D. Pohlmann Strategics Consulting.  Customer-Centered Products – Creating Successful Products through Smart Requirements Management , 2015 .

[20]  Mary Shaw,et al.  Software architecture: the next step for object technology (panel) , 1993, OOPSLA '93.

[21]  Maritta Heisel,et al.  Towards Systematic Integration of Quality Requirements into Software Architecture , 2011, ECSA.

[22]  Kristian Beckers,et al.  A Problem-Based Approach for Computer-Aided Privacy Threat Identification , 2012, APF.

[23]  Paul Clements,et al.  Software architecture in practice , 1999, SEI series in software engineering.

[24]  Pierre N. Robillard,et al.  The role of knowledge in software development , 1999, CACM.

[25]  Rene Meis,et al.  Problem-Based Consideration of Privacy-Relevant Domain Knowledge , 2013, Privacy and Identity Management.

[26]  G. Probst.  Practical Knowledge Management : A Model That Works , 1998 .

[27]  Michael A. Jackson,et al.  Problem Frames - Analysing and Structuring Software Development Problems , 2000 .

[28]  Axel van Lamsweerde,et al.  Requirements Engineering: From System Goals to UML Models to Software Specifications , 2009 .

[29]  Eric Yu,et al.  Conceptual Modeling: Foundations and Applications , 2009 .

[30]  Seok-Won Lee,et al.  Feature-Oriented Nonfunctional Requirement Analysis for Software Product Line , 2009, Journal of Computer Science and Technology.

[31]  Maritta Heisel,et al.  A comparison of security requirements engineering methods , 2010, Requirements Engineering.