Skip to content

Agile is a broader methodology that emphasizes flexibility and responsiveness. Scrum is a specific framework within Agile that provides a structured approach to manage iterative development and collaboration.

License

Notifications You must be signed in to change notification settings

givenmnisi6/CMPG323-Overview-34292748

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

42 Commits
 
 
 
 
 
 

Repository files navigation

Overview

Repositories

In my approach to this semester I'm going to use five repositories below:

Context Diagram

Context Diagram

Regarding my project I'm going to have each repository for each project if source control is needed. Essentially I'm going to have 5 different repositories and one project where all the of them come together through one "Kanban".

Branching Strategy

In all of my projects, Branching strategies will be used since I want to avoid conflicts when I am merging them and also allow a much easier integration of changes made into the main trunk. Moreover, to help organize a series of planned, structured releases. A branching strategy that I will be using in all of my projects is GitHub-Flow. Since all of the projects are individually and we have a single release version for each of our projects for each repository, GitHub-Flow is the winner for me. GitHub Flow is a simple and effective way to support continuous deployment and release. It gives me a delivery-focused project as possible.

Implementation

Most of my Implementation I will be using branches after major changes I push to my main branch and delete the branch I created.

  • The main is being branched to the feature branch, then code is added to the feature branch.
  • A pull request is created and pushed to pre-production while adding things and fixing bugs, when I'm content with the release I merge back to main.
This strategy eliminates a lot of room for error, if something goes wrong, I can simply roll back to the previous version.
  • The GitHub Flow branching strategy will consist of the following branches:
  • Master (main) - for production purposes
  • Feature/task - for the development of new features
  • Hotfix - to assist when there's a bug that has been found and needs fixing in production. A hotfix originates from the master branch and merges back into the master and develops.

.gitignore files

  • In my API Project, I'll use gitignore to ignore the JSON files anytime I save code in a public repository and want to secure it so that it’s not publicly accessible.
  • Under my MVC Web Application, I intend to use gitignore to ignore the bin, obj folders and JSON files; I just want the source code in source control. Moreover I will store all the Connection Strings in .JSON file and gitignore them.
  • In terms of RPA & Testing , I'm going to gitignore files like entities, local, templates, screenshots, settings, tmh
  • In Reporting project there won't be files that will be ignored.
  • Storage of Credentials

    In terms of storing sensitive credentials:

    • I’ll utilize a .JSON file in API Development and Standards & Patterns.
    • In Testing & RPA, credentials will be stored in UiPath Orchestrator.
    • In Reporting there will not be credentials that need to be stored.

    Reference List

    About

    Agile is a broader methodology that emphasizes flexibility and responsiveness. Scrum is a specific framework within Agile that provides a structured approach to manage iterative development and collaboration.

    Topics

    Resources

    License

    Stars

    Watchers

    Forks

    Releases

    No releases published

    Packages

    No packages published