Usage scenarios

An architecture is, first, an abstraction of a system s implementation. There are many different architectural models that help you understand the system process, module, usage dependencies, and so on. These models help you analyze certain qualities of the system runtime qualities, such as performance, security, or reliability and development-time qualities, such as modifiability and portability. These qualities are important to different system stakeholders not only the end user but also the system administrator, developer, customer, maintainer, and so on. Different kinds of usage scenarios, including system modifications and deployment scenarios, can help you to evaluate architectures against such qualities. 

Scope The system or business process for this use case. In our example, we are describing usage scenarios of a software system under development—CRS. 

All XML documents consist of elements and attributes, so they look very similar. It is therefore not surprising that some sorts of errors, such as missing attributes and the wrong order of children elements, reoccur in many different usage scenarios. This regularity of errors opens a way for simpler discovery of common problems with the help of general software tools. 

Schema evolution has been an active research area for a long time and it is increasingly supported in commercial systems. The need for powerful schema evolution has been increasing. One reason is that the widespread use of XML, web services, and ontologies has led to new schema types and usage scenarios of schemas for which schema evolution must be supported. The main goals of this survey chapter are as follows ...

Without an adequate structure in the documentation of requirements, it is not possible to provide the developers with the information they need for creating a complex system. A requirements specification provides a complete description of the functionality of the system to be developed. It also includes non-functional requirements describing constraints. The documentation will typically be structured in a hierarchical way, providing sections and subsections for different levels of requirements [9]. The hierarchy can be based on a modeling approach used for the system development, e.g. usage scenarios or data flow diagrams. 

More specifically, each participant experienced and evaluated Mary Biscuit under both trial scenario(s) and usage scenario(s). At the beginning, trial scenario(s) were assigned to participants for them to experience Mary Biscuit for the first time. Subsequently, based on the experiences and understanding about the product, participants can then choose preferred usage scenarios at the usage phase. The trial scenarios include three basic simations of the obtainment of the product while the nine usage scenarios cover both daily use and special events (see Table 24.1). 

During individual evaluation, participants chose their preferred usage occasions in which they would like to use the biscuit container. Corresponding to the first stage of the case study, the usage scenarios included both daily use occasions and special events occasions. 

Meanwhile, numerous medical device companies are adding communication capabilities into their existing products. Examples are BP meters, blood glucose meters, heart-rate (HR) monitors, thermometers, and spirometers with universal serial bus (USB), Bluetooth, and/or Wi-Fi connectivity. In a typical usage scenario, the mobile phone or Wi-Fi access... 

The current usage scenario for the Jacaranda System is typical of design tools. The user input is comprehensive the user sets up the system fully defines the problem defines the nature of the solution space through units available for a problem defines the granularity of the solution space through discretisations of continuous parameters provides cost... 

Figure I. Current Usage Scenario Use Case Diagram...

How to Combine Requirements and Interaction Design Through Usage Scenarios... 

Keywords Interaction design, usage scenarios, requirements engineering, user interfaces, usability. 

Kaindl, H., Jezek, R. From Usage Scenarios to User Interface Elements in a Few Steps. In Proceedings of the Fourth International Conference on Computer-Aided Design of User Interfaces (CADUI 2002), Valenciennes, France, May, pp. 91-102. Kluwer Academic Publishers, Dordrecht, The Netherlands (2002)... 

Usage Scenarios that Illustrate Needs for Semantic Support... 

Table 2.1 Production system engineering usage scenarios (UCx) and needs for engineering...

Semantic Web researchers and practitioners, who need to define goals for inteUigent engineering applications and to assess solution options using Semantic Web technologies, can compare their appUcation scenarios to the usage scenarios introduced in Sect. 2.4 to derive needs that can be addressed well by the capabilities of Semantic Web technologies, see Chaps. 3 and 15. 

This section reports on the application of the proposed EKB framework in the industrial domain of software-intensive production automation systems. In addition, we evaluate the EKB approach using two typical usage scenarios, namely data exchange between tools and model consistency checking across tool boundaries in detail. 

In this subsection, we describe two typical EKB usage scenarios. Data Exchange Between Tools and Model Consistency Checking Across Tool Boundaries, and compare the usage of both a common repository approach and an EKB-based approach for each of the scenarios. 

Chapter 2 of this book addresses several usage scenarios covering different phases of a production system s life cycle. K-RAMP illustrates another usage scenario, which differs from the others since it requires the statistical analysis of data which are collected during the production system s lifetime. 

The usage scenario 3 addresses a flexible organization of the production system. It must be ensured that the production system can produce a maximum variety of products. The authors explain that the production systems need to provide information about their capabilities, the access paths, and the control-related features. However, throughout the discussion of K-RAMP, some assumptions are made which are caused by achievements of the production infrastmcmre of IC factories. It is assumed that those achievements will be also the target of the development of classical production systems toward Industrie 4.0. Due to these achievements, the immediate knowledge about the production system s capabilities, its access paths or even the control-related features is not so relevant during the ramp-up of a new product. 

Although, the assumptions of K-RAMP deviate from the situation as it is described in usage scenario 3, the highlighted needs for semantic support are similar on a more abstract level. Product functions, product design, and process capabilities have to be represented (Nl), heterogeneous views with respect to the product, the process and process control have to be represented (N2), or analytics of process data is essential in order to classify capabilities of process segments (N3). 

Due to the similarities with the aforementioned usage scenarios, it can be shown that the same needs for semantic support are valid for the ramp-up of new products. 

One part of the information which has to be considered during the ramp-up of a new product is semi-stmctured data (N4), like machine vendor specific formats for machine setup (equipment recipes). This information has to be combined with stmctured handling instructions in order to compile the comprehensive semp of process segments (see previous discussion of usage scenario 3). 

As a summary, K-RAMP can be seen as another usage scenario with a broad variety of needs for semantic support. All requirements (addressed in Chap. 2 and further extended in this chapter) are shown in Table 9.1. 

The seventh chapter proposes a very useful remote laboratory concept based on the usage of the unified platform. Necessary hardware and software modules are described, and different usage scenarios are evaluated. 

---