A formal technique for the logical design of organisational information systems.

SIGLEAvailable from British Library Document Supply Centre- DSC:D51992/84 / BLDSC - British Library Document Supply CentreGBUnited Kingdo

MODELING REQUIREMENTS FOR FUTURE: ISSUES AND IMPLEMENTATION CONSIDERATIONS

In this paper, we discuss some requirements for future CASE (Computer Aided Software/Systems Engineering) environments. These requirements include increased modifiability and flexibility as well as support for task and agent models. We claim that they can only be addressed by developing more powerful representation and modeling techniques. As a possible basis for a modeling technique, we propose the GOPRR (Graph-Object-Property-Relationship-Role) data model, which addresses some of these requirements. In addition, a general information architecture for a future CASE environment is outlined. It includes three kinds of models for methodology specification: meta-datamodels, activity (task) models, and agent models. These models are defined using the GOPRR model with some additional concepts for IS development process and agent participation

A method for building and evaluating formal specifications of object-oriented conceptual models of database systems

This report describes a method called MCM (Method for Conceptual Modeling) for building and evaluating formal specifications of object-oriented models of database system behavior. An important aim of MCM is to bridge the gap between formal specification and informal understanding. Building a MCM model is a process that moves from the informal to the formal, evaluating the model is a process that moves back from the formal to the informal. First, a general framework for information system development methods is given, that is used to indicate which elements are needed to build a particular information system development method. In general, the following elements are needed (see figure 0.1) l. Requirements determination methods that can be used to determine the information needs of the environment, and to find functional and nonfunctional requirements specifications. 2. Conceptual modeling methods that can be used to elaborate the statement of functional require­ ments into a formal specification of observable system behavior. 3. Implementation methods that can be used to transform the conceptual model specification into an implementation within the constraints indicated by the nonfunctional requirements. 4. Project management methods that can be used to manage the development process in the presence of limited resources and a potentially disturbing environment. MCM is a conceptual modeling method, and must therefore in any information system development project be supplemented with three other kinds of methods. MCM contains three kinds of methods (figure 0.1). 1. Observation methods to find relevant data about the required database system. 2. Induction methods that allow one to go from a finite set of data about required system behavior to a conceptual model that represents all of this behavior. 3. Evaluation methods that allow one to test the quality of a specification of a conceptual model. In this report, I concentrate on induction and evaluation methods and merely make a list of relevant observation methods. The induction methods listed in figure 0.1 are not exhaustive. MCM can be viewed as a framework within which methods and techniques for conceptual modeling can be plugged. Some of these methods and techniques are mentioned in this report but not elaborated. There are three kinds of evaluation methods, that deal with the validity of the conceptual model, the utility of the specified behavior, and the quality of the use that is made of the available modeling constructs. Prototyping and animation are briefly discussed as evaluation methods. The quality checks, however, are listed exhaustively. The result of following MCM is a conceptual model. In the philosophy of MCM, a conceptual model consists of three components (see figure 0.2): 1. The UoD model is a model of the part of reality represented by the database system. 2. The DBS model represents DBS behavior, such as the queries to be asked from the DBS, the user interface, the contents and layout of reports produced by the DBS, etc. 3. A model of the boundary between the DBS and the UoD. This is a list of all possible transactions that the DBS can engage in, plus the function that this behavior has for the user of the DBS

Evaluating practitioner cyber-security attack graph configuration preferences

Attack graphs and attack trees are a popular method of mathematically and visually rep- resenting the sequence of events that lead to a successful cyber-attack. Despite their popularity, there is no standardised attack graph or attack tree visual syntax configuration, and more than seventy self-nominated attack graph and twenty attack tree configurations have been described in the literature - each of which presents attributes such as preconditions and exploits in a different way. This research proposes a practitioner-preferred attack graph visual syntax configuration which can be used to effectively present cyber-attacks. Comprehensive data on participant ( n=212 ) preferences was obtained through a choice based conjoint design in which participants scored attack graph configuration based on their visual syntax preferences. Data was obtained from multiple participant groups which included lecturers, students and industry practitioners with cyber-security specific or general computer science backgrounds. The overall analysis recommends a winning representation with the following attributes. The flow of events is represented top-down as in a flow diagram - as opposed to a fault tree or attack tree where it is presented bottom-up, preconditions - the conditions required for a successful exploit, are represented as ellipses and exploits are represented as rectangles. These results were consistent across the multiple groups and across scenarios which differed according to their attack complexity. The research tested a number of bottom-up approaches - similar to that used in attack trees. The bottom-up designs received the lowest practitioner preference score indicating that attack trees - which also utilise the bottom-up method, are not a preferred design amongst practitioners - when presented with an alternative top-down design. Practitioner preferences are important for any method or framework to become accepted, and this is the first time that an attack modelling technique has been developed and tested for practitioner preferences

The Future of Humanoid Robots

This book provides state of the art scientific and engineering research findings and developments in the field of humanoid robotics and its applications. It is expected that humanoids will change the way we interact with machines, and will have the ability to blend perfectly into an environment already designed for humans. The book contains chapters that aim to discover the future abilities of humanoid robots by presenting a variety of integrated research in various scientific and engineering fields, such as locomotion, perception, adaptive behavior, human-robot interaction, neuroscience and machine learning. The book is designed to be accessible and practical, with an emphasis on useful information to those working in the fields of robotics, cognitive science, artificial intelligence, computational methods and other fields of science directly or indirectly related to the development and usage of future humanoid robots. The editor of the book has extensive R&D experience, patents, and publications in the area of humanoid robotics, and his experience is reflected in editing the content of the book

Industrial Robotics

This book covers a wide range of topics relating to advanced industrial robotics, sensors and automation technologies. Although being highly technical and complex in nature, the papers presented in this book represent some of the latest cutting edge technologies and advancements in industrial robotics technology. This book covers topics such as networking, properties of manipulators, forward and inverse robot arm kinematics, motion path-planning, machine vision and many other practical topics too numerous to list here. The authors and editor of this book wish to inspire people, especially young ones, to get involved with robotic and mechatronic engineering technology and to develop new and exciting practical applications, perhaps using the ideas and concepts presented herein