The Use of Application Model Validation in Testing a Proposed Standard

Author(s):  
Mary J. Mitchell

Abstract From an information system development perspective, logical data modeling techniques have traditionally served in two roles. The first role is as a method of describing the information requirements of an application system. The second role is as a mechanism for integrating the requirements from a number of applications into a single logical and consistent schema so that data can be shared by multiple applications. The Standard for the Exchange of Product Model Data (STEP) project is developing an international standard1 which uses data modeling as the basis for a multi-national and multi-enterprise integration effort. STEP is designed to provide a complete, unambiguous, computer-readable definition of the characteristics of a product throughout its life cycle. STEP product definition specifications are implementation independent, though implementation interface techniques provide the communication mechanisms for applications using file exchanges2 or shared databases. Because of the diversity of applications that are within the scope of STEP, the integration generally causes extensive changes but the changes are justified if all of the information requirements are supported.

Author(s):  
Stefan Wo¨lkl ◽  
Kristina Shea

The importance of the concept development phase in product development is contradictory to the level and amount of current computer-based support for it, especially with regards to mechanical design. Paper-based methods for conceptual design offer a far greater level of maturity and familiarity than current computational methods. Engineers usually work with software designed to address only a single stage of the concept design phase, such as requirements management tools. Integration with software covering other stages, e.g. functional modeling, is generally poor. Using the requirements for concept models outlined in the VDI 2221 guideline for systematic product development as a starting point, the authors propose an integrated product model constructed using the Systems Modeling Language (SysML) that moves beyond geometry to integrate all necessary aspects for conceptual design. These include requirements, functions and function structures, working principles and their structures as well as physical effects. In order to explore the applicability of SysML for mechanical design, a case study on the design of a passenger car’s luggage compartment cover is presented. The case study shows that many different SysML diagram types are suitable for formal modeling in mechanical concept design, though they were originally defined for software and control system development. It is then proposed that the creation and use of libraries defining generic as well as more complicated templates raises efficiency in modeling. The use of diagrams and their semantics for conceptual modeling make SysML a strong candidate for integrated product modeling of mechanical as well as mechatronic systems.


2008 ◽  
Vol 22 (1) ◽  
pp. 47-62 ◽  
Author(s):  
A. Faye Borthick ◽  
Paul L. Bowen

This simulation affords an opportunity for learning to audit system development for an accounting application. The simulation responds to the growing emphasis on controlling system development for complying with the internal control assurance requirements of Section 404 of the Sarbanes-Oxley Act of 2002 (U.S. House of Representatives). Because of the lack of detailed accounting standards for vendor incentives, learners have to construct a working definition of “systematic and rational” allocation of incentives in order to develop audit objectives and procedures. In the simulation, learners (1) develop objectives for auditing the specific project of migration of legacy code for vendor incentives and the system development for a group of projects, (2) design audit procedures to achieve the audit objectives, (3) execute the audit procedures by querying the databases, and (4) communicate objectives, procedures, and results in a report. The simulation is staged with conversations among audit staff members and the company's system development manager, databases containing application test data and program library transactions, and readiness questions. Although the databases are supplied in the form of Microsoft Access® files, the simulation can be worked with any database query tool. The simulation helps learners develop their capabilities for designing audit objectives and procedures for testing system development and for querying databases.


2017 ◽  
pp. 261-289
Author(s):  
Sabine Koch ◽  
Maria Hägglund ◽  
Isabella Scandurra

The central role of eHealth to enable the successful implementation of integrated care is commonly acknowledged today. This is easier said than done. To provide correct, understandable, and timely information at the point of need and to facilitate communication and decision support for a network of actors with different prerequisites and needs are some of the big challenges of integrated care. This book chapter focuses on the specific challenges related to informatics and socio-technical issues when designing solutions for integrated eCare. Methods for requirements elicitation, evaluation, and system development using user-centred design in collaborative environments involving a variety of stakeholders are presented. Case studies in homecare of older patients, in the care of stroke patients, and regarding citizen eHealth services in general illustrate the application of these methods. Possible solutions and pitfalls are discussed based on the experiences drawn from the case studies. To address the main informatics and socio-technical challenges in integrated eCare, namely informatics-supported collaborative work and to provide coordinated continuity for the patient, top-down activities such as health informatics standardisation, and bottom-up activities resulting in the definition of concrete patient journey descriptions, interaction points, information needs (that can be transformed into standardised data sets), as well as visualisation and interaction patterns need to go hand in hand.


Author(s):  
Vincenzo Deufemia ◽  
Giuseppe Polese ◽  
Mario Vacca

The problem of changes in software development is a complex one, and it is almost impossible to avoid it. Indeed, the continuous evolution of the real world causes frequent changes in functional requirements, which entail frequent modifications to the software, yielding a gradual decay of its overall quality. To tackle this problem, two methodologies have been proposed: waterfall methodologies, and incremental/iterative methodologies. The formers try to prevent changes, whereas the second ones consider system development as a step by step process.


2013 ◽  
Vol 712-715 ◽  
pp. 1171-1174 ◽  
Author(s):  
Li Xin Wang ◽  
Yu Guo ◽  
Ming Yue Guo

A great change in mechanical industry has occurred after several successful practices using MBD (Model Based Definition) of The Boeing Company. It is an inevitable trend from two-dimensional product definition to three-dimensional product definition in mechanical industry. Several standards for MBD have emerged around the world. This paper explores the non-revolved parts modeling methods based on MBD and Pro/ENGINEER, presents several key steps about full-annotated model per MBD and then makes a conclusion. Following these methods we successfully build a typical non-revolved model which conforms to MBD standards correctly and efficiently.


2004 ◽  
Vol 4 (4) ◽  
pp. 76-107 ◽  
Author(s):  
Alastair Iles

In the 21st century, technology and material flows constitute an ever-growing set of global environmental change. In particular, electronic wastes are emerging as a major transnational problem. Industrial nations are shipping millions of obsolete computers to Asia yearly; Asian countries are emerging as generators of e-waste in their own right. This article argues that an environmental justice approach can help illuminate the impacts of technology and material flows. To do so, however, environmental justice definitions and methodologies need to account for how and why such flows occur. Using the case of computers, the article analyses some factors shaping the e-waste recycling chain, shows how e-waste risks depend on design and manufacturing chains, and evaluates inequalities in the ecological and health impacts of e-wastes across Asia. It proposes a definition of environmental justice as obviating the production of risk, using a framework that brings together the global production system, development models, and regulatory action.


Sign in / Sign up

Export Citation Format

Share Document