A framework for expressing the relationships between multiple views in requirements specification

A heterogeneous or composite system is a system in which the interacting component parts deploy a variety of different technologies. In such a system one part may be implemented using software, another with special purpose hardware, and yet another electromechanical devices.From a software engineering standpoint heterogeneous composite or multiparadigm system development presents some particular challenges. Almost inevitably, in a composite system the knowledge of the requirements and the design expertise is distributed among many different participants in the development. The person who understands the mechanical sensing and actuators in a chemical plant will not know about the process control algorithms to be employed, etc. This distribution of knowledge is reinforced by a natural heterogeneity in the representation schemes used by the participants.With many participants, many representation schemes and many development strategies the consequence is that a heterogeneous, composite or multiparadigm system means heterogeneous, composite or multiparadigm development.A further problem arises from this. We cannot readily presume that the different views maintained by the different participants are consistent.A number of solutions have been proposed to deal with these problems. These solutions are discussed here.

Spaces, places and possibilities: A participatory approach for developing and using integrated models for community planning

An individual's development and education process that starts in the family environment continues in the educational institutions. The primary school education period, which is the basis for the children's future achievements, should include regulations based on the equality of opportunity and access to education. The aim of this study is to examine in a comparative manner the school starting age of students with special requirements in Turkey and European Union countries and educational model applied, supports provided to students and classroom teachers, and the variables relating to other personnel. This study is a descriptive study aiming at determining the existing circumstances. In most of the EU countries integration, inclusion and separate training model for children with special educational requirements are applied together and as a whole in the primary school age. In addition, in the countries in which the integration and inclusion implementations are applied densely, families are provided with family training, health, financial and transportation supports together with support to academic skills for school teachers, and guidance and training service for families in terms of behavioral management.

The requirements of a system describe what the user expects from the system – in other words, what the system will do for the user. When defining the requirements of a system, the system should be viewed as a black box, so that only the external characteristics of the system are considered. Both functional and nonfunctional requirements need to be considered. Requirements modeling consists of requirements analysis and requirements specification. Use case modeling is an approach for describing the functional requirements of the system, as described in this chapter. The system's data requirements in terms of the information that needs to be stored by the system are determined using static modeling, as described in Chapter 7. The inputs to the system and the outputs from the system are described initially in the use case models and then specified in more detail during static modeling. This chapter gives an overview of software requirements analysis and specification in Section 6.1. It then goes on to describe the use case approach to defining functional requirements, as well as how to extend use cases to describe nonfunctional requirements. This chapter describes the concepts of actors and use cases , and then goes on to describe use case relationships, in particular, the include and extend relationships. Section 6.2 gives an overview of use case modeling followed by an example of a simple use case. Section 6.3 then describes actors and their role in use case modeling.

Composite systems generally comprise heterogeneous components whose specifications are developed by many development participants. The requirements of such systems are invariably elicited from multiple perspectives which will overlap, complement and contradict each other. If these requirements are developed and specified using multiple methods and notations respectively, then it is necessary to express and check the relationships between the resultant specification fragments.
\n
\nIn this paper we deploy multiple “ViewPoints” that hold partial requirements specifications, described and developed using different representation schemes and development strategies. We discuss the notion of interViewPoint communication in the context of this ViewPoints framework, and propose a general model for such communication. We elaborate on some of the requirements for expressing and enacting inter-ViewPoint relationships, and use fragments of the requirements specification method CORE to illustrate our model.

Devising a system requirements specification is a challenging task. Even after several decades of system development research, specifications for large-scale, widely-used systems remain difficult. In this paper, we suggest a first step toward a requirements specification through a stakeholder involvement approach with game elements. We report preliminary findings from a practice case in which our methods are applied to the requirement specification phase of a project management system. The analysis showed that our game approach fostered innovative idea generation and captured implicit user expectations, and as a result provided a list of requirements from other perspectives than those of conventional specification analysis. The granularities of extracted system requirements need to be refined and transferred to detailed requirements for developers to use, however, our results imply that our stakeholder involvement method with game elements can be effectively utilized as a first step towards requirement specification.

Specifying the requirements of a new system to be built is one of the most important parts of the life cycle of any project, but its support in practice is still insufficient. Since pure natural language has its disadvantages, and immediate formal representation is very difficult, a mediating representation is needed. Therefore, we used hypertext technology to develop a novel method for requirements specification (with tool support). This approach provides both for a mediating representation during incremental formalization and for convenient interaction of the requirements engineer with a computer. We have applied our approach in real-world projects, and our experience suggests its usefulness.Key WordsHypertextsemiformal representationrequirements engineering

Software requirements errors are considered to account for a majority of software failures, and a number of accidents happen because of software requirements errors. The requirements specification of transportation cyber physical system is particularly critical because we must provide high safety of these transportation systems. Therefore, techniques to provide adequate requirements specification and to find errors early are of great importance. Transportation cyber physical systems contain three parts: physical parts, communication parts and computation parts. Existing methods cannot be well suited for requirement specification and modeling of transportation cyber physical systems. In this paper, we extend the AADL to model the behavior characteristic, continuous dynamic features and spatial-temporal requirements of transportation cyber physical systems. We propose a method to transform the rule of Cellular Automata to AADL model for modeling spatial-temporal requirements and we propose an approach to describe the continuous dynamic features in AADL and transform the Modelica model to AADL model. The proposed method is illustrated by Vehicular Ad-hoc Network.

