Business process-based requirements specification and object-oriented conceptual modelling of information systems

Two of the main needs when developing an information system for an organization are that system analysts know and understand the application domain and that the system properly supports the business processes of the organization. Consequently, elicitation of system requirements from business process models has been acknowledged as a suitable activity to deal with that needs. In addition, system requirements must be linked to subsequent development stages. However, system analysts can face many challenges when performing these activities. They may have problems communicating with customer stakeholders and may need to analyse and operationalize the purpose of the information system. Furthermore, system analysts must bridge the gap between business and system domains for specification of system requirements, specify different types of system requirements and guarantee that their specification is precise, consistent and homogeneous. In relation to object-oriented conceptual modelling-based information system development, system analysts must also avoid potential problems that may arise when a conceptual schema is created from system requirements as part of their link with subsequent development stages. For example, a conceptual schema can be incomplete or inconsistent if it is not properly managed. As a solution, this thesis presents a methodological approach for business process-based requirements specification and object-oriented conceptual modelling of information systems. The approach consists of four stages: organizational modelling, purpose analysis, specification of system requirements and derivation of object-oriented diagrams. By following the design research methodology for performing research in information systems, the methodological approach has been designed on the basis of many existing ideas and principles in academia and industry. It also provides new mechanisms and guidance to address the challenges presented above. The methodological approach mainly aims to help system analysts to elicit system requirements from business process models, adequately specify system requirements and derive the object-oriented conceptual schema of an information system from its system requirements. It does so by taking advantage of existing solutions and by modifying them to better tackle the associated challenges. The methodological approach has been evaluated in laboratory and industrial contexts, especially focusing on its usefulness for practitioners. Thanks to evaluation, several lessons have been learned and many of them have driven definition of the methodological approach. Furthermore, the lessons learned can be very useful both in academia and in industry for identification of further research areas and for awareness of situations that may occur in information system development projects, respectively.

[1]  Oscar Pastor,et al.  Using UML as a Domain-Specific Modeling Language: A Proposal for Automatic Generation of UML Profiles , 2009, CAiSE.

[2]  Colette Rolland,et al.  Fitting Business Models to System Functionality Exploring the Fitness Relationship , 2003, CAiSE.

[3]  Kamel Rouibah,et al.  Requirement engineering elicitation methods: A Kuwaiti empirical study about familiarity, usage and perceived value , 2009, Inf. Manag. Comput. Secur..

[4]  Barbara Paech,et al.  An Analysis of Empirical Requirements Engineering Survey Data , 2005 .

[5]  Kurt Sandkuhl,et al.  Participative Enterprise Modeling: Experiences and Recommendations , 2007, CAiSE.

[6]  Danilo Caivano,et al.  Prediction Models for BPMN Usability and Maintainability , 2009, 2009 IEEE Conference on Commerce and Enterprise Computing.

[7]  Michael Jackson,et al.  Four dark corners of requirements engineering , 1997, TSEM.

[8]  Andrés Silva,et al.  Requirements Engineering for Sociotechnical Systems , 2005 .

[9]  Carson C. Woo,et al.  Investigating business-IT alignment through multi-disciplinary goal concepts , 2009, Requirements Engineering.

[10]  Keith Phalp,et al.  B-SCP: A requirements analysis framework for validating strategic alignment of organizational IT based on strategy, context, and process , 2006, Inf. Softw. Technol..

[11]  Sara Jones,et al.  Model-Driven Requirements Engineering: Synchronising Models in an Air Traffic Management Case Study , 2004, CAiSE.

[12]  John Mylopoulos,et al.  An Empirical Evaluation of the i* Framework in a Model-Based Software Generation Environment , 2006, CAiSE.

[13]  Franz Lehner,et al.  Requirements Engineering as a Success Factor in Software Projects , 2001, IEEE Softw..

[14]  Joaquín Nicolás,et al.  Transforming the OOram Three-Model Architecture into a UML-based Process , 2002, J. Object Technol..

[15]  Pericles Loucopoulos,et al.  System Requirements Engineering , 1995, System Requirements Engineering.

[16]  Ivar Jacobson,et al.  Object-oriented software engineering - a use case driven approach , 1993, TOOLS.

