From 24138cc09ed47c62399d511022528d7397b2da30 Mon Sep 17 00:00:00 2001 From: Stefan Date: Tue, 11 Apr 2017 19:41:29 +0200 Subject: [PATCH] blogged about need for use case --- content/blog/tightest-use-case-1/contents.lr | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 content/blog/tightest-use-case-1/contents.lr diff --git a/content/blog/tightest-use-case-1/contents.lr b/content/blog/tightest-use-case-1/contents.lr new file mode 100644 index 0000000..4b3a6b1 --- /dev/null +++ b/content/blog/tightest-use-case-1/contents.lr @@ -0,0 +1,13 @@ +title: TIGHTest Use Case (1) +--- +_discoverable: yes +--- +body: + +While developing LIGHTest, many discussions and decisions happen on a very abstract level. This makes sense, since LIGHTest, in contrast to TIGHTest, provides a abstract system, enabling to use it with different use cases. + +Since one of the goals of TIGHTest is to develop a prototype of the concepts proposed in LIGHTest, it is useful to remove the generic aspect of its design. It is not clear so far to what extend this is going to happen, but to start, we need a use case. + +A use case is useful to have a clear picture in mind, and to be able to test the planned architecture. Thus, a use case should use all aspects we have in mind in one way or another. +--- +pub_date: 2017-04-11