Oriented Software Development Research Articles

Compact Spiral Asymmetric encryption Distributed Ledger –Secured and authentication Mobile Payment System in Higher Institutions

Looking at the higher learning institutions, there is no question that the current methods for paying student fees are inefficient, inconvenient, and wasteful of time. In addition, the rise in the number of students studying in higher learning institutions has led to long frustrating queues and overcrowding in most financial institutions during payment of student fees. This paper sought to design and implement a secure block chain-based payment system for higher learning institutions in developing countries. Students are to use the proposed payment system to pay tuition fees and other student fees to their respective higher educational institution. In addition, students are to use the proposed payment to pay for goods and services provided by the institution and other merchants in the institution’s premises. In this study, object oriented software development methodology was used to implement the proposed payment system. The proposed system consists of a mobile e-wallet, RESTful API, and blockchain as the core component of the API.

Recipe Planning Application

Kenyalang’s Kitchen is an Android-based recipe planning application to promote Sarawak’s traditional recipe. The application will assist user in the preparation of customary cuisine from various ethnicities in Sarawak. The user is able to choose the recipe based on the ingredients selected. Besides that, the application provides the ‘Xprez List’ that consists of recipe list that can be prepared in a minimum time. This application offers unique features such as‘Food Famous’ which will list all the well-known cuisine from different ethnicities in Sarawak. Another uniqueness of this application is ‘Glossary’ to help the users to understand some of the unfamiliar terms. The recipe recommender is developed by using Object Oriented Software Development methodology. The software used is Android Studio in Java programming language. In short, the application aims to guide the users to prepare the Sarawak’s traditional recipe.

Recipe Planning Application

Kenyalang’s Kitchen is an Android-based recipe planning application to promote Sarawak’s traditional recipe. The application will assist user in the preparation of customary cuisine from various ethnicities in Sarawak. The user is able to choose the recipe based on the ingredients selected. Besides that, the application provides the ‘Xprez List’ that consists of recipe list that can be prepared in a minimum time. This application offers unique features such as‘Food Famous’ which will list all the well-known cuisine from different ethnicities in Sarawak. Another uniqueness of this application is ‘Glossary’ to help the users to understand some of the unfamiliar terms. The recipe recommender is developed by using Object Oriented Software Development methodology. The software used is Android Studio in Java programming language. In short, the application aims to guide the users to prepare the Sarawak’s traditional recipe.

Integrating security and privacy in software development

As a consequence to factors such as progress made by the attackers, release of new technologies and use of increasingly complex systems, and threats to applications security have been continuously evolving. Security of code and privacy of data must be implemented in both design and programming practice to face such scenarios. In such a context, this paper proposes a software development approach, Privacy Oriented Software Development (POSD), that complements traditional development processes by integrating the activities needed for addressing security and privacy management in software systems. The approach is based on 5 key elements (Privacy by Design, Privacy Design Strategies, Privacy Pattern, Vulnerabilities, Context). The approach can be applied in two directions forward and backward, for developing new software systems or re-engineering an existing one. This paper presents the POSD approach in the backward mode together with an application in the context of an industrial project. Results show that POSD is able to discover software vulnerabilities, identify the remediation patterns needed for addressing them in the source code, and design the target architecture to be used for guiding privacy-oriented system re-engineering.

The Role of Model-View Controller in Object Oriented Software Development

Object Oriented Software Development (OOSD) is a design technique that is used before the development and design of a software. This design method makes the system appears as a collection of objects to communicate with other objects by passing messages. The Model-View-Controller (MVC) has been inherited from Object-Oriented Programming (OOP) with the integration of Graphical User Interface (GUI) and interactive program execution. The MVC is very useful for developing Interactive and Dynamic Web Applications and iOS. With MVC, developers can trust on design patterns that are widely accepted as solutions for recurring problems. MVC can be used to develop flexible, reusable and modular Software. Applying the MVC design pattern in object-oriented Software development a flexible, reliable, modular and scalable website can be built. So, it’s necessary for every developer to have the knowledge of software development using MVC design pattern.

A Metrics-based Framework for Estimating the Maintainability of Object-Oriented Software

