Specifying the Global Execution Context of Computer-Mediated Tasks: A Visual Notation and a Supporting Tool

This paper presents the notion of the global execution context of a task as a representational construct for analysing complexity in software evolution. Based on this notion a visual notation and a supporting tool are presented to support specification of a system’s global execution context. A system’s global execution context is conceived as an evolving network of use scenarios depicted by nodes and links designating semantic relationships between scenarios. A node represents either a base or a growth scenario. Directed links characterize the transition from one node to another by means of semantic scenario relationships. Each growth scenario is generated following a critique (or screening) of one or more base or reference scenarios. Subsequently, representative growth scenarios are compiled and consolidated in the global execution context graph. The paper describes the stages of this process, presents the tool designed to facilitate the construction of the global execution context graph and elaborates on recent practice and experience.

[1]  Peter Fingar,et al.  Component-based frameworks for e-commerce , 2000, CACM.

[2]  Demosthenes Akoumianakis,et al.  Scenario Networks: Specifying User Interfaces with Extended Use Cases , 2005, Panhellenic Conference on Informatics.

[3]  K. Cooper,et al.  Integrating visual goal models into the Rational Unified Process , 2006, J. Vis. Lang. Comput..

[4]  Bo Jiang,et al.  Traceability and Evaluation in Scenario Analysis by Use Case Maps , 2003, Scenarios: Models, Transformations and Tools.

[5]  Kenji Takahashi,et al.  Inquiry-based requirements analysis , 1994, IEEE Software.

[6]  Dave Thomas.  Agile Programming: Design to Accommodate Change , 2005, IEEE Softw..

[7]  Tom Mens,et al.  Automating Support for Software Evolution in UML , 2000, Automated Software Engineering.

[8]  Václav Rajlich,et al.  Modeling software evolution by evolving interoperation graphs , 2000, Ann. Softw. Eng..

[9]  Thomas P. Moran,et al.  Mapping the method muddle: guidance in using methods for user interface design , 1995 .

[10]  Matthias Jarke,et al.  Scenarios in System Development: Current Practice , 1998, IEEE Softw..

[11]  Mario R. Barbacci,et al.  Quality Attribute Workshops, 2nd Edition , 2002 .

[12]  JarkeMatthias,et al.  Scenarios in System Development , 1998 .

[13]  Jintae Lee,et al.  What's in Design Rationale? , 1991, Hum. Comput. Interact..

[14]  Julio Cesar Sampaio do Prado Leite,et al.  Supporting scenario evolution , 2004, Requirements Engineering.

[15]  G. Avellis.  CASE support for software evolution: a dependency approach to control the change process , 1992, [1992] Proceedings of the Fifth International Workshop on Computer-Aided Software Engineering.

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

[17]  Lawrence Chung,et al.  Adaptable architecture generation for embedded systems , 2004, J. Syst. Softw..

[18]  Michael Eonsuk Shin,et al.  Software requirements and architecture modeling for evolving non-secure applications into secure applications , 2007, Sci. Comput. Program..

[19]  Mario R. Barbacci,et al.  Quality Attribute Workshops , 2001 .

[20]  Mary Shapcott,et al.  Generating semantically enriched user profiles for Web personalization , 2007, TOIT.

[21]  Markus Schneider,et al.  The GenAlg project: developing a new integrating data model, language, and tool for managing and querying genomic information , 2004, SGMD.

[22]  Carl K. Chang,et al.  Event-Based Traceability for Managing Evolutionary Change , 2003, IEEE Trans. Software Eng..

[23]  Benjamin B. Bederson,et al.  Toolkit design for interactive structured graphics , 2004, IEEE Transactions on Software Engineering.

[24]  Richard N. Taylor,et al.  A comprehensive approach for the development of modular software architecture description languages , 2005, TSEM.

[25]  Dimitrios Kotsalis,et al.  Experience-Based Social and Collaborative Performance in an 'Electronic Village' of Local Interest: The EKONES Framework , 2007, ICEIS.

[26]  John Mylopoulos,et al.  Representing and Using Nonfunctional Requirements: A Process-Oriented Approach , 1992, IEEE Trans. Software Eng..

[27]  Ivar Jacobson,et al.  Object-oriented software engineering - a use case driven approach , 1993, TOOLS.

[28]  Meir M. Lehman,et al.  Software Evolution and Software Evolution Processes , 2002, Ann. Softw. Eng..

[29]  Jeffrey Heer,et al.  prefuse: a toolkit for interactive information visualization , 2005, CHI.

[30]  Brad A. Myers,et al.  User interface software tools , 1995, TCHI.

[31]  S Buckingham Shum,et al.  Developing the Design Space with Design Space Analysis , 1993 .

[32]  Eric S. K. Yu,et al.  Towards modelling and reasoning support for early-phase requirements engineering , 1997, Proceedings of ISRE '97: 3rd IEEE International Symposium on Requirements Engineering.

[33]  Kent L. Beck,et al.  Embracing Change with Extreme Programming , 1999, Computer.

[34]  Ladan Tahvildari,et al.  Self-adaptive software: Landscape and research challenges , 2009, TAAS.

[35]  Colette Rolland,et al.  Guiding the Construction of Textual Use Case Specifications , 1998, Data Knowl. Eng..

[36]  Demosthenes Akoumianakis,et al.  Non-functional User Interface Requirements Notation (NfRn) for Modeling the Global Execution Context of Tasks , 2006, TAMODIA.

[37]  Constantine Stephanidis,et al.  Encapsulating intelligent interactive behaviour in unified user interface artefacts , 2000, Interact. Comput..

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

[39]  Julio Cesar Sampaio do Prado Leite,et al.  Scenario inspections , 2003, Requirements Engineering.

[40]  Chris Ford,et al.  Non-Functional Requirements , 2007 .

[41]  Jan Bosch,et al.  Architecting for usability: a survey , 2004, J. Syst. Softw..

[42]  Eytan Adar,et al.  GUESS: a language and interface for graph exploration , 2006, CHI.

[43]  Håvard D. Jørgensen,et al.  Model-driven visual requirements engineering , 2005, 13th IEEE International Conference on Requirements Engineering (RE'05).

[44]  Thomas A. Alspaugh,et al.  Using scenarios to support traceability , 2005, TEFSE '05.

[45]  Constantine Stephanidis,et al.  Blending scenarios of use and informal argumentation to facilitate universal access: Experience with the Universal Access Assessment Workshop method , 2003, Behav. Inf. Technol..

[46]  Marjan Mernik,et al.  A preliminary study on various implementation approaches of domain-specific language , 2008, Inf. Softw. Technol..

[47]  Fabio Paternò,et al.  Design and development of multidevice user interfaces through multiple logical descriptions , 2004, IEEE Transactions on Software Engineering.

[48]  T. Longstaff,et al.  Quality Attributes , 1995 .