Skip to content

CodingParkFunSeries/AttendanceManagementSystem

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

22 Commits
 
 
 
 
 
 

Repository files navigation

Project - AttendanceManagementSystem

Scope

Scope of the problem - Track the attendance of students

Technologies

  • Front-end : React
  • Backend : Java
  • Database : Mongo DB
  • Mobile Application : Android, IoS

Tasks

DAY 1

Task 1

Write down the possible features in attendance management system (AMS). Think out of box for any possible feature.

Detailed steps :
  1. Clone the AMS Github repo
git clone https://github.com/CodingParkFunSeries/AttendanceManagementSystem.git
  1. Direct check-in to master is not allowed, so create a branch in format users_<Github user Id>_task e.g for me it will be users_ajay109458_createFeatureSuggestion
git checkout -b users_ajay109458_createFeatureSuggestion
  1. Now there is a FeatureSuggestion folder create an md file in format <your name>.md ( learn to write md file) about possible features in the attendance management system.
  2. Commit and push you changes and raise a PR.
git add . 
git commit -m "your message for commit"
git push

Expected learning - Github basic commands and how to write md files.

Task 2

Select MVP features to keep application simplistic so that everyone has an efficient learning and new students can refer it in future for learning.

DAY 2

Task 1

Think of the entities in the system.

Task 2

UML and Sequence diagram of the application.

Task 3

Flow diagrams of the different flow in the application.

DAY 3 - Day 6

Task - Coding

  • Application should not consit of hard coded configuration. E.g. AMS can support any other school, new classroom, new student.
  • Naming convention should be followed. Every variable, method and class should be properly named.
  • Proper documenation for every contribution towards the project.
  • Documenation should mention the resources for learning the technologies that you have used in application.
  • Everyone will write automated tests - Unit test and end to end test for the code you have contributed.

DAY 7

Task 1

Demo of the application.

Task 2

  • Share the documentation of the work.
  • Share the learning during the application
  • Share your experience.

Expected Learning

  • Gather features of the application.
  • Design an application.
  • Learn to work with a team.
  • No fear to learn new technology anytime.

Feel free to share you suggestions.

Releases

No releases published

Packages

No packages published