13 WORKING WITH SYSTEMS ANALYSIS ARTEFACTS
‘What I hate about writing is the paperwork.’
– Peter De Vries
Although a working application is usually the end goal of developing a system, many different artefacts are created as by-products of the process, mostly in the form of documentation. Developers often dislike creating documentation, but many artefacts will naturally be created as part of the development flow. Common examples include class diagrams (schemas), project plans, business cases, risk assessments and user requirements.
In this chapter we’ll examine two key examples of system analysis artefacts – the use case and user stories – and how these may be employed in the workplace.
USE CASES
A use case is essentially a list of steps ...
Get Software Development in Practice now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