Time, effort and money required in maintaining software has always been considered greater than its development time. Also, its ambiguity in forecast at early stage of software development makes the process more complicated. The early estimation of maintainability will significantly help software designers to adjust the software product, if there is any fault, in early stages of designing. By doing this; time, effort and money required in maintaining software will be lessened. Although Object Oriented Software Development (OOSD) approach is equipped for enhancing software maintainability, a method for finding out if the required level of maintenance is being achieved amid the development process is required. This can be accomplished through measurement. This paper outlines the need and importance of maintainability at design phase and develops a Metrics-Based Maintainability Estimation Framework for Object-Oriented software(MEFOOS) that estimates the maintainability of object oriented software components in regard of their Understandability, Modifiability and Portability—which are the sub-attributes of maintainability. Keywords: Software maintenance, Software Maintainability, maintainability model, Software Metrics, Software Component DOI : 10.7176/JIEA/9-4-02 Publication date :June 30 th 2019

Software Evolution Rules with Condition Constrains to Support Component Type Matching Based on Bigraph

With the gradual maturity of component oriented software development method, component-based software evolution technology has become hot research in academia and industry. Although many evolution rules are designed, they rarely consider component type-mismatched problem in evolution rules. This has led to evolution rules that often run error in software evolution execution. Hence, focusing on the mismatch problem of component type in software evolution, this paper addresses various evolution rules with condition constrains to support component type matching. First, we use the bigraph theory to model the software architecture and employ bigraph term language to describe the basic component evolution operations. Second, we join type system into the term language and use the type term language to express the condition constraints on position and connection for component evolution rules. These condition constraints can guarantee the type-matched among components that participate in software evolution. Furthermore, we show that the component type-matched still kept during a number of different evolution rules are used in the whole software evolution reaction system. Finally, two cases study of evolution progress of ATM system and tourism information system are presented. Two cases illustrate the effectiveness of our approach.

E-Raser: File Shredder Application With Content Replacement by Using Random Words Function

Data shredding indicates a process of irreversible file destruction while file shredder is the program designed to render computer-based files unreadable by implementing overwriting method to destroy data in the content of a file. The addressable problem with existence of file recovery tools is it may lead to data leakage, exploitation or dissemination from an unauthorized person. Thus, this study proposed a file shredding application named E-Raser which replacing the content of the file using random words function algorithm. A file shredder application named E-Raser was developed to shred Microsoft Word documents with (.doc) or (.docx) format. The implemented algorithm replaced the original content of the files with uninformative words provided by the application. After rewriting phase is complete, shredding process take place to make the file unrecoverable. Object Oriented Software Development was used as the methodology to develop this application. As a result, E-Raser achieved the objectives to add, remove, rewrite, display and shred files. Also, E-Raser is significantly facilitates users to securely dispose their file, protect the confidentiality and privacy of the file’s content.

A COMPREHENSIVE INTERPRETATION OF OBJECT ORIENTED METRICS FOR QUALITY REFINEMENT IN SOFTWARE DEVELOPMENT

In Digital era, Software in electronic devices has become an indispensable to our daily life. Software Metric is a significant software engineering field that plays a quality role in software measurement. Better measurement and metrics are stepping stone to software growth with distinction. Moving from measurement to metrics is like moving from observation to understanding. Metrics are conceived by the user and designed to reveal a chosen characteristic in a reliable and meaning manner. Object Oriented Software is based on approach that works around the real-world entities and their characteristics. Object Oriented Software measurement is procedure in which calculations are done on real world entities to describe them according to clearly defined rules. Object Oriented Metric plays a vital role to find the efficiency of the software and improvement for future. The measurement of object oriented software seems to be a powerful tool for product effectiveness. This paper will analyze different Object Oriented Metrics and helpful for ensuring quality design with high cohesion and low coupling for advancement in Object Oriented Software Development.

AGNT7 for an Intelligent Software Agent

Objectives: The paper defines an agent structure that will help in designing of the agents in agent oriented software development. Methods/Statistical Analysis: The paper proposes a structure AGNT7 that defines elements needed in designing of an intelligent software agent. AGNT7 covers implementation aspect of agent. It is based on XML language. The paper defines all seven elements of the structure in detail. It also defines interaction among elements needed to proper functioning of agent. Findings: Two cases have been designed using proposed structure. It shows that all elements in the structure are necessary and worth for designing of intelligent software agent. Designed agent also exhibits evolving nature which is needed to update itself with changing requirements. Proposed structure also shows use of XML language in providing evolving capability in the agent. The paper defines various formats of XML language that can be utilized in software development based on agents. It also defines mathematical representation of elements of proposed structure. Applications/Improvement: AGNT7 provides clear guidelines to developer for designing of agent that speeds programming of software based on agents.

An approach based on runtime models for developing dynamically adaptive systems

