Good afternoon everyone,

I converted the spreadsheet version of the DoD document to Google doc.  Here it is for your reading pleasure (or if you need something to quickly fall asleep):

https://docs.google.com/document/d/1lGoejFjT309OSF4vw1zBMoQi1AQXJ5cNrR8UUPleF8o/edit?usp=sharing

I changed the link on the Tech Council’s confluence page too.

In this version I (think I) addressed a couple of comments raised in the sheets version.  Please remember to submit your comments by eod tomorrow.

As I was finishing work on the doc, I thought of the next steps (all are listed in the document now)

• Document and publish NFRs
• Establish and document security vulnerability quality gate in SonarQube.  When do we run it?  Should it happen nightly when the code deploys to an integration environment?  
• Document and publish UX guidelines: http://ux.folio.org/docs/design-guidelines/
• Define severity levels of the issues found by QA (critical, high, etc)
• Define supported FOLIO browser/devices
• Agree whether testing a feature across all supported browsers would need to be included in the nightly regression testing Jenkins job

Thanks,

-m

-- 

Mark Veksler

Director, FOLIO Development - EBSCO Information Services

mveksler@ebsco.com | +1-978-356-6500 x2349 (O) | +1-617-470-5453 (m)