Aggregated enterprise architecture wisdom
When was the last time you found yourself on a project that didn’t involve some degree of file transmission? No, that one doesn’t count… Ok, so maybe you occasionally have a solution that doesn’t require any file delivery but every architect worth his weight in .csv files is going to come across this task at […]
Rhinebeck, NY April 23, 2013 – Systems Flow, Inc. announced that the Systems Flow Investigative Architecture™ method has been recognized within The Open Group Certified Architect (Open CA) Program. “A foundational skill for an architect is the rapid ability to assess and document current and proposed solution designs,” said Dan Hughes, Principal with Systems Flow. […]
If you are attending The Open Group Conference in Sydney next week, we’ve put together a few tips on how to leverage social media to make networking at the conference easier, quicker and more effective. … Continue reading →
We use a system context diagram in the early stages of our Investigative Architecture™ process. It provides a high level functional view of a system and, while it is very powerful for the early stages of functional design, it also ensures you have identified any functional needs that impact the non-functional, or architectural, aspects of […]
One way to maximize the benefits is to make technology work for you. If you are attending The Open Group Conference in Newport Beach next week, we’ve put together a few tips on how to leverage social media to make networking at the conference easier, quicker and more effective. Continue reading →
As practicing solution and enterprise architects we regularly present our work to our stakeholders for feedback. Those stakeholders range from mentors to peers to project teams to executive sponsors. In any and all of those situations, it is important to be able to accept feedback. In some cases the feedback will have been solicited by […]
In my last post, Traceability 101, I talked about the essential role traceability plays in the success of a project. By writing business requirements, functional requirements, and then drawing traces between them you can create a traceability matrix that reveals 1) business requirements that are not covered by functional requirements, and 2) out-of-scope functional requirements […]
We write frequently on this blog about our proven method to deliver IT architectures based on industry-standard tools and approaches like UML and IT Risk Management. We also write about the critical intangible skills that an architect needs to succeed, such as meeting facilitation, diplomacy and organization. One needs to be steeped in all these […]
The Open Group Blog is celebrating its second birthday this month! While several members and Open Group staff serve as regular contributors, we’d like to take this opportunity to invite our community members to share their thoughts and expertise on topics related to The Open Group’s areas of expertise as guest contributors. Continue reading →
This may seem like an odd blog coming from a company that is so deliverable focused, but it isn’t. A design document is not just a document, but a powerful tool for figuring out an architecture. However, it is easy to get caught up in the “task” of completing the design document and lose focus […]
Objectives and requirements – they are what makes the project world go ’round. Changing a business’ operations for the better requires one to decide what are the objective of the change, and what are the requirements a change must meet to satisfy the objective. Implementing the change usually starts with someone needing to know what […]
Want to get an overview of what enterprise architecture bloggers blog about? I did, so I created this ‘planet’. Read more about it. Want your blog feed to be included? Contact me at @gotze. 00