Incident-Manager
Incident Manager simplifies incident reporting with a user-friendly setup and timely notifications. It's your practical tool to handle unexpected situations effortlessly, keeping you informed and in control. Everything is in your control, creating, updating, and deleting incidents. Seamless changes, creating new entries, modifying existing information. Our goal is to have a well-organized and efficiently managed incident database. You can Create, Update, and Delete incidents as you see fit. Development Journey
Visit Our site https://incidentvault.onrender.com/
How to get started: To create a new incident:
- Navigate to the incident page
- Click on the 'Create Incident' button
- Fill in the required details and click 'Submit'
Project Collaborator
- Prashanth Nallathamby
- Abishan Jeyanathan
- Sangeethan Thevathasan
- Omar Bushnaq
- Ayaan Bajwa
Our motivation for this project is to assist users in managing unexpected situations more effectively. The incident manager was created to address the challenges of efficiently handling unforeseen incidents, aiming to simplify the process of incident reporting. The goal was to devise a solution that makes incident reporting simple, allowing users to have a smooth and manageable experience. Lessons Learned
Throughout the development process, we encountered challenges, particularly in implementing the connection between Angular and CRUD to MongoDB. CRUD, essential for creating, reading, updating, and deleting data, was a necessary component. Angular proved to be a useful framework for developing user-friendly single-page applications.
(Week 1):
Splash page with team logo
Logo will direct the user to the incident page
Incident Report Requirements: Name, Date (day and time), type of incident, description, Administrator, damages, status (resolved or work in progress)
Git commits and push
Testing git
Need to make a video for change
Models done
Debugging issue with integrations from different collaborators successful
Adding new incidents to the database
Full CRUD working and compatible
Need to make a video
(Week 2): Next Steps
GUI, UI changes
Make it look nice
Logging and user authentications
About sections, Home Page views refining, and making it better.
(Week 3): Next Steps
Refresh GUI interface and user interfaces
Client-side intel
Check Control Version
Cloud Deployment
Comments on each file for general pointers
Background Image Implementation and a few server-side tweaks
Fully functional
Organized
Understandable
Appropriate Design, font, color choices
Allow users to update and delete the data
Functional and User Authentication is implemented and works
Integration with other services
Resources:
Special thanks to Prof for the insights shared on (Media Gallery) during the development.
w3school.com
www.npmjs.com
www.nodejs.org
www.expressjs.com
www.mongodb.com
www.mongoosejs.com
www.freecodecamp.org
render.com
mongodb-atlas.com
www.github.com