Portal de Periódicos da CAPES

Capabilities and Requirements Engineering: Research Challenges

2013; Wiley; Volume: 23; Issue: 1 Linguagem: Inglês

10.1002/j.2334-5837.2013.tb03041.x

2334-5837

Gonçalo Antunes, Ricardo Vieira, José Borbinha,

Service-Oriented Architecture and Web Services

INCOSE International SymposiumVolume 23, Issue 1 p. 590-605 Article Capabilities and Requirements Engineering: Research Challenges Gonçalo Antunes, Gonçalo Antunes [email protected] INESC-ID/IST, Lisbon, PortugalSearch for more papers by this authorRicardo Vieira, Ricardo Vieira [email protected] INESC-ID/IST, Lisbon, PortugalSearch for more papers by this authorJosé Borbinha, José Borbinha [email protected] INESC-ID/IST, Lisbon, PortugalSearch for more papers by this author Gonçalo Antunes, Gonçalo Antunes [email protected] INESC-ID/IST, Lisbon, PortugalSearch for more papers by this authorRicardo Vieira, Ricardo Vieira [email protected] INESC-ID/IST, Lisbon, PortugalSearch for more papers by this authorJosé Borbinha, José Borbinha [email protected] INESC-ID/IST, Lisbon, PortugalSearch for more papers by this author First published: 04 November 2014 https://doi.org/10.1002/j.2334-5837.2013.tb03041.xCitations: 3AboutPDF ToolsRequest permissionExport citationAdd to favoritesTrack citation ShareShare Give accessShare full text accessShare full-text accessPlease review our Terms and Conditions of Use and check box below to share full-text version of article.I have read and accept the Wiley Online Library Terms and Conditions of UseShareable LinkUse the link below to share a full-text version of this article with your friends and colleagues. Learn more.Copy URL Share a linkShare onEmailFacebookTwitterLinkedInRedditWechat Abstract The concept of capability can be used to provide a holistic view of a product or system, while offering new ways of dealing with complexity. Despite being a concept successfully adopted in several areas, there is opportunity for innovative usages in the engineering of systems. Traditionally, system development methods begin with the gathering and analysis of requirements, and as such, the final product is expected to be in line with the needs of the stakeholders. However, many engineering problems are often situated in complex socio-technical contexts, where systems are characterized as being highly contextual and uncertainty is a constant. Moreover, potential solutions might involve the adoption and integration of off-the-shelf solutions into the systems, or even the reutilization of existing solutions in different settings than those for which they were conceived initially, which is not particularly considered in nowadays engineering methods. This work proposes the usage of the concept of capability in requirements engineering, relating it to the concept of requirement. Based on this proposal, research challenges are identified. References Almisned, F., Keppens, J. 2010. Requirements Analysis: Evaluating KAOS Models. JSEA 3(9): 869–874. 10.4236/jsea.2010.39101 Google Scholar Anderson, P., and Kaplan, M. 2004. "Patterns of Capability Acquisition in Electronic Commerce." Journal of Strategic Management 12: 97–109. Google Scholar Bate, R., Garcia, S., Armitage, C., Cusick, K., Jones, R., Kuhn, D., Minnich, I., Pierson, H., Powell, T. Reichner, A., and Wells, C. 1994. " A Systems Engineering Capability Maturity Model, Version 1.0". Tech. Rep. CMU/SEI-94-HB-04. Software Engineering Institute, Carnegie Mellon University. Google Scholar Chandler, A. D. 1990. Scale and Scope: The Dynamics of Industrial Capitalism. Cambridge, MA (US): Harvard University Press. 10.4159/9780674029385 Google Scholar Chung, L., Nixon, B. A., Yu, E., Mylopoulos, J. 1999. Non-Functional Requirements in Software Engineering. International Series in Software Engineering, vol. 5, p. 476. Springer, Heidelberg. Google Scholar Electronic Industries Alliance. 2002. EIA-731.1 - Systems Engineering Capability Model. Government Electronics and Information Technology Association. Google Scholar C. Haskins, ed. 2010. Systems Engineering Handbook: A Guide for System Life Cycle Processes and Activities. Version 3.2. Revised by M. Krueger, D. Walden, and R. D. Hamelin. San Diego, CA (US): INCOSE. Google Scholar Henshaw, M. J. C., Kemp, D., Lister, P., Daw, A. J., Harding, A. D., Farncombe, A., and Touchin, M. 2011. " Capability Engineering: An Analysis of Perspectives". Paper presented at the Sixth Annual International Symposium of INCOSE, Denver, CO (US), 20–23 June. Google Scholar Humphrey, W. S. 1987. " Characterizing the Software Process: A Maturity Framework." Technical Report CMU/SEI-87-TR-11. Software Engineering Institute, Carnegie Mellon University. Google Scholar Humphrey, W. S., Sweet, W. L., Edwards, R. K., LaCroix, G. R., Owens, M. F., and Schulz, H. 1987. " A Method for Assessing the Software Engineering Capability of Contractors." Technical Report CMU/SEI-87-TR-23. Software Engineering Institute, Carnegie Mellon University. Google Scholar ISO and IEC (International Organisation for Standardisation and International Electrotechnical Commission). 2010. ISO/IEC TR 24748. Systems and Software Engineering – Life Cycle Management – Part 1: Guide for Life Cycle Management. Google Scholar ISO and IEC (International Organisation for Standardisation and International Electrotechnical Commission). 2011. ISO/IEC 25010. Systems and Software Engineering – Systems and Software Quality Requirements and Evaluation (SQuaRE) – System and Software Quality Models. Google Scholar ISO, IEC and IEEE (International Organisation for Standardisation, International Electrotechnical Commission and Institute of Electrical and Electronic Engineers). 2010. ISO/IEC/IEEE 24765. Systems and Software Engineering – Vocabulary. Google Scholar ISO, IEC and IEEE (International Organisation for Standardisation, International Electrotechnical Commission and Institute of Electrical and Electronic Engineers). 2011. Systems and Software Engineering – Architecture Description. Google Scholar Lamsweerde, A. V. 2001. Goal-Oriented Requirements Engineering: A Guided Tour. In Proceedings of the Fifth IEEE International Symposium on Requirements Engineering (RE '01). IEEE Computer Society, Washington, DC, USA, 249. Web of Science®Google Scholar Lamsweerde, A. V. 2009. Requirements Engineering: From System Goals to UML Models to Software Specifications. Wiley, West Sussex. Google Scholar Le, L. S., Ghose, A. K., and Morrison, E. 2010. " Definition of a Description Language for Business Service Decomposition". Proceedings of the 1st International Conference on Exploring Services Sciences. Google Scholar Nelson, R. R., and Winter, S. G. 1973. "Toward an Evolutionary Theory of Economic Capabilities." The American Economic Review 63: 440–449. Web of Science®Google Scholar Nelson, R. R., and Winter, S. G. 1985. An Evolutionary Theory of Economic Change. Cambridge, MA (US): Harvard University Press. Google Scholar Nuseibeh, B., and Easterbrook, S. 2000. Requirements engineering: a roadmap. In Proceedings of the Conference on The Future of Software Engineering (ICSE '00). ACM, New York, NY, USA, 35–46. Google Scholar Object Management Group. 2009. Service Oriented Architecture Modeling Language (SoaML) – Specification for the UML Profile and Metamodel for Services (UPMS). OMG Adopted Specification, Finalisation Task Force Beta 2 Document ptc/2009-12-09. Google Scholar Pagotto, J., and Walker, R. S. 2004. " Capability Engineering – Transforming Defence Acquisition in Canada". Proceedings of SPIE. Google Scholar Penrose, E. 1959. The Theory of the Growth of the Firm. New York, NY (US): John Wiley and Sons. Google Scholar Penserini, L., Perini, A., Susi, A., and Mylopoulos, J. 2007. "High Variability Design for Software Agents: Extending Tropos." ACM Transactions on Autonomous and Adaptive Systems 2(4): 16–27. 10.1145/1293731.1293736 Web of Science®Google Scholar Pohl, K. 2010. Requirements Engineering – Fundamentals, Principles, and Techniques. Springer, pp. I–XVII, 1–813. Google Scholar Ravichandar, R., Arthur, J. D., Bohner, S. A., and Tegarden, D. P. 2008. "Improving Change Tolerance Through Capabilities-based Design: an Empirical Analysis." Journal of Software Maintenance and Evolution: Research and Practice 20: 135–170. 10.1002/smr.367 Web of Science®Google Scholar Richardson, G. B. 1972. "The Organization of Industry". Economic Journal 82: 440–449. 10.2307/2230256 Web of Science®Google Scholar Sousa, P., Caetano, A., Vasconcelos, A., Pereira, C., and Tribolet, J. 2006. "Enterprise Architecture Modeling with the Unified Modeling Language." In Enterprise Modeling and Computing with UML, edited by P. Rittgen, 69–96. London (UK): Idea Group Publishing. Google Scholar Teece, D., and Pisano, G. 1994. " The Dynamic Capabilities of Firms: An Introduction." Working Paper, International Institute for Applied Systems Analysis. Google Scholar Teece, D., Pisano, G., and Shuen, A. 1997. "Dynamic Capabilities and Strategic Management". Strategic Management Journal 18: 509–533. 10.1002/(SICI)1097-0266(199708)18:7 3.0.CO;2-Z Web of Science®Google Scholar The Open Group. 2011. TOGAF Version 9.1. Zaltbommel (NL): Van Haren Publishing. Google Scholar UK Ministry of Defence. 2010. MOD Architecture Framework, Version 1.2.004. Ministry of Defence. Google Scholar US Department of Defense. 2001. Joint Publication 1-02: Department of Defense Dictionary of Military and Associated Terms. Washington, DC (US). Google Scholar US Department of Defense. 2010. DoD Architecture Framework, Version 2.02. Washington, DC (US): DoD Deputy Chief Information Office. Google Scholar Wiegers, K.E., 2003. Software Requirements ( 2 ed.). Microsoft Press, Redmond, WA, USA. Google Scholar Young, R. R. 2004. The Requirements Engineering Handbook. Artech House, London, United Kingdom. Google Scholar Yu, E. S. K. 1997. Towards modelling and reasoning support for early-phase requirements engineering. In: Proceedings of the Third IEEE International Symposium on Requirements Engineering, pp. 226–235. Google Scholar Citing Literature Volume23, Issue1Philadelphia, PA, June 24–27, 2013June 2013Pages 590-605 ReferencesRelatedInformation