Writing code

I will discuss in the following about bug and software development in general.  

I was reading an article about what a good programmer is.  The article contained a few good points, clearly matched by my previous experience.  While I may not necessarily agree with the rest of the points, I found the ones below of significance. 

"This is also about how we define quality and what a bug is.  If we look at a traditional and very "intuitive" definition of a bug, it is something that causes our software to produce an incorrect or unexpected result. However, if we think more about how the software is actually used and by whom, we'll see that there are many other types of bugs, including scalability, reliability, and even maintainability ones."

"If we put all those "-ilities" in a list and prioritize them by their severity and importance to the business, we'll see that functionality-related bugs are rather far from the top. I would actually put maintainability at the top."

"My point is that mistakes are not all equal. If I'm writing a PDF report generated by a piece of Java code and my report misses the footer, that's one type of bug, and its fix will cost the business X dollars. On the other hand, if my PDF generation code is so difficult to modify that in order to change its format from A4 to US Letter we have to rewrite it from scratch, that's a completely different type of bug. Needless to say, its fixing will be many times more expensive."

"There are exceptions, of course, where the business prioritizes functionality above everything else, but such situations happen very rarely (if the business is smart)." - however, the technical architect also has a role here to try to make things happen by this rule).

Organization and Architecture

Learning something new every day :)

Any organization that designs a system (defined broadly) will produce a design whose structure is a copy of the organization's communication structure.

-- Melvyn Conway, 1967

Microsoft reference architecture for banking

I spent some time documenting myself about Microsoft offerings for banking industry and I came across MIRA-B.

What I found interesting about this paper is that it covers in a clear and concise manner the business architecture from the banking perspective - challenges and goals for the banking sector, as well as a current snapshot of the trending market forces.

One example of some other forces disrupting the market is Apple Pay.

Here's the link, enjoy :)

http://www.microsoft.com/enterprise/industry/financial-services/banking-and-capital-markets/reference-architecture/default.aspx#fbid=onVDsDrUuky

EA

Enterprise Architecture

I did some study on TOGAF framework for my Open Group TOGAF 9.1 Certification Exam.
With this occasion, I took some time to think about it and came up with some opinions and ideas. Some of these could be found below.

I think there are some challenges on implementing it within enterprises:

1.  The technique to trim it down to a specific enterprise as needed in order to be easy to use within the enterprise - this also pertains to the key people and processes - think of it as a custom tailoring of the TOGAF framework for the enterprise it you will.  All this would require a significant amount of experience from the person driving this effort.   One could say that the activity to understand the specific business organization (not only processes but people and relationships) and to tailor the framework accordingly is also an art.

2. Triggering these kinds of changes within enterprises will always be challenging. That is, change, support and trigger the transformations within the enterprises in order to establish the enterprise architecture capabilities.

3.  My opinion remains that - and this is not something I read during my study - one must tailor and apply the TOGAF framework in an agile way.  The enterprise architecture capability and its processes should be designed with agility in mind, even for large enterprises.   Creating large amount of documentation, difficult to read and understand - much less to apply, as well as having complicated and time consuming architecture requirements management and governance processes is not going to help too much in this area.   I think that these enterprise capabilities should ensure that the IT supporting the enterprises is aligned to the business vision and requirements - but they need to do so in an agile way.

So, is TOGAF useful?  I think very much so.  But in the end it's just a framework with a vision - the real challenge will rest on the shoulders of people that are going to apply it - as always, an idea (strategy) however great remains an idea if you do not have the right people to understand it and execute on it ;)

Have fun

Architecture definition

While reading some materials a few days ago, I ran over a cool definition of IT architecture, and I thought about sharing it with you.  This is because in the past I encountered (and witnessed) difficulties while attempting to define it in a clear, concise manner.  So here it goes:

Architecture

1. A formal description of a system, or a detailed plan of the system at component level to guide its implementation

2. The structure of components, their inter-relationships, and the principles and guidelines governing their design and evolution over time

Have fun :)