Versions Compared

Version Old Version 8 New Version 9
Changes made by

Andrea Price (Deactivated)

Andrea Price (Deactivated)

Saved on

Key

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

...

Date:

Date:

Date:

Date:

Date:

We each know what the other is thinking for software development process and user acceptance testing.

We have identified any needs/gaps in knowledge (should UAT be designed by or done by a consultant?  HealthFlow does not have this strength).

 Assignment – watch 1-2 videos from Linked in Learning or read a web site that explains the process of UAT.

–

Date:

Possible discussion topics:

  • Review Kathy’s comments

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

  • Andrea ask LeeAnn for help with questionnaire

  • 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) -I managed a major overhaul and was guided through the process by the software developers. 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.

  2. Agile vs Waterfall

    1. https://en.wikipedia.org/wiki/Software_development_process

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

3. Agile Manifesto

4. https://ncube.com/blog/software-development-life-cycle-guide

Phase 1. Requirement collection - Goal: to gather and document business requirements

  • Develop user stories for what you WANT the software to do

  • Gather requirements (there is an entire field on this - and a format for requirements that makes it easy to communicate to the software developers)

Phase 2. Design - Goal: to translate software development requirements into design

Phase 3. Software development -Goal: To build the actual software

Phase 4. Testing - Goal: To ensure the software meets requirements

Phase 5. Deployment - Goal: To deliver completed software to users

Source: https://ncube.com/blog/software-development-life-cycle-guide

View file
nameHDC testing strategy 4-6-23 km.docx

...