SDEVEN Software Development & Engineering Methodology

Version: 7.0.13
Release date: 230810

-#NOTE the template starts here. README this before using this template
-#NOTE all fields that should be filled are marked as -#NOTE and enclosed in <...> as code section like me

-#NOTE <your project name here>

Document control

• updated at: <last updated date>
  
• updated by: <person who made last update>

Table of contents

Appendix F2 Test Scenario <code-name>

-#NOTE <set in title the scenario code-name that identify it>

General information

• code-name: <scenario code-name as set in title>
• tested functionality: <target functionality to test>

Requirements

• ... #NOTE here is the list with requirements to execute in good conditions all test scenarios
• ... ex; projector
• ... ex: video camera
• ...

Scenarios and activities

Legend

• # = an unique number which allow "in document" easy reference of step
• ATo = acceptable tolerance
• Dur = estimated duration
• RqTm = required team members indicating:
  • person name
  • person role
• OptTm = optional team members (only person name because these members will be considered observers)
• Exc = name of person who will execute the scenario (ie, operate the system)
• ExD = actual execution date
• Stat = status as PASS or FAIL

Notes & Remarks

• operation(s) that should d be executed in system (for example controls that should be auctioned, change focus in field, etc)
• data in as data that should be entered (clear & concrete values, not generic)
• expected output data that is expect to be obtained and system behavior (messages, events like refresh, waiting cursor, etc)

Final notes & remarks

-#NOTE this section is reserved for various notes and remarks regarding a particular scenario (refered by line #) or the plan itself

• ...
• ...

Approvals

-#NOTE this section is reserved for approver's signature