From the course: Software Design: From Requirements to Release

Using the GitHub repo

From the course: Software Design: From Requirements to Release

Start my 1-month free trial Buy for my team

Using the GitHub repo

“

- [Instructor] There are two sets of references that I have provided in this course. First set has the code, and the second set has development artifacts such as UML models and UI mock-ups. Both are available in Git repo. Let us first look at the code. The Git repo for this project is set up so that whichever lesson you go to, you can find its corresponding code in one of the branches. For example, when you are reviewing the seventh lesson in chapter two, you can go to 02-07b. The lesson ends with the code being check in to 02-07b. In some cases you will find that there is no b, or beginning branch, and only e, that is end branch, and that is because I have simply walked through the code without making any changes. I have created these branches so that you can see the code going through various stages. You will find me working off of master branch in some cases, especially when I'm pushing the code to production, and that is because I have set up Jenkins to pull the code from master. In some cases I have also demonstrated committing the code to one of the lesson branches locally, but then I have merged the changes to master before pushing them to production. These scenarios demonstrate various ways in which you may manage your code. The other development artifact has UML models and is available here, at the root, in this PDF. This PDF is structured so that you can refer to various diagrams shown in the video using the lesson name. For example, you may find the use case diagram discussed in lesson titled Elicit and Specify Requirements in the chapter with the same name.

Contents