- From: Tim Berners-Lee <timbl@w3.org>
- Date: Sat, 21 Dec 2024 07:03:53 +0000
- To: Sarven Capadisli <info@csarven.ca>
- Cc: public-lws-wg@w3.org
Looking at application domain use cases, then it is important to specify the persona as patient, as a doctor (sometimes very generally, sometimes quite specifically, depending on the use case - patient suffering froma long term disease - paient in a clinical trial - main doctor - Specialist doctor - next of kin - hospital administrator These personas are we talk of as classes but in fact they are ROLES in a system, thinking the as classes may be misleading. On other domains they - financial advisor - coach - parent - teacher - in loco parentis etc Tim > On Dec 17, 2024, at 16:48, Sarven Capadisli <info@csarven.ca> wrote: > > Hi all, > > I've noticed that a significant number of use cases are framed as "as a user" with little to no detail about the actors involved. > > I find "user" to be overly vague for use cases or at the very least too obvious given common alternative is software (or hardware, cyborgs, etc.). > > I suggest we take greater care in describing the actors so that the requirements derived from the use cases more accurately reflect what is actually needed, for whom, and in what context. > > The focus should be on actor diversity with variations in needs, capabilities, and aspirations. > > -Sarven > https://csarven.ca/#i >
Received on Saturday, 21 December 2024 07:04:06 UTC