Thesis (Ph. D.)--University of Hong Kong, 2001. / Includes bibliographical references (leaves 235-249).

In the bakery industry, it is sought to have zero defective products. It is in the packing; where it is evident, as the last area of the production chain, all the defects generated. Therefore, a combined redesign method is proposed, which consists in the use of Economy of Movement, Ergonomics, Poka Yoke and Method Engineering to reduce defective products in SMEs in the bakery industry. The losses of these generate a reduction of 29.50% for crushed bread and 19.67% of bread on the floor, reducing with the use of this method to 16.20% and 8.38% respectively.

A especificação dos requisitos de software pressupõe que se conheçam os requisitos do sistema do que será parte. Os requisitos do sistema, por sua vez, pressupõem o conhecimento do negócio (business) onde o sistema será utilizado. Para que estes conhecimentos sejam obtidos é importante o envolvimento dos stakeholders tanto no nível de sistema quanto no nível de negócio. As literaturas sobre Engenharia de Requisitos, Engenharia de Software e Engenharia de Sistemas concordam que o envolvimento dos stakeholders é fundamental. O tratamento dispensado ao assunto, no entanto, é pequeno, dada a importância do tema. Esta dissertação, utilizando conceitos da Engenharia de Métodos Situacionais e de Design Science, apresenta o ZEP Framework, um artefato, produzido com o software EPF Composer, que permite a criação de métodos para envolver o stakeholder. Estes métodos, para serem criados, devem levar em consideração as peculiaridades da organização, dos recursos disponíveis e do projeto em si. São apresentados, ainda, alguns cenários, na área de Turismo, como exemplos da utilização do framework. / The specification of software requirements implies that the system requirements are known. The system requirement requires knowledge about the business of which the system will be a part. To obtain this knowledge it is important to engage stakeholders not only at the system level, but at the business level as well. The literature on Requirements Engineering, Software Engineering and Systems Engineering consider the involvement of stakeholders as fundamental. Despite this, the treatment of the subject is not proportional to its importance. This dissertation, using concepts from Situational Method Engineering and Design Science, presents the ZEP Framework, an artifact built with the EPF Composer software, that allows the creation of methods to engage stakeholders. These methods consider the specific situation of the organization, the resources available and the characteristics of the initiative itself. Some scenarios, in the Tourism field, are presented as examples of the utilization of the framework.

A especificação dos requisitos de software pressupõe que se conheçam os requisitos do sistema do que será parte. Os requisitos do sistema, por sua vez, pressupõem o conhecimento do negócio (business) onde o sistema será utilizado. Para que estes conhecimentos sejam obtidos é importante o envolvimento dos stakeholders tanto no nível de sistema quanto no nível de negócio. As literaturas sobre Engenharia de Requisitos, Engenharia de Software e Engenharia de Sistemas concordam que o envolvimento dos stakeholders é fundamental. O tratamento dispensado ao assunto, no entanto, é pequeno, dada a importância do tema. Esta dissertação, utilizando conceitos da Engenharia de Métodos Situacionais e de Design Science, apresenta o ZEP Framework, um artefato, produzido com o software EPF Composer, que permite a criação de métodos para envolver o stakeholder. Estes métodos, para serem criados, devem levar em consideração as peculiaridades da organização, dos recursos disponíveis e do projeto em si. São apresentados, ainda, alguns cenários, na área de Turismo, como exemplos da utilização do framework. / The specification of software requirements implies that the system requirements are known. The system requirement requires knowledge about the business of which the system will be a part. To obtain this knowledge it is important to engage stakeholders not only at the system level, but at the business level as well. The literature on Requirements Engineering, Software Engineering and Systems Engineering consider the involvement of stakeholders as fundamental. Despite this, the treatment of the subject is not proportional to its importance. This dissertation, using concepts from Situational Method Engineering and Design Science, presents the ZEP Framework, an artifact built with the EPF Composer software, that allows the creation of methods to engage stakeholders. These methods consider the specific situation of the organization, the resources available and the characteristics of the initiative itself. Some scenarios, in the Tourism field, are presented as examples of the utilization of the framework.

[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]. Universitat Politècnica de València. https://doi.org/10.4995/Thesis/10251/53931

