Defining goals in a COTS-aware requirements engineering approach

Systems Engineering

Volumn 7, Issue 1, 2004, Pages 61-83

  Chung, Lawrence ^a   Cooper, Kendra ^a  

^a The University of Texas at Dallas   (United States)

Author keywords

Agent orientation; CARE approach; COTS components; Goal orientation; Requirements engineering

Indexed keywords

AGENT ORIENTATION; CARE APPROACH; COTS COMPONENTS; GOAL ORIENTATION;

COMPUTATIONAL COMPLEXITY; CUSTOMER SATISFACTION; DIGITAL LIBRARIES; MATHEMATICAL MODELS; SOFTWARE ENGINEERING; SYSTEMS ENGINEERING;

REQUIREMENTS ENGINEERING;

EID: 12344312366     PISSN: 10981241     EISSN: 15206858     Source Type: Journal    
DOI: 10.1002/sys.10055     Document Type: Article

References (66)

1. C. Abts, A perspective on the economic life span of COTS-based software systems: The COTS-LIMO model, TR USC-CSE-2000-503, U.S.C. Center for Software Engineering, University of Southern California, Los Angeles, 2000.
2. E. Addy, A framework for performing verification and validation in reuse-based software engineering, Ann Software Eng 5 (1998), 279-292.
3. M. Addy and M. Sitaraman, Bridging the gap between COTS product reuse and formal methods: A case study, Technical Report NASA-IVV-98-016, NASA/WVU Software Research Lab, Fairmont, WV, 1998.
4. M. Addy and M. Sitaraman, Formal specification of COTS-based software: A case study, Proc 5th Symp Software Reusability, 1999, pp. 83-91.
5. A.I. Antón and C. Potts, The use of goals to surface requirements for evolving systems, Int. Conf Software Engineering, Kyoto, Japan, 19-25 April 1998, pp. 157-166.
6. K. Ballurio, B. Scalzo, and L. Rose, "Risk reduction in COTS software selection with BASIS," Lecture Notes in Computer Science 2255, J.C. Dean and A. Gravel (Editors), Springer-Verlag, New York, 2002, pp. 31-43.
7. V.R. Basili and B. Boehm, COTS-based systems top 10 list, IEEE Comput 34(5) (2001), 91-95.
8. L. Beus-Dukic and A. Wellings, Requirements for a COTS software component: a case study, Requirements Eng 3(2) (1998), 115-120.
9. B. Boehm, Requirements that handle IKIWISI, COTS, and rapid change, IEEE Comput 33(7) (2000), 99-102.
10. B. Boehm, D. Port, M. Abi-Antoun, and A. Egyed, Guidelines for the Life Cycle Objectives (LCO) and the Life Cycle Architecture (LCA) deliverables for Model-Based Architecting and Software Engineering (MBASE),TR USC-CSE-98-519, U.S.C. Center for Software Engineering, University of Southern California, Los Angeles, 1998.
11. C. Braun, Organizing for the effective reuse of commercial off-the-shelf (COTS) software, Proc 6th Int Conf Fuzzy Theory and Technology, Research Triangle Park, NC, 23-28 October 1998, Vol. 3, pp. 503-506.
12. E. Brenner and I. Derado, Specifying a certification process for COTS software components using UML, Proc 4th IEEE Int Symp Object-Oriented Real-Time Distributed Comput, Magdeburg, Germany, 2-4 May 2001, pp. 291 - 297.
13. L.C. Briand, COTS evaluation and selection, Proc Int Conf Software Maintenance, 16-19 November 1998, Bethesda, MD, pp. 222-223.
14. L. Brownsword, D. Carney, and T. Oberndorf, The opportunities and complexities of applying commercial-off-theshelf components, CrossTalk 11 (April 1998), 4-6.
15. L. Brownsword, T. Oberndorf, and C.A. Sledge, Developing new processes for COTS-based systems, IEEE Software 17(4) (2000), 48-55.
16. S. Bussman and J. Muller, A negotiation framework for co-operating agents, Proc CKBS-SIG, Dake Centre, The University of Keele, 1992, pp. 1-17.
17. D. Carney, S.A. Hissam, and D. Plakosh, Complex COTS-based software systems: practical steps for their maintenance, J Software Maintenance Res Practice 12(6) (2000), 357-376.
18. L. Chung and K. Cooper, Towards a Model-based COTS-aware Requirements Engineering process, Proc Model Based Requirements Eng Workshop, 30 November 2001, San Diego, CA, pp. 52-61.
19. L. Chung and K. Cooper, A COTS-Aware Requirements Engineering (CARE) process: Defining system level agents, goals and requirements, Version 2, TR UTDCS-11-02, Department of Computer Science, The University of Texas at Dallas, 2002a.
20. L. Chung and K. Cooper, A COTS-Aware Requirements Engineering process, Proc Int Council Syst Eng Symp, 28 July-1 August 2002b, Las Vegas, NV, Paper 3.5.4, pp. 1-8.
21. L. Chung and K. Cooper, A framework for adaptable COTS-aware software architecting, Comput Stand Interfaces 25(3) (2003a), 223-231.
22. L. Chung and K. Cooper, Defining an architecture with a COTS-Aware Software Engineering process, Proc Int Council Syst Eng Symp, 29 June-3 July 2003b, Arlington, VA, pp. 1219-1228.
23. L. Chung, B. Nixon, E. Yu, and J. Mylopoulos, Non-functional requirements in software engineering, Kluwer Academic, New York, 2000.
24. A.M. Davis, Software requirements: Objects, functions, states, Prentice-Hall, Englewood Cliffs, NJ, 1993.
25. J.C. Dean, Ensuring the capability of COTS products, Proc 23rd Annu Int Comput Software Appl Conf, 25-26 October 1999, Phoenix, AZ, pp. 96-97.
26. A. Egyed, P. Grunbacher, and N. Medvidovic, Refinement and evolution issues in bridging requirements and architecture - the CBSP approach, Proc 1st Int Workshop From Software Requirements to Architectures, 2001, http://www.cin.ufpe.br/~straw01.
27. H. Erdogmus and J. Vandergraaf, Quantitative approaches for assessing the value of COTS-centric development, Proc 6th Int Symp Software Metrics, 4-6 November 1999, Boca Raton, FL, pp. 279-290.
28. Federal Information Processing Standard (FIPS), Publication 183, Integration Definition for Function Modeling (IDEFO), 21 December 1993.
29. P. Goodwin and G. Wright, Decision analysis formanagement judgment, 2nd edition, John Wiley & Sons, New York, 1999.
30. S. Greenspan, J. Mylopolous, and A. Borgida, On formal requirements modeling languages: RML revisited, Proc 16th Int Conf Software Eng, 16-21 May 1994, Sorrento, Italy, pp. 135-147.
31. J. Hall and R. Naff, The cost of COTS, IEEE Aerospace Electron Syst Mag 16(8) (2001), 20-24.
32. S. Hissam, Experience report: Correcting system failure in a COTS information system, Proc Int Conf Software Maintenance, 16-19 November 1998, Bethesda, MD, pp. 170-176.
33. S. Hissam and D. Carney, Isolating faults in complex COTS-based systems, J Software Maintenance Res Practice 11 (3) (1999), 183-199.
34. S. Hissam, G. Moreno, J. Stafford, and K. Wallnau, Packaging predictable assembly, Proc IFIP/ACM Working Conf Component Deployment, 21-22 June 2002, Berlin, Germany, Lecture Notes in Computer Science 2370, J. Bishop (Editor), Springer-Verlag, New York, pp. 108-124.
35. D. Hybertson, A. Ta, and W. Thomas, Maintenance of COTS-intensive software systems, J Software Maintenance 9(4) (1997), 203-216.
36. X. Illa, X. Franch, and J. Pastor, Formalising ERP selection criteria, Proc 10th Int Workshop Software Specification Des, 5-7 November 2000, San Diego, CA, pp. 115-122.
37. H. In, R. Kazman, and D. Olson, From requirements negotiation to software architectural decisions, Proc 1st Int Workshop From Software Requirements to Architectures, 2001, http://www.cin.ufpe.br/~straw01.
38. M. Jackson, System development, Prentice-Hall, Englewood Clifffs, NJ, 1983.
39. I. Jacobson, G. Booch, and J. Rumbaugh, The Unified Software development process, Addison Wesley Longman, Reading, MA, 1999.
40. R. Jensen, Estimating the cost of reuse, CrossTalk 10(5) (1997), 17-21.
41. J. Kontio, OTSO: A systematic process for reusable software component selection, University of Maryland, Technical Report, December 1995.
42. K. Korel, Black-box understanding of COTS components, Proc 7th Int Workshop Program Comprehension, 24-26 June 1998, Ischia, Italy, pp. 92-99.
43. P. Krachten, Modeling component systems with the Unified Modeling Language, Proc Int Workshop Component-Based Software Eng, 25-26 April 1998, Kyoto, Japan, http://www.sei.cmu.edu/activities/cbs/icse98/.
44. P. Krutchen, What is the Rational Unified Process?, Rational Edge e-zine (January 2001), http://www.therationaledge.com/content/jan_01/f_rup_pk.html.
45. D. Kunda and L. Brooks, Applying social-technical approach for COTS selection, Proc 4th UK Acad Inform Syst Conf, 7-9 April 1999, University of York, pp. 552-565.
46. P. Loucopoulos and P. Karakostas, System requirements engineering, McGraw-Hill, New York, 1995.
47. N. Maiden, H. Kim, and C. Ncube, "Rethinking process guidance for software component selection," Lecture Notes in Computer Science 2255, J.C. Dean and A. Gravel (Editors), Springer-Verlag, New York, 2002, pp. 151 -164.
48. M. Morisio and A. Tsoukias, IusWare: A methodology for the evaluation and selection of software products, IEE Proc Software Eng 144(3) (1997), 162-174.
49. M. Morisio, C.B. Seaman, A. Parra, V. Basili, S. Kraft, and S. Condon, Investigating and improving a COTS-based software development process, Proc Int Conf Software Eng, 4-11 June 2000, Limerick, Ireland, pp. 32-41.
50. A. Morris, COTS score: An acceptance methodology for COTS software, Proc 19th Digital Avionics Syst Conf, Philadelphia, Vol. 1, pp. 1-8.
51. J. Mylopoulos, A. Borgida, M. Jarke, and M. Koubarakis, Telos: Representing knowledge about information systems, ACM Trans Inform Syst 8(4) (1990), 325-362.
52. J. Mylopoulos, L. Chung, and B. Nixon, Representing and using nonfunctional requirements: a process-oriented approach, IEEE Trans Software Eng 18(6) (1992), 483-497.
53. C. Ncube and N. Maiden,"Guiding parallel requirements acquisition and COTS software selection, Proc IEEE Int Symp Requirements Eng, 7-11 June 1999, Limerick, Ireland, pp. 133-140.
54. B. Nuseibeh, Weaving the software development process between requirements and architectures, Proc 1st Int Workshop From Software Requirements to Architectures, 2001, http://www.cin.ufpe.br/~straw01.
55. R. Seacord, D. Mundie, and S. Boonsiri, K-BACEE: Knowledge-based automated component ensemble evaluation, Proc Workshop Component-Based Software Eng, 6-8 September 2001, Warsaw, Poland, pp. 56-63.
56. M. Shaw and D. Garlan, Software architecture: Perspectives on an emerging discipline, Prentice-Hall, Englewood Cliffs, NJ, 1996.
57. A. van Lamsweerde and E. Letier, Handling obstacles in goal-oriented requirements engineering, IEEE Trans Software Eng (Special Issue on Exception Handling) 26(10) (2000), 978-1005.
58. M. Vidger and J.C. Dean, Building maintainable COTS based systems, Proc Int Conf Software Maintenance, 16-19 March 1998, Bethesda, MD, pp. 132-138.
59. J. Voas, COTS software: The economical choice?, IEEE Software 15 (March/April 1998a), 16-19.
60. J. Voas, The challenges of using COTS software in component based development, IEEE Comput 31 (June 1998b), 44-45.
61. M. Wooldridge and P. Ciancarini, "Agent-oriented software engineering: The state of the art," Handbook of software engineering and knowledge engineering, P. Ciancarini and W. Wooldridge (Editors), World Scientific, Singapore, 2001, pp. 1-28.
62. M. Wooldridge, N.R. Jennings, and D. Kinny, A methodology for agent-oriented analysis and design, Proc 3rd Int Conf Autonomous Agents, 1-5 May 1999, Seattle, WA, pp. 69-76.
63. I. Yen, L. Khan, B. Prabhakaran, F.B. Bastani, and J. Linn, An on-line repository for embedded software, Proc 13th Int Conf Tools with Artificial Intelligence, 7-9 November 2001, Dallas, TX, pp. 314-321.
64. I. Yen, J. Goluguri, F. Bastani, L. Khan, and J. Linn, A component-based approach for embedded software development, Proc 5th Int Symp Object-Oriented Real-Time Distributed Comput, 29 April-1 May 2002, Washington, DC, pp. 402-410.
65. E. Yu, Modelling strategic relationships for process reengineering, DKBS-TR-94-6, The University of Toronto, Canada, December 1994.
66. E. Yu, Agent orientation as a modelling paradigm, Wirtschaftsinformatik 43(2) (2001), 123-132.