Software specification by behavioural canons

2005 ◽  
pp. 117-135
Author(s):  
Horst Reichel
Keyword(s):  
Software Specification

Extending Linear Temporal Logic with Clocks to Object-Z

2014 ◽  
Vol 513-517 ◽  
pp. 927-930
Author(s):  
Zhi Cheng Wen ◽  
Zhi Gang Chen
Keyword(s):  
Real Time ◽  
Temporal Logic ◽  
Formal Specification ◽  
Large Scale ◽  
Linear Temporal Logic ◽  
Specification Language ◽  
Continuous Variables ◽  
Real Time System ◽  
Software Specification ◽  
Formal Specification Language

Object-Z, an extension to formal specification language Z, is good for describing large scale Object-Oriented software specification. While Object-Z has found application in a number of areas, its utility is limited by its inability to specify continuous variables and real-time constraints. Linear temporal logic can describe real-time system, but it can not deal with time variables well and also can not describe formal specification modularly. This paper extends linear temporal logic with clocks (LTLC) and presents an approach to adding linear temporal logic with clocks to Object-Z. Extended Object-Z with LTLC, a modular formal specification language, is a minimum extension of the syntax and semantics of Object-Z. The main advantage of this extension lies in that it is convenient to describe and verify the complex real-time software specification.

Software Specification

2021 ◽  
pp. 251-270
Author(s):  
Ian J. Hayes ◽  
Steve King
Keyword(s):  
Software Specification

A Data Base Approach to Software Specification

1980 ◽  
pp. 176-204 ◽  
Author(s):  
John Miles Smith ◽  
Diane C. P. Smith
Keyword(s):  
Data Base ◽  
Software Specification ◽  
Base Approach

Behavior-Driven Development Using Specification by Example

2016 ◽  
pp. 237-282
Author(s):  
Praveen Ramachandra Menon
Keyword(s):  
Software Development ◽  
Programming Language ◽  
English Language ◽  
Effective Communication ◽  
Project Managers ◽  
Software Specification ◽  
Technical Language ◽  
Current State ◽  
Crucial Problem ◽  
The Right

This chapter highlights a crucial problem seen often in software development that is bridging the communication gap between business and technical language and that it can be addressed with “Behavior Driven Development” (BDD) methodology supplemented with “Specification By Example” approach of delivering the right software that matters. Effective communication has always been a challenge between clients, business stakeholders, project managers, developers, testers and business analysts because a “ubiquitous” language that every one can easily understand and use does not exist. Specification By Example serves as that ubiquitous language for all, helps build right software that matters through effective communication. Specifications are written in plain English language using the Gherkin syntax to describe various behaviors of software. BDD tools help write software specification using gherkin language and also create a living documentation that is automatically generated by programming language reflecting the current state of software at any given point of time.

Sign in / Sign up

Export Citation Format

Share Document