10 research outputs found
KNOWLEDGE MODELING OF AGILE PROCESSES IN HEALTHCARE SYSTEMS DEVELOPMENT
Requirements on healthcare software products are becoming more and more complicated and software systems of today are characterized by increasing complexity and size. Therefore, software systems can no longer be developed feasibly without the processes supported by appropriate methods. We propose a method for configuration and modification of agile processes behind healthcare products development based on gathered knowledge and formal modeling. Our approach allows to support and optimize the processes with formal methods of modeling and machinelearning based simulations
A Governance Framework for Mitigating Risks and Uncertainty in Collaborative Business Processes
International audienceThe development of collaborative business process relies mostly on software services spanning multiple organizations. Therefore, uncertainty related to the shared assets and risks of Intellectual Property infringement form major concerns and hamper the development of inter-enterprise collaboration. This paper proposes a governance framework to enhance trust and assurance in such collaborative context, coping with the impacts of Cloud infrastructure. First, a collaborative security requirements engineering approach analyzes assets sharing relations in business process, to identify risks and uncertainties and, therefore, elicits partnersâ security requirements and profiles. Then, a âdue usageâ aware policy model supports negotiation between asset providerâs requirements and consumerâs profiles. The enforcement mechanism adapts to dynamic business processes and Cloud infrastructures to provide end-to-end protection on shared assets
There Is Still No Fit for All IS Development Method: Business Development Context and IS Development Characteristics Need to Match
Information systems development has returned to strategic management due to the increase of software-enabled businesses. We investigated two failed IS development projects using the exploratory case study method. One of the projects was executed with the plan-driven approach methods and the other with the change-driven (agile) approach methods. Data analysis showed that both projects followed the principles of the selected methods. That, however, was not enough. The plan-driven project achieved project objectives but did not deliver business value and the IS was never taken into use. The change-driven project delivered desired business value but failed to release a robust IS. Our main contribution to research is our proposition to match the characteristics of IS development methods with the characteristics of business development contexts. We also disclose some novel reasons for IS project failures
Selecting the right method for the right project
The development of information systems is constantly changing. As a background of the change, there is almost a traditional problem about the high failure rates of information systems development (ISD) projects, but it is no longer the only change-driving force. The role of information systems and their strategic significance has increased considerably due digitalization. This has happened also in the areas of business, which have not been traditionally thought as IT-oriented. Furthermore, the new agile development methods have forced ISD clients to take more responsibility for ISD than before. In practice, this means that completely outsourcing ISD is not as sensible nor as simple as before. ISD clients who acquire information systems must be aware of the different ISD methods and be able to compare and choose the most suitable for the business situation and the objectives in question.
ISD method selection is rarely studied, and the majority of publications concentrate on different selection criteria relating to the ISD method choice without a clear selection model. Only a few ISD method selection models were found in the literature. Furthermore, the earlier ISD method selection models are restricted by two factors: firstly, the recommendations behind the prior ISD selection models do not correspond to todayâs thoughts about the ISD methods; secondly, prior ISD selection models concentrate only on the properties of the ISD pro-jects, and attention is not really given to the business environment or the business to be developed.
In a situation like this, it was considered necessary to develop and study an ISD selection framework which takes the business development and business environment into account as well. Furthermore, it was seen as necessary to study both the customer and supplier practices related to the ISD method choice. The objective was to understand the present situation and estimate how the developed ISD selection framework could be utilized in the future.
The study was carried out in several stages. Firstly, two unsuccessful ISD projects were studied in the case study, and it was found that the ISD method used in the projects did not correspond to the properties of the business environment in either case. After that, a contingency theoryâmotivated ISD selection framework was developed, and a systematic literature review was conducted to study earlier ISD method selection criteria and compare them with the developed ISD method selection framework. In the next stage, expert interviews were done. Altogether, 31 ISD experts working on the borderline between the IS sup-plier and client were interviewed and asked their opinions on existing ISD method selection practices by both the client and the supplier. Furthermore, the experts were asked for their opinions on the recommendations of earlier ISD method selection models and on the developed ISD method selection framework.
As a result of the study, it can be stated that the developed ISD method framework covers both the previous ISD method selection criteria, which mainly concentrates on ISD project factors, and the business environment factors. Whereas the majority of the interviewed experts considered the developed ISD method selection framework useful, the recommendations of earlier ISD method selection models were regarded as outdated. Furthermore, it was noticed that in IS client organizations, there was almost no discussion about the ISD methods, and in the supplier organizations, the discussion was very rare. Any systematic projectspecific ISD method selection practice had not been perceived in either organizations. Supplier organizations can justify their reasons for favouring a certain ISD method with the bounded rationality, whereas the operation of customer companies doing (or not doing) the ISD method selection seems to be filling the features of functional stupidity. In the future, it is important to study how to plant the ISD method selection as part of the starting stage of the ISD project. In addition, the developed ISD method selection framework should be tested in the practice.TietojÀrjestelmien kehittÀminen on jatkuvassa murroksessa. Muutoksen taustalla on jo perinteiseksi muodostunut ongelma tietojÀrjestelmÀprojektien epÀonnistumisesta, mutta se ei ole enÀÀ ainoa syy. Digitalisaation myötÀ tietojÀrjestelmien rooli ja strateginen merkitys on kasvanut huomattavasti myös sellaisilla liiketoiminta-alueilla, joita ei ole ajateltu IT-orientoituneina. LisÀksi uudet ketterÀt tietojÀrjestelmien kehittÀmismenetelmÀt osallistavat tietojÀrjestelmÀprojektien asiakkaat, jotka joutuvat entistÀ vastuullisempaan asemaan. KÀytÀnnössÀ tÀmÀ kaikki merkitsee sitÀ, ettÀ tietojÀrjestelmien kehittÀmisen tÀydellinen ulkoistaminen ei enÀÀ ole yhtÀ mielekÀstÀ, eikÀ myös yhtÀ yksinkertaista kuin ennen. TÀssÀ tilanteessa myös tietojÀrjestelmiÀ hankkivan asiakkaan pitÀÀ tietÀÀ erilaisista kehittÀmismenetelmistÀ ja kyetÀ vertailemaan ja valitsemaan kyseiseen liiketoimintatilanteeseen ja tavoitteisiin parhaiten sopiva kehittÀmismenetelmÀ.
TietojÀrjestelmien kehittÀmismenetelmien valintaa on tutkittu vÀhÀn ja suurin osa löydetyistÀ julkaisuista keskittyy listaamaan erilaisia menetelmÀvalintaan liittyviÀ kriteerejÀ. Varsinaisia tietojÀrjestelmien kehitysmenetelmien valintamalleja on esitetty vain muutamia. Aiempien valintamallien kÀyttökelpoisuutta rajoittaa kaksi tekijÀÀ: ensinnÀkin mallien taustalla olevat olettamukset eivÀt vÀlttÀmÀttÀ tÀsmÀÀ tÀmÀn pÀivÀn ajatuksiin kehittÀmismenetelmistÀ, ja toisekseen valintamallit keskittyvÀt tietojÀrjestelmien kehittÀmisprojektien ominaisuuksiin, kehitettÀvÀÀ liiketoimintaa tai liiketoimintaympÀristöÀ ei aikaisemmissa valintamalleissa juurikaan huomioida.
Tilanteen ollessa tÀmÀ kehitimme ja tutkimme tietojÀrjestelmÀn kehittÀmismenetelmien valintamallia, joka ottaa huomioon myös samaan aikaan tapahtuvan liiketoiminnan kehittÀmisen ja liiketoimintaympÀristön. LisÀksi tutkimme tietojÀrjestelmÀn kehittÀmismenetelmien valintaan liittyviÀ kÀytÀntöjÀ sekÀ asiakkaan ettÀ toimittajan nÀkökulmasta. Tavoitteena oli ymmÀrtÀÀ menetelmÀvalinnan nykytilannetta ja arvioida miten valintamallia voisi jatkossa hyödyntÀÀ.
Tutkimus toteutettiin useammassa vaiheessa. EnsimmÀiseksi tapaustutkimuksin tutkittiin kahta epÀonnistunutta tietojÀrjestelmÀkehitysprojektia, ja havaittiin ettÀ kummassakaan tapauksessa valittu tietojÀrjestelmÀn kehittÀmismalli ei vastannut liiketoimintaympÀristön tarpeita. Sen jÀlkeen kehitimme kontingenssiteoreettisen tietojÀrjestelmÀn kehitysmenetelmÀn valintamallin, jota verrattiin systemaattisella kirjallisuuskatsauksella löydettyihin aikeisempiin valintasuosituksiin. Vertailun jÀlkeen haastateltiin 31 asiantuntijaa. Haastatteluilla selvitettiin nykyisiÀ tietojÀrjestelmÀn kehitysmenetelmien valintaan liittyviÀ kÀytÀntöjÀ, niin tietojÀrjestelmÀasiakkaan kuin toimittajan nÀkökulmasta. LisÀksi asiantuntijoilta kysyttiin heidÀn mielipidettÀÀn aiempien valintamallien taustalla olevista vÀittÀmistÀ sekÀ nyt kehitetystÀ valintamallista.
Tulos on, ettÀ ehdottamamme kontingessimalli kattaa sekÀ aiemmat, projektinominaisuuksiin keskittyvÀt valintakriteerit, ettÀ myös liiketoimintaympÀristön epÀvarmuuteen liittyvÀt tekijÀt. Suurin osa haastatelluista asiantuntijoista (23 vastaajaa 31 haastatellusta) piti ehdotettua valintamallia kÀyttökelpoisena. Aiempien valintamallien taustalla olevat vÀittÀmÀt koettiin ajastaan jÀlkeen jÀÀneiksi. LisÀksi havaittiin, ettÀ asiakasyrityksissÀ keskustelua tietojÀrjestelmÀn kehittÀmismenetelmistÀ ei kÀytÀnnössÀ ollut juuri lainkaan, eikÀ myöskÀÀn suurimmassa osassa toimittajayrityksiÀ. MitÀÀn sÀÀnnöllistÀ projektikohtaista valintakÀytÀntöÀ ei kummissakaan yrityksissÀ oltu havaittu. Haastateltujen asiantuntijoiden mukaan kehittÀmisprojekteissa kuitenkin pÀÀsÀÀntöisesti kÀytetÀÀn jotain tietojÀrjestelmÀn kehittÀmismenetelmÀÀ, ja syyt menetelmÀn kÀyttöön vaihtelevat. Toimittajayritysten syyt tietyn menetelmÀn suosimiseen ovat pÀÀosin perusteltavissa rajoitetulla rationaalisuudella (bounded rationality), kun taas asiakasyritysten toiminta menetelmÀn valinnassa nÀyttÀÀ tÀyttÀvÀn toiminnallisen typeryyden (functional stupidity) tunnuspiirteet. Jotta kehitetystÀ mallista tulee asiakasyrityksille hyödyllinen kÀytÀnnön työkalu, on seuraavaksi syytÀ tutkia miten tietojÀrjestelmÀn kehittÀmismenetelmÀn valinta saadaan osaksi projektin kÀynnistÀmisvaiheen tehtÀviÀ. TÀrkeÀÀ on myös testata nyt esitetyn kontingenssimallin toimivuutta kÀytÀnnön tilanteissa
Recommended from our members
Novel processes for smart grid information exchange and knowledge representation using the IEC common information model
This thesis was submitted for the degree of Doctor of Philosophy and awarded by Brunel University.The IEC Common Information Model (CIM) is of central importance in enabling smart grid interoperability. Its continual development aims to meet the needs of the smart grid for semantic understanding and knowledge
representation for a widening domain of resources and processes. With smart grid evolution the importance of information and data management has become an increasingly pressing issue not only because far more data is being generated using modern sensing, control and measuring devices but
also because information is now becoming recognised as the âintegral componentâ that facilitates the optimal flexibility required of the smart grid. This thesis looks at the impacts of CIM implementation upon the landscape of smart grid issues and presents research from within National Grid
contributing to three key areas in support of further CIM deployment. Taking the issue of Enterprise Information Management first, an information management framework is presented for CIM deployment at National Grid. Following this the development and demonstration of a novel secure cloud
computing platform to handle such information is described. Power system application (PSA) models of the grid are partial knowledge representations of a shared reality. To develop the completeness of our understanding of this reality it is necessary to combine these representations.
The second research contribution reports on a novel methodology for a CIM-based
model repository to align PSA representations and provide a
knowledge resource for building utility business intelligence of the grid.
The third contribution addresses the need for greater integration of information relating to energy storage, an essential aspect of smart energy management. It presents the strategic rationale for integrated energy modeling and a novel extension to the existing CIM standards for modeling grid-scale energy storage. Significantly, this work has already contributed to a larger body of work on modeling Distributed Energy Resources currently under development at the Electric Power Research Institute (EPRI) in the
USA.Dr. Martin Bradley on behalf of National Grid Plc. and the Engineering and Physical
Sciences Research Council (EPSRC
A method to build information systems engineering process metamodels
Several process metamodels exist. Each of them presents a different viewpoint of the same information systems engineering process. However, there are no existing correspondences between them. We propose a method to build unified, fitted and multi-viewpoint process metamodels for information systems engineering. Our method is based on a process domain metamodel that contains the main concepts of information systems engineering process field. This process domain metamodel helps selecting the needed metamodel concepts for a particular situational context. Our method is also based on patterns to refine the process metamodel. The process metamodel can then be instantiated according to the organisation's needs. The resulting method is represented as a pattern system. © 2009 Elsevier Inc. All rights reserved
24th International Conference on Information Modelling and Knowledge Bases
In the last three decades information modelling and knowledge bases have become essentially important subjects not only in academic communities related to information systems and computer science but also in the business area where information technology is applied. The series of European â Japanese Conference on Information Modelling and Knowledge Bases (EJC) originally started as a co-operation initiative between Japan and Finland in 1982. The practical operations were then organised by professor Ohsuga in Japan and professors Hannu Kangassalo and Hannu Jaakkola in Finland (Nordic countries). Geographical scope has expanded to cover Europe and also other countries. Workshop characteristic - discussion, enough time for presentations and limited number of participants (50) / papers (30) - is typical for the conference. Suggested topics include, but are not limited to: 1. Conceptual modelling: Modelling and specification languages; Domain-specific conceptual modelling; Concepts, concept theories and ontologies; Conceptual modelling of large and heterogeneous systems; Conceptual modelling of spatial, temporal and biological data; Methods for developing, validating and communicating conceptual models. 2. Knowledge and information modelling and discovery: Knowledge discovery, knowledge representation and knowledge management; Advanced data mining and analysis methods; Conceptions of knowledge and information; Modelling information requirements; Intelligent information systems; Information recognition and information modelling. 3. Linguistic modelling: Models of HCI; Information delivery to users; Intelligent informal querying; Linguistic foundation of information and knowledge; Fuzzy linguistic models; Philosophical and linguistic foundations of conceptual models. 4. Cross-cultural communication and social computing: Cross-cultural support systems; Integration, evolution and migration of systems; Collaborative societies; Multicultural web-based software systems; Intercultural collaboration and support systems; Social computing, behavioral modeling and prediction. 5. Environmental modelling and engineering: Environmental information systems (architecture); Spatial, temporal and observational information systems; Large-scale environmental systems; Collaborative knowledge base systems; Agent concepts and conceptualisation; Hazard prediction, prevention and steering systems. 6. Multimedia data modelling and systems: Modelling multimedia information and knowledge; Contentbased multimedia data management; Content-based multimedia retrieval; Privacy and context enhancing technologies; Semantics and pragmatics of multimedia data; Metadata for multimedia information systems. Overall we received 56 submissions. After careful evaluation, 16 papers have been selected as long paper, 17 papers as short papers, 5 papers as position papers, and 3 papers for presentation of perspective challenges. We thank all colleagues for their support of this issue of the EJC conference, especially the program committee, the organising committee, and the programme coordination team. The long and the short papers presented in the conference are revised after the conference and published in the Series of âFrontiers in Artificial Intelligenceâ by IOS Press (Amsterdam). The books âInformation Modelling and Knowledge Basesâ are edited by the Editing Committee of the conference. We believe that the conference will be productive and fruitful in the advance of research and application of information modelling and knowledge bases. Bernhard Thalheim Hannu Jaakkola Yasushi Kiyok
Contribution Ă lâamĂ©lioration du processus de conception des produits innovants : DĂ©veloppement dâoutils dâaide au choix des processus
The optimization of the design process is a research evolving highlighted in numerous references and business practices with the aim improving and developing new products. Our approach is a continuation of those activities that takes as its starting point the diversity of existing design processes and the difficulty of achieving a selection where adaptation. Hence our problem is summarized around a central question which we formulate as follows: how to optimize the choice of the design process subject to a constrained environment? The answer to this question is through the proposition of a tool Help in choosing which converges to the installation of a design process. This tool is three-dimensional, where the first dimension relates to the preparation of the upstream design phase, the second dimension selects a design process on a map classification and the objective of the third dimension is the identification of trades tools and methods for product development. The experimental part of our work has led us to validate the developed tool and propose how to use by designers. Optimization is achieved in our work by the proposal of a three-dimensional tool side and the other by the use of optimization algorithms for modeling tool. New avenues of research for improvement are identified and proposed for future work.L'optimisation des processus de conception est une activitĂ© de recherche en pleine Ă©volution, soulignĂ©e dans de nombreuses rĂ©fĂ©rences et pratiques des entreprises dans l'objectif l'amĂ©lioration et le dĂ©veloppement de produits nouveaux. Notre dĂ©marche s'inscrit dans la continuitĂ© de ces activitĂ©s qui prend comme point de dĂ©part la diversitĂ© des processus de conception existants et la difficultĂ© de rĂ©aliser un choix oĂč une adaptation. D'ou notre problĂ©matique est rĂ©sumĂ©e autour d'une question centrale que nous formulons de la maniĂšre suivante : comment optimiser le choix d'un processus de conception soumis Ă un environnement contraint ? La rĂ©ponse Ă cette question est Ă travers la proposition d'un outil d'aide au choix qui converge vers l'installation d'un processus de conception. Cet outil est tridimensionnel, oĂč la premiĂšre dimension vise la prĂ©paration de la phase amont de conception, la deuxiĂšme dimension sĂ©lectionne un processus de conception sur une carte de classement et l'objectif de la troisiĂšme dimension est l'identification des mĂ©tiers, outils et mĂ©thodes pour le dĂ©veloppement des produits. La partie expĂ©rimentale de notre travail nous a conduit Ă valider l'outil dĂ©velopper et proposer comment l'exploiter par des concepteurs. L'optimisation est rĂ©alisĂ©e dans notre travail par la proposition de l'outil tridimensionnel d'un cotĂ© et de l'autre par l'exploitation des algorithmes d'optimisation pour la modĂ©lisation de l'outil. Des nouvelles pistes de recherche pour l'amĂ©lioration sont identifiĂ©es et proposĂ©es pour des futurs travaux