About this site

This site is a place where personally put tools I've created for consulting. There are two tools.

  1. Scenario-based requirements creation tool
  2. MC/DC Desing tool

1. Scenario-based requirements creation tool

There are several methods to clean up a requirement scenario, but the cleanup method used here is Given-When-Then method. Based on this, you can use the tool to create an acceptance test case to facilitate testing of requirements later.

The key to how we present it is to map out the requirements. Let's now map the requirements and see how they can derive the acceptance test case.

(1) Persona Confirmation

You should first consider which user's perspective defines the Action.

For example, I would like to select a fan service app exclusively for idol singers. The main purpose of this program is to communicate with idols and fans, and to receive notices, fan boards, and notices related to idols.

The primary user is a teenage high school girl. Since this is not an analysis site for UX, we will not write down the detailed analysis.

(2) Confirmation of Given, When

Let's anticipate how this user will behave with this app.

No Exposed Action
1 Send a text to my idol
2 Download the photos
3 Comment on my idol's post.
4 With membership registration, you can become a fan club member.
5 You'll be notified when your idol's new post is registered.

Let's split the Action into more detail.
No Expected Action Details
1 Text my idol
  • Texts are only available to members.
  • There is no entry restriction.
2 Download the photos
  • Phots can be downloaded by members and non-members.
  • Comments are available to members only(140 chars)
3 Comment on my idol's post.
  • Comments are available to members only(140 chars)
4 With membership registration, you can become a fan club member.
  • Membership registration is open to anyone.
5 You'll be notified when your idol's new post is registered.
  • Allow anyone when App is installed

Can this be a requirement? Requirements should be testable, which does not seem easy to derive specific test cases.

Let's divide this into Given(Condition) and When(Action).

Given
  1. Permissions would be changed depending on membership registration status.
  2. Limit the number of comment letters to 140 characters
  3. Character is not restricted in text message
When
  1. Send text messages.
  2. Join a member.
  3. download idol pictures.
  4. Write a comment on the picture
  5. Write a comment on your idol's post.

(3) MindMap

Making a Given-When relationship based on mindmap gives good perspective to us. Based on this, the acceptance test case can be created.


This is, of course, from a tool. Root, Given, and When have been left alone and have changed the children.

Now let's think about the case where the association cannot be.

In Given section, Limit of character count Over/under 140 and Download Photos in When section cannot make assosiation. Download Photos can assosiate with Limit of character count / irrelevant

Considering these relationships, click Set Condition to set the following.

To save your results here, click the SaveMapData button. Click OK to view the results of the test case creation.

The result is a pairwise combination, not a full one. Although the case of your choice may have missing, verification of the requirements is a concept of acceptance testing, so you don't have to be a full case.

(4) Conclusion

The structure of work we persued is like below.

Requirement Structure TestCase
Requirement in the form of Given-When-Then MindMap Acceptance test cases

The requirements should be testable and the above structure shall be a set of test cases to be derived and verified for a single requirement structure (Map).



2. MC/DC design tool

MC/DC is the strongest structural-based test design technology existing. But we didn't have a lot of design tools to do that.

It's simple to use. Attaching the desired logic code onto the input form will produce a test case using MC/DC techniques.

Here we will use the code that is supplied as a sample immediately.

Click Down to download the file as an Excel file if you want to see more comportable structure.

The last part of !b and a is test data for MC/DC. !b means b=false and a means that a=true.

Happy Testing!