Date: Fri, 29 Mar 2024 01:40:38 +0100 (CET) Message-ID: <582539415.17585.1711672838655@09e9d69a2016> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_17584_1344714300.1711672838655" ------=_Part_17584_1344714300.1711672838655 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
User Characters are the a= ctors of user stories. They include personas and extreme characters.
User characters help to visualize the users of a system. They are closel= y related to roles, but mode= l real or imagined users that may map to multiple roles.
The document type user character provides the following propert= ies:
Please note that only information about specific properties is provided = here. Common document property used by all document types are documented by= Document Propert= ies.
The type of the user character.
Type | Description |
---|---|
user role | A user that holds one or more roles. |
persona | An imaginary user with detailed background. |
extreme character | A very exaggerated persona to help to improve us= er stories. |
Select a type for the user with the User Character Type Macro.
The actor type defines how the user character is mainly acting with the =
system. The information is used to separate the primary (main) user charact=
ers ("Primary
") from those that are only used in stories that =
support the system, but not fulfil its main goal. If the user character car=
es for the system, it is called ''Secondary
'', if it provides =
additional functionality, it is called ''Supporting
''.
Add a reference to an image for a role or persona to. The URL to an imag= e may be a plain URL or a link that points to an image.
Typically the URL is used to fetch the image and render it using the Display Document Property As Image Macro.
The description of the user character.
Describe the background of the user character in some detail. Sketch out= some facts to visualize the context the character lives in. This may inclu= de some demographic information.
Since version 3.1.2.
List the needs you assume the user character has from a brainstorming se= ssion. This may lead to hypotheses that have to be worked on later.
Since version 3.1.2.
From a brainstorming session add possible solutions to the needs your pr= oduct may provide or be involved with. Again, these points may not to be ta= ken as granted, but used as a tool to visualize the character.
Since version 3.1.2.
User characters may be grouped in hierarchies.
These are internal notes that are usually not exported and only visible = to team members with write access.
But this is not a safe place to store sensible informat= ion. It is just a convenience for the reader to not be bothered with notes = stored here for the authors for later use. The security level is about supp= ressing the representation by a CSS style. Therefore consider this as a con= venience for the reader, not as a security tool.
The text of notes sections is also indexed.
For a document the references section contains pointers to resources tha= t prove the statements of the document.
Often these proofs are not easily distinguishable from further informati= on. In this case you may want to skip the reference section in favour for t= he resource list.
For further information please refer to References and Resources.
The resources section provides references to further information to the = topic of the document.
This may be information on the internet provided by the resource or info= rmation in the team's information systems. Anything the reader of the resou= rce might want to know, may be listed here.
For further information please refer to References and Resources.
User characters are based on = roles.
User characters are actors in user stories.