Chapter 2: Exploring Architecture Frameworks and Methodologies

In this chapter, we will explore the most widespread frameworks that you will typically encounter in various organizations. Be aware that I only introduce them because most of these frameworks deserve a dedicated book. I will try to highlight the essential parts and the mindset behind each framework.

More specifically, this chapter covers the following topics:

• Introducing frameworks and methodologies
• Delving into The Open Group Architecture Framework (TOGAF), ArchiMate, and related tools—enterprise architecture (EA)
• Introducing security frameworks
• The Information Technology (IT) Infrastructure Library (ITIL) in a nutshell

By the end of the chapter, you should be better equipped to interact with stakeholders who contribute to the broader IT landscape. Understanding their concerns is key to growing as an architect. I encourage you to go the extra mile on your own, to brush up your skills...

Introducing frameworks and methodologies

There are many frameworks, standards, and architecture tools in the IT industry. Frameworks are essentially a set of best practices that should be inspirational for an enterprise's users. They differ from standards in that they are not prescriptive. Conversely, standards are prescriptive, in that you must adhere to all their rules to get certified. The following screenshot shows some of the recurring frameworks, standards, and tools, as per the architecture discipline:

Figure 2.1 – Frameworks and tools

Starting from the left, we have the EA practice, which is mostly conducted using TOGAF and the ArchiMate modeling language. Sparx Systems Enterprise Architect is a widespread tool suite that helps you build both ArchiMate viewpoints and Unified Modeling Language (UML) diagrams. ArchiMate is used to draw high-level types of viewpoints, while UML can be used to draw both high- and low-level types of views. If...

Delving into TOGAF, ArchiMate, and related tools – EA

As explained in the first chapter, the main purpose of the EA function is to connect the IT department to different business lines and to make sure that IT investments and initiatives ultimately create business value. Most EA organizations are based on TOGAF.

Introducing TOGAF's ADM

The purpose of the Architecture Development Method (ADM) is to manage the development life cycle of the EA practice. The following screenshot shows the ADM proposed by TOGAF:

Figure 2.2 – TOGAF ADM

You can follow this to cover the entire spectrum of EA in a series of logical steps. However, because TOGAF is only a framework, you can perfectly decide to work only with some of the steps of that development cycle. The extent to which you apply TOGAF will be better understood once you have completed the preliminary steps and the architecture vision (Step A in Figure 2.2). If there were only one required step...

Introducing security frameworks

Before exploring security frameworks, let me describe the typical duties of a security architect. One of the best ways to identify them is to look at Certified Information Systems Security Professional (CISSP) certification, which is the most wanted certification for security professionals. The CISSP exam covers the following topics:

• Security and Risk Management
• Asset Security
• Security Architecture and Engineering
• Communication and Network Security
• Identity and Access Management (IAM)
• Security Assessment and Testing
• Security Operations Center (SOC)
• Software Development Security

The list is composed of both IT and technical security topics. I don't know about you, but as a cloud architect I am heavily exposed to security demands, and I consider that being able to talk the language of a security architect is a key asset to overcome some hurdles.

A properly driven security organization revolves around...

ITIL in a nutshell

ITIL is a United Kingdom (UK)-born framework. Back in the 1980s, the UK administration realized that its internal IT service management was rather chaotic. They decided to clean the house and build a framework that would assemble best practices from all over the place when it came to service management. Since then, ITIL, currently at version 4 (v4), is a world-leading IT service management framework. Infrastructure and operations teams around the world use ITIL, consciously or unconsciously.

ITIL primarily focuses on internal customers. For example, when you, as an employee or collaborator, request a corporate laptop to work with or when you need to access a certain system, you resort to ITSM. ITSM encompasses the organizational capabilities that deliver value to a customer (internal, in this case). The infrastructure department and the service-desk function are the back offices of a company. They keep the lights on and make sure everyone has the necessary tools...

Summary

In this chapter, we browsed through some of the most widespread frameworks in the IT industry. You learned that TOGAF and ArchiMate are the languages of enterprise architects. As a software architect, you might be brought in to draw architectural patterns and some EA building blocks. We then reviewed NIST and COBIT for Risk, which come in handy to drive a security practice. We finally explored ITIL, the de facto ITSM framework used by most organizations. By understanding the essential parts of these frameworks, you should be able to optimize your interactions with other stakeholders. These extra skills might become a differentiation factor between you and an average software architect. Of course, I encourage you to explore some of the frameworks further, as these were only introduced in this chapter.

In the next chapter, I will introduce a software architecture methodology that I have been using at different places and that you will undoubtedly encounter sooner or later...