Requirements WG Status 2016 May 9

• Patrick Holmes announced his resignation

• Oleg Abdrashitov proposed ideas to improve the development of the Requirements Document

  • Feedback loop: the requirements should feed the Architecture WG and influence their decisions. Produce a monthly report of the new use cases and requirements.
  • Depth: the use cases need to be further developed and conform to the template.
  • Coverage: reach out to industry experts to gather new use cases.

These ideas were supported by the WG and by other key members of the project prior to the meeting.

• Oleg started implementing:

  • created a Google form to gather new use cases from the wider community
  • created and analyzed a database of the project members on Slack to determine experts from the industries not yet covered by use cases. Will reach out to solicit their input.
  • working to normalize existing use cases to conform to the template

• there's a concern that some project members may be bound by NDAs not to reveal their use cases. One of the solutions is to bring the existing use cases to the experts and have them not volunteer but only validate or comment on them.

• a suggestion was made to approach the Linux community for the new use cases

• Christopher Allen walked thru his contribution to the Requirements section of the Use Case template. Proposed to introduce Policy and Regulatory Requirements section

• The WG agreed to introduce milestones into the development of the use cases

  • Milestone 1: Sections 1 (Intro and User Stories) and Section 2 (States and Transitions). When completed, announce to the Architecture and other WGs.
  • Milestone 2: Section 3 (Requirements). Work with the Architecture group to develop technical requirements such as Correctness, Privacy, Hardware

• Nikilesh Subramoniapillai Ajeetha shared a mindmap of the requirements space captured so far by WG. It can be accessed here