Clinician Subdomain Installer

Transcription

1 Clinician Subdomain Installer Senior Project, Spring 2018 A project by Arbitrary Coders: Daniel Jensen Gabriel Wohlwend Barry Bethay www2.cs.siu.edu/~arc/

2 Abstract Clinician Subdomain Installer is a web portal for use by DxR employees to create, install, edit, and delete instances of the DxR Clinician software, each hosted on its own subdomain. This web portal uses authenticated user accounts that can also be created, edited, and deleted with the portal itself.

3 Motivation Current process Clinician is installed manually by IT staff for each sale Installation can only be done via a slow and involved command line process Customers have to wait up to a day for IT to perform the installation before they can access their product Client DxR Admin Sales Team

4 Motivation With Clinician Installer Clinician can be installed by sales employees rather than IT Site installation is easy and quick Customers can access their product immediately Client Sales Team

5 Goals Platform independent Any Operating System Any Web Browser Accessible from anywhere Secure Available on the web Authenticated with salted hashed passwords Simple to use Self-Sufficient Should be able to do all Clinician maintenance tasks with no outside assistance

6 Plan Develop a web portal that can be used to Create, install, edit, and delete subdomain installations of DxR Clinician software Create, edit, and delete user accounts for logging into the web portal Develop a CRON script that Performs installation, modification, and upgrading of Clinician installations Pass information via a database

7 Process Agile Scrum 2 week sprints Scrum meetings twice per week Functionality/Issue Code review QA by mentor

8 Technology Overview Ubuntu LTS Server Node.js Express.js Handlebars Bootstrap 4 MySQL Python CRON script

9 System Design Clinician installer web application takes information for the to-be-installed Clinician instance All information gets stored in a MySQL database CRON runs a python script on an interval which checks the database for Clinician instances that need to be installed, modified, or upgraded and updates the database when complete Python script creates or modifies an installation of DxR Clinician

10 Challenges Multiple new or unfamiliar programming languages Each team member had varied, limited experience with the technology used in the project. Adjusting to sprint schedule and time constraints Sprints are two weeks, but code needs to be completed, reviewed, QA ed, potentially revised, and signed off on within that two week time. Scheduling conflicts Balancing work, school, and extracurricular activities with the time needed to complete the project.

11 Database

12 System Interface

13 System Interface

14 System Interface

15 Moving Forward What would we do to improve if we continued working? Massive refactor Clinician is written entirely in perl, so Clinician Installer sometimes acts as a wrapper to call those perl scripts. To clean this up we would move as much of the functionality away from perl as possible. Additional user types Currently only god account and a regular account Better logging More descriptive error messages logging to console

16 Acknowledgements Many thanks to Robert Evans from DxR who mentored us through the project. He was a large help to us getting familiar with the tools involved and creating a product that fit his vision and would be of great benefit to the employees at DxR.