Data Analysis & Modeling

Chaos! Stress! Everyday mess! Isn’t this an everyday situation for a business analyst? If not, either you’ve job satisfaction or you’re not being introduced to the real world of business analysis.

A person might possess great skills, however, (s)he might not be able to utilize skills without the right mix of tools and environment. A toolbox enables a person to implement the skills in the most efficient way. Possessing necessary tools is just the one part of it. Another is the knowledge to utilize the right tools at the right time to cater the solution and ensure timely committed delivery.

What are these tools? How do we map the usage of tools to the given circumstance? How can we efficiently utilize the tool? Does it depend on the solution or the approach?

It your responsibility to make sure that you understand what the impact of GDPR are going to be for the data that you work with. There is no doubt that this is going to shake things up in the data protection world for both organisations and individuals. We will publish another blog that will tell you what steps as a business analyst you need to make sure that you and your organisation do not breach GDPR regulations.

I don’t know how many articles I’ve read where the author states requirements should be “what” the user/client needs, not “how” to deliver the solution. They say “A requirement should never specify aspects of physical design, implementation decisions or system architecture”... In my humble opinion, every requirement, even the business level needs, goals and objectives, are just the start of a long march to a solution.

State Models include two RML Data models (State Tables and State Diagrams) that show the transition of an object through various states or statuses, including which transitions are valid and what triggers an object to transition state. A state is a short-form description of a stage in a data object’s life that influences the behavior of the system.

The end products of requirements development for a business analytics project will be similar to those for any other project—a set of business, user, functional, and nonfunctional requirements. Process flows, use cases, and user stories can reveal that someone needs to generate analytics results, and performance requirements describe how quickly they need results, but none of these uncovers the complex knowledge required to implement the system... An effective elicitation strategy for business analysts (BAs) is to drive requirements specification based on the decisions that stakeholders need to make to achieve their business objectives.

There are various schools of thought about how to define terms, some arising from professional terminologists and academia. But those approaches are often relatively arcane and not well-suited to everyday business practice.

Definitions with subtle IT or ‘data’ bias are an anathema to effective communication with business partners. Good business definitions are oriented to what words mean when used by real business people talking directly about real business things.

Opportunities abound for new and experienced analysts to advance their careers if they are willing to increase their knowledge of analytics, metrics, and Business Intelligence. In the meantime, following these five steps will help get you and your organization on your way to being a well-measured one.

Business analysts’ performance and how we could measure it appeared to be a hot topic of interest for the Business Analysis community.   “If you can’t measure it, you can’t manage it” (Peter Drucker) – this statement hides lots of questions for the Business Analysis managers, like what to measure, how to assess, quantifiable or qualifiable metrics to use? 

This article explores strategy mapping as discussed within Business Architecture Guild BIZBOK, and attempts to extend the discussion by defining a set of information and graphical principles that allows strategy to be represented graphically.

Data migration is typically the most forgotten or underestimated component of an IT project which is the process of making a copy of data and moving it from one system to another, preferably without disrupting or disabling active business processes. On some occasions, it is not easy to understand that a data migration is needed in the project and ...

Adoption of The Decision Model (TDM) is growing and includes major corporations, such as those in the financial industry. As a result, decision models based on TDM are operating in production worldwide on behalf of critical business transactions and some with huge transaction volumes.  This means there are organizations and people with several years of TDM experience. However, there are also people and organizations interested in TDM and contemplating how to get started. This article provides insights by which business analysts can plant the seed for TDM.

What is a data normalization? Normalization ensures that each attribute is assigned correctly to its proper entity. And that the attribute does not repeat within an entity and is fully dependent on its primary key and nothing but the key. Make sense? If not, let’s translate the gibberish into business language.

This is a complete example of a Business/Systems Analysis Model using UML and including: Use Cases, Activity Diagrams, Context Diagram, and more.

Of all the reasons for data quality problems, I find user interface design issues to be the most interesting. This may be because it is tied to the software requirements, and I have worked as a requirements analyst for a number of years.