Pass Your The Open Group TOGAF OG0-091 Exam Easy!

The Open Group OG0-091 TOGAF 9 Part 1 exam dumps vce, practice test questions, study guide & video training course to study and pass quickly and easily. The Open Group OG0-091 TOGAF 9 Part 1 exam dumps & practice test questions and answers. You need avanset vce exam simulator in order to study the The Open Group TOGAF OG0-091 certification exam dumps & The Open Group TOGAF OG0-091 practice test questions in vce format.

ADM: Starting Out

7. Phase A: Architecture Vision

Let's get into talking about Phase A, which is the Architecture Vision Phase. Phase A sits at the top of the ATM cycle, just after the preliminary phase is finished. The purpose, the main purpose of the vision, and the phases are to develop the high-level vision to be delivered. You may also receive approval for the Statement of Architecture Work. The Statement of Architecture Work contains things such as a scope, resources, a roadmap and schedule, any KPIs and metrics, and a communication plan for the architecture work. Remember, we treat the architecture work as a project, and a project has a budget, a scope, and a schedule. So the objectives of vision phase number one are to develop a high-level aspirational vision of the capabilities and business value to be delivered. And number two is to obtain approval for a Statement of Architecture Work. The first approach is to create the request for architecture work, which is going to define what is in and what is out of scope. What you're going to find is that if you don't define the scope or if you define the scope too broadly, you're basically taking on a massive project to try to define the baseline and target architectures in one huge scoop, especially if you're starting off with a very low architecture capability or you've never really done this before. The architecture work is going to define your scope, and that's really what's going to get this project to succeed. Creating the Architecture Vision—we'll get into that when we get into the steps of going through the ADMS business scenarios process. So what we do in the TOGAF world is use business scenarios to define the problems and dig down deeper. and I'll just show you real quick what a business scenario looks like. So you start with a problem. The problem lives in the environment. That environment has objectives. There are human actors, which are the employees and the customers, and other people who operate within this environment. There are computer actors, which are systems. There are roles and responsibilities for all of these things. And then you are going to have to go back and refine the problem. Refine the problem. As you can see, every problem has a business scenario process within the toy aspect. It goes into these steps and how to really go through them in detail. As usual, I'm going to fly through the inputs because I find them to be the least helpful bits.You've got the reference materials request for ArchitectureWork. Some of these things have been principles. They were created in the preliminary phase of a tailored architecture framework. Again in preliminary phasepopulated architecture repository. You'll notice that a lot of these things are outputs of the last phase and are going to become inputs. I'm calling the ones on screen common inputs because you'll notice that they're used in a lot of the phases, almost all of the architecture definition phases, and there's really no point in talking about them. Step number one: establish the architecture project. Okay? This is the kickoff meeting. This is your schedule. You've got a project manager. I'm going to do this within two weeks. This will take four weeks. You've got tasks. Identify stakeholders, their concerns, and the business requirements. Now, identifying stakeholders is a super important part of the TOGAF process because the stakeholders are the people who are going to help you succeed by answering your questions. B. They're the ones you're trying to satisfy. So they give you the requirements, and you turn around and give them a solution that meets their requirements. See, you do need to learn how to talk to different people. You're going to have the Chief Financial Officer, you're going to have the CIO CEO, and you're going to have some front line It has staff—the sales staff, the call centre staff. Every department is going to need to be talked to. And they have a vested interest in whatever you do. But you talk to me using different language, different diagrams, and different documents. You do not show a lot of the deep technical stuff to the Chief Financial Officer. You don't have to show the call centre a lot of financial information. Once again, confirming business goals We did this in the last phase as well. Evaluate your business capabilities. Now, we've already talked about the architectural capability in this phase. You're going to talk about what your company is good at, what it's not good at, sort of a scale of one to ten types of things in each of the things that you're trying to do, how well you do them, and to what degree. Okay, so the readiness for transformation will pop up, especially when you get into the migration planning, opportunities, and solutions phases. But readiness for transformation is an evaluation of how your company adapts to change. A lot of companies do embrace change, and they do go rapidly, sometimes to their detriment when they go too rapidly. But there are companies where change is expected, and then there are other companies where change is extremely difficult. I was recently on a project where even getting a minor version number change for a piece of software and getting approval for that was just too difficult. We ended up implementing a version behind the most recent because that was already approved, and trying to get a minor version number to get approved would have been too much. So some companies have very difficult times adapting to any change, and some companies have a lot easier time defining the scope of their vision. Okay, number seven, the architectural principles. So you've defined them. Now you're into the process of creating your vision. You're creating some of your solutions at a high level. You need to confirm that your principles are still working for you. Develop the architectural vision. Okay? The architecture vision is what you're seeing the target architecture as being at a very high level, but you kind of define what the problems are. And now you're going to say it's actually right in the first phase here, phase A. You get to say, "Okay, this is what we're probably going to implement," something like this. It's boxes and lines. It might be a very short piece of paper—one or two pages—to describe this. It's a very high level. You don't know the specifics yet, but you have a general idea of the solution, as well as the target architecture value. So what is your company going to be able to do with this new architecture? What are they going to be able to earn? What are they going to be able to save? Our change is going to be easier and quicker. Okay. What are the values of the business that you're proposing? And the transformation, risk, and mitigation activities are listed at number ten. And number eleven is the statement of architecture work, which is that once you've got your vision, you go and sell it, and they say, "Yes, go and develop it for me," and you get approvals. Those are the eleven steps of the vision phase. The outputs. Once again, these are documents that are created during these steps. We do talk about them during the steps. You've made changes to some of your existing documents. You've got a vision. Of course, the draught architecture document version zero is a high-level draught of your architecture. The communications plan talks about how you communicate with stakeholders and any additional content that goes in there because your repository, the artefacts listed on screen, are too numerous for me to really go through them. But in the vision phase, you do create some diagrams and a matrix, at least, and your assignment. So now that we've gone through the vision phase, reading Chapter Seven of the Specs should be a lot easier. You can go ahead and do that. I have added chapter section ten to this course, which goes through each of the steps of the vision phase one by one in more detail. So go ahead and check out Section 10 if you want to get more in-depth on that. So that's it for preliminary Phase A. Let's have a little quiz about what you've learned.

