Software specification in business terminology

A specification formalism for business application software is presented. The 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, incorporating only business terminology without losing a certain level of formality. Also, to avoid redundancy of the specification, there are some implicit assumptions in the specification. The authors have analyzed the commonality of the assumptions hidden in specification documents and are trying to construct a language by formalizing the underlying system model.< >