Introducing a Game Approach Towards IS Requirements Specification

Collaborative, Participatory, and Empowerment Evaluation

Historically, Participatory Design (PD) was introduced and applied in the Scandinavian and American context as a practical design method for collective creativity and stakeholder involvement. In this paper, by fusing game elements into PD, we suggest a first step towards a culturally independent PD method called the ICT Service Design Game to ease the prevailing concern that PD has limited applicability in other cultural settings. We conduct four experiments on ICT Service Design Game in Scandinavia and Asia to evaluate its feasibility. The experiments identify some differences in the PD process and the created Persona characteristics, probably due to cultural differences. Of more interestingly, despite these process differences, the game elements of our PD variant were found to promote the key values of PD in culturally diverse settings by stimulating idea creation and participation. Our experiments imply that the introduction of game elements allows PD to be effectively utilized in culturally diverse settings.

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.

Towards a Graphical Tool for Refining User to System Requirements

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.

Information systems security issues have usually been considered only after the system has been developed completely, and rarely during its design, coding, testing or deployment. However, the advisability of considering security from the very beginning of the system development has recently begun to be appreciated, and in particular in the system requirements specification phase. We present a practical method to elicit and specify the system and software requirements, including a repository containing reusable requirements, a spiral process model, and a set of requirements documents templates. In this paper, this method is focused on the security of information systems and, thus, the reusable requirements repository contains all the requirements taken from MAGERIT, the Spanish public administration risk analysis and management method, which conforms to ISO 15408, Common Criteria Framework. Any information system including these security requirements must therefore pass a risk analysis and management study performed with MAGERIT. The requirements specification templates are hierarchically structured and are based on IEEE standards. Finally, we show a case study in a system of our regional administration aimed at managing state subsidies.

Recently, business transformation towards the used of Information and Communication Technology (ICT) is a necessity toward rapid industries and the paradigm shifted to sustain business competitiveness. The holistic electronic approach is one of business innovations, especially in handling a lot of tender documentations and process in an electronic environment namely as e-Tendering. Unfortunately, the existing tender process transformation in the electronic approach is not properly followed certain standard and guideline, especially in establishing a good e-Tendering functional requirements specification to ensure the organizations would be in the best served. This is important to ensure a good e-Tendering system can be developed by e-Tendering developers based on a good e-Tendering functional requirement specifications. The requirements specification is a process of documenting user and system requirements. Commonly, user and system requirements should be clear, unambiguous, easy to understand, complete, and consistent. In practice, this is difficult to achieve due to interpretation of the requirements in different ways by stakeholders, which are often inherent conflicts and inconsistencies of the requirements. The implementation of the existing e-tendering still remains uncertainties, especially in defining the functional requirements of the e-tendering system. Therefore, this study aims to construct the e-Tendering functional requirement model using requirement template in natural language representation approach. Moreover the development of this system requirement model may provide a consistency to the requirements representation. The study uses UN/CEFACT Business Standard of the e-Tendering Business. The identified functional requirements are designed by using Requirement Template to ensure the reliability and understandability of requirements. Besides, the proposed functional requirements is constructed by adapting the natural language and verified by expert review approaches. As a result, this study proposed a functional requirements specification of the e-Tendering that contains detailed description which can be referred by software practitioners in developing a secure e-tendering system effectively.

The purpose of this work is to develop an approach for assisting the temporal requirements' specification phase, within critical systems. We use a new typology taking into account all the common temporal properties one may meet when dealing with requirements specification. On the other hand, we develop a literal-words-based formal grammar able to express all the types of the identified requirements. The goal being to provide specification means which are at the same time simple, intuitive and rigorous. Then, in order to check requirements consistency, a graph-based algorithm has been elaborated. To our best knowledge, this is the first study which formalizes the consistency checking problem as a graph exploration. The whole of the developed mechanisms have been implemented in a prototype tool with an intuitive graphical interface that offers interesting facilities in terms of requirements' specification and consistency-checking.

It is not feasible to engineer requirements for adaptable and open service-oriented systems (AOSS) by specifying stakeholders’ expectations in detail during system development. Openness and adaptability allow new services to appear at runtime so that ways in, and degrees to which the initial functional and nonfunctional requirements will be satisfied may vary at runtime. To remain relevant after deployment, the initial requirements specification ought to be continually updated to reflect such variation. Depending on the frequency of updates, this paper separates the requirements engineering (RE) of AOSS onto the RE for: individual services (Service RE), service coordination mechanisms (Coordination RE), and quality parameters and constraints guiding service composition (Client RE). To assist existing RE methodologies in dealing with Client RE, the Dynamic Requirements Adaptation Method (DRAM) is proposed. DRAM updates a requirements specification at runtime to reflect change due to adaptability and openness.

