Executable system architecting using systems modeling language in conjunction with Colored Petri Nets - a demonstration using the GEOSS network centric system

Models and simulation furnish abstractions to manage complexities allowing engineers to visualize the proposed system and to analyze and validate system behavior before constructing it. Unified Modeling Language (UML) and its systems engineering extension, Systems Modeling Language (SysML), provide a rich set of diagrams for systems specification. However, the lack of executable semantics of such notations limits the capability of analyzing and verifying defined specifications. This research has developed an executable system architecting framework based on SysML-CPN transformation, which introduces dynamic model analysis into SysML modeling by mapping SysML notations to Colored Petri Net (CPN), a graphical language for system design, specification, simulation, and verification. A graphic user interface was also integrated into the CPN model to enhance the model-based simulation. A set of methodologies has been developed to achieve this framework. The aim is to investigate system wide properties of the proposed system, which in turn provides a basis for system reconfiguration --Abstract, page iii

Designing for the Ubiquitous Computing era: towards the reinvention of everyday objects and the creation of new user experiences

Researchers of the Ubiquitous Computing community (Ubicomp) have been pursuing the vision of a world where technologies and services permeates every object of our lives for years. With components getting smaller, cheaper and more powerful, it has become possible to manufacture connected objects capable of interacting with resources of the World Wide Web. This opens up the possibility for researchers and practitioners to consider information as a design material and objects as platforms for services. By allowing users to personalize, complement or repurpose the functions of their objects, such services have a great impact on the way artifacts are designed. Designing for the Ubiquitous Era requires modifying our practice and reinforcing collaboration between disciplines at every steps of the creation process. In this article, we discuss the need to reinvent objects and to investigate the tools supporting the creation of rich services’ experiences

Tradespace and Affordability – Phase 1

One of the key elements of the SERC’s research strategy is transforming the practice of systems engineering – “SE Transformation.” The Grand Challenge goal for SE Transformation is to transform the DoD community’s current systems engineering and management methods, processes, and tools (MPTs) and practices away from sequential, single stovepipe system, hardware-first, outside-in, document-driven, point-solution, acquisition-oriented approaches; and toward concurrent, portfolio and enterprise-oriented, hardware-software-human engineered, balanced outside-in and inside-out, model-driven, set-based, full life cycle approaches.This material is based upon work supported, in whole or in part, by the U.S. Department of Defense through the Office of the Assistant Secretary of Defense for Research and Engineering (ASD(R&E)) under Contract H98230-08- D-0171 (Task Order 0031, RT 046).This material is based upon work supported, in whole or in part, by the U.S. Department of Defense through the Office of the Assistant Secretary of Defense for Research and Engineering (ASD(R&E)) under Contract H98230-08- D-0171 (Task Order 0031, RT 046)

Tradespace and Affordability – Phase 2

MOTIVATION AND CONTEXT: One of the key elements of the SERC’s research strategy is transforming the practice of systems engineering – “SE Transformation.” The Grand Challenge goal for SE Transformation is to transform the DoD community’s current systems engineering and management methods, processes, and tools (MPTs) and practices away from sequential, single stovepipe system, hardware-first, outside-in, document-driven, point-solution, acquisition-oriented approaches; and toward concurrent, portfolio and enterprise-oriented, hardware-software-human engineered, balanced outside-in and inside-out, model-driven, set-based, full life cycle approaches.This material is based upon work supported, in whole or in part, by the U.S. Department of Defense through the Office of the Assistant Secretary of Defense for Research and Engineering (ASD(R&E)) under Contract H98230-08- D-0171 (Task Order 0031, RT 046).This material is based upon work supported, in whole or in part, by the U.S. Department of Defense through the Office of the Assistant Secretary of Defense for Research and Engineering (ASD(R&E)) under Contract H98230-08- D-0171 (Task Order 0031, RT 046)

Experimental Object-Oriented Modelling

This thesis examines object-oriented modelling in experimental system development. Object-oriented modelling aims at representing concepts and phenomena of a problem domain in terms of classes and objects. Experimental system development seeks active experimentation in a system development project through, e.g., technical prototyping and active user involvement. We introduce and examine "experimental object-oriented modelling" as the intersection of these practices

Validation of a Content Analysis System Using an Iterative Prototyping Approach to Action Research

In the face of a more rapid pace of scientific development, academic societies and competitive organizations alike are seeking new methods for content analysis. This paper describes a theoretically driven action research study that delivers a technology-mediated solution for specifying, organizing, representing and using elements of meaning in a body of knowledge. The theoretical basis, \u27ontological specification\u27 is of particular interest to IS professionals, particularly those involved in analysis and design, because it guides the efficient transformation of tacit knowledge into an explicit form. The technology-mediated solution influenced by ontological specification was validated through an iterative prototyping form of action research. Users reported that the system was useful in their work, easy to use, and compatible with collaborative work when using it for content analysis in academic research

Architectural decision-making as a financial investment:An industrial case study

Context Making architectural decisions is a crucial task but also very difficult, considering the scope of the decisions and their impact on quality attributes. To make matters worse, architectural decisions need to combine both technical and business factors, which are very dissimilar by nature. Objectives We provide a cost-benefit approach and supporting tooling that treats architectural decisions as financial investments by: (a) combining both technical and business factors; and (b) transforming the involved factors into currency, allowing their uniform aggregation. Apart from illustrating the method, we validate both the proposed approach and the tool, in terms of fitness for purpose, usability, and potential limitations. Method To validate the approach, we have performed a case study in a software development company, in the domain of low-energy embedded systems. We employed triangulation in the data collection phase of the case study, by performing interviews, focus groups, an observational session, and questionnaires. Results The results of the study suggested that the proposed approach: (a) provides a structured process for systematizing decision-making; (b) enables the involvement of multiple stakeholders, distributing the decision-making responsibility to more knowledgeable people; (c) uses monetized representations that are important for assessing decisions in a unified manner; and (d) enables decision reuse and documentation. Conclusions The results of the study suggest that architectural decision-making can benefit from treating this activity as a financial investment. The various benefits that have been identified from mixing financial and technological aspects are well-accepted from industrial stakeholders

Documentation Driven Software Development

The views, opinions and/or findings contained in this report are those of the author(s) and should not contrued as an official Department of the Army position, policy or decision, unless so designated by other documentation.Our objective is to develop an integrated, systematic, documentation centric approach to software development, known as Documentation Driven Software Development (DDD). The research issues for DDD are creation and application of three key documenting technologies that will drive the development process and a Document Management System (DMS) that will support them. These technologies address (1) representations for active documents; (2) representations for repositories; (3) methods for analysis, transformation, and presentation of this information. In addition, we explored new possibilities for computed-aided interfaces that help humans with routine tasks. In doing so we applied Cognitive Science and machine learning methods to design user interfaces that can learn and assist users. We also expanded our work in the area of integration of ontologies from heterogeneous sources. Specifically, we studied Knowledge System Integration Ontology (KSIO) that aligns data and information systems with current situational context for the efficient knowledge collection, integration and transfer. The role of ontology is to organize and structure knowledge (e.g. by standardized terminology) so that semantic queries and associations become more efficient. We assessed the degree to which natural language processing can be usefully applied to the analysis of requirement changes and their impact on system structure and implementation