Search

The Medical Imaging Interaction Toolkit (MITK) is a powerful tool for image processing and application development with a long history [1, 2]. It provides an easy-to-use superbuild for a variety of development scenarios and a host of customization options. This very exibility can be intimidating to new users and even more experienced users might miss out on new developments due to the sheer size of the code base. In this tutorial we will give an overview on MITK, theunderlying concepts and the usage of the MITK Workbench. Afterwards we will show the attendees how to start their own software development with MITK and what pitfalls to look out for. Due to time constraints this will be in the form of a development demonstration, instead of a hands-on session. This will be followed by an introduction into more advanced usage scenarios, intended to provide a customized Workbench for special work ows or to conform to branding requirements. We will close with newly finished and ongoing developments and the new opportunities which arise based on them.

Despite all the reasons why complex simulations are desirable for decision and policy making, and despite advances in computing power, large distributed simulations of urban areas are still rarely used, with most of their adoption in military applications. The reality is that developing distributed simulations is much harder than developing non-distributed, specialized ones, and requires a much higher level of software engineering expertise. This paper looks at urban simulations from a software engineering and systems design perspective, and puts forward the idea that non-traditional decompositions in simulation load management are not just beneficial for these applications, but are likely the only way to move that field forward.

In view of the problem that current jigsaw games have no functions of upgrades or accumulation scores, the UML (Unified Modeling Language) technology is adopted to analyze to design the mobile game software via spitting jigsaw puzzle pieces of a map. The results of software development illustrate that it is very easy to upgrade and accumulate scores. The gaps between design and coding are smaller using UML than before. Also, the software development period is shorter. Not only the material resources for entity toys can be saved greatly via this software, but also it is significant for children users to study the knowledge of map and traffic.

The research shows that maintenance of enterprise information systems consumes about 65---75i¾?% of the software development time and about 40---60i¾?% of maintenance efforts are devoted to software understanding. This paper compares the Anemic Domain Model used by the three-layered architecture followed by Java EE and .NET platforms and the Rich Domain Model often deployed into many conventional MVC-like web frameworks to a novel Aspect Domain Model followed by the Aspect-driven design. While all these models strive to avoid information restatement, they greatly differ in the underlying idea and resulting efficiency. This research compares considered models based on development efficacy, maintainability and their impact on the rest of the system. We evaluate qualities such as information cohesion, coupling and restatement, and discuss related maintenance efforts of the novel approach in the context of existing approaches.

Modern software systems are increasingly long-lived. In order to gracefully evolve these systems as they address new requirements, developers need to navigate effectively between domain concepts and the code that addresses those domains. One of the original promises of object-orientation was that the same object-oriented models would be used throughout requirements analysis, design and implementation. Software systems today however are commonly constructed from a heterogeneous "language soup" of mainstream code and dedicated DSLs addressing a variety of application and technical domains. Has object-oriented programming outlived its purpose? In this essay we argue that we need to rethink the original goals of object-orientation and their relevance for modern software development. We propose as a driving maxim, "Programming is Modeling," and explore what this implies for programming languages, tools and environments. In particular, we argue that: 1 source code should serve not only to specify an implementation of a software system, but should encode a queryable and manipulable model of the application and technical domains concerned; 2 IDEs should exploit these domain models to enable inexpensive browsing, querying and analysis by developers; and 3 barriers between the code base, the running application, and the software ecosystem at large need to be broken down, and their connections exploited and monitored to support developers in comprehension and evolution tasks.

Many cryptographic protocols proposed to securely send and receive information with someone in unsecured network for various purposes. To design secure cryptographic protocols, formal analysis for cryptographic protocols should be included as an essential activity in a process of cryptographic protocol design. In other word, the ideal process consists of design, formalization, formal analysis, interpretation, and improvement, and the five activities are done repeatedly as similar as activities in spiral model of software development. This paper presents a supporting tool for the ideal process of cryptographic protocol design. At first, the paper presents the spiral model of cryptographic protocol design, and introduces formal analysis method with reasoning as a suitable formal analysis method for the spiral model. The paper also presents design of the supporting tool and its implementation for key exchange protocols. By the supporting tool, designers can only focus on design and improvement activities in the spiral model.

Today’s software systems rely heavily on complex resources, such as humans. Human-intensive systems are particularly important in our society, especially in the healthcare, financial, and software development domains. One challenge in developing such systems is that the system design must account for the constraints, capabilities, and allocation policies of their complex resources, particularly the humans. The resources, their capabilities, and their allocation policies and constraints need to be carefully specified, and modeled. Toward the goal of supporting the design of systems that make effective use of such resources, we introduce a resource specification language and a process-aware, discrete-event simulation engine that simulates system executions while adhering to these resource specifications. The simulation supports (1) modeling the resources that are used by the system, and the ways in which they are used, (2) experimenting with different resource capability mixes and allocation policies, and (3) identifying such undesirable situations as bottlenecks, and inefficiencies that result from these mixes and policies. The joint use of detailed resource specifications and simulation supports rapid evaluation of human-intensive system designs. We evaluate our specification language and simulation framework in the healthcare domain, on a software system for managing a hospital emergency department.

Scrum is an efficient software development process. However, in order to master its concept, practitioners need to have a considerable level of software development skills and go through cycles of actual activities. This could be expensive and time consuming. “Scrum simulation with LEGO bricks” is a very popular solution to tackle such limitations. Unfortunately, due to its high costs, implementing this workshop in a large software engineering class could be financially challenging. This paper proposes an alternative low cost solution for simulating scrum software development by using low cost plasticine as main material. It also reports results of two pilot studies on this alternative simulation.

Software development is either creation activities that rely on developers creativity and talents, or manufacturing activities that follow the engineering processes. Engineering processes need to include creation activities to address tasks such as requirement elicitation and bug finding . On the other hand, by exploiting the crowd wisdom, open-source development has been demonstrated to be a suitable environment for software creation. However, it also has several limitations, such as guaranteeing the progress and quality of production process. This paper introduces a software development platform and ecosystem that combines the strengths of the two models. First, we propose the Trustworthy Software Model as a basis to support such a hybrid development ecosystem . The core of this model contains a novel lifecycle model, an evidence model and an evolution model. Second, based on the model, we propose the Trustworthy Software Development and Evolution Service Model. It integrates crowd collaboration , resource sharing, runtime monitoring , and trustworthiness analysis into an unified framework. Based on this integrated model, we designed and implemented TRUSTIE , which distinguishes itself from other software crowdsourcing platforms by providing the software collaborative development service and the resource sharing service with the general support of trustworthiness-analysis tools. TRUSTIE enables crowd-oriented collaboration among internal development teams and the external crowds by combining the software creation and software manufacturing in one ecosystem.