Composite systems are generally comprised of heterogeneous components whose specifications are developed by many development participants. The requirements of such systems are invariably elicited from multiple perspectives that overlap, complement, and contradict each other. Furthermore, these requirements are generally developed and specified using multiple methods and notations, respectively. It is therefore necessary to express and check the relationships between the resultant specification fragments. We deploy multiple ViewPoints that hold partial requirements specifications, described and developed using different representation schemes and development strategies. We discuss the notion of inter-ViewPoint communication in the context of this ViewPoints framework, and propose a general model for ViewPoint interaction and integration. We elaborate on some of the requirements for expressing and enacting inter-ViewPoint relationships-the vehicles for consistency checking and inconsistency management. Finally, though we use simple fragments of the requirements specification method CORE to illustrate various components of our work, we also outline a number of larger case studies that we have used to validate our framework. Our computer-based ViewPoints support environment, The Viewer, is also briefly described.< <ETX xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink">&gt;</ETX>

Task modeling is undoubtedly a key step for task analysis during the development of iterative systems since it helps not only in the understanding of what users want but also in how to design for them. As a consequence, it should be considered as indispensable while specifying the requirements of an interactive system. With this in mind, we analyzed the requirement specifications of a typical interactive system which is a compulsory element of the final grade for a human–computer interaction course in two Master’s degree programs at the University of Valenciennes. To that end, we decided to use an approach based on project-based learning. Sixty-three requirement specifications performed since 2010 were investigated to find out how the task modeling was represented. Moreover, suggestions concerning pedagogical improvement made by the students in an open question on the evaluation form were analyzed using the ground theory method. The results showed that since students are not required to perform task modeling by the requirement specification, they do not do so even in the case of complex interactive systems. Criticism, positive and improvement issues raised by the students were also identified. In this paper, we present a detailed analysis of this study that opens up questions about HCI education and effective learning of task modeling, and, as a consequence, its potential use in industry.

Connected vehicles provide advanced transformations and attractive business opportunities in the automotive industry. Presently, IEEE 802.11p and evolving 5G are the mainstream radio access technologies in the vehicular industry, but neither of them can meet all requirements of vehicle communication. In order to provide low-latency and high-reliability communication, an SDN-enabled network architecture assisted by MEC, which integrates different types of access technologies, is proposed. MEC technology with its on-premises feature can decrease data transmission time and enhance quality of user experience in latency-sensitive applications. Therefore, MEC plays as important a role in the proposed architecture as SDN technology. The proposed architecture was validated by a practical use case, and the obtained results have shown that it meets application- specific requirements and maintains good scalability and responsiveness.

: The distributed nature of command and control requires the consideration of both processes and communications in the formulation of requirements. Cube Tool is a methodology used to derive the processing and communication needs for each system function. An approach is introduced for extending the applicability of Cube Tool to the determination of requirements for C3I systems. First, using Cube Tool for each function, a Petri Net is derived that models all processes and communications for the correct execution of the function. Then, for a given scenario, these nets are interconnected and the steps of the methodology are applied again to derive the Petri Net that represents the mission-dependent requirements for the system. For different modes of operation are considered, different Petri Net are obtained which can then be folded together to obtain a Colored Petri Net representation of the processes and communications needs.

A panel has been formed to study situational approaches to organizing and managing knowledge-based system (KBS) development efforts. It is noted that the most effective approach to organizing KBS developmental efforts is to start with specific company situation requirements and then develop an organizing approach suited to the specific organization, system, people and available resource requirements, and limitations under study. >

Hybrid systems air he/erogenous dynamical systems cliaracterized by interacting continuous and discrete dynamics. Such mathematical mode's have proved fruitful in a great d:ersiry of engineering applications. Including air-traffic control, automated manufacturing, and cliemical process control. The high-profile and safely-critical nature of the application areas /'.as fostered a large and growing body of work on formal methods for hybrid systems: mathematical logics, computational models and methods, and computer-aided reasoning tools supporting the formal specification and verification of performance requirements for hybrid systems, and the design and synthesis of control programs for hybrid systems that are provably correct with respect to formal specifications. This paper offers a synthetic overview of, am! original contributions to, the use of logics and formal methods in the analysis of hybrid systems. Keywords-Automata, computer-aided analysis, computer-aided software engineering, design automation, formal languages, hybrid control systems, logic, software verification, temporal logic.