Abstract

While capturing software requirements of business process, multinational firms are confronted with the fact that their business operations are scattered over a number of national markets. This paper suggests the approach of central-local-central loop to tackle the contextual complexity. First, Business process information is elicited, analysed and elaborated at the central headquarters. Second, requirements engineers must validate the centrally documented requirements at the local national markets where the application will ultimately be deployed. Empirical experience shows that observation, apprenticing and online-interview are effective field elicitation methodologies if they are applied in a combined and balanced manner. Third, the adapted, changed and added information shall be satisfactorily verified centrally and agreed upon by local and central product champions and decision makers.

Highlights

  • While capturing software requirements of business process, multinational firms are confronted with the fact that their business operations are scattered over a number of national markets

  • Empirical experience shows that observation, apprenticing and online-interview are effective field elicitation methodologies if they are applied in a combined and balanced manner

  • Observation and apprenticing should form the basis for generating effective questions for online-interviews

Read more

Summary

Background

Software for industrial applications is by nature mainly made in two ways. The last two decades have witnessed breathtaking growth of technology houses specialised in software production. Software vendors, such as SAP, have induced the emergence and development of industrial applications based upon core systems that can be individualised by parameterisation and customisation. Business processes are descriptions of how a firm’s value chain is built and how its operations are conducted and accomplished by different classes of users and end-consumers. These descriptions naturally shed light on system features, behaviour and interactions with users. The more seamlessly the system is integrated into the business processes defined by the operational and product managers, the more forcefully the application software is supporting the overarching business strategy of the firm

General Patterns
A Conceptual Framework
Conclusion

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call

Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.