Difficulties in the transition from OO analysis to design

Kaindl, Hermann

doi:10.1109/52.795107

Cited by 57 publications

(24 citation statements)

References 6 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…This challenge has been recognised in the past [21,11,3] but does not seem to have been addressed adequately. The software ecosystem research community is not unique in experiencing such difficulties in transitioning from analysis to design: similar difficulties have been reported in other areas of software engineering [35,38].…”

Section: Quality and Designmentioning

confidence: 98%

Challenges in Software Ecosystems Research

Serebrenik

Mens

2015

Proceedings of the 2015 European Conference on Software Architecture Workshops

View full text Add to dashboard Cite

The paper is a meta-analysis of the research field of software ecosystems, by method of surveying 26 authors in the field. It presents a relevant list of literature and six themes in which challenges for software ecosystems can be grouped: Architecture and Design, Governance, Dynamics and Evolution, Data Analytics, Domain-Specific Ecosystems Solutions, and Ecosystems Analysis. As such, it provides a roadmap for future research in the field. Categories and Subject Descriptors

show abstract

Section: Quality and Designmentioning

confidence: 98%

Challenges in Software Ecosystems Research

Serebrenik

Mens

2015

Proceedings of the 2015 European Conference on Software Architecture Workshops

View full text Add to dashboard Cite

show abstract

“…Existe la necesidad de estructurar y categorizar la masa de información proveniente del proceso de educción de requisitos a los efectos de facilitar la comprensión del problema manifestado por el usuario [5] [6] [7]. El problema abierto que se aborda en este artículo consiste en la existencia de una "brecha conceptual" en la transición del proceso de conceptualización de requisitos entre el Discurso del Usuario y los Requisitos.…”

Section: B Problema Abiertounclassified

Propuesta de Conceptualización de Requisitos para Proyectos Software Basados en Formalismos de Ingeniería de Conocimiento

Ferrer¹

2016

ReLAIS

View full text Add to dashboard Cite

Resumen-El proceso de conceptualización de requisitos para Proyectos Software basados en formalismos de Ingeniería de Conocimiento presenta una serie de inconvenientes al identificarlos. En este artículo se presenta una propuesta de conceptualización de requisitos para Proyectos Software basados en formalismos de Ingeniería de Conocimiento que se estructura en dos fases: (a) Análisis Orientado al Problema: cuya finalidad es comprender el problema planteado por el usuario que concluye en la conceptualización del modelo de conocimiento para Proyectos Software, y (b) Análisis Orientado al Producto: cuya finalidad consiste en la obtención de los modelados que determinarán la manera de construir el sistema software en cuestión, dependiendo de lo analizado en la primera fase. Se proponen ocho tareas que articulan cada una de las técnicas que componen las fases del proceso propuesto.

show abstract

“…This is consistent with the ideas of Smith [Smi96], who sees the object as derived from more primitive abstractions. The difficulties in making the transition from OOA to OOD identified in [Kai99] can also be attributed to this source.…”

Section: Background To Empirical Modellingmentioning

confidence: 99%

“…For instance, business goals may be viewed as very sophisticated observables, and autopoietic systems as highly sophisticated ways of construing the interaction of agents. The problems of reconciling objectoriented analysis and object-oriented design [Kai99] are associated with issues of comparable subtlety. Another long-term goal for EM is the automatic or semi-automatic generation of systems from ISMs [ABCY98].…”

Section: Prospects For Em In Bprmentioning

confidence: 99%

Business and IT Perspectives on AMORE: a Methodology using Object-Orientation in Re-engineering Enterprises

Fernandes

Raja

Keast

et al. 2002

Systems Engineering for Business Process Change: New Directions

View full text Add to dashboard Cite

This paper is both an outline and a critique of AMORE, A Methodology Based on Object-Orientation for Re-engineering Enterprises that is being developed at the University of Warwick under the auspices of EPSRC grant GR/M02675. The methodology involves two principal phases, which deal with reengineering from business and software viewpoints respectively. AMORE proposes models and guidelines that are intended to achieve a closer integration between these two viewpoints than is possible with alternative approaches. To this end, it exploits business domain modelling that takes account of the business factors (such as goals, location and organizational structure) that influence the design of processes. The prospects for AMORE are reviewed first with reference to current thinking on BPR and software development for business information systems by IT specialists such as Jacobson and Warboys, and subsequently with reference to business applications of a new computer-based modelling paradigm that are being developed in parallel with AMORE by Beynon and Russ in the

show abstract

Difficulties in the transition from OO analysis to design

Cited by 57 publications

References 6 publications

Challenges in Software Ecosystems Research

Challenges in Software Ecosystems Research

Propuesta de Conceptualización de Requisitos para Proyectos Software Basados en Formalismos de Ingeniería de Conocimiento

Business and IT Perspectives on AMORE: a Methodology using Object-Orientation in Re-engineering Enterprises

Contact Info

Product

Resources

About