Mapping from Business Processes to Requirements Specification


There are three basic reasons why you might need to model a business: to re-engineer a business, to improve a business process and to automate a business process. Nevertheless, another reason may be very useful for analyst of software systems and their customers – to understand and automatically generate functional requirements to the system. The present paper describes the process of redefinition of the business process captured by the activity diagram and its mapping to the requirements specification represented by the use case model.

1 Figure or Table

Cite this paper

@inproceedings{Stolfa2004MappingFB, title={Mapping from Business Processes to Requirements Specification}, author={Svatopluk Stolfa and Ivo Vondr{\'a}k}, year={2004} }