Julio Cesar Sampaio do Prado Leite

Departamento de Informática

Pontifícia Universidade Católica do Rio de Janeiro

(PUC-Rio)

Eliciting Operationalizations for an

Awareness Catalogue: A Collaborative Process

Support from:

Presentation at the IFIP W.G. 2.9 2016 Meeting

©jcspl 2

Research Goal

Reuse Software Awareness

©jcspl 3

Context

• Non-Functional Reuse

• NFR Framework

• SIG (Softgoal Interdependence Graph)

• Herbet de Souza Cunha’s Ph. D. Thesis

©jcspl 4

Non-Functional Reuse

Leite, J.C.S.P, Yu Y.,Liu Y.,Yu E.S.K., Mylopoulos, J., Quality-Based Software Reuse, CAiSE-05, LNCS

3520, pp.535-550, 2005, Springer-Verlag.

©jcspl 5

NFR Framework

©jcspl 6

SIG (Softgoal Interdependence Graph)

http://www.yorku.ca/cysneiro/nfrs/Usability/usefulness.png - Cysneiros,L.M., Yu, E., Leite, J.C.S.P.

“Cataloguing Non-Functional Requirements as Softgoals Networks” in Proc. of. Requirements Engineering for

Adaptable Architectures @ 11th International Requirements Engineering

Conference, 2003 p.13-20

©jcspl 7

Herbet de Souza Cunha’s Ph. D. Thesis

Herbet de Souza Cunha: Desenvolvimento de Software Consciente com Base em Requisitos, Março de 2014,

Departamento de Informática PUC-Rio http://www-di.inf.puc-rio.br/~julio/tese-herbet.pdf

©jcspl 8

Herbet de SouzaCunha’s Ph. D. Thesis

Herbet de Souza Cunha: Desenvolvimento de Software Consciente com Base em Requisitos, Março de 2014,

Departamento de Informática PUC-Rio http://www-di.inf.puc-rio.br/~julio/tese-herbet.pdf

©jcspl 9

Herbet de Souza Cunha’s Ph. D. Thesis

Herbet de Souza Cunha: Desenvolvimento de Software Consciente com Base em Requisitos, Março de 2014,

Departamento de Informática PUC-Rio http://www-di.inf.puc-rio.br/~julio/tese-herbet.pdf

©jcspl 10

Goal of this Talk

Share first results of an elicitation process to

operationalize a Software Awareness Catalog

©jcspl 11

Eliciting Operationalizations

• Use Cunha’s SIG as basis

• Select “random” research papers dealing with

awareness

• For each paper

– Read the paper

– Use 3C Collaboration Strategy

• Attach “operationalizations” to the SIG

• If necessary “evolve” the SIG (basis)

• Assign researcher

• Produce a first version for each paper

• Review the version (SIG with operationalizations)

©jcspl 12

3C Collaboration Strategy

Gerosa, M.A., Raposo, A.B., Fuks, H. & Lucena, C.J.P. (2006)

“Component-Based Groupware Development Based on the 3C Collaboration Model”, Anais do XX Simpósio Brasileiro

de Engenharia de Software – SBES 2006, 16-20 de Outubro, Florianópolis-SC, ISBN 85- 7669-079-9, pp. 129-144.

"The 3C collaboration model is based on the idea that to collaborate,

members of a group communicate, coordinate and cooperate. The 3C

model derives from the seminal article by Ellis et al."

"Communication involves the exchange of messages and the negotiation

of commitments. Coordination enables people, activities and resources

to be managed so as to resolve conflicts and facilitate communication

and cooperation. Cooperation is the joint production of members of a

group within a shared space, generating and manipulating cooperation

objects in order to complete tasks [Fuks et al. 2005]. Despite their

separation for analytic purposes, communication, coordination and

cooperation should not be seen in an isolated fashion; there is a

constant interplay between them."

©jcspl

3C Collaboration Strategy

13

Cooperation

Communication

Coordination

Operationalization

(SIG)

Presencial Meeting

Paper

Sig

White Board

Pen

Senior Researcher

Senior Researcher

Researchers

©jcspl 14

3C Collaboration Strategy (Actors)

Julio Cesar Sampaio do Prado Leite, Vera Werneck, Antonio de Pádua Albuquerque Oliveira, Claudia Cappelli, Ana

Luiza A. Cerqueira, Herbet de Souza Cunha, Bruno González-Baixauli:

Understanding the Strategic Actor Diagram: an Exercise of Meta Modeling. WER 2007: 2-12

©jcspl 15

3C Collaboration Strategy (White Board)

©jcspl 16

Assign researcher

• For a given paper read by all

• Discussed by all (3C)

• Assigned researcher uses googledocs to edit the white board draft

• A first version is produced

– Introduction

– Rationale for the paper be considered

– SIG (per leave) operationalizations

– Conclusion

©jcspl 17

Review the version

• Using googledocs

• Reviewers check the version

• If there are comments, the responsible researcher changes the version.

©jcspl 18

3C Collaboration Strategy (White Board)

©jcspl 19

Alrajeh, D., Kramer, J., Russo, A., & Uchitel, S. (2015). Automated support for diagnosis and repair. Communications

of the ACM, 58(2), 65-72

©jcspl 20

Example 1

Sourour, M., Adel, B., & Tarek, A. (2009, March). Environmental awareness intrusion detection and prevention system

toward reducing false positives and false negatives. In Computational Intelligence in Cyber Security, 2009. CICS'09.

IEEE Symposium on (pp. 107-114). IEEE

©jcspl 21

Example 2

Braberman, V., D'Ippolito, N., Kramer, J., Sykes, D., & Uchitel, S. (2015). MORPH: A Reference Architecture for

Configuration and Behaviour Self-Adaptation. arXiv preprint arXiv:1504.08339.

.

©jcspl 22

Example 3

Designing an adaptive computer-aided ambulance dispatch system with Zanshin: an experience report. Silva Souza,

V. E., & Mylopoulos, J. (2013). Designing an adaptive computer‐aided ambulance dispatch system with Zanshin: an

experience report.Software: Practice and Experience.

©jcspl 23

General Observations

• Uneven collaboration during meetings

• Several discussions.

• Very few new nodes added to the SIG

• A final report is being written

• Truism: knowledge building is costly

– 11 people

– 16 meetings of 3 hours each

• 2 meetings for NFR introduction

• 2 meetings for revision

• 1 meeting for consolidation

• Most articles took just one meeting