We think you have liked this presentation. If you wish to download it, please recommend it to your friends in any social system. Share buttons are a little bit lower. Thank you!
Presentation is loading. Please wait.
Published byPatrick Rolph
Modified over 2 years ago
OCNG OpenClinica Next Generation 1
© What Is OCNG? OpenClinica Next Generation A Test Bed For New Technology Developed Independently of OC 3.x Keeping Same Features, Adding a Few More Same Database Schema 100% REST Interface Complete Client and Server Decoupling Alpha Release 26-Aug
© How much of this will end up in the real OpenClinica? It depends on how much you like it. When it is released as an Alpha it will have many documented aspects to it that may become part of a future OpenClinica release. 3
© Project Timeline July 8: Initial pre-pre-pre-alpha that will include a narrow cross section (about 10%) of the basic operations of OC, now mimicked in this new architecture July 15, July 22, July 29, August 5, August 12, August 19: Weekly milestone releases tracking a path to the August 26 Alpha release. August 26: Alpha release of OCNG that will include a wide cross section (about 80%) of the current operations of OC, along with many new features. 4
© 100% REST, 100% Data Portable ODM Fragments Sent Back and Forth Every OpenClinica action will be represented Complete Decoupling of Service and Clients 5
© One OpenClinica Service, Many Clients The Web Service Is The Web Application All clients will access this service the same way: OpenClinica Browser Client External REST Web Service Clients iOS Applications Android Applications All of these clients access the same REST URLs and send and receive the same ODM fragments in either JSON or XML. 6
© Architecture Breakdown The following components will be described in terms of their composition and differences from the current architecture: Same Database Schema, Many Databases Supported Full Hibernate ORM Implementation Fully Published Service Layer REST URL Interface Fully Decoupled HTML Client 7
© Same Database Schema, Many Databases Full Backwards Compatibility With 3.x Schema Database For Storage and Not Application Logic Removal of Vendor-Specific Artifacts While Postgres Default, Support for Many Vendors 8
© Full Hibernate ORM Implementation Vendor-neutral database support by using Object Relational Mapping and no vendor-specific procedures. Hibernate will be used for the Object Relational Mapping (ORM) functionality. Straightforward Data Entities and Data Access Objects that map the OpenClinica services to the data that is acted on. There will be a single location for all native SQL calls. 9
© Fully Published Service Layer All of the application services will be mapped to a published service layer specification This eliminates the secret sauce factor where it is difficult to trace application functionality. Each of the services will be grouped and mapped to a similarly grouped set of REST URLs so that it is easy to work with the application logic. 10
© REST URL Interface All interaction with OpenClinica is accomplished via a data exchange referenced by an easy to understand REST convention. These REST URL patterns map smoothly to the published OpenClinica service layer. XML and JSON, usually in the format of ODM or ODM fragments, are exchanged as data. 11
© CRF Authoring Improvements A unified interface will generate the eCRF, the printable CRF, and the authoring interface to the CRF. Layout will be more controllable since every item can be custom sized and positioned. Rules and Validation can be authored in the form interface. Excel-based CRFs will still be supported but not required. 13
© 14 Enough of your Vulcan logic, where is the code? Application and source code distribution: https://dev.openclinica.com/hg/openclinica/community/OCNGhttps://dev.openclinica.com/hg/openclinica/community/OCNG The latest deployment: OCNG Wiki: +OpenClinica+Next+Generationhttp:// :8090/display/OCNG/OCNG+- +OpenClinica+Next+Generation
1 Copyright © 2013, Oracle and/or its affiliates. All rights reserved.
1 Introduction to ASP.NET. 2 Static and Dynamic Web Applications HTML is used to create static content Browser software interprets HTML tags and formats.
(2-Tier) (n-Tier) (Component) (Business Components)
Service Oriented Architecture 1 Master of Information System Management Service Oriented Architecture Web Services and REST.
Software Engineering Model Driven Architecture Software Engineering 2011 Department of Computer Science Ben-Gurion university Based on the book: MDA Explained:
Snejina Lazarova Senior QA Engineer, Team Lead CRMTeam Dimo Mitev Senior QA Engineer, Team Lead SystemIntegrationTeam Telerik QA Academy RESTful Web Services.
1 Computer Systems & Architecture Lesson 3 5. Designing the Architecture.
DATABASE SYSTEM CONCEPTS AND ARCHITECTURE CHAPTER 2 1.
Server Access The REST of the Story David Cleary Principal Software Engineer June 12, 2013.
© Liron Blecher Web Services Written by Liron Blecher.
Copyright © 2010 Accenture All Rights Reserved. Accenture, its logo, and High Performance Delivered are trademarks of Accenture. Accenture Software ALIP.
Contents Client-data script It refers to class of computer programs on the web that are executed client-side, by the user`s web browser, instead of server.
Implementation Architecture Lecture Implementation View (1) “ how the system is built ” Focuses on “ how the system is built ” technological.
RESTful (Web) Applications In Practice Nupul Kukreja CS 577b 6 th February
Clark County & the Web Application Development Framework.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 7 Slide 1 Chapter 7 System Models.
1 Copyright © . Roger L. Costello, Timothy D. Kehoe. All Rights Reserved. REST (Representational State Transfer) Roger L. Costello Timothy D. Kehoe.
©Silberschatz, Korth and Sudarshan8.1Database System Concepts, 5 th Ed, slide version 5.0, August Chapter 8: Application Design and Development.
The Client/Server Database Environment CS263 Lecture 12.
Silberschatz, Galvin and Gagne ©2013 Operating System Concepts – 9 th Edition Chapter 3: Processes.
Chapter 10, Slide 1Starting Out with Visual Basic 3 rd Edition Chapter 11 Developing Web Applications.
Chapter 7 – Design and Implementation 1Chapter 7 Design and implementation Note: These are a modified version of Ch 7 slides available from the authors.
© 2008 AT&T Knowledge Ventures. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Knowledge Ventures. 1 Numbering for IP-Based Relay Services.
ARINs RESTful Provisioning Interface Tim Christensen.
Web Center v4.1 Proprietary and Confidential Topic Section Overview 1 Rates and Data 2 Creating Promotions 3 Sitemap / Formatting Content 4 Administration.
Copyright © 2005 SOA Software, Inc. All Rights Reserved. Specifications Subject to Change Without Notice. Overcoming the SOA Network Fallacy Roberto Medrano.
Architectural Design IS301 – Software Engineering Lecture # 14 – M. E. Kabay, PhD, CISSP Dept of Computer Information Systems Norwich University.
GETTING STARTED WITH HTML5 - By Suresh Kumar. Agenda History, Vision & Future of HTML5 Getting Started With HTML5 Structure of a Web Page Forms Audio.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 6 Slide 1 Chapter 6 Requirements Engineering Process.
© 2016 SlidePlayer.com Inc. All rights reserved.