Requirements specification: learning object, process, and data methodologies
Communications of the ACM
Four dark corners of requirements engineering
ACM Transactions on Software Engineering and Methodology (TOSEM)
Writing Effective Use Cases
Aris-Business Process Modeling
Aris-Business Process Modeling
Requirements Engineering: A Good Practice Guide
Requirements Engineering: A Good Practice Guide
From conceptual modelling to requirements engineering
Annals of Software Engineering
Scenarios in System Development: Current Practice
IEEE Software
Task Descriptions as Functional Requirements
IEEE Software
Process Aware Information Systems: Bridging People and Software Through Process Technology
Process Aware Information Systems: Bridging People and Software Through Process Technology
How do practitioners use conceptual modeling in practice?
Data & Knowledge Engineering - Special issue: ER 2004
Model-Driven Architecture in Practice: A Software Production Environment Based on Conceptual Modeling
Business Process Modelling and Purpose Analysis for Requirements Analysis of Information Systems
CAiSE '08 Proceedings of the 20th international conference on Advanced Information Systems Engineering
Communication Analysis: A Requirements Engineering Method for Information Systems
CAiSE '09 Proceedings of the 21st International Conference on Advanced Information Systems Engineering
Informing the specification of a large-scale socio-technical system with models of human activity
REFSQ'07 Proceedings of the 13th international working conference on Requirements engineering: foundation for software quality
An empirical evaluation of the i* framework in a model-based software generation environment
CAiSE'06 Proceedings of the 18th international conference on Advanced Information Systems Engineering
| Hi-index | 0.01 |
[Context & motivation] The need of organizational modelling during the requirements engineering process of an information system has been widely acknowledged, and business process modelling can be considered a must. Nonetheless, the specification of functional requirements can be inadequate if business processes are not properly analysed so as to elicit these requirements. [Question/problem] There is a gap between business processes and functional requirements that must be bridged in order to specify the functional requirements of an information system. In addition, means of precisely and homogeneously elicit these requirements from business processes are necessary. [Principal ideas/results] The goals of this paper are: 1) to present an approach that provides methodological guidance to properly specify functional requirements from business processes; and 2) to report on practical experience using the approach. The approach is based on the analysis and graphical enrichment of BPMN diagrams for the elicitation and specification of functional requirements in the form of task descriptions, and it has been applied in field trials with a software development company. [Contribution] The main contributions of the paper are: 1) the extension of BPMN for proper elicitation of task descriptions; 2) the provision of detailed guidance in order to adequately use BPMN diagrams for the specification of task descriptions; and 3) the presentation of the lessons learnt by using the approach.