In the software development industry, technical debt is regarded as a critical issue in term of the negative consequences such as increased software development cost, low product quality, decreased maintainability, and slowed progress to the long-term success of developing software. However, despite the vast research contributions in technical debt management for software engineering, the idea of technical debt fails to provide a holistic consideration to include both IT and business aspects. Further, implementing an enterprise architecture (EA) project might not always be a success due to uncertainty and unavailability of resources. Therefore, we relate the consequences of EA implementation failure with a new metaphor --Enterprise Architecture Debt (EA Debt). We anticipate that the accumulation of EA Debt will negatively influence EA quality, also expose the business into risk.
Ylimäki goes even further and defines twelve critical success factors for Enterprise Architecture. These factors obviously influence EA and its quality, although they are different to previously known aspects. Here high-quality EA is described with: high-quality EA conforms to the agreed and fully understood business requirements, fits for its purpose (e.g. a more efficient IT decision making), and satisfies the key stakeholder groups’ (the top management, IT management, architects, IT developers, and so forth) expectations in a cost-effective way understanding both their current needs and future requirements'' @cite_22 .
@cite_22
1599980315 2027705422 2151597242 2963353797
This article presents a model for projects that have to adhere to Enterprise Architecture (EA) in order for their results to be aligned with the broader organization. The model features project artifacts (i.e. deliverables such as Software Architecture Documents), their mutual relationships, their relationship with EA, and the processes in which they are created and tested on conformance. We start with applying Activity Theory to show the crucial mediating role that artifacts have in projects and to identify and justify the new EA-related artifacts we introduce. We subsequently incorporate these findings and existing best practices in a standard systems development approach in order to create a practical model that projects can apply for EA conformance. This model features both new, dedicated EA artifacts, and well-known existing artifacts of which we describe the way they should conform to EA. Finally, two action research studies are used to empirically support the model. : Enterprise architecture (EA) is a new approach that organizations should practice to align their business strategic objectives with information and communication technology (ICT). Enterprise Architecture encompasses a collection of different views and aspects of the enterprise which constitute a comprehensive overview when put together. Such an overview cannot be well-organized regardless of incorporating a logical structure called Enterprise Architecture Framework (EAF). EAF presents a transparent and comprehensive map of an organization that shows how all organization elements (business and IT) work together to achieve defined business objectives. Several distinctive EAF have been proposed, but many organizations are struggling with using these frameworks. This article try to eliminate the challenges of common and famous EAF by using Service Oriented (SO) paradigm. This service oriented EAF (SOEAF) named KASRA EAF. KASRA EAF involves a SO Roadmap that is compatible with ITIL and a Classification Schema comprises four rows and six columns. Enterprise Architecture models can be used to support IT business alignment. However, existing approaches do not distinguish between different IT business alignment situations. Since companies face diverse challenges in achieving a high degree of IT business alignment, a universal ‘one size fits all’ approach does not seem appropriate. This paper proposes to decompose the IT business alignment problem into tangible qualities for business, IT systems, and IT governance. An explorative study among 162 professionals is used to distinguish four IT business alignment situations, i.e. four clusters of IT business alignment problems. These situations each represent the current state according to certain qualities and also the priorities for future development. In order to increase IT business alignment, enterprise architecture meta models are proposed for each identified situation. One core meta model (to reflect common priorities) as well as situation specific extensions are presented. Due to the publicly-known deterministic character- istic of pilot tones, pilot-aware attack, by jamming, nulling and spoofing pilot tones, can significantly paralyze the uplink channel training in large-scale MISO-OFDM systems. To solve this, we in this paper develop an independence-checking coding based (ICCB) uplink training architecture for one-ring scattering scenarios allowing for uniform linear arrays (ULA) deployment. Here, we not only insert randomized pilots on subcarriers for channel impulse response (CIR) estimation, but also diversify and encode subcarrier activation patterns (SAPs) to convey those pilots simultaneously. The coded SAPs, though interfered by arbitrary unknown SAPs in wireless environment, are qualified to be reliably identified and decoded into the original pilots by checking the hidden channel independence existing in sub- carriers. Specifically, an independence-checking coding (ICC) theory is formulated to support the encoding decoding process in this architecture. The optimal ICC code is further devel- oped for guaranteeing a well-imposed estimation of CIR while maximizing the code rate. Based on this code, the identification error probability (IEP) is characterized to evaluate the reliability of this architecture. Interestingly, we discover the principle of IEP reduction by exploiting the array spatial correlation, and prove that zero- IEP, i.e., perfect reliability, can be guaranteed under continuously-distributed mean angle of arrival (AoA). Besides this, a novel closed form of IEP expression is derived in discretely-distributed case. Simulation results finally verify the effectiveness of the proposed architecture.