Inggriani Liem

Metadata approach in modeling multi structured data collection using object oriented concepts

In designing an enterprise wide system, a system architect must consider different concerns of the stakeholders. In this paper, we propose a generic metadata approach for modeling data with multi structure representations derived from different points of view of the stakeholders. The notion of structures/organizational views of data is separated from the collection of the data itself. We introduce two layers of the generic metamodel: (1) dataset: real data handled as a collection; (2) viewpoint: a more abstract layer describing the many structures/metadata for each point of view. The idea of datasets and viewpoints are adopted from the concepts of abstract and concrete class in object oriented modeling. To validate the generic model, we provide several case studies. We expect the proposed model provides a better architectural way of thinking in modeling an enterprise.

Reshaping software engineering education towards 2020 engineers

In this paper, we present an overview on how to reshape the software engineering education in our undergraduate study program (i.e., curriculum program, software engineering curriculum package, and learning process) so that our graduates have sufficient skills to be the 2020 software engineers. We believe that the corner blocks to produce fine engineers are good understanding in the following areas: basic fundamentals and principles of science and computing, methodology, techniques-tools-platform, capability to understand domain problems, communication and personal skill, attitude to be a good learner and self disciplined. We translate these values to our undergraduate curriculum with an aim to produce general software engineer who are quick to master specific platforms/technologies and devices and to understand domain problems.

Automatic grader for programming assignment using source code analyzer

Source code analyzer is a tool for analyzing source code that aim to improve the quality of programs in software development. This research enhanced the ability of source code analyzer for automatic grading of programming assignments. The automatic grading process runs in three phases: (a) source code analysis by source code analyzer, (b) analytical results unification, and (c) unification results assessments. Analysis unification use the XSLTtransformation process, while the assessment done by matching bugs/flaws found in the source code with a list of bugs/flaws that have been defined. This research deliver application called SCAGrader. SCAGrader consists of a Java engine application in the Java language and web-based user interface. The score obtained by giving a negative score to each bugs/flaws found in students source code. Beside its independent capability, SCAGrader also integrated to existing blackbox autograding system by services. The other result of this study is a classification of bugs/flaws for teaching programming, based on five source code analyzers.

Android security assessment based on reported vulnerability

Android is considered as the leading platform on smartphone market. Thus, it becomes a prime target by many security crooks and its security becomes at most concern. This research aims at assessing Android Security, especially the fact whether Androids folks are getting better or worse in delivering a secure platform? In this research, we use data extracted from National Vulnerability Database (NVD) to answer such question. Surprisingly, the study discovers that 83.3% of reported Android vulnerability is originated from third-party apps that runs on Android platform and not inherently from the Android platform itself. We also discover strong evidence that Android security is getting better based on the declining numbers of reported Android vulnerability and the reducing of Android vulnerability Time-to-Patch.

Concern Based SaaS Application Architectural Design

With SaaS application, tenant can focus on application utilization while Independent Software Vendor (ISV) is responsible for application dep- loyment, installation, operation and maintenance. Using Aspect Oriented Soft- ware Development (AOSD), we propose eight concerns, i.e. configurability, discriminator, measurement, monitoring, tenant management, billing manage- ment, performance management, and application management. Those concerns are integrated into a SaaS system architectural design, to enhance SaaS opera- tional flexibility and maintainability. As a proof of concept, we developed a SaaS operational environment using Spring and AOP. Two Java applications have been integrated to this environment after tailoring. We have tested the modules, classes and services and then the applications, to demonstrate that the platform is able to run a set of web applications as a SaaS. Using this system, ISV can modify an existing Java application easily to be a part of SaaS and measure resource usage and monitor SaaS operation by a dashboard.

Software versioning quality parameters: Automated assessment tools based on the parameters

Version Control System (VCS) is used by software developers during a software development project with the purpose for maintaining versions and collaborative work. It is a part of configuration management. Developers work together using the same environment. Though all developers must follow the same best practices, each developer may work individually with different practices due to different knowledge and experience of using VCS. Many best practices are available, but they are different. In this paper, we define quality parameters based on quality factors. The quality factors and associated metrics are extracted from the log file of VCS. These parameters bear out good software versioning activities. To prove the concept, we build a tool for automatically assessing the quality of versioning activities of a developer, based on the log file of a VCS. The tool has been tested and used for assessing the quality of software versioning of two open source projects. As the result, developers versioning activities can be analysed.

Automated data consistency checking using SBVR: Case study: Academic data in a University

Data are the most important asset of an organization. Even though the application or business rules change, consistent data stored in the database must be kept. This research is intended to propose a framework for checking the consistency of an existing database to the business rules in which the data must comply. The research focuses on the situation where the documents of database and the application are obsolete. The rules are extracted from the associated documents (e.g. the decrees) before they are finally expressed in SBVR. Those rules are used for data checker SQL script generation. The automation process is possible if the database has a naming convention and the organization has a standardized vocabulary. The framework has been tested using academic data, where the database has no documentation, and the application is still operating until today. A business rule grammar and SQL query templates are proposed. Data consistency checker tool based on the academic rules expressed in SBVR is developed. The research conducted found data that do not comply with the rules. The contribution of this research is a framework and a tool for data consistency checking.

Source code generator for automating business rule implementation

Business rules can be implemented on business processes, business behavior, people, or software in an organization. Aligned with software development, business rules are captured from requirement elicitation and analysis, then designed and implemented in the software. The changes of business environment may affect business rules. The changes of the business rules may bring impact in the software, so that the software needs to be redeveloped. In this paper, we present a source code generator to automate business rule implementation using business rule approach. We propose a Domain Specific Language (DSL) of business rule to help expressing business rules in a business-friendly language. We also develop a business rule generator to generate source codes based on a DSL script for expressing the business rules. The proposed solution has been tested in two case studies. It is shown that the generator can help the implementation of the business rules in source codes and that the generated code can be used in business applications.

A/B test tools of native mobile application

When an application developer wants to introduce a new idea to his application, the idea needs to be validated with hypothesis testing in order to prove the treatment variant (application with new idea) will become a better alternative compared with the control variant (base application). In web application development, controlled experiment (known as A/B test) is commonly used as tools for testing a hypothesis. Controlled experiment for native mobile application (hereinafter, mobile application) in this research is created based on controlled experiment in web. We identified three main difficulties in mobile application controlled experiment compared to experiment of web application: element composition, variant delivery, and network connectivity. We propose techniques to overcome the difficulties in controlled experiment for mobile application: splitter generator and plugin architecture + custom build system. This technique is implemented as set of tools for creating variant easily and conducting controlled experiment of mobile application, consists of variant generator, library for tracking experiment execution, a build system, and a monitoring web application. Tools have been tested using two cases. The experiment shows that our tools are able to help developer produce a controlled variant with clearer separation of concern and to conduct controlled experiment easier.

Agent-message based multi-io application framework development

Nowadays, due to diversity of devices and mode of application, similar functionalities of software must be implemented in more than one application software. Each functionality can be represented by an agent, and the application that activates the agent can be considered as input/output, which we called a multi i/o agent based system. As example, a client of a banking system can have access to his account (check balance, invoke a transaction, make a transfer or payment, etc) through web application, mobile device and the same account can be accessed by bank officer through a desktop application. This situation motivates us to write an agent based framework that facilitates such kind of information system development. This paper describes the design and the development of Ameba, an agent based framework for developing multi-io applications. The framework has been tested by developing a small application as a case study for demonstrating the functionalities and usage of framework.