Abstract

A business analyst typically encounters activities and features that they have previously worked on as they move from project to project. Interestingly, despite the fact that these tasks are identical, analysts typically begin to work on them from scratch. Recreating the wheel leads to fundamental problems like neglecting the flaws in requirement analysis. Therefore, the analyst must begin implementing the strategy of requirement reuse through requirements patterns to ensure higher quality requirements with far less ambiguous parts and in a brief time. The focus of building a requirement pattern for transformation requirements of software-intensive systems ensures that critical information is not overlooked. It also enhances the effectiveness of business analysts. Although there is a plethora of research on requirements patterns in the studies, the studies did not focus on the requirement patterns for software-intensive systems. This research paper focuses mainly on the interactions of data-intensive systems namely transition requirements and a Transformation Requirement Pattern (TFReqPat) template is generated to capture the transitions requirements. It also analyses the anatomy of TFReqPat which is a guideline for capturing the data-intensive applications transition requirements. As a case study, a requirement pattern catalog with a systematic example of requirements for a banking application is presented. Furthermore, an empirical investigation was conducted to study participant’s perceptions of requirement patterns in general and in particular in order to evaluate the proposed TFReqPat. The statistical analysis reveals that the TFReqPat is more appropriate, efficient, and successful for software-intensive systems than the conventional reuse strategy.