Enterprise Analysis (BABOK KA)

Feb 07, 2021
7803 Views
3 Likes
0 Comments

The intention of this article is to identify and specify the artifacts listed in the BABOK. These artifacts are listed within the Outputs section of the BABOK tasks. Outputs are described by a paragraph of text within each task. In this article I attempted to expand on these descriptions by adding detail to their content.

It is assumed that each activity produces a tangible output[2] which is consistent with the layout of the BABOK. Those outputs are classed as artifacts with attributes. Each artifact’s attribute description is taken from the element description of the tasks that output that artifact. The BABOK element descriptions provide guidelines for activity that produces the attribute, without necessarily defining the information contained in the attribute.That information has been derived from the element description.

Artifacts are derived from the BABOK Output sections. Artifact attributes are derived from the BABOK Element sections. A useful addition to the BABOK might be examples or templates of the outputs.

Jan 10, 2021
7830 Views
10 Likes
0 Comments

Consider the situation where you are the business analyst who is planning project work according to the BABOK guidelines. The project manager wants to plan their time spent on business analysis activities. You produce a report of the BABOK that shows tasks that the project manager is expected to contribute to.

This article describes an analysis I performed of the Business Analysis Body Of Knowledge v3 (BABOK). The result of this analysis is a model contained in the Visual Paradigm modeling tool. This model captures 461 pages of the BABOK, from the Business Analysis Key Concepts chapter through to the end of the Techniques To Tasks Mapping chapter.

May 03, 2020
8218 Views
42 Likes
0 Comments
While the IIBA-AAC exam is not the most challenging exam that I've ever taken, it does require you to have a very specific type of understanding of the Agile Extension to the BABOK Guide. Though it's not a requirement, I recommend taking an exam prep course to increase your chances of passing the exam. Those who did not initially pass the exam reported that they underestimated the exam and figured that they would be able to rely on their agile experience to pass the exam. WRONG!! In fact, the exam doesn't focus much on the details of agile ceremonies or daily activities, but more so on the general principles of agile business analysis.
Apr 13, 2020
6363 Views
25 Likes
0 Comments

This final article in the Requirements in Context series discusses detailed requirements for a fully automated business activity. ‘Fully automated’ means that the business information system (BIS) is expected to perform the activity from start to finish without user involvement. A simple example is the system automatically posting a monthly fee against customer accounts. A more complex example is the system utilizing customer-specific pricing details to determine the amount charged for a purchase made by a customer.

10599 Views
49 Likes
0 Comments

Visual analysis models provide a powerful set of tools that let business analysts depict system information at various levels of abstraction. These models serve as an aid to understanding, as well as an aid to communicating. Alas, I fear that modeling is somewhat of a neglected practice. I believe modeling is an essential skill every BA should master. Here’s why.

Mar 01, 2020
6261 Views
28 Likes
0 Comments

Has society become so unimaginative in the products, services, organisations and societies that we choose to create? Have we started giving up on ‘inspiration’ and ‘excitement’ as values with the way in which we create schools, workplaces and organizational cultures? My personal belief is that Business Analysts are ideally and uniquely positioned by make an incredible and positive difference in the world.

9646 Views
25 Likes
0 Comments

If we look at the previously proposed process end to end, it starts with the customer journey. The journey is mapped to the internal business processes, systems, and data sources. For both the customer facing and internal parts of the journey user stories are created to document the gaps between the as-is and to-be states - effectively form the backlog for the change. For each story, acceptance criteria are prepared in a way that enforces the expected behaviour in the system. Ideally, those should be the scenarios that are likely to appear on the real life journeys and not the hypothetical future scenarios. These scenarios when implemented and tested feed back to the journey and underlying layers changing them as the new functionality is introduced.

16169 Views
38 Likes
0 Comments

Capability-based planning is a growing practice in the field of enterprise architecture. Its success is due to the fact that it provides actual value to practitioners and the organizations that employs them. Indeed, capability-based planning helps in a number of ways, from providing a clear understanding of existing capabilities to promoting effective Business-IT alignment. Considering these benefits, we thought it useful to address this practice and bring some clarity to the subject for the benefit of all who might not yet have a good handle on the topic.

10947 Views
19 Likes
0 Comments

This article describes the process of the strategic enterprise analysis utilizing text and tables. In the past 5 years, things have changed, and I have gained new insight and most important learned new aspects. As a result, this article expands previous material to include...

18150 Views
28 Likes
0 Comments

Personally, I believe the best approach to enterprise risk and security management (ERSM) is to rely on several open standards, most notably the ArchiMate standard for enterprise architecture modeling, as well as the Open FAIR standard for information risk management. More details are described in The Open Group’s white paper on modeling enterprise risk management and security.
12701 Views
33 Likes
0 Comments

If you have some experience in modeling real-life, full-size architectures for large-scale organizations – preferably in the ArchiMate language, of course – you have likely come across the challenge of organizing your models in logical and manageable ways. In the following pages, we’re going to share our top 6 ways to organize your architecture models. These methods should help you keep your models neat and tidy, while also supporting better outcomes for your strategic initiatives. Let’s see what they are.

16137 Views
55 Likes
0 Comments
Strategists, architects, process experts, software developers, data managers and other professionals involved in changing the enterprise often put substantial effort in creating all kinds of useful models of their designs. In many cases, such business models, enterprise architecture models, business process models, software models, or data models are only used to specify some design, i.e. to describe what should be built. 
But there is much more value to be had from these models, by using powerful analysis techniques to elicit new insights. In the following pages I will cover 7 of these analyses, discussing the business outcomes you can achieve with their help.
9849 Views
56 Likes
3 Comments

One of my former business analysts on the team asked me this question recently; ‘I am really over being a BA. How do I move into strategy?’ I got to the realization that she was associating ‘strategy’ with a job title which consists of certain tasks.  In my view, it appears as if for some business analysts, before becoming strategic, they have to be given a title ‘Strategic Business Analyst’. This I believe is the mystery that surrounds ‘strategy’ and ‘strategic thinking’, making it appear as a destination to reach, at some point.

16511 Views
80 Likes
0 Comments
In a classic business analyst universe, requirements are the soul of all the work a business analyst does. If a business analyst fails to identify and translate the right requirements, they’re out of a job. This is the reason why a successful business analyst is always good at requirements handling/management process. What makes requirements...
5285 Views
17 Likes
0 Comments

There are a small number of core concepts that can be said to embody the essence of an enterprise. This article asserts that one such concept is the business algorithm, the unique combination of business logic, algebra, and rules that is used by the enterprise to convert real world data and events into useful outcomes that benefit all stakeholders – giving rise to happy customers, prosperous proprietors, and fulfilled staff! ... The business algorithm is a unique and fundamentally important concept that no enterprise can function without. There are other aspects of the enterprise like brand or culture that may also claim to be ‘of the essence’, but the business algorithm is the only such concept that has a formal existence inside computer systems. The business algorithm is like the soul of the enterprise, uniquely defining the enterprise and giving it life via its systems. As such it has a unique claim to relevance as a first-order systems requirements artifact.

Page 1 of 5First   Previous   [1]  2  3  4  5  Next   Last   

 



 

Copyright 2006-2021 by Modern Analyst Media LLC