The Need to Support of Data Flow Graph Visualization of Forensic Lucid Programs, Forensic Evidence, and their Evaluation by GIPSY

Lucid programs are data-flow programs and can be visually represented as data flow graphs (DFGs) and composed visually. Forensic Lucid, a Lucid dialect, is a language to specify and reason about cyberforensic cases. It includes the encoding of the evidence (representing the context of evaluation) and the crime scene modeling in order to validate claims against the model and perform event reconstruction, potentially within large swaths of digital evidence. To aid investigators to model the scene and evaluate it, instead of typing a Forensic Lucid program, we propose to expand the design and implementation of the Lucid DFG programming onto Forensic Lucid case modeling and specification to enhance the usability of the language and the system and its behavior. We briefly discuss the related work on visual programming an DFG modeling in an attempt to define and select one approach or a composition of approaches for Forensic Lucid based on various criteria such as previous implementation, wide use, formal backing in terms of semantics and translation. In the end, we solicit the readers' constructive, opinions, feedback, comments, and recommendations within the context of this short discussion.Comment: 11 pages, 7 figures, index; extended abstract presented at VizSec'10 at http://www.vizsec2010.org/posters ; short paper accepted at PST'1

Leveraging service-oriented business applications to a rigorous rule-centric dynamic behavioural architecture.

Today’s market competitiveness and globalisation are putting pressure on organisations to join their efforts, to focus more on cooperation and interaction and to add value to their businesses. That is, most information systems supporting these cross-organisations are characterised as service-oriented business applications, where all the emphasis is put on inter-service interactions rather than intra-service computations. Unfortunately for the development of such inter-organisational service-oriented business systems, current service technology proposes only ad-hoc, manual and static standard web-service languages such as WSDL, BPEL and WS-CDL [3, 7]. The main objective of the work reported in this thesis is thus to leverage the development of service-oriented business applications towards more reliability and dynamic adaptability, placing emphasis on the use of business rules to govern activities, while composing services. The best available software-engineering techniques for adaptability, mainly aspect-oriented mechanisms, are also to be integrated with advanced formal techniques. More specifically, the proposed approach consists of the following incremental steps. First, it models any business activity behaviour governing any service-oriented business process as Event-Condition-Action (ECA) rules. Then such informal rules are made more interaction-centric, using adapted architectural connectors. Third, still at the conceptual-level, with the aim of adapting such ECA-driven connectors, this approach borrows aspect-oriented ideas and mechanisms, and proposes to intercept events, select the properties required for interacting entities, explicitly and separately execute such ECA-driven behavioural interactions and finally dynamically weave the results into the entities involved. To ensure compliance and to preserve the implementation of this architectural conceptualisation, the work adopts the Maude language as an executable operational formalisation. For that purpose, Maude is first endowed with the notions of components and interfaces. Further, the concept of ECA-driven behavioural interactions are specified and implemented as aspects. Finally, capitalising on Maude reflection, the thesis demonstrates how to weave such interaction executions into associated services

Towards an understanding of business design within enterprise architecture management: a cautionary tale

Includes bibliographical references.Business Design represents a set of concepts that are described in the literature as providing a sound foundation for sustainable competitive advantage into the future. The particular values underpinning Business design are based on the enablement of a design thinking approach to solving the imponderable problems that organisations regularly encounter. In particular, the application of a design thinking approach to Business Design requires that resultant system designs are economically viable and technologically feasible. Enterprise Architecture Management plays a vital role in supporting these latter two requirements. Yet the definition of Enterprise Architecture Management as the 'normative restriction of design freedom' (Deitz, 2011) implies constraints that could impose limits on such business design. Consequently, the qualitative inductive research described in this document was undertaken to explore the perceived paradoxical relationship between Business Design and Enterprise Architecture Management. This dissertation recounts the process and results of this research initiative based on data recorded during interviews with a number of management level staff at a leading South African Insurance organisation. The participants were intimately involved in a programme to, amongst other objectives, establish a platform to support enterprise-wide Business Design within Enterprise Architecture Management, a programme that was experiencing a number of challenges and that was still underway at the time of completion of this research. Findings arising from this research were that the varying perceptions and levels of commitment of business and IT stakeholders associated with the programme and its requirements, contributed significantly to these challenges. In addition to providing a rich description of the case organisation's journey towards the establishment of a Business Design platform, a sensitising framework – 'The 6 Cs Framework in Support of the Successful Enablement of Business Design within Enterprise Architecture Management' – is proposed as a useful tool to assist organisations that might be considering a similar programme in the future