Towards a Graphical Tool for Refining User to System Requirements

Solution structures of two Src homology 3 (SH3) domain-ligand complexes have been determined by nuclear magnetic resonance. Each complex consists of the SH3 domain and a nine-residue proline-rich peptide selected from a large library of ligands prepared by combinatorial synthesis. The bound ligands adopt a left-handed polyproline type II (PPII) helix, although the amino to carboxyl directionalities of their helices are opposite. The peptide orientation is determined by a salt bridge formed by the terminal arginine residues of the ligands and the conserved aspartate-99 of the SH3 domain. Residues at positions 3, 4, 6, and 7 of both peptides also intercalate into the ligand-binding site; however, the respective proline and nonproline residues show exchanged binding positions in the two complexes. These structural results led to a model for the interactions of SH3 domains with proline-rich peptides that can be used to predict critical residues in complexes of unknown structure. The model was used to identify correctly both the binding orientation and the contact and noncontact residues of a peptide derived from the nucleotide exchange factor Sos in association with the amino-terminal SH3 domain of the adaptor protein Grb2.

Many researchers have studied the adoption of business‐to‐business Electronic Marketplaces (EMs), but agreement on which factors are more important driving forces of EM adoption has not been achieved. This may be because researchers have not adopted multiple perspectives, since the importance of EM driving factors may vary when analytical perspectives change. The objective of this paper is to determine if evidence exists that this might indeed be the case. This paper explores the adoption of EMs from multiple perspectives, using case studies. Due to its parsimony, the UTAUT framework suggested by Venkatesh et al. (2003) is adopted to guide the case analysis. EM adoption factors fall into four UTAUT super‐categories: performance expectancy; effort expectancy; institutional influence; and facilitating conditions. Results from the case studies indicate that performance expectancy is the most important and ease of use is the least important consideration for participating users. The importance of the...

Calls for decolonising IR are often focused on the need to decolonise dominant epistemologies. This article explores whether a shift towards decolonising ontology is able to provide a more profound challenge. Decolonising ontology implies acknowledging that there are multiple actual “worlds”, rather than just multiple perspectives on THE (“one”) world. However, I argue that this approach is limited by the representational strategies that are used for making the encounter of multiple worlds legible for an academic audience. Drawing on ethnographic work that anthropologists have undertaken in relation to the GMO controversy as well as broader decolonial work in IR, I maintain that the writing-up of research often entails the settling and stabilising of ontological encounters that have been experienced as unsettling and disconcerting. This move towards stabilisation is grounded in hegemonic, colonial understandings of which questions should be pursued and why: questions that continue to be about determining what “is” (rather than asking what questions would lead to rightful action), that can be answered with the help of all-encompassing concepts (such as the concept of the “pluriverse”), and that provide insights for entire disciplines (such as IR). The article shows to what extent this is detrimental to projects of decolonisation.

A series of reverberating shock experiments on the precompressed hydrogen-deuterium (H-D) mixture were performed by using a two-stage light gas gun, and an elaborately designed diagnostic configuration was presented to probe the multishock states of dense fluid H-D mixtures. The particular diagnostics allowed multiple physical parameters, including the equation of state (EOS), refractive index, reflectivity, molecular polarizability, and energy gap, of H-D mixtures under double-shock compression to be simultaneously determined in a single shot. The multiple parameters obtained provide a comprehensive evaluation for existing theoretical models from multiple perspectives. It is found that, compared with the semilocal Perdew–Burke–Ernzerhof xc functional, the EOS data predicted by a nonlocal van der Waals exchange-correlation (xc) functional (vdW-DF1) are in much better agreement with the experimental results. Furthermore, the commonly used Gladstone–Dale relation is not appropriate for describing the refractive index in high-pressure-temperature regions, and the refractive index and reflectivity can be well reproduced by the Heyd–Scuseria–Ernzerhof hybrid xc functional. These observations may provide insights into future theoretical developments and a better understanding of material properties under extreme pressure-temperature conditions.

Vision-based apple quality grading with multi-view spatial network

Modeling software components from multiple perspectives provides complementary views of a software system and enables sophisticated analyses of its functionality. A software component is traditionally modeled from one or more of four functional aspects: interface, static behavior, dynamic behavior, and interaction protocol. Each of these aspects helps to ensure different levels of component compatibility and interoperability. Existing approaches to component modeling have either focused on only one of the aspects (e.g., interfaces in various IDLs) or on well-understood combinations of pairs of aspects (e.g., interfaces and their associated pre- and post-conditions in static behavior models). We advocate that, in order to accrue the true benefits of component-based software development, one needs to model all four aspects of components. In such a case, ensuring the consistency among the multiple views becomes critical. We offer an approach to modeling components using a fourview perspective (called the Quartet) and identify the points at which the consistency among the models must be maintained. We outline the range of possible intra-component, inter-model relationships, discuss their respective advantages and drawbacks, and motivate the specific choices we have made in our on-going research on ensuring the dependability of software systems from an architectural perspective.