Characterizing Sets of Systems: Representation and Analysis of Across-Systems Properties

. System quality is assessed with respect to the value of relevant properties of that system. The level of abstraction of these properties can be very high (e.g. usability) or very low (e.g. all the “Ok” buttons in the application have the same size). These properties can be generic and thus applicable to a large group of systems (e.g. all the interactive systems should be usable) or very specific to a system (e.g. the “Quit” button in my application should always be visible). While properties identification and verification is at the core of interactive systems engineering, much less attention is paid to properties that aims at characterizing a pair (or more) of systems. In this paper, we propose to study such properties (defined as across-systems properties) and propose a notation for representing them. We propose a process for the analysis of such properties using the proposed notation. This process and analysis can be used during systems design or integration. We also present several examples of across-systems properties and demonstrate their importance and use on a simple example of aircraft cockpits buttons.


Introduction
The term property conveys multiple meanings in different domains.However, in computing systems domain [18], they are used to describe characteristics that the system should exhibit but their assessment (on a given system) is usually a complex and cumbersome activity.Formal description techniques are aimed at describing both the system and their expected properties and to demonstrate (or not) that the system really exhibits these properties.Fig. 1 presents the process advocated by DO178-C standard [22] for the design of computing systems in the aeronautics domain.That process highlights the need for explicit representation of expected properties for a given aircraft system (bottom of the Figure ) and the formal methods supplement to this standard [17] even recommend the use of CTL (Computational Tree Logic) from [21] to represent them.The right-hand side of the Figure highlights the activity of formal verification that checks whether properties hold on the behavioral description of the system produced in the LLR phase (upper part of the Figure ).Such approach follows the work done by Sistla and Pnueli [19] on the safety and liveness properties of reactive systems.Their focus, and the one of DO 330 standard, is on the representation of multiple properties for a single system under design or evaluation.
Fig. 1.Formal Approach to System Design as in DO178C-Supplement 330 on Formal Methods [17] The HCI community usually focusses on properties that characterize a single system in relation to the user and his/her environment.For instance, the well-studied usability property determines the effectiveness, the efficiency and the satisfaction according to standard ISO 9241 [7] of the system for a given user (or set of users).Other usability definitions add learnability [12] or accessibility [14] to the standard definition.Usability evaluation can be performed on one single system.In other words, the usability evaluation function needs one parameter (a system) and returns a set of value.This means that for usability evaluation would blend a value for the effectiveness of the system, a value for the efficiency of the system and one for the satisfaction of the user using the system.One important aspect of this is that the type of the values depends on the property.It can be Boolean (the property is true or false) but also enumerated type or a number (e.g.error rate).We call within-system property this kind of property for which the evaluation function needs one single system as parameter.User Experience [15], privacy [5], dependability and security [2] are other examples of within-system properties that can be evaluated on a single system.In contrast, other systems properties can be evaluated only with, at least, two systems as parameter.For instance, similarity property determines the distance between several interfaces in terms of orientation, order and density of their items (according to the definition in [6]).The evaluation function of similarity needs at least two parameters (two user interfaces) and returns a set of three values: one for the orientation, one for the order and one for the density.We call this kind of properties across-systems properties.Proximity [16] and congruence [3] are other examples of across-systems properties, as their evaluation function needs at least two parameters too.Less attention is paid to across-systems properties even though these properties can be extremely useful to characterize sets of systems as, for instance, in the prototyping phases of interactive systems development where multiple alternatives are designed and assessed.We propose to investigate and define different across-systems properties and a mean to describe explicitly these properties in interactive systems design process.
In the next section, we detail different examples of across-systems properties.In the third section, we propose QSCA notation supported by the DREAMER tool to represent across-systems properties.In the fourth section, we propose a process for the analysis of across-systems properties of systems using QSCA notation.The fifth section illustrates how this notation and process help in describing the across-systems properties of aircraft cockpit elements.Section 5 concludes the paper and highlights directions for future work.

