Wessel373 / CMPG-323-Overview-27644227-

0 stars 0 forks source link

CMPG-323-Overview-27644227

The project will consist of 5 smaller projects that is as follow:

Each of the projects will be submited at a due date. Projects have related tasks that is placed in sprints format. These tasks must be done before the work is done on the project as it acts as trainning to be able to do the projects.

The Related tasks is categorised as follow:

Each Task has the following Attributes per tick logged:

Views of the project:

The Project has four views to manage and track the progress of the project:

Branching strategy of the Project

The Project will use a trunk based branching stategy

Trunk Based branching uses the approach to have one main master branch and the user only branches out for a single feature per branch. While the master branch is always ready for production.

Reasoning for the selected branching strategy is it keeps the merging of branches simple it helps to keep the code relavant by doing frequent and small merges

Git Ignore

Git ignore will be used to exclude dependencies and compiled files that is not necessary to be on the repositry. For every file in the project that is not necessary those files would be deleted once and then add a git ignore for that file. So that we do not need to by hand delete the same file over and over when a commit was pushed to the project's master branch.

Repositries OutLine

The Repositories consist of 5 seperate repositories as the following(Click on the links to navigate to the repositories):

How will credentials be stored:

RPA installation steps Link

Geek for Geeks link to RPA steps for installation