E
elmagnifico
Hi all,
I am working with a documentation of a medical app I wonder what is a better way to write requirements and how to put them in sentences properly for verification and validation. Here is a small part of the requirements;
a) Launching the mobile application
- Launch icon should be visible
- Launch icon should bring the splash screen on
- Splash screen should not stay more than 1 second
b) Logging in to the mobile application
- USER have a master pin code
- Pin code should consist four numerical character
- USER should see how many characters being entered
- The numbers entered are replaced by circles and remains hidden
- If the pin code is right, USER should reach to the main menu
- If the pin code is wrong, USER will see an option to receive a new pin code by email
First of all, I wonder if there is a better way to write requirements. For example, should it be like this;
1) Launching the mobile application
1.1 Launch icon should be visible
1.2 Launch icon should bring the splash screen on
1.3 Splash screen should not stay more than 1 second
After listing them correctly, how should I write the validation plan. Here is an example that I plan to continue with
Requirement
Req1.1 Launch icon should be visible
Validation Plan
The application is used by 5 typical users and they are asked to launch the application on the main window. Upon completion, they are given a survey asking: ?On a scale of 1-5, how visible is the launch icon of the app?
Acceptance Criteria
Average of greater than 3.0
Notes
But i wonder now should do it that way and validate all sub-levels or should I create a more general validation plan and skip the details of it such as;
80% of users should be able to launch the app within 10 seconds on their first try
And for the verification, I feel like some of the requirements don't look verifiable or I don't know how to put them in words in a good way. For example, how can I verify the requirement that saying "launch icon should be visible"? It looks validatable but not verifiable. Should I create my requirement in a way that they should be both verifiable and validatable?
I hope I managed to explain my problem. Please ask if it is not clear.
Cheers,
I am working with a documentation of a medical app I wonder what is a better way to write requirements and how to put them in sentences properly for verification and validation. Here is a small part of the requirements;
a) Launching the mobile application
- Launch icon should be visible
- Launch icon should bring the splash screen on
- Splash screen should not stay more than 1 second
b) Logging in to the mobile application
- USER have a master pin code
- Pin code should consist four numerical character
- USER should see how many characters being entered
- The numbers entered are replaced by circles and remains hidden
- If the pin code is right, USER should reach to the main menu
- If the pin code is wrong, USER will see an option to receive a new pin code by email
First of all, I wonder if there is a better way to write requirements. For example, should it be like this;
1) Launching the mobile application
1.1 Launch icon should be visible
1.2 Launch icon should bring the splash screen on
1.3 Splash screen should not stay more than 1 second
After listing them correctly, how should I write the validation plan. Here is an example that I plan to continue with
Requirement
Req1.1 Launch icon should be visible
Validation Plan
The application is used by 5 typical users and they are asked to launch the application on the main window. Upon completion, they are given a survey asking: ?On a scale of 1-5, how visible is the launch icon of the app?
Acceptance Criteria
Average of greater than 3.0
Notes
But i wonder now should do it that way and validate all sub-levels or should I create a more general validation plan and skip the details of it such as;
80% of users should be able to launch the app within 10 seconds on their first try
And for the verification, I feel like some of the requirements don't look verifiable or I don't know how to put them in words in a good way. For example, how can I verify the requirement that saying "launch icon should be visible"? It looks validatable but not verifiable. Should I create my requirement in a way that they should be both verifiable and validatable?
I hope I managed to explain my problem. Please ask if it is not clear.
Cheers,
Last edited by a moderator: