Skip to toolbar
KYC is primarily about decision making

April 26, 2017

Know Your Customer (KYC) is primarily about the decisions a financial institution needs to make about a (potential) customer. However, I have yet to find a definition online that focuses on decisions. Wikipedia’s definition focuses on the process, while Investopedia and The Free Dictionary place emphasis on the form that has to be completed. Although […]

Things aren’t the same just because you treat them the same

April 5, 2017

Several years ago a major software consultancy built a Pega solution for a client and within two years of deploying it, the client was having to rebuild it themselves. It’s not an uncommon scenario. The client brought me in to take a look at the business architecture underlying the original solution and that is where […]

Software delivery does not equal success

March 23, 2017

I’ve done work for many software delivery organisations and they all have one thing in common: they think delivery of software to the client is success. I beg to differ. Several years ago, one such organisation delivered a software solution to its client on time and within budget at a cost of roughly £15 million. […]

Data modelling as a BA technique is in decline

March 21, 2017

In my experience, very few business analysts produce data models. Of course my experience is that of one person across the whole IT industry, so my view is a thin slice through a very big cake. What’s more, my experience is limited to process-driven projects. I have no experience in, for example, Data Warehousing. By […]

The 12 Agile Principles Adapted to Business Architecture

January 11, 2017

You are probably familiar with the Agile Manifesto that was written in 2001 by several forward-thinking software developers. However, it is a manifesto for software development and, as you may have seen in a previous post, business architecture is about more than software requirements. Does that mean we cannot apply the 12 principles behind the […]

Documenting Strategic Goals

January 6, 2017

Most projects I’ve worked on have had a set of strategic goals that the project was supposed to realise. However, most people working on those projects could not say what the goals were or where they could be looked up. Even on projects where the goals were stated and available, they were not always clearly […]

I have a problem with user stories

December 2, 2016

I admit it. I have a problem with user stories. Not with the Actor/Narrative/Benefit syntax or the idea of adding acceptance criteria or the idea of valuing conversation over documentation. I love all that. I have a problem with the name “user” stories.

Decision models, user stories and acceptance criteria

December 1, 2016

Decision modelling dramatically changed how I view business rules. In a nutshell, business rules are not particularly useful on their own. For example, if the business has a rule that a person must be aged 18 or over in order to have an account, that does not give us the full picture. What decision is the business trying to make when taking into account a person’s age? What other data (fact types) does the business take into account when making that decision? At which points in which processes can that decision be made? What other decisions take into account a person’s age?

Business Architecture is About More Than Documenting Software Requirements

March 17, 2015

Many companies, whether those purchasing software or those developing it, don’t start analysis until the software development lifecycle begins. This results in software developers and testers being engaged before a vision of the business need has even been explored and it explains why so many projects stall because of unclear and incomplete requirements. Declan talks about how modelling business architecture is an essential activity before even choosing a solution technology.




Declan Chellar

Profile picture of Declan Chellar

@declanchellar

active 2 years, 11 months ago