top of page

Software Design Documents

Below is a collection of different documents created and used during coursework and development of software.
The button takes you to my git repository where you can view any code created during my work.

AGILE-ility is important

There are many different methodologies in the development of software. The Agile method is, in my opinion, one of the best. The power point describes the agile method, its roles, and a comparison to the waterfall method.  Then there's the product owner, the scrum master, the developer and the tester. Each document describes what the roles do and why they're important to the agile method. There's, also, a final reflection to the agile method.  You'll find them in a zip file together.

Putting the R in BRD

Business Requirements Documents were another thing we learned to do in class. This particular one is the requirements document for a company that wants an application to help them run their business. The business is about helping newer drivers with their driver's tests. The BRD goes over the purpose of the projects, its designs, constraints, security and a lot more.

What was in the Design Document again?

Software Design Documents are important to any software being created. Or at least documents like them. They help keep the development on track with what was chosen already. This SDD is for the development of an environment for a web based application. It goes over the design, the constraints, architecture, models, tools, recommendations, and other things.

bottom of page