ADM: The Four Domains of BDAT

1. Introduction to BDAT

So now comes this acronym, which you're going to hear about a lot. It's called BDAT. BDAT. It stands for Business Data, Application, and Technology. If you think of an enterprise, the BDAT are the layers that go from the business to the underlying technology. In between are the applications and data that connect to the BDAT domain architecture. Domains are a way of dividing up the architecture of the entire company into four manageable parts. You'll often find within companies that there are architects who specialise in one of the domains. So you'll have a business architect who specialises in business architecture, has a relationship with the business, interviews the business owners, and can translate their requirements into TOGAF adm requirements. Then there are the technical experts who can go into networking and understand how things are currently connected and transition that into a target architecture. So each of these domains is an area of specialisation for an architect. All four of these things work together to create the architecture. The output of the AD architecture definition basis The reason why we do business architecture first is because we want the business needs of the business to drive the technology, not the other way around. So if the business needs a mobile workforce, then we have the technologies to respond to that and create the technology for them to work in that mobile space. We do not turn around and say that technology wants to provide these things that the business may not need. So in the following videos we'll go through each of the phases of BDAC phases B, C, and D. You'll notice that C divides data and application into two phases in one. And I don't know why they did that, but they did. So coming up in the next three or four videos, we'll go through the BDP phase.

2. Phase B: Business Architecture