[17]  Tony Gorschek,et al.  Technology transfer decision support in requirements engineering research: a systematic review of REj , 2009, Requirements Engineering.

[18]  Esperanza Marcos,et al.  Applying CIM-to-PIM model transformations for the service-oriented development of information systems , 2011, Inf. Softw. Technol..

[19]  Karl Cox,et al.  Requirements Engineering and Software Project Success: an industrial survey in Australia and the U.S , 2005, Australas. J. Inf. Syst..

[20]  Silvia Mara Abrahão,et al.  A systematic review of the use of requirements engineering techniques in model-driven development , 2010, MODELS'10.

[21]  Mario Piattini,et al.  Semi-formal transformation of secure business processes into analysis class and use case models: An MDA approach , 2010, Inf. Softw. Technol..

[22]  Patrick Heymans,et al.  Comparing Goal Modelling Languages: An Experiment , 2007, REFSQ.

[23]  Varun Grover,et al.  Business process reengineering: A tutorial on the concept, evolution, method, technology and application , 1997 .

[24]  Jason Rubens.  Business analysis and requirements engineering: the same, only different? , 2007, Requirements Engineering.

[25]  Andreas L. Opdahl,et al.  Comparing GRL and KAOS using the UEML Approach , 2007, IESA.

[26]  Evangelia Kavakli,et al.  Goal-Oriented Requirements Engineering: A Unifying Framework , 2002, Requirements Engineering.

[27]  Søren Lauesen,et al.  Communication gaps in a tender process , 2005, Requirements Engineering.

[28]  Peter Weill,et al.  The Implications of Information Technology Infrastructure for Business Process Redesign , 1999, MIS Q..

[29]  Cláudia Maria Lima Werner,et al.  Info Cases: Integrating Use Cases and Domain Models , 2008, 2008 16th IEEE International Requirements Engineering Conference.

[30]  Mathias Kirchmer.  Business Process Oriented Implementation of Standard Software: How to Achieve Competitive Advantage Efficiently and Effectively , 1999 .

[31]  Klaus Pohl,et al.  Requirements Engineering - Fundamentals, Principles, and Techniques , 2010 .

[32]  Owen Rambow,et al.  Conceptual modeling through linguistic analysis using LIDA , 2001, Proceedings of the 23rd International Conference on Software Engineering. ICSE 2001.

[33]  Christof Ebert,et al.  The Top Risks of Requirements Engineering , 2001, IEEE Softw..

[34]  Colin Potts,et al.  Software-engineering research revisited , 1993, IEEE Software.

[35]  Shari Lawrence Pfleeger,et al.  Personal Opinion Surveys , 2008, Guide to Advanced Empirical Software Engineering.

[36]  Colin Sharp.  Qualitative Research and Evaluation Methods (3rd ed.) , 2003 .

[37]  Tony Gorschek,et al.  Quality Requirements in Practice: An Interview Study in Requirements Engineering for Embedded Systems , 2009, REFSQ.

[38]  R. Kaplan,et al.  The Balanced Scorecard: Translating Strategy into Action , 1996 .

[39]  Soren Lauesen,et al.  Software Requirements: Styles & Techniques , 2002 .

[40]  Michael Pidd,et al.  A conceptual framework for understanding business processes and business process modelling , 2000, Inf. Syst. J..

[41]  John Krogstie,et al.  Analysis and Design of Business Processes Using BPMN , 2010 .

[42]  Søren Lauesen,et al.  Preventing Requirement Defects: An Experiment in Process Improvement , 2001, Requirements Engineering.

[43]  Oscar Pastor,et al.  Dealing with Usability in Model Transformation Technologies , 2008, ER.

[44]  Ljerka Beus-Dukic,et al.  Discovering Requirements: How to Specify Products and Services , 2009 .

[45]  Lidia Fuentes,et al.  Relating Feature Models to Other Models of a Software Product Line - A Comparative Study of FeatureMapper and VML* , 2010, LNCS Trans. Aspect Oriented Softw. Dev..

[46]  Raian Ali,et al.  A goal-based framework for contextual requirements modeling and analysis , 2010, Requirements Engineering.

