Specifying Software Behavior for Requirements and Design
It would be useful to write one description of software behavior to serve both requirements and design. Having one description could reduce effort by eliminating the work of developing two descriptions and of keeping them consistent and relevant throughout development, evolution, and sustainment. It...
Main Author: | |
---|---|
Format: | Article |
Language: | English |
Published: |
International Institute of Informatics and Cybernetics
2013-12-01
|
Series: | Journal of Systemics, Cybernetics and Informatics |
Subjects: | |
Online Access: | http://www.iiisci.org/Journal/CV$/sci/pdfs/iSA152MV.pdf
|
id |
doaj-941d33e5364b45cc9cd5a438b71493ef |
---|---|
record_format |
Article |
spelling |
doaj-941d33e5364b45cc9cd5a438b71493ef2020-11-25T00:26:02ZengInternational Institute of Informatics and CyberneticsJournal of Systemics, Cybernetics and Informatics1690-45242013-12-011188088Specifying Software Behavior for Requirements and DesignJames Kirby Jr.0 Naval Research Laboratory It would be useful to write one description of software behavior to serve both requirements and design. Having one description could reduce effort by eliminating the work of developing two descriptions and of keeping them consistent and relevant throughout development, evolution, and sustainment. It would also eliminate the inconsistency inherent in having two descriptions, a fertile source of error. A question paramount to software engineers is, Could one description of behavior for a real system serve both requirements and design? This paper answers that question by describing one such description of the software behavior of a real system.http://www.iiisci.org/Journal/CV$/sci/pdfs/iSA152MV.pdf Software MethodsComputational BehaviorReactive SystemsSoftware DesignSoftware Requirements |
collection |
DOAJ |
language |
English |
format |
Article |
sources |
DOAJ |
author |
James Kirby Jr. |
spellingShingle |
James Kirby Jr. Specifying Software Behavior for Requirements and Design Journal of Systemics, Cybernetics and Informatics Software Methods Computational Behavior Reactive Systems Software Design Software Requirements |
author_facet |
James Kirby Jr. |
author_sort |
James Kirby Jr. |
title |
Specifying Software Behavior for Requirements and Design |
title_short |
Specifying Software Behavior for Requirements and Design |
title_full |
Specifying Software Behavior for Requirements and Design |
title_fullStr |
Specifying Software Behavior for Requirements and Design |
title_full_unstemmed |
Specifying Software Behavior for Requirements and Design |
title_sort |
specifying software behavior for requirements and design |
publisher |
International Institute of Informatics and Cybernetics |
series |
Journal of Systemics, Cybernetics and Informatics |
issn |
1690-4524 |
publishDate |
2013-12-01 |
description |
It would be useful to write one description of software behavior to serve both requirements and design. Having one description could reduce effort by eliminating the work of developing two descriptions and of keeping them consistent and relevant throughout development, evolution, and sustainment. It would also eliminate the inconsistency inherent in having two descriptions, a fertile source of error. A question paramount to software engineers is, Could one description of behavior for a real system serve both requirements and design? This paper answers that question by describing one such description of the software behavior of a real system. |
topic |
Software Methods Computational Behavior Reactive Systems Software Design Software Requirements |
url |
http://www.iiisci.org/Journal/CV$/sci/pdfs/iSA152MV.pdf
|
work_keys_str_mv |
AT jameskirbyjr specifyingsoftwarebehaviorforrequirementsanddesign |
_version_ |
1725346305051459584 |