Notre thèse porte sur la Modélisation d'Entreprise et plus particulièrement sur une vision Ingénierie Système de celle-ci afin de faciliter son application « à minima » en entreprise. Alors que la modélisation d’entreprise arrive à maturité scientifique et technologique, force est de constater que sa pratique est encore trop peu courante. En outre, il n’existe pas à proprement parler de tâche de modélisation, de maintenance et de gestion de modèles dans l’entreprise. La question s’est alors posée de la relation d’interopération entre les systèmes, d’un Système-Entreprise évolutif, le plus souvent composé de façon ad-hoc de sous-systèmes (COTS), qui ont pour particularité d’encapsuler leur propre Savoir-Faire et leurs Ingénieries respectives, en incluant le Système-Produit (son besoin, son projet, …) à la source de chaque recomposition « à la demande » du Système-Entreprise. Un des objectifs de nos travaux est donc de faciliter l’interopération entre les ingénieries de ces systèmes interopérants (autour du produit A Faire) et l’Ingénierie du Système-Projet d’Entreprise (Pour Faire). Nous nous sommes alors inspirés de la proposition de Kuras pour formaliser notre Système-Entreprise (en fait son Ingénierie) dans une sorte de « Système de Systèmes d’Information » (SdSI) en tenant compte de ses aspects récursifs et multi-échelles dans un contexte organisationnel évolutif. De plus, en nous appuyant sur la théorie des patterns, nous avons identifié puis dérivé le « composite-pattern» pour mieux décrire la nature « Tout et Partie » de l’Holon Système-Entreprise utilisé par Kuras pour extraire le patron de conceptualisation le plus adéquat. Parmi tous les points de vue d’un système, cette dérivation nous permet de représenter ceux du Système A Faire et ceux du Système Pour Faire avec son contenu d’Ingénierie associée guidée par le cadre de modélisation de Zachman. Nous avons outillé notre proposition de cadre d’Ingénierie Système Basée sur des Modèles (ISBM) en étendant le méta-modèle de l’outil « MEGA Modelling Suite » ainsi qu’en développant les interfaces utilisateurs nécessaires et nous l’avons appliqué à l’Ingénierie d’un Système de Traçabilité d’un Produit dans le contexte d’un scénario PLM plausible entre l’AIPL et DIMEG. / Today’s needs for more capable enterprise systems in a short timeframe are leading more organizations toward the integration of existing component-systems. In the domain of Enterprise Modelling and more generally on Systems Engineering, the key issue is related to aligning enterprise models with the composite structure of the modelled systems. While Enterprise Modelling matures both scientifically and technologically, it is clear that its practice is still uncommon in the enterprises. There is no modelling approach in enterprise, neither even capitalization of models. This paper aims at proposing a Model-Based System Engineering (MBSE) approach, by using the recursion principle, together with a “multiple scales system thinking”, for capitalizing the engineering know-how, over time, during a project lifecycle. In this context, we advocate that, within an enterprise, the heterogeneous set of Information Systems may be considered as COTS (Commercial-Off-The-Shelf), encapsulating their own expertise (engineering), and contributing all together to a single System-of-Information System (SoIS). We are then proposing a SoIS engineering methodology resulting from deriving our MBSE approach with a recursive view of the Zachman framework. This approach, based on modelling rules and enterprise modelling constructs, is contributing to ensure the consistency and the completeness of the various heterogeneous models interoperating during systems engineering projects. To validate our MBSE proposal, a modelling tool has been prototyped. It helped at applying our SoIS engineering methodology in a use case scenario related to the requirement analysis and the specification of a product traceability system.

An interpretive research approach will be used to describe and decompose UML diagrams into their respective building blocks. A top down approach will be used to determine views that are important to enterprises during the system development lifecycle. The importance of providing graphical representations to describe conceptual ideas will be stressed. A short history will be provided of the origins of UML as well as a description of the diagrams used. Since UML is a language and not a methodology a brief discussion regarding a methodology, the Rational Unified Process, will be covered. The Zachman framework will be used to present a two-dimensional (Columns and Rows) view of an enterprise together with a summary of what could be represented in the framework. The UML building blocks will be mapped within the Zachman framework together with possible reasons for the mapping. The paper will conclude by combining several views by different authors to represent artefacts within the Zachman framework and to show the strengths and weaknesses of the current UML version 1.5 and what organisations should be aware of when considering implementing UML. / Dissertation (M.IT)--University of Pretoria, 2007. / Informatics / unrestricted

