20170927 [ESDEBP] Draft of two pages for a chapter proposal.
Purpose of the meeting.
Review the proposal of a chapter for ESDEBP and distribute activites to construct the two pages document required by the "Call for chapter"
Agenda
- ESDEBP Review
- Summary of the proposal.
- Draft on ShareLateX.
- Next Step (Strategy).
Development
ESDEBP Review
1.ESDEPBP: Experimental Studies on Development of Executable Business Processes
Book Publication
The book will be published by Springer (final approval pending).
Topics of Interest
- Combination of Process Elicitation and Requirements Engineering approaches
- Understandability of Executable Business Process Models by different stakeholders
First date
2017-10-15 Submission of a two-page summary
2. Summary of the proposal
An experiment to evaluate the level of comprehension of the requirements, from a case study with a BPMN model, or with an Use Case Specification or with both.
Type of experiment.
Comparison of levels of comprehension of requirements, depending of the source artifacts used to describe them. The questions will be oriented to completeness and correctness.
Additionally we will collect data to study the reasons for the results found, by means of:
-
The "think out loud" strategy to study how people understand and relate the artifacts, what is the flow of analysis people make when reading the artifacts and so on.
-
Applying open questions about perception, facilities or difficulties found in the artifacts, to know how to improve the process for understanding requirements.
CaseStudy
In the Stephen Schach' book, "Classical and Object-Oriented Software Engineering", there are two case studies that can be used to the experiment:
MSG Foundation: A foundation that offers financing and grants for buying a house, to newly married couples with scarce resources.
Chocoholics Anonymous: An organization that offers, by an affiliation, healthcare professionals access for controlling the chocolate addiction.
The original version of these case studies is too long for the experiment, so @olvegam will resume them and will traduce to Spanish too. The length must be of middle page with two paragraphs: The first one with a context and the last with the process.
Artifacts:
- Text with the Case Study.
- Use Case Specification (diagram + RUP format - @olvegam will search in Scott Ambler:Effective Use Cases).
- BPMN TO-BE.
Pilot test.
Applied to the professors
- Andrea Herrera
- Oscar Gonzalez
Population.
Master students of the professor Mario Sánchez' course.
Groups
-
Group 1
- A case study in natural language
- The Use Case specification
-
Group 2.
- A case study in natural language
- A BPMN model (TO-BE)
-
Group 3.
- A case study in natural language
- The Use Case specification
- A BPMN model (TO-BE)
Questionnaire
The three groups will be given the same set of questions. Some questions will contain use case diagrams that the participants will have to evaluate in order to decide whether or not they result from the requirements expressed in each of the delivered models (natural language form and BPMN diagrams).
The questionnaire must have demographic background.
ShareLatex
3. Draft on@olvegam will send an e-mail to the editors asking the format for the chapter summary: Springer, double column IEE or ACM format?
4. Next Step (Strategy).
Co-authors' tasks.
Coauthor | Task |
---|---|
Olga Lucero |
|
Jaime Chavarriaga | Related work |
Mario Sánchez | Revisión de artefactos |
Mario Linares Vásquez | Experimental Design |
Next meeting
Friday 6 October, 2:00pm - ML-651 (@olvegam reserve)
Bring:
Two pages summary of the chapter proposal
Case studies in original
Case studies summarized and traduced to Spanish.