#Requirements
5 notas · última:
A Note on Essential Complexity
The post argues that software engineers should think beyond accidental versus essential complexity. By questioning requirements and shaping users and organizations, they can sometimes reduce complexity by changing the problem itself.
Understanding Pure Domain Modelling
Argues that domain experts default to describing their existing system rather than the real domain, and proposes asking 'what would you do without a system?' to get past that bias.
The Hardest thing about Engineering is Requirements
The post argues that requirements are hard because engineering is really a communication problem. It compares shalls, user stories, use cases, user cases, and rapid prototyping as ways to capture stakeholder intent.
6 Practical Agile Techniques You Can Start Using Today
The article argues for small Agile changes that improve speed, quality, and communication: deliver more often, involve testers in requirements, write user stories, use prototypes, and think about testing early.
It's Not A Bug, It's....
The page argues that a defect exists only when code differs from the requirements specification, and that many “defects” are really missing, incomplete, or inconsistent requirements that should be tracked as change requests.