Software Specification in Business Terminology
Summary :
A specification formalism for business application software is presented. Our approach is to investigate specification documents which are actually used in development projects of business applications in banking, insurance, and government systems. Since the specification documents are prepared mainly for users' review for the developing software, the representation of the documents is designed to be easy to understand for users, only in business terminology without losing a certain level of formality. Also, to avoid redundancy of the specification, there are some implicit assumptions in the specification. We have analyzed some commonality of these assumptions hidden in specification documents and are trying to construct a language by formalizing the underlying system model.
- Publication
- IEICE TRANSACTIONS on Information Vol.E75-D No.5 pp.648-656
- Publication Date
- 1992/09/25
- Publicized
- Online ISSN
- DOI
- Type of Manuscript
- Special Section PAPER (Special Issue on Software)
- Category
Authors
Keyword
Latest Issue
Copyrights notice of machine-translated contents
The copyright of the original papers published on this site belongs to IEICE. Unauthorized use of the original or translated papers is prohibited. See IEICE Provisions on Copyright for details.
Cite this
Copy
Jun GINBAYASHI, Keiji HASHIMOTO, "Software Specification in Business Terminology" in IEICE TRANSACTIONS on Information,
vol. E75-D, no. 5, pp. 648-656, September 1992, doi: .
Abstract: A specification formalism for business application software is presented. Our approach is to investigate specification documents which are actually used in development projects of business applications in banking, insurance, and government systems. Since the specification documents are prepared mainly for users' review for the developing software, the representation of the documents is designed to be easy to understand for users, only in business terminology without losing a certain level of formality. Also, to avoid redundancy of the specification, there are some implicit assumptions in the specification. We have analyzed some commonality of these assumptions hidden in specification documents and are trying to construct a language by formalizing the underlying system model.
URL: https://global.ieice.org/en_transactions/information/10.1587/e75-d_5_648/_p
Copy
@ARTICLE{e75-d_5_648,
author={Jun GINBAYASHI, Keiji HASHIMOTO, },
journal={IEICE TRANSACTIONS on Information},
title={Software Specification in Business Terminology},
year={1992},
volume={E75-D},
number={5},
pages={648-656},
abstract={A specification formalism for business application software is presented. Our approach is to investigate specification documents which are actually used in development projects of business applications in banking, insurance, and government systems. Since the specification documents are prepared mainly for users' review for the developing software, the representation of the documents is designed to be easy to understand for users, only in business terminology without losing a certain level of formality. Also, to avoid redundancy of the specification, there are some implicit assumptions in the specification. We have analyzed some commonality of these assumptions hidden in specification documents and are trying to construct a language by formalizing the underlying system model.},
keywords={},
doi={},
ISSN={},
month={September},}
Copy
TY - JOUR
TI - Software Specification in Business Terminology
T2 - IEICE TRANSACTIONS on Information
SP - 648
EP - 656
AU - Jun GINBAYASHI
AU - Keiji HASHIMOTO
PY - 1992
DO -
JO - IEICE TRANSACTIONS on Information
SN -
VL - E75-D
IS - 5
JA - IEICE TRANSACTIONS on Information
Y1 - September 1992
AB - A specification formalism for business application software is presented. Our approach is to investigate specification documents which are actually used in development projects of business applications in banking, insurance, and government systems. Since the specification documents are prepared mainly for users' review for the developing software, the representation of the documents is designed to be easy to understand for users, only in business terminology without losing a certain level of formality. Also, to avoid redundancy of the specification, there are some implicit assumptions in the specification. We have analyzed some commonality of these assumptions hidden in specification documents and are trying to construct a language by formalizing the underlying system model.
ER -
English
