Workflow Diagrams Code Submission and Testing Process.

Slides:



Advertisements
Similar presentations
Testing Workflow Purpose
Advertisements

Branching, Switching and tagging Francesco Furfari CNR-ISTI Italy.
Indistar: Updates, Additions, and Coming Soon Stephanie Benedict, ADI.
Fully Developed Claims
Workflow Diagrams Code Submission and Testing Process.
Software life cycle processes Purpose n A new international standard (ISO/IEC 12207:1995(E) that –establishes a common framework for software life cycle.
TECHNICAL BID OPENING. Tender creator logs in 1. Dept user logs in with login id and password 2. Click Login.
OPERA Electronic Submission of Administrative Supplement and Change of Institution Requests David Curren and Emily Linde Office of Policy for Extramural.
1 Electronic Filing System United States Patent and Trademark Office.
PROACTIS: Supplier User Guide Contract Management.
Chapter 10 Publishing and Maintaining Your Web Site.
CEN th Lecture CEN 4021 Software Engineering II Instructor: Masoud Sadjadi Change Control.
Sudheesh Singanamalla. Editable and Free Every open source software is free to download and use for a lifetime. At the same time it gives the transparency.
UML - Development Process 1 Software Development Process Using UML (2)
Open Source EHR Services OSEHRA Architecture Work Group Meeting June 4, 2013.
RUP Implementation and Testing
Rational Unified Process Fundamentals Module 4: Disciplines II.
Software Engineering CSCI 201L Jeffrey Miller, Ph.D. HTTP :// WWW - SCF. USC. EDU /~ CSCI 201 USC CSCI 201L.
Deliverable Readiness Review LexEVS 5.1 December 17, 2009.
 To explain the importance of software configuration management (CM)  To describe key CM activities namely CM planning, change management, version management.
Afsin Ustundag, Ray Group International 1. Scheduling Update Scheduling was chosen as the second package to refactor  Significant number of dependencies.
Configuration Management (CM)
Using Turnitin® and ETS e-rater® with myWriteSmart
Testing Workflow In the Unified Process and Agile/Scrum processes.
Three State Data Warehouse 1 Cassie Archuleta Tom Moore May 6, 2014 Progress Update for 3SDW Development.
Chapter 9 Publishing and Maintaining Your Site. 2 Principles of Web Design Chapter 9 Objectives Understand the features of Internet Service Providers.
INFO 637Lecture #101 Software Engineering Process II Review INFO 637 Glenn Booker.
T Iteration Demo Group name [PP|I1|I2] Iteration
TEST-1 6. Testing & Refactoring. TEST-2 How we create classes? We think about what a class must do We focus on its implementation We write fields We write.
Managing Change 1. Why Do Requirements Change?  External Factors – those change agents over which the project team has little or no control.  Internal.
Health eDecisions Use Case 2: CDS Guidance Service Strawman of Core Concepts Use Case 2 1.
Configuration Management and Change Control Change is inevitable! So it has to be planned for and managed.
Report Sharp-Shooter is released in the following editions: 1) 2) 3) 4) 5) 6)
SAMSUNG AMERICAN LEGION SCHOLARSHIP APPLICATION PROCESS & BEST PRACTICES.
Configuration Management CSCI 5801: Software Engineering.
Anubha Gupta | Software Engineer Visual Studio Online Microsoft Corp. Visual Studio Enterprise Leveraging modern tools to streamline Build and Release.
Updates to the Windows Logo Program Tools for Windows 7 Karl FroelichCraig Rowland Lead Program ManagerSenior Program ManagerOnline Device Services
Community Codes Free and shared resource Ongoing distributed development by both research and operational communities – Maintained under version control.
1 Proposal and Observation Handling Ravi Sankrit (User Support Scientist) SSSC May 11, 2011.
VxVistA Project: Summary Slide The vxVistA Project is envisioned as a method of providing a platform for an Open Source EMR based on the FOIA released.
Product Definition Christopher Edwards
Indistar® Dashboard overview. School and District Dashboard HOME tab Link(s) to Indicators that school’s assess, plan and monitor Quick access to live.
SES Performance-Based Pay System Three steps to USDA implementation and change: 1. Convert all senior executives to new pay for performance system 2. Develop.
Certification and Adoption Workgroup HIT Policy Committee April 28, 2014 Discussion on Incremental Rulemakings.
® Secure Destruction Service Sam Pulcrano Vice President, Sustainability MTAC Washington, DC February 17, 2010.
28 June 2000P. Mato, CERN1 Software Checklist Proposal for controlling and documenting all the steps in developing software Program of Work Meeting, June.
SWRCBSWRCBSWRCBSWRCB AB2886 Implementation San Jose Training San Jose Training July 30, 2001 Marilyn R. Arsenault ArsenaultLegg, Inc.
T EST T OOLS U NIT VI This unit contains the overview of the test tools. Also prerequisites for applying these tools, tools selection and implementation.
Software Development Security Chapter 10 Part 3 Pages 1108 to 1125.
MEA Document Overview Slides 26 February About these slides This slide pack is designed to provide market participants with an introduction to.
Workflow Diagrams Code Submission and Testing Process.
Gilda certificates. Certification Authority
December 17, 2014 popHealth® OSEHRA Update Fred Prior, PhD Special Projects Consultant Peter Li Director, Engineering Don Hewitt VP, Business Operations.
Adaptive Software Development Process Framework. Version / 21 / 2001Page Project Initiation 2.0 Adaptive Cycle Planning 5.0 Final Q/A and.
Zscaler Support Best Practices Guide Version September 27, 2016.
Developers Users Committers How do I configure this now? Just one more fix and I am done! CVS Download/Use Software Submit problems/ request features Store.
Part Approval / Compliance Data Submission via Jotform.com
Engineering Change Request (ECR) Process Change Request (PCR)
Software Engineering (CSI 321)
Software Verification and Validation
The Use of AMET and Automated Scripts for Model Evaluation
Using Turnitin, GradeMark, and ETS e-rater in myWriteSmart
Object Oriented Analysis and Design
Introduction to Software Testing
This presentation document has been prepared by Vault Intelligence Limited (“Vault") and is intended for off line demonstration, presentation and educational.
Adaptive Product Development Process Framework
Delivering great hardware solutions for Windows
Software Development Process Using UML Recap
CAS Recommendation Portal
Certification Plan EdgeX TSC F2F May 1,
Presentation transcript:

Workflow Diagrams Code Submission and Testing Process

Developer VA OSEHRA Code Submission – Bug Fix User Develops Code Submit to Gerrit OSEHRA Gold (3) OSEHRA Review (1) VA Review (2) VA Gold (4) (1)Reviewer is required to download code/tests, execute tests and evaluate the code. Referral is either back to Gerrit for additional modifications/abandonment or for acceptance. OSEHRA review may include manual functional testing. (2)VA certification process as defined by VA. Two types of feedback can come out of the VA process – Bug Fixes which require recertification by OSEHRA, and requests for additional artifacts such as BRDs, ICRs, Requirements Documents, Test Plans, etc. (3)OSEHRA gold version may need to be separate from VA gold unless we can identify a mechanism whereby the VA can accept code outside its area of interest such as pediatrics packages, open source versions of redacted code, etc. (4)VA gold as defined by/maintained by VA. Bug Fix or Increment al Change Notify OSEHRA Notify VA

Developer VA OSEHRA Code Submission – New Capability User Develops Code Submit to OTJ OSEHRA Gold (3) OSEHRA Review (1) VA Review (2) VA Gold (4) (1)Reviewer is required to download code/tests, execute tests and evaluate the code. Referral is either back to Gerrit for additional modifications/abandonment or for acceptance. OSEHRA review may include manual functional testing. (2)VA certification process as defined by VA. Two types of feedback can come out of the VA process – Bug Fixes which require recertification by OSEHRA, and requests for additional artifacts such as BRDs, ICRs, Requirements Documents, Test Plans, etc. (3)OSEHRA gold version may need to be separate from VA gold unless we can identify a mechanism whereby the VA can accept code outside its area of interest such as pediatrics packages, open source versions of redacted code, etc. (4)VA gold as defined by/maintained by VA. New Capability Notify OSEHRA Notify VA

Developer VA OSEHRA Nightly Testing/Dashboard (1)Process for Nightly Regression/Unit Tests. (2)The test engine automatically uploads to the dashboard on completion of the tests. No additional user action is required. Automatic From Cron Script Submit to Dashboard (2) Nightly Process (1) Download Test Harness Adapt Script/Set up Cron Update Test Harness Update VistA Code Execute Nightly Tests Automatic From Cron Script Submit to Dashboard (2) Nightly Process (1) Download Test Harness Adapt Script/Set up Cron Update Test Harness Update VistA Code Execute Nightly Tests Display Results Automatic From Cron Script Submit to Dashboard (2) Nightly Process (1) Download Test Harness Adapt Script/Set up Cron Update Test Harness Update VistA Code Execute Nightly Tests

Developer VA OSEHRA Experimental Testing/Dashboard (1)Process for verification of changes either as a developer or during review. (2)Changes may be downloaded from Gerrit, the OTJ, or be made as part of ongoing development. (3)The test engine automatically uploads to the dashboard on completion of the tests. No additional user action is required. Submit to Dashboard (3) Experimen tal Process (1) Download Test Harness Download VistA Code Apply Changes (2) Upload to Caché / GT.M Execute Tests Display Results Submit to Dashboard (3) Experimen tal Process (1) Download Test Harness Download VistA Code Apply Changes (2) Upload to Caché / GT.M Execute Tests Submit to Dashboard (3) Experimen tal Process (1) Download Test Harness Download VistA Code Apply Changes (2) Upload to Caché / GT.M Execute Tests

OSEHRA Developer VA (1) Sufficien t Artifacts ? Interest ? VA Intake OSEHRA Certifies VA Notified (1)This is our understanding of the process as the VA intends to implement it based on our discussions with VA developers. We will need to adapt to whatever process the VA implement. (2) “Additional Effort” can either be a request for additional artifacts (BRD, ICRs, Requirements Documents, Testing), a notice of a bug, or a request for additional development prior to acceptance. Artifact requests do not require additional OSEHRA effort other than potentially a cursory review. Code changes will require eventual recertification by OSEHRA; although, that can follow formal acceptance of the changes by the VA. VA Initial Evaluation Discard Code Submitted VA Certifies ? Request Additional Effort (2) Notify OSEHRA Additional Artifacts