alternate text alternate text alternate text alternate text

IFEAD

People -- Process -- Business -- Technology
IFEAD is an independent research and information exchange organization working on the future state of Enterprise Architecture.

Information Exchange Area of the

Institute For Enterprise Architecture Developments

-

Collaboration between IFEAD and Logica Management Consulting

Mr. Jaap Schekkerman, the President & Thought Leader of IFEAD, will by the 1st of April join Logica Management Consulting. On a part-time base his activities for Logica Management Consulting will be focused on enhancement of the EA practice and board room consulting to customers.


Enterprise Architecture: a journey, not a destination.

GCN Interview with Jan Popkin, founder of Popkin Software and a strategist at Telelogic.

GCN: What developments are we likely to see with enterprise architecture this year? Some experts talk about the need for more data management, business processes and security.

Popkin: Enterprise architecture continues to mature. There is an understanding of what it is, and people are saying, “Now that we are doing enterprise architecture, what benefits or actions do we want to result from that?” It’s less, “Should we or shouldn’t we do the program?” [and more] “We’re doing the program now; let’s tune it to our particular needs.”

Enterprise architecture is a mechanism to provide results — whether it’s agility, alignment, collaboration — and so…it is an enabler in itself. I see [users] looking for results, tuning programs. The other part of the enterprise architecture discussion is moving further out from an IT chief architect discussion to involving extended-team collaboration with other groups. And that opens up the questions of data management, business process and security.

For instance, “We have data we want to share — what are the rules for sharing it?” “We provide this process or business service — how can we share it?”

And security is an ongoing discussion. In the past, there has been discussion of laying in a security view. I think that’s always been balanced with having security intrinsic across everything you’re doing and having it especially called out.

GCN: We’re hearing a lot about service-oriented architecture and business process management. How can agencies apply these disciplines and associated technologies in an EA framework?

Popkin: When we talk about an EA framework, I’d like to map that into an EA program. An EA program is an ongoing mechanism to understand what your goals are and what an agency’s service goals are and align that with IT services and business processes. So the enterprise architecture program or framework provides a context to understand the implementation of such a thing as SOA or business process management.

But when we talk about SOA, there are multiple definitions of it. When I talk about SOA in this context, I’m talking about it as an architectural principle, which means supporting the agility of moving things around over time and [supporting] data sharing. I think in the federal space that is what people are talking about, which is having that agility and data sharing.

It’s not discussing SOA technology, it’s talking about the architecture around it. Having said that, you can see the alignment of an EA program — which involves understanding and defining services, an agency’s goals and what it needs to achieve — and then having the SOA architectural principle below supporting that in a high-level implementation.

As you do the services, you have to involve the business processes around it. When you’re talking about the SOA architectural principle, there are people and things around that and the processes which are very important to enable those SOA architectures.

Tying that all together, the EA program is a higher-level view of what’s going on, how that’s aligned to where you are and where you are going.


IEEE 1471 has been adopted by ISO as ISO/IEC 42010:2007

IEEE 1471 has been adopted by ISO as ISO/IEC 42010:2007, Systems and software engineering -- Recommended practice for architectural description of software-intensive systems.


IEEE and ISO have begun joint revision of the standard which will become Systems and software engineering -- Architectural description. The revision will be undertaken by ISO/IEC JTC 1/SC 7 Working Group 42*
___________
* "42" because it is said that, "Architecture is the answer to life, the universe, and everything." :-)
___________

The joint revision has several goals:
  • to widen the scope of application from software-intensive systems to general systems architecture (including enterprise architecture);
  • to harmonize with the ISO systems engineering (ISO 15288) and software engineering (ISO 12207) life cycle processes; and
  • to align terms and concepts with other ISO architecture efforts, including RM-ODP (ISO 10746) and GERAM (ISO 15704).


Interested parties may participate in the revision either through their ISO member bodies, or through IEEE.


For more information, see IEEE 1471 | ISO 42010 web site:

http://www.iso-architecture.org/ieee-1471/


Third Renewed and Updated Edition Now Available

Book is expended with an additional 40 pages including the European Interoperability Framework as well as new chapters about EA tool selection & support.

publication cover shot

ISBN 1-4120-1607-X

Trafford Publishing, Canada

By Jaap Schekkerman

Book is also available via AMAZON.COM, Barnes & Noble.com, All-Computer- books.co.uk, etc.

New Book Announcement from IFEAD

Expected May 2008

Titled:

'Enterprise Architecture Good Practices Guide'

How to Manage the Enterprise Architecture Practice

Trafford Publishing, Canada

by Jaap Schekkerman

This Enterprise Architecture Good Practices Guide is based on IFEAD's well known sets of EA guides that are published over the years and enhanced on feedback from users.

Topics addressed in this guide.

Defining EA maturity; Initiating EA Program; Adoption of EA Frameworks; Developing EA Results; Selecting EA Tools; Explaining EA Deliverables; Doing EA Assessments; Showing EA Sets of Viewpoints; EA Governance, Etc.


How do you show your executives the value of EA?

The First Enterprise Architecture Book that addresses the issues of the Economic Benefits of Enterprise Architecture; Read more .....and Order Direct

'The Economic Benefits of Enterprise Architecture: How to Quantify and Manage the Economic Value of Enterprise Architecture'

ISBN 1-4120-6729-4

Trafford Publishing, Canada

by Jaap Schekkerman

First Edition;295 pages; Perfect bound; catalogue #05-1640; ISBN 1-4120-6729-4

This book is explaining, how to quantify and manage the economic value of enterprise architecture. Several methods, models and techniques are described to adopt an economic approach when dealing with Enterprise Architecture.

Go to Traffords website of this Book and order this book directly at the Publisher's website, the easiest and cheapest way to do.

-
IFEAD in the News
More Information about IFEAD

For more information about 'The Institute For Enterprise Architecture Developments', or information about partnerships with the institute send an e-mail to the secretary:

E-mail: info[AT]enterprise-architecture.info [AT]=@

RSS Feed News

Latest Update 05/05/2008

Extended Enterprise Architecture Framework / E2AF & Extended Enterprise Architecture Maturity Model / E2AMM are Service Marks (SM) registered by IFEAD