Förändringar i affärsvärlden leder till att företag idag ständigt ställs inför nya utmaningar. Samverkan mellan affärsverksamheten och IT har därför blivit en viktig aspekt inom organisationer. Företag står inför problemet att hantera sina komplexa affärsprocesser, information och infrastruktur, relaterat till att IT bör ge maximala värden för affärsprocesserna. Det för att verksamheterna ska vara med i spelet bland de konkurrenskraftiga organisationerna, vilket leder till en av anledningar till att företagen kommer i kontakt med Enterprise Architecture (EA). EA kan ses som en helhetsbild av organisationen och dess information, applikationer och infrastruktur. Relaterat till EA, kan EA-ramverk vara till hjälp för att få ett strukturerat arbetssätt. För att förbättra arbetet med EA hjälper ramverket till att kartlägga verksamhetsmiljön, processer och IT. Existensen av ett stort antal olika ramverk och de olika perspektiven på om ett ramverk är ett måste eller inte för verksamheten vid EA-arbetet, kan problematisera processen för verksamheter att veta om det ska välja ett ramverk och vilka effekter det skulle ge. Vi ser därför ett behov att av undersöka ramverkets roll i ett praktiskt EA-arbete. Studien är baserad på antaganden av en empirisk studie bestående av sex stycken Enterprise arkitekter. Enterprise arkitekterna har delat sina vyer av deras arbete med EA och ramverk. Resultatet av den empiriska studien visar att ramverkets roll kan dras utifrån tre perspektiv. Hur ramverket har implementerats, kopplat till hur det används utgör grunden för vilken roll ramverket har i det praktiska arbetet. Forskningens slutsatser visar att ramverket kan ses som; ett hjälpmedel för arkitekten, en inkörsport för det övergripande EA-arbetet och slutligen som ett hjälpmedel för en personlig karriärutveckling. / Program: Systemvetarutbildningen

I samband med dagens lågkonjunktur, ökade globalisering samt en ökandekonkurrensmarknad tillkommer en ökad komplexitet av verksamheter. Det är även viktigt för dagens verksamheter att öka sina resurser och minska sina kostnader samtidigt som de skall öka sina vinster. För att motverka komplexiteten och maximera vinsten behövs nya, fler och innovativa IT-lösningar. Användning av ett arkitektuellt ramverk som Zachmans kan vara till fördel i en verksamhet, dock är det en investering som i sig kan vara kostsam ochtidskrävande, det är därmed viktigt för verksamhetens ledning och medarbetare att försöka tänka långsiktigt istället för kortsiktigt och se till hur en användning av ramverket kan vara till nytta för verksamheten. Efter en teoriinsamling och intervjuer med experter på området, gårdet att konstatera att trots vissa kritiska ställningstaganden mot ramverket Zachman, har en användning av ramverket ändå full kapacitet att påverka ekonomin i en verksamhet. Ramverket är stort och det finns mycket att hämta, det har som syfte att bringa ordning och reda i en verksamhet och skapa gemensamma synsätt och värderingar. Förbättrad ordning och struktur är faktorer som genererar i ökad effektivisering i form av minskade risker och minskade kostnader. / Program: Kandidatutbildning i informatik

隨著資訊科技的進步，企業莫不冀望藉由資訊科技來協助公司達成營運目標與成長，其中也包含利用資訊系統來協助企業減低作業複雜度、提高作業效率或是達成企業策略目標。然而，抓取出符合企業策略的資訊需求是一項困難的工作，因此本論文期望能建立起一套資訊需求分析架構，來協助我們在抓取系統需求時的一個進入思考點。 　本研究所提出的資訊需求分析架構，可協助系統規劃人員在發展資訊系統時，將企業策略與企業流程落實，以協助企業在面臨需求的多變性時，增加組織決策活動的理性，並銜接物件導向開發方法的優點，發展出具有高度彈性的資訊系統，維持並創造出新的競爭優勢。在策略分析階段，我們期望針對企業的內外部環境作分析，再擬定出符合現今環境的企業策略，因此提出了企業在採用策略管理時普遍使用的SWOT分析，來協助企業為網際網路應用而提出具有競爭力的策略；在策略定義階段，為分析企業組織而結合了價值鏈與為網際網路定義的ICDT Model兩種模式來協助我們對策略活動作定義；在需求分析階段，以Zachman Framework與4+1 View物件導向軟體架構來分析；在需求定義階段，銜接物件導向系統發展方法（OOSD）定義需求規格與實作系統；總結而言，本資訊需求分析架構是一個具有策略分析、策略定義、需求分析、需求定義的四個階段特性的基礎架構。