We propose an approach based on runtime models and Aspect Oriented Software Development for modeling and implementing dynamically adaptive systems. Such system requires specific modeling formalisms to support the definition of the monitoring and reconfiguration modules at an abstract level. The verification of the consistency during the reconfiguration is also an essential and primordial task in the development process of dynamically adaptive systems. In addition, a middleware that enables to perform the dynamic reconfiguration during execution should be implemented.Our proposed approach addresses these requirements: It enables specifying dynamically adaptive systems using AADL and AO4AADL and verifying the integrity of the system at any time of its life cycle even at runtime based on a set of architectural patterns. Our approach uses the Aspect Oriented Software Development to ensure the monitoring of the system and perform the reconfiguration through a set of routines developed in our middleware.

Proposed Rough Edges of Interface-a Design Pattern

Interface of java used as a design pattern for object oriented software development mostly used with inheritance, in java multiple inheritance is possible only through the interface this approach is widely used with modern software development approach apart from that there is also a rough side of java’s Interface which discussed in this paper, interface doesn’t allow the any kind of definition under it, but there is also some other concept like parent and child class concept if such concept apply with the interface then the theory of interface has been changed in this paper a practical approach has been used for this research problem.

Aspect-oriented middleware framework for resolving service discovery issues in Internet of Things

Internet of Things IoT is a model of future internet and pervasive computing which have its own challenges derived from the internet in terms of scalability, undefined topology and so on. The proposed work aims to resolve the challenges posed by IoT in service discovery functionality. Considering the pervasive and context dependent nature of IoT the planned work bases its development strategy using an aspect oriented software development methodology. The novelty lies in achieving high degree configuration and customisability by selecting subset of middleware functionality depending on the need. The performance is compared with MUSIC pervasive computing middleware and Android built-in configuration. The result reveals 6.5% decrease on average boot up and reconfiguration time for smart phones and 11.6% percentage decrease in Android tablets. In the context of boot up and reconfiguration time the middleware brings out 5% decrease for smart phones and 3% for Android tablets when compared with MUSIC middleware. The middleware shows 6.3% and 4% reduction in execution time of applications on smart phones and tablets when assessed with MUSIC middleware.

Formalizing the ISDF Software Development Methodology

The paper is aimed at depicting the ISDF software development methodology by emphasizing quality management and software development lifecycle. The ISDF methodology was built especially for innovative software development projects. The ISDF methodology was developed empirically by trial and error in the process of implementing multiple innovative projects. The research process began by analysing key concepts like innovation and software development and by settling the important dilemma of what makes a web application innovative. Innovation in software development is presented from the end-user, project owner and project manager's point of view. The main components of a software development methodology are identified. Thus a software development methodology should account for people, roles, skills, teams, tools, techniques, processes, activities, standards, quality measuring tools, and team values. Current software development models are presented and briefly analysed. The need for a dedicated innovation oriented software development methodology is emphasized by highlighting shortcomings of current software development methodologies when tackling innovation. The ISDF methodology is presented in the context of developing an actual application. The ALHPA application is used as a case study for emphasizing the characteristics of the ISDF methodology. The development life cycle of the ISDF methodology includes research, planning, prototyping, design, development, testing, setup and maintenance. Artefacts generated by the ISDF methodology are presented. Quality is managed in the ISDF methodology by assessing compliance, usability, reliability, repeatability, availability and security. In order to properly asses each quality component a dedicated indicator is built. A template for interpreting each indicator is provided. Conclusions are formulated and new related research topics are submitted for debate.Keywords: Software Development Methodology, Innovation, Project Management(ProQuest: ... denotes formulae omitted.)IntroductionT he research efforts and results presented in the current paper apply exclusively to web applications. Though they might apply to other categories of software applications or to other fields altogether, they were validated only in the context of web applications. From the end-user's point of view, a web application is considered to be innovative if it's easier to use, faster, cheaper, more reliable or more secure than other applications that accomplish the same results or if it fulfils a need that has yet to be address in the online environment. In the context of the end-user, innovation targets the fulfilment of a specific need.From the project owner's point of view a web application is considered innovative if it:* includes at least a functionality that generates added value for the end-user and the functionality is not found in other web applications that target the same market;* includes a combination of functionalities that generate added value and the combination of functionalities is not found in the same configuration in any other web application that targets the same market; functionalities can be found separately in other web applications but not in the same configuration;* provides access to a graphic interface that includes elements or element combinations which improve user experience and are not found in other web applications that target the same market.In the context of the project owner innovation focusses on market characteristics and targets novelty and added value. From the project manager and from the development team's point of view a web application is considered to be innovative if it includes functionality that they have never implemented before. In the context of the project manager and the project team, innovation focusses on the degree of novelty of the current application compared to previously implemented applications. …

