Domain Objects and Microservices for Systems Development: a roadmap

This paper discusses a roadmap to investigate Domain Objects being an adequate formalism to capture the peculiarity of microservice architecture, and to support Software development since the early stages. It provides a survey of both Microservices and Domain Objects, and it discusses plans and reflections on how to investigate whether a modeling approach suited to adaptable service-based components can also be applied with success to the microservice scenario

Constructing the Phylomemetic Tree: Indonesian Tradition-Inspired Buildings\ud

The paper discusses the importance of phylomemetic visualization to approach the cultural diversity in the social system like Indonesia, and thus revisit formal methodology regarding to the construction of the phylomemetic tree as an inspiration lent from the phylogenic analysis. A case of study is presented regarding to the data obtained from the diversity of traditionally inspired building-designs in Indonesia. Some future conjectures and open future analytical works in the anthropological studies are drawn

Software architecture: styles and representational schemes

Software architecture is being widely used today to describe a very high-level design methodology of large software systems. Software architecture represents the overall structure of a system in an abstract, structured manner. A good architectural representation scheme holds the key to the effectiveness of a software architecture description and usage. In this work we look at architectural styles and architectural representation schemes. We propound the idea that the layered architectural model is a suitable candidate for a generalized architectural style and that it can cater to many different problem domains, other than the message-passing systems it has traditionally been used to model. We propose some rules by which the layered architectural style can be improved and modified in order to be able to model a wider problem domain. Then we evaluate different methods of architectural representations that have been used to model software architecture and analyze their strengths and shortcomings. We propose the use of a modified data flow diagram architecture representation scheme. This scheme is called AND-OR DFD method and is introduced and developed in this thesis. The main concept introduced here is a combination of components to form action groups to support multiple workflows and the relationships among them, without significant increase in the architectural complexity. Finally, we look at UML as a prospect for a generalized architecture description language and discuss its merits and demerits with examples

Semantic Bridging between Conceptual Modeling Standards and Agile Software Projects Conceptualizations

Software engineering benefitted from modeling standards (e.g. UML, BPMN), but Agile Software Project Management tends to marginalize most forms of documentation including diagrammatic modeling, focusing instead on the tracking of a project\u27s backlog and related issues. Limited means are available for annotating Jira items with diagrams, however not on a granular and semantically traceable level. Business processes tend to get lost on the way between process analysis (if any) and backlog items; UML design decisions are often disconnected from the issue tracking environment. This paper proposes domain-specific conceptual modeling to obtain a diagrammatic view on a Jira project, motivated by past conceptualizations of the agile paradigm while also offering basic interoperability with Jira to switch between environments and views. The underlying conceptualization extends conceptual modeling languages (BPMN, UML) with an agile project management perspective to enrich contextual traceability of a project\u27s elements while ensuring that data structures handled by Jira can be captured and exposed to Jira if needed. Therefore, concepts underlying the typical software development project management are integrated with established modeling concepts and tailored (with metamodeling means) for the domain-specificity of agile project management. A Design Science approach was pursued to develop a modeling method artifact, resulting in a domain-specific modeling tool for software project managers that want to augment agile practices and enrich issue annotation

A Catalog of Reusable Design Decisions for Developing UML/MOF-based Domain-specific Modeling Languages

In model-driven development (MDD), domain-specific modeling languages (DSMLs) act as a communication vehicle for aligning the requirements of domain experts with the needs of software engineers. With the rise of the UML as a de facto standard, UML/MOF-based DSMLs are now widely used for MDD. This paper documents design decisions collected from 90 UML/MOF-based DSML projects. These recurring design decisions were gained, on the one hand, by performing a systematic literature review (SLR) on the development of UML/MOF-based DSMLs. Via the SLR, we retrieved 80 related DSML projects for review. On the other hand, we collected decisions from developing ten DSML projects by ourselves. The design decisions are presented in the form of reusable decision records, with each decision record corresponding to a decision point in DSML development processes. Furthermore, we also report on frequently observed (combinations of) decision options as well as on associations between options which may occur within a single decision point or between two decision points. This collection of decision-record documents targets decision makers in DSML development (e.g., DSML engineers, software architects, domain experts).Series: Technical Reports / Institute for Information Systems and New Medi

The need of diagrams based on Toulmin schema application: an aeronautical case study

In this article, Justification Diagrams are introduced for structuring evidence to support conclusions that are reached from results of simulation studies. An industrial application is used to illustrate the use of the Justification Diagrams. Adapted from the Toulmin schema, the aim of Justification Diagram is to define a comprehensive, auditable and shareable notation to explain the results, the input data, the assumptions made and the techniques applied, to construct a cogent conclusion. Further, the Justification Diagrams provide a visual representation of the argument that aims to corroborate the specified claims, or conclusions. A large part of this work is based on the application of the Justification Diagrams in the context of the European project, TOICA. The Justification Diagrams were used to structure all justifications that would be needed to convince an authority that a simulation process, and the associated results, upheld a particular conclusion. These diagrams are built concurrently in a product development process that accompanies the various stages of Verification and Validation (V&V) and where, for each design stage of V&V, argumentation is constructed by aggregating evidence and documents produced at this design stage

Design thinking support: information systems versus reasoning

Numerous attempts have been made to conceive and implement appropriate information systems to support architectural designers in their creative design thinking processes. These information systems aim at providing support in very diverse ways: enabling designers to make diverse kinds of visual representations of a design, enabling them to make complex calculations and simulations which take into account numerous relevant parameters in the design context, providing them with loads of information and knowledge from all over the world, and so forth. Notwithstanding the continued efforts to develop these information systems, they still fail to provide essential support in the core creative activities of architectural designers. In order to understand why an appropriately effective support from information systems is so hard to realize, we started to look into the nature of design thinking and on how reasoning processes are at play in this design thinking. This investigation suggests that creative designing rests on a cyclic combination of abductive, deductive and inductive reasoning processes. Because traditional information systems typically target only one of these reasoning processes at a time, this could explain the limited applicability and usefulness of these systems. As research in information technology is increasingly targeting the combination of these reasoning modes, improvements may be within reach for design thinking support by information systems