SaaS Requirements Engineering for Agile Development
- IGI Global
- Publication Type:
- Agile and Lean Service-Oriented Development: Foundations, Theory, and Practice, 2013, 1, pp. 64 - 93
- Issue Date:
Copyright Clearance Process
- Recently Added
- In Progress
- Closed Access
This item is closed access and not available.
The emergence of Software as a Service (SaaS) has made it possible to develop dynamic and complex business processes as eServices. The development of business processes as eServices (SaaS) can be assisted by the means of adaptive or agile development processes. The development of business processes in terms of SaaS require to perform SaaS requirements engineering (RE), which is an important phase of a software development process for the success of any project. The challenge here is how best to do SaaS RE (e.g. mapping business process to eServices) and select agile development practices for developing business processes in terms of SaaS. In order to address this challenge, an integrated agile RE model for SaaS project development environments is outlined within this chapter. The purpose of the proposed RE model is to aid in iteratively determining SaaS requirements in short iterations as opposed to the only first and onetime upfront phase of a development process. Each identified SaaS requirement or a set of requirements for a given iteration is linked to a single or set of specific agile practices for implementation in short iterations. This model can be used as a guideline by organisations wishing to understand the challenging task of mapping business processes to SaaS and its implementation by using agile software development processes or practices.
Please use this identifier to cite or link to this item: