
Enterprise architectures (EA) embody the business objectives, processes and information technology infrastructure reflecting the desired incorporation and standardization requirements of a company’s operating model. It is vital that during the initial design stages the software system’s architecture aligns with the EA. While frameworks exist to check the alignment of enterprise and system architectures, there is an assumption of well-defined requirements derived from the EA’s business objectives. This transition is non-trivial as the EA can be a significant document representing the viewpoints of the stakeholders. This paper proposes and illustrates, using the Grounded Theory Methodology, a systematic, qualitative procedure, to extract the functional and non-functional enterprise requirements from the EA and/or system description. The contribution of this work is to further systematize the alignment and traceability of EA and system architectures and provide the initial requirements and system models necessary for supporting the of enterprise systems.
| selected citations These citations are derived from selected sources. This is an alternative to the "Influence" indicator, which also reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically). | 10 | |
| popularity This indicator reflects the "current" impact/attention (the "hype") of an article in the research community at large, based on the underlying citation network. | Average | |
| influence This indicator reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically). | Top 10% | |
| impulse This indicator reflects the initial momentum of an article directly after its publication, based on the underlying citation network. | Average |
