Assessments and peer reviews will allow you to explore challenges within software requirements elicitation, development, writing, and management. Assignments will be based on described "wanted" products. Discussion is also a key component- make use of the forums!
Requirements Engineering: Secure Software Specifications Specialization
From Customers to Secure Software Products. This specialization helps learners to create secure software from beginning to end of development.
About This Specialization
This specialization is intended for software engineers, development and product managers, testers, QA analysts, product analysts, tech writers, and security engineers. Even if you have experience in the requirements realm, this course will expand your knowledge to include new viewpoints, development styles, techniques and tools. For anyone seeking a graduate degree, certificate, or professional degree in computer science, these courses will additionally give you a broad understanding of how requirements engineering is performed and help you get a first foot forward into your upcoming careers. The Software Requirements specialization focuses on traditional software requirements elicitation and writing techniques, while also looking at requirements from a security standpoint. In traditional methods, non-functional requirements, such as security, are often ignored overall. In this specialization, students will be introduced to ways of eliciting requirements from stakeholders, how to analyze these requirements, conduct risk mitigation and analysis, prioritize requirements, document, and bring security concerns into the software lifecycle early on.
Follow the suggested order or choose your own.
Designed to help you practice and apply the skills you learn.
Highlight your new skills on your resume or LinkedIn.
- Beginner Specialization.
- No prior experience required.
Requirements Gathering for Secure Software Development
- 4 weeks, 1-2 hours a week
About the CourseIn 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 go
Requirements Elicitation: Artifact and Stakeholder Analysis
- 4 weeks of study, 1-2 hours per week
About the CourseIn Elicitation: Artifact and Stakeholder Driven Analysis, you will learn to use both recorded and presently unrecorded knowledge in your elicitation techniques. As you get started in finding out about the new product, you must first learn about the
Requirements Specifications: Goals and Conflict Analysis
- 4 weeks, 2-5 hours/week
About the CourseIn Requirements Goal Development and Language Analysis, we move from the spoken word to precise writing. A first step in this is writing goals. We will talk about goals used in requirements engineering and, from this, writing use cases from what we lea
Software Requirements Prioritization: Risk Analysis
- 4 weeks, 1-2 hours per week
About the CourseRisk Analysis, Assessment, and Prioritization looks at how you can manage conflicts at system levels, but it can also be applied to lower level assessments. How do you manage and document conflict, along with alternatives? In analyzing alternati
SRS Documents: Requirements and Diagrammatic Notations
- 4 weeks, 1-2 hours/week
About the CourseAs requirements are being gathered and prioritized, they also need to be documented. In Diagrammatic Notations and Software Requirements Specification Writing, we discuss and practice the process of turning requirements into something readable to the cust
More questions? Visit the Learner Help Center.