2014 IEEE 22nd International Requirements Engineering Conference (RE) 2014
DOI: 10.1109/re.2014.6912247
|View full text |Cite
|
Sign up to set email alerts
|

Protos: Foundations for engineering innovative sociotechnical systems

Abstract: Abstract-We address the challenge of requirements engineering for sociotechnical systems, wherein humans and organizations supported by technical artifacts such as software interact with one another. Traditional requirements models emphasize the goals of the stakeholders above their interactions. However, the participants in a sociotechnical system may not adopt the goals of the stakeholders involved in its specification. We motivate, Protos, a requirements engineering approach that gives prominence to the int… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
21
0

Year Published

2015
2015
2023
2023

Publication Types

Select...
4
3
2

Relationship

5
4

Authors

Journals

citations
Cited by 28 publications
(21 citation statements)
references
References 25 publications
(26 reference statements)
0
21
0
Order By: Relevance
“…We would need to develop a methodology around the protocol languages that would support (1) refining stakeholder requirements into protocols, e.g., as in [39], [40]; (2) protocol verification tools, e.g., to verify safety and liveness of information protocols [34], [41] and to verify the satisfiability and falsifiability of norms [27]; (3) middleware to ensure correct decentralized enactment [42]; and (4) interaction-oriented programming models for agents, as described above. We term this overall methodology Interaction-Oriented Software Engineering (IOSE) [43] to distinguish it from Agent-Oriented Software Engineering (AOSE).…”
Section: B Interaction-oriented Software Engineeringmentioning
confidence: 99%
“…We would need to develop a methodology around the protocol languages that would support (1) refining stakeholder requirements into protocols, e.g., as in [39], [40]; (2) protocol verification tools, e.g., to verify safety and liveness of information protocols [34], [41] and to verify the satisfiability and falsifiability of norms [27]; (3) middleware to ensure correct decentralized enactment [42]; and (4) interaction-oriented programming models for agents, as described above. We term this overall methodology Interaction-Oriented Software Engineering (IOSE) [43] to distinguish it from Agent-Oriented Software Engineering (AOSE).…”
Section: B Interaction-oriented Software Engineeringmentioning
confidence: 99%
“…The sociotechnical aspects of requirements engineering have been gaining prominence [10], [34]. NANE demonstrates a computational approach that goes beyond the conceptual work in previous approaches.…”
Section: Related Workmentioning
confidence: 99%
“…Approaches such as Colaba [10] that capture stakeholder rationales via arguments appear promising as do approaches such as Rodríguez et al's [32] that mine reusable model patterns from crowds. Protos [9] relates protocols to an abstract requirements engineering process, although it does not represent stakeholder rationales. A combination of such techniques is what is needed.…”
Section: Ongoing and Future Workmentioning
confidence: 99%