This document discusses the design principles of advanced task elicitation systems. It begins with an introduction that outlines the motivation and challenges of manual task elicitation in software development. It then reviews related work on task elicitation systems and the need to evaluate their design principles empirically. The methodology section describes a design science research approach used to conceptualize and evaluate an artifact called REMINER. Evaluation results show that semi-automatic task elicitation and leveraging imported knowledge bases can significantly increase elicitation productivity compared to manual elicitation. The discussion covers limitations and opportunities for future research at the intersection of task elicitation and software development processes.
The document provides an overview of an information systems project presented by Mr. Sagar Ajit Waghela and Mr. Nikhil Sharma. It thanks the ICAI for the opportunity and guidance provided. It then discusses key concepts in information systems including the system development life cycle, roles of various participants, and the main phases and activities involved in planning, analysis, design, implementation, and support of an information system project.
This document provides an overview of the research and outcomes for developing an e-menu prototype for a Thai restaurant. [1] It reviews the research question, objectives, and framework, which focused on identifying key issues, requirements, and users' perceptions of the prototype. [2] It discusses the structure of the portfolio that will contain artifacts like system analysis documents, the prototype application, and presentations to demonstrate features. [3] The outcomes include analyzing requirements, developing the prototype, evaluating users' feedback, and recommending how to approach future e-menu development.
1. The document discusses integrated media research planning and methods, including interpretation methods like affinity diagrams.
2. It explains the affinity diagram process, which involves gathering notes from interpretation, identifying related notes, and grouping them into "blue labels", then grouping blue labels into "pink labels" and pink labels into high-level "green labels".
3. The document provides steps for building an affinity diagram, including preparing notes, adding labels, and reorganizing the diagram to incorporate new findings.
The document summarizes an intensive business analysis training course that covers topics like business analysis techniques, software development lifecycles, requirements analysis, UML modeling, use cases, and business process improvement. The 36-hour course uses industry standard tools and teaches practical skills like simulated JAD sessions and creating requirements documents. The training aims to provide entry-level business analysts and other professionals with a solid understanding of business analysis principles and the ability to apply them to real-world projects.
Quality problems related to agile methods / scalability.Darío Macchi
In this presentation we will see some problems with agile practices of quality assurance.
Then we will focus on the particular problem of non-functional requirements.
Finally we will refer to the quality problems that arise when using agile methods in large projects.
Is assumed that these practices improve the quality of a software product.
We will see that in any case there are problems in implementation, especially when scaling agile projects and take them to big projects distributed environments.
Design of an Ameliorated Methodology for the Abstraction of Usable Components...IDES Editor
The object oriented design requires that the view
element required for the design is to be abstracted from the
SRS. So it is required to transform the requirements into
object oriented paradigm and then proceed for the
development. We are intending in our ensued project, to
develop a sequence of methods in the form of methodology,
those take the requirements and then transform it into objectoriented
paradigm. We are intending to develop an automated
(with least human intervention) sequence of methodology that
takes requirements specification as input and abstracts
required elements for the object oriented system. This is a
semiautomatic methodology. In few steps of our methodology
whenever the human intervention is required the detailed
guidelines for that of the process is framed to facilitate the
human worker to take unique unambiguous decision.
This document contains a chapter from a course manual on Object Oriented Analysis and Design. The chapter discusses the inherent complexity of software systems. It identifies four main reasons for this complexity: 1) the complexity of the problem domain and changing requirements, 2) the difficulty of managing large software development teams, 3) the flexibility enabled by software which can lead to more demanding requirements, and 4) the challenges of characterizing the behavior of discrete systems. Software systems can range from simple to highly complex, depending on factors like purpose, lifespan, number of users, and role in research.
The document provides an overview of an information systems project presented by Mr. Sagar Ajit Waghela and Mr. Nikhil Sharma. It thanks the ICAI for the opportunity and guidance provided. It then discusses key concepts in information systems including the system development life cycle, roles of various participants, and the main phases and activities involved in planning, analysis, design, implementation, and support of an information system project.
This document provides an overview of the research and outcomes for developing an e-menu prototype for a Thai restaurant. [1] It reviews the research question, objectives, and framework, which focused on identifying key issues, requirements, and users' perceptions of the prototype. [2] It discusses the structure of the portfolio that will contain artifacts like system analysis documents, the prototype application, and presentations to demonstrate features. [3] The outcomes include analyzing requirements, developing the prototype, evaluating users' feedback, and recommending how to approach future e-menu development.
1. The document discusses integrated media research planning and methods, including interpretation methods like affinity diagrams.
2. It explains the affinity diagram process, which involves gathering notes from interpretation, identifying related notes, and grouping them into "blue labels", then grouping blue labels into "pink labels" and pink labels into high-level "green labels".
3. The document provides steps for building an affinity diagram, including preparing notes, adding labels, and reorganizing the diagram to incorporate new findings.
The document summarizes an intensive business analysis training course that covers topics like business analysis techniques, software development lifecycles, requirements analysis, UML modeling, use cases, and business process improvement. The 36-hour course uses industry standard tools and teaches practical skills like simulated JAD sessions and creating requirements documents. The training aims to provide entry-level business analysts and other professionals with a solid understanding of business analysis principles and the ability to apply them to real-world projects.
Quality problems related to agile methods / scalability.Darío Macchi
In this presentation we will see some problems with agile practices of quality assurance.
Then we will focus on the particular problem of non-functional requirements.
Finally we will refer to the quality problems that arise when using agile methods in large projects.
Is assumed that these practices improve the quality of a software product.
We will see that in any case there are problems in implementation, especially when scaling agile projects and take them to big projects distributed environments.
Design of an Ameliorated Methodology for the Abstraction of Usable Components...IDES Editor
The object oriented design requires that the view
element required for the design is to be abstracted from the
SRS. So it is required to transform the requirements into
object oriented paradigm and then proceed for the
development. We are intending in our ensued project, to
develop a sequence of methods in the form of methodology,
those take the requirements and then transform it into objectoriented
paradigm. We are intending to develop an automated
(with least human intervention) sequence of methodology that
takes requirements specification as input and abstracts
required elements for the object oriented system. This is a
semiautomatic methodology. In few steps of our methodology
whenever the human intervention is required the detailed
guidelines for that of the process is framed to facilitate the
human worker to take unique unambiguous decision.
This document contains a chapter from a course manual on Object Oriented Analysis and Design. The chapter discusses the inherent complexity of software systems. It identifies four main reasons for this complexity: 1) the complexity of the problem domain and changing requirements, 2) the difficulty of managing large software development teams, 3) the flexibility enabled by software which can lead to more demanding requirements, and 4) the challenges of characterizing the behavior of discrete systems. Software systems can range from simple to highly complex, depending on factors like purpose, lifespan, number of users, and role in research.
AsianPLoP'14: How and Why Design Patterns Impact Quality and Future ChallengesPtidej Team
The document discusses schemas, design patterns, and how patterns relate to schemas and learning. It notes that schemas are mental representations that allow people to recognize patterns. Design patterns aim to capture best practices and reusable solutions to common problems. When patterns are reused, it activates existing schemas and can lead to better design through experiences being shared. The document explores how pattern reuse relates to theories of schema and learning, and how patterns can be codified and shared between designers based on these theories.
In this first lecture, we discuss software quality, introduce the quality characteristic of maintainability, and argue that maintainability can be studied from four different points of view: (1) quality models, (2) good practices, (3) social studies, and (4) developers' studies. We discuss major works and results for these four points of view and show the last three can be used in the first one to build better quality models. We show that quality models are mandatory to make sense of any quality evaluation.
The document discusses the development of a Laboratory Assistant Suite (LAS) database application to manage data from a preclinical cancer model experiment involving implanting patient tumor samples in mice. It provides background on using such preclinical models for personalized cancer medicine. It describes the contributions of two research institutions (IRCC and Politecnico di Torino) to the LAS project and outlines the data flow, requirements, and database design for the LAS application.
Mouse tracking is a technique for monitoring and visualizing mouse movement and activity of the users.
This is a Comparative study of cursor movement pattern between a touchpad and a mouse devices based on patterns of cursor movement.
ATAM is an architecture evaluation method that assesses architectural decisions based on quality attribute requirements. It identifies risks, tradeoffs, and sensitivity points. The ATAM process has 3 phases - introduction, analysis and investigation, and follow up. It involves stakeholders generating scenarios, analyzing how architectural approaches address quality attributes, and identifying risks. The results include documented architectural approaches, utility trees, scenarios, and risks/tradeoffs to improve the architecture.
This document summarizes a study on the impact of classes playing roles in design patterns. The study analyzed classes playing zero, one, or two roles across six Java programs. It found that on average 8.24% of classes played one role and 17.81% played two roles. Classes playing roles, especially two roles, had significantly higher values for internal metrics like coupling and cohesion. Classes playing two roles also changed significantly more than other classes. The results confirm previous findings and justify further study into ranking design pattern occurrences based on class roles and metrics.
The document discusses patterns in software development. It begins by defining what a pattern is, noting that a pattern describes a general reusable solution to a commonly occurring problem within a specific context. It then discusses some qualities of patterns, including that they aim to enhance reusability, encapsulate design experiences, and provide a common vocabulary among designers. The document also notes that patterns aim to capture an ineffable "quality without a name". It provides examples of patterns from different programming languages to illustrate recurring solutions.
The document discusses usability and user experience (UX) in several contexts:
1. It defines usability according to ISO usability standard 9241 as how effectively, efficiently, and satisfactorily users can achieve goals within a specified context.
2. It lists 47 common usability activities including heuristic evaluation, personas, usability testing, and more.
3. It describes how to measure usability through effectiveness, efficiency, and satisfaction metrics like tasks completed, time on task, errors, and user ratings.
4. It notes that usability is complex and interdisciplinary, drawing on fields like information architecture, interaction design, industrial design, and more.
5. It suggests that
Software Engineering with Objects (M363) Final Revision By Kuwait10Kuwait10
This document provides an overview of software engineering concepts covered in various course units. It begins with introductions to approaches to software development, requirements concepts, and modeling. Key topics covered include the software development life cycle, requirements elicitation and analysis techniques, types of requirements (functional and non-functional), modeling languages like UML, and risks and traceability in software projects. The document also lists contents for each of the 14 course units.
The document outlines the engineering design process from problem identification through various phases of design and project management. It begins with problem identification, which involves defining customer needs and organizing them into a hierarchy of needs. This leads to developing a problem statement and specifying engineering requirements. Various concept generation techniques are then discussed along with evaluating and selecting concepts. Considerations for the detailed design phase include reliability, safety, and manufacturability. The document concludes with discussions on project management techniques like scheduling, communication, and presentations.
Complexity is a term very often used to express difficulties in organisational change programs or (IT related) projects. Instead of using complexity as excuse for failure assessing complexity is a much more attractive option.
The document discusses user-centric design (UCD) and user experience (UX). It defines UX and discusses how UCD focuses on involving intended users throughout the design process through iterative testing. The basic UCD workflow involves concept, research, prototyping, testing, building, and post-launch testing. It also discusses the Five Planes Model for structuring UCD and covers creating user personas and stories to understand users.
20th and last slide set of CECS 542
Recap of the 2nd half of the semester for preparing for the final
Complete course: http://foss2serve.org/index.php/Requirements_Engineering,_CSU_Long_Beach,_Penzenstadler
J.kim c.bouchard other:a study on designers mental process of information ca...ArchiLab 7
The document summarizes a study on how designers mentally categorize information in the early stages of design. Researchers conducted a study with 8 product designers who verbalized their thoughts while sketching in response to a design brief. The study found that designers employ information at high, middle, and low levels of abstraction. High and middle level information like semantics, analogies, and functions made up the majority of information used. Designers transformed information through cognitive operations of memory retrieval, association, and transformation. The study provides insight into the mental processes designers use to generate and develop early design concepts and sketches.
Slides from the talk "Model-Driven Engineering: a first glance at a ¿new? way of conceiving software development". Summer course on "Data Management". University of Santander (Spain), July 2011)
The role of systems analysis in co-learning. Walter RossingJoanna Hicks
Systems analysis can play different roles in addressing problems depending on the type of problem and level of agreement. Co-learning through boundary work between science and decision-making can help address "messy" problems with many stakeholders. Effective strategies for co-learning include meaningful participation in setting the research agenda, arrangements for accountability, and producing boundary objects that can be understood from different perspectives. Challenges for systems science include meeting requirements for credible, salient and legitimate knowledge while accommodating multiple disciplines and stakeholders.
This document introduces architectural modeling and discusses key concepts including:
- Architectural models capture principal design decisions about a system's architecture. Architectural modeling is documenting these decisions.
- When modeling, architects choose what to model based on stakeholder concerns, desired level of detail, and cost/benefit. Aspects that are more important to stakeholders receive more modeling depth.
- Common things modeled include architectural elements like components, connectors and interfaces, as well as static and dynamic aspects, and functional and non-functional properties. Models are organized into views that focus on specific concerns or viewpoints.
iBeaken is a visitor engagement and activation program making it possible to publish content around heritage, nature, tourism, museums to the visitor's own smartphones.
Presentación aldea de la ilusión de microsoft office power pointEscuelas para la Vida
La Aldea de la Ilusión, un proyecto pedagógico pendiente de ESCUELAS PARA LA VIDA.
Con vuestro apoyo se podrá realizar en un futuro cercano. Http://escuelasparavida.blogspot.com
This document is a lesson on Rails3 that discusses creating venues, restaurants, and workshops using a Rails application. It covers setting up routes and controllers for venues, adding related restaurants and workshops to a venue, and using Enumerable#map to generate select options from an array of labels and values. The lesson provides examples of URL paths for viewing, creating and editing venues, restaurants, and workshops.
AsianPLoP'14: How and Why Design Patterns Impact Quality and Future ChallengesPtidej Team
The document discusses schemas, design patterns, and how patterns relate to schemas and learning. It notes that schemas are mental representations that allow people to recognize patterns. Design patterns aim to capture best practices and reusable solutions to common problems. When patterns are reused, it activates existing schemas and can lead to better design through experiences being shared. The document explores how pattern reuse relates to theories of schema and learning, and how patterns can be codified and shared between designers based on these theories.
In this first lecture, we discuss software quality, introduce the quality characteristic of maintainability, and argue that maintainability can be studied from four different points of view: (1) quality models, (2) good practices, (3) social studies, and (4) developers' studies. We discuss major works and results for these four points of view and show the last three can be used in the first one to build better quality models. We show that quality models are mandatory to make sense of any quality evaluation.
The document discusses the development of a Laboratory Assistant Suite (LAS) database application to manage data from a preclinical cancer model experiment involving implanting patient tumor samples in mice. It provides background on using such preclinical models for personalized cancer medicine. It describes the contributions of two research institutions (IRCC and Politecnico di Torino) to the LAS project and outlines the data flow, requirements, and database design for the LAS application.
Mouse tracking is a technique for monitoring and visualizing mouse movement and activity of the users.
This is a Comparative study of cursor movement pattern between a touchpad and a mouse devices based on patterns of cursor movement.
ATAM is an architecture evaluation method that assesses architectural decisions based on quality attribute requirements. It identifies risks, tradeoffs, and sensitivity points. The ATAM process has 3 phases - introduction, analysis and investigation, and follow up. It involves stakeholders generating scenarios, analyzing how architectural approaches address quality attributes, and identifying risks. The results include documented architectural approaches, utility trees, scenarios, and risks/tradeoffs to improve the architecture.
This document summarizes a study on the impact of classes playing roles in design patterns. The study analyzed classes playing zero, one, or two roles across six Java programs. It found that on average 8.24% of classes played one role and 17.81% played two roles. Classes playing roles, especially two roles, had significantly higher values for internal metrics like coupling and cohesion. Classes playing two roles also changed significantly more than other classes. The results confirm previous findings and justify further study into ranking design pattern occurrences based on class roles and metrics.
The document discusses patterns in software development. It begins by defining what a pattern is, noting that a pattern describes a general reusable solution to a commonly occurring problem within a specific context. It then discusses some qualities of patterns, including that they aim to enhance reusability, encapsulate design experiences, and provide a common vocabulary among designers. The document also notes that patterns aim to capture an ineffable "quality without a name". It provides examples of patterns from different programming languages to illustrate recurring solutions.
The document discusses usability and user experience (UX) in several contexts:
1. It defines usability according to ISO usability standard 9241 as how effectively, efficiently, and satisfactorily users can achieve goals within a specified context.
2. It lists 47 common usability activities including heuristic evaluation, personas, usability testing, and more.
3. It describes how to measure usability through effectiveness, efficiency, and satisfaction metrics like tasks completed, time on task, errors, and user ratings.
4. It notes that usability is complex and interdisciplinary, drawing on fields like information architecture, interaction design, industrial design, and more.
5. It suggests that
Software Engineering with Objects (M363) Final Revision By Kuwait10Kuwait10
This document provides an overview of software engineering concepts covered in various course units. It begins with introductions to approaches to software development, requirements concepts, and modeling. Key topics covered include the software development life cycle, requirements elicitation and analysis techniques, types of requirements (functional and non-functional), modeling languages like UML, and risks and traceability in software projects. The document also lists contents for each of the 14 course units.
The document outlines the engineering design process from problem identification through various phases of design and project management. It begins with problem identification, which involves defining customer needs and organizing them into a hierarchy of needs. This leads to developing a problem statement and specifying engineering requirements. Various concept generation techniques are then discussed along with evaluating and selecting concepts. Considerations for the detailed design phase include reliability, safety, and manufacturability. The document concludes with discussions on project management techniques like scheduling, communication, and presentations.
Complexity is a term very often used to express difficulties in organisational change programs or (IT related) projects. Instead of using complexity as excuse for failure assessing complexity is a much more attractive option.
The document discusses user-centric design (UCD) and user experience (UX). It defines UX and discusses how UCD focuses on involving intended users throughout the design process through iterative testing. The basic UCD workflow involves concept, research, prototyping, testing, building, and post-launch testing. It also discusses the Five Planes Model for structuring UCD and covers creating user personas and stories to understand users.
20th and last slide set of CECS 542
Recap of the 2nd half of the semester for preparing for the final
Complete course: http://foss2serve.org/index.php/Requirements_Engineering,_CSU_Long_Beach,_Penzenstadler
J.kim c.bouchard other:a study on designers mental process of information ca...ArchiLab 7
The document summarizes a study on how designers mentally categorize information in the early stages of design. Researchers conducted a study with 8 product designers who verbalized their thoughts while sketching in response to a design brief. The study found that designers employ information at high, middle, and low levels of abstraction. High and middle level information like semantics, analogies, and functions made up the majority of information used. Designers transformed information through cognitive operations of memory retrieval, association, and transformation. The study provides insight into the mental processes designers use to generate and develop early design concepts and sketches.
Slides from the talk "Model-Driven Engineering: a first glance at a ¿new? way of conceiving software development". Summer course on "Data Management". University of Santander (Spain), July 2011)
The role of systems analysis in co-learning. Walter RossingJoanna Hicks
Systems analysis can play different roles in addressing problems depending on the type of problem and level of agreement. Co-learning through boundary work between science and decision-making can help address "messy" problems with many stakeholders. Effective strategies for co-learning include meaningful participation in setting the research agenda, arrangements for accountability, and producing boundary objects that can be understood from different perspectives. Challenges for systems science include meeting requirements for credible, salient and legitimate knowledge while accommodating multiple disciplines and stakeholders.
This document introduces architectural modeling and discusses key concepts including:
- Architectural models capture principal design decisions about a system's architecture. Architectural modeling is documenting these decisions.
- When modeling, architects choose what to model based on stakeholder concerns, desired level of detail, and cost/benefit. Aspects that are more important to stakeholders receive more modeling depth.
- Common things modeled include architectural elements like components, connectors and interfaces, as well as static and dynamic aspects, and functional and non-functional properties. Models are organized into views that focus on specific concerns or viewpoints.
iBeaken is a visitor engagement and activation program making it possible to publish content around heritage, nature, tourism, museums to the visitor's own smartphones.
Presentación aldea de la ilusión de microsoft office power pointEscuelas para la Vida
La Aldea de la Ilusión, un proyecto pedagógico pendiente de ESCUELAS PARA LA VIDA.
Con vuestro apoyo se podrá realizar en un futuro cercano. Http://escuelasparavida.blogspot.com
This document is a lesson on Rails3 that discusses creating venues, restaurants, and workshops using a Rails application. It covers setting up routes and controllers for venues, adding related restaurants and workshops to a venue, and using Enumerable#map to generate select options from an array of labels and values. The lesson provides examples of URL paths for viewing, creating and editing venues, restaurants, and workshops.
The document reflects fondly on childhood experiences from a simpler time before modern technology. It recalls outdoor games, cartoons on Saturday mornings, family dinners at the cafeteria, and parents being able to discipline any misbehaving child. Childhood mistakes were seen as learning opportunities. The biggest fears children had were of angering their parents, not threats like drive-by shootings. The passage evokes nostalgia for an earlier era defined by old-fashioned values and activities.
adRom Holding AG Spam und Erlaubnis E-Mail Marketing sind zweierlei. Der Expe...Norbert Rom
Oft wird E-Mail Marketing mit Spam in Verbindung gebracht. Der Experte kennt den Unterschied. Für E-Mail Marketing braucht es eine vorherige Zustimmung vom Empfänger - ohne diese geht nichts. Warum E-Mail Marketing Firmen die jährlich Milliarden von E-Mails für ihre Kunden versenden, immer wieder ins Gespräch wegen SPAM kommen liegt vermutlich daran dass Millionen von Empfängern im dialog Kanal die Möglichkeit haben sofort einen möglichen Unmut über die Marke oder Produkt freien Lauf zu lassen. Norbert Rom erklärt auf de rMarketing on Tour in Berlin, Hamburg, Frankfurt, Düsseldorf, München und Wien vor breitem Fachpuplikum die Gefahren und Schutzmöglichkeiten vor SPAM
Am IKAMED verstehen wir Kinesiologie als eine Methode die ganz viel Farbe ins Leben bringt.
IKAMED Kinesiologie ist für Menschen die eine bodenständige Kinesiologie suchen.
Munish Kaushal is a customer-oriented professional with over 3 years of experience as an Account Manager handling IT infrastructure projects. He has expertise in solutions such as data center services, cloud computing, routing and switching, and MPLS. His core responsibilities include identifying business opportunities, requirements gathering, solution design, vendor management, and ensuring project delivery within deadlines. He is proficient in networking technologies and holds certifications in CCNA and F5 load balancing.
Víctor Humareda fue un pintor peruano expresionista reconocido por su creatividad. Nació en 1920 en Lampa, Puno y falleció en 1986 en Lima. Estudió en la Escuela Nacional de Bellas Artes del Perú y luego obtuvo becas para estudiar en Argentina y Europa. Entre sus obras más destacadas se encuentran Arlequín con mandolina, Pueblo Joven y Cóndores. Recibió varios premios y su obra reflejaba la melancolía y oscuridad de su vida personal.
Este documento describe conceptos y clasificaciones de fracturas expuestas, así como su diagnóstico y tratamiento. Las fracturas expuestas se clasifican según el tiempo transcurrido desde la lesión y el grado de daño a los tejidos blandos, y su tratamiento prioriza prevenir infecciones, alinear los huesos fracturados e inmovilizarlos, y cubrir el hueso expuesto.
Este documento presenta la información sobre un curso de Producción Radial en la Universidad Central del Ecuador. El curso tiene una duración de 4 horas semanales y 2 horas de tutoría. Se divide en 4 unidades que cubren temas como el panorama actual de la radio, elementos del lenguaje radiofónico, y planificación de programas publicitarios y periodísticos. El objetivo es capacitar a los estudiantes en la producción de diferentes géneros y programas radiales de manera teórica y práctica.
El documento anuncia un seminario sobre el mercado eléctrico italiano que se llevará a cabo el 11 de febrero de 2015 en Madrid. El seminario cubrirá temas como los agentes del mercado eléctrico italiano, las oportunidades para las energías renovables, el funcionamiento del mercado mayorista, la evolución de los precios y las nuevas oportunidades creadas por la Directiva D522/2014, incluyendo casos prácticos.
El documento presenta varios casos de esclavitud moderna en Europa, donde pandillas criminales capturan personas vulnerables en el Reino Unido y los obligan a trabajar en condiciones de esclavitud en otros países europeos como Suecia y Noruega. También discute el problema de los "minijobs" en Alemania, donde más de siete millones de personas tienen empleos precarios con salarios inferiores a 400 euros.
Servicios de consultoria de negocios en México Centroamérica y Sudamérica actualización 2014 . Empresa mexicana de consultoría integral. Experiencia y compromiso en su Estrategia de negocio.
Este documento resume las enseñanzas del catolicismo romano sobre la Biblia en varios capítulos. Muestra que aunque la iglesia católica reconoce la inspiración divina de las Escrituras, no les da autoridad final, sino a la iglesia, que tiene el derecho de interpretar su significado. Históricamente, ha prohibido su lectura por el pueblo y su traducción a lenguas vernáculas. Sin embargo, la Biblia muestra que Dios quiso que su pueblo conociera sus palabras y las transmitiera a generaciones fut
Diferencias entre rna monocapa y multicapaDelita Paulina
El documento describe las diferencias entre RNA monocapa y multicapa. Las RNA monocapa tienen una sola capa y resuelven problemas de forma lineal, mientras que las multicapa pueden tener múltiples capas y resuelven problemas de forma no lineal, requiriendo que su función sea derivable. Las multicapa también tienen un rango más amplio de tareas en comparación con las monocapa. Ambos tipos de RNA pueden clasificar patrones y generar reglas como los humanos de forma no algorítmica.
This document provides an overview of a seminar on the basic design of experiments using the Taguchi approach. The seminar aims to teach participants how to apply experimental design principles to solve production problems and optimize product and process designs. The seminar covers topics such as orthogonal arrays, main effects, interactions, mixed level factors, experiment planning, and uses software demonstrations and hands-on exercises. The goal is to prepare attendees for immediate application of experimental design methods in industry.
The research framework outlines a process to develop a prototype electronic menu application for casual dining restaurants. It involves reviewing literature on e-menu systems, usability, and mobile development. Requirements will be gathered through direct observation and interviews then analyzed using UML techniques. A rapid application development methodology will be used to iteratively design and evaluate a prototype menu app for iOS or Android. The analysis will examine users' perceptions of the prototype and recommend improvements to the software development process.
The research framework outlines a process to develop a prototype electronic menu application for casual dining restaurants. It involves reviewing literature on e-menu systems, usability, and mobile development. Requirements will be gathered through direct observation and interviews then analyzed using UML techniques. A prototype will be developed using rapid application development and evaluated based on user satisfaction and perception. Recommendations will be made regarding the software development methodology.
Abstract:
Though in essence an engineering discipline, software engineering research has always been struggling to demonstrate impact. This is reflected in part by the funding challenges that the discipline faces in many countries, the difficulties we have to attract industrial participants to our conferences, and the scarcity of papers reporting industrial case studies.
There are clear historical reasons for this but we nevertheless need, as a community, to question our research paradigms and peer evaluation processes in order to improve the situation. From a personal standpoint, relevance and impact are concerns that I have been struggling with for a long time, which eventually led me to leave a comfortable academic position and a research chair to work in industry-driven research.
I will use some concrete research project examples to argue why we need more inductive research, that is, research working from specific observations in real settings to broader generalizations and theories. Among other things, the examples will show how a more thorough understanding of practice and closer interactions with practitioners can profoundly influence the definition of research problems, and the development and evaluation of solutions to these problems. Furthermore, these examples will illustrate why, to a large extent, useful research is necessarily multidisciplinary. I will also address issues regarding the implementation of such a research paradigm and show how our own bias as a research community worsens the situation and undermines our very own interests.
On a more humorous note, the title hints at the fact that being a scientist in software engineering and aiming at having impact on practice often entails leading two parallel careers and impersonate different roles to different peers and partners.
Bio:
Lionel Briand is heading the Certus center on software verification and validation at Simula Research Laboratory, where he is leading research projects with industrial partners. He is also a professor at the University of Oslo (Norway). Before that, he was on the faculty of the department of Systems and Computer Engineering, Carleton University, Ottawa, Canada, where he was full professor and held the Canada Research Chair (Tier I) in Software Quality Engineering. He is the coeditor-in-chief of Empirical Software Engineering (Springer) and is a member of the editorial boards of Systems and Software Modeling (Springer) and Software Testing, Verification, and Reliability (Wiley). He was on the board of IEEE Transactions on Software Engineering from 2000 to 2004. Lionel was elevated to the grade of IEEE Fellow for his work on the testing of object-oriented systems. His research interests include: model-driven development, testing and verification, search-based software engineering, and empirical software engineering.
Web-Based Self- and Peer-Assessment of Teachers’ Educational Technology Compe...Hans Põldoja
This document summarizes a research project that aimed to develop a web-based tool for assessing teachers' educational technology competencies through self-assessment and peer assessment. It outlines existing competency frameworks, the design challenges, methodology used which included personas, scenarios, and participatory design sessions. Prototypes were created including a competency test, profile, grouping and requirements features. Future work includes expanding assessment tasks and integrating the tool into other digital platforms.
This document summarizes a discussion on improving standards development processes in the learning, education, and training domain. It outlines the current Process and Product Legitimacy model used to analyze standards. Participants identified opportunities like increasing stakeholder involvement and recognizing diverse standards bodies. Barriers included a lack of inclusiveness and understanding of standards scopes. Solutions proposed were learning from agile specification processes, improving adoption support, and managing expectations of policymakers. The document concludes by outlining an improved model with multiple perspectives to better understand standards development drivers and motivate diverse stakeholders.
Study of solution development methodology for small size projects.Joon ho Park
Medium-size system integration or IT Solution Company’s solution development project has limitation as like human resource limitation, budget limitation and expert limitation. Especially it is hard to maintain many IT experts for medium-size and small-size system integration or IT Solution Company. Thus in order to efficiently and beneficially complete projects, medium-size and small-size system integration or IT Solution Company should have appropriate solution development methodology.Solution development projects for medium-size and small-size system integration or IT Solution Company are usually shot-term and small budget so that they need slim and light-weight solution development methodology. But usual medium-size and small-size system integration or IT Solution Company do not have their own appropriate solution development methodology. Thus, if those kinds of solution development methodologies are applied to solution development projects for medium-size and small-size system integration or IT solution company without some modifications, shortage of human resources, incompleteness of solution and deliverables could arouse.Especially unnecessary paper works (deliverables and documentations) to both of projects teams and client’s wastes project resources and time. We analyze previous solution development methodologies and derive mandatory deliverables and optional deliverables. Before deriving them, we newly define procedures and tasks for each project stages which are necessary to projects team and clients, from client and expert of interviews. Our proposed solution development methodology can easily leverage the development overhead of short-term projects. Optional deliverables can be omitted by the contraction between project team and client.
Information Systems design science researchRaimo Halinen
The document discusses various aspects of developing and evaluating information systems using a design science research approach. It provides guidelines for conducting design science research, including that the research should design an artifact to solve an identified problem, evaluate the artifact and process, and ensure rigorous and communicable results. The document also discusses various process models and approaches for design science research.
State of the Art on methodologies for the development of Dublin Core Applicat...Mariana Curado Malta
This document provides a summary of a research paper on methodologies for developing Dublin Core Application Profiles. The paper analyzed 21 existing items on the topic and found that while some provided guidelines for certain phases of the development process, none provided a comprehensive methodology. The researchers aim to contribute to defining such a methodology by studying existing data modeling processes and combining them with the specific needs of application profile development, particularly regarding global interoperability concerns.
1) The document discusses various ways that artificial intelligence can be applied to different phases of the software engineering lifecycle, including requirements specification, design, coding, testing, and estimation.
2) It provides examples of using techniques like natural language processing to clarify requirements, knowledge graphs to manage requirements information, and computational intelligence for requirements prioritization.
3) For design, the document discusses using intelligent agents to recommend patterns and designs to satisfy quality attributes from requirements and assist with assigning responsibilities to components.
This document discusses the automatic detection and correction of software architectural defects (SADs) in object-oriented designs. It aims to formalize SADs including antipatterns and design defects to enable their detection and correction. It covers terminology related to SADs, existing techniques for detection and correction of SADs, and challenges in developing tools and techniques to automatically detect and semi-automatically correct SADs.
The document summarizes the key phases and activities of the system development life cycle, including planning, analysis, design, implementation, and operation/support phases. It describes the objectives of each phase such as determining requirements during analysis or developing detailed designs during design. Project management, documentation, and techniques like prototyping and testing are discussed as important elements that occur throughout the entire development cycle.
The document justifies the approaches used for developing an e-menu prototype for a Thai restaurant. It uses a case study methodology to understand business requirements in-depth. Rapid Application Development and iterative prototyping are used to develop the software in an agile manner to accommodate changing requirements. Direct observation and interviews gather requirements and evaluate users' perceptions of the prototype.
OO Development 2 - Software Development MethodologiesRandy Connolly
Course material from my Object-Oriented Development course. This presentation discusses methodologies, development processes, the waterfall model and interative development.
The document summarizes a feasibility assessment of three candidate systems for an information system project. It describes the operational, technical, economic and schedule feasibility of each candidate. Metrics like functionality, costs, benefits and timelines are evaluated. Candidate 2 scores the highest overall due to fully supporting required functionality, using a mature technology, having the best cost-benefit profile and moderate implementation timeline.
Software engineering is the systematic application of engineering principles to software development and maintenance. It involves requirements analysis, design, development, testing, documentation, and maintenance following a systematic process. Software engineering aims to provide cost-effective solutions to software problems and is the branch of engineering concerned with developing software solutions.
This document is a master's thesis that examines best practices for managing agile software development projects. It discusses traditional and agile development methodologies like Scrum and Extreme Programming (XP). It also analyzes three case studies of agile projects and evaluates tools to support agile development. The thesis concludes that adopting a methodology fully and using communication tools are keys to agile success.
Awareness Support for Knowledge Workers in Research Networks - Very brief PhD...Wolfgang Reinhardt
1) The document discusses a PhD thesis that examined how to best support knowledge workers' awareness in research networks. 2) The research questions focused on characterizing knowledge workers, defining awareness in this context, identifying relevant data sources, and suitable technologies. 3) The methodology included expert interviews, surveys, data analysis, and evaluations.
Similar to Design Principles of Advanced Task Elicitation Systems (20)
Prof. Dr. Alexander Mädche, University of Mannheim
Dr. Hendrik Meth, BorgWarner IT Services Europa GmbH
Walldorf, September 11th 2015
SAP University Alliance EMEA Conference
The document discusses user assistance systems. It begins by noting that while human cognitive abilities have grown slowly, computing power has grown exponentially. It then discusses challenges users face with software-intensive systems and the need for user assistance. The document defines user assistance systems and provides a classification scheme along dimensions of intelligence, automation, data sources, and user interaction. Several examples of assistance systems are described, including help systems, process guidance systems, and intelligent feedback systems. Research projects on developing various assistance systems are summarized. The document concludes by discussing perspectives on future advanced human-technology cooperation with user assistance systems.
This document summarizes a presentation about designing digital services in retail banking. It discusses how technological changes have both evolved and revolutionized retail banking over time. The relationship between banks and customers is described as a service system characterized by co-creation of value. Challenges in these service systems are presented through customer and employee quotes. The presentation advocates for synchronization across different levels to transform service systems effectively. Technology investments are categorized into three "buckets" - integration, intelligence, and interaction. Each bucket is defined with its objectives and challenges. The presentation was given at the InES Symposium and discusses the Institute for Enterprise Systems and its Banking Enterprise Systems Center of Competence.
This presentation discusses SAP's Big Data Innovation Lab at the University of Mannheim and the development of data-driven process applications. It outlines how SAP HANA provides an integrated platform for transactional and analytical systems as well as big data technologies. The presentation demonstrates a new spatial process application in insurance that analyzes the impact of Hurricane Sandy. It describes the goals of the SAP UA pilot project to establish a Big Data Innovation Center and Lab to extend SAP systems and develop innovative applications using next-generation database technologies.
Stand der Forschung und Praxis aus einer interdisziplinären Perspektive
Vortrag auf Evaluations-Workshop Usability am Bundesministerium für Wirtschaft und Technologie, Bonn,
28. November 2013
The document summarizes information about the Graduate School of Economic and Social Sciences (GESS) at the University of Mannheim. GESS trains doctoral students according to international best practices, with 240 current students enrolled across three centers focused on business, economics, and social sciences. The program emphasizes quantitative methods, international experiences, and placement of graduates in academic and private sector positions around the world.
The document discusses enterprise systems in banking and how banks can achieve both standardization and flexibility through these systems. It provides an overview of challenges in the banking industry from changing customer and regulatory conditions. It then discusses the concepts of enterprise systems and the importance of usability, adoption, and fit between the organization and technology for realizing benefits. Finally, it presents the Banking Enterprise Systems Center of Competence which provides education, research and networking on banking enterprise systems.
1. The document reviews the history of enterprise systems and identifies key issues like limited functionality, inconsistencies, and high costs over time.
2. It introduces platform-based ecosystems as a powerful concept used successfully in other domains, and outlines how corporate IT could adopt this approach for future enterprise systems.
3. By developing capabilities around platform architecture, governance, and environmental dynamics, corporate IT can help transition enterprise systems toward a more modular, flexible platform-based model that supports both internal and external development of new applications and services.
This document discusses best practices for software product development. It covers:
1. Motivation for focusing on best practices due to trends like globalization, industrialization, and consumerization.
2. The state-of-the-art in science and practice, examining concepts from research areas like information systems, product management, and usability methods, as well as practices from industries like automotive and Apple.
3. Six key best practices are distilled from science and practice: having a clear product vision and leadership, using focused interdisciplinary empowered teams, maintaining a clear product scope, employing an artifact-centric development approach, integrating stakeholders continuously, and taking an incremental milestone-based approach.
Design Principles of Advanced Task Elicitation Systems
1. Chair of Information Systems IV (ERIS)
Institute for Enterprise Systems (InES)
Design Principles of Advanced Task
Elicitation Systems (*)
Karlsruhe, November 30th 2012
Prof. Dr. Alexander Mädche
Chair of Information Systems IV, Business School and
Institute for Enterprise Systems (InES), University of Mannheim
http://eris.bwl.uni-mannheim.de
http://ines.uni-mannheim.de
(*) Joint work with: H. Meth, Y. Li, B. Mueller.
2. Agenda 2
Agenda
1 Introduction
2 Related Work
3 Methodology
4 Exploring and Evaluating Design Principles
5 Discussion, Future Research & Summary
3. Motivation 3
Failure rate of software development projects is still high.
Driven by private life software usage the user expectations
are growing.
Understanding the requirements remains the major
challenge:
35 % of requirements change throughout the software
lifecycle (Jones, 2008)
45 % of delivered features are never used.
(Standish Report, 2009)
82 % of projects cited incomplete and unstable requirements
as the number one reason for failure (Taylor, 2000)
4. State-of-the-Art in Software Development 4
Continuous stakeholder integration, cross-functional teams
as well as incremental & artifact-driven development
Analysis Analysis
Phase Phase
Analysis Engineering
Phase Phase
IS
Human Requirements
Software Development
Computer Engineering
Engineering
Interaction
5. Focus of this talk 5
Approximately 80% of the requirements are
recorded in natural language (Mich et al.
2004; Neill and Laplante 2003):
Interview transcripts,
Workshop nemos,
Narrative scenarios
In large-scale development, manual requirements elicitation
is known to be time-consuming, error-prone, and
monotonous.
The study by Mich et al. (2004) on current elicitation practices
explicates the need for advanced support with specific
focus on automation.
6. Agenda 6
Agenda
1 Introduction and Motivation
2 Related Work
3 Methodology
4 Exploring and Evaluating Design Principles
5 Discussion, Future Research & Summary
7. Basic Definitions 7
Requirements elicitation is the process of discovering
requirements through direct interaction with stakeholders or
analysis of documents or other sources of information
(Ratchev et al. 2003).
A core activity in this process is the identification of relevant
tasks to be supported by the software, referred to as task
elicitation (also task analysis) (Lemaigre et al. 2008;
Paterno 2002).
Task elicitation aims at capturing the interaction between
user and system on a detailed level, differentiating between
actors, activity, and data (Tam et al. 1998).
8. Related Work 8
Various attempts for advancing task elicitation by specialized
task elicitation systems (TES) have been made, two major
research streams:
1 Requirements Engineering
• Identification of abstractions (Gacitua et al. 2011; Goldin and
Berry 1997; Kof 2004; Rayson et al. 2000)
• Identification and classification of requirements (Cleland-Huang
Pattern:
et al. 2007; Casamayor et al. 2010; Kiyavitskaya and Zannone
2008) Leverage
• Create requirements and design model (Ambriola and Gervasi automation
2006) techniques
and
knowledge
2 Human Computer Interaction bases
• Automate task elicitation with artifacts, e.g. U-TEL (Tam et al.
1998) or the model elicitation tool (Lemaigre et al. 2008)
9. Related Work 9
Existing work has three major shortcomings:
Manual creation of knowledge bases
Lacking systematic empirical evaluation of productivity effects
Limited explanation of artifact’s conceptualization
Research Question addressing this gap:
Which design principles of task elicitation systems
improve task elicitation productivity over manual task
elicitation?
10. Agenda 10
Agenda
1 Introduction and Motivation
2 Related Work
3 Methodology
4 Exploring and Evaluating Design Principles
5 Discussion, Future Research & Summary
11. Methodology 11
Research question aims at the acquisition of theoretical
design knowledge about task elicitation systems.
Design Science Research as proposed by March & Smith
(1995) is an applicable and appropriate approach to
address the research question.
Hevner et al (2004)
12. Research Design 12
DSR project builds and evaluates an artifact to support task
elicitation from natural language documents, guided by the
Design Science framework suggested by Kuechler &
Vaishnavi (2008):
General Design Science Cycle Cycle1 Cycle2 Cycle3
Literature Review, Literature Review,
Awareness of Problem Expert Interviews Expert Feedback
Suggestion Analysis & Conceptualization
Operation and Artifact Concept Artifact Prototype
Goal Artifact Final
Development Version Version (First
Version
Knowledge (Click-Through) Implementation)
Expert Evaluation Expert Evaluation Experiment
Evaluation Focus: Usefulness Focus: Ease of use Evaluation
Conclusion Design Principles
(Meth et al. 2012a)
13. Agenda 13
Agenda
1 Introduction and Motivation
2 Related Work
3 Methodology
4 Exploring and Evaluating Design Principles
5 Discussion, Future Research & Summary
14. Justificatory Knowledge 14
The tool-supported task elicitation process can been seen as
a series of advice-giving and advice-taking tasks
(Bonaccio and Dalal 2006).
An increase of the advisor’s advice accuracy has been found to
result in an increasing decision accuracy (of the advice-taker).
Productivity improvement will only occur if the quality of approved
requirements (the decision which has been taken) improves.
The underlying knowledge base influences the results of the
advice-giving process (Casamayor et al. 2010):
Leverage existing knowledge and enable continuous evolution of
knowledge base.
15. Conceptualization 15
Mapping Design-Requirements (DR) to Design Principles
(DP) to Design Features (DF):
DR1. Increase quality DF1. Pre-Processing
of approved & Elicitation
requirements Algorithms
DP1. Semi-
Automatic Task
Elicitation
DR2. Decrease DF2. One-click Task
Elicitation Effort Element Highlighting
DR3. Increase quality
of underlying DF3. Integrated
DP2. Usage of Knowledge Base
knowledge imported and
retrieved
knowledge
DR4. Decrease DF4. Supervised
knowledge creation Knowledge
and maintenance Supplementation
efforts
16. Conceptual Architecture 16
Requirements
Natural Engineer
language
Automatic
documents
Knowledge
Category Text brick POS Tag
Creation
Manual Category Text brick POS Tag
Elicitation
Retrieved Knowledge
Pre-
Processing
Algorithm Knowledge
Engineer
Automatic Category Text brick
Elicitation
Category Text brick
Manual Knowledge
Text POS Creation
Imported Knowledge
brick Tag Elicitation
Text POS Algorithm
brick Tag Knowledge Base
17. Artifact REMINER: Semi-Automatic Task Elicitation 17
MR1. Enable
automatic task
elicitation within
natural language DF1. One-click
documents Task Element
Highlighting
DP1. Semi-
Automatic
Task
Elicitation
MR2. Allow DF2. Natural
manual Language
adaptions of Processing
automatically Capabilities
elicited tasks
MR3. Require
minimal efforts to
DF3. Knowledge
build up task
DP2. Usage Upload Capability
knowledge
of imported
and
retrieved
knowledge
MR4. Support DF4. Knowledge
simple Retrieval and Re-
supplementation Use
of domain-
specific
knowledge
Online available at: http://www.reminer.com/
(Meth et al. 2012a)
18. Artifact REMINER: Imported and Retrieved Knowledge 18
MR1. Enable
automatic task
elicitation within
natural language
DF1. One-click Task
documents
Element Highlighting
DP1. Semi-
Automatic Task
Elicitation
MR2. Allow manual DF2. Natural
adaptions of Language
automatically Processing
elicited tasks Capabilities
MR3. Require
minimal efforts to
build up task DF3. Knowledge
knowledge Upload Capability
DP2. Usage of
imported and
retrieved
knowledge
DF4. Knowledge
MR4. Support simple
Retrieval and Re-Use
supplementation of
domain-specific
knowledge
Upload
Retrieve & Re-Use
19. Evaluation Methodology 19
Controlled within-subject experiment to rigorously test the
effect of two design principles (DP1, DP2) on task elicitation
productivity.
Experimental task: task elicitation with interview transcripts
Task domain: Travel Management
Similar length, readability, and the distribution of task elements
Sample size calculation:
Calculated with G*Power 3 (Faul et al., 2007), at least 35 participants
are needed (f =0,25, 0.05 significance level)
Participants: Student sample (Lab) Practitioner sample (Field)
(N= 40) (N=5)
Gender
Female 8 2
Male 32 3
(Meth et al. 2012b) Avg. age 25.4 (SD=2.07) 34.8 (SD=3.56)
20. Evaluation Model 20
H1: In a fixed time period,
TES configuration (2)
results in higher
recall than TES
configuration (1)
Task Elicitation
Productivity H2: In a fixed time period,
(in a fixed time period) TES configuration (3)
results in higher
Recall recall than TES
Task Elicitation System (TES) H1,H2
configuration (2)
Configuration
H3 H3: In a fixed time period,
(1,2,3)
Precision TES configuration (1),
(2) and (3) does NOT
result in significantly
different precision
(Meth et al. 2012b)
21. Experimental Procedure 21
Introduction
Pre-task questionnaire Demographic information, task elicitation
experience
Use transcripts about “train reservation
Training & Practice
application”
Use transcripts about “car sharing
Experimental task
application”; 3 TES configurations,
counterbalanced
3 times
Post-task questionnaire Task elicitation knowledge, motivation
Overall: 70 minutes
22. Data Analysis: Descriptive Results 22
Recall and Precision for Different TES Configurations
(3) Semi-automatic with
(2) Semi-automatic with
(1) Manual imported and retrieved
imported knowledge
knowledge
Mean SD Mean SD Mean SD
Lab experiment (student participants, N=40)
Recall 50.7% 12.0% 69.8% 9.8% 79.5% 8.0%
Precision 71.0% 8.5% 72.0% 6.7% 73.2% 6.5%
Field experiment (practitioner participants, N=5)
Recall 37.6% 12.9% 68.6% 6.0% 77.8% 3.9%
Precision 70.1% 14.5% 72.7% 3.5% 68.5% 5.3%
Data analysis method
Internal reliability, normality and homogeneity of variance checked
RMANCOVA: “Task elicitation knowledge” and “motivation” are not
covariates
Univariate RMANOVA for hypotheses testing
23. Data Analysis: Hypotheses Testing Results 23
Results of RMANOVA for Recall and Precision
DV Source DF MS F p η2 Cohen’s f
TES Config. 2 0.861 129.76 < .001 .77 1.82
Recall
Error 78 0.007
TES Config. 2 0.005 1.36 .263 .03 0.19
Precision H3: supported
Error 78 0.004
Results of Pairwise Comparisons for Recall
Mean 95% CI*
Pair comparison p*
difference Lower Upper
TES config. (2) TES config. (1) 19.2% < .001 14.4% 23.9%
H1: supported
TES config. (3) TES configur. (2) 9.7% < .001 5.8% 13.6%
H2: supported
* Bonferroni corrections are applied for multiple comparisons
External validity evaluation: the practitioner sample doesn’t demonstrate
a different behavioral pattern on recall and precision.
Huberty & Morris (1989)
24. Agenda 24
Agenda
1 Introduction and Motivation
2 Related Work
3 Methodology
4 Exploring and Evaluating Design Principles
5 Discussion, Future Work & Summary
25. Discussion 25
Design principles DP1 and DP2 impact recall:
Suggestion mechanism based on imported knowledge leads to 20%
recall increase: Trust recommendations and increase recall through
further manual elicitation of additional tasks in remaining time.
Dynamically retrieved knowledge leads to additional 10% recall
increase: Continuous contribution of additional knowledge through
ongoing manual elicitation.
Limitations
Limited complexity of task domain and time-constraint evaluation
approach.
Laboratory sessions were conducted with master IS students, only
small-scale experiment was carried out with experts.
26. Future Research 26
Presented work contributes to the design theory body of
knowledge for task elicitation in the analysi phase.
Interdisciplinary perspective is promising, research on task
elicitation needs to be embedded:
End-to-End Process Models &
Development Management
Tools Analysis Analysis Concepts
Phase Phase
Analysis Engineering
Phase Phase
http://www.usability-in-germany.de/
27. Example: From Task Elicitation to Interaction Flows 27
(Meth et al. 2012a)
28. Summary 28
• Design principles of an advanced task elicitation
1 system following a design science research approach
have been presented.
• Rigorous experimental evaluation has shown that semi-
2 automatic and knowledge-based elicitation has positive
impact on elicitation productivity;
• Contribution: The design theory body of knowledge for
3 task elicitation systems has been expanded. Software
vendors can leverage results to provide advanced tool-
based elicitation support
29. Thank you for your attention! 29
Q&A
Prof. Dr. Alexander Mädche
+49 621 181 3606
maedche@es.uni-mannheim.de
Chair of Information Systems IV, Business School and
Institute for Enterprise Systems, University of Mannheim
http://eris.bwl.uni-mannheim.de
http://ines.uni-mannheim.de
30. References 30
Neill, C. J., and Laplante, P. A. 2003. “Requirements Engineering: The State of the Practice,”
IEEE Software (20:6), pp. 40-45.
Mich, L., Franch, M., and Novi Inverardi, P. L. 2004. “Market research for requirements analysis
using linguistic tools,” Requirements Engineering (9:1), pp. 40-56.
Meth, H., Maedche, A., and Einoeder, M. 2012a. “Exploring design principles of task elicitation
systems for unrestricted natural language documents,” Proceedings of the 4th ACM SIGCHI
symposium on Engineering interactive computing systems - EICS ’12. New York, New York, USA:
ACM Press, pp. 205 - 210.
Meth, H., Li, Y., Maedche, A., and Mueller, B. 2012b. “Advancing Task Elicitation Systems - An
Experimental Evaluation of Design Principles,” In ICIS 2012 Proceedings.
Jones, C. 2008. Applied Software Measurement. McGraw Hill.
Taylor, A. 2000. “IT projects: sink or swim.” The Computer Bulletin, 42 (1): 24-26.
Standish Group Report 2009, http://luuduong.com/blog/archive/2009/03/04/applying-the-
quot8020-rulequot-with-the-standish-groups-software-usage.aspx
Bonaccio, S. and Dalal, R.S. (2006) “Advice taking and decision-making: An integrative literature
review, and implications for the organizational sciences,” Organizational Behavior and Human
Decision Processes (101: 2), pp. 127-151.
Hevner, A. R., March, S. T., Park, J., and Ram, S. (2004) “Design Science in Information Systems
Research,” MIS Quarterly (28:1), pp. 75-105.
31. References (cont’d) 31
March, S. T., and Smith, G. F. 1995. “Design and natural science research on information
technology,” Decision Support Systems (15:4), pp. 251–266.
Lemaigre, C., García, J. G., and Vanderdonckt, J. (2008) “Interface Model Elicitation from Textual
Scenarios,” in Proceedings of the Human-Computer Interaction Symposium, 272, pp. 53-66.
Mich, L., Franch, M., and Novi Inverardi, P. L. (2004) “Market research for requirements analysis
using linguistic tools,” Requirements Engineering (9:1), pp. 40-56.
Kuechler, B., and Vaishnavi, V. (2008) “On theory development in design science research:
anatomy of a research project,” European Journal of Information Systems (17:5), pp. 489–504.
Ratchev, S. M., Urwin, E., Muller, D., Pawar, K. S., and Moulek, I. (2003) “Knowledge based
requirement engineering for one-of-a-kind complex systems,” Knowledge Based Systems (16:1),
pp. 1-5.
Paterno, F. (2002) “Task Models in Interactive Software Systems,” in Handbook of Software
Engineering and Knowledge Engineering Vol 1 Fundamentals, S. K. Chang (ed.), World Scientific,
pp. 1-19.
Tam, R. C.-man, Maulsby, D., and Puerta, A. R. (1998) “U-TEL: A Tool for Eliciting User Task
Models from Domain Experts,” in Proceedings of the 3rd international conference on Intelligent
user interfaces, pp. 77-80.
Faul, F., Erdfelder, E., Lang, A.-G. and Buchner, A. (2007) “G*Power 3: a flexible statistical
power analysis program for the social, behavioral, and biomedical sciences.,” Behavior
research methods 39(2), pp. 175-91.
32. References (cont’d) 32
Gacitua, R., Sawyer, P., and Gervasi, V. (2011) “Relevance-based abstraction identification:
technique and evaluation,” Requirements Engineering (16:3), pp. 251-265.
Goldin, L., and Berry, D. M. (1997) “AbstFinder, A Prototype Natural Language Text Abstraction
Finder for Use in Requirements Elicitation,” Automated Software Engineering (4:4), pp. 375-412.
Kof, L. (2004) “Natural Language Processing for Requirements Engineering: Applicability to Large
Requirements Documents,” in Proceedings of the 19th International Conference on Automated
Software Engineering.
Rayson, P., Garside, R., and Sawyer, P. (2000) “Assisting requirements engineering with
semantic document analysis,” in Proceedings of the RIAO, pp. 1363-1371.
Cleland-Huang, J., Settimi, R., Zou, X., and Solc, P. (2007) “Automated classification of non-
functional requirements,” Requirements Engineering (12:2), pp. 103-120.
Casamayor, A., Godoy, D., and Campo, M. (2010) “Identification of non-functional requirements in
textual specifications: A semi-supervised learning approach,” Information and Software
Technology (52:4), pp. 436-445.
Kiyavitskaya, N., and Zannone, N. (2008) “Requirements model generation to support
requirements elicitation: the Secure Tropos experience,” Automated Software Engineering (15:2),
pp. 149-173.
Ambriola, V., and Gervasi, V. (2006) “On the Systematic Analysis of Natural Language
Requirements with CIRCE,” Automated Software Engineering (13:1), pp. 107-167.
Huberty, C. J. and Morris, J. D. (1989) “Multivariate analysis versus multiple univariate
analyses.,” Psychological Bulletin 105(2), pp. 302-308.