Search

Requirements prioritization is an important activity of the software development process. It is performed to rank information systems (IS) requirements in the order in which they will be implemented to maximize the value delivered to customers. A number of methods and techniques have been proposed to help organizations prioritize IS requirements. However, they all suffer from a number of limitations and their implementation are mostly informal. This work aims to design a novel method that automates the requirements prioritization process. The proposed method uses the Goal-oriented Requirement Language (GRL) that permits the: (i) modeling of requirements and linking them to the business objectives/goals, and (ii) evaluation of the impact of requirement choices on business objectives/goals. The method attaches contribution and preference values to GRL edges (e.g., contribution links) and GRL nodes (e.g., goals and solutions) to compute the score of IS requirements. The attached values can be based on any set of business and IT factors (e.g., value for the customer, cost of implementation, risk). This paper also presents the principles underlying the proposed IS requirements prioritization method and discusses its possible implementation in practice.

Robotic Process Automation (RPA) is an emerging approach that automates repetitive human tasks using robots. For business processes, RPA refers to configuring software-based robots to do the work previously done by actors in the organizations. RPA offers many benefits including improved business efficiency, increased productivity, data security, reduced cycle time, and improved accuracy while allowing organizations to relieve their employees from repetitive and tedious tasks. However, implementing RPA represents a challenge and organizations must learn to manage RPA adoption to achieve maximum results. This paper aims to help organizations to effectively adopt RPA for automating their business processes. More precisely, it proposes a new method to guide organizations in analyzing their business processes in order to identify the most suitable for RPA. We present the principles underlying our method and the results obtained in the context of key processes from the banking domain.