From d4b9f96378547a8b4ea2383c17a288d7eb6a7510 Mon Sep 17 00:00:00 2001 From: William Sandner Date: Tue, 14 Aug 2018 20:31:13 +0200 Subject: [PATCH] GFM changes --- Glossary-Standard-Terms.md | 161 +++++++++++++++++++++++++++++++++---- Glossary.md | 40 ++------- 2 files changed, 155 insertions(+), 46 deletions(-) diff --git a/Glossary-Standard-Terms.md b/Glossary-Standard-Terms.md index ed8c495..b461386 100644 --- a/Glossary-Standard-Terms.md +++ b/Glossary-Standard-Terms.md @@ -10,14 +10,14 @@ helps keep other documents more concise and easy to edit. Check the [ReadySET glossary](http://readyset.tigris.org/templates/glossary-std.html) for updates. -Jump to: [General](#general_terms) | -[Computer science & technology](#computer_science_and_technology_terms) | -[Process](#process_terms) | -[Software development tools](#development_tool_terms) | -[Requirements](#requirements_terms) | [Design](#design_terms) | -[Design goals terms](#design_goals_terms) | [QA terms](#qa_terms) | -[QA goals terms](#qa_goals_terms) | [Additional terms](#additional_standard_terms)| -[Project terms](Glossary#glossary) +Jump to: [General](#general-terms) | +[Computer science & technology](#computer-science-and-technology-terms) | +[Process](#process-terms) | +[Software development tools](#development-tool-terms) | +[Requirements](#requirements-terms) | [Design](#design-terms) | +[Design goals terms](#design-goals-terms) | [QA terms](#qa-terms) | +[QA goals terms](#qa-goals-terms) | [Additional terms](#additional-standard-terms)| +[Project terms](Glossary) ### General Terms @@ -176,13 +176,146 @@ 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 -many different ways as part of many different use cases. +details on all aspects of the feature. One feature may be used in + + +
+
+ + + + + + + + + + + + + +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. diff --git a/Glossary.md b/Glossary.md index bfa611c..5c3dda2 100644 --- a/Glossary.md +++ b/Glossary.md @@ -1,27 +1,3 @@ - - - - - - ReadySet Markdown - - - - - - Overview - Project Plan - Workflows - Current - - - - -<!-- Markdown content here --> - -# Glossary ---- - **Process impact:** This file as a dictionary of terms defined as they are used during the project. Writing out the definitions of terms and acronyms here helps keep other documents more concise and precise. A @@ -32,7 +8,7 @@ Jump to: [A](#a) | [B](#b) | [C](#c) | [D](#d) | [E](#e) | [F](#f) | [G](#g) | [H](#g) | [I](#i) | [J](#j) | [K](#k) | [L](#l) | [M](#m) | [N](#n) | [O](#o) | [P](#p) | [Q](#q) | [R](#r) | [S](#s) | [T](#t) | [U](#u) | [V](#v) | [W](#w) | [X](#x) | [Y](#y) | [Z](#z) | -[Standard terms](Glossary-Standard-Terms#standard_terms) +[Standard terms](Glossary-Standard-Terms) ### Project-specific Terms @@ -115,13 +91,13 @@ credits needed? #### T -##### ::Term1 -::Definition1 - -##### ::Term2 -- ::Definition2a -- ::Definition2b - +t +t +t +t +t +t +t ##### ::Term3 ::Definition3