An Approach to Supporting the Technical Solution in Organization-Oriented Software Development Environments

• Sávio Figueiredo UFRJ
• Ana Regina Rocha UFRJ
• Gleison Santos UFRJ
• Mariano Montoni UFRJ

DOI: https://doi.org/10.5753/sbqs.2006.15616

Abstract

The size and complexity of software products have been continuously increasing over the years. Moreover, the number of software projects that fail to finish inside the constraints of budget and schedule established and to deliver a product that addresses the needs of the customer, also increases significantly. In this context, the research with focus at software processes has began because people have realized that the software product quality is extremely dependent of the software process that has been adopted in order to develop the product. This work presents an approach to support the Technical Solution process, which is executed during the software development.

Keywords: Technical Solution, Software Development, Organization-Oriented

References

Boehm B. e Bose, P. (1994), A Collaborative Spiral Software Process Model Based on Theory W, Third International Conference on the Software Process, Reston, VA, pp. 59-68.

Bose, P. (1995), A Model for Decision Maintenance in the WinWin Collaboration Framework, Knowledge Based Software Engineering (KBSE '95), pp. 105-113.

Bouchriha, H., D ́Amours, S. e Ladet, P. (2002), A “make or buy” decision model with economies of scale, Article de conférence avec actes.

Burge, J. E. (2005), "Software Engineering Using design RATionale", PhD Dissertation, CS Dept., WPI, May.

Burge, J. E. e Brown, D. C. (2002), “Discovering a Research Agenda for Using Design Rationale in Software Maintenance”, Computer Science Technical Report, Worcester Polytechnic University, WPI-CS-TR-02-03.

Cánez, L., Probert, D. e Platts, K. (2001), Testing a Make-or-Buy Process, Proceedings of the Twelfth Annual Conference of the Production and Operations Management Society, POM-2001, March 30 – April 2, Orlando.

Chrissis, M. B., Konrad, M. e Shrum, S. (2003), CMMI: Guidelines for Process Integration and Product Improvement, Addison-Wesley.

Conklin, J., (1989), “Design Rationale and Maintainability”. Vol. II: Software Track, Proceedings of the Twenty-Second Annual Hawaii International Conference on Volume 2, 3-6 Jan. Page(s): 533-539. Vol. 2 Digital Object Identifier 10.11 09/HICSS. 1989.48049.

Conklin, J. e Burgess-Yakemovic, K., (1995), A Process-Oriented Approach to Design Rationale, In Design Rationale Concepts, Techniques, and Use, T. Moran and J. Carrol, (eds), Lawrence Erlbaum Associates, Mahwah, NJ, pp. 293-428.

Dellen, B., Kohler, K. e Maurer, F. (1996), Integrating Software Process Models and Design Rationales, In: Proceedings Knowledge-based Software Engineering, Syracuse, NY, IEEE Computer Society Press, pp. 84-93.

Figueiredo, S., Rocha, A.R., Santos, G., Montoni, M. e Natali, A.C., (2005), “Apoio à Manutenção de Software através de Design Rationale em Amb ientes de Manutenção de Software Taba” , II Workshop de Manutenção de Software Moderna (WMSWM -05), Manaus, Brasil.

Francisco, S. D. (2004), DocRationale - uma ferramenta para suporte a Design Rationale de artefatos de Software. São Carlos-SP, março de 2004. 123p. Dissertação de Mestrado. Instituto de Ciências Matemáticas e de Computação de São Carlos, Universidade de São Paulo.

Fuggeta, A. (2000), Software Process: A Roadmap. In: 22nd International Conference on the Future of Software Engineering, Limerick, Ireland: ACM -Association for Computing Machinery, p. 25-34.

Golubié, S. (2005), Influence of Software Development Process Capability on Product Quality, In: 8th International Conference on Telecommunications, Zagreb, Croatia, June 5-17.

Gomes, A. (2001), Avaliação de processos de software baseada em medições, Tese de MSc., COPPE/UFRJ, Rio de Janeiro, RJ, Brasil, Jul.

ISO/IEC 14102 (1995), Information technology - Guideline for the evaluation and selection of CASE tools.

Lee, J. (1990), SIBYL: a tool for managing design rationale. In: Proceedings o fthe Conference on Computer Supported Cooperative Work, Los Angeles, EUA, p. 79-92.

Lee, J. (1997), Design Rationale Systems: Understanding the issues. IEEE expert/Intelligent Systems and Their Applications, v. 12, n. 3, p. 78-85.

Lee, J. e Lai, K. (1991), What’s in design rationale. Human-Computer Interaction, 6(3-4): 251-280.

McCall, R. (1991), PHI: A Conceptual Foundation for Design Hypermedia. Design Studies 12, pp.30-41.

Montoni, M., (2003), Aquisição de Conhecimento no Desenvolvimento de Software, Tese de M. Sc., COPPE/UFRJ, Rio de Janeiro, RJ, Brasil.

MPS.BR (2005), MPS.BR - Melhoria de Processo do Software Brasileiro, Guia Geral (v. 1.0).

Sheard, S, A. (1997), The Frameworks Quagmire, A Brief Look, Technical Report, Software Productivity Consortium.

Shipman, F. e McCall, R. (1997), Integrating Different Perspectives on Design Rationale: Supporting the Emergence of Design Rationale from Design Communication. Artificial Intelligence in Engineering Design, Analysis, and Manufacturing, 11(2):141–154.

Souza, C, R. B., Wainer, J. e Rubira , C. M., R. (1997), An annotation model for the cooperative software development. In III Workshop on Hypermedia and Multimedia Applications, pages 143-154, São Carlos, Brazil, 23-25 May 1997.

Souza, C, R. B., Wainer, J., Santos, D. B. e Dias, K. L. (1998), A model and tool for semi-automatic recording of design rationale in software diagra ms. In: Proceedings of the 6th String Processing and Information Retrieval Symposium & 5th International Workshop on Groupware, Cancun, Mexico, 1998, p. 306-313.

Villela , K. V. C. (2004), Definição e Construção de Ambientes de Desenvolvimento de Software Orientados à Organização, Tese de D. Sc., COPPE/UFRJ, Rio de Janeiro, Brasil.

Xavier, J, R. (2001), Criação e Instanciação de Arquiteturas de Software Específicas de Domínio no Contexto de uma Infra-Estrutura de Reutilização, Dissertação de Mestrado, Universidade Federal do Rio de Janeiro, Brasil.