The organizational and digital transformation projects are very complex because of many reasons, and they depend on the initial project's phase, which depends on the critical building blocks (BB)-based unbundling process (UP). The organizational UP (OUP), which is a set of UPs whose primary goal is to disassemble the organization's legacy structure, system administration, resources, applications, working models, and components into dynamic reusable BBs which can be (re)used in standardized architectural BBs. The UP faces major difficulties because of the organization's heterogenous human profiles/cultures, system parts, managers' financial ambitions, and the project's limited time/budgets. Another major problem is that transformation and innovation techniques have been monopolized for achieving only immediate tangible goals like business and financial aspects/profits and where the intangible complex technical aspects are simply ignored.
TopIntroduction
Various application domains have critical needs for transformation projects and the hyper evolution of methodologies and technologies create a major problem for organizational transformation initiatives, because of the immense evolution gaps between the two mentioned fields. Transformation projects are very complex and take a long time to terminate, on the other hand technology domains have a hyper-evolution and in a chaotic manner, which makes such projects obsolete in a short time. That is why there is a need to find a transcendent MDTCAS to ensure that project’s evolution is independent of all technological, which are mainly commercial/financial evolutions. MDTCAS based BBbOUPS is the most important factor for the success of Organizational and Digital Transformation Projects (or simply Projects), because UPs unify BBs management to support sets of Project’s requirements, development, and platform integration activities. BB based OUP is the most risky part of a Project, because it consists of many inter-related critical factors and dependencies, like for example, the need for MDTCAS to interact between various variables like, limits of refinement processes, project management, domain users, enterprise architects, implementation developers, and other Project actors. In this chapter, the author proposes that a BBbOUPS supports Project Managers (or simply Managers) in unbundling legacy environments. UP is not only disassembling (and reassembling) of requirements, application/software modelling & implementations, and platform components, but it is a structural and coherent reorganization that delivers, models diagrams/documents, and stores them in a repository of reusable BBs and Architectural BBs (ABB), which can used in CARS (Trad, 2005; Trad, & Kalpić, 2004; Trad, & Kalpić, 2017). UP is mainly a reengineering, which delivers well-engineered BBs/ABBs, which are used in all Project’s phases. In many Projects UPs are underestimated and ignored, and that causes Project’s failure. Therefore, UP’s success is mandatory for Project’s next phases. UP’s activities and its transformed/generated BBs/artefacts are independent of a specific brand, methodology, tool, or other locked-in strategy. In this chapter the author uses an adapted version of the Applied Holistic Mathematical Model (AHMM) for UP (AHMM4UP) (Trad, & Kalpić, 2020a) to support Project’s UP’s feasibility. BBbOUPS uses also the Automated Refine Processes (ARP) to extract useful BBs/artefacts. The ARP is a concrete process that iteratively refactors existing legacy components into BBs/ABBs. To support the BBbOUPS, and UP activities, this chapter proposes a structured Project’s evolution by using ARP, which tries to propose an optimal MDTCAS. This chapter keywords show UP’s complexity and the need for a holistic/polymathic approach; that is achieved by using an Enterprise Architecture (EA) based BBbOUPS that can be used in any APplication Domain (APD). ARP’s objective is to reengineer common System and/or Domain Components (SDC)... The UP done in separate steps which use a Polymathic-AHMM4UP based UP, to surpass the complexity of heterogenous approaches and ensures Project’s integrity (Trad, 2022a, 2022b). The proposed Polymathic-AHMM4UP, supports iterative ARP based UP (simply ARP/UP) of the legacy system, by using MDTCAS to integrate standard methodologies, like The Open Group’s (TOG) Architecture Framework’s (TOGAF) Architecture Development Method (ADM) (The Open Group, 2011a).