In Software Abstractions Daniel Jackson introduces an approach to software design that draws on traditional formal methods but exploits automated tools to find flaws as early as possible. This approach--which Jackson calls "lightweight formal methods" or "agile modeling"--takes from formal specification the idea of a precise and expressive notation based on a tiny core of simple and robust concepts but replaces conventional analysis based on theorem proving with a fully automated analysis that gives designers immediate feedback. Jackson has developed Alloy, a language that captures the essence of software abstractions simply and succinctly, using a minimal toolkit of mathematical notions. This revised edition updates the text, examples, and appendixes to be fully compatible with the latest version of Alloy (Alloy 4). The designer can use automated analysis not only to correct errors but also to make models that are more precise and elegant. This approach, Jackson says, can rescue designers from "the tarpit of implementation technologies" and return them to thinking deeply about underlying concepts. Software Abstractions introduces the key elements: a logic, which provides the building blocks of the language; a language, which adds a small amount of syntax to the logic for structuring descriptions; and an analysis, a form of constraint solving that offers both simulation (generating sample states and executions) and checking (finding counterexamples to claimed properties).

/pdf/software-abstractions-logic-language-and-analysis-3g5voq3xt7.pdf

Software Abstractions: Logic, Language, and Analysis

The expected contribution of Industry 4.0 technologies for industrial performance

JML is a behavioral interface speci cation language tailored to Java It also allows assertions to be intermixed with Java code, as an aid to veri cation and debugging JML is designed to be used by working software engineers, and requires only modest mathematical training To achieve this goal, JML uses Ei el-style assertion syntax combined with the model-based approach to speci cations typi ed by VDM and Larch However, JML supports quanti ers, speci cation-only variables, frame conditions, and other enhancements that make it more expressive for speci cation than Ei el This paper discusses the goals of JML, the overall approach, and describes the language through examples It is intended for readers who have some familiarity with both Java and behavioral speci cation using preand postconditions

https://lib.dr.iastate.edu/cgi/viewcontent.cgi?article=1123&context=cs_techreports

Preliminary Design of JML: A Behavioral Interface Specification

Manufacturers are faced with many challenges, such as globalization, disparate enterprise systems and a lack of platform maturity. These will only multiply as technology advances, offshore manufacturing increases and new ways of working emerge. To overcome these challenges, many manufacturers have embraced product lifecycle management (PLM) or have expanded the use of PLM processes and tools to manage product data effi ciently, with increased visibility and control over the life cycle of the product.

/pdf/product-lifecycle-management-4mlr7de931.pdf

Product lifecycle management

The application of modular products is seen as an important enabler for delivering customized products competitively. However, many companies struggle to find ways to implement modular products in ...

/pdf/a-framework-for-determining-product-modularity-levels-1m7ponxm8z.pdf

A framework for determining product modularity levels

PLM system support for modular product development

Information technology - Programming languages, their environments and system software interfaces: Vienna DevelopmentMethod - Specification Language - Part 1: Base language

For products with a myriad of systems, groups of specialised engineers develop entire technical sub-systems, and great effort is needed to integrate these systems for fulfilling the product’s inten...

Interface diagram: Design tool for supporting the development of modularity in complex product systems:

The goal of this paper is to determine the role of a product architecture model to support communication and to form the basis for developing and maintaining information of product structures in a PLM system This paper contains descriptions of a modelling tool to represent a product architecture in a company to support the development of a family of products, as well as the reasons leading to the use of the specific model and its terminology The fundamental idea for using the architecture model is that an improved understanding of the whole product system, will lead to better decision making Moreover, it is discussed how the sometimes intangible elements and phenomena within an architecture model can be visually modeled in order to form the basis for a data model in a PLM system

/pdf/visual-product-architecture-modelling-for-structuring-data-5dogrw1mbe.pdf

Visual Product Architecture Modelling for Structuring Data in a PLM System

The work presented here concerns abstract specification of type checking for a specification language VDM-SL of the Vienna Development Method. Where previous work has focussed on rejection of “obviously” ill-typed specifications we do, in addition, consider acceptance of “obviously” well-typed expressions.

Hans Peter Lomholt Bruun

Papers

PLM system support for modular product development

Information technology - Programming languages, their environments and system software interfaces: Vienna DevelopmentMethod - Specification Language - Part 1: Base language

Interface diagram: Design tool for supporting the development of modularity in complex product systems:

Visual Product Architecture Modelling for Structuring Data in a PLM System

An Approach to the Static Semantics of VDM-SL