Enterprise architecture: agile transition and implementation

In our previous articles, we made the case for having an enterprise architecture and discussed the first phases of an architecture development process. The second article concentrated on describing the baseline architecture and defining the target architecture. We complete our discussion of the meth...

Ausführliche Beschreibung

Gespeichert in:
Bibliographische Detailangaben
Veröffentlicht in:IT professional 2001-11, Vol.3 (6), p.30-37
Hauptverfasser: Armour, F.J., Kaisler, S.H.
Format: Artikel
Sprache:eng
Schlagworte:
Online-Zugang:Volltext bestellen
Tags: Tag hinzufügen
Keine Tags, Fügen Sie den ersten Tag hinzu!
container_end_page 37
container_issue 6
container_start_page 30
container_title IT professional
container_volume 3
creator Armour, F.J.
Kaisler, S.H.
description In our previous articles, we made the case for having an enterprise architecture and discussed the first phases of an architecture development process. The second article concentrated on describing the baseline architecture and defining the target architecture. We complete our discussion of the methodology by focusing on transition and implementation planning. Transition planning focuses on deriving a time-phased set of actions to achieve a given goal-in this case, implementation of the target architecture. Large organizations will remediate, renovate, or replace many systems concurrently. In doing so, they must recognize interdependencies among systems and accommodate them in activity scheduling. Implementation planning has a different time frame and a different audience. It maps resources (people, places, things, and funding) to transition planning activities.
doi_str_mv 10.1109/6294.977769
format Article
fullrecord <record><control><sourceid>proquest_RIE</sourceid><recordid>TN_cdi_proquest_miscellaneous_28810948</recordid><sourceformat>XML</sourceformat><sourcesystem>PC</sourcesystem><ieee_id>977769</ieee_id><sourcerecordid>29462886</sourcerecordid><originalsourceid>FETCH-LOGICAL-c286t-6662dee629b356ee702d741a63be168ec226831b91b0f162fe12eb4ff28c3a183</originalsourceid><addsrcrecordid>eNqFkT1PwzAQhi0EEqUwsTFFDDCgFNtxLjZiQVX5kCqxgMRmOekFXKVJsZ2Bf4-jVAwMMN3p7tF9vC8hp4zOGKPqGrgSM1UUBag9MmFKsJSK_G0_5jmnqeKUH5Ij79eUMhBCTsjtog3ots56TIyrPmzAKvQObxLzbhtMgjOtt8F2bWLaVWI32wY32AYzlI7JQW0ajye7OCWv94uX-WO6fH54mt8t04pLCCkA8BViPK7MckAsKF8VghnISmQgseIcZMZKxUpaM-A1Mo6lqGsuq8wwmU3J5Th367rPHn3QG-srbBrTYtd7rZiI3xR5HsmLP8moD3Ap4X9QyiioGHaf_wLXXe_a-K7mFDIBlA7Trkaocp33DmsdFd0Y96UZ1YMzenBGj85E-mykLSL-kLvmN76Ah4M</addsrcrecordid><sourcetype>Aggregation Database</sourcetype><iscdi>true</iscdi><recordtype>article</recordtype><pqid>206346006</pqid></control><display><type>article</type><title>Enterprise architecture: agile transition and implementation</title><source>IEEE Electronic Library (IEL)</source><creator>Armour, F.J. ; Kaisler, S.H.</creator><creatorcontrib>Armour, F.J. ; Kaisler, S.H.</creatorcontrib><description>In our previous articles, we made the case for having an enterprise architecture and discussed the first phases of an architecture development process. The second article concentrated on describing the baseline architecture and defining the target architecture. We complete our discussion of the methodology by focusing on transition and implementation planning. Transition planning focuses on deriving a time-phased set of actions to achieve a given goal-in this case, implementation of the target architecture. Large organizations will remediate, renovate, or replace many systems concurrently. In doing so, they must recognize interdependencies among systems and accommodate them in activity scheduling. Implementation planning has a different time frame and a different audience. It maps resources (people, places, things, and funding) to transition planning activities.</description><identifier>ISSN: 1520-9202</identifier><identifier>EISSN: 1941-045X</identifier><identifier>DOI: 10.1109/6294.977769</identifier><identifier>CODEN: IPMAFM</identifier><language>eng</language><publisher>Washington: IEEE</publisher><subject>Architects ; Architecture ; Companies ; Costs ; Design ; Enterprise resource planning ; Focusing ; Force feedback ; Funding ; Information systems ; Information technology ; Iterative methods ; Legacy systems ; Phases ; Planning ; Process planning ; Recognition ; Resource management ; Scheduling ; Technology planning</subject><ispartof>IT professional, 2001-11, Vol.3 (6), p.30-37</ispartof><rights>Copyright IEEE Computer Society Nov/Dec 2001</rights><lds50>peer_reviewed</lds50><woscitedreferencessubscribed>false</woscitedreferencessubscribed><citedby>FETCH-LOGICAL-c286t-6662dee629b356ee702d741a63be168ec226831b91b0f162fe12eb4ff28c3a183</citedby></display><links><openurl>$$Topenurl_article</openurl><openurlfulltext>$$Topenurlfull_article</openurlfulltext><thumbnail>$$Tsyndetics_thumb_exl</thumbnail><linktohtml>$$Uhttps://ieeexplore.ieee.org/document/977769$$EHTML$$P50$$Gieee$$H</linktohtml><link.rule.ids>314,780,784,796,27924,27925,54758</link.rule.ids><linktorsrc>$$Uhttps://ieeexplore.ieee.org/document/977769$$EView_record_in_IEEE$$FView_record_in_$$GIEEE</linktorsrc></links><search><creatorcontrib>Armour, F.J.</creatorcontrib><creatorcontrib>Kaisler, S.H.</creatorcontrib><title>Enterprise architecture: agile transition and implementation</title><title>IT professional</title><addtitle>ITP-M</addtitle><description>In our previous articles, we made the case for having an enterprise architecture and discussed the first phases of an architecture development process. The second article concentrated on describing the baseline architecture and defining the target architecture. We complete our discussion of the methodology by focusing on transition and implementation planning. Transition planning focuses on deriving a time-phased set of actions to achieve a given goal-in this case, implementation of the target architecture. Large organizations will remediate, renovate, or replace many systems concurrently. In doing so, they must recognize interdependencies among systems and accommodate them in activity scheduling. Implementation planning has a different time frame and a different audience. It maps resources (people, places, things, and funding) to transition planning activities.</description><subject>Architects</subject><subject>Architecture</subject><subject>Companies</subject><subject>Costs</subject><subject>Design</subject><subject>Enterprise resource planning</subject><subject>Focusing</subject><subject>Force feedback</subject><subject>Funding</subject><subject>Information systems</subject><subject>Information technology</subject><subject>Iterative methods</subject><subject>Legacy systems</subject><subject>Phases</subject><subject>Planning</subject><subject>Process planning</subject><subject>Recognition</subject><subject>Resource management</subject><subject>Scheduling</subject><subject>Technology planning</subject><issn>1520-9202</issn><issn>1941-045X</issn><fulltext>true</fulltext><rsrctype>article</rsrctype><creationdate>2001</creationdate><recordtype>article</recordtype><sourceid>RIE</sourceid><sourceid>ABUWG</sourceid><sourceid>AFKRA</sourceid><sourceid>AZQEC</sourceid><sourceid>BENPR</sourceid><sourceid>CCPQU</sourceid><sourceid>DWQXO</sourceid><sourceid>GNUQQ</sourceid><recordid>eNqFkT1PwzAQhi0EEqUwsTFFDDCgFNtxLjZiQVX5kCqxgMRmOekFXKVJsZ2Bf4-jVAwMMN3p7tF9vC8hp4zOGKPqGrgSM1UUBag9MmFKsJSK_G0_5jmnqeKUH5Ij79eUMhBCTsjtog3ots56TIyrPmzAKvQObxLzbhtMgjOtt8F2bWLaVWI32wY32AYzlI7JQW0ajye7OCWv94uX-WO6fH54mt8t04pLCCkA8BViPK7MckAsKF8VghnISmQgseIcZMZKxUpaM-A1Mo6lqGsuq8wwmU3J5Th367rPHn3QG-srbBrTYtd7rZiI3xR5HsmLP8moD3Ap4X9QyiioGHaf_wLXXe_a-K7mFDIBlA7Trkaocp33DmsdFd0Y96UZ1YMzenBGj85E-mykLSL-kLvmN76Ah4M</recordid><startdate>200111</startdate><enddate>200111</enddate><creator>Armour, F.J.</creator><creator>Kaisler, S.H.</creator><general>IEEE</general><general>IEEE Computer Society</general><scope>RIA</scope><scope>RIE</scope><scope>AAYXX</scope><scope>CITATION</scope><scope>3V.</scope><scope>7WY</scope><scope>7WZ</scope><scope>7XB</scope><scope>87Z</scope><scope>8AL</scope><scope>8FE</scope><scope>8FG</scope><scope>8FK</scope><scope>8FL</scope><scope>ABJCF</scope><scope>ABUWG</scope><scope>AFKRA</scope><scope>ARAPS</scope><scope>AZQEC</scope><scope>BENPR</scope><scope>BEZIV</scope><scope>BGLVJ</scope><scope>CCPQU</scope><scope>DWQXO</scope><scope>FRNLG</scope><scope>F~G</scope><scope>GNUQQ</scope><scope>HCIFZ</scope><scope>JQ2</scope><scope>K60</scope><scope>K6~</scope><scope>K7-</scope><scope>L.-</scope><scope>L6V</scope><scope>M0C</scope><scope>M0N</scope><scope>M7S</scope><scope>P5Z</scope><scope>P62</scope><scope>PQBIZ</scope><scope>PQBZA</scope><scope>PQEST</scope><scope>PQQKQ</scope><scope>PQUKI</scope><scope>PRINS</scope><scope>PTHSS</scope><scope>Q9U</scope><scope>7SC</scope><scope>8FD</scope><scope>L7M</scope><scope>L~C</scope><scope>L~D</scope><scope>7TB</scope><scope>FR3</scope><scope>7SP</scope><scope>F28</scope></search><sort><creationdate>200111</creationdate><title>Enterprise architecture: agile transition and implementation</title><author>Armour, F.J. ; Kaisler, S.H.</author></sort><facets><frbrtype>5</frbrtype><frbrgroupid>cdi_FETCH-LOGICAL-c286t-6662dee629b356ee702d741a63be168ec226831b91b0f162fe12eb4ff28c3a183</frbrgroupid><rsrctype>articles</rsrctype><prefilter>articles</prefilter><language>eng</language><creationdate>2001</creationdate><topic>Architects</topic><topic>Architecture</topic><topic>Companies</topic><topic>Costs</topic><topic>Design</topic><topic>Enterprise resource planning</topic><topic>Focusing</topic><topic>Force feedback</topic><topic>Funding</topic><topic>Information systems</topic><topic>Information technology</topic><topic>Iterative methods</topic><topic>Legacy systems</topic><topic>Phases</topic><topic>Planning</topic><topic>Process planning</topic><topic>Recognition</topic><topic>Resource management</topic><topic>Scheduling</topic><topic>Technology planning</topic><toplevel>peer_reviewed</toplevel><toplevel>online_resources</toplevel><creatorcontrib>Armour, F.J.</creatorcontrib><creatorcontrib>Kaisler, S.H.</creatorcontrib><collection>IEEE All-Society Periodicals Package (ASPP) 1998-Present</collection><collection>IEEE Electronic Library (IEL)</collection><collection>CrossRef</collection><collection>ProQuest Central (Corporate)</collection><collection>Access via ABI/INFORM (ProQuest)</collection><collection>ABI/INFORM Global (PDF only)</collection><collection>ProQuest Central (purchase pre-March 2016)</collection><collection>ABI/INFORM Global (Alumni Edition)</collection><collection>Computing Database (Alumni Edition)</collection><collection>ProQuest SciTech Collection</collection><collection>ProQuest Technology Collection</collection><collection>ProQuest Central (Alumni) (purchase pre-March 2016)</collection><collection>ABI/INFORM Collection (Alumni Edition)</collection><collection>Materials Science &amp; Engineering Collection</collection><collection>ProQuest Central (Alumni Edition)</collection><collection>ProQuest Central UK/Ireland</collection><collection>Advanced Technologies &amp; Aerospace Collection</collection><collection>ProQuest Central Essentials</collection><collection>ProQuest Central</collection><collection>Business Premium Collection</collection><collection>Technology Collection</collection><collection>ProQuest One Community College</collection><collection>ProQuest Central Korea</collection><collection>Business Premium Collection (Alumni)</collection><collection>ABI/INFORM Global (Corporate)</collection><collection>ProQuest Central Student</collection><collection>SciTech Premium Collection</collection><collection>ProQuest Computer Science Collection</collection><collection>ProQuest Business Collection (Alumni Edition)</collection><collection>ProQuest Business Collection</collection><collection>Computer Science Database</collection><collection>ABI/INFORM Professional Advanced</collection><collection>ProQuest Engineering Collection</collection><collection>ABI/INFORM Global</collection><collection>Computing Database</collection><collection>Engineering Database</collection><collection>Advanced Technologies &amp; Aerospace Database</collection><collection>ProQuest Advanced Technologies &amp; Aerospace Collection</collection><collection>ProQuest One Business</collection><collection>ProQuest One Business (Alumni)</collection><collection>ProQuest One Academic Eastern Edition (DO NOT USE)</collection><collection>ProQuest One Academic</collection><collection>ProQuest One Academic UKI Edition</collection><collection>ProQuest Central China</collection><collection>Engineering Collection</collection><collection>ProQuest Central Basic</collection><collection>Computer and Information Systems Abstracts</collection><collection>Technology Research Database</collection><collection>Advanced Technologies Database with Aerospace</collection><collection>Computer and Information Systems Abstracts – Academic</collection><collection>Computer and Information Systems Abstracts Professional</collection><collection>Mechanical &amp; Transportation Engineering Abstracts</collection><collection>Engineering Research Database</collection><collection>Electronics &amp; Communications Abstracts</collection><collection>ANTE: Abstracts in New Technology &amp; Engineering</collection><jtitle>IT professional</jtitle></facets><delivery><delcategory>Remote Search Resource</delcategory><fulltext>fulltext_linktorsrc</fulltext></delivery><addata><au>Armour, F.J.</au><au>Kaisler, S.H.</au><format>journal</format><genre>article</genre><ristype>JOUR</ristype><atitle>Enterprise architecture: agile transition and implementation</atitle><jtitle>IT professional</jtitle><stitle>ITP-M</stitle><date>2001-11</date><risdate>2001</risdate><volume>3</volume><issue>6</issue><spage>30</spage><epage>37</epage><pages>30-37</pages><issn>1520-9202</issn><eissn>1941-045X</eissn><coden>IPMAFM</coden><abstract>In our previous articles, we made the case for having an enterprise architecture and discussed the first phases of an architecture development process. The second article concentrated on describing the baseline architecture and defining the target architecture. We complete our discussion of the methodology by focusing on transition and implementation planning. Transition planning focuses on deriving a time-phased set of actions to achieve a given goal-in this case, implementation of the target architecture. Large organizations will remediate, renovate, or replace many systems concurrently. In doing so, they must recognize interdependencies among systems and accommodate them in activity scheduling. Implementation planning has a different time frame and a different audience. It maps resources (people, places, things, and funding) to transition planning activities.</abstract><cop>Washington</cop><pub>IEEE</pub><doi>10.1109/6294.977769</doi><tpages>8</tpages></addata></record>
fulltext fulltext_linktorsrc
identifier ISSN: 1520-9202
ispartof IT professional, 2001-11, Vol.3 (6), p.30-37
issn 1520-9202
1941-045X
language eng
recordid cdi_proquest_miscellaneous_28810948
source IEEE Electronic Library (IEL)
subjects Architects
Architecture
Companies
Costs
Design
Enterprise resource planning
Focusing
Force feedback
Funding
Information systems
Information technology
Iterative methods
Legacy systems
Phases
Planning
Process planning
Recognition
Resource management
Scheduling
Technology planning
title Enterprise architecture: agile transition and implementation
url https://sfx.bib-bvb.de/sfx_tum?ctx_ver=Z39.88-2004&ctx_enc=info:ofi/enc:UTF-8&ctx_tim=2024-12-25T23%3A53%3A42IST&url_ver=Z39.88-2004&url_ctx_fmt=infofi/fmt:kev:mtx:ctx&rfr_id=info:sid/primo.exlibrisgroup.com:primo3-Article-proquest_RIE&rft_val_fmt=info:ofi/fmt:kev:mtx:journal&rft.genre=article&rft.atitle=Enterprise%20architecture:%20agile%20transition%20and%20implementation&rft.jtitle=IT%20professional&rft.au=Armour,%20F.J.&rft.date=2001-11&rft.volume=3&rft.issue=6&rft.spage=30&rft.epage=37&rft.pages=30-37&rft.issn=1520-9202&rft.eissn=1941-045X&rft.coden=IPMAFM&rft_id=info:doi/10.1109/6294.977769&rft_dat=%3Cproquest_RIE%3E29462886%3C/proquest_RIE%3E%3Curl%3E%3C/url%3E&disable_directlink=true&sfx.directlink=off&sfx.report_link=0&rft_id=info:oai/&rft_pqid=206346006&rft_id=info:pmid/&rft_ieee_id=977769&rfr_iscdi=true