Requirements Elicitation: Artifact and Stakeholder Analysis

Requirements Elicitation: Artifact and Stakeholder Analysis

This course is part of Requirements Engineering: Secure Software Specifications Specialization

Instructor: Kristen Walcott-Justice

Access provided by CalArts

9,074 already enrolled

4 modules

Gain insight into a topic and learn the fundamentals.

122 reviews

Beginner level

No prior experience required

2 weeks to complete

at 10 hours a week

Flexible schedule

Learn at your own pace

4 modules

Gain insight into a topic and learn the fundamentals.

122 reviews

Beginner level

No prior experience required

2 weeks to complete

at 10 hours a week

Flexible schedule

Learn at your own pace

Skills you'll gain

Details to know

Shareable certificate

Add to your LinkedIn profile

Assessments

14 assignments¹

AI Graded see disclaimer

Taught in English

See how employees at top companies are mastering in-demand skills

Learn more about Coursera for Business

logos of Petrobras, TATA, Danone, Capgemini, P&G and L'Oreal

Build your subject-matter expertise

This course is part of the Requirements Engineering: Secure Software Specifications Specialization

When you enroll in this course, you'll also be enrolled in this Specialization.

Learn new concepts from industry experts
Gain a foundational understanding of a subject or tool
Develop job-relevant skills with hands-on projects
Earn a shareable career certificate

There are 4 modules in this course

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".

One step of gathering domain knowledge and knowledge of the system that was and the system to be is through artifact-driven elicitation. Here we will discuss what artifact-driven elicitation entails, how to go about learning background from the stakeholders, and methods to obtain and deal with the data.

What's included

4 videos5 readings4 assignments1 discussion prompt

4 videos Total 23 minutes

Artifact-driven elicitation- What is it? 7 minutes
Artifact gathering - Questionnaires 7 minutes
Repertory grids 4 minutes
Card sorts/conceptual laddering 4 minutes

5 readings Total 85 minutes

Artifact-driven Elicitation - Slides 20 minutes
Get help and meet other learners in this course. Join your discussion forums! 5 minutes
Artifact Gathering - Slides 20 minutes
Repertory Grids - Slide 20 minutes
Card Sorts / Conceptual Laddering - Slide 20 minutes

4 assignments Total 120 minutes

Artifact Driven Elicitation 30 minutes
Artifact Driven Elicitation Challenge Questions 30 minutes
Artifact Gathering Practice Questions 30 minutes
Practice Questions Repertory Grids 30 minutes

1 discussion prompt Total 30 minutes

Who are your Stakeholders? A Meeting Scheduler Example 30 minutes

As you talk with customers early on, developing storyboards and scenarios help. They are easily communicable to both the customer and later to developers and work in all software development lifecycles. Mockups and prototypes can also be used- CAREFULLY. Here we explain these concepts along with their large benefits and dangers.

What's included

4 videos4 readings3 assignments1 peer review1 discussion prompt

4 videos Total 31 minutes

Storyboarding 9 minutes
Scenarios 8 minutes
Scenario Advantages and Disadvantages 7 minutes
Mockups and Prototypes 7 minutes

4 readings Total 83 minutes

Storyboarding 5 minutes
Scenarios / Scenarios Advantages & Disadvantages - Slides 8 minutes
Requirements Elicitation: Towards the Unknown Unknowns 60 minutes
Mockups and Prototypes - Slides 10 minutes

3 assignments Total 90 minutes

Storyboarding and Putting a Project Together 30 minutes
Challenge/Practice Questions Storyboarding/Scenarios 30 minutes
Challenge questions Mockups/Prototypes 30 minutes

1 peer review Total 105 minutes

Storyboards and Scenarios 105 minutes

1 discussion prompt Total 10 minutes

Storyboarding Discussion 10 minutes

In understanding the system to be and the system that was, existing knowledge of the domain and current scenarios needed are helpful. These can be related back to models. This lesson discusses knowledge that can be obtained, from what resources, and how that can be mapped to existing models for help in further elicitation.

What's included

2 videos3 readings3 assignments1 discussion prompt

2 videos Total 13 minutes

Knowledge Reuse 6 minutes
Meta-Model Usage and Reuse Pros and Cons 7 minutes

3 readings Total 180 minutes

Knowledge Reuse - Slides 30 minutes
Meta-Model Usage and Reuse Pros and Cons - Slides 30 minutes
Inferring declarative requirements specifications from operational scenarios 120 minutes

3 assignments Total 90 minutes

Reusing Existing Knowledge 30 minutes
Practice Questions for Knowledge ReUse 30 minutes
Challenge Questions Meta-model Useage 30 minutes

1 discussion prompt Total 10 minutes

Discussion Knowledge Reuse 10 minutes

Knowledge of the system-as-is and the system-to-be can be obtained through interviews. While the concept of conducting an interview seems easy overall, an efficient and effective interview is challenging to conduct. Here we'll talk about guides to meeting effectiveness and guidelines for conducting a useful interview, specifically for determining what the stakeholder has and needs.