Quick questions on Eliasson et al. reading
Usual disclaimer: Being able to answer these questions does not prove that
you remember the reading perfectly! But at least, not being able to answer
them does suggest you should reread it.
There's no automated checking of these: just see if you could answer each
question. If not, see the page indicated (page numbers
are given in terms of the PDF document, e.g. "p2" has 434 at the top) -
though in this case, some of these questions have more holistic answers.
- What is agile development? (covered in lecture, but essential to
understand here!)
- What is a mechatronic system? What is the broader
domain discussed in this paper, and why is software relevant?
- Why does the company concerned want to use an approach that
combines agile development with model-driven development?
- What is "MIL testing" and how does it fit into the overall development
approach described? (p4)
- What are the research questions addressed in this paper? (Make sure you
understand what each means!) (p5)
- The paper refers repeatedly to "assumptions". How? What is their
importance? (throughout, especially p7)
- Describe the two main case studies. What role did "plant models" play
in each? (p8ff)
- What do the authors say about the pros and cons of the use of plant
models and MIL testing? (p12ff)
- "Agile" means many things to many people. What does it mean to these
authors? (throughout...)
This page is maintained by
Perdita Stevens (
perdita@inf.ed.ac.uk)
