Transforming/Developing Drupal-Based Case Management System
Budget: ₹250,000 – ₹500,000 INR
Project Start Date: 3rd June 2024
Project End date : 30th June 2024
Task: ONLY DEVELOPMENT ( UI UX is being developed by a different team )
Portal Details: https://www.neuralit.com/saas-products/entrust-web-portal-lawyers
We are seeking a highly skilled developer to build a new, modular, and API-driven Case Management System (CMS) from scratch. The new system should adhere to modern software architecture principles, particularly the Model-View-Controller (MVC) pattern, to ensure maintainability, scalability, and efficiency. While our previous system was developed using Drupal, we are open to using a new tech stack that aligns with the latest industry standards.
Responsibilities:
1.System Design: Architect a modular CMS following MVC principles to ensure a clear separation of concerns.
2.API Development: Design and implement RESTful APIs to facilitate communication between various system modules, adhering to industry best practices.
3.Development: Build the CMS from the ground up, focusing on modularity and replaceable components.
4.Testing: Conduct thorough testing of each module and the integrated system to ensure functionality, performance, and interoperability.
5.Documentation: Provide comprehensive documentation for APIs, architectural decisions, and system functionalities. Conduct training sessions for developers and stakeholders as needed.
6.Collaboration: Work closely with the project manager and team members to ensure timely delivery and adherence to project requirements.
Requirements:
1.Proficiency in Modern Tech Stacks: Expertise in a current tech stack suitable for building scalable and maintainable systems following MVC principles.
2.Experience in API Design: Proven experience in developing RESTful APIs with robust security and performance features.
3.Software Architecture: Strong understanding of software architecture principles, particularly modular and MVC design.
4.Development Expertise: Ability to build complex systems from scratch, ensuring high performance and scalability.
5.Project Experience: Prior experience in large-scale system development projects .
To Apply:
Please submit your proposal outlining your relevant experience and approach to building modular, API-driven architectures. Include any past projects or case studies demonstrating similar work. We look forward to collaborating with a talented developer to elevate our Case Management System to new heights!
Note from the IT Head:
•Our platform is based on Drupal, I believe some version of Drupal 6( old version ).
•We have a module which is called liberation and we have done coding in that Liberation module which is customizable.
•We want to move into MVC pattern.
•Eg : Let’s consider a project, there are N number of modules. Let’s take a Lead Management System.
•There is lead module, then opportunity and then account module.
•If something is hard coded across the module then we cannot maintain that. Many teams are working on the same module simultaneously there will be conflict.
•We will have to create Separate modules with APIs, API will be resposible to handle the input and give the response back.
•X input will be given to an API and it will give the required output. If code it in a modular manner, then we can give it to any team members.
•Code to be modular and API driven so that everyone will get to know their roles and responsibilities that x is the expected input and Y is the expected output.
•E.g.: I am working on a report, Date from and date to is passed in API, it will give me the report. and now I want to do load testing, it will become very handy in this case, i will just have to pass the API URL and do the load testing.
•Modules have to be independent and refined. Tomorrow if there is any glitch we can go to that particular API only instead of checking the whole code and troubleshoot.
•Please review and let me know your approach on how you will implement this.
•We will require an email stating the approach, but I understand that outside communication is not allowed; therefore, please share the detailed version of your approach here on chat.
•Once we are satisfied with your approach, we can talk Further.
•I will provide you with credential to take a look at our current system.
Project End date : 30th June 2024
Task: ONLY DEVELOPMENT ( UI UX is being developed by a different team )
Portal Details: https://www.neuralit.com/saas-products/entrust-web-portal-lawyers
We are seeking a highly skilled developer to build a new, modular, and API-driven Case Management System (CMS) from scratch. The new system should adhere to modern software architecture principles, particularly the Model-View-Controller (MVC) pattern, to ensure maintainability, scalability, and efficiency. While our previous system was developed using Drupal, we are open to using a new tech stack that aligns with the latest industry standards.
Responsibilities:
1.System Design: Architect a modular CMS following MVC principles to ensure a clear separation of concerns.
2.API Development: Design and implement RESTful APIs to facilitate communication between various system modules, adhering to industry best practices.
3.Development: Build the CMS from the ground up, focusing on modularity and replaceable components.
4.Testing: Conduct thorough testing of each module and the integrated system to ensure functionality, performance, and interoperability.
5.Documentation: Provide comprehensive documentation for APIs, architectural decisions, and system functionalities. Conduct training sessions for developers and stakeholders as needed.
6.Collaboration: Work closely with the project manager and team members to ensure timely delivery and adherence to project requirements.
Requirements:
1.Proficiency in Modern Tech Stacks: Expertise in a current tech stack suitable for building scalable and maintainable systems following MVC principles.
2.Experience in API Design: Proven experience in developing RESTful APIs with robust security and performance features.
3.Software Architecture: Strong understanding of software architecture principles, particularly modular and MVC design.
4.Development Expertise: Ability to build complex systems from scratch, ensuring high performance and scalability.
5.Project Experience: Prior experience in large-scale system development projects .
To Apply:
Please submit your proposal outlining your relevant experience and approach to building modular, API-driven architectures. Include any past projects or case studies demonstrating similar work. We look forward to collaborating with a talented developer to elevate our Case Management System to new heights!
Note from the IT Head:
•Our platform is based on Drupal, I believe some version of Drupal 6( old version ).
•We have a module which is called liberation and we have done coding in that Liberation module which is customizable.
•We want to move into MVC pattern.
•Eg : Let’s consider a project, there are N number of modules. Let’s take a Lead Management System.
•There is lead module, then opportunity and then account module.
•If something is hard coded across the module then we cannot maintain that. Many teams are working on the same module simultaneously there will be conflict.
•We will have to create Separate modules with APIs, API will be resposible to handle the input and give the response back.
•X input will be given to an API and it will give the required output. If code it in a modular manner, then we can give it to any team members.
•Code to be modular and API driven so that everyone will get to know their roles and responsibilities that x is the expected input and Y is the expected output.
•E.g.: I am working on a report, Date from and date to is passed in API, it will give me the report. and now I want to do load testing, it will become very handy in this case, i will just have to pass the API URL and do the load testing.
•Modules have to be independent and refined. Tomorrow if there is any glitch we can go to that particular API only instead of checking the whole code and troubleshoot.
•Please review and let me know your approach on how you will implement this.
•We will require an email stating the approach, but I understand that outside communication is not allowed; therefore, please share the detailed version of your approach here on chat.
•Once we are satisfied with your approach, we can talk Further.
•I will provide you with credential to take a look at our current system.