MetaCase : from a start-up to an international company

The development of a business case study is the main goal of this dissertation. The appliacation of strategic concepts intends to provide a better understanding of the current situation of the company, as well as to offer recommendations for the future. The dilemma that is further analyzed concerns whether the company should opt for an internationalization process or not, including the markets to explore and the entry modes to adopt. The company is MetaCase, a services firm that provides a consultancy-based solution for financial management, through its own in-house conceived and developed financial ERP. Nowadays, it is only present in the Portuguese market, however it has already been introduced in some projects abroad, all of them through Portuguese based clients. Following the case study, a Literature Review is developed. The topics approached in this section are directly connected to the case itself, such as the key success factors for financial services, financial flows, internationalization and strategic concepts. Moreover, the Teaching Note section presents a personal analysis on the case, aligned with a possible way to approach this case study in a classroom, including the analysis and the recommendations. The relevance of moving on with the internationalization process in order to keep growing is explained. The reasons behind this decision are sustained, and the practical action to be taken is suggested.Esta dissertação tem, como principal objetivo, o desenvolvimento de um case-study. A este caso serão aplicados alguns conceitos estratégicos, de modo a proporcionar uma melhor compreensão da atual situação da empresa, bem como a recomendação de decisões a tomar no futuro. O dilema que a empresa enfrenta, que será analisado ao longo desta dissertação, consiste no processo de internacionalização. Não só é necessário perceber se o mesmo deverá ser o próximo passo a tomar, mas também, e caso a decisão seja neste sentido, em que moldes deverá ser feito, nomeadamente em que mercados e com que modos de entrada. A empresa em questão é a MetaCase, uma empresa de serviços que disponibiliza uma solução de consultoria para a gestão de fluxos financeiros, através de um ERP financeiro internamente concebido e desenvolvido. Presentemente, a empresa está apenas presente no mercado português, no entanto já desenvolveu alguns projetos noutros países, todos eles para clientes sedeados em Portugal. Após o case-study, é desenvolvido um capítulo de revisão de literatura, Literature Review. Os tópicos abordados nesta secção estão diretamente ligados ao caso em estudo, tais como fatores de sucesso para serviços financeiros, fluxos financeiros, internacionalização e conceitos de estratégia. Em seguida, surge a secção da Teaching Note, na qual é apresentada uma análise ao caso, juntamente com uma sugestão de como apresentar este caso numa aula, incluindo as recomendações para o futuro. A resposta ao dilema sobre a relevância do processo de internacionalização para o crescimento da empresa é, também, explicado. As razões que baseiam esta decisão são sustentadas, bem como as ações práticas a implementar são sugeridas

MID: A MetaCASE Tool For A Better Reuse Of Visual Notations

International audienceModeling tools facilitate the development process from modeling to coding. Such tools can be designed using a Model-Driven approach into metamodeling environments called metaCASE tools. It turned out that current metaCASE tools still require, in most cases, manual programming to build full tool support for the modeling language. First of all, we want to specify, using models, diagrams editors with a high graphical expressiveness without any need for manual intervention to perform this task. The second axis is dedicated to this specification reuse in other contexts of use. The redundancy of diagrams editors specification raises the problem of inconsistency during the evolution or the update of this specification. We propose then MID, a tool based on a set of meta-models supporting the easy specification of modeling editors with reusable components

Managing Evolutionary Method Engineering by Method Rationale

This paper explores how to integrate formal meta-models with an informal method rationale to support evolutionary (continuous) method development. While the former provides an exact and computer-executable specification of a method, the latter enables concurrent learning, expansion, and refinement of method use (instances of meta-models) and meta-models (evolution of method specifications). We explain the need for method rationale by observing the criticality of evolving method knowledge in helping software organizations to learn, as well as by the recurrent failure to introduce rigid and stable methods. Like a design rationale, a method rationale establishes a systematic and organized trace of method evolution. Method rationale is located at two levels of type-instance hierarchy depending on its type of use and the scope of the changes traced. A method construction rationale garners a history of method knowledge evolution as part of the method engineering process, which designs and adapts the method to a given organizational context. A method use rationale maintains knowledge of concrete use contexts and their history and justifies further method deployment in alternative contexts, reveals limitations in its past use, and enables sharing of method use experience. The paper suggests how a method rationale helps share knowledge of methods between method users and engineers, explores how method engineers coordinate the evolution of the existing method base through it, and suggests ways to improve learning through method rationale

