2018‐01 Introduction
This wiki describes the system. Includes the complete software requirements, design decisions, architectural design and the steps followed to implement the Multi-cloud WebApp Attendance
The wiki is based on a class final project for the Masters degree of Service oriented computing in Auckland University of technology AUT. The report gives the implementation details of a composite web service that uses orchestration across several web services to mark the class attendance.
Mulesoft repo: GitHub Repo Integration project project used MuleSoft and some microservices communication techniques
For the architecture i used Visio
image is uploaded to my personal account in www.imgur.com
I missed that some of my colleagues were working on their own creating a full AWS infrastructure. I re-created the infrastructure architecture based on documentation from this wiki and copies I kept in my GDrive.
Developed to replace the manual attendance system, making it more secure and reliable.
- The lecturer uses the Admin module log in to the Attendance Webapp system, generate a one-time authentication code
- Students can access the Attendance Webapp on their mobile phones or any device, enter the authentication code, scan the QR code and log their Class attendance
- University Staff has access to student attendance records, reports and can add papers, rooms, and users
The intended audience of this system are:
- Students
- Lecturers
- University staff officer
An initial brain-storming marked the commencement of the project. The Figure 1 represents current attendance sheet that was analyzed and the basic functionality required was recognized. Based on the analysis of the attendance sheet, a mind map, as represented in Figure 2, was created to understand how the same process could be automated and what services would be needed and how they could be called.
 |
 |
|---|---|
| _Figure 1: Attendance Sheet | Figure2: High level view Sketch _ |
the process is paper based. The information found in the sheet of paper is
- Name of university
- title verification attendance
- Code of Class and name of Class or paper
- year
- code class again
- Programme with empty info
- stream
- status
- semester
- student id
- signature
- name
- date
the paper sheet though effective is unclear and rather useless. a system can do a better job and impose more strictness
Figure 2 shows brainstorming of the high level architecture. The goal of the app is to integrate a Java Web App with AWS, Mulesoft, a private cloud, Public REST services and public WSDL SOAP services
The next step taken was to determine the platform to be used to develop this project. It was unanimously decided to use Visual Studio Online (2023 called Azure DevOps) and Scrum methodology was used to plan how to manage the work items. As an initial step, all the team members identified the different user stories that would be addressed in this project. Of all the identified user stories, the ones that were most relevant to the project were identified. Depending on the timeframe, the set of user stories were categorized in 3 iterations or sprints, seen in Figure 3.
Figure 3: Backlog for Attendance System
The different user stories were segregated and organized into sprints for delivery. Depending on which user story was accepted and assigned to a sprint, the board was updated. Figure 4 represents the scrum board.
Figure 4: Scrum Board depicting Work in progress