This document summarizes an empirical study that developed a simplicity evaluation model for object-oriented software. It establishes relationships between software design simplicity factors and object-oriented design properties like encapsulation, coupling, inheritance, and polymorphism. A linear regression model was developed and validated experimentally to predict simplicity scores based on these design metrics. The model showed a high correlation with known simplicity values, demonstrating it is an effective way to quantitatively evaluate simplicity in object-oriented designs. Future work could involve testing the model on more and larger real-world projects.
A New Model for Study of Quality Attributes to Components Based Development A...Kiogyf
A New Model for Study of Quality Attributes to Components Based Development Approach
by bstract :
Software development costs, time - to release and quality product are important factors affecting the construction of software. Different types of tools and techniques are suggested by researchers to improve in delivering quality software systems with lower cost and reduce time to delivery. One such practice is development of software using ased Software Development (CBSD) techniques. CBSD recommended Component Bbuilding software systems using existing reusable components, instead of writing from scratch. The main objective of CBSD is to writes once and reuse any number of time with no or modification . Some of the advantages that a company may available by adapting CBSD for the Software development are shorter development time which results in meet tight dead line, increase productivity and Quality Product. CBSD also, s paper is to develop the new model of software support reusability. The aim of thiproduct and describe the characteristics of some selected of attributes of CBSD models that are widely practiced in software industries. We proposed a complete model for or reuse. This Model will cover both Component Based Software Development fcomponent based software development as well as Component development phases for
A - Model. This Model is represent one good solution for Component Based Development with reduce cost and time to deliverable and save the quality of product . Keywords: Component Based Approach, Quality Model, Quality Attributes, , A - Model for CBD .
1. Introduction
An Agile Software Development FrameworkWaqas Tariq
Agility in software projects can be attained when software development methodologies attain to external factors and provide a framework internally for keeping software development projects focused. Developer practices are the most important factor that has to cope with the challenges. Agile development assumes a project context where the customer is actively collaborating with the development team. The greatest problem agile teams face is too little involvement from the customer. For a project to be agile, the developers have to cope with this lack of collaboration. Embracing changing requirements is not enough to make agile methods cope with business and technology changes. This paper provides a conceptual framework for tailoring agile methodologies to face different challenges. The framework is comprised of three factors, namely, developer practices, customer collaboration, and predicting change
A User Story Quality Measurement Model for Reducing Agile Software Developmen...ijseajournal
In Mobile communications age, the IT environment and IT technology update rapidly. The requirements
change is the software project must face challenge. Able to overcome the impact of requirements change,
software development risks can be effectively reduced. Agile software development uses the Iterative and
Incremental Development (IID) process and focuses on the workable software and client communication.
Agile software development is a very suitable development method for handling the requirements change in
software development process. In agile development, user stories are the important documents for the
client communication and criteria of acceptance test. However, the agile development doesn’t pay attention
to the formal requirements analysis and artifacts tracability to cause the potential risks of software change
management. In this paper, analyzing and collecting the critical quality factors of user stories, and
proposes the User Story Quality Measurement (USQM) model. Applied USQM model, the requirements
quality of agile development can be enhanced and risks of requirement changes can be reduced.
A New Model for Study of Quality Attributes to Components Based Development A...Kiogyf
A New Model for Study of Quality Attributes to Components Based Development Approach
by bstract :
Software development costs, time - to release and quality product are important factors affecting the construction of software. Different types of tools and techniques are suggested by researchers to improve in delivering quality software systems with lower cost and reduce time to delivery. One such practice is development of software using ased Software Development (CBSD) techniques. CBSD recommended Component Bbuilding software systems using existing reusable components, instead of writing from scratch. The main objective of CBSD is to writes once and reuse any number of time with no or modification . Some of the advantages that a company may available by adapting CBSD for the Software development are shorter development time which results in meet tight dead line, increase productivity and Quality Product. CBSD also, s paper is to develop the new model of software support reusability. The aim of thiproduct and describe the characteristics of some selected of attributes of CBSD models that are widely practiced in software industries. We proposed a complete model for or reuse. This Model will cover both Component Based Software Development fcomponent based software development as well as Component development phases for
A - Model. This Model is represent one good solution for Component Based Development with reduce cost and time to deliverable and save the quality of product . Keywords: Component Based Approach, Quality Model, Quality Attributes, , A - Model for CBD .
1. Introduction
An Agile Software Development FrameworkWaqas Tariq
Agility in software projects can be attained when software development methodologies attain to external factors and provide a framework internally for keeping software development projects focused. Developer practices are the most important factor that has to cope with the challenges. Agile development assumes a project context where the customer is actively collaborating with the development team. The greatest problem agile teams face is too little involvement from the customer. For a project to be agile, the developers have to cope with this lack of collaboration. Embracing changing requirements is not enough to make agile methods cope with business and technology changes. This paper provides a conceptual framework for tailoring agile methodologies to face different challenges. The framework is comprised of three factors, namely, developer practices, customer collaboration, and predicting change
A User Story Quality Measurement Model for Reducing Agile Software Developmen...ijseajournal
In Mobile communications age, the IT environment and IT technology update rapidly. The requirements
change is the software project must face challenge. Able to overcome the impact of requirements change,
software development risks can be effectively reduced. Agile software development uses the Iterative and
Incremental Development (IID) process and focuses on the workable software and client communication.
Agile software development is a very suitable development method for handling the requirements change in
software development process. In agile development, user stories are the important documents for the
client communication and criteria of acceptance test. However, the agile development doesn’t pay attention
to the formal requirements analysis and artifacts tracability to cause the potential risks of software change
management. In this paper, analyzing and collecting the critical quality factors of user stories, and
proposes the User Story Quality Measurement (USQM) model. Applied USQM model, the requirements
quality of agile development can be enhanced and risks of requirement changes can be reduced.
SOFTWARE REQUIREMENT CHANGE EFFORT ESTIMATION MODEL PROTOTYPE TOOL FOR SOFTWA...ijseajournal
In software development phase software artifacts are not in consistent states such as: some of the class artifacts are fully developed some are half developed, some are major developed, some are minor developed and some are not developed yet. At this stage allowing too many software requirement changes may possibly delay in project delivery and increase development budget of the software. On the other hand rejecting too many changes may increase customer dissatisfaction. Software change effort estimation is one of the most challenging and important activity that helps software project managers in accepting or rejecting changes during software development phase. This paper extends our previous works on developing a software requirement change effort estimation model prototype tool for the software development phase. The significant achievements of the tool are demonstrated through an extensive experimental validation using several case studies. The experimental analysis shows improvement in the estimation accuracy over current change effort estimation models.
Following presentation answers:
- Why do we need evolution?
- What happens if we do not evolve the software?
- What are the types of software evolution?
- What are Lehman's laws
- What are the strategies for evolution?
The DSS presented in this document is a tool that improves the effectiveness of the decision making process that results in estimating, planning, and adapting: the products (software architecture, design specifications and code ), the activities (designing architecture, defining design specifications, and producing code) , and the measures of goodness (number of known requirements met, degree of resilience to new requirements, and degree of reusability) of the design and implementation phases of a Software Development Life Cycle.
Flexibility a key factor to testability ijseajournal
Testability is an important software quality factor that is ineffective if it is not available at an early stage in
the development life-cycle. It becomes more essential in the case of object oriented design. Flexibility is an
important key factor to testability analysis and measurement for delivering high class testable and
maintainable software. Flexibility is a criterion of crucial significance to software developers, designers
and the quality controllers. It constantly guides and supports to avoid wastage of resources as well as
enable the designers for continuous improvement in the development process. Flexibility is concerned with
building high quality and reliable software within the constraints of cost and time. It greatly influences
cost, quality and reliability at software evolution process. Despite the fact flexibility is vital and highly
significant aspect for software development processes, it is poorly managed. This paper focuses the need
and importance of flexibility early at design phase. A model has been proposed for flexibility measurement
of object oriented design by establishing multiple linear regression. Finally the proposed model has been
validated using experimental tryout.
Modern gadgets and machines such as medical equipments, mobile phones, cars and even military hardware run on software. The operational efficiency and accuracy of these machines are critical to life and the well being of modern civilization. When the software powering these machines fail it exposes life to danger and can cause the failure of businesses. In this paper, software quality measure is presented with the emphasis on improving standard and controlling damages that may result from badly developed application. The research shows various software quality standards and quality metrics and how they can be applied. The application of the metrics in measuring software quality in the research produced results which shows that the code metrics performance is better than the design metrics performance and points to a new way of improving quality by refactoring application code instead of developing new designs. This is believed to ensure reusability and reduced failure rate when software is developed
SOFTWARE REQUIREMENT CHANGE EFFORT ESTIMATION MODEL PROTOTYPE TOOL FOR SOFTWA...ijseajournal
In software development phase software artifacts are not in consistent states such as: some of the class artifacts are fully developed some are half developed, some are major developed, some are minor developed and some are not developed yet. At this stage allowing too many software requirement changes may possibly delay in project delivery and increase development budget of the software. On the other hand rejecting too many changes may increase customer dissatisfaction. Software change effort estimation is one of the most challenging and important activity that helps software project managers in accepting or rejecting changes during software development phase. This paper extends our previous works on developing a software requirement change effort estimation model prototype tool for the software development phase. The significant achievements of the tool are demonstrated through an extensive experimental validation using several case studies. The experimental analysis shows improvement in the estimation accuracy over current change effort estimation models.
Following presentation answers:
- Why do we need evolution?
- What happens if we do not evolve the software?
- What are the types of software evolution?
- What are Lehman's laws
- What are the strategies for evolution?
The DSS presented in this document is a tool that improves the effectiveness of the decision making process that results in estimating, planning, and adapting: the products (software architecture, design specifications and code ), the activities (designing architecture, defining design specifications, and producing code) , and the measures of goodness (number of known requirements met, degree of resilience to new requirements, and degree of reusability) of the design and implementation phases of a Software Development Life Cycle.
Flexibility a key factor to testability ijseajournal
Testability is an important software quality factor that is ineffective if it is not available at an early stage in
the development life-cycle. It becomes more essential in the case of object oriented design. Flexibility is an
important key factor to testability analysis and measurement for delivering high class testable and
maintainable software. Flexibility is a criterion of crucial significance to software developers, designers
and the quality controllers. It constantly guides and supports to avoid wastage of resources as well as
enable the designers for continuous improvement in the development process. Flexibility is concerned with
building high quality and reliable software within the constraints of cost and time. It greatly influences
cost, quality and reliability at software evolution process. Despite the fact flexibility is vital and highly
significant aspect for software development processes, it is poorly managed. This paper focuses the need
and importance of flexibility early at design phase. A model has been proposed for flexibility measurement
of object oriented design by establishing multiple linear regression. Finally the proposed model has been
validated using experimental tryout.
Modern gadgets and machines such as medical equipments, mobile phones, cars and even military hardware run on software. The operational efficiency and accuracy of these machines are critical to life and the well being of modern civilization. When the software powering these machines fail it exposes life to danger and can cause the failure of businesses. In this paper, software quality measure is presented with the emphasis on improving standard and controlling damages that may result from badly developed application. The research shows various software quality standards and quality metrics and how they can be applied. The application of the metrics in measuring software quality in the research produced results which shows that the code metrics performance is better than the design metrics performance and points to a new way of improving quality by refactoring application code instead of developing new designs. This is believed to ensure reusability and reduced failure rate when software is developed
Testability measurement model for object oriented design (tmmood)ijcsit
Measuring testability early in the development life cycle especially at design phase is a criterion of crucial importance to software designers, developers, quality controllers and practitioners. However, most of the
mechanism available for testability measurement may be used in the later phases of development life cycle.
Early estimation of testability, absolutely at design phase helps designers to improve their designs before
the coding starts. Practitioners regularly advocate that testability should be planned early in design phase.
Testability measurement early in design phase is greatly emphasized in this study; hence, considered significant for the delivery of quality software. As a result, it extensively reduces rework during and after implementation, as well as facilitate for design effective test plans, better project and resource planning in a practical manner, with a focus on the design phase. An effort has been put forth in this paper to recognize the key factors contributing in testability measurement at design phase. Additionally, testability
measurement model is developed to quantify software testability at design phase. Furthermore, the relationship of Testability with these factors has been tested and justified with the help of statistical measures. The developed model has been validated using experimental tryout. Finally, it incorporates the empirical validation of the testability measurement model as the author’s most important contribution.
APPLYING CONTINUOUS INTEGRATION FOR INCREASING THE MAINTENANCE QUALITY AND EF...ijseajournal
In order to project resource management and time control, software system needs to be decomposed into
subsystems, functional modules and basis components. Finally, all tested components have to integrate to
be the complete system. Applying IID (Iterative Incremental Development) mechanism, agile development
model becomes the practical method to reduce software project failure rate. Continuous integration (CI) is
an IID implementation concept which can effectively reduce software development risk. Web app with high
change characteristic is suitable to use agile development model as the development and maintenance
methodology. The paper depth surveys CI operating environment and advantages. Introducing CI concept
can make up the moving target problems to impact of Web app. For this, the paper proposes a Continuous
Integration based Web Applications Maintenance Procedure (CIWAMP) to assist the system integration
operating. Based on CI characteristics, CIWAMP makes Web app can be deployed quickly, increase
stakeholder communication frequency, improve staff morale, and effectively reduce Web app maintenance
quality and efficiency
APPLYING CONTINUOUS INTEGRATION FOR INCREASING THE MAINTENANCE QUALITY AND EF...ijseajournal
In order to project resource management and time control, software system needs to be decomposed into subsystems, functional modules and basis components. Finally, all tested components have to integrate to be the complete system. Applying IID (Iterative Incremental Development) mechanism, agile development model becomes the practical method to reduce software project failure rate. Continuous integration (CI) is an IID implementation concept which can effectively reduce software development risk. Web app with high change characteristic is suitable to use agile development model as the development and maintenance methodology. The paper depth surveys CI operating environment and advantages. Introducing CI concept can make up the moving target problems to impact of Web app. For this, the paper proposes a Continuous
Integration based Web Applications Maintenance Procedure (CIWAMP) to assist the system integration operating. Based on CI characteristics, CIWAMP makes Web app can be deployed quickly, increase stakeholder communication frequency, improve staff morale, and effectively reduce Web app maintenance
quality and efficiency.
Software quality model based on development team characteristicsIJECEIAES
Many factors have a significant impact on producing high-quality software products. Development team members are among the most important factors. Paying attention to the quality from this perspective will be a good innovation in the software development industry. Given that team members play a very important role in software products, this study tries to focus specifically on team characteristics in software product quality and provide a qualitative model based on this. The required data were collected through observations and interviews with project managers and development team members in several companies under study. Then, data were analyzed through hierarchical analysis. According to the results, the use of this model led to the improvement of the software development process so that the team members were satisfied with it. Also, time management was improved, and the customer expressed his satisfaction with the use of this model. Finally, data analysis showed that this model may lead to faster product delivery.
A comparative studies of software quality model for the software product eval...imdurgesh
Actually, software products are increasing in a fast way and are used in almost all activities of human life.
Consequently measuring and evaluating the quality of a software product has become a critical task for many companies.
Several models have been proposed to help diverse types of users with quality issues. The development of techniques for
building software has influenced the creation of models to assess the quality. Since 2000 the construction of software
started to depend on generated or manufactured components and gave rise to new challenges in assessing quality.
These components introduce new concepts such as configurability, reusability, availability, better quality and lower cost.
Consequently, the models are classified into basic models which were developed until 2000, and those based on
components called tailored quality models. The purpose of this article is to describe the main models with their strengths
and point out some deficiencies. In this work, we conclude that in the present age, aspects of communications play an
important factor in the quality of the software.
A study of various viewpoints and aspects software quality perspectiveeSAT Journals
Abstract The software quality is very important research of software engineering grown from the last two decades. The software engineering paradigm adopted by many organizations to develop the high quality software at affordable cost. The high quality software is considered as one of the key factor in the rapid growth of Global Software Development. The software metrics computes and evaluates the quality characteristics and used to take quantitative and qualitative decisions for risk assessment and reduction. The multiple stakeholders can view the software quality in multiple angles with various aspects. In this paper we present multiple views of the software quality with respect to various quality aspects. Key Words : Stakeholders, Functional aspect, Structural aspect, Process aspect, Metrics etc.
STRATEGIES TO REDUCE REWORK IN SOFTWARE DEVELOPMENT ON AN ORGANISATION IN MAU...ijseajournal
Rework is a known vicious circle in software development since it plays a central role in the generation of
delays, extra costs and diverse risks introduced after software delivery. It eventually triggers a negative
impact on the quality of the software developed. In order to cater the rework issue, this paper goes in depth
with the notion of rework in software development as it occurs in practice by analysing a development
process on an organisation in Mauritius where rework is a major issue. Meticulous strategies to reduce
rework are then analysed and discussed. The paper ultimately leads to the recommendation of the best
strategy that is software configuration management to reduce the rework problem in software development
A maintainability enhancement procedureijseajournal
In mobile communications age, environment changes rapidly, the requirements change is the software
project must face challenge. Able to overcome the impact of requirements change, software development
risk can be effectively decreased. In order to reduce software requirements change risk, the paper
investigates the major software development models and recommends the adaptable requirements change
software development. Agile development applied the Iterative and Incremental Development (IID)
approach, focuses on workable software and client communication. In software development, agile
development is a very suitable approach to handle the requirements change. However, agile development
maintenance existed many defects that include development documents control, user story inspection and
CM system. The maintenance defects of agile development should be improved. Analysing and collecting
the critical quality factors of agile development maintainability, in this paper proposes the Agile
Development Maintainability Measurement (ADMM) model. Based on ADMM model, the Agile
Development Maintainability Enhancement (ADME) procedure can be defined and deployed for reducing
the risk of requirements change.
A reliability estimation framework for OO design complexity perspective has been developed inthis paper. The proposed framework correlates the object oriented design constructs with complexity and also correlates complexity with reliability. No such framework has been available in the literature that estimates software reliability of OO design by taking complexity into consideration. The framework bridges the gap between object oriented design constructs, complexity and reliability. Framework measures and minimizes the complexity of software design at the early stage of software development life cycle leading to a reliable end product. Reliability and complexity estimation models have been proposed by following the proposed framework. Complexity estimation model has been developed which takes OO design constructs into consideration and proposed reliability estimation models take complexity in consideration for estimating reliability of OO design.
DESQA a Software Quality Assurance FrameworkIJERA Editor
In current software development lifecycles of heterogeneous environments, the pitfalls businesses have to face are that software defect tracking, measurements and quality assurance do not start early enough in the development process. In fact the cost of fixing a defect in a production environment is much higher than in the initial phases of the Software Development Life Cycle (SDLC) which is particularly true for Service Oriented Architecture (SOA). Thus the aim of this study is to develop a new framework for defect tracking and detection and quality estimation for early stages particularly for the design stage of the SDLC. Part of the objectives of this work is to conceptualize, borrow and customize from known frameworks, such as object-oriented programming to build a solid framework using automated rule based intelligent mechanisms to detect and classify defects in software design of SOA. The implementation part demonstrated how the framework can predict the quality level of the designed software. The results showed a good level of quality estimation can be achieved based on the number of design attributes, the number of quality attributes and the number of SOA Design Defects. Assessment shows that metrics provide guidelines to indicate the progress that a software system has made and the quality of design. Using these guidelines, we can develop more usable and maintainable software systems to fulfill the demand of efficient systems for software applications. Another valuable result coming from this study is that developers are trying to keep backwards compatibility when they introduce new functionality. Sometimes, in the same newly-introduced elements developers perform necessary breaking changes in future versions. In that way they give time to their clients to adapt their systems. This is a very valuable practice for the developers because they have more time to assess the quality of their software before releasing it. Other improvements in this research include investigation of other design attributes and SOA Design Defects which can be computed in extending the tests we performed.
Similar to EMPIRICALLY VALIDATED SIMPLICITY EVALUATION MODEL FOR OBJECT ORIENTED SOFTWARE (20)
TROUBLESHOOTING 9 TYPES OF OUTOFMEMORYERRORTier1 app
Even though at surface level ‘java.lang.OutOfMemoryError’ appears as one single error; underlyingly there are 9 types of OutOfMemoryError. Each type of OutOfMemoryError has different causes, diagnosis approaches and solutions. This session equips you with the knowledge, tools, and techniques needed to troubleshoot and conquer OutOfMemoryError in all its forms, ensuring smoother, more efficient Java applications.
top nidhi software solution freedownloadvrstrong314
This presentation emphasizes the importance of data security and legal compliance for Nidhi companies in India. It highlights how online Nidhi software solutions, like Vector Nidhi Software, offer advanced features tailored to these needs. Key aspects include encryption, access controls, and audit trails to ensure data security. The software complies with regulatory guidelines from the MCA and RBI and adheres to Nidhi Rules, 2014. With customizable, user-friendly interfaces and real-time features, these Nidhi software solutions enhance efficiency, support growth, and provide exceptional member services. The presentation concludes with contact information for further inquiries.
First Steps with Globus Compute Multi-User EndpointsGlobus
In this presentation we will share our experiences around getting started with the Globus Compute multi-user endpoint. Working with the Pharmacology group at the University of Auckland, we have previously written an application using Globus Compute that can offload computationally expensive steps in the researcher's workflows, which they wish to manage from their familiar Windows environments, onto the NeSI (New Zealand eScience Infrastructure) cluster. Some of the challenges we have encountered were that each researcher had to set up and manage their own single-user globus compute endpoint and that the workloads had varying resource requirements (CPUs, memory and wall time) between different runs. We hope that the multi-user endpoint will help to address these challenges and share an update on our progress here.
Large Language Models and the End of ProgrammingMatt Welsh
Talk by Matt Welsh at Craft Conference 2024 on the impact that Large Language Models will have on the future of software development. In this talk, I discuss the ways in which LLMs will impact the software industry, from replacing human software developers with AI, to replacing conventional software with models that perform reasoning, computation, and problem-solving.
Navigating the Metaverse: A Journey into Virtual Evolution"Donna Lenk
Join us for an exploration of the Metaverse's evolution, where innovation meets imagination. Discover new dimensions of virtual events, engage with thought-provoking discussions, and witness the transformative power of digital realms."
OpenFOAM solver for Helmholtz equation, helmholtzFoam / helmholtzBubbleFoamtakuyayamamoto1800
In this slide, we show the simulation example and the way to compile this solver.
In this solver, the Helmholtz equation can be solved by helmholtzFoam. Also, the Helmholtz equation with uniformly dispersed bubbles can be simulated by helmholtzBubbleFoam.
Custom Healthcare Software for Managing Chronic Conditions and Remote Patient...Mind IT Systems
Healthcare providers often struggle with the complexities of chronic conditions and remote patient monitoring, as each patient requires personalized care and ongoing monitoring. Off-the-shelf solutions may not meet these diverse needs, leading to inefficiencies and gaps in care. It’s here, custom healthcare software offers a tailored solution, ensuring improved care and effectiveness.
In 2015, I used to write extensions for Joomla, WordPress, phpBB3, etc and I ...Juraj Vysvader
In 2015, I used to write extensions for Joomla, WordPress, phpBB3, etc and I didn't get rich from it but it did have 63K downloads (powered possible tens of thousands of websites).
Enhancing Research Orchestration Capabilities at ORNL.pdfGlobus
Cross-facility research orchestration comes with ever-changing constraints regarding the availability and suitability of various compute and data resources. In short, a flexible data and processing fabric is needed to enable the dynamic redirection of data and compute tasks throughout the lifecycle of an experiment. In this talk, we illustrate how we easily leveraged Globus services to instrument the ACE research testbed at the Oak Ridge Leadership Computing Facility with flexible data and task orchestration capabilities.
Innovating Inference - Remote Triggering of Large Language Models on HPC Clus...Globus
Large Language Models (LLMs) are currently the center of attention in the tech world, particularly for their potential to advance research. In this presentation, we'll explore a straightforward and effective method for quickly initiating inference runs on supercomputers using the vLLM tool with Globus Compute, specifically on the Polaris system at ALCF. We'll begin by briefly discussing the popularity and applications of LLMs in various fields. Following this, we will introduce the vLLM tool, and explain how it integrates with Globus Compute to efficiently manage LLM operations on Polaris. Attendees will learn the practical aspects of setting up and remotely triggering LLMs from local machines, focusing on ease of use and efficiency. This talk is ideal for researchers and practitioners looking to leverage the power of LLMs in their work, offering a clear guide to harnessing supercomputing resources for quick and effective LLM inference.
Enhancing Project Management Efficiency_ Leveraging AI Tools like ChatGPT.pdfJay Das
With the advent of artificial intelligence or AI tools, project management processes are undergoing a transformative shift. By using tools like ChatGPT, and Bard organizations can empower their leaders and managers to plan, execute, and monitor projects more effectively.
Software Engineering, Software Consulting, Tech Lead.
Spring Boot, Spring Cloud, Spring Core, Spring JDBC, Spring Security,
Spring Transaction, Spring MVC,
Log4j, REST/SOAP WEB-SERVICES.
Providing Globus Services to Users of JASMIN for Environmental Data AnalysisGlobus
JASMIN is the UK’s high-performance data analysis platform for environmental science, operated by STFC on behalf of the UK Natural Environment Research Council (NERC). In addition to its role in hosting the CEDA Archive (NERC’s long-term repository for climate, atmospheric science & Earth observation data in the UK), JASMIN provides a collaborative platform to a community of around 2,000 scientists in the UK and beyond, providing nearly 400 environmental science projects with working space, compute resources and tools to facilitate their work. High-performance data transfer into and out of JASMIN has always been a key feature, with many scientists bringing model outputs from supercomputers elsewhere in the UK, to analyse against observational or other model data in the CEDA Archive. A growing number of JASMIN users are now realising the benefits of using the Globus service to provide reliable and efficient data movement and other tasks in this and other contexts. Further use cases involve long-distance (intercontinental) transfers to and from JASMIN, and collecting results from a mobile atmospheric radar system, pushing data to JASMIN via a lightweight Globus deployment. We provide details of how Globus fits into our current infrastructure, our experience of the recent migration to GCSv5.4, and of our interest in developing use of the wider ecosystem of Globus services for the benefit of our user community.
Check out the webinar slides to learn more about how XfilesPro transforms Salesforce document management by leveraging its world-class applications. For more details, please connect with sales@xfilespro.com
If you want to watch the on-demand webinar, please click here: https://www.xfilespro.com/webinars/salesforce-document-management-2-0-smarter-faster-better/
Unleash Unlimited Potential with One-Time Purchase
BoxLang is more than just a language; it's a community. By choosing a Visionary License, you're not just investing in your success, you're actively contributing to the ongoing development and support of BoxLang.
Listen to the keynote address and hear about the latest developments from Rachana Ananthakrishnan and Ian Foster who review the updates to the Globus Platform and Service, and the relevance of Globus to the scientific community as an automation platform to accelerate scientific discovery.
Field Employee Tracking System| MiTrack App| Best Employee Tracking Solution|...informapgpstrackings
Keep tabs on your field staff effortlessly with Informap Technology Centre LLC. Real-time tracking, task assignment, and smart features for efficient management. Request a live demo today!
For more details, visit us : https://informapuae.com/field-staff-tracking/
Field Employee Tracking System| MiTrack App| Best Employee Tracking Solution|...
EMPIRICALLY VALIDATED SIMPLICITY EVALUATION MODEL FOR OBJECT ORIENTED SOFTWARE
1. International Journal of Software Engineering & Applications (IJSEA), Vol.9, No.6, November 2018
DOI:10.5121/ijsea.2018.9606 71
EMPIRICALLY VALIDATED SIMPLICITY
EVALUATION MODEL FOR OBJECT ORIENTED
SOFTWARE
Dr. Abdullah1
and Dr. Mahfuzul Huda2
1
Assistant Professor, Adigrat University, Adigrat- Tigray, Ethiopia-Africa.
2
Assistant Professor, Saudi Electronic University, Riyadh -Saudi Arabia
ABSTRACT
Software program developers need to go from beginning to ending and understand source code of the
program and other software attributes. The software complexities and length of the program exceedingly
affects many design level quality attributes, specifically Simplicity, Testability and software
Maintainability. Incomplete design of any software generally leads to misunderstanding and ambiguities
and therefore to gives faulty design and development results. This is mainly seeming and appears owing to
the absence of it’s an appropriate observation, design and development control. However, high level design
and program simplicity are very necessary and one of the vital attributes of the system development cycle.
This research paper highlights the impact and significance of design level software simplicity in common
and as a one of the most useful key factor or index of software quality assurance and testing. In this
research work principally there are three major efforts are made. As a first contribution, a valuable
relationship between software design quality factor simplicity and related object oriented design
properties, this has been set up. In the second contribution, using design level corresponding metrics a
simplicity evaluation model for object oriented software is developed. Subsequently, the developed
simplicity model has been rationally authenticated by means of experimental data try-out.
KEYWORDS
Simplicity, Reliability, Maintainability, Testability, Portability, Flexibility, Object Oriented Software.
1. INTRODUCTION
To timely fulfill the continuing changing demands and the requirements of users and the customer
or may be some additional reasons, developed software must want to be proper renovated or
altered on or after time to time. This procedure of maintenance or modification is generally
worked out by current/existing programmers and developers, which might be not have built that
previous application software [5]. They must require proper narrating and proper recognizing
source codes and additional associated credentials [21]. Yet for the program creators of the object
oriented design, next a break of not many years, it might not be always a simple or easy work for
them to understand original source programs and other associated design documents of the
program or the software [8, 22]. Incorrect interpretations and explanations can proceed to or
direct to misconceptions and finally to not acceptable delivered results [15]. Rundown of an
understanding and the capability to eloquent the procedures in use, it is not probable that it can be
enhanced [16, 23].
So, the ability to be understood and the design simplicity of software have many direct influences
on the criteria that indirectly or directly disturb quality of software. Complicated software design
assuredly direct to bad maintainability and testability results, which in go products to un
2. International Journal of Software Engineering & Applications (IJSEA), Vol.9, No.6, November 2018
72
successful maintenance and testing that may outcome to bad significances [9, 24]. It is unspoken
truth that defects of software design creation have a robust adverse effect on expected quality
attributes. Organizing a good quality complex design endures to be an inefficiently well-defined
procedure [10]. Hence, software implementation design and further development must be simple
as well as minimal complex, this minimizes the required development efforts for the unexpected
coming functional and operational extensions. Moreover, the design is alienated into functionally
separated and less interdependent modules of reasonable program size [25]. Finally, we can
achieve to build in this method so as to make them simply testable, maintainable, and possibly
stable [11, 14].
2. SOFTWARE QUALITY
In this segment, it discusses the contents of the following quality model for software: McCall
software quality model, Boehm software quality model, FURPS model, and finally Dromey
model. The McCall’s software quality method has focus on three (3) main value of software
application: Product Transition perspective (that is adaptableness to new platform setting) product
Revision perspective (The capability to go through proper changes) product Operations
perspective (Its operational characteristics).
McCall’s Quality Assurance Model contains 11 software quality factors and twenty-three quality
criteria [3]. Where the quality criteria define disparate kinds of software properties and software
quality criterions are valuable characteristics to single or supplementary of the software quality
factors. Boehm’s quality model works to qualitatively evaluation of the quality of software [1, 7].
The high level factors address three classifications; maintainability, portability and general utility
into as utility. In the intermediate level criteria, Boehm quality model has seven quality factors
like reliability, portability, Usability, efficiency, Human engineering, understandability,
flexibility. Dromey’s software quality model proposed a complete framework to evaluate the
phases of requirement, design and implementation [12]. The high level design properties for the
Dromey’s implementation software quality model that include: internal, correctness, descriptive
and contextual.
Furps quality model [13] formerly presented by quality expert Grady [9], then it is extended by
IBM Software (Rational) into FURPS+. Where the ‘+’ indicates such requirements as design
constraints, requirements, implementation, physical requirements and interface requirements.
There are mainly four characteristics in FURPS quality model. The quality factors and features of
the software in the FURPS quality mode clearly indicated under ISO 9000 and stated as “they
provide crystal clear implementation guidelines for product quality assurance [17]. ISO 9000 is a
process or procedure oriented approach for software quality management [19]. It processes
designing, implementing, documenting, monitoring, supporting, improving and controlling.
Recently, the ISO/IEC 9126-1: 2001 product quality model of software, which defined mainly six
quality factors, has replaced by software product quality model and ISO/IEC 205010:2011 system
[20]. The ISO 25010 is the widely used quality standard model now a day. ISO 25010 uses ten
main quality factors: operability, Functional, suitability, reliability, security, efficiency,
performance, compatibility, maintainability, and portability. The given 28 software quality
features are arranged and given under the basis of major six quality criteria [20].
3. SOFTWARE SIMPLICITY
When you genuinely discuss about software design simplicity, means you want to approve and
validate of it because it reduced complicated details [18]. Simplicity tends to promote ease of
testing and maintenance. Software simplicity is one of the most noteworthy quality factor for any
type of system design and development. Designing a simple system is time consuming. It will
3. International Journal of Software Engineering & Applications (IJSEA), Vol.9, No.6, November 2018
73
have significant impact with the architecture level. It is crucial and challenging task that a product
design shows reduced complexity and remains as simple design as possible while developer still
being able to meet the needs of the requirements and services. Product’s systems designs grow
and it becomes more challenging and giving complex looks over the time. Eventually starting
with a software system’s design that is already getting complex means starting with at
disadvantages. The more complex the system leads to the more difficult it is to have a
comprehensive and an accurate model. An excessively complex design of a system results in a
condition where no single user can understand it all at any one time.
The software or program quality factor describes dissimilar kinds of crucial system properties,
whether software quality criteria are mainly attributes to single or supplementary of the quality
factor. The quality model presented by Boehm try to attempts qualitatively assessment of the
excellence of software. The high level software characteristics explain three important
classifications; maintainability, portability and general explanation into as utility. Where at the
intermediate level properties, the Boehm’s design product quality model described seven
important features of the quality factors like as efficiency portability, Usability, flexibility,
Human engineering, reliability, understandability, [2]. Table 1 is denoted as the software quality
factors and quality-criteria of Boehm quality-mode.
4. SIMPLICITY QUALITY CRITERIA AND RELATED FACTORS
Quality criteria are the characteristics which properly define the quality factor. The software
quality criteria for the related factors are the characteristics of the software creation process or
software product by which the factor can be defined. The relationships amid the simplicity quality
factors between the related crucial criteria can be seen in Table 1.
Table1. Criteria of Simplicity Quality-Factors [1, 27, 28, 29, 30, 31]
Criterion
Definition Related Factors
Simplicity
Those attributes or the factors of the
program or the software that gives
implementation of functions in the most
understandable manner.
• Reliability
• Maintainability
• Testability
• Portability
• Flexibility
5. ESTABLISHING RELATION BETWEEN DESIGN PROPERTIES AND
SIMPLICITY FACTORS
Figure1: Mapping between Design Properties and Simplicity Factors
4. International Journal of Software Engineering & Applications (IJSEA), Vol.9, No.6, November 2018
74
6. MODEL DEVELOPMENT FOR SIMPLICITY EVALUATION OF OBJECT
ORIENTED SOFTWARE
In direction to create Simplicity evaluation model for object oriented software, “Multivariate
Linear Regression System” has been applied, that is specified as given below.
Z=b0+ b1 x1+ b2 x2+ b3 x3……bn xn Eq. (1)
Simplicity= b0+ b1 x Encapsulation+ b2 x Coupling+ b3 x Inheritance + b4 x Polymorphism
Eq. (2)
The data set accustomed for creating simplicity evaluation model for object oriented software is
occupied from [26] that have been collected through the measured experimentation. It includes a
group of 20 object oriented design class diagrams (symbolized as P1 to P20) and the associated
metrics value of respective class diagram. Moreover, the mean value of the specialist’s score of
simplicity of these class diagrams is also given and labeled as ‘Known Values’ in this research
work. The association amid simplicity factor and program design properties has been recognized
as represented in figure one. Using SPSS, respective value of each coefficients is decided and
simplicity evaluation model is articulated as given below.
Simplicity= 4.741 -.686 x Encapsulation -1.843 x Coupling + .334 x Inheritance +
2.841 x Polymorphism Eq. (3)
Table 2 shows the coefficients for Simplicity evaluation model. The Unstandardized coefficients
component of the table 2 gives us the values that we require in order to develop the regression
equation (2). The experimental assessment of Simplicity is very hopeful to get simplicity index of
object oriented design for low cost software maintenance.
Table 2: Coefficients for Simplicity Evaluation Model
6.1. SIMPLICITY MODEL SUMMARY
The model summary table 3 results are very helpful when writing multiple regressions. Capital
(R), is the coefficient determinant that tells us how powerfully the all independent-variables are
associated to the respective dependent- variable. The value of “R Square” is also very
encouraging as it gives us the coefficient determination.
5. International Journal of Software Engineering & Applications (IJSEA), Vol.9, No.6, November 2018
75
Table 3: Simplicity Evaluation Model Summary
7. INVESTIGATIONAL TRYOUT
No problem, in what way powerful a hypothetical conclusion may be, it has to be experimentally
authenticated if it is functioning to be of any real-world use [6]. This is real in all engineering
systems, counting software engineering. Hence, in adding to the hypothetical or theoretical
authentication, an investigational and experimental test is similarly significant in directive to
make the claim additional adaptable. In assessment of this truth, an investigational authentication
of the developed simplicity evaluation model (equation 2) has been performed by the assistance
of design level metrics specified in the data set [26]. Summary of the values obtained by the
developed model against the ‘Known Values’ of simplicity are given in Table 4.
Spearman’s rank correlation coefficient (rs) used to get the association among values of
simplicity nature of a design using developed model and it’s given values. The ‘rs’ was calculated
by the method specified as under:
Rank Relation (rs) –
‘d’ = Variance amongst, Computed Rank and Known Rank of Simplicity
‘n’ = Quantity of all projects used in the experimentation.
Table 4: Simplicity Index Values
Projects
Detail
Projects Known
Values
Obtained Values Using Developed
Simplicity Model
P-11 7.0 5.54
P-12 8.3 3.92
P-13 7.9 4.56
P-14 8.6 7.75
P-15 9.6 7.90
P-16 7.4 4.31
P-17 8.5 6.91
P-18 6.9 2.40
P-19 9.3 6.24
P-20 6.8 2.69
Spearman’s Rank Correlation Coefficient (rs = 0.84242) computed for the developed model is
more than the threshold value for n=10. This displays that the values of simplicity model
calculated using proposed model are extremely associated with the ‘Given Values’.
Consequently, the association is satisfactory with the high level of confidence, i.e. at the 0.05.
The correlation is up to standard with high level of justification i.e. at the 95%. Hence, short of
6. International Journal of Software Engineering & Applications (IJSEA), Vol.9, No.6, November 2018
76
any damage of oversimplification our study can accomplish that simplicity evaluation model (in
eq. 2) calculations are consistent and effective in the viewpoint.
8. CONCLUSION AND FUTURE RESEARCH DIRECTION
This research work shows the importance of simplicity and its correlation with object oriented
design properties viz. Encapsulation, Coupling, Inheritance and Polymorphism. Further, research
study developed a simplicity evaluation model SEMOOD with the assistance of multiple linear
regression method on object oriented design properties. Statistical result confirms that simplicity
evaluation model is extremely significant and up to standard. The perfect validation on the
simplicity model it is to be completed in future on live industrial projects for improved suitability
and usefulness. Software simplicity is dynamic and one of the greatest noteworthy parts of the
software development life cycle nowadays. Above described five quality attributes, have
numerous highlighted properties in shared, in counting low level coupling, modularity and high
level cohesion. Design level Simplicity is directly boosted software Reliability, Flexibility,
Testability, Maintainability and Portability. Simplicity of the software when combined with
design quality attributes and criteria supports to develop project with less development and
further maintenance cost in the minimum time and framework, as well as improve acceptable
consistency and better reliability of the final delivered software. Still, the proposed research work
wants to be more investigational tryout with a bigger set of data for better level of acceptability
and utility.
REFERENCES
[1] Boehm BW, Brow JR, Lipow M, McLeod G, Merritt M. Characteristics of software quality. North
Holland Publishing. Amsterdam, the Netherlands; 1978.
[2] Abdullah, Dr, M. H. Khan, and Reena Srivastava. “Flexibility: A Key Factor To Testability”,
International Journal of Software Engineering & Applications (IJSEA), Vol.6, No.1, January 2015.
DOI: 10.5121/ijsea.2015.6108.
[3] McCall JA, Richards PK, Walters GF. Factors in software quality, RADC TR-77-369: 1977. (Rome:
Rome Air Development Center)
[4] Huda, M., Arya, Y.D.S. and Khan, M.H. (2015) Evaluating Effectiveness Factor of Object Oriented
Design: A Testability Perspective. International Journal of Software Engineering & Applications
(IJSEA), 6, 41-49. http://dx.doi.org/10.5121/ijsea.2015.6104
[5] Huda, M., Arya, Y.D.S. and Khan, M.H. (2015) Metric Based Testability Estimation Model for
Object Oriented Design: Quality Perspective. Journal of Software Engineering and Applications, 8,
234-243. http://dx.doi.org/10.4236/jsea.2015.84024
[6] Abdullah, Dr, Reena Srivastava, and M. H. Khan. "Testability Measurement Framework: Design
Phase Perspective”. International Journal of Advanced Research in Computer and Communication
Engineering, Vol. 3, Issue 11, Pages 8573- 8576 November 2014.
[7] Boehm BW, Brown JR, Lipow M. Quantitative evaluation of software quality, In Proceeding of the
2nd International Conference on Software engineering. 1976;592605.
[8] Abdullah, Dr, M. H. Khan, and Reena Srivastava. “Testability Measurement Model for Object
Oriented Design (TMMOOD)”. International Journal of Computer Science & Information
Technology (IJCSIT), Vol. 7, No 1, February 2015, DOI: 10.5121/ijcsit.2015.7115.
[9] Grady, RB. Practical software metrics for project management and process improvement, Prentice
Hall; 1992.
7. International Journal of Software Engineering & Applications (IJSEA), Vol.9, No.6, November 2018
77
[10] Huda, M., Arya, Y.D.S. and Khan, M.H. (2015) Quantifying Reusability of Object Oriented Design:
A Testability Perspective. Journal of Software Engineering and Applications, 8, 175-183.
http://dx.doi.org/10.4236/jsea.2015.84018
[11] Abdullah, Dr, Reena Srivastava, and M. H. Khan. “Modifiability: A Key Factor To Testability”,
International Journal of Advanced Information Science and Technology, Vol. 26, No.26, Pages 62-
71 June 2014.
[12] Dromey RG. Concerning the Chimera (software quality). IEEE Software. 1996;1:3343.
[13] Jacobson I, Booch G, Rumbaugh J. The unified software development process, Addison Wesley;
1999.
[14] Drown DJ, Khoshgoftaar TM, Seiya N. Evaluation any sampling and software quality model of high
assurance systems, IEEE Transaction on systems, Mean and Cybernetics, Part A: Systems and
Human. 2009;39(5):1097-1107.
[15] Abdullah, Dr, Reena Srivastava, and M. H. Khan. "Testability Estimation of Object Oriented Design:
A Revisit". International Journal of Advanced Research in Computer and Communication
Engineering, Vol. 2, Issue 8, pages 3086-3090, August 2013.
[16] Tomar AB, Thakare VM. A systematic study of software quality models, International Journal of
software engineering & application. 2011;12(4):61-70.
[17] ISO 9001:2005, Quality management system Fundamentals and vocabulary; 2005.
[18] Huda, M., Arya, Y.D.S. and Khan, M.H. (2014) Measuring Testability of Object Oriented Design: A
Systematic Review. International Journal of Scientific Engineering and Technology (IJSET), 3,
1313-1319.
[19] ISO 9001:2001, Quality management system Requirements; 2001.
[20] ISO /IEC25010: Software engineering– system and software quality requirement and evaluation
(SQuaRE)- system and software quality model; 2011.
[21] Huda, M., Arya, Y.D.S. and Khan, M.H. (2015) Testability Quantification Framework of Object
Oriented Software: A New Perspective. International Journal of Advanced Research in Computer
and Communication Engineering, 4, 298- 302. http://dx.doi.org/10.17148/IJARCCE.2015.4168
[22] McCable TJ. A complexity measure, IEEE Transaction on Software Engineering, 1976; SE-
2(4):308-320.
[23] Kemerer CF. An empirical validation of software code estimation models, Communications of the
ACM. 2008;30(5):416-429.
[22] Basili VR, Weiss DM. A methodology for collecting valid software engineering data, IEEE
Transactions on Software Engineering. 1984;SE-10:728-738.
[25] Pandian CR. Software metrics – A guide to planning, Analysis, and Application, CRC press
Company; 2004.
[26] MoboDexter Software India Pvt. Ltd., Novel Tech Park, Third Floor, #43/4, GB playa, Hosur Road
Bangalore
[27] Tomar AB, Thakare VM. A systematic study of software quality models, International
Journal of software engineering & application. 2011;12(4):61-70.
8. International Journal of Software Engineering & Applications (IJSEA), Vol.9, No.6, November 2018
78
[28] Boehm BW, Brow JR, Lipow M, McLeod G, Merritt M. Characteristics of software quality. North
Holland Publishing. Amsterdam, the Netherlands; 1978.
[29] Dromey RG. A model for software product quality. IEEE Transaction on Software
Engineering. 1995;21:146-162.
[30] ISO /IEC25010: Software engineering– system and software quality requirement and
evaluation (SQuaRE)- system and software quality model; 2011.
[31] Lee, Ming-Chang. "Software Quality Factors and Software Quality Metrics to Enhance Software
Quality Assurance." British Journal of Applied Science & Technology 4.21 (2014).
AUTHORS
Dr. Abdullah, Assistant Professor, Department of Information Technology,
Adigrat University, Ethiopia (Africa). Dr. Abdullah did MCA from UP
Technical University & Ph.D. (Computer Applications) from BBD University,
Lucknow India. He has more than Twelve Years of Teaching and Research
experience as an Associate Professor / Assistant Professor/ Lecturer in reputed
Universities of India and Foreign/Abroad.Dr. Abdullah has written Three Books
and sixteen study materials for different Indian Government and Private
Universities published numerous articles, several research papers in the National
and International refereed Journals and conference proceedings. His published
research work cited and accepted by lot of academicians and researchers across the world and published
research papers got 76 Google Scholar citations. His areas of expertise are Software Quality Assurance,
Software Testing, Object Oriented Design and Development. He has around Twelve Years of Teaching and
Research experience in India and Abroad. He has contributed a lot in academics & research in the form of
delivering lectures, research supervision and curriculum developments. He has also organized Seminars,
National & International Conferences. He is a Reviewer and Editorial Board member of various national
and International research journals as well as professional bodies.
Dr. Mahfuzul Huda currently working as Assistant Professor in the department
of Computer Science & Engineering, Saudi Electronic University, Kingdom of
Saudi Arabia. He has more than ten years of core teaching experience. Dr. Huda
has credible contribution in research work. His research papers accepted and
appreciated by various researchers across the world and his published research
papers got 66 Google Scholar citations with h-index: 5 & i10-index: 3, in a very
short span of time. Subsequently, he has guided more than 50 students for
academic projects and seminars and attended more than 30 seminars and
workshops related to academic work.