How to reach a usable DSL? Moving toward a Systematic Evaluation

Domain-Specific Languages (DSLs) are claimed to increase productivity,while reducing the required maintenance and programming expertise.  In thiscontext, DSL usability by domain experts is a key factor for its successfuladoption.Evidence that support those improvement claims is mostly anecdotal.  Oursystematic literature review showed that a usability evaluation was oftenskipped, relaxed, or at least omitted from papers reporting the development of DSLs.  Thefew exceptions mostly take place at the end of the development process where fixing problems identified is too expensive.We argue that a systematic approach based on User Interface experimentalvalidation  techniques should be used to assess the impact of the new DSLs.  The rationale is that assessing important and specially tailored usability attributes for DSLs early in language construction will ultimately foster a higher productivity of the DSL users. This paper, besides discussing thequality criteria, proposes a development and evaluation process that can be usedto achieve usable DSLs in a better way

A Model-Driven Approach for the Design, Implementation, and Execution of Software Development Methods

[EN] Software development projects are diverse in nature. For this reason, software companies are often forced to define their methods in-house. In order to define methods efficiently and effectively, software companies require systematic solutions that are built upon sound methodical foundations. Providing these solutions is the main goal of the Method Engineering discipline. Method Engineering is the discipline to design, construct, and adapt methods, techniques, and tools for the development of information systems. Over the last two decades, a lot of research work has been performed in this area. However, despite its potential benefits, Method Engineering is not widely used in industrial settings. Some of the causes of this reality are the high theoretical complexity of Method Engineering and the lack of adequate software support. In this thesis, we aim to mitigate some of the problems that affect Method Engineering by providing a novel methodological approach that is built upon Model-Driven Engineering (MDE) foundations. The use of MDE enables a rise in abstraction, automation, and reuse that allows us to alleviate the complexity of our Method Engineering approach. Furthermore, by leveraging MDE techniques (such as metamodeling, model transformations, and models at runtime), our approach supports three phases of the Method Engineering lifecycle: design, implementation, and execution. This is unlike traditional Method Engineering approaches, which, in general, only support one of these phases. In order to provide software support for our proposal, we developed a Computer-Aided Method Engineering (CAME) environment that is called MOSKitt4ME. To ensure that MOSKitt4ME offered the necessary functionality, we identified a set of functional requirements prior to developing the tool. Then, after these requirements were identified, we defined the architecture of our CAME environment, and, finally, we implemented the architecture in the context of Eclipse. The thesis work was evaluated by means of a study that involved the participation of end users. In this study, MOSKitt4ME was assessed by means of the Technology Acceptance Model (TAM) and the Think Aloud method. While the TAM allowed us to measure usefulness and ease of use in a subjective manner, the Think Aloud method allowed us to analyze these measures objectively. Overall, the results were favorable. MOSKitt4ME was highly rated in perceived usefulness and ease of use; we also obtained positive results with respect to the users' actual performance and the difficulty experienced.[ES] Los proyectos de desarrollo de software son diversos por naturaleza. Por este motivo, las compañías de software se ven forzadas frecuentemente a definir sus métodos de manera interna. Para poder definir métodos de forma efectiva y eficiente, las compañías necesitan soluciones sistemáticas que estén definidas sobre unos fundamentos metodológicos sólidos. Proporcionar estas soluciones es el principal objetivo de la Ingeniería de Métodos. La Ingeniería de Métodos es la disciplina que aborda el diseño, la construcción y la adaptación de métodos, técnicas y herramientas para el desarrollo de sistemas de información. Durante las dos últimas décadas, se ha llevado a cabo mucho trabajo de investigación en esta área. Sin embargo, pese a sus potenciales beneficios, la Ingeniería de Métodos no se aplica ampliamente en contextos industriales. Algunas de las principales causas de esta situación son la alta complejidad teórica de la Ingeniería de Métodos y la falta de un apropiado soporte software. En esta tesis, pretendemos mitigar algunos de los problemas que afectan a la Ingeniería de Métodos proporcionando una propuesta metodológica innovadora que está basada en la Ingeniería Dirigida por Modelos (MDE). El uso de MDE permite elevar el nivel de abstracción, automatización y reuso, lo que posibilita una reducción de la complejidad de nuestra propuesta. Además, aprovechando técnicas de MDE (como por ejemplo el metamodelado, las transformaciones de modelos y los modelos en tiempo de ejecución), nuestra aproximación da soporte a tres fases del ciclo de vida de la Ingeniería de Métodos: diseño, implementación y ejecución. Esto es a diferencia de las propuestas existentes, las cuales, por lo general, sólo dan soporte a una de estas fases. Con el objetivo de proporcionar soporte software para nuestra propuesta, implementamos una herramienta CAME (Computer-Aided Method Engineering) llamada MOSKitt4ME. Para garantizar que MOSKitt4ME proporcionaba la funcionalidad necesaria, definimos un conjunto de requisitos funcionales como paso previo al desarrollo de la herramienta. Tras la definción de estos requisitos, definimos la arquitectura de la herramienta CAME y, finalmente, implementamos la arquitectura en el contexto de Eclipse. El trabajo desarrollado en esta tesis se evaluó por medio de un estudio donde participaron usuarios finales. En este estudio, MOSKitt4ME se evaluó por medio del Technology Acceptance Model (TAM) y del método Think Aloud. Mientras que el TAM permitió medir utilidad y facilidad de uso de forma subjetiva, el método Think Aloud permitió analizar estas medidas objetivamente. En general, los resultados obtenidos fueron favorables. MOSKitt4ME fue valorado de forma positiva en cuanto a utilidad y facilidad de uso percibida; además, obtuvimos resultados positivos en cuanto al rendimiento objetivo de los usuarios y la dificultad experimentada.[CA] Els projectes de desenvolupament de programari són diversos per naturalesa. Per aquest motiu, les companyies es veuen forçades freqüenment a definir els seus mètodes de manera interna. Per poder definir mètodes de forma efectiva i eficient, les companyies necessiten solucions sistemàtiques que estiguin definides sobre uns fundaments metodològics sòlids. Proporcionar aquestes solucions és el principal objectiu de l'Enginyeria de Mètodes. L'Enginyeria de Mètodes és la disciplina que aborda el diseny, la construcció i l'adaptació de mètodes, tècniques i eines per al desenvolupament de sistemes d'informació. Durant les dues últimes dècades, s'ha dut a terme molt de treball de recerca en aquesta àrea. No obstant, malgrat els seus potencials beneficis, l'Enginyeria de Mètodes no s'aplica àmpliament en contextes industrials. Algunes de les principals causes d'aquesta situació són l'alta complexitat teòrica de l'Enginyeria de Mètodes i la falta d'un apropiat suport de programari. En aquesta tesi, pretenem mitigar alguns dels problemes que afecten a l'Enginyeria de Mètodes proporcionant una proposta metodològica innovadora que està basada en l'Enginyeria Dirigida per Models (MDE). L'ús de MDE ens permet elevar el nivell d'abstracció, automatització i reutilització, possibilitant una reducció de la complexitat de la nostra proposta. A més a més, aprofitant tècniques de MDE (com per exemple el metamodelat, les transformacions de models i els models en temps d'execució), la nostra aproximació suporta tres fases del cicle de vida de l'Enginyeria de Mètodes: diseny, implementació i execució. Açò és a diferència de les propostes existents, les quals, en general, només suporten una d'aquestes fases. Amb l'objectiu de proporcionar suport de programari per a la nostra proposta, implementàrem una eina CAME (Computer-Aided Method Engineering) anomenada MOSKitt4ME. Per garantir que MOSKitt4ME oferia la funcionalitat necessària, definírem un conjunt de requisits funcionals com a pas previ al desenvolupament de l'eina. Després de la definició d'aquests requisits, definírem la arquitectura de l'eina CAME i, finalment, implementàrem l'arquitectura en el contexte d'Eclipse. El treball desenvolupat en aquesta tesi es va avaluar per mitjà d'un estudi on van participar usuaris finals. En aquest estudi, MOSKitt4ME es va avaluar per mitjà del Technology Acceptance Model (TAM) i el mètode Think Aloud. Mentre que el TAM va permetre mesurar utilitat i facilitat d'ús de manera subjectiva, el mètode Think Aloud va permetre analitzar aquestes mesures objectivament. En general, els resultats obtinguts van ser favorables. MOSKitt4ME va ser valorat de forma positiva pel que fa a utilitat i facilitat d'ús percebuda; a més a més, vam obtenir resultats positius pel que fa al rendiment objectiu dels usuaris i a la dificultat experimentada.Cervera Úbeda, M. (2015). A Model-Driven Approach for the Design, Implementation, and Execution of Software Development Methods [Tesis doctoral no publicada]. Universitat Politècnica de València. https://doi.org/10.4995/Thesis/10251/53931TESI

A generic model for representing software development methods.

This thesis has adopted the premise that the use of a method offers a valuable contribution to the software development process. Many methods have not been adequately defined. This thesis is based on the hypothesis that it is possible to represent software development methods using a Generic Method Representation (GMR). This GMR includes the three basic components of the method, which are the product model, the process model and the heuristic model. The elements and interrelationships of these models are investigated. In addition to a graphical representation, a method specification language (MSL) is derived, to enhance the expressive and executable power of GMR. A three-stage knowledge acquisition model, known as IFV (inspection, fabrication and verification), is also introduced to elicit method semantics from the available acquisition media. Moreover, the key benefits of meta modelling, such as method comparison, fragment dissection, method evaluation and selection (or customisation) of a method, are highlighted. An application of GMR, that is the mapping to a practical metaCASE tool model, is also illustrated comprehensively to demonstrate the applicability of the approach

Towards a multidimensional self-assessment for software process improvement: a pilot tool

The SPI Manifesto provides a framework for guiding software development organisations in their improvement efforts. Based on the Values of People, Business and Change, which are supported and informed by one or more of the ten principles, the designer and developer can avoid pitfalls, minimise risks and make their business successful. It has been established, in theory and practice, that improving the process results in improvement of the products and services emanating from that process. Following a number of earlier multidimensional analyses of the SPI Manifesto, carried out by the authors, a series of tabular representations identifying the nature, importance and strength of relationships between the Manifesto’s Values and Principles in terms of eight dimensions encapsulated in the acronym STEEPLED (Sociocultural, Technical, Economic, Environmental, Political, Legal, Ethical and Demographic) were developed. In this paper, we present a conceptualisation of a pilot automated tool (based on the STEEPLED Analysis), which could, potentially, be implemented/realised and used for self-assessment by software developing organisations. Starting with a self-assessment, current issues and requirements could be identified and revealed. The self-assessment using the pilot automated tool would, additionally, reveal areas requiring improvement, and would serve as a guide for the participating organisation to put focus on prioritising candidate process areas that require improvement. Also, the field testing of the pilot tool could enable the design and improvement of the tool itself, which, in turn, will be used in future for expert external/independent process assessment

BORM - Business Object Relation Modeling

BORM is an object-oriented and process-based analysis and design methodology, which has proved to be effective in the development of business systems. The effectiveness gained is largely due to an unified and simple method for presenting necessary aspects of the relevant business model, which can be simulated, verified and validated for subsequent software implementation. The BORM methodology makes extensive use of business process modeling towards the area of software engineering. This paper outlines BORM and presents it on an application example created in Craft.CASE analysis and modeling tool