Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

This page is a landing spot for notes LeeAnn and Andrea to share information on FHIR software development from the design and project management level.

...

Date:

Possible discussion topics:

  • Review Kathy’s comments

  • Discuss typical software development process - what we do, what HealthFlow does, where to find information.

  • Discuss learnings from LinkedIn Learning and web research (see notes below)

  • Invite Sarah P to talk about what she would do differently and critique the plan?

 Andrea’s notes and thoughts prompted by Linked In Learning

  1. There is a standard software development process. HealthFlow takes direction from us, but we are not equipped, experienced, or using a traditional software development process on our end. Example of STEVE (State and Territorial Exchange of Vital Events) - there is a whole process starting with requirements gathering. LeeAnn dis-covered that in her thinking process, i.e., asking potential users what they want rather than starting with what we think they need.

Establish requirements now (Source 2)

Establish acceptance criteria (Source 2)

 

Info

Sources

1.What is User Acceptance Testing (UAT): A Complete Guide (softwaretestinghelp.com)

2. A Beginner's Guide to Writing User Stories

...