Skip to main content

2. The four causes



Aristotle's was often thinking which were the four causes of... anything: the material, formal, efficient, and final cause. To my own risk, I'll try to apply these causes, to the very limited scope of software requirements.

Final cause:   to build a software that works well and is efficiently used by customers.

Efficient cause: it's us, we want build software for our customers.

Material cause:  the pieces of paper we write requirements on.

Formal cause: well. I still have to think about this one.

Aristotle used the word aition, "cause".
He meant an explanation that accounts for something: "x is the aition of y" means "x explains y".

Comments

Popular posts from this blog

1. What is a Requirement ?

The word Requirement comes from the latin word Requisitum , that comes from requirĕre  «to demand, to require, to call for» and quaerĕre  «to ask, to strive for, to require». Never forget that asking a lot of questions is one of the key in understaning the real needs of your customers.

Questiologie for complex requirements - Frédéric Falisse

I just watched this TedX video of Frédéric Falisse explaining his Questiolgie and found it very interesting. The video is in french but it has English captions. I think it could be greatly useful while gathering elaborate or difficult requirements. As far as I understand it, he proposes four tips for asking good questions 1. Change of mental posture  If the interviewed is already an actor , remove him from the action and ask for a feeling . Do not ask "why do you get stuck" but "what do you feel when you feel stuck ? If instead he starts with an emotion, ask about an action. 2. Double the verb Like in the phrase "What are you afraid of when you are afraid of losing control?" 3. Reconcile Use right and left hands  "When you fail a test ... Makes you lose control over future choices" 4. Project in the future i.e. What will happen if you fail the test? Here's his main site  https://www.questiologie.fr/ Have a great day!