Intention driven conceptual modelling

Information Systems Engineering: From Data Analysis to Process Networks

Volumn , Issue , 2008, Pages 16-42

  Rolland, Colette ^a  

^a UNIVERSITÉ PARIS 1 PANTHÉON SORBONNE   (France)

Author keywords

[No Author keywords available]

Indexed keywords

EID: 84892202088     PISSN: None     EISSN: None     Source Type: Book    
DOI: 10.4018/978-1-59904-567-2.ch002     Document Type: Chapter

References (69)

1. Antòn, A. I., & Potts, C. (1998). The use of goals to surface requirements for evolving systems. International Conference on Software Engineering (ICSE '98), Kyoto, Japan, (pp. 157-166).
2. Antòn, A. I., Carter, R., Dagnino, A., Dempster, J., & Siege, D. F. (2001). Deriving Goals from a Use-Case Based Requirements Specification. Requirements Engineering Journal, 6, 63-73.
3. Ackoff, R. L., & Emery, R. E. (1972). On purposeful systems, Aldine-Atherton, Chicago.
4. Bachmann, F., & Bass, L. (2001). Managing variability in software architecture. ACM Press, NY, USA.
5. Boehm, B., Bose, P., Horowitz, E., & Lee, M. J. (1994). Software requirements as negotiated win conditions. In 1st International Conference on Requirements Engineering (pp. 74-83), USA.
6. Bosch, J., & Svahnberg, M. (2001). Variability Issues in Software Product Lines. 4th International Workshop on Product Family Engineering (PEE-4), Bilbao, Spain.
7. Bubenko, J., Rolland, C., Loucopoulos, P., & de Antònellis, V. (1994). Facilitating fuzzy to formal requirements modelling. In IEEE 1st Conference on Requirements Enginering, ICRE'94 (pp. 154-158).
8. Chung, K. L., Nixon, B. A., Yu, E., & Mylopoulos, J. (2000). Non- Functional Requirements in Software Engineering. Kluwer Academic Publishers (pp. 440).
9. Cockburn, A. (1995). Structuring use cases with goals (Tech. Rep). Human and Technology, 7691 Dell Rd, Salt Lake City, UT 84121, HaT.TR.95.1.
10. Dano, B., Briand, H., & Barbier, F. (1997). A use case driven requirements engineering process. In 3rd IEEE International Symposium On Requirements Engineering RE'97, Antapolis, Maryland, USA.
11. Dardenne, A., Lamsweerde, A. V., & Fickas, S. (1993). Goal-directed Requirements Acquisition. Science of Computer Programming, 20, Elsevier, 3-50.
12. Darimont, R., van Lamsweerde, A., & Letier, E. (1998). Managing Conflicts in Goal-Driven Requirements Engineering. IEEE Transactions on Software Engineering, 24(11), 908-926.
13. th International Workshop on software Specification and design (pp. 34-42). IEEE CS Press.
14. Dubois, E., Hagelstein, J., & Rifaut, A. (1989). Formal Requirements Engineering with ERAE. Philips Journal of Research, 43(4).
15. Easterbrook, S. M. (1994). Resolving Requirements Conflicts with Computer- Supported Negotiation. In M. Jirotka & J. Goguen (Eds.), Requirements Engineering: Social and Technical Issues (pp. 41-65), London: Academic Press.
16. European Software Institute (1996). European User Survey Analysis. Report USV_EUR 2.1, ESPITI Project.
17. Gotel, O., & Finkelstein, A. (1994). Modelling the contribution structure underlying requirements. In 1st Int. Workshop on Requirements Engineering: Foundation of Software Quality, Utrech, Netherlands.
18. Halmans, J. (2003). Communicating the variability of a software product family to customers. Software and System Modeling, Springer-Verlag.
19. Haumer, P., Pohl, K., & Weidenhaupt, K. (1998). Requirements elicitation and validation with real world scenes. IEEE Transactions on Software Engineering, Special Issue on Scenario Management, In M. Jarke, R. Kurki-Suonio (Eds.), 24(12), 1036-1054.
20. Hoh, P. (2002). Multi-Criteria Preference Analysis for Systematic Requirements Negotiation. In 26th Annual International Computer Software and Applications Conference (pp. 887), Oxford, England.
21. Hui, B., Liaskos, S., & Mylopoulos, J. (2003). Requirements Analysis for Customizable Software: A Goals-Skills-Preferences Framework. In IEEE Conference on Requirements Engineering (pp. 117-126), Monterey Bay, USA.
22. Ivankina, E., & Salinesi, C. (2004). An Approach to Guide Requirement Elicitation by Analysing the Causes and Consequences of Threats. In 14th European - Japanese Conference on Information Modelling and Knowledge Bases, Skövde, Sweden.
23. Jackson, M. (1995). Software Requirements & Specifications - a Lexicon of Practice, Principles and Prejudices. ACM Press. Addison-Wesley.
24. Jacobson, I. (1995). The Use case construct in object-oriented software engineering. In J. M. Carroll (Ed.), Scenario-Based Design: Envisioning Work and Technology in System Development (pp. 309-336).
25. Johnson, J. (1995). Chaos: the Dollar Drain of IT project Failures. Application Development Trends, 41-47.
26. Kaindl, H. (2000). A design process based on a model combining scenarios with goals and functions. IEEE Trans. on Systems, Man and Cybernetic, 30(5), 537-551.
27. Kang, K., Cohen, S., Hess, J., Novak, W., & Peterson, A. (1990). Feature- Oriented Domain analysis (FODA) Feasibility Study (Tech. Rep. CMU/SEI-90-TR-21), Pittsburgh, PA, Software Engineering Institute, Carnegie Mellon University.
28. Karlsson, J., Olsson, S., & Ryan, K. (1997). Improved Practical Support for Large-scale Requirements Prioritizing. Journal of Requirements Engineering, Springer-Verlag, 51-60.
29. Lamsweerde, A. V., Dardenne, B., Delcourt, & Dubisy, F. (1991). The KAOS project: knowledge acquisition in automated specification of software. Proc. AAAI Spring Symp. Series, Track: "Design of Composite Systems", (pp. 59-62), Stanford University.
30. Lamsweerde, A. V. (2001). Goal-oriented requirements engineering: a guided tour. In RE'01 International Joint Conference on Requirements Engineering (pp. 249-263), Toronto.
31. Lamsweerde, A. V., & Letier, E. (2000). Handling obstacles in goal-oriented requirements engineering. IEEE Transactions on Software Engineering, Special Issue on Exception Handling, 26(10), 978-1005.
32. Lamsweerde, A. V., & Willemet, L. (1998). Inferring declarative requirements specifications from operational scenarios. In IEEE Transactions on Software Engineering, Special Issue on Scenario Management. 24(12), 1089-1114.
33. Lee, S. P. (1997). Issues in requirements engineering of object-oriented information system: a review. Malaysian Journal of computer Science, 10(2).
34. Leite, J. C. S., Rossi, G., Balaguer, F., Maiorana, A., Kaplan, G., Hadad, G., & Oliveros, A. (1997). Enhancing a requirements baseline with scenarios. In 3rd IEEE International Symposium On Requirements Engineering RE'97 (pp. 44-53), Antapolis, Maryland.
35. Letier, E. (2001). Reasoning about agents in goal-oriented requirements engineering. Ph. D. Thesis, University of Louvain.
36. Loucopoulos, P., Kavakli, V., & Prakas, N. (1997). Using the EKD approach, the modelling component. ELEKTRA project internal report.
37. 3 (from fuzzy to formal) view on requirements engineering. Ingénierie des systèmes d'information, 2(6), 639-655.
38. META Group (2003). Research on Requirements Realization and Relevance, report.
39. Moisiadis, F. (2002). The Fundamentals of Prioritising Requirements Systems Engineering. Test & Evaluation Conference, Sydney, Australia.
40. Mostow, J. (1985). Towards better models of the design process. AI Magazine, 6, 44-57.
41. Mylopoulos, J., Chung, K. L., & Yu, E. (1999). From object-oriented to goal-oriented requirements analysis. Communications of the ACM, 42(1), 31-37.
42. Mylopoulos, J., Chung, K. L., & Nixon, B. A. (1992). Representing and using non- functional requirements: a process-oriented approach. In IEEE Transactions on Software Engineering, Special Issue on Knowledge Representation and Reasoning in Software Development 18(6), 483-497.
43. Nilsson, N. J. (1971). Problem Solving Methods in Artificial Intelligence. McGraw Hill.
44. Nuseibeh, B., Kramer, J., & Finkelstein, A. (1994). A framework for expressing the relationships between multiple views in requirements specification. In IEEE Transactions on Software Engineering, 20, 760-773.
45. Pohl, K., & Haumer, P. (1997). Modelling contextual information about scenarios. Proceedings of the Third International Workshop on Requirements Engineering: Foundations of Software Quality REFSQ'97 (pp. 187-204), Barcelona, Spain.
46. Pohl, K. (1996). Process centred requirements engineering. J. Wiley and Sons Ltd.
47. Potts, C. (1995). Using schematic scenarios to understand user needs. ACM Symposium on Designing interactive Systems:Processes, Practices and Techniques, University of Michigan, USA.
48. Potts, C., Takahashi, K., & Antòn, A. I. (1994). Inquiry-based requirements analysis. In IEEE Software 11(2), 21-32.
49. Ramesh, B., Powers, T., Stubbs, C., & Edwards, M. (1995). Implementing requirements traceability: a case study. In Proceedings of the 2nd Symposium on Requirements Engineering (RE'95) (pp. 89-95), UK.
50. Robinson, W.N., & Volkov, S. (1998). Supporting the Negotiation Life-Cycle. Communications of the ACM, 95-102.
51. Robinson, W. N., & Volcov, S. (1996). Conflict Oriented Requirements Restructuring. Working Paper CIS-96-15.
52. Robinson, W. N. (1989). Integrating multiple specifications using domain goals. Proc. IWSSD-5 - 5th Intl. Workshop on Software Specification and Design (pp. 219-225), IEEE.
53. Rolland, C. (2006). Aligning Business and System Functionality Through Model Matching, Systèmes d'Information et Management (SIM), Editions ESKA.
54. Rolland, C., Salinesi, C. & Etien, A. (2004). Eliciting Gaps in Requirements Change. Requirement Engineering Journal, 9, 1-15.
55. Rolland, C., & Prakash, N (2001). Matching ERP System Functionality to Customer Requirements. In Procs of the 5th IEEE International Symposium on Requirements Engineering, Toronto, Canada. August 27-31.
56. Rolland, C., & Prakash, N. (2000). Bridging the gap between Organizational needs and ERP functionality. Requirements Engineering journal 5.
57. Rolland, C., Grosz, G., & Kla, R. (1999a). Experience with goal-scenario coupling in requirements engineering. In Proceedings of the Fourth IEEE International Symposium on Requirements Engineering, Limerik, Ireland
58. Rolland, C., Prakash, N., & Benjamen, A. (1999b). A Multi-Model View of Process Modelling. Requirements Engineering Journal (REJ), 169-187.
59. Rolland, C., Souveyet, C., & Ben Achour, C. (1998). Guiding goal modelling using scenarios. IEEE Transactions on Software Engineering, Special Issue on Scenario Management, 24(12).
60. Ross, D. T., & Schoman, K.E. (1977). Structured Analysis for Requirements Definition. IEEE Transactions on Software Engineering, 3(1), 6-15.
61. Sommerville, I., & Sawyer, P. (1997). Requirements engineering. Worldwide Series in Computer Science, Wiley.
62. Standish Group (1995). The Chaos. Standish Group Internal Report.
63. Sutcliffe, A. G, & Minocha, S (1999a). Analyzing Socio-Technical System Requirements. CREWS project Report 98-37.
64. Sutcliffe, A. G., Galliers, J., Minocha, S. (1999b). Human Errors and System Requirements. International Symposium on Requirements Engineering, RE'1999. Limerick, Ireland.
65. Sutcliffe, A. G., Maiden, N. A., Minocha, S., & Darrel, M. (1998). Supporting scenario-based requirements engineering. IEEE Trans. Software Engineering 24(12), 1072-1088.
66. van Gurp, J., Bosch, J., & Svahnberg, M. (2001). On the notion of variability in Software Product Lines. In Procs of the Working IEEE/IFIP Conference on Software architecture.
67. van Gurp, J. (2000). Variability in Software Systems, the key to Software Reuse. Licentiate Thesis, University of Groningen, The Netherlands.
68. Yu, E. (1997). Towards Modelling and Reasoning Support for Early-Phase Requirements Engineering. In Procs of the 3rd IEEE International Symposium on Requirements Engineering (RE'97).
69. Yu, E. (1994). Modelling strategic relationships for process reengineering. Ph.D. Thesis, Dept. Computer Science, University of Toronto.