Skip to content
BestCerts
Search
Generic filters
Exact matches only

Requirements Gathering for Secure Software Development (Coursera)

Rate this post

In Software Requirements Elicitation for Secure Software Development, we’re going to discuss the overall software requirements process as it applies in waterfall, spiral, and agile models. You’ll learn about each of these processes and your goals as a software requirements analyst.

This is not an easy task! Who do you talk to, when, and what kind of knowledge are you trying to obtain, in any software life cycle? How do you handle obstacles as you go?

These are the questions we will focus on answering in this specialization.

Who is this class for: This is a graduate level class and can prove useful to those just entering the software engineering process, as well as those who have years of experience. Coding is not needed. Software engineers, managers, security engineers, technical writers, testers, and many more can learn much from these lessons in gaining a better understanding of how software requirements tie to your jobs. You will also gain extended views compared to the software processes your companies currently use. This specialization is a beginning course into Software Requirements and introduces fundamental software engineering lifecycle comparisons, applied to the roles of the requirements analyst. This is also a course in the Engineering Secure Software Requirements Certificate, which can be used as a professional certificate or as a start toward further graduate studies in Computer Science or Software Engineering.

Course 1 of 5 in the Requirements Engineering: Secure Software Specifications Specialization.

Syllabus

WEEK 1

The Software Requirement Specification Process and Cost

Software Requirements are a vital part of the Software Development Lifecycle. While there are many ways to go about collecting and recording requirements, the cost of bad requirements is high. Here we discuss what Software Requirements Specifications are and some challenges in writing them well.

Graded: Software Specification Process

WEEK 2

Starting to Build Requirements- What does the customer want?

We need to figure out what the customer wants. And moreso- what they need! How do you develop a relationship with you customers and learn about the overall domain and potential solutions? Here you will learn about the requirements engineering process, what it entails, how to develop a relationship with your customer, and some tips to succeed early on.

Graded: Requirements Engineering

WEEK 3

Software Lifecycles

Not all requirements documents are created equally- if at all (formally). How you work with requirements partially depends on the software lifecycle used. Here we learn about the different software development lifecycles and discuss how they affect the requirements we produce.

Graded: Software Lifecycles

WEEK 4

Goals and Models for Elicitation

To increase flexibility to change in software development, the agile lifecycle was produced. The agile process much changes how we deal with requirements. We discuss these challenges and your role as a requirements analyst. We also begin to analyze the types of statements that you want to form as you elicit data to move towards clarity.

Graded: Goals and Models

ENROLL IN COURSE