Audit Management System

Team: Pod - 1

Team Members :
Mentor : Mr.Kannadhasan Mariappan
Lakshmi Priya T (919909)
Trainer : Mr.Sumit Kumar

Coach : Ms.Jenifer Nancy

Niranjana S R (918515)

Mayank Pant (919655)

Agenda

● Overview
● Design
● Modules
● Deployment
Overview

● The main objective of Audit Management System is to manage audits of a

firm handling various types of audits with each having their own checklists.
● A unique ID is generated for each audit with remedial messages.
● This application has four microservices namely Authorization, Benchmark,
Severity,Checklist microservice.
● An User Interface is designed in the name of portal microservice.The
designed User Interface is a client MVC Application.
Project Architecture

Audit Checklist

Client application Authorization Audit Benchmark

(MVC)

Audit Severity
Audit CheckList Microservice

● Intent of this microservice is to display the list of audit checklist questions

based on the audit type given by the user.
● It uses post method for authorizing JWT and also adds the audit type in the
body.
● Input of audit type is either internal/SOX.
● Audit checklist questions are outputted based on the audit type.
Audit CheckList Microservice
Authorization Microservice

● Authorization Microservice functions to authenticate and authorize the user.

● User Credentials are passed to the authentication manager.
● UserDetailsService will get the data from the database.
● JWT token is generated and returned to the user.
● Each token lasts 30 minutes after it being created.
● Upon each request, token is added to the header for validation.
● If the token is invalid, i.e after 30 minutes the session automatically closes,
the user needs to login again for further processing.
Authorization Microservice
Audit Benchmark Microservice

● This Microservice provides acceptable benchmark value for every audit type.
● Service class has getBenchMarks method which returns all the records that are
stored in the database.
● Controller class is autowired with AuditBenchMarkServiceImpl and
AuthorizationClient.
● At controller, authorization is done with the help of requestTokenHeader which is
added in the header of each request.
● The controller returns a list of Audit Benchmark (audit type and Acceptable
benchmark value of number of questions whose answers can be No ).
Audit Benchmark Microservice
Audit Severity Microservice

● Audit Severity microservice will get input as a request from checklist,

about the project details and questions.
● It calls Audit Benchmark to get acceptable benchmark values i.e the
number of questions whose answers can be No.
● Then it calculates number of “No” and check for the given condition.
● Based on the condition, it returns project execution status and the duration
in which remedial action should be taken which is then displayed in Portal.
Audit Severity Microservice
Audit Management Portal

● Audit management portal communicates with all the other microservices.

● It allows users to login to the system.
● It acquires set of details from the project manager.
● According to the details given, it invokes audit severity microservice and
generates status.
● It displays project execution status in the UI.
Audit Management Portal
Thank You