Examples of existing across-systems properties
Across-systems properties are meant to characterize the quality of a set of systems.As mentioned in the introduction, Similarity is an across-systems property that aims at assessing the distance between the visual layouts of several systems interfaces in terms of orientation, order and density as introduced in [6], refined in [11] and more recently used for experience gathering [23].This Similarity property can be included as a contributing factor of the Proximity property.The term Proximity is used by Wickens and Carswell [16] as compatibility principle between sets of displays for interface design.We propose to use the term Proximity as defined in [16] to be an across-systems property.The Proximity across-systems property is composed of Perceptual Proximity and Processing Proximity [16].Perceptual proximity includes: ─ the spatial proximity of displayed items, ─ the visual connection between displayed items, ─ the similarity (e.g.color, orientation) between displayed items, ─ the homogeneous information display (i.e.all digital, all analogous, both), ─ the object integration (i.e.contiguity, contour and spatial integration) of displayed items.

Processing proximity includes:
─ the cognitive processing proximity of the tasks, ─ the similarity between units of the displayed parameters, ─ the temporal proximity of the task (i.e. the time to perform the task).
Another example of across-systems property is Congruence.Dekker and Hollnagel [3] define Congruence as the ability of the system to take into account the variation of user capabilities and needs depending on the current situation.Extending this proposal, we propose to consider congruence across a set of systems.In other words, Congruence property aims at characterizing the ability of a set of systems to maintain their input/output compatible with user capabilities and needs whatever the situation.
Finally, we propose a list of across-systems properties that are initially within-system properties but that can also be applied as across-systems properties: ─ Equivalency: One or several systems exhibit the same properties as another system or several systems.─ Dependency: One or several systems depend on the outputs of other systems.For instance, a set of radio receptors are dependent from a radio transmitter, as receptors need the radio waves of the transmitter.─ Complementarity: Each system belonging to a set of systems performs a share of the overall activity.The complete work is the union of each part.For instance, a set of factory robots of production line highly support complementary property, as each robot completes the work produced by the previous one.─ Diversity: Each system of the set of systems is implemented in a different language or technology.A set composed of a C++ application, a JAVA application and a Python application highly supports diversity property [24].─ Redundancy: Each system of the set of systems offers the same functions.For instance, a set composed of a computer extinguisher application and an extinguisher physical button of the computer highly support redundancy property for the shutdown function [26].─ Equality: The control authority is equally distributed between the systems of the set.
For instance, a set of systems under the so-called "master-slave" protocol have a very low equality property.─ Uniformity: Each system of the set contributes with the same amount of work to the overall activity.─ Concurrency: Each system of the set of systems work at the same time [25].
Defining properties of set of systems is useful to analyze how to integrate several systems for a particular function or to replace a system by another one inside an integrated set of systems.For example, in aircrafts, to integrate a system as a backup in case of a failure of another system, redundancy and diversity are important properties (that are related to the implementation of fault tolerance mechanisms [2,4]).Another example is the replacement of a system by a newest one in a factory.In order to minimize the learning time for the operators, the proximity property has to be assessed (to ensure that the required number of new cognitive tasks to learn is low).In the same way that within-system properties may be used to define requirements for the systems and then drive the design of these systems, across-systems properties also may be targeted during the design of an integrated set of systems.In order to provide support for the comparison of design options with respect to a set of across-systems properties, we propose to extend TEAM design rationale notation (which is based on QOC [9]).

