[MUSIC]
Hi, I'm Bradley Poulette.
I have worked as a project manager on many software projects in the past and
have studied a broad range of techniques relating to the field
here at the University of Alberta.
I am incredibly passionate about software product management and
I'm excited to share that passion with you.
In this lesson, I'm going to cover why requirements are important
when working on software projects.
I'm going to start by outlining some of the main reasons why we need requirements,
as well as some examples of what happens when you lose focus on those requirements.
So let's begin with why we need requirements.
Requirements are a set of specific descriptions of your client's needs.
I'll cover this in more detail in the Client Needs and
Software Requirements course, but for now, the client is the person or
group of people who want the software product built in the first place.
Requirements combined with processes
are the backbone of any successful software project.
So what makes them so important?
Here's an example of a list of requirements
for a great social network app.
The user could:
store user profiles on their data,