<p>There are a countless number of methods in the field of Information Systems Development (ISD) today, where only a few have received much attention by practitioners. These ISD methods are described and developed using knowledge in the field of Method Engineering (ME). Most methods concern either what a system is to contain or how the system is to be realised, but as of now, there is no best method for all situations. Bridging the gap between the fuzzier "what"-methods and the more formal "how"-methods is difficult, if not impossible. Methods therefore need to be integrated to cover as much of the systems life cycle as possible. An integration of two methods, one from each side of the gap, can be performed in a number of different ways, each way having its own obstacles that need to be overcome.</p><p>The case study we have performed concerns a method integration of the fuzzier Business Process Model (BPM) in the EKD method with the more formal description technique SDL (Specification and Description Language). One meta model per technique was created, which were then used to compare BPM and SDL. The integration process consisted of translating EKD business process diagrams into SDL correspondences, while carefully documenting and analysing encountered problems. The encountered problems mainly arose because of either transaction-independence differences or method focus deviations. The case study resulted in, for example, a number of implications for both EKD and SDL, as well as for ME, and include suggestions for future work.</p>

<p>In the area of information systems design it is important to select an appropriate methodology in order to get an information system that functions as expected. The perspective behind the methodology is seldom stated explicitly. The epistemology that a methodology is based on has impacts on the design of the system. Therefore, the process of selecting an appropriate methodology is important. The aim of this work is to study how the process of metamodelling or metathinking is considered in the area of information systems design.</p><p>Interviews and a study of the literature have been performed in order to investigate the awareness of metamodelling thinking in the area of information systems design.In the literature we found that only a small part dealt with the process of metamodelling. The method engineering (ME) approach was found as a way of thinking that seems to consider metamodelling thinking. We have evaluated ME according to a synthesis of the works by van Gigch, Churchman, and Flood and Carson. The evaluation has shown that ME deals with metamodelling thinking. In order to improve the metamodelling thinking in ME, it is important to explicitly define how ME considers the aspect of participation of motivated actors and the iterative process. The interviews have shown that information systems designers use some kind of metamodelling thinking, but they do not seem to be aware of the process.</p><p>In an information system design process, it is important to shift perspectives from reality to modelling, and to the metamodelling level, in order to apply metamodelling thinking. Further work should be performed with the purpose of making the information systems designers aware of the importance of applying metamodelling thinking.</p>

<p>The increasing complexity of Information Systems (IS) calls for IS development methods to be adapted to the specific situations of the projects at hand. Method engineering is important because it focus on the creation of new methods that can be used in the system development process with the aim of constructing new information systems. The size and complexity of projects for developing information systems are becoming larger and more complicated. Therefore, development methods turn out to be one of the most significant key factors to achieve great success of development projects.</p><p>The discipline of Situational Method Engineering (SME) focuses on the creation of new project specific methods. SME is a reuse strategy to assemble reusable method fragments or method chunks originating from different methods. New methods can be constructed from a method repository by selecting the chunks that are the most appropriate to a given situation. Thus, method chunks are the basic building blocks for constructing methods in a modular way.</p><p>This dissertation have identified, analyzed and categorized a set of interoperability problems for the content of a method chunk repository. These problems have been represented as a set of patterns. The patterns will facilitate the understanding of specific interoperability problems that belong to a specific method chunk. If we are aware of the different interoperability problems that exist it is more likely that we can use a method chunk successfully within the context of SME.</p>

Thesis (M.S.)--Brigham Young University. Dept. of Mechanical Engineering, 2005. / Includes bibliographical references (p. 107-109).

There are a countless number of methods in the field of Information Systems Development (ISD) today, where only a few have received much attention by practitioners. These ISD methods are described and developed using knowledge in the field of Method Engineering (ME). Most methods concern either what a system is to contain or how the system is to be realised, but as of now, there is no best method for all situations. Bridging the gap between the fuzzier "what"-methods and the more formal "how"-methods is difficult, if not impossible. Methods therefore need to be integrated to cover as much of the systems life cycle as possible. An integration of two methods, one from each side of the gap, can be performed in a number of different ways, each way having its own obstacles that need to be overcome. The case study we have performed concerns a method integration of the fuzzier Business Process Model (BPM) in the EKD method with the more formal description technique SDL (Specification and Description Language). One meta model per technique was created, which were then used to compare BPM and SDL. The integration process consisted of translating EKD business process diagrams into SDL correspondences, while carefully documenting and analysing encountered problems. The encountered problems mainly arose because of either transaction-independence differences or method focus deviations. The case study resulted in, for example, a number of implications for both EKD and SDL, as well as for ME, and include suggestions for future work.