Let's get into Phase B, the Business Architecture Phase. Phase B is the second phase of the ATM cycle. So once you've created the vision, you get into the business architecture definition. Togaf has this acronym called BDAT. To summarise this and the next two phases, that stands for Business Data Application and Technology. These are the four architecture domains that make up a total architecture. So one of your objectives for the business architecture phase is to develop a baseline business architecture for Version 1.0. Now there are two approaches. It could be a bottom-up approach, which means the baseline architecture already exists. You just need to go out there and discover it and document it. Okay, the target business architecture is normally a top-down approach, which means you sit it down, you think up your desired needs, you find the solutions for those needs, and that gets put into the target architecture. It doesn't already exist. You're dreaming up what should exist, and that's called a top-down approach. Finally, once you've got your baseline, which is the present, and your target, which is the future, your goal is to identify the gaps between where you are and where you want to be in the business architecture domain, and that gets into the requirements. So keep in mind that the four architecture domains—business data, application, and technology—are all going to be very similar. They're done using a similar process. The inputs, steps, and outputs are almost the same. There's always going to be one little difference, but that's pretty much the same. Now that makes it easier for your studying, but it does make it a bit repetitive when we're going through them one by one. The other thing to keep in mind is that, oftentimes, in a large organization, you have different architects that specialise in one of these domains. So you're going to have business architects, sometimes called business analysts, data architects, application architects, and technical architects. And these people have deep domain expertise in those particular domains and can feed that into the design of the overall architecture. So we're going to get into all of these things. It's going to sound like I'm talking about one person that does everything, but oftentimes people specialise in the objectives of the business architecture phase, which is to develop the target business architecture. That's ultimately the goal: to develop a target business architecture and to identify the candidate roadmap components. The roadmap is the layout of what you're going to implement and how you'll approach those two objectives. One is that business architecture is the foundation on which the other domains are built on.This is why we're doing business first. You can't really do a good technical or application architecture without understanding what the business wants and why the business wants it. So your approach is going to be to develop a baseline, bottom-up architecture description of the business architecture and then use business modeling, which is activities and use cases, to model the architecture. You may have to find models from other sources. So if you're in the banking sector,there are banking groups that provide businessmodels for banking, et cetera. The inputs, again, are skimmed because they are common inputs across all the phases. These are going to be the outputs of the preliminary work in Phase A. You've got them on screen here. There are lots of them. So the steps—this is the key here—of the business architecture Step one: select the reference models, viewpoints, and tools. Okay? So when you're sitting down to do your business architecture, you're not sitting down on a blank piece of paper. You're going to get the models that already exist. You may go into the architecture repository and grab some business models that already exist. You may go to the industry groups that have business models that are related to your industry, etc. Step two is to develop your baseline business architecture. Again, if this is a bottom-up approach, you're going to go through your organisation and document the business processes, follow people, and talk to them. What is it that you do? Why do you do this? Why do you do that? How do you do that? Some of these documents may exist. You may live in a nice world where some of these documents exist, and it's just a case of validating that. Develop the target business architecture. So when we went through the vision phase, we addressed people's problems. We came up with a candidate list of potential problems that we need to be solving here and that made up our vision and our high-level architecture. And so now we need to get into the final version 10 development of the target architecture. How is the business going to look once we've done all of these implementations? Step four is the gap analysis. The differences between the baseline and the target are the gaps. And so maybe you will find that business isn't going to change radically. That means a lot of the changes you're going to end up having are technical changes. But from the business user's point of view, they may not see a lot of difference. Maybe the financial guy will think that you're saving tonnes of money, but basically, the gaps might be small or they might be large. The roadmap components, once you've pulled stuff out of the gap analysis, you put them on a roadmap. You start saying, "Okay, we're going to be doing this in three months, this in six months, and this in twelve months." You start laying out in a row what you're doing when resolving impacts. So when you are doing this work, sometimes you're going to have an impact on some other team that's outside of your scope. Okay, so maybe you need data from another department, but that department is not part of your design. But you need to go to them and say, "Listen, I need to hook into your API." I know it exists, but we need to do this. You need to mitigate those impacts. Or maybe there's a project in the works; someone is creating or developing something, and you've already decided that it's not the best way to proceed. I've been part of that, where projects get cancelled after going on for a while and getting cancelled because they're no longer business needed.So, if you want to make an impact on others, this is the place to do it. Step seven, formal stakeholder review That's basically self evident.You go in there, present your solution, and you get approval. Then you're going to come back with some feedback, and you're going to revise your requirements based on that. Step eight is to finalise everything—all of the documentation—and make sure you've justified all of your decisions. Step Nine is the business architecture section of the architecture definition that documents the outputs, so anything that you've had to change along the way Phase A deliverables: your draught definition and requirements The architecture components of your roadmap on screen are a whole host of business artifacts, which are lists, which are catalogs, matrices, and diagrams. Put some keywords at the bottom here that will help you identify, when you're looking at an artifact, which phase it belongs to, because that could be important. So if you see the word business in the artefact name, that's a clue. Product, service, organization, role, and location—those are business things. You're not talking about applications; you're not talking about technology, networks, or things like that. You're talking about business products and services. Your Assignment now that we've gone through Phase Bin this deliver of detail, when you go tochapter eight, things will make a lot more sense. If you wish, you can go check out the business principles that are part of Chapter 23. This is an optional assignment, and if you really want to get more detailed, I've just created Section Eleven of this course, which will go through each of those steps in a lot more detail. So switch over to Section Eleven if you really want to dive deep into the depths of Phase B. Let's now talk about phase C, which is the information systems architecture covering data and application in the next lesson.

