Phase E is the first phase that does the actual implementation of the Target architecture developed in the previous phases. This phase provides the process to identify major implementation projects and grouping these projects into work packages.
Continue readingIntroduction to TOGAF (Part 2 of 4) Phase A
Architecture Vision TOGAF is required for every architecture cycle.
Continue readingIntroduction to TOGAF (Part 1 of 4) Preliminary Phase
Preliminary phase is the initial phase of the TOGAF ADM Process. In this phase the preparation and initiation activities for creating an Architecture Capability are carried out. It includes key activities
Continue readingTOGAF ADM Phase A (Part 4 of 4) — Statement of Architecture Work
The ‘Statement of Architecture Work’ defines the scope and approach that will be used to complete an architecture project. This video shows you how to develop a Statement of Architecture Work.
Continue readingTOGAF ADM Phase A (Part 3 of 4) — Capability Assessment
Before embarking upon a detailed Architecture Definition, it is valuable to understand the baseline and target capability level of the enterprise. This video shows you how to assess an organization’s business and IT capabilities.
Continue readingTOGAF ADM Phase A (Part 2 of 4) — Communications Plan
Enterprise architectures contain large volumes of complex and inter-dependent information. Effective communication of targeted information to the right stakeholders at the right time is a critical success factor for enterprise architecture. This video shows you how to develop a Communications Plan.
Continue readingTOGAF ADM Phase A (Part 1 of 4) — Architecture Vision
Provides a high-level, aspirational view of the end architecture product. The purpose of the vision is to agree at the outset what the desired outcome should be for the architecture, so that architects can then focus on the critical areas to validate feasibility. This video shows you how to develop an Architecture Vision document.
Continue readingUML vs Software Development Process
A software development process is a recipe used for constructing software determining the capabilities it has, how it is constructed, who works on what, and the time frames for all activities. Processes aim to bring discipline and predictability to software development, increasing the chance of success of a project .UML is the language for modeling your software, it’s an important part of the software development process. Modelling consists of building an abstraction of reality. Abstractions are simplifications that They ignore irrelevant details and They only represent the relevant details.
Continue readingUML: What is Package Diagram? How to use it?
A package is a grouping of model elements which means that a package can contain model elements of different kinds, including other packages to create hierarchies. A package defines a namespace for its contents using for various purposes.
Continue readingUML from What to How with Use Case and Activity Diagram
Use cases show what your system should do. Activity diagrams allow you to specify how your system will accomplish its goals. Activity diagrams show high-level actions chained together to represent a process occurring in your system. Activity diagrams are particularly good at modeling business processes or elaborating a use case. This article shows you how to do so.
Continue reading