GFM changes

This commit is contained in:
William Sandner 2018-08-14 20:31:13 +02:00
parent 361c83e2c6
commit d4b9f96378
2 changed files with 155 additions and 46 deletions

View File

@ -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 [ReadySET glossary](http://readyset.tigris.org/templates/glossary-std.html) for
updates. updates.
Jump to: [General](#general_terms) | Jump to: [General](#general-terms) |
[Computer science & technology](#computer_science_and_technology_terms) | [Computer science & technology](#computer-science-and-technology-terms) |
[Process](#process_terms) | [Process](#process-terms) |
[Software development tools](#development_tool_terms) | [Software development tools](#development-tool-terms) |
[Requirements](#requirements_terms) | [Design](#design_terms) | [Requirements](#requirements-terms) | [Design](#design-terms) |
[Design goals terms](#design_goals_terms) | [QA terms](#qa_terms) | [Design goals terms](#design-goals-terms) | [QA terms](#qa-terms) |
[QA goals terms](#qa_goals_terms) | [Additional terms](#additional_standard_terms)| [QA goals terms](#qa-goals-terms) | [Additional terms](#additional-standard-terms)|
[Project terms](Glossary#glossary) [Project terms](Glossary)
### General Terms ### 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 and completely describes how that feature can be used. It includes a
brief description of the purpose of the feature, the input and brief description of the purpose of the feature, the input and
output, and any constraints. Individual bullet items give precise 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<!-- End Markdown content -->
many different ways as part of many different use cases. </xmp>
<div w3-include-html="_words-of-wisdom.html"></div>
<div w3-include-html="_footer.html"></div>
<script>
w3IncludeHTML();
</script>
<script src="http://strapdownjs.com/v/0.2/strapdown.js"></script>
<!-- Include it AFTER strapdown -->
<script src="assets/strapdown/strapdown-topbar.min.js"></script>
<!-- Include it AFTER EVERYTHING -->
<script src="assets/logo.js"></script>
<script src="assets/themeswitcher.js"></script>
</body>
</html>
many different ways as part of many different use cases.<!-- End Markdown content -->
</xmp>
<div w3-include-html="_words-of-wisdom.html"></div>
<div w3-include-html="_footer.html"></div>
<script>
w3IncludeHTML();
</script>
<script src="http://strapdownjs.com/v/0.2/strapdown.js"></script>
<!-- Include it AFTER strapdown -->
<script src="assets/strapdown/strapdown-topbar.min.js"></script>
<!-- Include it AFTER EVERYTHING -->
<script src="assets/logo.js"></script>
<script src="assets/themeswitcher.js"></script>
</body>
</html>
<!-- End Markdown content -->
</xmp>
<div w3-include-html="_words-of-wisdom.html"></div>
<div w3-include-html="_footer.html"></div>
<script>
w3IncludeHTML();
</script>
<script src="http://strapdownjs.com/v/0.2/strapdown.js"></script>
<!-- Include it AFTER strapdown -->
<script src="assets/strapdown/strapdown-topbar.min.js"></script>
<!-- Include it AFTER EVERYTHING -->
<script src="assets/logo.js"></script>
<script src="assets/themeswitcher.js"></script>
</body>
</html>
#### Use case<!-- End Markdown content -->
</xmp>
<div w3-include-html="_words-of-wisdom.html"></div>
<div w3-include-html="_footer.html"></div>
<script>
w3IncludeHTML();
</script>
<script src="http://strapdownjs.com/v/0.2/strapdown.js"></script>
<!-- Include it AFTER strapdown -->
<script src="assets/strapdown/strapdown-topbar.min.js"></script>
<!-- Include it AFTER EVERYTHING -->
<script src="assets/logo.js"></script>
<script src="assets/themeswitcher.js"></script>
</body>
</html>
The main part of a use case is a set of steps that give an example<!-- End Markdown content -->
</xmp>
<div w3-include-html="_words-of-wisdom.html"></div>
<div w3-include-html="_footer.html"></div>
<script>
w3IncludeHTML();
</script>
<script src="http://strapdownjs.com/v/0.2/strapdown.js"></script>
<!-- Include it AFTER strapdown -->
<script src="assets/strapdown/strapdown-topbar.min.js"></script>
<!-- Include it AFTER EVERYTHING -->
<script src="assets/logo.js"></script>
<script src="assets/themeswitcher.js"></script>
</body>
</html>
of how an [actor](#actor) can use the product to succeed at<!-- End Markdown content -->
</xmp>
<div w3-include-html="_words-of-wisdom.html"></div>
<div w3-include-html="_footer.html"></div>
<script>
w3IncludeHTML();
</script>
<script src="http://strapdownjs.com/v/0.2/strapdown.js"></script>
<!-- Include it AFTER strapdown -->
<script src="assets/strapdown/strapdown-topbar.min.js"></script>
<!-- Include it AFTER EVERYTHING -->
<script src="assets/logo.js"></script>
<script src="assets/themeswitcher.js"></script>
</body>
</html>
a goal. These steps are called the "Main success scenario", and they<!-- End Markdown content -->
</xmp>
<div w3-include-html="_words-of-wisdom.html"></div>
<div w3-include-html="_footer.html"></div>
<script>
w3IncludeHTML();
</script>
<script src="http://strapdownjs.com/v/0.2/strapdown.js"></script>
<!-- Include it AFTER strapdown -->
<script src="assets/strapdown/strapdown-topbar.min.js"></script>
<!-- Include it AFTER EVERYTHING -->
<script src="assets/logo.js"></script>
<script src="assets/themeswitcher.js"></script>
</body>
</html>
#### 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 include both user intentions and system responses. One use case may
show how the actor uses several features to accomplish a goal. show how the actor uses several features to accomplish a goal.

View File

@ -1,27 +1,3 @@
<!DOCTYPE html>
<html>
<head>
<meta charset="utf-8"/>
<link type="image/png" href="assets/logo.png" rel="icon">
<title>ReadySet Markdown</title>
</head>
<script src="https://www.w3schools.com/lib/w3data.js"></script>
<body>
<topbar style="display:none;">
<item><a href="index.html">Overview</a></item>
<item><a href="plan.html">Project Plan</a></item>
<item><a href="index-all.html">Workflows</a></item>
<menu name="Themes"><item><a id="settheme"><b>Current</b></a></item></menu>
<toc></toc>
</topbar>
<xmp theme="readable" style="display:none;">
<!-- Markdown content here -->
# Glossary
---
**Process impact:** This file as a dictionary of terms defined as they **Process impact:** This file as a dictionary of terms defined as they
are used during the project. Writing out the definitions of terms and are used during the project. Writing out the definitions of terms and
acronyms here helps keep other documents more concise and precise. A 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) | [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) | [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) | [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 ### Project-specific Terms
@ -115,13 +91,13 @@ credits needed?
#### T #### T
##### ::Term1 t
::Definition1 t
t
##### ::Term2 t
- ::Definition2a t
- ::Definition2b t
t
##### ::Term3 ##### ::Term3
::Definition3 ::Definition3