3. Phase C: Information Systems Architecture, Data

Okay. In this lesson, we're going to talk about Phase C, which actually comprises both data and application architectures. In this lesson, we're going to talk about the data architecture. To remind you, the phase sits at the 03:00 position of the AD cycle. This covers both DNA and BDAT. The data and application phases are actually done separately, even though they are covered by the same phase. You develop your baseline and target data architecture. Your baseline and target application architecture identify the gaps between the baseline and target of your approach. Now, in general, for Phase C, the point to keep in mind is that both the data and applications can be worked on in either order or in parallel. You could have both things going on at the same time, filling out different parts of this documentation. the information systems architecture. The objective of the course is to develop the target architecture and identify the candidate rollback components. This is the same style of objective as phase B, as you'll remember. Now, I did say we were going to get into the data architecture specifically in this video. So we're going to get the target data architecture created, and we're going to identify the architecture rulemack components as well. So approach number one is to understand and address any data management issues When you're managing data, the data has its own unique challenges. This is a lot of times hugeasset of the corporation and undervalued asset. Can you imagine if you were someone like Amazon.com? and one day you come in, you've lost your database, it's corrupt, and you find out your backup process hasn't been working for months. So the last backup you have is from three months ago. That would be an absolute disaster. The stock would be annihilated; the company would be in super big trouble. It would take a year to recover from that, if you could ever recover. So the data asset is hugely important in a lot of businesses, and so you need to understand the issues around that. any data migration issues. If you're going to be moving solutions from one type of platform to another, moving large quantities of data around securely is a huge concern. Data Governance So again, we've talked about backup security and making sure that you've got the right level of protection for your data. The problem with a lot of these companies that get hacked is they've got some random account from several years ago from an employee that no longer works there or a vendor that had access to systems they didn't require or the vendor security wasn't as rigorous as the company security, et cetera. The architecture repository: are there any existing data standards that can be borrowed? Different industries have standards. The education industry has what's called the SIF standard, and retail stores have what's called Arts. There are data standards, depending on the industry. Again, with the inputs, I'm going to skim through them because they are the outputs of the preliminary phase A. Phase B, some of the Towaf stuff, is not on the test, and it's pretty self explanatory.Everything that you've done to this point becomes an input, essentially. The steps. Again, this is going to follow the business Phase B phase very closely. Select your reference models, viewpoints, and tools. Are there any reference models in your architecture repository that can help you with this data definition that you're trying to come up with? So develop your baseline data architecture. Fortunately, with data architecture, most companies are in pretty good shape with those definitions. Okay. The tools themselves, like the database servers, lend themselves to extracting the layout of the databases, the number of databases, the roles and responsibilities, and the security around that fairly easily. So, hopefully, developing your baseline data architecture will not be too difficult for you. Now. The target architecture If you are planning to make major technical changes to the designs of your systems, then yes, you may have to spend some time saying, "Well, let's move ourselves into a software as a service model or service-oriented architecture model." We're going to put services in front of all of our data so that applications can access data as they need it, since they're authenticated too. So you may come up with a whole new plan for the way data is managed and shared within your organization. Once you've got your target and your baseline, you perform the gap analysis, extract those differences, put those differences on a road map, and resolve any impacts across your company. So again, if somebody is working on something else and, as they're working on it, it impacts you, you have to go out and figure those things out. If something you're doing is impacting someone else, figure that out. If you have ideas for, say, turning your data into a service and making it available to everyone, you might want to go to different departments and say, "Listen, we're going to do this; maybe this can become a company-wide thing." Step Seven is the formal stakeholder review. Again, you go in there with your plans and pitch them to the stakeholders, especially the people relating to business and technology who are most interested in data. You take their feedback, and you go and apply their feedback. Finally, you get their approval. You can finalise your data architecture, document everything, explain the reasons for certain decisions, and create the data section of the architecture definition. The outputs. These are the outputs of the data phase. the data definition document. Version one is a finalised version. The requirements, the gap analysis, anything that goes onto a roadmap The artefacts, thankfully, are easy to determine because every artefact uses the word "data." So if you see the contextual data diagram, you know that's part of the data phase. Your Assignments Now that we've gone through the information systems architecture, you can go check out chapter nine. It's pretty light because there are no steps relating to the information systems architecture. The steps exist in chapter ten, which is the data architecture. Hopefully, after going through this video, you'll be able to review that, and it will make a bit more sense. The data principles live in Chapter 23. Again, this is optional. It's up to you if you want to investigate that more. And I've just created section twelve of this course with brand new content that goes through the data architecture phase C in more detail. That is currently called sacred. Section Twelve is new and was added in June of 2015. So go there and check that out if you want more detail on that. Coming up next, we'll get to the other side of that coin, the application architecture part of FaceC. So come back for that.

