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.
Spécialisation Requirements Engineering: Secure Software Specifications
From Customers to Secure Software Products. This specialization helps learners to create secure software from beginning to end of development.
Offert par
Spécialisation Requirements Engineering: Secure Software SpecificationsCompétences que vous acquerrez
Comment fonctionne la Spécialisation
Suivez les cours
Une Spécialisation Coursera est une série de cours axés sur la maîtrise d'une compétence. Pour commencer, inscrivez-vous directement à la Spécialisation ou passez en revue ses cours et choisissez celui par lequel vous souhaitez commencer. Lorsque vous vous abonnez à un cours faisant partie d'une Spécialisation, vous êtes automatiquement abonné(e) à la Spécialisation complète. Il est possible de terminer seulement un cours : vous pouvez suspendre votre formation ou résilier votre abonnement à tout moment. Rendez-vous sur votre tableau de bord d'étudiant pour suivre vos inscriptions aux cours et vos progrès.
Projet pratique
Chaque Spécialisation inclut un projet pratique. Vous devez réussir le(s) projet(s) pour terminer la Spécialisation et obtenir votre Certificat. Si la Spécialisation inclut un cours dédié au projet pratique, vous devrez terminer tous les autres cours avant de pouvoir le commencer.
Obtenir un Certificat
Lorsque vous aurez terminé tous les cours et le projet pratique, vous obtiendrez un Certificat que vous pourrez partager avec des employeurs éventuels et votre réseau professionnel.
Cette Spécialisation compte 5 cours
Requirements Gathering for Secure Software Development
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.
Requirements Elicitation: Artifact and Stakeholder Analysis
In 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 product that was (if there was one) and then learn about the system to be. Oftentimes, you'll find yourself in an environment you know nothing about! This course will help you find ways to learn about the domain, the system that was, and the system to be. Please review: "Who this class is for to determine if you are ready to take this graduate level course".
Requirements Specifications: Goals and Conflict Analysis
In 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 learn. Use cases can be in diagram and written form. Then- the villains enter- misuse cases and abuse cases are discussed in how we can deal with them in a Requirements environment. In gathering requirements, you'll have many questions remaining. Often this leads to the need of more interviews and group sessions. We'll go through how to handle group meetings, dealing with inconsistency, and handling conflict between stakeholders.
Software Requirements Prioritization: Risk Analysis
Risk 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 alternatives, you must consider risks. In this course, we'll look into how to analyze risk, evaluate risk, document risks, and use this information for prioritization of requirements. Qualitative and Quantitative approaches will be covered.
Enseignant
Kristen Walcott-Justice
Assistant ProfessorÀ propos de University of Colorado System
Foire Aux Questions
Quelle est la politique de remboursement ?
Puis-je m'inscrire à un seul cours ?
Oui ! Pour commencer, cliquez sur la carte du cours qui vous intéresse et inscrivez-vous. Vous pouvez vous inscrire et terminer le cours pour obtenir un Certificat partageable, ou vous pouvez accéder au cours en auditeur libre afin d'en visualiser gratuitement le contenu. Si vous vous abonnez à un cours faisant partie d'une Spécialisation, vous êtes automatiquement abonné(e) à la Spécialisation complète. Visitez votre tableau de bord d'étudiant(e) pour suivre vos progrès.
Une aide financière est-elle possible ?
Puis-je suivre le cours gratuitement ?
Ce cours est-il vraiment accessible en ligne à 100 % ? Dois-je assister à certaines activités en personne ?
Ce cours est entièrement en ligne : vous n'avez donc pas besoin de vous présenter physiquement dans une salle de classe. Vous pouvez accéder à vos vidéos de cours, lectures et devoirs en tout temps et en tout lieu, par l'intermédiaire du Web ou de votre appareil mobile.
Quelle est la durée nécessaire pour terminer la Spécialisation ?
Approximately 21 weeks
What background knowledge is necessary?
None although a vague knowledge of programming and the software development process is helpful.
Do I need to take the courses in a specific order?
No. Courses can be taken in any order according to your interests and needs.
Puis-je obtenir des crédits universitaires si je réussis la Spécialisation ?
At this point in time, university credit is not offered.
What will I be able to do upon completing the Specialization?
You will have the background knowledge necessary to work in product management and requirements engineering overall. You will also benefit as a developer, tester, QA analyst, and designer, as all these are closely tied to software requirements and often rely on the product created in this software development lifecycle phase. As this is a graduate level course, it's also a good preparation for graduate studies, especially those that focus in Software Engineering.
D'autres questions ? Visitez le Centre d'Aide pour les Etudiants.
