Salion case study

1
Examination Assistant
Markus Jevring, Erwin Kroon Group 2
2
Outline

• Case Description
• Adopted PLE Process
• Domain Engineering
• Requirements
• Use Cases
• Feature Diagram
• Domain Variability Model
• Conclusions

3
Case Description

• Examination Assistant
• Automated Examination System
• Working environment
• University courses, driver lessons, IQ-tests
• Touch screens, sound input, normal computers
• Features
• Test taking,
• Test monitoring
• Automatic grading

4
Adopted PLE Approach

• Steps taken
• Requirements
• Variabilities
• Use Cases Diagram
• Feature Diagram
• Domain Variability Model
• Definition of commonality
• Binding time
• Variation point, variant

5
Domain Engineering Variability (1/2)

• Variation points
• Test Type
• Random ordered, Ordered, Adaptive
• Question Grading Type (internal)
• Machine gradable, Human gradable
• Question Type
• Open questions (commonality), Multiple choice
• Test Help
• Dynamic, Static, Live, (none)

6
Domain Engineering Variability (2/2)

• Test Monitoring
• Statistical, Live View, (none)
• Test Interface
• Keyboard Mouse, Touch Screen, Drawing tablet,
  Sound input
• Interface Language
• Grading System
• Country specific,
• Authentication System
• Radius,

7
Domain Engineering Use Cases (1/5)
8
Domain Engineering Use Cases (2/5)
9
Domain Engineering Use Cases (3/5)
10
Domain Engineering Use Cases (4/5)
11
Domain Engineering Use Cases (5/5)

• Usability of Use Cases
• Dependent on level of detail of Use Case
• Abstract
• Precise
• Linking Use Cases to Variants is difficult
• In the diagram
• In the Use Case description

12
Feature Diagram (1/2)
13
Feature Diagram Mutex Relations (2/2)
14
Domain Variability Model
15
Conclusions

• Definition of commonality is vague
• Use Cases are not well suited to use with SPLE
• Feature diagrams are vaguely defined in Pohl et
  al.
• An editor for feature diagrams would be nice

16
Questions