Aggregated enterprise architecture wisdom
One of the most challenging aspects in our role as architects is that we often have to influence without direct authority. We often wrestle with this fact as we may not have the managerial clout and there may be lack of clarity on what precisely we are accountable for. Perhaps simply stated, we have to be THE accountable party for…
How well does your system-design cope with something that doesn’t fit? And how can you design a system for a business-context of mass-uniqueness, where the likelihood of coming across something that doesn’t fit – maybe often – is not so much…
I’ve got some very exciting news to share with all of you. I have accepted the position of Research Director within the Enterprise Architecture practice at Gartner! As many of you know that read my blog I often comment on…
In less than 2 minutes, this video – from Orbus Software – gives a great overview of the The Open Group’s Enterprise Architecture framework:
Enterprise Architecture (EA) and organizational performance assessment and improvement are often viewed as separate and distinct disciplines. The former, often residing in the realm of the Chief Information Officer (CIO)
The post TOGAF® meets Baldrige: Strange Bedfellows or a Marriage Made in Heaven? appeared first on Enterprise Architecture Professional Journal.
Mike Callahan is a recognized business architecture expert and co-founder of AgileLayer, a provider of business architecture methodologies, software and consulting services. Mike and his colleagues have introduced a number
The post Thought Leader Interview: Mike Callahan on Business Architecture appeared first on Enterprise Architecture Professional Journal.
This paper was written by Abi O’Neal to fulfill an assignment from the University of Denver University College ICT 4010 Enterprise Architecture course taught by EAPJ founder Dr. Steve Else.
The post Case Study: Improving a Cloud Computing Initiative at a Non-Profit Organization appeared first on Enterprise Architecture Professional Journal.
We can easily generate automatically monster diagrams inputting at random all we know about the enterprise entities and their relationships.
“Form follows function” – that’s what we were always taught at design-school. Yet is that actually true? I wonder… There was nothing in particular that triggered this one off: it was just one of those ‘first thing in the morning’…
We recently wrote about Enterprise Intelligence (EI) as a concept that delivers executives and decision makers with the insights they need to make more informed business and technology strategy decisions because of its enterprise transparency and visibility. In light of the recent wave of cyber security breaches it’s a good time to point out that EI insights also help with decisions related to everyday operations. In this case, strengthening cyber security
The bad guys are winning
Cyber security experts tell us that virtual crimes have hit a tipping point. In 2013 cyber-crimes affected more than 200 million users worldwide and in the US alone more than 480 corporate data breaches occurred involving 95+ million records (The 9 Biggest Privacy And Security Breaches That Rocked 2013 / thinkprogress.org).
The attackers don’t discriminate. Government systems, social networks, and a leading retailer were all compromised leaving the public uneasy about the data they share online.
The truth shall set you free
It’s a hard truth, but the reality is that the proactive use of EI can single-handedly evade even the worst of attacks. You see, with the complete enterprise transparency EI provides there are no questions about security and exposure risk within the IT walls of a business.
For context let’s revisit the very public 2013 Department of Energy (DOE) data breach that left more than 100,000 names compromised. In this case, not knowing the lifecycle of an application cost the DOE upwards of $3.7 million in lost productivity and credit monitoring.
At the time the DOE was using Adobe’s Cold Fusion, which had become unsupported, so Adobe wasn’t sending patches to fix security holes, resulting in the security lapse.
With EI companies have a complete view of the application lifecycle so they can take appropriate measures to retire or find way to obtain extended support applications.
At Troux we work with data-cloud company, BDNA to provide clean, rich data so that companies know how their applications, technologies, processes and people relate to one another and the overall business. The BDNA Technopedia catalog contains more than 38 million researched data points for over 960,000 hardware and software products. The data is updated every day with new products and market information such as software support levels, Windows compatibility, end-of-life dates, hardware power consumption, and much more. Technopedia also tracks vendor mergers and acquisitions, informing users of market changes so enterprises are never left guessing if their data is accurate.
Evolution means evolving problems. Nowadays we have to worry about cyber bugs and attacks. With that comes new ways to fend off the perpetrators. How about using EI to fend off these online security attacks?
Recently Troux hosted a webinar on cyber security, touching on ways to proactively mitigate threats. To learn how to develop a cyber security plan for your connected enterprise, click here.
 |
| Architect and Engineer Perspectives – in Zachman Framework All Copyrights with Zachman International |
TOGAF though defines Architect roles well; it probably does not clearly differentiate between an Architect and an Engineer at a role profile level. But it does offer a good methodical (as you can expect from TOGAF) and well defined classification of view; namely, Business Architecture View, Data Architecture View, Software Engineering View, System Engineering View and so on. In my opinion that works well too as with these views an organisation can then map roles, responsibilities of Architects and Engineers onto its operating model.
While many readers of this blog may or may not agree with precise definitions, I think this is still a good enough framework for us to start building operating model constructs around how best do Architects work with Engineers? Or vice versa! In some organisation they may be played by single role profile, in large environments it may be spread across say two or three role profiles. In an outsourced environment, Architect role may still be part of the retained IT staff and Engineers (or Engineering Services) may be procured from suppliers. I suppose, individual organisational operating model will dictate the specifics on these.
|
|
Architect and Engineer Perspectives – in Zachman Framework All Copyrights with Zachman International |
TOGAF though defines Architect roles well; it probably does not clearly differentiate between an Architect and an Engineer at a role profile level. But it does offer a good methodical (as you can expect from TOGAF) and well defined classification of view; namely, Business Architecture View, Data Architecture View, Software Engineering View, System Engineering View and so on. In my opinion that works well too as with these views an organisation can then map roles, responsibilities of Architects and Engineers onto its operating model.
While many readers of this blog may or may not agree with precise definitions, I think this is still a good enough framework for us to start building operating model constructs around how best do Architects work with Engineers? Or vice versa! In some organisation they may be played by single role profile, in large environments it may be spread across say two or three role profiles. In an outsourced environment, Architect role may still be part of the retained IT staff and Engineers (or Engineering Services) may be procured from suppliers. I suppose, individual organisational operating model will dictate the specifics on these.