Skip to content

2018‐10 Conclusion & Future Work

Andres Leon Rangel edited this page Jul 20, 2023 · 1 revision

6. Summary

6.1 Learning Experience

The Attendance Webapp application has opened a great avenue of learning for the entire team. Once the brainstorming was done and a business plan was finalized and the scrum methodology was incorporated to develop the main layers of the solution which have been integrated to developing the functional module. It has not only aided in refreshing the concepts associated with the development of software but also helped in learning some of the latest technologies, thus providing each member of the team to have hands-on experience. The latest technologies that we have learnt while working on the Attendance Webapp are J2EE with primefaces, NodeJS, Docker container automation, Mulesoft integration, DynamoDB and Lambda.

6.2 Features Backlog

1. Type-as-you-go information look ups in Web Applications (i.e. real-time query to list room service to fetch room information).

2. User level authorization of Microservices (currently access privileges same across student/lecturer/admin).

3. API Keys on API Gateway for System to System interactions (i.e. composite service needs privileged access to perform some actions/lookups).

4. Stricter validation of information passed into Microservice operations.

5. "Pretty" date formatting in front-end applications.

6. Verify class is occurring today within a specific time-period before attendance can be registered (requires enhancements to Paper Microservice).

7. Allow a reason to be entered with absence records.

8. Search/filter criteria drop downs for admin Web App.

9. Add pagination support to Web Apps and Microservices.

10. Add checks and constraints for active/inactive flags (i.e. an inactive user shouldn't be able to create any records in the system, or register for any papers).

7. Conclusion

The Attendance Management System makes use of mobile device and web applications in a multicloud environment. The mobile device allows the students to log in their attendance and the data is maintained by the web application. The genuineness is maintained by incorporating the authentication code that is generated by the lecturer.

The work presented here puts forth the different possibilities associated with multi cloud integration and the use of an ESB such as mulesoft for service orchestration. There can be some straightforward extensions that can be added to the current developed system. Automation of containers in docker for testing, optimisation of resources to enhance the performance of the web services and increasing interoperability through use of API integrations are considered prospective future work.

  • Agile methodology using latest cloud technologies shows reduction in effort and delivery time​

  • Future work could be to containerise the application in Docker hub for quicker deployment​

  • Java libraries to invoke REST services are not standardized and it has steep learning curve