A Reference Architecture for Digital Ecosystems

Digital ecosystems are a new type of application based on a “universal digital environment” populated by digital entities that form communities that evolve and interact with information exchange and who trade digital objects that are produced through the system. Entities that participate and form the ecosystem can be applications running not only on simple devices: wearable, sensors, actuators, but also on complex services executed on smartphones, tablets, personal computers, company servers, etc. A reference architecture for digital ecosystems is a step toward standardization, as it defines a set of guidelines in designing and implementing a digital ecosystem. Often such architectures are very abstract, difficult to understand and implement. In this chapter, we introduce a vendor- and technology-neutral reference architecture for digital ecosystems and apply this architecture to an actual use case

Knowledge-based system for collaborative process specification

Le marché industriel est aujourd’hui de plus en plus dynamique et compétitif. Cette tendance évolutive de l’écosystème amène les entreprises à prendre part à un nombre croissant de réseaux industriels, dans l’optique de maintenir leur activité et d’accroître leur compétitivité. La qualité d’interaction et de collaboration de partenaires de ces réseaux dépend grandement de la capacité de leurs systèmes d’information (SIs) respectifs à gérer et à partager les informations. Le projet MISE (Mediation Information System Engineering) relève pleinement de cette problématique en proposant une approche de conception d’une solution (conceptuelle et technologique) pour le support de l’interopérabilité d’entreprises au travers de leurs SIs. Ce projet s’appuie sur la notion de MDE (Model-Driven Engineering) et s’articule autour de trois niveaux : métier, logique et technologique. Les travaux de thèse dont il est ici question relèvent du niveau métier en présentant une démarche d’obtention d’un modèle indépendant de toute implémentation (CIM pour Computer Independent Model). Il s’agit en particulier de s’appuyer sur un système basé sur la gestion de connaissance pour concevoir des processus collaboratifs en BPMN (Business Process Modelling Notation). En se positionnant à un niveau d’abstraction au dessus de celui du CIM, on peut capitaliser, manipuler et raisonner une connaissance permettant d’une part de caractériser des collaborations et d’autre part de mettre en place des mécanismes de déduction pour descendre au niveau de CIM. Ces principes sont en outre illustrés par le biais d’un prototype développé pour valider l’approche. ABSTRACT : Enterprises are now operating in an environment where market is more open, globalized, and competitive. Changes in market conditions are obliging enterprises to become involved in various kinds of industrial networks in order to maintain their business efficiency. The integration of business partners depends deeply on the ability to capture and share information seamlessly amongst the information systems (ISs) of different enterprises. The MISE (Mediation Information System Engineering) project was evolved in order to tackle this problem by providing an information technology solution for supporting the enterprise interoperability through ISs. It is developed on the basis of the MDE (Model Driven Engineering). This dissertation addresses the business level of the interoperability, and the CIM (Computer Independent Model) of the MDE. Its main objective is to develop a knowledge-based system for supporting the design of collaborative processes that conform to the BPMN (Business Process Modeling Notation). We propose to work at the upper level of the CIM to capture knowledge that allows us to characterize collaboration by basing on the perspectives and experiences of business partners. We use this knowledge together with the existing knowledge (instances about business processes) from the MIT Process Handbook for moving down to the CIM level. The prototype of our knowledge-based system is also developed in order to validate and evaluate the approach