[47]  Jan Recker,et al.  Opportunities and constraints: the current struggle with BPMN , 2010, Bus. Process. Manag. J..

[48]  Karl E. Wiegers,et al.  Software Requirements , 1999 .

[49]  Cmmi Product Team.  CMMI for Development, Version 1.2 , 2010 .

[50]  Sara Jones,et al.  Rescue an integrated method for specifying requirements for complex sociotechnical systems , 2005 .

[51]  Yair Wand,et al.  Choosing classes in conceptual modeling , 1997, CACM.

[52]  Mohsen Attaran,et al.  Exploring the relationship between information technology and business process reengineering , 2004, Inf. Manag..

[53]  Oscar Pastor,et al.  Systematic derivation of state machines from communication-oriented business process models , 2011, 2011 FIFTH INTERNATIONAL CONFERENCE ON RESEARCH CHALLENGES IN INFORMATION SCIENCE.

[54]  Richard Stevens,et al.  Writing Better Requirements , 2002 .

[55]  Stephen Fickas,et al.  Goal-Directed Requirements Acquisition , 1993, Sci. Comput. Program..

[56]  Keith Phalp,et al.  Practical experience of eliciting classes from use case descriptions , 2007, J. Syst. Softw..

[57]  Betty H. C. Cheng,et al.  Research Directions in Requirements Engineering , 2007, Future of Software Engineering (FOSE '07).

[58]  Jan Recker.  Evaluations of Process Modeling Grammars - Ontological, Qualitative and Quantitative Analyses Using the Example of BPMN , 2011, Lecture Notes in Business Information Processing.

[59]  Ron Zahavi,et al.  Business Modeling: A Practical Guide to Realizing Business Value , 2008 .

[60]  Manuele Kirsch-Pinheiro,et al.  An Intentional Approach to Service Engineering , 2010, IEEE Transactions on Services Computing.

[61]  Alan M. Davis,et al.  Software Requirements: Objects, Functions and States , 1993 .

[62]  Martin Glinz,et al.  On Non-Functional Requirements , 2007, 15th IEEE International Requirements Engineering Conference (RE 2007).

[63]  Martin Glinz,et al.  A lightweight approach to consistency of scenarios and class models , 2000, Proceedings Fourth International Conference on Requirements Engineering. ICRE 2000. (Cat. No.98TB100219).

[64]  Andreas Borg,et al.  The Bad Conscience of Requirements Engineering : An Investigation in Real-World Treatment of Non-Functional Requirements , 2003 .

[65]  Capers Jones,et al.  Why software fails , 1996 .

[66]  Mark Strembeck,et al.  Influence Factors of Understanding Business Process Models , 2008, BIS.

[67]  Kyo Chul Kang,et al.  Feature-Oriented Domain Analysis (FODA) Feasibility Study , 1990 .

[68]  E. Kavakli,et al.  Experiences with goal-oriented modeling of organizational change , 2006, IEEE Transactions on Systems, Man, and Cybernetics, Part C (Applications and Reviews).

[69]  Xavier Franch,et al.  Dealing with Non-Functional Requirements in Model-Driven Development , 2010, 2010 18th IEEE International Requirements Engineering Conference.

[70]  Amela Karahasanovic,et al.  A survey of controlled experiments in software engineering , 2005, IEEE Transactions on Software Engineering.

[71]  Björn Regnell,et al.  Supporting Roadmapping of Quality Requirements , 2008, IEEE Software.

[72]  Lionel C. Briand,et al.  A systematic review of transformation approaches between user requirements and analysis models , 2011, Requirements Engineering.

[73]  Pamela Zave.  Classification of research efforts in requirements engineering , 1997, ACM Comput. Surv..

[74]  Ian Sommerville,et al.  Requirements Engineering: Processes and Techniques , 1998 .

[75]  Oscar Pastor,et al.  Facing the Technological Challenges of Web 2.0: A RIA Model-Driven Engineering Approach , 2009, WISE.

[76]  Marta Indulska,et al.  Measuring Method Complexity: UML versus BPMN , 2009, AMCIS.

[77]  Julio Cesar Sampaio do Prado Leite,et al.  On Non-Functional Requirements in Software Engineering , 2009, Conceptual Modeling: Foundations and Applications.

[78]  Robert L. Glass,et al.  An assessment of systems and software engineering scholars and institutions (1993-1997) , 1997, Journal of Systems and Software.

[79]  Anil Nigam,et al.  Business artifacts: An approach to operational specification , 2003, IBM Syst. J..

[80]  C. Rolland.  Capturing System Intentionality with Maps , 2007 .

[81]  Michael Rosemann,et al.  Factors and measures of business process modelling: model building through a multiple case study , 2005, Eur. J. Inf. Syst..

[82]  Barbara Paech,et al.  Rationale-Based Use Case Specification , 2002, Requirements Engineering.

[83]  David K. Carr,et al.  Best Practices in Reengineering: What Works and What Doesn't in the Reengineering Process , 1995 .

[84]  Rob Davis,et al.  ARIS Design Platform: Getting Started with BPM , 2007 .

[85]  Colin J. Neill,et al.  Requirements Engineering: The State of the Practice , 2003, IEEE Softw..

[86]  Janice Singer,et al.  Guide to Advanced Empirical Software Engineering , 2007 .

[87]  Claes Wohlin,et al.  Empirical Research Methods in Software Engineering , 2003, ESERNET.

[88]  Craig Larman,et al.  Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and Iterative Development (3rd Edition) , 1997 .

[89]  Ana I. Anton,et al.  Goal identification and refinement in the specification of software-based information systems , 1997 .

[90]  Marta Indulska,et al.  Modeling languages for business processes and business rules: A representational analysis , 2009, Inf. Syst..

[91]  August-Wilhelm Scheer,et al.  ARIS - Business Process Modeling , 1998 .

[92]  Xavier Franch,et al.  ReeF: Defining a Customizable Reengineering Framework , 2007, CAiSE.

[93]  Ilia Bider.  Choosing Approach to Business Process Modeling - Practical Perspective , 2005 .

[94]  Guttorm Sindre,et al.  An Analytical Evaluation of BPMN Using a Semiotic Quality Framework , 2005, EMMSAD.

[95]  Richard Kamm,et al.  Bridging the gap between business models and system models , 2003, Inf. Softw. Technol..

[96]  Francisco A. C. Pinheiro.  Requirements honesty , 2003, Requirements Engineering.

[97]  Richard Berntsson Svensson,et al.  Managing quality requirements in software product development , 2009 .

[98]  Jaap Gordijn,et al.  Value-based requirements engineering: exploring innovative e-commerce ideas , 2003, Requirements Engineering.

[99]  Alain Wegmann,et al.  Defining early IT system requirements with regulation principles: the Lightswitch approach , 2004, Proceedings. 12th IEEE International Requirements Engineering Conference, 2004..

[100]  R. Yin,et al.  Case Study Research: Design and Methods (4th ed. , 2009 .

[101]  Leon G. Higley,et al.  Forensic Entomology: An Introduction , 2009 .

[102]  Pericles Loucopoulos,et al.  Relating evolving business rules to software design , 2004, J. Syst. Archit..

[103]  Matthias Jarke,et al.  Scenarios in System Development: Current Practice , 1998, IEEE Softw..

[104]  Alan M. Davis,et al.  201 Principles of Software Development , 1995 .

[105]  Antoni Olivé,et al.  Conceptual modeling of information systems , 2007 .

[106]  Oscar Pastor,et al.  Systematic Derivation of Class Diagrams from Communication-Oriented Business Process Models , 2011, BMMDS/EMMSAD.

[107]  Mathias Weske,et al.  Business Process Management: Concepts, Languages, Architectures , 2007 .

[108]  Lionel C. Briand,et al.  A Use Case Modeling Approach to Facilitate the Transition towards Analysis Models: Concepts and Empirical Evaluation , 2009, MoDELS.

[109]  Oscar Pastor,et al.  Communication Analysis: A Requirements Engineering Method for Information Systems , 2009, CAiSE.

[110]  Marta Indulska,et al.  Extending Representational Analysis: BPMN User and Developer Perspectives , 2007, BPM.

[111]  Camille Salinesi,et al.  Aligning IS to Organization's Strategy: The InStAlMethod , 2007, CAiSE.

[112]  Ian Graham.  Requirements Modelling and Specification for Service Oriented Architecture , 2008 .

[113]  Daniel Sinnig,et al.  Capturing business transaction requirements in use case models , 2008, SAC '08.

[114]  Matthias Jarke,et al.  The Brave New World of Design Requirements: Four Key Principles , 2010, CAiSE.

[115]  Anthony Finkelstein,et al.  Requirements engineering: a review and research agenda , 1994, Proceedings of 1st Asia-Pacific Software Engineering Conference.

[116]  Vijay K. Vaishnavi,et al.  Design Science Research Methods and Patterns: Innovating Information and Communication Technology , 2007 .

[117]  Jan Recker,et al.  How Much Language Is Enough? Theoretical and Practical Use of the Business Process Modeling Notation , 2008, CAiSE.

[118]  Ian Sommerville,et al.  Integrated requirements engineering: a tutorial , 2005, IEEE Software.

[119]  Donald Firesmith,et al.  Common Requirements Problems, Their Negative Consequences, and the Industry Best Practices to Help Solve Them , 2007, J. Object Technol..

[120]  Claes Wohlin,et al.  Experimentation in software engineering: an introduction , 2000 .

[121]  Michael zur Muehlen,et al.  Primitives: Design Guidelines and Architecture for BPMN Models , 2010 .

[122]  Giancarlo Guizzardi,et al.  Requirements engineering based on business process models: A case study , 2009, 2009 13th Enterprise Distributed Object Computing Conference Workshops.

[123]  Hajo A. Reijers,et al.  Best practices in business process redesign: an overview and qualitative evaluation of successful redesign heuristics , 2005 .

[124]  M. Porter.  Competitive Advantage: Creating and Sustaining Superior Performance , 1985 .

[125]  Nelly Condori-Fernández,et al.  Evaluating the Completeness and Granularity of Functional Requirements Specifications: A Controlled Experiment , 2009, 2009 17th IEEE International Requirements Engineering Conference.

[126]  A.M. Davis,et al.  System Phenotypes , 2003, IEEE Softw..

[127]  Mario Piattini Velthuis,et al.  Measurement in business processes: a systematic review , 2010 .

[128]  Chris Marshall,et al.  Enterprise modeling with UML , 1999 .

[129]  Ken Lunn,et al.  Business processes--attempts to find a definition , 2003, Inf. Softw. Technol..

[130]  Eng Wah Lee,et al.  Business process management (BPM) standards: a survey , 2009, Bus. Process. Manag. J..

[131]  C. Woo,et al.  A Methodology for Discovering Goals at Different Organizational Levels , 2008 .

[132]  Jörg Becker,et al.  Exploring the Status Quo of Business Process Modelling Languages in the Banking Sector – An Empirical Insight into The Usage of Methods in Banks , 2010 .

[133]  Heather A. Smith,et al.  Making IT Happen: Critical Issues in IT Management , 2003 .

[134]  Selmin Nurcan,et al.  Intentional Perspectives on Information Systems Engineering , 2010 .

[135]  Michael Rosemann,et al.  Process Management: A Guide for the Design of Business Processes , 2011 .

[136]  Jeffrey Parsons,et al.  Understanding the Role of Use Cases in UML: A Review and Research Agenda , 2000, J. Database Manag..

[137]  Camille Salinesi,et al.  A method to analyse changes in the realisation of business intentions and strategies for information system adaptation , 2002, Proceedings. Sixth International Enterprise Distributed Object Computing.

[138]  Bruce Campbell,et al.  Alignment: Resolving Ambiguity within Bounded Choices , 2005, PACIS.

[139]  Colette Rolland,et al.  A multi-method for defining the organizational change , 2003, Inf. Softw. Technol..

[140]  Ingrid Lunt,et al.  Real World Research (2nd ed.) by Colin Robson , 2006 .

[141]  Søren Lauesen,et al.  Use Cases versus Task Descriptions , 2011, REFSQ.

[142]  Jerry N. Luftman,et al.  Key Issues for IT Executives 2010: Judicious IT Investments Continue Post-Recession , 2010, MIS Q. Executive.

[143]  Jeffrey Parsons,et al.  How UML is used , 2006, CACM.

[144]  Sandra Seiz,et al.  On a Study of Layout Aesthetics for Business Process Models Using BPMN , 2010, BPMN.

[145]  Keng Siau,et al.  Are use case and class diagrams complementary in requirements analysis? An experimental study on use case and class diagrams in UML , 2004, Requirements Engineering.

[146]  François B. Vernadat,et al.  Enterprise Modelling and Integration , 2002, ICEIMT.

[147]  Michael zur Muehlen,et al.  Service Process Innovation: A Case Study of BPMN in Practice , 2008, Proceedings of the 41st Annual Hawaii International Conference on System Sciences (HICSS 2008).

[148]  Roel Wieringa,et al.  Requirements researchers: are we really doing research? , 2005, Requirements Engineering.

[149]  Colette Rolland,et al.  A decision-making pattern for guiding the enterprise knowledge development process , 2000, Inf. Softw. Technol..

[150]  Howard Smith,et al.  Business Process Management: The Third Wave , 2003 .

[151]  Mark Strembeck,et al.  On the Cognitive Effectiveness of Routing Symbols in Process Modeling Languages , 2010, BIS.

[152]  Janis A. Bubenko,et al.  Requirements Engineering and Technology Transfer: Obstacles, Incentives and Improvement Agenda , 2002, Requirements Engineering.

[153]  Tony Gorschek,et al.  Requirements Abstraction Model , 2005, Requirements Engineering.

[154]  Oscar Pastor,et al.  Model-driven architecture in practice - a software production environment based on conceptual modeling , 2007 .

[155]  Iris Vessey,et al.  Requirements specification: learning object, process, and data methodologies , 1994, CACM.

[156]  Per Runeson,et al.  Using Students as Experiment Subjects – An Analysis on Graduate and Freshmen Student Data , 2003 .

[157]  João Araújo,et al.  Mdgore: Towards Model-Driven and Goal-Oriented Requirements Engineering , 2010, 2010 18th IEEE International Requirements Engineering Conference.

[158]  John Mylopoulos,et al.  Integrating organizational requirements and object oriented modeling , 2001, Proceedings Fifth IEEE International Symposium on Requirements Engineering.

[159]  Oscar Pastor,et al.  Transformation templates: adding flexibility to model-driven engineering of user interfaces , 2010, SAC '10.

[160]  Georg Kösters,et al.  Coupling Use Cases and Class Models as a Means for Validation and Verification of Requirements Specifications , 2001, Requirements Engineering.

[161]  Colette Rolland,et al.  Modeling Goals and Reasoning with Them , 2005 .

[162]  Remco M. Dijkman,et al.  The Business Process Modeling Notation , 2010, Modern Business Process Automation.

[163]  Marta Indulska,et al.  A Study of the Evolution of the Representational Capabilities of Process Modeling Grammars , 2006, CAiSE.

[164]  Bruce Silver,et al.  Bpmn Method And Style , 2009 .

[165]  June M. Verner,et al.  Defining and contributing to software development success , 2006, CACM.

[166]  Mike Cohn,et al.  User Stories Applied: For Agile Software Development , 2004 .

[167]  Alistair Cockburn,et al.  Writing Effective Use Cases , 2000 .

[168]  Hajo A. Reijers,et al.  Product-Based Workflow Design , 2003, J. Manag. Inf. Syst..

[169]  Sara Jones,et al.  Informing the Specification of a Large-Scale Socio-technical System with Models of Human Activity , 2007, REFSQ.

[170]  Harald C. Gall,et al.  Generation of Business Process Models for Object Life Cycle Compliance , 2007, BPM.

[171]  Oscar Pastor,et al.  Evaluating the usefulness of a functional size measurement procedure to detect defects in MDD models , 2010, ESEM '10.

[172]  Arlene Fink,et al.  The Survey Handbook , 1995 .

[173]  Patrick Heymans,et al.  Visual syntax does matter: improving the cognitive effectiveness of the i* visual notation , 2010, Requirements Engineering.

[174]  Sjaak Brinkkemper,et al.  Conceptual Modelling in Information Systems Engineering , 2007 .

[175]  Thomas H. Davenport,et al.  Process Innovation: Reengineering Work Through Information Technology , 1992 .

[176]  Cláudia Maria Lima Werner,et al.  Precise specification and validation of transactional business software , 2004, Proceedings. 12th IEEE International Requirements Engineering Conference, 2004..

[177]  Larry L. Constantine,et al.  Software for Use - A Practical Guide to the Models and Methods of Usage-Centered Design , 1999 .

[178]  Suzanne Robertson,et al.  Mastering the Requirements Process (2nd Edition) , 2006 .

[179]  Johann Schumann,et al.  Generating statechart designs from scenarios , 2000, Proceedings of the 2000 International Conference on Software Engineering. ICSE 2000 the New Millennium.

[180]  Michael A. Jackson,et al.  Software requirements and specifications - a lexicon of practice, principles and prejudices , 1995 .

[181]  Janis Stirna,et al.  Anti-patterns as a Means of Focusing on Critical Quality Aspects in Enterprise Modeling , 2009, BMMDS/EMMSAD.

[182]  Michael E. Whitman,et al.  IT divergence in reengineering support: Performance expectations vs. perceptions , 1996, Inf. Manag..

[183]  Patrick McDermott,et al.  Workflow Modeling: Tools for Process Improvement and Application Development , 2001 .

[184]  Pourya Shaker.  Feature-oriented requirements modelling , 2010, 2010 ACM/IEEE 32nd International Conference on Software Engineering.

[185]  Volker Gruhn,et al.  Reducing the cognitive complexity of business process models , 2009, 2009 8th IEEE International Conference on Cognitive Informatics.

[186]  Sven Apel,et al.  An Overview of Feature-Oriented Software Development , 2009, J. Object Technol..

[187]  Richard Berntsson-Svensson,et al.  Successful software project and products: An empirical investigation , 2006, ISESE '06.

[188]  Ghassan Beydoun,et al.  A field study of the requirements engineering practice in Australian software industry , 2007, Requirements Engineering.

[189]  Rik Eshuis,et al.  Symbolic model checking of UML activity diagrams , 2006, TSEM.

[190]  Björn Regnell,et al.  What Happened to Our Features? Visualization and Understanding of Scope Change Dynamics in a Large-Scale Industrial Setting , 2009, 2009 17th IEEE International Requirements Engineering Conference.

[191]  Alan M. Davis,et al.  Good requirements practices are neither necessary nor sufficient , 2005, Requirements Engineering.

[192]  Jianwen Su,et al.  Towards Formal Analysis of Artifact-Centric Business Process Models , 2007, BPM.

[193]  Henk Sol,et al.  Information Systems Methodologies: A Framework for Understanding , 1988 .

[194]  Remco M. Dijkman,et al.  Semantics and analysis of business process models in BPMN , 2008, Inf. Softw. Technol..

[195]  Colette Rolland,et al.  From conceptual modelling to requirements engineering , 2000, Ann. Softw. Eng..

[196]  Per Runeson,et al.  Guidelines for conducting and reporting case study research in software engineering , 2009, Empirical Software Engineering.

[197]  Hiroyuki Ohsaki,et al.  Message from the workshop organizers , 2012, VR 2012.

[198]  Neil A. M. Maiden,et al.  PRiM: An i*-based process reengineering method for information systems specification , 2008, Inf. Softw. Technol..

[199]  Yair Wand,et al.  Emancipating instances from the tyranny of classes in information modeling , 2000, TODS.

[200]  David Chenho Kung,et al.  Status report: requirements engineering , 1993, IEEE Software.

[201]  Andrea Taylor-Cummings,et al.  Bridging the user-IS gap: a study of major information systems projects , 1998, J. Inf. Technol..

[202]  Detmar W. Straub,et al.  Information Technology Adoption Across Time: A Cross-Sectional Comparison of Pre-Adoption and Post-Adoption Beliefs , 1999, MIS Q..

[203]  Jörg Becker,et al.  Guidelines of Business Process Modeling , 2000, Business Process Management.

[204]  John M. Wilson,et al.  Business Processes: Modelling and Analysis for Re-engineering and Improvement , 1995 .

[205]  Michael W. Godfrey,et al.  Concept identification in object-oriented domain analysis: why some students just don't get it , 2005, 13th IEEE International Conference on Requirements Engineering (RE'05).

[206]  Izak Benbasat,et al.  Factors That Influence the Social Dimension of Alignment Between Business and Information Technology Objectives , 2000, MIS Q..

[207]  Jon Atle Gulla,et al.  Understanding requirements in enterprise systems projects , 2004, Proceedings. 12th IEEE International Requirements Engineering Conference, 2004..

[208]  H. Harrington.  Business process improvement : the breakthrough strategy for total quality, productivity, and competitiveness , 1991 .

[209]  Martin Glinz,et al.  Object-oriented modeling with A , 2002, Inf. Syst..

[210]  Pierre-Yves Schobbens,et al.  What ' s in a Feature ? A Requirements Engineering Perspective , 2008 .

[211]  Wil M. P. van der Aalst,et al.  On the Suitability of BPMN for Business Process Modelling , 2006, Business Process Management.

[212]  Ruth Sara Aguilar-Savén,et al.  Business process modelling: Review and framework , 2004 .

[213]  Keng Siau,et al.  Unified Modeling Language: A Complexity Analysis , 2001, J. Database Manag..

[214]  Erik Kamsties,et al.  Requirements engineering in small and medium enterprises , 1998, Requirements Engineering.

[215]  Akhil Kumar,et al.  A Framework for Document-Driven Workflow Systems , 2005, Business Process Management.

[216]  Santhosh Kumaran,et al.  On the Duality of Information-Centric and Activity-Centric Models of Business Processes , 2008, CAiSE.

[217]  Jinwoo Kim,et al.  How Do We Understand a System with (So) Many Diagrams? Cognitive Integration Processes in Diagrammatic Reasoning , 2000, Inf. Syst. Res..

[218]  Fei Peng,et al.  Understanding Chinese Characteristics of Requirements Engineering , 2009, 2009 17th IEEE International Requirements Engineering Conference.

[219]  Bashar Nuseibeh,et al.  Requirements engineering: a roadmap , 2000, ICSE '00.

[220]  Roel Wieringa.  Requirements Engineering Research Methodology: Principles and practice , 2008 .

[221]  Alain Wegmann,et al.  Where do goals come from: the underlying principles of goal-oriented requirements engineering , 2005, 13th IEEE International Conference on Requirements Engineering (RE'05).

[222]  John Mylopoulos,et al.  Towards requirements-driven information systems engineering: the Tropos project , 2002, Inf. Syst..

[223]  Tony Gorschek,et al.  A method for evaluating rigor and industrial relevance of technology evaluations , 2011, Empirical Software Engineering.

[224]  Marta Indulska,et al.  Business Process Modeling: Current Issues and Future Challenges , 2009, CAiSE.

[225]  Fausto Giunchiglia,et al.  Tropos: An Agent-Oriented Software Development Methodology , 2004, Autonomous Agents and Multi-Agent Systems.

[226]  Jan Mendling,et al.  The Impact of Secondary Notation on Process Model Understanding , 2009, PoEM.

[227]  Jan Mendling,et al.  Activity labeling in process modeling: Empirical insights and recommendations , 2010, Inf. Syst..

[228]  Ying Liang,et al.  From use cases to classes: a way of building object model with UML , 2003, Inf. Softw. Technol..

[229]  Eric Yu,et al.  Modeling Strategic Relationships for Process Reengineering , 1995, Social Modeling for Requirements Engineering.

[230]  Peter Kawalek,et al.  Goal-based business process models: creation and evaluation , 1997, Bus. Process. Manag. J..

[231]  Remco M. Dijkman,et al.  Deriving use case diagrams from business process models , 2002 .

[232]  David Budgen,et al.  The application of use cases in systems analysis and design specification , 2003, Inf. Softw. Technol..

[233]  Olivia R. Liu Sheng,et al.  Formulating the Data-Flow Perspective for Business Process Management , 2006, Inf. Syst. Res..