Institute For Enterprise Architecture Developments OBASHI The OBASHI methodology provides a framework and method for capturing, illustrating and modeling the relationships, dependencies and dataflows between business and Information technology (IT) assets and resources in a business context. A Business and IT (B&IT) diagram built using the OBASHI Framework. It is a formal and structured way of communicating the logical and physical relationships and dependencies between IT assets and resources (Ownership, Business Processes, Applications, Systems, Hardware, and Infrastructure) to define the business services of a modern enterprise. The name OBASHI is a licensed trademark of OBASHI Ltd. Core Principle[edit] OBASHI is based around a core principle: that IT exists for one reason, namely, to manage the flow of data between business assets. Business resources (which include people) and IT assets are either providers of data, consumers of data or provide the conduit through which the data can flow. The Origins of OBASHI[edit] Characteristics[edit]
IT Strategies from Oracle IT Strategies from Oracle is an authorized library of guidelines and reference architectures that will help you better plan, execute, and manage your enterprise architecture and IT initiatives. The IT Strategies from Oracle library offers two types of best practice documents: practitioner guides containing pragmatic advice and approaches, and reference architectures containing the proven technology patterns to jump-start your initiative. Learn more: The IT Strategies from Oracle library can help you establish a reliable set of principles and standards to guide your use of Oracle technology. Overview documents providing an introduction to all the resources available in the library and best practices maturity models Oracle Reference Architectures covering the application infrastructure foundation, management and monitoring, security, software engineering, service-oriented integration, service orientation, user interaction, engineered systems, and a master glossary.
How to manage requirements within the Enterprise Architecture using the TOGAF® and SABSA® frameworks By Pascal de Koning, KPN You want to put your company’s business strategy into action. What’s the best way to accomplish this? This can be done in a structured manner by using an Enterprise Architecture Framework like TOGAF®. As the figure shows, Requirements Management plays a central role in the architecture work in the TOGAF® methodology. Unfortunately, TOGAF® does not offer guidance on Requirements Management. Business Attribute Profiling is a requirements engineering technique that translates business goals and drivers into requirements (see figure 2). Executive communication in non-ICT termsGrouping and structuring of requirements, keeping oversightTraceability mapping between business drivers, requirements and capabilities The BAP process decomposes the business goal into its core elements. TOGAF® is a registered trademark of The Open Group. Pascal de Koning MSc CISSP is a Senior Business Consultant with KPN Trusted Services, where he leads the security consulting practice.
Home - Enterprise Integration Patterns NASA Nebula | Nurturing Innovation with Nebula I’ve been with NASA for over 25 years and Nebula is by far the most dynamic project I’ve worked on to date. Truly inspired, Nebula has many lessons to share with others on how a small group can drive innovation within a larger, highly structured organization. I’m glad to be a part of Team Nebula so that can I experience daily the energy that pumps through this project team. Innovation doesn’t always come easily… especially in a large federal government agency. How does Nebula do it? Fortunately, Nebula has become a magnet for IT talent. The use of leading edge communications brings us together as a team. Shoot me an email at nebula-inquiries@lists.nasa.gov
TOGAF exam prep Outside-In Business Architecture with VDML Information technology has enabled new approaches to business architecture. It has changed relationships with business partners and customers, enabled business operations to be globally distributed, and reduced the time and cost of business operations. However, optimal business design can no longer be achieved by simply automating the existing business design—an inside-out approach. VDML is designed as a business design language for business people. The solid boxes represent viewpoints that are currently addressed in the draft specification, and the dashed boxes represent viewpoints that are still under consideration. Core Concepts In the following paragraphs I will outline the core concepts of VDML that support this integrated business modeling. Values and value propositions A value is a characteristic of a product or service that is desired by a recipient. The value contribution metrics are aggregated in a value proposition. Collaborations, organizations, activities and roles e3Value
CloudStandards TOGAF cloud computing
Right, I like TOGAF much better. by clemense May 19