QSCA notation: extensions to the QOC and TEAM notations
MacLean et al. [9] introduced the QOC (Question Option Criteria) notation for system design rational.QOC allows to document design choices with their explanations during the design process.This notation is also a tool for reasoning and communicating with various stakeholders as it uses very simple concepts.The TEAM (Traceability, Exploration and Analysis Method) [10] notation extends the QOC notation with the description of properties and factors associated to the criteria, as well as with the identification of design artefacts associated to the design options.
We propose to extend the TEAM notation to enable the representation of acrosssystems properties, in order to take into account across-systems properties when designing a set of systems.For that purpose, we propose to slightly adapt the TEAM notation to create QSCA notation: • Question: Design question about the system under design (Square in Fig. 2).
• System: possible option for the system to answer the design question (Disc in Fig. 2  The DREAMER (Design Rationale Environment for Argumentation and Modeling and Engineering Requirements) tool supports recording, edition and analysis of TEAM models [10].We propose to use DREAMER to describe QSCA models.

From the across-systems properties description to a process for the analysis of across-systems properties of systems
In this section, we present the process for the analysis of across-systems properties of systems.This process presented in Fig. 3 can be used for various purposes during the design process (e.g.design choices or integration of systems).

Across-systems properties
Select systems to be compared During the first step, the involved stakeholders identify the design question related to the object of the analysis.For example, a design question can be "what are the most similar systems?".They describe this design question in the QSCA model.During the step 2, they select the systems to compare.They describe these systems in the QSCA model.During the step 3, they identify the across-systems properties they want the selected systems to support.They identify the contributing factors of the selected acrosssystems properties as well.In the same way as the selection of within-system properties, the selection of across-systems properties can result from user studies, organizational or legal constraints.As for within-systems properties, it is possible that only some of the contributing factors of the across-systems property are identified relevant to support.For example, the appearance and identification contributing factors of UX withinsystem property can be identified relevant to the detriment of others during a user study.In the same way, the similarity of users tasks contributing factor of Proximity acrosssystems property can be identified relevant to the detriment of the others contributing factors.They describe the selected across-systems properties and/or across-systems property contributing factors in the QSCA model.During the step 4, they select the concrete properties to be measured on selected systems.For example, a concrete property of Similarity across-systems property is "same interface items orientation".They describe these concrete properties in the QSCA model.During the step 5, they produce the final QSCA model.They describe how (strongly denied, denied, neutral, supported, strongly supported) the combinations of systems support each concrete property in the QSCA model and how these concrete properties support their relative across-systems properties.During step 6, they identify the combinations of systems that achieve across-systems properties.As a result, at the end of the process, the list of combinations of systems that achieve the across-systems properties is identified.

Select properties for comparison
For the illustrative example of this paper, we follow this process and use the DREAMER tool [10] to analyze across-systems properties of different system designs of the FIRE push-button in an aircraft cockpit.

Representing across-systems properties: illustrative example
In the A350 aircraft cockpit, there are guarded FIRE push-buttons on the overhead panel, one for each engine of the aircraft.These buttons are composed of a backlighting system, a guard and a toggle button (see Fig. 4).When a fire is detected in an engine, the backlighting system turns on and the pilot must raise the guard and press the toggle button [1] to acknowledge the alarm.When the button is pressed, all the systems that are connected to the engine are isolated and the fire extinguisher bottles are armed for a possible discharge [1].
. Fig. 4. Engine 1 FIRE push-button on the overhead panel.
In this example, we study the digitalization of such FIRE push-button (FIRE pb).Two different designs of the digital FIRE pb are proposed.The first design option mimics all the graphical aspects and interactions of the physical FIRE pb.The difference is that the button is no more physical and user interactions must be performed with a mouse.The sequence of interaction is visible in Fig. 5. Like the physical FIRE pb, the user sees the backlighting system on, raises the guard and presses the button to isolate the engine and to prepare the bottles to discharge.We call this design option "overhead panel-like FIRE pb".

Fig. 5. Interactions sequence for pushing overhead panel-like FIRE push button
The second design option supports a different interaction sequence that still enables the guard of the button.This interaction sequence is similar to the GoPro1 unlock interaction and is called GoPro-like FIRE pb.This sequence of interactions is presented in Fig. 6 and is composed of the following steps: the user sees the backlighting system on, drags the button on the bolt area, maintains the button in this area until the animation finishes, releases and presses the button to isolate engine and prepare the bottles to discharge.For this proposed interaction design, the attention has been paid to respect the same interaction time to remove the guard and press the button as with the physical FIRE pb.

Fig. 6. Interactions sequence for pushing GoPro-like FIRE push-button
We propose to analyze these different designs with the physical FIRE pb with respect to a subset of the across-systems properties presented in section 2 in order to choose a digital design for the FIRE push-button.This goal is described by "which user control to perform an acknowledgment of fire?" design question (step 1 of the process described in Fig. 3).The systems to be compared are the physical, the overhead panellike and GoPro-like fire push-buttons (step 2 of the process).For this illustrative example, we choose to compare the push-buttons relative to their processing proximity, homogeneous information display, temporal proximity (contributing factors of Proximity across-systems property), redundancy and similarity (acrosssystems properties) (step 3 of the process).We choose "same graphical rendering", "same functions", "same time to perform tasks", "same logical processing", and the type of the output (physical and digital) as concrete properties to be measured on pushbuttons (step 4).We describe in the QSCA model (Fig. 7) how the combinations of push-buttons support or not the concrete properties (step 5).The actual FIRE pb and overhead panel-like FIRE pb have the same graphical rendering.Then, they support the Similarity across-systems property (first multi-systems property from the bottom of Fig. 7) (step 6).All the systems have the same functions: fire alert, isolate engine and prepare the fire extinguisher bottles to discharge.Then, these systems support the Redundancy across-systems property (second multi-systems property from the bottom of Fig. 7) (step 6).All the systems are designed so that it takes the same time to perform the button push.Then, they support the temporal proximity across-systems property (step 6).The physical FIRE pb is physical whereas overhead panel-like and GoPro-like FIRE pb are digital.Then, they provide low support to the homogeneous information display across-systems property (step 6).Finally, all systems require the same logical processing user task: the button can be pushed to prepare fire extinguishing when the backlighting system is on and guard raised.Then, all the systems support the processing proximity across-systems property (step 6).
Across-systems properties can inform the design option decision if a single digital option must be chosen.In order to not modify the pilot training procedure as applied with the current physical FIRE pb, the preferred option should be the overhead panel-like FIRE pb one.Indeed, all of the design options are graphically alike and user cognitive tasks are close (similarity and processing proximity).Otherwise, despite the use of different input devices and interactions techniques used for the three design options, their across-systems properties indicate that they are alike.In this case, usability evaluation can be performed to discriminate the most suitable option according to the users.

Conclusion
This position paper introduces the concept of across-systems properties and proposes a mean to represent across-systems properties using QSCA notation based on TEAM and a process.It illustrates (on an example) how one can use it.This example is based on the physical FIRE push-button found in an aircraft cockpit and on its digital design alternatives (if we consider that future cockpits would replace such physical buttons with touch screen interactions).Even though, the physical FIRE push-button and digital alternatives seem to be very different, across-systems properties highlights their common characteristics and suitability to pilot tasks.In addition, if designers want to replace the current system by a digital one or want to integrate a redundant one, the representation of across-systems properties can guide design choices depending on the properties designers want to preserve and the ones they are ready to abandon.
In the same way as the pilot does not only use the FIRE push-button to deal with an engine fire (they could do testing for instance), it is common for users to manipulate several systems to reach a goal.In other words, users can use complex systems composed of several sub-systems to perform their work.For instance, an office employee use several systems such as a computer, a telephone and a printer to perform his/her work.All these systems compose a workstation complex system.For this reason, it might be interesting to investigate possible links between within-system properties of systems and across-system properties of the entire work environment.For instance, redundancy across-system property is also a fault tolerant technique to contribute to the within-system dependability [2] of a given system.Looking at each redundant component, we might want to identify within-system properties (e.g.performance).The variants used for redundancy must exhibit similar behaviors and thus similarity is, for them, an across-system property.If similarity is guaranteed then the fault-tolerant system embedding all the redundant ones will exhibit dependability as a within-system property.
One perspective to this work lays in the analysis of how within-system properties can help designers when they have to integrate several systems.For example, if several systems of the cockpit have a high proximity, the integration of these systems to support a user goal may enhance the usability of the whole cockpit, as pointed out by Huchins in the work on distributed cognition [27].In other words, the description of the relationship between within-system properties and across-system properties can enable to understand how the first influences the second and to design systems with a more global integrated perspective.
replaces design option of the TEAM notation.•Concrete property: Desired property met (or not) by the related set of systems (Lower right triangle in Fig.2) replaces the desired property met by one or several design options of TEAM notation.• Across-systems property (Upper right triangle in Fig.2) encompassing the concrete property of several systems.If a system option highly supports an across-systems property, a plain line is drawn between this across-systems property and the line that connect a system option and the concrete property associated to this across-systems property.If a system option gives few support to an across-systems property, a dashed line is drawn between this across-systems property and the line that connect a system option and the concrete property associated to this across-systems property.Across-systems property replaces the notation element Argument of the TEAM notation.The notation element Argument stands for the reason behind the choice of one design option in the TEAM notation.

Fig. 2 .
Fig. 2. Main elements of the QSCA notation (extension to the notation TEAM) edited with the DREAMER tool

Fig. 3 .
Fig. 3. Process for analysis of across-systems properties of systems.

Fig. 7 .
Fig. 7. Representation of across-systems properties of FIRE pb, GoPro-like FIRE pb and overhead panel-like FIRE pb using extended QOC & TEAM notations to answer the design question "Which user control to perform acknowledge fire action?"