This paper discusses characteristics of the surface mobility problem that present challenges for validation of autonomous mobility software. We provide a general description of a commonly used hardware-centric and dynamic approach to mobility software validation for flight systems. We also highlight some effects and impacts of flight schedules and deliveries on this validation approach and rela...

With conventional methods of performing verification and validation heavily reliant on testing performed late in the software production process the late detection of errors adds substantially to project costs and delays in delivery, and introduces significant risks. This paper presents a method of software development aimed at "correctness by construction", which greatly attenuates these probl...

Verification and validation (V&V) is a prominent technical area within simulation, attested to by the 12 tutorial sessions (including five advanced) included in the past ten Winter Simulation Conferences (WSCs). In recent WSCs the issue of Independent V&V (IV&V) has drawn increased attention, with sessions examining the perceived lack of use and little concern for the technique evinced within t...

Verification and validation (V&V) are two important tasks that need to be done during software development. There are many suggestions in the literature for techniques that can be used during V&V. Some of these are varied and need to be adapted to the particular software product being developed. There are no defined V&V techniques that can be applied to agent-based simulations specifically. It ...

© 1993, Edward Colbert By integrating object–oriented requirements analysis with OO design, the Object–Oriented Software Development Method (OOSD) allows a practical focus on the objects of a problem throughout. OOSD requirements analysis clearly represents problem requirements and leads smoothly to design, creating a single consistent abstract model with strong validation and verification, whi...

Model-based software development offers new opportunities and challenges for validation and verification of safetycritical software. In this report, we describe an approach for validating the artifacts generated in a model-based development process. Our approach divides the traditional testing process into two parts: one that validates the formal model implements the high-level requirements and...

Requirements engineering is the first step in the software engineering process. A major part of building requirements is the modelling of the system to be developed (or updated) together with the system environment. These models are, of course, abstractions of the real world and as such we can say that they are simulations which need to be validated to show that they actually correspond to what...

The availability of significant metrics in the early phases of the software development process allows for a better management of the later phases, and a more effective quality assessment when software quality can still be easily affected by preventive or corrective actions. In this paper, we introduce and compare four strategies for defining high-level design metrics. They are based on differe...

This paper argues that software measurement and the software development process are mutually dependent. Firstly, a high-level view of the relationship between measurement and the development process is taken. This view shows where the various activities within software measurement are positioned within the context of the high-level project stages. The topic of process modelling is introduced, ...