The sequence-based software specification method was developed to convert ordinary, or typical requirements and requirements statements into mathematically precise specifications, at an acceptable level of abstraction, for deterministic systems. In view of the iterative nature of modern software developing process, requirements, once defined, are not frozen; changes are integrated continuously that need to be accommodated and validated. The need for managing changes of requirements in sequence-based specifications arises both as a consequence of practicing this method and as a general topic in software requirements engineering. In this research we have explored the theoretical consequences of three major requirements changes in sequence-bas...
Abstract. The most important reason for software systems to evolve is the change in user requirement...
Formal methods have had little impact on software engineering practice, despite the fact that most s...
The derivation of a specification document that is understandable, precise and unambiguous is indisp...
Sequence-based software specification is a rigorous method for deriving a formal system model based ...
Sequence-based specification is a constructive method designed to convert ordinary functional requir...
Updating the requirements specification when software systems evolve is a manual task that is expens...
AbstractThis paper establishes an axiomatic foundation and a representation theorem for the rigorous...
The plant safety and regulatory requirements for software-based systems mandate rigorous verificatio...
This paper proposes a model of software changes for supporting the evolution of software prototypes....
A rigorous behavioral specification can greatly reduce risk by exposing ambiguities in requirements ...
This paper aims at deriving software specification descriptions from elicited user requirements and ...
Software problems – problems whose solution is software-intensive – come in many forms. Given that s...
Context: Following the evolution of the business needs, the requirements of software systems change ...
Formal specifications of software systems need to evolve in many ways during system development. Not...
For any proposed software project, when the software requirements specification has been established...
Abstract. The most important reason for software systems to evolve is the change in user requirement...
Formal methods have had little impact on software engineering practice, despite the fact that most s...
The derivation of a specification document that is understandable, precise and unambiguous is indisp...
Sequence-based software specification is a rigorous method for deriving a formal system model based ...
Sequence-based specification is a constructive method designed to convert ordinary functional requir...
Updating the requirements specification when software systems evolve is a manual task that is expens...
AbstractThis paper establishes an axiomatic foundation and a representation theorem for the rigorous...
The plant safety and regulatory requirements for software-based systems mandate rigorous verificatio...
This paper proposes a model of software changes for supporting the evolution of software prototypes....
A rigorous behavioral specification can greatly reduce risk by exposing ambiguities in requirements ...
This paper aims at deriving software specification descriptions from elicited user requirements and ...
Software problems – problems whose solution is software-intensive – come in many forms. Given that s...
Context: Following the evolution of the business needs, the requirements of software systems change ...
Formal specifications of software systems need to evolve in many ways during system development. Not...
For any proposed software project, when the software requirements specification has been established...
Abstract. The most important reason for software systems to evolve is the change in user requirement...
Formal methods have had little impact on software engineering practice, despite the fact that most s...
The derivation of a specification document that is understandable, precise and unambiguous is indisp...