Understand UIs needed by AIV for ITF 'signal chain' for LOW

Relevant stakeholders are identified: including members of AIV teams including AIV leaders including some of the architects A report describing a list of user-level use cases (what Cockburn calls "sea level" use cases) for AIV actors is made available. It should be such that: the use cases should be big enough to provide value to the actor they should refer to an uninterruptible chunk of activites performed by the actor no need to dive into too much details a 1 or 2-paragraph description of the user goal is needed, which should include a statement explaining the value to the actor no flows are needed yet no need for triggers, preconditions, postconditions would be good primary actor is needed no need to be careful about secondary actors no need to be precise about the structure of the information processed by the use case some summary use case is needed to provide context 1 or more use-case diagrams are needed the scope of each use case is the 'Signal Chain' ITF,  the system itself or the test bed, and it should be made explicit. The report should as complete as possible: involved stakeholders would claim that it contains all that they may think of The report should be as valid as possible: involved stakeholders would argue that the contained use cases do depict what will be needed. If important areas/issues have been discovered but cannot be included in the report for some reason, they should be mentioned.