For environmental workers who need to report spills or look up information about chemicals if a report is needed. The Chemical Spill Tracker is an information system that will allow users to calculate whether or not a spill at the company or location will need to be reported to the proper authorities and if so, who to contact.
We are creating this project as a continuation of our courses at Western Oregon University for the Computer Science Program. Courses in this program for the Senior Capstone are: CS460 - Software Engineering I, CS461 - Software Engineering II, CS462 - Software Engineering III. As well as prerequisite courses CS361 - Algorithms, CS364 - Information Systems.
Under Title 40 Chapter I SubChapter J Parts 302 and 355 of the Code of Federal Regulations in the USA, requirements are established for facilites to submit emergency notification of chemical releases for designated chemicals on the List of Hazardous Substances and Reportable Quantities and List of Extremely Hazardous Substances and Their Threshold Planning Quantities.
We use equation 7 from the EPA's Technical Guidance for Hazard Analysis Appx. G §2 to calculate the evaporation rate (rate of volatilization) for spilled pools of chemicals.
- Follow MVC: Model, View, Controller
- Controllers and Models written in C#
- Views Written in HTML, Javascript, and CSS
- Add comments where code might be confusing or to help others understand its purpose
- Curly braces on their own line
- variable names in camel case, no '_' in between words - "variableName"
- Class names must start with a capital and second word is also capital, no '_' in between words - "ClassName"
- Database context will be named db
- Follow Bootstrap formatting
- Follow color schema that is chosen in advance
- id names will be camel case - "variableName"
- Format using in-line styling
- size things using % do not use px or ef
- Format after you get your functional code working
- Function names in camel case - "functionName"
- Variable names in camel case - "variableName"
- Curly braces on their own line
- Primary keys will be named 'ID'
- Foreign Keys will include the table and ID where it came from - "ChemicalID"
- Constraints will be sperated by a '_' - "Form_FK_Chemical"
- Use separate feature branches.
- Only commit working code (Unless others require your code to help fix a bug) and commit often.
- Write meaningful commit messages.
- Pull the upstream development code and merge it into your feature branch before submitting a Pull Request.
- Pull Request must be made to the dev branch. All other pull requests will be rejected.
- GitHub Repo Master will merge the dev branch into the main branch after Sprint Meetings
- Be Kind
- Work Efficiently
- Microsoft Azure
- Identity Framework
- Core 3.1
- SQL Server
- C#, HTML, Javascript, CSS
- Continuous Deployment
LGPL-3.0-or-later
For more info see License.md file