系統分析困難的地方是找出符合使用者要求的需求，有時候使用者的需求與企業目標之間產生不能配合的狀況，傳統的需求分析鮮少注意此，大抵都是只著重於滿足客戶眼前的需求，並未考量這需求是否符合企業策略目標。傳統的需求分析方法，如：訪談、問卷、觀察使用者、研讀企業的文件，還是需要的，但對大型系統而言，整理文件是很費時的，對目前快速變化的競爭環境，所造成的需求變動性，上述的需求分析方法必須做個改進，如此才能跟得上競爭環境快速變化而導致的需求改變。基於此，只有重覆利用前人對某一問題的解決方式，才能避免浪費資源於解決已有標準解答的問題，樣版(Pattern)的概念似乎可以幫助我們避免無謂的資源浪費。 　　本研究以Zachman Framework的計劃者的觀點做為需求分析的思考架構，亦即建構系統時所需考慮的六種角度─5W1H。至於如何充實此架構的內容，本研究提出以E-P企業模型的企業樣版做為此架構的內涵。建議依塑模企業的情況，尋找合適的企業樣版。以企業樣版塑模企業可以比較一致的方式調適企業面臨動態的環境挑戰，面對不斷的變，企業必須動態的調整企業策略，而資訊系統也需即時的更新，本研究利用前人已證實無誤且已存在的企業樣版可以幫助企業快速建立新的或是變更已有的企業模型，而順利找到符合企業策略目標的需求並建立系統進而輔助策略的遂行。本研究目的是建立協助尋找系統功能需求的分析架構，不直接以描述使用案例進行，即資訊系統與使用者之間的互動，來了解資訊系統應提供的功能。理由在於本研究強調找出符合企業策略目標的需求，必須先進行策略分析，然後找出策略活動，進而以本資訊需求架構模塑企業的目標、達成企業目標的程序。這樣的好處在於可對企業程序做深入的了解，當環境變化時而需要對企業程序做改進甚至創造新的企業程序時可以有參考的模型。這是直接進行描述使用案例所做不到的。

M.Ing. / The research is based on the complexity of project management and risk management fields and how applying each field on its own can be problematic. This poses an everyday challenge to project managers when implemented simultaneously and such a problem predominantly exists in the engineering construction field.The challenge faced by project managers is approached throughout the research study by introducing a commonly used six order matrix framework with a high success rate in analysing and dissecting complex fields into small fragments. The framework is known as the Zachman Framework for Enterprise Architecture. However this is only done once a thorough literature review of both project and risk management as well as the limitations of the Zachman Framework have been well documented.Once the Zachman Framework for Construction adaptation is complete, it is then applied to an inner city construction case study. The results of the case study are used to determine if throughout the project lifecycle it has been possible to analyse and implement all project and risk management requirements simultaneously with little or no correction of project constraints.Using a developed integrated risk management tool which graphically tracks aggregate risk( s) in cost and time together with the Zachman Framework for Construction, the case study results reveal that it is possible to increase the ability to simultaneously manage risk and normal activities by concluding that the project constraints (i.e. cost) are accurately estimated and accomplished. In conclusion the research study,discussion and recommendations are made in order to implement all cells within the Zachman Framework for Construction therefore increasing the success of any project and risk management construction field.

Information security is an essential part of all information systems; especially in large organizations and companies dealing with classified material. Every large information system has an architecture that includes many parts that together form an Enterprise Architecture. The aim of this thesis is to study how to describe several security functions in an Enterprise Architecture and also how to ensure accountability between requirements and the implementation of the security functions. The description is for stakeholders on a conceptual level rather than a technical level. The study has been carried out by comparing the theoretical framework that has been formed by a study of the literature, and the empirical framework that has been formed by a group discussion and interviews with Information Security Consultants from Combitech AB. The process of the study was to obtain a theoretical background about Enterprise Architectures and then generate prototypes that could be tested in the interviews. The tests gave suggestions regarding how to change the prototypes to find the optimal way to describe security functions on a conceptual level. The final result of this study is to use integrated views for each security function. The integrated view should include: an identifier, a brief description of the security function, the requirements and a picture or use case. For the accountability, the requirements are numbered and displayed in the picture, in this way the stakeholder can see how the requirements are fulfilled.

