ComD2: Family of Techniques for Inspecting Defects in Models that Affect Team Communication

Communication failures in software development teams can compromise the software quality. Therefore, identifying and mitigating risks for effective team communication are important activities in software development. Software models are one of the means of communication in development teams, because it communicates other members of the development team about the software. Thus, our research focuses on inspection techniques for identifying defects that affect the team communication through the software models. This paper presents a family of techniques for inspecting defects that affect team communication, called ComD2 (Communication between Designers and Developers). The ComD2 family was developed based on theories that investigate different ways of communication. For the time being, the ComD2 family has three specific inspection techniques for UML models, such as class diagrams, activity diagrams, and state machine diagrams. We performed a feasibility study and the results showed that the ComD2 family was considered useful for the identification of defects that affect the team communication through the software

[1]  Silvia Mara Abrahão,et al.  Further analysis on the validation of a usability inspection method for model-driven web development , 2012, Proceedings of the 2012 ACM-IEEE International Symposium on Empirical Software Engineering and Measurement.

[2]  Filippo Ricca,et al.  What are the used activity diagram constructs? a survey , 2014, 2014 2nd International Conference on Model-Driven Engineering and Software Development (MODELSWARD).

[3]  Mamoona Humayun,et al.  A Comparative Study of Software Inspection Techniques for Quality Perspective , 2016 .

[4]  Paul Ralph,et al.  Social theory for software engineering research , 2016, EASE.

[5]  Pekka Abrahamsson,et al.  The impact of agile practices on communication in software development , 2008, Empirical Software Engineering.

[6]  Cláudia Maria Lima Werner,et al.  Verification of Software Product Line Artefacts: A Checklist to Support Feature Model Inspections , 2014, J. Univers. Comput. Sci..

[7]  Juan Carlos Augusto,et al.  Handbook of Ambient Intelligence and Smart Environments , 2009, HAIS 2010.

[8]  Linda V. Knight,et al.  Effect of a virtual project team environment on communication-related project risk , 2010 .

[9]  Clarisse Sieckenius deSouza The Semiotic Engineering of Human-Computer Interaction (Acting with Technology) , 2005 .

[10]  Simone Diniz Junqueira Barbosa,et al.  Extreme designing: binding sketching to an interaction model in a streamlined HCI design approach , 2006, IHC '06.

[11]  Priyanka More,et al.  Generating UML Diagrams from Natural Language Specifications , 2012 .

[12]  Nicu Sebe,et al.  Human-Centered Computing , 2010, Encyclopedia of Software Engineering.

[13]  Verena Käfer Summarizing software engineering communication artifacts from different sources , 2017, ESEC/SIGSOFT FSE.

[14]  Siobhan Chapman Logic and Conversation , 2005 .

[15]  Tanja E. J. Vos,et al.  What do we know about the defect types detected in conceptual models? , 2015, 2015 IEEE 9th International Conference on Research Challenges in Information Science (RCIS).

[16]  Sabrina Marczak,et al.  A controlled experiment with Usability Inspection Techniques applied to Use Case Specifications: comparing the MIT 1 and the UCE techniques , 2015, 2015 ACM/IEEE 18th International Conference on Model Driven Engineering Languages and Systems (MODELS).

[17]  Forrest Shull,et al.  Detecting defects in object-oriented designs: using reading techniques to increase software quality , 1999, OOPSLA '99.

[18]  Daniela Cruzes,et al.  Communication Challenges and Strategies in Distributed DevOps , 2016, 2016 IEEE 11th International Conference on Global Software Engineering (ICGSE).

[19]  Robert Biddle,et al.  Collaborative Events and Shared Artefacts: Agile Interaction Designers and Developers Working Toward Common Aims , 2011, 2011 AGILE Conference.

[20]  Christian Bird,et al.  Convergent contemporary software peer review practices , 2013, ESEC/FSE 2013.