Abstract

The principal objective of modelling symposium is to help form an active community working on various aspects of modelling and its applications. The focus is on problems that would be critical 3-5 years out in future. For example, problem spaces such as enterprises, systems, cyber-physical systems, etc. will be given more importance. The event has keynote and 6 invited talks delivered by personnel from Academia and Industry around the world. ModSym invited students and researchers to submit posters and extended abstracts.

Abstract

Software engineering researchers and their industrial counterparts have emphasized that research is essential for innovation. In practice, rather than ending up in a win-win situation, most of the times both the parties lose because of differences in expectations between the two sides. In this report, we briefly summarize the key insights from 1st International Workshop on Software Engineering Research and Industrial Practices (SER&IPs 2014) co-located with 36th International Conference on Software Engineering (ICSE 2014). The core lesson that stems out of this workshop is a definite need to have multiple approaches to deal with software engineering research-industrial practices partnership. Specifically, the workshop presented two keynotes: one from an industrial researcher explaining the need for academic expertise and an academic researcher on how their research added value to industry. An invited …

Abstract

Integrated software products are complex in design. They are prone to defects caused by integrated and non-integrated modules of the entire integrated software suite. In such software products, a small proportion of defects are fixed as soon as they are reported. Rest of the defects are targeted for fixes in future product release cycles. Among such targeted defects, most of them seem to be insignificant and innocuous in the current version but have the potential to become acute in future versions. In this paper, we propose an approach to study defect dependency of the reported defect using a dependency metric. Identifying the dependency of a defect in an integrated product suite can help the product stake-owners to prioritize them and help improve software quality.

Abstract

India has 790+ million active mobile connections and 80.57 million smartphone users. However, as per Reserve Bank of India, the number of transactions performed using smartphone based mobile banking applicationsis less than 12% of the overall banking transactions. One of the major reasons for such low numbers is the usability of the mobile banking app. In this paper, we focus on usability issues related tomobile banking apps and propose a Mobile App Usability Index (MAUI) for enhancing the usability of a mobile banking app. The proposed Index has been validatedwith mobile banking channel managers, chief information security officers, etc.

Abstract

Aspect oriented programming (AOP) is a programming paradigm that provides mechanisms for encapsulating cross-cutting concerns. Developers who want to learn AOP often experiment with aspects and different Pointcuts on their existing code bases to try and incorporate aspects into their software project. This typically involves an iterative process of testing multiple Pointcuts, partially due to the new syntax the developer has to learn, as well as to try and find the aspectual implementation that best fits their needs. Incremental weaving time is a huge factor in making this process smooth and faster for developers to more readily learn and adopt AOP. We propose an optimization approach that focuses on reducing redundant re-compilations and weaving. We propose that the approach can reduce the time being spent for weaving and thereby facilitating faster iterative project build time. We have done some initial

Abstract

Refactoring is a set of techniques used to enhance the quality of code by restructuring existing code/design without changing its behavior. Refactoring tools can be used to detect specific code smells, propose relevant refactorings, and in some cases automate the refactoring process. However, usage of refactoring tools in industry is still relatively low. One of the major reasons being the veracity of the detected code smells, especially smells that aren’t purely syntactic in nature. We conduct an empirical study on some refactoring tools and evaluate the correctness of the code smells they identify. We analyze the level of confidence users have on the code smells detected by the tools and discuss some issues with such tools.

Abstract

Product based organizations have diverse product offerings that meet various business needs. The products are in turn integrated to create integrated product suites. Rigorous product engineering is a must for creation of high quality integrated software products. Adequate measures must be taken to improve quality of the integrated product before every release of its module or sub-product. It is hard to imagine upgrading an integrated software product with unidentified defects prior to its release. In this paper, we share our observations on implementing a defect dependency metric to identify the dependency of a defect over a real-time industry defect dataset of an integrated software product. This defect dependency metric was captured and analyzed during release cycle (s) to avoid surprise issues post product launch.

Abstract

Traditional engineering disciplines like electrical engineering, mechanical engineering, metallurgical engineering have focused on the design of artifacts. However most the modern day software engineering course with in the undergraduate-computing curriculum focuses on teaching software processes rather than design of software artifacts. This paper argues the need for introducing software product engineering, i.e., a course that extensively deals with design of software artifacts in undergraduate computing curriculum. At a broader level, we also argue the need for more undergraduate software engineering programs in India.

Abstract

Refactoring tools suffer from usability in the areas of automating mundane tasks, providing user customization, and providing strategies for error recovery. The automation of refactoring tools can be a risky undertaking since user intervention is required in many scenarios to maintain the internal quality of the system. Any type of design level refactoring requires complex changes to the code, the validation of preconditions, and could potentially harm the system. Smaller refactorings that handle code-smells can be carried out automatically with considerably lower risk. This paper discusses the current state of automated refactoring tools, and the development of an automated refactoring tool to extract and propagate Java literal expressions in IntelliJ IDEA.

Abstract

Presence of information from multiple sources on the internet requires evaluating the credibility of the information, before its utilization. Researchers have suggested that internet users experience difficulty in accessing necessary information and do not pay enough attention to its credibility. We present here the design and implementation of an automated Web Credibility Assessment Support Tool (WebCAST) that considers multiple factors (type of website, popularity, sentiment, date of last update, reputation and review based on users' ratings reflecting personal experience) for assessing the credibility of information and returns a summary indication of the credibility of a website. We use Potentially All Pairwise RanKings of all possible Alternatives (PAPRIKA) method of Multi-Criteria Decision Analysis (MCDA) to give weights to the scale values on each factor, representing the relative importance of the attributes. An empirical evaluation of the tool was conducted by computing the correlation between the tool-generated credibility scores and that of human judges. The correlation was found to be 0.89, thus verifying the validity of the tool. In the future the proposed tool can be made useful to students in their learning process of credibility assessment.