台灣金融業為因應全球金融自由化及國際化的趨勢，近年來，陸續成立了十四家金融控股公司，藉由原有之金融三大領域；銀行、保險與證券之資源統籌與資本集中，建立多角化的經營版圖，同時開發創新的組合式金融商品，以共同行銷之方式，提供顧客一次購足的服務並降低營運成本。 本研究基於探索共同行銷電腦化整合的動機，並以下列二點為研究目的： 1. 探討金融控股公司如何運用集團資訊資源，減少各子公司之重覆投資，達到資源共享目的。 2. 探討金融集團共同行銷之資訊應用系統整合架構。 本研究以Zachman Framework資訊架構為分析工具，進行以國內某金融集團為例之個案研究，此一個案之核心係銀行與保險公司之保單借款，並於其中加入證券公司資源以利探討金融集團應用資訊之整合，分析企業應用整合(EAI)平台進行即時之借款、還款與財富理財等服務之建置工作。 研究結果發現，資訊科技的整合在共同行銷上應用之成效主要有四個層面： 1. 整合集團客戶資料，建立客戶關係管理。 2. 發展組合式金融商品，滿足客戶需求。 3. 通路整合，銷售流程自動化。 4. 建立集團單一入口網站，有效降低資訊成本。 / In recent years, fourteen financial holding companies have been consecutively founded in Taiwan’s financial sector in response to the liberalization and globalization trends of the world finance. Stemming from three major finance realms, such as the pooling of resources and capital for banking, insurance, and securities, multi-faceted business territories have been established. By providing the customers with bundling of financial products and services towards a on-stop-shopping manner, the financial industry has begun to reducing operation costs by using cross-selling methodologies. This research explores thus the framework and IT requirement behind cross-selling services, with the following research goals: 1. to investigate the methodology needed by financial holding companies to employ corporate information resources to reduce redundant investments of subsidiary companies and to achieve the mutual resource usage goal. 2. to investigate the information resources integration framework for cross-selling financial corporations. Based on analytic method originated from Zachman Framework, this research conducted thus a case study on a domestic financial group. The core of this case study is to identify policy loan related cross-selling activities among the banking and insurance companies of the financial group. Therefore, the author has dissected and restructured the legacy financial application of information technology to establish an overview of the architect of EAI (Enterprise Applications Integration) platform with extension of real-time lending, repayment, and wealth management services, etc. A last, this research concludes the affected efficacy with respect to four aspects on information technology integration of cross-selling: 1. Organization of information resources and establishment of customer relations management. 2. Development of composite financial products to satisfy customer needs. 3. Channels integration and sales force automation system. 4. Establishment of enterprise portal with at least single-sign-on functionality to reduce cost efficiently.

Šiame magistro baigiamajame darbe yra nagrinėjama, kaip ir kokiu mastu, struktūrinant reikalavimus pagal J.A.Zachmano karkasą ir panaudojant Toronto grupės pasiūlytą nefunkcinių reikalavimų dekomponavimo metodiką (NFR), galima bent iš dalies formalizuoti reikalavimų nuleidimą iš verslo lygmens į programų sistemos lygmenį. Darbo teorinėje darbo dalyje, remiantis atliktos mokslinės literatūros analizės rezultatais, pasiūlyta kaip pritaikyti Toronto metodiką reikalavimams nuleisti iš verslo į programų sistemos lygmenį Zachmano tipo karkasuose. Darbo eksperimentinėje dalyje šie pasiūlymai patikrinti praktiškai, atliekant konkrečios sistemos reikalavimų nuleidimą iš verslo į programų sistemos lygmenį. Tyrimo rezultatai parodė, kad NFR metodika tinkama ne visų reikalavimų nuleidimui žemyn, nes joje yra per silpnos dinamikos modeliavimo priemonės. / The aim of the master thesis is to investigate possibilities to use the NFR (non-functional requirements) approach proposed by Toronto group to perform the flowdown of requirements from business to software level in the methodical requirements engineering frameworks that organize requirements in a way similar to the J.A. Zachman’s Enterprise Architecture. Using results of the library research, the theoretical part of the thesis proposes a methodology how to apply NRF approach to perform flow down of the higher level requirements to lower ones in cases when requirements are organized according to principles proposed by J.A. Zachman. The experimental part of the thesis is devoted to the validation of the proposed approach using a simplified banking system example. The main conclusion of the thesis is that the NFR approach is applicable only to some part of requirements because the modelling means provided by this approach are not sufficient to model the system dynamic.