Aspect oriented design for team learning management system

A multi agent system (MAS) is a complex system composed of heterogeneous agents each has a number of concern that are cross-cutting such as mobility, learning, collaboration, adaptation, interaction and autonomy. MASs are currently designed to be superimposed on object oriented designs so that it can be possible to separate these concerns in order to improve reusability and maintainability. Hence, aspect-oriented software development (AOSD) exists to cope with complexity of software development for the purpose of separating functionality that are not handled by other software development. Following this line of thought, AOSD is considered for developing aspects for team learning management system; that allows recognizing learner’s learning preferences and associated learning style in the learning environment. This paper presents an approach to move from object oriented eTutor to agent oriented eTutor through aspect oriented software development. This transition is being deployed through the implementation level.

A Framework for Assessing the Software Reusability using Fuzzy Logic Approach for Aspect Oriented Software

Abstract —Software reusability is very important and crucial attribute to evaluate the system software. Due to incremental growth of software development, the software reusability comes under attention of many researcher and practitioner. It is pretty easier to reuse the software than developing the new software. Software reusability reduces the development time, cost and effort of software product. Software reusability define the depth to which a module can be reused again with very little or no modification. However the prediction of this quality attribute is cumbersome process. Aspect oriented software development is new approach that introduce the concerns to overcome the issues with modular programming and object oriented programming. However many researcher worked on accessing the software reusability on object oriented system but the software reusability of aspect oriented system is not completely explored. This paper explores the various metric that affects the reusability of aspect oriented software and estimate it using fuzzy logic approach.

A Theoretical Framework for the Maintainability Model of Aspect Oriented Systems

Abstract Aspect Oriented Software Development is gaining wide attention because of its key feature modularization. Aspect Oriented paradigm supports the separation of concerns that are scattered over the system which helps in achieving modularity. Aspect Oriented Software Development encompasses software engineering abstractions and complexity at new and different dimensions. So Aspect Oriented Software Development requires models to assess its external quality attributes. The quality attribute maintainability is vital, because maintenance tasks employs major chunk of the total software development cost. The quality, maintainability is indicated using metrics. This paper proposes a framework to build maintainability model for aspect oriented systems using already defined software measures.

An Analysis on Software Reusability in Context of Object Oriented and Aspect Oriented Software Development

An Analysis on Software Reusability in Context of Object Oriented and Aspect Oriented Software Development

A Review of Requirement Engineering Issues and Challenges in Various Software Development Methods

Requirement Engineering (RE) is a systemic and integrated process of eliciting, elaborating, negotiating, prioritizing, specifying, validating and managing the requirements of a system. The detailed and agreed requirements are documented and specified to serve as the basis for further system development activities. The software industry has moved from traditional software development method to service oriented software development. While many researchers and practitioners have observed issues and challenges in Requirement Engineering phase specific to a software method, very little attention has been given to investigate diversity of issues and challenges of RE in different software development methods under one umbrella. This paper tries to review significant issues and challenges of RE from traditional software development method to recent service oriented software development method. The study unveils that there is a wide scope for developing new approaches and techniques in requirement engineering to resolve problems observed in various SE methods. The review discussion reveals the need of standardization and automation of RE process especially for Service oriented software development. KeywordsEngineering, RE phase, SE methods, traditional software development, service oriented software development, automation of RE

What makes service oriented requirements engineering challenging? A qualitative study

The focus of Service Oriented Software Development (SOSD) is to develop software by integrating reusable services to lower the required cost, time and effort of development and increase reusability, agility, quality and customer satisfaction. It has been recognised in the literature that SOSD faces various challenges especially in requirements engineering (RE). The objective of this study is to investigate these challenges of Service Oriented RE (SORE) from practitioners' perspectives in order to gain a deeper understanding of the related issues and to reveal potential gaps between research and practice in SORE. They present a qualitative study of the challenges and issues in SORE. The data were collected by conducting interviews with practitioners working in IT companies in Sydney, who have had substantial experience with service oriented software projects. The authors findings reveal that most of the challenges of SORE are similar to those that are faced during RE in traditional or component-based software development. According to the practitioners, the research and practice has made some advances in the technical direction but the human related issues in SORE have not been addressed adequately.