4. Phase C: Information Systems Architecture, Application

Alright, we're moving ahead. We are on the application architecture section of Phase C of TOGAF nine one eight M. We have not moved off of Phase C. So this is the same as the last section. The objectives for application architecture are always to develop the target application architecture based on the business goals and identify the architecture roadmap components relating to application architecture. There's only one approach for this. The architecture repository can contain models that already exist for the application architecture. Are there existing models that can be adopted? The telecommunications industry has what's called the TMF Telemanagement Forum. That's an application architecture model. The triple IRM, which is part of the TOGAF spec. the open groups. Triple IRM can also be adopted. That's more of a service model. Again, scanning through the inputs, they are the outputs of previous phases, like preliminary phase A and phase B, selecting reference models. So we go to the architecture repository and see what already exists for application architecture. If we've gone through the adm cycle a few times, you might already have everything you need in the architecture repository. If you haven't, there might be almost nothing there, and you're going to have to create these. So then you develop the baseline application architecture description. You can do this "bottom down, bottom up," which means you go out, you find the applications that exist in your organization, you go to each of the business units, and you document an inventory. All of their applications, who uses them, what theydo, how they connect to each other, the relationships. Now you have developed a target application architecture based on your vision and what you know you want to get this company to move towards. Now this might be what a lot of people think about when it comes to architecture. It's thinking about software and off-the-shelf systems off the shelf.Develop your own customization by talking to B. This is the type of architecture that a lot of people think of when they think of that architecture. They don't think of business design, architecture, or that technical stuff underneath, where there's the gap analysis. Of course, once you've got the baseline and the target, you're going to pull out all of the differences. Chances are, in the application domain, there's going to be lots of them, because that's the main way that businesses get value from the applications that they use. The gaps, or things you've identified as gaps, are added to a roadmap, and then you must go and resolve the impacts. What other application development is underway? Very infrequently. Most rarely, the company stops doing any development work while you're off doing architecture. So projects are always going on. Something needs to change. There's an upgrade project going on. Okay, we're getting ready for the coming holiday season. These go on. And then you need to figure out what they're doing and pull them back into your designs. Step Seven is the stakeholder review. So again, you go in there, present your application architecture, take their feedback, refine it, and finally get their approval. You're going to finalise all the documentation. You're going to justify the business building blocks that you've chosen, the solution building blocks, etc for.And you're going to create the Application Architecture sections of the Architecture and Definition document for the outputs. So you're going to have the baseline target of the architecture definition document the requirements. You're going to have application architecture components on your roadmap. The artefacts again: there are lots of them. Luckily, they do use application-limited terms like application interface and software. Your assignment, now that you've gone through this, should make a lot more sense after reading Chapter 11 of the TogaSpec. It's a lot easier to read. You can skim through that. As long as you're understanding what I'm saying, you should be able to understand what's in that chapter. The application principles are listed in Chapter 23. That's optional. Or I created a brand new Section 13, which goes into each of the steps of the application architecture phase in more detail. Let's keep this party going, and we're going to get into Phase D technology architecture. Next.

Go to testing centre with ease on our mind when you use The Open Group TOGAF OG0-091 vce exam dumps, practice test questions and answers. The Open Group OG0-091 TOGAF 9 Part 1 certification practice test questions and answers, study guide, exam dumps and video training course in vce format to help you study with ease. Prepare with confidence and study using The Open Group TOGAF OG0-091 exam dumps & practice test questions and answers vce from ExamCollection.