Project VERITAS

Problem Definition
Our client has requested that we create a web interface that communicates with a dynamic database securely. To do this, we have broken the project up into three main parts:
 * the web interface's design and implementation
 * the database's design (including how to simply edit the contents given the proper permissions)
 * the communication protocols between the two.

Background
PNNL is looking for a means of displaying particular information about various products and their specifications in a dynamic, secure, and reasonable way. This project, thus, will require a background in databasing, querying languages, webpage languages, servers, and general client-server security.

Deliverables

 * An accessibility-standards-compliant webpage, that will act as an interface for the client wanting information.
 * An SQL database/server, able to be changed dynamically and easily, that can be queried by the webpage.
 * Documentation detailing the use of each.
 * Potentially a duplicate database/server that will be air-gapped, but this is a stretch goal.

Specifications
NOTE: SUBJECT TO CHANGE Currently still detailing specifications with client. Current hosting will be done on an Amazon web server. All code must be accessibility-specification compliant.

Relevant Links/Document Archive
This space to be updated with links to repository (with permission) and to the hosted webpage. Will also include meeting minutes, client interview notes, and design notes (again with permission. This project is considered confidential, so what actually ends up here is still TBD by our client)


 * [[Media:VERITASMeetingMinutes.pdf|VERITAS Meeting Minutes]]

News

 * Access to PNNL servers denied. Hosting being moved to Amazon web server for now.
 * First commits of code to repository in the works. More design direction to follow.

Project Learning

 * What is applicable to other engineering majors isn't as applicable to CS majors. For instance, having a prototype of something in mechanical engineering makes a lot more sense than having a prototype in CS, where things are subjects to major and immediate changes.


 * So much difficulty comes from waiting for permission to move ahead. Without proper resources (namely, a server to host our work) and the go-ahead, effectively we don't have leave to start working on anything. This is where we've been, stuck drafting ideas on paper and reading documentation, waiting for something to happen.

Team Member Information

 * Alex Wezensky is a senior dual majoring in computer science and mathematics. Within computer science, Alex is interested in artificial intelligence and big data. In his free time, Alex enjoys playing basketball and ping-pong, and playing Rock Band with his roommates.