From 488297b04bd03296077e5e970bdfda56f22903e5 Mon Sep 17 00:00:00 2001 From: William Sandner Date: Tue, 14 Aug 2018 20:36:54 +0200 Subject: [PATCH] GFM changes --- Glossary-Standard-Terms.md | 144 ++----------------------------------- 1 file changed, 6 insertions(+), 138 deletions(-) diff --git a/Glossary-Standard-Terms.md b/Glossary-Standard-Terms.md index b461386..cfc6dbc 100644 --- a/Glossary-Standard-Terms.md +++ b/Glossary-Standard-Terms.md @@ -176,146 +176,14 @@ A feature specification focuses on one feature of a software product and completely describes how that feature can be used. It includes a brief description of the purpose of the feature, the input and output, and any constraints. Individual bullet items give precise -details on all aspects of the feature. One feature may be used in - +details on all aspects of the feature. One feature may be used in +many different ways as part of many different use cases. -
-
- - - - - - - - - - - - - -many different ways as part of many different use cases. - - -
-
- - - - - - - - - - - - - - - - -
-
- - - - - - - - - - - - - -#### Use case - - -
-
- - - - - - - - - - - - - -The main part of a use case is a set of steps that give an example - - -
-
- - - - - - - - - - - - - -of how an [actor](#actor) can use the product to succeed at - - -
-
- - - - - - - - - - - - - -a goal. These steps are called the "Main success scenario", and they - - -
-
- - - - - - - - - - - - +#### Use case +The main part of a use case is a set of steps that give an example +of how an [actor](#actor) can use the product to succeed at +a goal. These steps are called the "Main success scenario", and they include both user intentions and system responses. One use case may show how the actor uses several features to accomplish a goal.