Causal Knowledge Modelling for Agile Development of Enterprise Application Systems

Abstract

Experience shows that Agile project management tools such as Atlassian Jira capture the state of EAS projects by relying solely on expert judgement that is not supported by any knowledge model. Therefore, the assessment of project content against strategic objectives and business domain features are not supported by any tool. This is one of the reasons why Agile project management still does not provide sufficient EAS project delivery results. In order to address this problem, the Enterprise Application Software (EAS) development using Agile project management is summarized in a conceptual model. The model highlights the knowledge used and indicates its nature (empirical or causal digitized). The modified Agile management process we have developed and described in previous works is based on causal knowledge models that supports EAS development and Agile management processes. The purpose of this article is to specify knowledge repository to ensure the Agile management solutions of an EAS project are aligned with strategic goals and business domain causality. It is worth noticing that strategic goals have been identified and specified as capabilities using some enterprise architecture framework (NAF, MODAF, ArchiMate, etc.). The novelty of the proposed method is incorporating the business domain causal knowledge modelling approach into the Agile project management process. The causal knowledge unit is considered as a Management Transaction (MT), which includes closed loop dependence of its components. The modified Agile activity hierarchy (theme, initiative, epic, user story) defines the required content of their mutual interactions. An important new results obtained are the conceptual model of causal knowledge base (KB) and specification of enhanced Agile management tool components: project management database and project state assesment knowledge base. Causal KB includes specification of causal knowledge unit (MT metamodel) and specifications of traditional and causal Agile hierarchy meta-models. These conceptual models define the causal knowledge components necessary to evaluate the state of Agile activities in the EAS development project using intelligent Agile project management tool.

Fragmented Securities Regulation, Information-Processing Costs, and Insider Trading

“…However, post-crisis regulations such as the Dodd-Frank Act and Basel III increased the regulatory burden for bank holding companies and motivated some banks to shed their holding-company structures. 2 Recently, banks and regulators have started questioning the usefulness of the holding company structure (Noreika, 2017;Rexrode, 2017). 3 From 2017 to 2019, Zions Bancorp, Bank OZK, BancorpSouth, and Northeast Bancorp dissolved 1 See Rosen (2003Rosen ( , 2005, Agarwal, Lucca, Seru, and Trebbi (2014), Rezende (2016), Charoenwong, Kwan, and Umar (2019), Costello, Granja, and Weber (2019), Granja and Leuz (2022), and Bischof, Daske, Elfers, and Hail (2022).…”