Embedded Files
Team Members :- Anil kantipudi ,Yousuf Mohamed Abdulla ,Neelima sattor , Khaleem
Project mission
Project mission
The Project requirement was to develop an IT-Management software to manage Licenses and Assets owned by an organization.
The Main objective was to focus on License and Asset management.
We took the following strategy since we were required to complete an existing project within the constraints of the proposed tech stack.
Getting each system up and operating for the first time.
Familiarizing ourselves with the tech stack and tools already in use in the underlying code.
Recognize the project's current flow.
Forming small groups inside the team to contribute to and complete the overall aim.
To make headway on this project, we needed to master the TWIG templating engine, the PHOENIX library, and other design tools.
In order to communicate with the database and the front end, we needed to comprehend and learn how to write rest endpoints.
What was there in the base code base:
What was there in the base code base:
1) Docker composer file for starting the containers and testing the app functionality on localhost.
2) A sample codebase with endpoints for pulling data from the backend for license tracking.
3) Users, profiles, and so on were already operational, however the main code base contained numerous flaws.
4) Sample schema files are provided as migrations, so that anyone may clone the project and execute it locally without having to worry about dependencies.
5) A polarising/bcrypt library is used to encrypt and decrypt sensitive data.
6) Use the vlucas/phpdotenv package to load environment-related parameters into the project.
What was newly developed:
What was newly developed:
1) Improved License Tracking with Insert, Update, and Delete actions.
2) Created Asset Tracking from the ground up, including the database schema, using database migrations.
3) New UI components to facilitate License and Asset tracking CRUD operations.
4) Complete error handling.
5) Improved user interface to notify end users of issues occurring on the client or server side while the program is running.
6) Added new routes to facilitate CURD asset and license tracking activities.
What can be done further:
What can be done further:
1) Enhancing asset and license tracking to support more use cases. For example role based operations.
2) Enhance the UI to make end user more confortable and engaging.
3) Enhance the DB schemas to cover more real time use cases.
4) Introduced more modules into system to support other aspects of IT-Management operations.
Page updated
Google Sites
Report abuse