The current technology tend leads us to recognize the need for adaptive guidance process for all process of
software development. The new needs generated by the mobility context for software development led these
guidance processes to be adapted. In order to improve the performance of the deployed software
development, it is useful to manage the configuration of its evolving aspects. This paper deals with the
configuration management of guidance process or its ability to be adapted to specific development
contexts. The proposed adaptive configuration Meta-model is worked out on the basis of a Y description
for adaptive guidance process. This description focuses on three dimensions defined by the
material/software platform, the adaptation form and provided guidance service. Each dimension considers
several factors to develop a coherent configuration strategy and provide automatically the appropriate
guidance process to a current development context.
Configuration of a Guidance Process for Software Process Modeling csandit
This document discusses the configuration of guidance processes for software process modeling. It proposes describing adaptive guidance processes in a "Y" structure with three dimensions: the development context, the adaptation form, and the provided guidance service. The development context considers the material/software platform, activity context, and developer profile. Adaptation forms include contextual, adaptive, and mixed guidance. Services include corrective, constructive, and automatic guidance. The document also presents a configuration management approach for guidance processes involving five interrelated elements: context description, guidance process, configuration basis, deployment cycle, and invocation basis. The goal is to automatically provide the most appropriate guidance process based on the current development context.
Process-Centred Functionality View of Software Configuration Management: A Co...theijes
The International Journal of Engineering & Science is aimed at providing a platform for researchers, engineers, scientists, or educators to publish their original research results, to exchange new ideas, to disseminate information in innovative designs, engineering experiences and technological skills. It is also the Journal's objective to promote engineering and technology education. All papers submitted to the Journal will be blind peer-reviewed. Only original articles will be published.
This paper deals with an adaptive guidance system for software processes. The aim is to define
an approach of process modeling with a recursive adaptation of the guidance. This one is
specifically adapted to the developer model through its role and its qualification, and in relation
to the activity model associated with the context of the activity in progress. This guidance system
is provided on the basis on the choice criteria like the suitable access mode, the assistance
function to be ensured and the object of assistance to be considered. The description of the suggested approach is done using the modeling formalism SPEM extended by new concepts and principles dedicated to the modeling of the adaptive guidance.
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
This document discusses approaches for organizing and leveraging past experience in project management. It describes how a large software company captures lessons learned from prior projects by systematically recording project data, deriving insights, and making them available to other projects. The key elements discussed for building organizational knowledge are collecting and organizing knowledge, making it available through systems like processes and a process database, and reusing it to improve new project execution.
Can “Feature” be used to Model the Changing Access Control Policies? IJORCS
Access control policies [ACPs] regulate the access to data and resources in information systems. These ACPs are framed from the functional requirements and the Organizational security & privacy policies. It was found to be beneficial, when the ACPs are included in the early phases of the software development leading to secure development of information systems. Many approaches are available for including the ACPs in requirements and design phase. They relied on UML artifacts, Aspects and also Feature for this purpose. But the earlier modeling approaches are limited in expressing the evolving ACPs due to organizational policy changes and business process modifications. In this paper, we analyze, whether “Feature”- defined as an increment in program functionality can be used as a modeling entity to represent the Evolving Access control requirements. We discuss the two prominent approaches that use Feature in modeling ACPs. Also we have a comparative analysis to find the suitability of Features in the context of changing ACPs. We conclude with our findings and provide directions for further research.
A Fuzzy Expert System for Maturity Assessment based on OPM3IDES Editor
Despite of increasing interest of researchers to
issues related to maturity and specially the role of
organizational maturity and its impact on OPM3 there is not
enough studies about maturity level measurement. The
purpose of this research is maturity assessment of OPM3 of
organizations by an intelligent system. Here, a Fuzzy Expert
System has been designed with considering main effective
variables on maturity assessment as Inputs variables and level
of maturity as output. Then, the system rules have been
extracted from some experts and the system has been
developed with the use of FIS tool of MATLAB software.
Finally, the presented steps have been run in an IT company
as empirical study.
Selenium - A Trending Automation Testing Toolijtsrd
Selenium is an important testing tool for software quality assurance. In recent days number of websites are increasing rapidly and it becomes essential to test the websites against various quality factors to make sure it meets the expected quality goals. Several companies are spending a lot of bucks for the testing tool while Selenium is available completely free for the performance test. The open source tool is well known for its unlimited capabilities and unlimited reach. Selenium stands out from the crowd in this aspect. Anyone could visit the Selenium website and download the latest version and use it. It is not only an open source but also highly modifiable. Testers could make changes based upon their needs and requirements. Manav Kundra "Selenium - A Trending Automation Testing Tool" Published in International Journal of Trend in Scientific Research and Development (ijtsrd), ISSN: 2456-6470, Volume-4 | Issue-4 , June 2020, URL: https://www.ijtsrd.com/papers/ijtsrd31202.pdf Paper Url :https://www.ijtsrd.com/engineering/software-engineering/31202/selenium-%E2%80%93-a-trending-automation-testing-tool/manav-kundra
Configuration of a Guidance Process for Software Process Modeling csandit
This document discusses the configuration of guidance processes for software process modeling. It proposes describing adaptive guidance processes in a "Y" structure with three dimensions: the development context, the adaptation form, and the provided guidance service. The development context considers the material/software platform, activity context, and developer profile. Adaptation forms include contextual, adaptive, and mixed guidance. Services include corrective, constructive, and automatic guidance. The document also presents a configuration management approach for guidance processes involving five interrelated elements: context description, guidance process, configuration basis, deployment cycle, and invocation basis. The goal is to automatically provide the most appropriate guidance process based on the current development context.
Process-Centred Functionality View of Software Configuration Management: A Co...theijes
The International Journal of Engineering & Science is aimed at providing a platform for researchers, engineers, scientists, or educators to publish their original research results, to exchange new ideas, to disseminate information in innovative designs, engineering experiences and technological skills. It is also the Journal's objective to promote engineering and technology education. All papers submitted to the Journal will be blind peer-reviewed. Only original articles will be published.
This paper deals with an adaptive guidance system for software processes. The aim is to define
an approach of process modeling with a recursive adaptation of the guidance. This one is
specifically adapted to the developer model through its role and its qualification, and in relation
to the activity model associated with the context of the activity in progress. This guidance system
is provided on the basis on the choice criteria like the suitable access mode, the assistance
function to be ensured and the object of assistance to be considered. The description of the suggested approach is done using the modeling formalism SPEM extended by new concepts and principles dedicated to the modeling of the adaptive guidance.
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
This document discusses approaches for organizing and leveraging past experience in project management. It describes how a large software company captures lessons learned from prior projects by systematically recording project data, deriving insights, and making them available to other projects. The key elements discussed for building organizational knowledge are collecting and organizing knowledge, making it available through systems like processes and a process database, and reusing it to improve new project execution.
Can “Feature” be used to Model the Changing Access Control Policies? IJORCS
Access control policies [ACPs] regulate the access to data and resources in information systems. These ACPs are framed from the functional requirements and the Organizational security & privacy policies. It was found to be beneficial, when the ACPs are included in the early phases of the software development leading to secure development of information systems. Many approaches are available for including the ACPs in requirements and design phase. They relied on UML artifacts, Aspects and also Feature for this purpose. But the earlier modeling approaches are limited in expressing the evolving ACPs due to organizational policy changes and business process modifications. In this paper, we analyze, whether “Feature”- defined as an increment in program functionality can be used as a modeling entity to represent the Evolving Access control requirements. We discuss the two prominent approaches that use Feature in modeling ACPs. Also we have a comparative analysis to find the suitability of Features in the context of changing ACPs. We conclude with our findings and provide directions for further research.
A Fuzzy Expert System for Maturity Assessment based on OPM3IDES Editor
Despite of increasing interest of researchers to
issues related to maturity and specially the role of
organizational maturity and its impact on OPM3 there is not
enough studies about maturity level measurement. The
purpose of this research is maturity assessment of OPM3 of
organizations by an intelligent system. Here, a Fuzzy Expert
System has been designed with considering main effective
variables on maturity assessment as Inputs variables and level
of maturity as output. Then, the system rules have been
extracted from some experts and the system has been
developed with the use of FIS tool of MATLAB software.
Finally, the presented steps have been run in an IT company
as empirical study.
Selenium - A Trending Automation Testing Toolijtsrd
Selenium is an important testing tool for software quality assurance. In recent days number of websites are increasing rapidly and it becomes essential to test the websites against various quality factors to make sure it meets the expected quality goals. Several companies are spending a lot of bucks for the testing tool while Selenium is available completely free for the performance test. The open source tool is well known for its unlimited capabilities and unlimited reach. Selenium stands out from the crowd in this aspect. Anyone could visit the Selenium website and download the latest version and use it. It is not only an open source but also highly modifiable. Testers could make changes based upon their needs and requirements. Manav Kundra "Selenium - A Trending Automation Testing Tool" Published in International Journal of Trend in Scientific Research and Development (ijtsrd), ISSN: 2456-6470, Volume-4 | Issue-4 , June 2020, URL: https://www.ijtsrd.com/papers/ijtsrd31202.pdf Paper Url :https://www.ijtsrd.com/engineering/software-engineering/31202/selenium-%E2%80%93-a-trending-automation-testing-tool/manav-kundra
Working software measures the progress. Basically, Agile method involves interleaving the specification, implementation, design and testing. Series of versions are developed with the involvement of and evaluation by the stake holders in each version. Agile methods aim at reducing the software process overheads (like documentation) and concentrate more on code rather than the design. Customer involvement, incremental delivery, freedom of developers to evolve new working methods, change management, and last but not the least simplicity is the basic essence of Agile development. Agile methodologies are well suited for small as well as medium sized projects.
Assessment of cmm and its impact on software qualityIAEME Publication
The document discusses the Capability Maturity Model (CMM) and its impact on software quality. CMM provides guidance for software organizations to gain control of their processes and evolve toward excellence. It consists of 5 maturity levels, with each level comprised of key process areas that must be addressed to improve process capability. Achieving a higher maturity level indicates the organization is better able to manage projects and deliver high quality software. The document outlines the structure of CMM and describes the key process areas that define each maturity level. Overall CMM aims to help organizations implement disciplined, measured software development processes to continuously improve quality.
This document discusses tools and techniques for managing projects that encounter problems and become "red" or off-track. It provides two case studies of implementing Oracle ERP projects and discusses lessons learned. The objectives are to familiarize audiences with readily available tools to get projects back on schedule, such as enhanced communication, examining the "triple constraints," breaking projects into smaller phases, and reanalyzing and mitigating risks. Keywords include risk identification/mitigation and early warning signs of project issues.
AN APPROACH TO IMPROVEMENT THE USABILITY IN SOFTWARE PRODUCTSijseajournal
One of the significantaspects of software quality is usability. It is one of the characteristics that judge by
the success or failure of software applications. The most important risk facing the software applications is
usability which may lead to the existence of a gap between users and systems. This may lead to system
failure because of Poor design. This is due to the design is not based on the desires and requirements of the
customer. To overcome these problems, this paper proposed an approach to improve usability of software
applications to meet the needs of the customer and interacts with the user easily with an efficient and
effective manner.The proposed approach is based prototyping technique due to itssimplicity and it does not
require additional costs to elicit precise and complete requirement and design.
Evaluation of the software architecture styles from maintainability viewpointcsandit
In the process of software architecture design, different decisions are made that have systemwide
impact. An important decision of design stage is the selection of a suitable software
architecture style. Lack of investigation on the quantitative impact of architecture styles on
software quality attributes is the main problem in using such styles. So, the use of architecture
styles in designing is based on the intuition of software developers. The aim of this research is
to quantify the impacts of architecture styles on software maintainability. In this study,
architecture styles are evaluated based on coupling, complexity and cohesion metrics and
ranked by analytic hierarchy process from maintainability viewpoint. The main contribution of
this paper is quantification and ranking of software architecture styles from the perspective of
maintainability quality attribute at stage of architectural style selection.
Program analysis is useful for debugging, testing and maintenance of software systems due to information
about the structure and relationship of the program’s modules . In general, program analysis is performed
either based on control flow graph or dependence graph. However, in the case of aspect-oriented
programming (AOP), control flow graph (CFG) or dependence graph (DG) are not enough to model the
properties of Aspect-oriented (AO) programs. With respect to AO programs, although AOP is good for
modular representation and crosscutting concern, suitable model for program analysis is required to
gather information on its structure for the purpose of minimizing maintenance effort. In this paper Aspect
Oriented Dependence Flow Graph (AODFG) as an intermediate representation model is proposed to
represent the structure of aspect-oriented programs. AODFG is formed by merging the CFG and DG, thus
more information about dependencies between the join points, advice, aspects and their associated
construct with the flow of control from one statement to another are gathered. We discussthe performance
of AODFG by analysing some examples of AspectJ program taken from AspectJ Development Tools
(AJDT).
Lightweight processes are beginning to replace more formal methods. The motivation for this transition is based on many factors. The Internet, time to market, cost reduction, quality increases, market pressures, as well as the popularization of these programming methods. This series of articles will investigate the various lightweight methods, their impact on the management of software development projects and the processes by which managers can determine the appropriateness and usefulness of the various processes. The definition of a lightweight Process is more difficult than it would first appear. This article outlines the foundations of a heavyweight process and describes the appropriate pieces that can be converted to lightweight.
THE UNIFIED APPROACH FOR ORGANIZATIONAL NETWORK VULNERABILITY ASSESSMENTijseajournal
The present business network infrastructure is quickly varying with latest servers, services, connections,
and ports added often, at times day by day, and with a uncontrollably inflow of laptops, storage media and
wireless networks. With the increasing amount of vulnerabilities and exploits coupled with the recurrent
evolution of IT infrastructure, organizations at present require more numerous vulnerability assessments.
In this paper new approach the Unified process for Network vulnerability Assessments hereafter called as
a unified NVA is proposed for network vulnerability assessment derived from Unified Software
Development Process or Unified Process, it is a popular iterative and incremental software development
process framework.
Assessment of cmm and its impact on software qualityiaemedu
The document discusses the Capability Maturity Model (CMM) and its impact on software quality. It describes the five levels of the CMM and the key process areas within each level. The CMM is designed to help software organizations improve their processes by advancing through the maturity levels. Advancing to higher levels involves institutionalizing effective software engineering practices. The document also presents a problem statement about software projects facing cost overruns and quality issues. It reviews literature on the CMM and outlines a project conversion process framework to assess CMM implementation.
The document provides an overview of object-oriented technology and software engineering approaches. It describes the structured and object-oriented approaches, the roles of modeling, notation, process and techniques in software development. It also summarizes the Unified Modeling Language (UML), Unified Process, View Alignment techniques, and the Visual Paradigm for UML (VP-UML) CASE tool.
A Software System Development Life Cycle Model for Improved Students Communic...IJCSES Journal
This document describes a proposed software development life cycle (SDLC) model to improve student communication and collaboration. The model uses a spiral development process simulated using Simphony.NET. This allows the project manager to determine the optimal number of team members needed for each phase. The goal is to increase productivity by keeping all members busy at all times. Key aspects of the model include using Edmodo to create an online student learning network for communication and collaboration, dividing projects into small, medium, and large scales, and specifying time distributions for phases and resource needs.
THE USABILITY METRICS FOR USER EXPERIENCEvivatechijri
THE USABILITY METRICS FOR USER EXPERIENCE was innovatively created by Google engineers and it is ready for production in record time. The success of Google is to attributed the efficient search algorithm, and also to the underlying commodity hardware. As Google run number of application then Google’s goal became to build a vast storage network out of inexpensive commodity hardware. So Google create its own file system, named as THE USABILITY METRICS FOR USER EXPERIENCE that is GFS. THE USABILITY METRICS FOR USER EXPERIENCE is one of the largest file system in operation. Generally THE USABILITY METRICS FOR USER EXPERIENCE is a scalable distributed file system of large distributed data intensive apps. In the design phase of THE USABILITY METRICS FOR USER EXPERIENCE, in which the given stress includes component failures , files are huge and files are mutated by appending data. The entire file system is organized hierarchically in directories and identified by pathnames. The architecture comprises of multiple chunk servers, multiple clients and a single master. Files are divided into chunks, and that is the key design parameter. THE USABILITY METRICS FOR USER EXPERIENCE also uses leases and mutation order in their design to achieve atomicity and consistency. As of there fault tolerance, THE USABILITY METRICS FOR USER EXPERIENCE is highly available, replicas of chunk servers and master exists.
Majority of agile projects currently involve interactive user interface designs, which can only be possible by following UCD in agile software model. But the integration of UCD is not clear in the current agile models. Both Agile models and UCD have iterative nature but agile models focus on coding and development of software; whereas, UCD focuses on user interface of the software. Similarly, both of them have testing features where the agile model involves automated tested code while UCD involves an expert or a user to test the user interface. In this paper, a new agile usability model is presented and tested in companies and are presented. Key results from these projects clearly shows: the proposed agile model incorporates usability evaluation methods, improve the relationship between usability experts to work with agile software experts; in addition, allows agile developers to incorporate the result from UCD into subsequent interactions.
The document discusses project planning measures in the Capability Maturity Model Integration (CMMI). It applies the Goal Question Metric (GQM) approach to identify measures for the three specific goals and fourteen specific practices of the Project Planning process area in CMMI. The paper defines questions and measures related to each specific practice by following the three steps of GQM: defining goals, generating quantifiable questions, and defining measures to answer the questions. The identified measures are intended to help evaluate and control software products and processes.
Computer information project planning is one of the most important activities in the modern software
development process. Without an objective and realistic plan of software project, the development of
software process cannot be managed effectively. This research will identify general measures for the
specific goals and its specific practices of Project Planning Process Area in Capability Maturity Model
Integration (CMMI). CMMI is developed in USA by Software Engineering Institute (SEI) in Carnegie
Mellon University. CMMI is a framework for assessment and improvement of computer information
systems. The procedure we used to determine the measures is to apply the Goal Questions Metrics (GQM)
approach to the three specific goals and its fourteen specific practices of Project Planning Process Area in
CMMI.
A Review of Agent-Oriented Development Methodologies and Programming Language...Waqas Tariq
Agents are software systems and can be associated with an entity, framework, architecture and even languages. They are piece of program codes that are able to autonomously complete tasks. Before developing an agent, methodology to be used in development should be clarified and based on the methodology, suitable programming language and framework should be selected. This paper reviews three agent development methodologies (Prometheus, Tropos, and MaSE) and six agent-oriented programming languages/frameworks (MetateM, IndiGolog, Brahms, GOAL, JIAC, and Agent Factory).
STATISTICAL ANALYSIS FOR PERFORMANCE COMPARISONijseajournal
Performance responsiveness and scalability is a make-or-break quality for software. Nearly everyone runs into performance problems at one time or another. This paper discusses about performance issues faced during Pre Examination Process Automation System (PEPAS) implemented in java technology. The challenges faced during the life cycle of the project and the mitigation actions performed. It compares 3 java technologies and shows how improvements are made through statistical analysis in response time of the application. The paper concludes with result analysis.
The document discusses object-oriented system development and modeling. It covers topics like:
1. The main stages of traditional system development life cycles like requirements, analysis, design, implementation, and installation. As well as common life cycle models like waterfall, V-model, spiral, and prototyping.
2. Phases of object-oriented development focus on the state of the system rather than activities, including inception, elaboration, construction, and transition.
3. Modeling techniques for object-oriented systems including the Unified Modeling Language (UML), Rational Unified Process (RUP), abstraction, decomposition, and class-responsibility-collaboration (CRC) cards.
4
Integrating profiling into mde compilersijseajournal
Scientific computation requires more and more performance in its algorithms. New massively parallel
architectures suit well to these algorithms. They are known for offering high performance and power
efficiency. Unfortunately, as parallel programming for these architectures requires a complex distribution
of tasks and data, developers find difficult to implement their applications effectively. Although approaches
based on source-to-source intends to provide a low learning curve for parallel programming and take
advantage of architecture features to create optimized applications, programming remains difficult for
neophytes. This work aims at improving performance by returning to the high-level models, specific
execution data from a profiling tool enhanced by smart advices computed by an analysis engine. In order to
keep the link between execution and model, the process is based on a traceability mechanism. Once the
model is automatically annotated, it can be re-factored aiming better performances on the re-generated
code. Hence, this work allows keeping coherence between model and code without forgetting to harness the
power of parallel architectures. To illustrate and clarify key points of this approach, we provide an
experimental example in GPUs context. The example uses a transformation chain from UML-MARTE
models to OpenCL code.
Integrating goals after prioritization andijseajournal
Decision support system in Requirements engineering plays an important role in software development life
cycle. The relationship between functional and non-functional requirements often plays a crucial role in
resolving conflicts or arriving at decisions in requirements engineering phase. Goal-Oriented
Requirements Engineering (GORE) methods make a good attempt of addressing these aspects which are
helpful in decision support. We propose a GORE method - Integrating goals after prioritization and
evaluation (IGAPE). The method is semi-formal in nature thereby ensuring active stakeholder
participation. In this paper we elaborate the various steps of IGAPE method. The output of IGAPE is then
given as input to a decision support system which makes use of Analytic Hierarchy Process (AHP) and
Technique for Order of Preference by Similarity to Ideal Solution (TOPSIS). Integration of IGAPE with
AHP and TOPSIS will clearly provide a rationale for various decisions which are arrived at during the
requirements engineering phase. The method is illustrated for an e-commerce application and is validated
by expert analysis approach.
QUALITY ASSESSMENT MODEL OF THE ADAPTIVE GUIDANCEijseajournal
The need for adaptive guidance systems is now recognized for all software development processes. The new needs generated by the mobility context for software development led these guidance systems to both quality and ability adaptation to the possible variations of the development context. This paper deals with the adaptive guidance quality to satisfy the developer’s guidance needs. We propose a quality model to the adaptive guidance. This model offers a more detailed description of the quality factors of guidance service adaptation. This description aims to assess the quality level of each guidance adaptation factor and therefore the evaluation of the adaptive quality guidance service.
A SIMILARITY MEASURE FOR CATEGORIZING THE DEVELOPERS PROFILE IN A SOFTWARE PR...cscpconf
Software development processes need to have an integrated environment that fulfills specific
developer needs. In this context, this paper describes the modeling approach SAGM ((Similarity
for Adaptive Guidance Model) that provides adaptive recursive guidance for software
processes, and specifically tailored regarding the profile of developers. A profile is defined from
a model of developers, through their roles, their qualifications, and through the relationships
between the context of the current activity and the model of the activities. This approach
presents a similarity measure that evaluates the similarities between the profiles created from
the model of developers and those of the development team involved in the execution of a
software process. This is to identify the profiles classification and to deduce the appropriate
type of assistance (that can be corrective, constructive or specific) to developers.
Working software measures the progress. Basically, Agile method involves interleaving the specification, implementation, design and testing. Series of versions are developed with the involvement of and evaluation by the stake holders in each version. Agile methods aim at reducing the software process overheads (like documentation) and concentrate more on code rather than the design. Customer involvement, incremental delivery, freedom of developers to evolve new working methods, change management, and last but not the least simplicity is the basic essence of Agile development. Agile methodologies are well suited for small as well as medium sized projects.
Assessment of cmm and its impact on software qualityIAEME Publication
The document discusses the Capability Maturity Model (CMM) and its impact on software quality. CMM provides guidance for software organizations to gain control of their processes and evolve toward excellence. It consists of 5 maturity levels, with each level comprised of key process areas that must be addressed to improve process capability. Achieving a higher maturity level indicates the organization is better able to manage projects and deliver high quality software. The document outlines the structure of CMM and describes the key process areas that define each maturity level. Overall CMM aims to help organizations implement disciplined, measured software development processes to continuously improve quality.
This document discusses tools and techniques for managing projects that encounter problems and become "red" or off-track. It provides two case studies of implementing Oracle ERP projects and discusses lessons learned. The objectives are to familiarize audiences with readily available tools to get projects back on schedule, such as enhanced communication, examining the "triple constraints," breaking projects into smaller phases, and reanalyzing and mitigating risks. Keywords include risk identification/mitigation and early warning signs of project issues.
AN APPROACH TO IMPROVEMENT THE USABILITY IN SOFTWARE PRODUCTSijseajournal
One of the significantaspects of software quality is usability. It is one of the characteristics that judge by
the success or failure of software applications. The most important risk facing the software applications is
usability which may lead to the existence of a gap between users and systems. This may lead to system
failure because of Poor design. This is due to the design is not based on the desires and requirements of the
customer. To overcome these problems, this paper proposed an approach to improve usability of software
applications to meet the needs of the customer and interacts with the user easily with an efficient and
effective manner.The proposed approach is based prototyping technique due to itssimplicity and it does not
require additional costs to elicit precise and complete requirement and design.
Evaluation of the software architecture styles from maintainability viewpointcsandit
In the process of software architecture design, different decisions are made that have systemwide
impact. An important decision of design stage is the selection of a suitable software
architecture style. Lack of investigation on the quantitative impact of architecture styles on
software quality attributes is the main problem in using such styles. So, the use of architecture
styles in designing is based on the intuition of software developers. The aim of this research is
to quantify the impacts of architecture styles on software maintainability. In this study,
architecture styles are evaluated based on coupling, complexity and cohesion metrics and
ranked by analytic hierarchy process from maintainability viewpoint. The main contribution of
this paper is quantification and ranking of software architecture styles from the perspective of
maintainability quality attribute at stage of architectural style selection.
Program analysis is useful for debugging, testing and maintenance of software systems due to information
about the structure and relationship of the program’s modules . In general, program analysis is performed
either based on control flow graph or dependence graph. However, in the case of aspect-oriented
programming (AOP), control flow graph (CFG) or dependence graph (DG) are not enough to model the
properties of Aspect-oriented (AO) programs. With respect to AO programs, although AOP is good for
modular representation and crosscutting concern, suitable model for program analysis is required to
gather information on its structure for the purpose of minimizing maintenance effort. In this paper Aspect
Oriented Dependence Flow Graph (AODFG) as an intermediate representation model is proposed to
represent the structure of aspect-oriented programs. AODFG is formed by merging the CFG and DG, thus
more information about dependencies between the join points, advice, aspects and their associated
construct with the flow of control from one statement to another are gathered. We discussthe performance
of AODFG by analysing some examples of AspectJ program taken from AspectJ Development Tools
(AJDT).
Lightweight processes are beginning to replace more formal methods. The motivation for this transition is based on many factors. The Internet, time to market, cost reduction, quality increases, market pressures, as well as the popularization of these programming methods. This series of articles will investigate the various lightweight methods, their impact on the management of software development projects and the processes by which managers can determine the appropriateness and usefulness of the various processes. The definition of a lightweight Process is more difficult than it would first appear. This article outlines the foundations of a heavyweight process and describes the appropriate pieces that can be converted to lightweight.
THE UNIFIED APPROACH FOR ORGANIZATIONAL NETWORK VULNERABILITY ASSESSMENTijseajournal
The present business network infrastructure is quickly varying with latest servers, services, connections,
and ports added often, at times day by day, and with a uncontrollably inflow of laptops, storage media and
wireless networks. With the increasing amount of vulnerabilities and exploits coupled with the recurrent
evolution of IT infrastructure, organizations at present require more numerous vulnerability assessments.
In this paper new approach the Unified process for Network vulnerability Assessments hereafter called as
a unified NVA is proposed for network vulnerability assessment derived from Unified Software
Development Process or Unified Process, it is a popular iterative and incremental software development
process framework.
Assessment of cmm and its impact on software qualityiaemedu
The document discusses the Capability Maturity Model (CMM) and its impact on software quality. It describes the five levels of the CMM and the key process areas within each level. The CMM is designed to help software organizations improve their processes by advancing through the maturity levels. Advancing to higher levels involves institutionalizing effective software engineering practices. The document also presents a problem statement about software projects facing cost overruns and quality issues. It reviews literature on the CMM and outlines a project conversion process framework to assess CMM implementation.
The document provides an overview of object-oriented technology and software engineering approaches. It describes the structured and object-oriented approaches, the roles of modeling, notation, process and techniques in software development. It also summarizes the Unified Modeling Language (UML), Unified Process, View Alignment techniques, and the Visual Paradigm for UML (VP-UML) CASE tool.
A Software System Development Life Cycle Model for Improved Students Communic...IJCSES Journal
This document describes a proposed software development life cycle (SDLC) model to improve student communication and collaboration. The model uses a spiral development process simulated using Simphony.NET. This allows the project manager to determine the optimal number of team members needed for each phase. The goal is to increase productivity by keeping all members busy at all times. Key aspects of the model include using Edmodo to create an online student learning network for communication and collaboration, dividing projects into small, medium, and large scales, and specifying time distributions for phases and resource needs.
THE USABILITY METRICS FOR USER EXPERIENCEvivatechijri
THE USABILITY METRICS FOR USER EXPERIENCE was innovatively created by Google engineers and it is ready for production in record time. The success of Google is to attributed the efficient search algorithm, and also to the underlying commodity hardware. As Google run number of application then Google’s goal became to build a vast storage network out of inexpensive commodity hardware. So Google create its own file system, named as THE USABILITY METRICS FOR USER EXPERIENCE that is GFS. THE USABILITY METRICS FOR USER EXPERIENCE is one of the largest file system in operation. Generally THE USABILITY METRICS FOR USER EXPERIENCE is a scalable distributed file system of large distributed data intensive apps. In the design phase of THE USABILITY METRICS FOR USER EXPERIENCE, in which the given stress includes component failures , files are huge and files are mutated by appending data. The entire file system is organized hierarchically in directories and identified by pathnames. The architecture comprises of multiple chunk servers, multiple clients and a single master. Files are divided into chunks, and that is the key design parameter. THE USABILITY METRICS FOR USER EXPERIENCE also uses leases and mutation order in their design to achieve atomicity and consistency. As of there fault tolerance, THE USABILITY METRICS FOR USER EXPERIENCE is highly available, replicas of chunk servers and master exists.
Majority of agile projects currently involve interactive user interface designs, which can only be possible by following UCD in agile software model. But the integration of UCD is not clear in the current agile models. Both Agile models and UCD have iterative nature but agile models focus on coding and development of software; whereas, UCD focuses on user interface of the software. Similarly, both of them have testing features where the agile model involves automated tested code while UCD involves an expert or a user to test the user interface. In this paper, a new agile usability model is presented and tested in companies and are presented. Key results from these projects clearly shows: the proposed agile model incorporates usability evaluation methods, improve the relationship between usability experts to work with agile software experts; in addition, allows agile developers to incorporate the result from UCD into subsequent interactions.
The document discusses project planning measures in the Capability Maturity Model Integration (CMMI). It applies the Goal Question Metric (GQM) approach to identify measures for the three specific goals and fourteen specific practices of the Project Planning process area in CMMI. The paper defines questions and measures related to each specific practice by following the three steps of GQM: defining goals, generating quantifiable questions, and defining measures to answer the questions. The identified measures are intended to help evaluate and control software products and processes.
Computer information project planning is one of the most important activities in the modern software
development process. Without an objective and realistic plan of software project, the development of
software process cannot be managed effectively. This research will identify general measures for the
specific goals and its specific practices of Project Planning Process Area in Capability Maturity Model
Integration (CMMI). CMMI is developed in USA by Software Engineering Institute (SEI) in Carnegie
Mellon University. CMMI is a framework for assessment and improvement of computer information
systems. The procedure we used to determine the measures is to apply the Goal Questions Metrics (GQM)
approach to the three specific goals and its fourteen specific practices of Project Planning Process Area in
CMMI.
A Review of Agent-Oriented Development Methodologies and Programming Language...Waqas Tariq
Agents are software systems and can be associated with an entity, framework, architecture and even languages. They are piece of program codes that are able to autonomously complete tasks. Before developing an agent, methodology to be used in development should be clarified and based on the methodology, suitable programming language and framework should be selected. This paper reviews three agent development methodologies (Prometheus, Tropos, and MaSE) and six agent-oriented programming languages/frameworks (MetateM, IndiGolog, Brahms, GOAL, JIAC, and Agent Factory).
STATISTICAL ANALYSIS FOR PERFORMANCE COMPARISONijseajournal
Performance responsiveness and scalability is a make-or-break quality for software. Nearly everyone runs into performance problems at one time or another. This paper discusses about performance issues faced during Pre Examination Process Automation System (PEPAS) implemented in java technology. The challenges faced during the life cycle of the project and the mitigation actions performed. It compares 3 java technologies and shows how improvements are made through statistical analysis in response time of the application. The paper concludes with result analysis.
The document discusses object-oriented system development and modeling. It covers topics like:
1. The main stages of traditional system development life cycles like requirements, analysis, design, implementation, and installation. As well as common life cycle models like waterfall, V-model, spiral, and prototyping.
2. Phases of object-oriented development focus on the state of the system rather than activities, including inception, elaboration, construction, and transition.
3. Modeling techniques for object-oriented systems including the Unified Modeling Language (UML), Rational Unified Process (RUP), abstraction, decomposition, and class-responsibility-collaboration (CRC) cards.
4
Integrating profiling into mde compilersijseajournal
Scientific computation requires more and more performance in its algorithms. New massively parallel
architectures suit well to these algorithms. They are known for offering high performance and power
efficiency. Unfortunately, as parallel programming for these architectures requires a complex distribution
of tasks and data, developers find difficult to implement their applications effectively. Although approaches
based on source-to-source intends to provide a low learning curve for parallel programming and take
advantage of architecture features to create optimized applications, programming remains difficult for
neophytes. This work aims at improving performance by returning to the high-level models, specific
execution data from a profiling tool enhanced by smart advices computed by an analysis engine. In order to
keep the link between execution and model, the process is based on a traceability mechanism. Once the
model is automatically annotated, it can be re-factored aiming better performances on the re-generated
code. Hence, this work allows keeping coherence between model and code without forgetting to harness the
power of parallel architectures. To illustrate and clarify key points of this approach, we provide an
experimental example in GPUs context. The example uses a transformation chain from UML-MARTE
models to OpenCL code.
Integrating goals after prioritization andijseajournal
Decision support system in Requirements engineering plays an important role in software development life
cycle. The relationship between functional and non-functional requirements often plays a crucial role in
resolving conflicts or arriving at decisions in requirements engineering phase. Goal-Oriented
Requirements Engineering (GORE) methods make a good attempt of addressing these aspects which are
helpful in decision support. We propose a GORE method - Integrating goals after prioritization and
evaluation (IGAPE). The method is semi-formal in nature thereby ensuring active stakeholder
participation. In this paper we elaborate the various steps of IGAPE method. The output of IGAPE is then
given as input to a decision support system which makes use of Analytic Hierarchy Process (AHP) and
Technique for Order of Preference by Similarity to Ideal Solution (TOPSIS). Integration of IGAPE with
AHP and TOPSIS will clearly provide a rationale for various decisions which are arrived at during the
requirements engineering phase. The method is illustrated for an e-commerce application and is validated
by expert analysis approach.
QUALITY ASSESSMENT MODEL OF THE ADAPTIVE GUIDANCEijseajournal
The need for adaptive guidance systems is now recognized for all software development processes. The new needs generated by the mobility context for software development led these guidance systems to both quality and ability adaptation to the possible variations of the development context. This paper deals with the adaptive guidance quality to satisfy the developer’s guidance needs. We propose a quality model to the adaptive guidance. This model offers a more detailed description of the quality factors of guidance service adaptation. This description aims to assess the quality level of each guidance adaptation factor and therefore the evaluation of the adaptive quality guidance service.
A SIMILARITY MEASURE FOR CATEGORIZING THE DEVELOPERS PROFILE IN A SOFTWARE PR...cscpconf
Software development processes need to have an integrated environment that fulfills specific
developer needs. In this context, this paper describes the modeling approach SAGM ((Similarity
for Adaptive Guidance Model) that provides adaptive recursive guidance for software
processes, and specifically tailored regarding the profile of developers. A profile is defined from
a model of developers, through their roles, their qualifications, and through the relationships
between the context of the current activity and the model of the activities. This approach
presents a similarity measure that evaluates the similarities between the profiles created from
the model of developers and those of the development team involved in the execution of a
software process. This is to identify the profiles classification and to deduce the appropriate
type of assistance (that can be corrective, constructive or specific) to developers.
Adaptive guidance model based similarity for software process development pro...ijseajournal
This paper describes a modeling approach SAGM (Similarity for Adaptive Guidance Model) that provides
adaptive and recursive guidance for software process development. This approach, in accordance to
developer needs, allows specific tailored guidance regarding the profile of developers. A profile is partially
or completely defined from a model of developers, through their roles, their qualifications, and through the
relationships between the context of the current activity and the model of the defined activities. This
approach aims to define the generic profile of development context and a similarity measure that evaluates
the similarities between the profiles created from the model of developers and those of the development
team involved in the execution of a software process. This is to identify the profiles classification and to
deduce the appropriate type of assistance to developers (that can be corrective, constructive or specific).
Ever wonder what a robust, well-formed and fully articulated methodology should look like? We've used our Methodology Framework to provide you an real-world (and free!) example.
Service oriented configuration management of software architectureIJNSA Journal
Software configuration management (SCM) is an important activity in the software engineering life cycle. SCM by control of the evolution process of products leads to constancy and stability in software systems. Nowadays, use of software configuration management is essential during the process of software development as rules to control and manage the evolution of software systems. SCM effects different levels of abstraction included the architectural level. Configuration of software architecture causes improvement in the configuration of the lower abstraction levels. CM of software architecture is more significant in large scale software with longevity of life cycle. Traditional SCM approaches, at the architectural level, do not provided the necessary support to software configuration management, so systems that use these approaches are faced with problems. These problems arise because of the lack of a serious constant and repeated changes in the software process. To overcome this it is necessary to create an infrastructure. Hence, a service oriented approach for configuration management is presented in this paper. In this approach, the activities of configuration management are conducted from a service oriented viewpoint. This approach was also used to try and control the evolution and number of versions of different software systems in order to identify, organize and control change and reforms during the production process. This approach can compose services and create composite services for new undefined activities of configuration.
SERVICE ORIENTED CONFIGURATION MANAGEMENT OF SOFTWARE ARCHITECTUREIJNSA Journal
Software configuration management (SCM) is an important activity in the software engineering life cycle. SCM by control of the evolution process of products leads to constancy and stability in software systems. Nowadays, use of software configuration management is essential during the process of software development as rules to control and manage the evolution of software systems. SCM effects different levels of abstraction included the architectural level. Configuration of software architecture causes improvement in the configuration of the lower abstraction levels. CM of software architecture is more significant in large scale software with longevity of life cycle. Traditional SCM approaches, at the architectural level, do not provided the necessary support to software configuration management, so systems that use these approaches are faced with problems. These problems arise because of the lack of a serious constant and repeated changes in the software process. To overcome this it is necessary to create an infrastructure. Hence, a service oriented approach for configuration management is presented in this paper. In this approach, the activities of configuration management are conducted from a service oriented viewpoint. This approach was also used to try and control the evolution and number of versions of different software systems in order to identify, organize and control change and reforms during the production process. This approach can compose services and create composite services for new undefined activities of configuration.
A SIMILARITY MEASURE FOR CATEGORIZING THE DEVELOPERS PROFILE IN A SOFTWARE PR...csandit
Software development processes need to have an integrated environment that fulfills specific
developer needs. In this context, this paper describes the modeling approach SAGM ((Similarity
for Adaptive Guidance Model) that provides adaptive recursive guidance for software
processes, and specifically tailored regarding the profile of developers. A profile is defined from
a model of developers, through their roles, their qualifications, and through the relationships
between the context of the current activity and the model of the activities. This approach
presents a similarity measure that evaluates the similarities between the profiles created from
the model of developers and those of the development team involved in the execution of a
software process. This is to identify the profiles classification and to deduce the appropriate
type of assistance (that can be corrective, constructive or specific) to developers.
A methodology to evaluate object oriented software systems using change requi...ijseajournal
It is a well known fact that software maintenance plays a major role and finds importance in software
development life cycle. As object
-
oriented programming has become the standard, it is very important to
understand th
e problems of maintaining object
-
oriented software systems. This paper aims at evaluating
object
-
oriented software system through change requirement traceability
–
based impact analysis
methodology
for non functional requirements using functional requirem
ents
. The major issues have been
related to change impact algorithms and inheritance of functionality.
A Comparative Analysis Of Various Methodologies Of Agile Project Management V...Brittany Allen
This document provides a comparative analysis of project management methodologies, specifically comparing the Project Management Body of Knowledge (PMBOK) and various agile project management approaches. It first describes the key processes and knowledge areas of PMBOK. It then outlines some popular agile methodologies like Scrum, Extreme Programming (XP), and Feature Driven Development (FDD). The document aims to identify similarities and differences between the traditional PMBOK framework and more flexible agile approaches.
Adopting DevOps practices: an enhanced unified theory of acceptance and use o...IJECEIAES
DevOps software development approach is widely used in the software engineering discipline. DevOps eliminates the development and operations department barriers. The paper aims to develop a conceptual model for adopting DevOps practices in software development organizations by extending the unified theory of acceptance and use of technology (UTAUT). The research also aims to determine the influencing factors of DevOps practices’ acceptance and adoption in software organizations, determine gaps in the software development literature, and introduce a clear picture of current technology acceptance and adoption research in the software industry. A comprehensive literature review clarifies how users accept and adopt new technologies and what leads to adopting DevOps practices in the software industry as the starting point for developing a conceptual framework for adopting DevOps in software organizations. The literature results have formulated the conceptual framework for adopting DevOps practices. The resulting model is expected to improve understanding of software organizations’ acceptance and adoption of DevOps practices. The research hypotheses must be tested to validate the model. Future work will include surveys and expert interviews for model enhancement and validation. This research fulfills the necessity to study how software organizations accept and adopt DevOps practices by enhancing UTAUT.
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.
Software testing is a key part of software engineering used to evaluate software quality and identify errors. There are various software testing techniques and methods, but thoroughly investigating a complex software is more important than following a specific procedure. Testing complex software cannot discover all errors, but can help improve quality. Software engineering involves defining requirements, design, development, testing, and maintenance of software using methodologies like agile development.
ITERATIVE AND INCREMENTAL DEVELOPMENT ANALYSIS STUDY OF VOCATIONAL CAREER INF...ijseajournal
Software development process presents various types of models with their corresponding phases required to be accordingly followed in delivery of quality products and projects. Despite the various expertise and skills of systems analysts, designers, and programmers, systems failure is inevitable when a suitable development process model is not followed. This paper focuses on the Iterative and Incremental Development (IID)model and justified its role in the analysis and design software systems. The paper adopted the qualitative research approach that justified and harnessed the relevance of IID in the context of systems analysis and design using the Vocational
Career Information System (VCIS) as a case study. The paper viewed the IID as a change-driven software development process model. The results showed some system specification, functional specification of system and design specifications that can be used in implementing the VCIS using the IID model. Thus, the paper concluded that in systems analysis and design, it is imperative to consider a suitable development process that reflects the engineering mind-set, with heavy emphasis on good analysis and design for quality assurance.
Distributed Software Development Process, Initiatives and Key Factors: A Syst...zillesubhan
Geographically Distributed Software Development (GSD) process differs from Collocated Software Development (CSD) process in various technical aspects. It is empirically proven that renowned process improvement initiatives applicable to CSD are not very effective for GSD. The objective of this research is to review the existing literature (both academia and industrial) to identify initiatives and key factors which play key role in the improvement and maturity of a GSD process, to achieve this goal we planned a Systematic Literature Review (SLR) following a standard protocol. Three highly respected sources are selected to search for the relevant literature which resulted in a large number of TOIs (Title of Interest). An inter-author custom protocol is outlined and followed to shortlist most relevant articles for review. The data is extracted from this set of finally selected articles. We have performed both qualitative and quantitative analysis of the extracted data to obtain the results. The concluded results identify several initiatives and key factors involved in GSD and answer each research question posed by the SLR.
A Guideline Tool for Ongoing Product Evaluation in Small and Medium-Sized Ent...IJECEIAES
As consumer demand for user friendly software increases, usability evaluation is crucial to develop software systems which are easy to learn and use. However, implementation of usability evaluation is challenging for small and medium-sized enterprises (SMEs) due to factors such as lack of technical expertise, knowledge and experience of methods and standards. This results in neglect, or poorly executed evaluations of projects, resulting in software that disappoints and frustrates clients. To overcome this loss of competitiveness, we propose here a visual incorporation tool derived from ISO standards that would assist software development teams in SMEs in understanding and implementing usability evaluations. It shows fundamental Usability Engineering (UE) and Software Engineering (SE) activities and artifacts relevant to the usability evaluation and software development process, with potential incorporation points being highlighted. Dependencies and relationships are shown by links between activities and artifacts. Additionally, convergent artifacts of both disciplines were identified and shown. Evaluation of the proposed tool was based on the questionnaire results of software development practitioners from SMEs.
A Systematic Review On Software Cost Estimation In Agile Software DevelopmentBrooke Heidt
This document provides a summary of a systematic literature review on software cost estimation techniques for agile software development. It discusses the challenges of cost estimation for agile projects due to their dynamic nature. The review examines various cost estimation mechanisms that have been explored for agile methodologies and compares their accuracy based on parameters like magnitude of relative error, mean magnitude of relative error, and others. It aims to help agile practitioners understand current trends in cost estimation and determine which techniques may be suitable given different project circumstances.
A SURVEY ON ACCURACY OF REQUIREMENT TRACEABILITY LINKS DURING SOFTWARE DEVELO...ijiert bestjournal
There are number of routing protocols proposed for the data transmission in WSN. Initially single path routing schemes with number of variations are proposed. Sti ll there were some drawbacks in single path routing . Single path routing was unable to provide the reliability and h igh throughput. Also security level was not conside red while routing. Recently,to remove the drawbacks of the s ingle path routing new routing technique is propose d called as multipath routing. In this paper we discussed the different multipath routing protocols with number of variants. Initiall y multipath routing was proposed for the purpose of guaranteed delivery of packet to sink in case of link or node failure. There are other protocols which are proposed for the reli ability,energy saving,security and high throughpu t. Some multipath routing protocols have discussed the load balancing and security during packet transmission.
STATISTICAL ANALYSIS OF METRICS FOR SOFTWARE QUALITY IMPROVEMENT ijseajournal
Software product quality can be defined as the features and characteristics of the product that meet the user needs. The quality of any software can be achieved by following a well defined software process. These software process results into various metrics like Project metrics, Product metrics and Process metrics. Software quality depends on the process which is carried out to design and develop software. Even though the process can be carried out with utmost care, still it can introduce some error and defects. Process metrics are very useful from management point of view. Process metrics can be used for improving the software development and maintenance process for defect removal and also for reducing the response
time.
This paper describes the importance of capturing the Process metrics during the quality audit process and also attempts to categorize them based on the nature of error captured. To reduce such errors and defects found, steps for corrective actions are recommended.
A Methodology For Large-Scale E-Business Project ManagementApril Smith
This document proposes an environment-based methodology for managing large-scale e-business projects. The methodology defines six working environments - development, integration, pre-production, production, demonstration, and software repository - that represent increasing stages of stability for a software product. It describes the tasks and migration processes between environments. The methodology aims to systematically guide e-business project management according to an organization's needs and resources.
Similar to ADAPTIVE CONFIGURATION META-MODEL OF A GUIDANCE PROCESS (20)
Have you ever been confused by the myriad of choices offered by AWS for hosting a website or an API?
Lambda, Elastic Beanstalk, Lightsail, Amplify, S3 (and more!) can each host websites + APIs. But which one should we choose?
Which one is cheapest? Which one is fastest? Which one will scale to meet our needs?
Join me in this session as we dive into each AWS hosting service to determine which one is best for your scenario and explain why!
Main news related to the CCS TSI 2023 (2023/1695)Jakub Marek
An English 🇬🇧 translation of a presentation to the speech I gave about the main changes brought by CCS TSI 2023 at the biggest Czech conference on Communications and signalling systems on Railways, which was held in Clarion Hotel Olomouc from 7th to 9th November 2023 (konferenceszt.cz). Attended by around 500 participants and 200 on-line followers.
The original Czech 🇨🇿 version of the presentation can be found here: https://www.slideshare.net/slideshow/hlavni-novinky-souvisejici-s-ccs-tsi-2023-2023-1695/269688092 .
The videorecording (in Czech) from the presentation is available here: https://youtu.be/WzjJWm4IyPk?si=SImb06tuXGb30BEH .
Driving Business Innovation: Latest Generative AI Advancements & Success StorySafe Software
Are you ready to revolutionize how you handle data? Join us for a webinar where we’ll bring you up to speed with the latest advancements in Generative AI technology and discover how leveraging FME with tools from giants like Google Gemini, Amazon, and Microsoft OpenAI can supercharge your workflow efficiency.
During the hour, we’ll take you through:
Guest Speaker Segment with Hannah Barrington: Dive into the world of dynamic real estate marketing with Hannah, the Marketing Manager at Workspace Group. Hear firsthand how their team generates engaging descriptions for thousands of office units by integrating diverse data sources—from PDF floorplans to web pages—using FME transformers, like OpenAIVisionConnector and AnthropicVisionConnector. This use case will show you how GenAI can streamline content creation for marketing across the board.
Ollama Use Case: Learn how Scenario Specialist Dmitri Bagh has utilized Ollama within FME to input data, create custom models, and enhance security protocols. This segment will include demos to illustrate the full capabilities of FME in AI-driven processes.
Custom AI Models: Discover how to leverage FME to build personalized AI models using your data. Whether it’s populating a model with local data for added security or integrating public AI tools, find out how FME facilitates a versatile and secure approach to AI.
We’ll wrap up with a live Q&A session where you can engage with our experts on your specific use cases, and learn more about optimizing your data workflows with AI.
This webinar is ideal for professionals seeking to harness the power of AI within their data management systems while ensuring high levels of customization and security. Whether you're a novice or an expert, gain actionable insights and strategies to elevate your data processes. Join us to see how FME and AI can revolutionize how you work with data!
Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slackshyamraj55
Discover the seamless integration of RPA (Robotic Process Automation), COMPOSER, and APM with AWS IDP enhanced with Slack notifications. Explore how these technologies converge to streamline workflows, optimize performance, and ensure secure access, all while leveraging the power of AWS IDP and real-time communication via Slack notifications.
Introduction of Cybersecurity with OSS at Code Europe 2024Hiroshi SHIBATA
I develop the Ruby programming language, RubyGems, and Bundler, which are package managers for Ruby. Today, I will introduce how to enhance the security of your application using open-source software (OSS) examples from Ruby and RubyGems.
The first topic is CVE (Common Vulnerabilities and Exposures). I have published CVEs many times. But what exactly is a CVE? I'll provide a basic understanding of CVEs and explain how to detect and handle vulnerabilities in OSS.
Next, let's discuss package managers. Package managers play a critical role in the OSS ecosystem. I'll explain how to manage library dependencies in your application.
I'll share insights into how the Ruby and RubyGems core team works to keep our ecosystem safe. By the end of this talk, you'll have a better understanding of how to safeguard your code.
Unlock the Future of Search with MongoDB Atlas_ Vector Search Unleashed.pdfMalak Abu Hammad
Discover how MongoDB Atlas and vector search technology can revolutionize your application's search capabilities. This comprehensive presentation covers:
* What is Vector Search?
* Importance and benefits of vector search
* Practical use cases across various industries
* Step-by-step implementation guide
* Live demos with code snippets
* Enhancing LLM capabilities with vector search
* Best practices and optimization strategies
Perfect for developers, AI enthusiasts, and tech leaders. Learn how to leverage MongoDB Atlas to deliver highly relevant, context-aware search results, transforming your data retrieval process. Stay ahead in tech innovation and maximize the potential of your applications.
#MongoDB #VectorSearch #AI #SemanticSearch #TechInnovation #DataScience #LLM #MachineLearning #SearchTechnology
For the full video of this presentation, please visit: https://www.edge-ai-vision.com/2024/06/building-and-scaling-ai-applications-with-the-nx-ai-manager-a-presentation-from-network-optix/
Robin van Emden, Senior Director of Data Science at Network Optix, presents the “Building and Scaling AI Applications with the Nx AI Manager,” tutorial at the May 2024 Embedded Vision Summit.
In this presentation, van Emden covers the basics of scaling edge AI solutions using the Nx tool kit. He emphasizes the process of developing AI models and deploying them globally. He also showcases the conversion of AI models and the creation of effective edge AI pipelines, with a focus on pre-processing, model conversion, selecting the appropriate inference engine for the target hardware and post-processing.
van Emden shows how Nx can simplify the developer’s life and facilitate a rapid transition from concept to production-ready applications.He provides valuable insights into developing scalable and efficient edge AI solutions, with a strong focus on practical implementation.
How to Interpret Trends in the Kalyan Rajdhani Mix Chart.pdfChart Kalyan
A Mix Chart displays historical data of numbers in a graphical or tabular form. The Kalyan Rajdhani Mix Chart specifically shows the results of a sequence of numbers over different periods.
Taking AI to the Next Level in Manufacturing.pdfssuserfac0301
Read Taking AI to the Next Level in Manufacturing to gain insights on AI adoption in the manufacturing industry, such as:
1. How quickly AI is being implemented in manufacturing.
2. Which barriers stand in the way of AI adoption.
3. How data quality and governance form the backbone of AI.
4. Organizational processes and structures that may inhibit effective AI adoption.
6. Ideas and approaches to help build your organization's AI strategy.
Webinar: Designing a schema for a Data WarehouseFederico Razzoli
Are you new to data warehouses (DWH)? Do you need to check whether your data warehouse follows the best practices for a good design? In both cases, this webinar is for you.
A data warehouse is a central relational database that contains all measurements about a business or an organisation. This data comes from a variety of heterogeneous data sources, which includes databases of any type that back the applications used by the company, data files exported by some applications, or APIs provided by internal or external services.
But designing a data warehouse correctly is a hard task, which requires gathering information about the business processes that need to be analysed in the first place. These processes must be translated into so-called star schemas, which means, denormalised databases where each table represents a dimension or facts.
We will discuss these topics:
- How to gather information about a business;
- Understanding dictionaries and how to identify business entities;
- Dimensions and facts;
- Setting a table granularity;
- Types of facts;
- Types of dimensions;
- Snowflakes and how to avoid them;
- Expanding existing dimensions and facts.
5th LF Energy Power Grid Model Meet-up SlidesDanBrown980551
5th Power Grid Model Meet-up
It is with great pleasure that we extend to you an invitation to the 5th Power Grid Model Meet-up, scheduled for 6th June 2024. This event will adopt a hybrid format, allowing participants to join us either through an online Mircosoft Teams session or in person at TU/e located at Den Dolech 2, Eindhoven, Netherlands. The meet-up will be hosted by Eindhoven University of Technology (TU/e), a research university specializing in engineering science & technology.
Power Grid Model
The global energy transition is placing new and unprecedented demands on Distribution System Operators (DSOs). Alongside upgrades to grid capacity, processes such as digitization, capacity optimization, and congestion management are becoming vital for delivering reliable services.
Power Grid Model is an open source project from Linux Foundation Energy and provides a calculation engine that is increasingly essential for DSOs. It offers a standards-based foundation enabling real-time power systems analysis, simulations of electrical power grids, and sophisticated what-if analysis. In addition, it enables in-depth studies and analysis of the electrical power grid’s behavior and performance. This comprehensive model incorporates essential factors such as power generation capacity, electrical losses, voltage levels, power flows, and system stability.
Power Grid Model is currently being applied in a wide variety of use cases, including grid planning, expansion, reliability, and congestion studies. It can also help in analyzing the impact of renewable energy integration, assessing the effects of disturbances or faults, and developing strategies for grid control and optimization.
What to expect
For the upcoming meetup we are organizing, we have an exciting lineup of activities planned:
-Insightful presentations covering two practical applications of the Power Grid Model.
-An update on the latest advancements in Power Grid -Model technology during the first and second quarters of 2024.
-An interactive brainstorming session to discuss and propose new feature requests.
-An opportunity to connect with fellow Power Grid Model enthusiasts and users.
Generating privacy-protected synthetic data using Secludy and MilvusZilliz
During this demo, the founders of Secludy will demonstrate how their system utilizes Milvus to store and manipulate embeddings for generating privacy-protected synthetic data. Their approach not only maintains the confidentiality of the original data but also enhances the utility and scalability of LLMs under privacy constraints. Attendees, including machine learning engineers, data scientists, and data managers, will witness first-hand how Secludy's integration with Milvus empowers organizations to harness the power of LLMs securely and efficiently.
Skybuffer SAM4U tool for SAP license adoptionTatiana Kojar
Manage and optimize your license adoption and consumption with SAM4U, an SAP free customer software asset management tool.
SAM4U, an SAP complimentary software asset management tool for customers, delivers a detailed and well-structured overview of license inventory and usage with a user-friendly interface. We offer a hosted, cost-effective, and performance-optimized SAM4U setup in the Skybuffer Cloud environment. You retain ownership of the system and data, while we manage the ABAP 7.58 infrastructure, ensuring fixed Total Cost of Ownership (TCO) and exceptional services through the SAP Fiori interface.
HCL Notes and Domino License Cost Reduction in the World of DLAUpanagenda
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-and-domino-license-cost-reduction-in-the-world-of-dlau/
The introduction of DLAU and the CCB & CCX licensing model caused quite a stir in the HCL community. As a Notes and Domino customer, you may have faced challenges with unexpected user counts and license costs. You probably have questions on how this new licensing approach works and how to benefit from it. Most importantly, you likely have budget constraints and want to save money where possible. Don’t worry, we can help with all of this!
We’ll show you how to fix common misconfigurations that cause higher-than-expected user counts, and how to identify accounts which you can deactivate to save money. There are also frequent patterns that can cause unnecessary cost, like using a person document instead of a mail-in for shared mailboxes. We’ll provide examples and solutions for those as well. And naturally we’ll explain the new licensing model.
Join HCL Ambassador Marc Thomas in this webinar with a special guest appearance from Franz Walder. It will give you the tools and know-how to stay on top of what is going on with Domino licensing. You will be able lower your cost through an optimized configuration and keep it low going forward.
These topics will be covered
- Reducing license cost by finding and fixing misconfigurations and superfluous accounts
- How do CCB and CCX licenses really work?
- Understanding the DLAU tool and how to best utilize it
- Tips for common problem areas, like team mailboxes, functional/test users, etc
- Practical examples and best practices to implement right away
Digital Marketing Trends in 2024 | Guide for Staying AheadWask
https://www.wask.co/ebooks/digital-marketing-trends-in-2024
Feeling lost in the digital marketing whirlwind of 2024? Technology is changing, consumer habits are evolving, and staying ahead of the curve feels like a never-ending pursuit. This e-book is your compass. Dive into actionable insights to handle the complexities of modern marketing. From hyper-personalization to the power of user-generated content, learn how to build long-term relationships with your audience and unlock the secrets to success in the ever-shifting digital landscape.
Digital Marketing Trends in 2024 | Guide for Staying Ahead
ADAPTIVE CONFIGURATION META-MODEL OF A GUIDANCE PROCESS
1. International Journal of Computer Science & Information Technology (IJCSIT) Vol 8, No 3, June 2016
DOI:10.5121/ijcsit.2016.8312 157
ADAPTIVE CONFIGURATION META-MODEL OF A
GUIDANCE PROCESS
Hamid Khemissa1
and Mourad Oussalah2
1
Computer Systems Laboratory, Computer Science Institute, USTHB University, Bab
Ezzouar Algeria
2
Computer Laboratory Nantes Atlantique, Faculty of science Nantes University
ABSTRACT
The current technology tend leads us to recognize the need for adaptive guidance process for all process of
software development. The new needs generated by the mobility context for software development led these
guidance processes to be adapted. In order to improve the performance of the deployed software
development, it is useful to manage the configuration of its evolving aspects. This paper deals with the
configuration management of guidance process or its ability to be adapted to specific development
contexts. The proposed adaptive configuration Meta-model is worked out on the basis of a Y description
for adaptive guidance process. This description focuses on three dimensions defined by the
material/software platform, the adaptation form and provided guidance service. Each dimension considers
several factors to develop a coherent configuration strategy and provide automatically the appropriate
guidance process to a current development context.
KEYWORDS
Guidance process, Configuration process, Adaptive meta-model, Development context.
1. INTRODUCTION AND CURRENT TEND
The software development organizations are actually confronted to difficulties regarding the
development of their applications. Due to technological progress, the developer is considered
nowadays as a mobile actor working in various development context using variable platforms.
This trend seems interesting from a user’s perspective, it poses a new problem in software
processes engineering. This concern denotes the adaptation ability to the possible variations of the
development context. The objective is to support the software process by providing software tools
to model, improve, assist and automate development activities [1, 2]. They agree on the following
goals like to facilitate the comprehension and communication process, to describe clearly the
roles, responsibilities and interactions between users, to automate the execution of repetitive tasks
that do not require the human actor intervention and to provide guidance to actors about modeling
and handling a software process. According to the aim and orientation given to the software
process, it is possible that other concepts such as strategy, organization and guidance can be
described in the software process meta-model [2,3,4].
For this, it is necessary to assist developers and to ensure configuration management of the
guidance processes [5, 6] by their ability to adapt to the current development context in respect of
their usefulness. By development context, we mean the triplet (material/software platform,
developer profile, activity context). Usefulness refers to the ability of a guidance process to allow
the developer to reach his objective preserving consistency and product quality in software
development.
2. International Journal of Computer Science & Information Technology (IJCSIT) Vol 8, No 3, June 2016
158
In this perspective, a rigorous guidance process targets two basic aspects: 1) The progress control
of the software process development regarding the temporal constraints of the activity and the
consistency of the results, and 2) the guidance interventions adapted to the specific needs within
the development context in progress.
Several process-centered environments [7, 8, 9] deal with the guidance aspect in the support of
the software product development. Some Process Centered Software Engineering Environments
(PSEEs) use a guidance description structured in phases like prescribing systems or proactive
systems to control the operations carried out by the developer. Nevertheless, they are essentially
limited to the adaptive guidance aspect to current development context. However, the provided
guidance is not often adapted to the development context profile. The orientations of the guidance
are defined on the basis that the human actor, regardless of his profile (qualifications and
behaviour), has a central role in the progress of the development process.
Among this new generation of software process engineering, we can invoke the following meta-
models and modeling environments: SPEM [10] and APEL [8] considered as the most
representative in the software process modeling, RHODES [7, 11] that uses basic concepts closest
to those introduced in the proposed approach.
SPEM meta-model introduced the concept of "Guidance". According to SPEM, the guidance is a
describable element, which provides additional information to define the describable elements of
modeling. However, the proposed guidance is not suitable to the development context’s profile
(role, qualifications and behaviour). The guidance is rather defined in an intuitive way.
ADELE/APEL proposes a global guidance of proscriptive type without considering the
development context profile and automates part of the development process using triggers.
RHODES/PBOOL+ uses an explicit description of a development process. The activities are
associated to a guidance system with various scenarios of possible realization.
An effective support to software process depends on several factors, in particular the
personalization and adaptation factor. The definition of a process with an active guidance for
automation and coherency control would be effective if it can be adapted to each development
context. The platform, task and developer factors may considerably vary.
Taking into account specific criteria for an adaptive guidance, we have classified these limits
through several criteria describing explicitly the basic concepts linked to the adaptive guidance
[5, 6, 12]. To realize the effectiveness of the configuration concept of the guidance process
supported by its adaptation ability to current development context, we refer to the studied meta-
models and modeling environments [12, 13, 14, 15, 16]. The selected criteria are defined by:
• Global guidance core: The basic guidance is defined as a global orientation core regardless
the profile of both the activity and the actor.
• Developer profile oriented guidance: the guidance orientations are defined on the basis
that the human actor, regardless his profile, has a central role in the progress of the
development process.
• Context development guidance: The selection of the appropriate type of guidance is more
often not adapted nor suitable to a current context.
• Guidance types: the selection of guidance types remains defined in a manual and intuitive
way. It depends on the experience and on the informal personality of the project manager.
• Configuration of guidance process: the guidance functions are defined and offered on the
basis that the human actor always operates in a uniform development context.
3. International Journal of Computer Science & Information Technology (IJCSIT) Vol 8, No 3, June 2016
159
To respond to these limits, one currently tries to offer more flexibility in the language of software
process modeling. This tendency results in the idea to define interventions of adaptive guidance in
particular contexts during the progress of software process. In considering the principal
limitations of PSEEs and essential characteristics of our approach in particularly the context
adaptation aspect, a comparative table of the studied meta-models is as follows.
Table 1. Comparative table of the studied meta-models.
The current tendency is that developers would like to have integrated environments that are
suitable to specific needs according to the development context factors. However, despite the
necessity imposed by technological evolution, the provided efforts to develop such environments
remain an insufficient contribution. This generation of guidance environment still interests
researchers in defining new concepts and objectives of the software process modeling [4, 17, 18].
Our work proposes an approach to define configuration of an adaptive guidance modeling in
software process. The concepts of proposed approach are described through a meta-model
denoted CGPM (Configuration of Guidance Process Meta-model). The information provided
must be adapted to the development context profile. They must guide the developer during the
software process development through suitable actions and decisions to undertake with
corrective, constructive or automatic intervention [12]. The three dimensions defined by the
development context, the adaptation form and the provided service explicitly describe our
guidance process adaptation.
Section 2 of this paper presents our approach of the Y adaptive guidance modeling. Section 3
describes the configuration management usefulness and the generic view of its operational model,
while section 4 describes the configuration management of the guidance process, as well as the
Configuration of Guidance Process Meta-model (CGPM) and section 5 presents the practical
cases study of the adaptive guidance process. It ends with a conclusion and future prospects.
2. THE ADAPTIVE GUIDANCE IN Y
A guidance process may be processed in many different ways according to the perspective
guidance to provide interveners with development context. Thus, there are generally several
possible guidance models, each of them with a particular relevance and need. This vision denotes
the configuration of guidance process, and its ability to adapt to its development context.
The configuration concept describes its capacity to adapt to the intrinsic variations of required
conditions in terms of usefulness [16, 19, 20].
Meta model
Criteria
ADELE/APEL RHODES / PBOOL+ SPEM
Global guidance core Global Global Global
Developer profile
oriented guidance
Not adapted
Considered strategy
Model
Not adapted
Context development
guidance
Not adapted Adapted Not adapted
Guidance types Not invoked
Associated with a
specific guide system
Intuitive selection
Configuration of
guidance process
Not covered
(Single Platform)
Not covered
(Single Platform)
Not covered
(Single Platform)
4. International Journal of Computer Science & Information Technology (IJCSIT) Vol 8, No 3, June 2016
160
In this context, we propose a description in Y of the adaptive guidance. This description will
focus on the three considered dimensions. Each dimension considers several factors to deduce
automatically the appropriate guidance service according to the current context. Schematically,
we describe it as follow
Figure 1. Adaptive guidance description in Y.
The principle of our approach is to generate, from the development context related to the specific
data for each defined models according to the retained adaptation form, the guidance
interventions (corrective, constructive, automatic) adapted to the current development context.
2.1. The basic conceptual model description
The conceptual model highlights the guidance process aspect through the adaptation form
described by the inherent relationship between the three considered dimensions.
1. THE DEVELOPMENT CONTEXT
A guidance intervention is provided according to an object or set of objects. An object is
associated to the following:
• The material/software platform: described by the computing resources, the software
services as well as the interaction and communication modes.
• The activity context: models the structure and the workflow, they are defined by a
progression mode in the activity ensuring that all tasks can be performed under control in a
preset order established by the designer and a temporal progression mode specifying
deadlines for completion.
• The developer profile: defines the specific properties of each developer. These properties
can be either static or dynamic. The static aspect refers to the user characteristic as his
role, his business competence and his familiarity with the software process. The dynamic
aspect refers to the behaviour of using the guidance service, by the fact to execute, to
define or to complete the software process resource and the user’s reaction to a guidance
message.
The description performance rate of these factors is evaluated by considering each identified
object as concepts, principles, procedures, and resources. These guidance objects represent the
Adaptation form
+
- Adaptive
- Contextual
- Mixed
- Corrective
- Constructive
- Automatic
Provided service
Development
context
Description ratio
[0,1]
Adaptation ratio
[0, 1]
Description ratio
[0, 1]
Interpretation
sense
- Material/software Platform
- Developer profile
- Activity context
5. International Journal of Computer Science & Information Technology (IJCSIT) Vol 8, No 3, June 2016
161
basis of different guidance interventions related to a particular situation. This performance serves
as the selection of the adaptation form to retain and guidance service to provide to the user.
2. THE ADAPTATION FORM
Each guidance intervention is done according to the retained adaptation form. It relates to a
specific situation described by the development context description. Our modeling approach
allows the following guidance adaptation forms:
• Contextual guidance: intervention is provided dynamically according to the
material/software platform and activity models. The adaptation rate is related to the
model description rate of the activity and the material/software platform. The guidance
intervention does not consider the developer model (e.g. to avoid inconsistency during
the affectation of a resource).
• Adaptive guidance: intervention is provided according to the developer model and the
material/software platform specificity (e.g.: the user asks for explanations on his choice).
The adaptation rate is related to the developer and material platform models description.
• Mixed guidance: intervention is provided according to the development context (e.g.: to
guide the developer on the sequencing principle during the software process progression).
This form describes the highest adaptation rate. This rate is evaluated on the basis of the
developer, activity and material/software platform models description.
The adaptation form performance is described by a strong coupling between the development
environment and guidance process. It determines the relevance and precision of the guidance
provided to developers.
This criterion is directly related to the adaptive guidance process concept. Through a strong
coupling, the process would deduce the guidance service and can therefore extract useful and
helpful information to the user.
3. THE PROVIDED SERVICE
The guidance process offers several service types in relation to a defined context by the current
development and adaptive form. The provided guidance services are corrective, constructive or
automatic order.
Control and taking corrective initiative: protect the user of his own initiatives when they are
inadequate under progress.
Control and taking constructive initiative: the ability to take positive initiatives, executing
and combining the performance of operations without the user intervention.
The guidance adaptation performance associated to a development environment is done by
enrichment or reduction of the possible offers of the guidance. Among these offers, we have:
• The directive guidance: to show the developer how to execute a task by an adaptive control
of the guidance system, specifying the steps of an activity or the whole process development.
• Retroaction, to offer the developer more information on the activities context (e.g. new
available resources) or on the progress state of his work (progression of an activity).
• Explanation, to offer explanations about a guidance object at the request developer. (e.g. the
activities coordination of the software process).
• Reminding, to remind the developer some principles or procedures on the sequencing of the
activities or their activation conditions when the system detects a conflict or inconsistency.
6. International Journal of Computer Science & Information Technology (IJCSIT) Vol 8, No 3, June 2016
162
Automatic guidance: analyze the impact projection to define the solution to consider in order
to avoid deadlocks or delays, by the fact to start, suspend, discontinue or continue ongoing
actions to avoid conflict.
These guidance services can be combined. They may be temporary, permanent or left under the
developer control.
The usefulness rate is evaluated by the degree of the performance description of the development
context and adaptation form.
3. WHY PROCESS CONFIGURATION MANAGEMENT
The configuration management is a constant concern of the software development community,
classified as a fundamental discipline to software process development, and necessary for
providing all the time a coherent system support regardless the changes of the different
development context. This management process seeks adapted tools which allow to supervise
any entity evolution under the pre-established norms and rules of a software process. The tools
and techniques of initiating, evaluating and controlling change in the software development
environment where any entity managed in the software engineering process can potentially be
considered under configuration management control. The main purpose of a process management
configuration targets the establishment of the coherent support process synchronizing with
possible evolutions while maintaining the quality continuity of software process development [14,
21].
The configuration management is one of 17 process of ISO 12207 (Software life cycle support
processes) [22]. A specific standard, ISO 10007 is devoted to this process. This management
allows to identify, manage and control configuration items throughout the software development
process cycle. [23]. However, all the existing standards are still powerless to promote the best
practices in the development area.
The dynamic aspect of the configuration management process results from a development
perspective of a successive static description in time. It enables to coordinate the development
activities and supervise each profile entity evolution over the elaboration of software process to
promote coherence with the provided support. In an effective dynamic environment, efficient and
flexible guidance process is a suitable support for modeling and handling software process. The
guidance process management is an overall task supporting the whole lifecycle of software
process. Therefore, a guidance process needs to be planned, adapted and controlled in terms of
user's requirements. The operational process of the guidance is analyzed to identify each time the
guidance needs in order to improve the performance of the deployed software process. This
performance is due to innovations produced by developers, who are expecting to benefit from
using support services. This means that we should develop the configuration that fulfills their
exact needs, leading them to have a trend to benefit from a support solution, to preserve
consistency and product quality in software development [15, 16].
The configuration management plan describes the application scope and key terms. It identifies
the responsible who achieves the planned configuration management activities (Who manages?),
identifies the management activities to be performed (What activities?). Then identifies tools and
techniques required for the configuration planning (HOW planned?), establishes the sequence and
coordination of the management configuration activities (When scheduled?). Finally, identifies
activities and responsibilities on how the SCMP will be held active during the development
lifecycle. As regard the implementation of its process, the required information should be
collected by identifying the configuration items to be applied to the configuration management
and its application constraints. As well as, to identify the need for a change and how to provide a
7. International Journal of Computer Science & Information Technology (IJCSIT) Vol 8, No 3, June 2016
163
service support. Moreover, assumptions that might have an impact on schedule and ability to
perform defined configuration activities [24].
The operational model of a configuration process is based on the fact that the software
configuration management plan might be extended or revised during the rest of the project
following any change at the developers’ request or by a trigger event that is assessed against the
project goals.
This configuration process is an application developed using a configuration server and based on
a set of constraints and / or preferences described by the characteristics of the current
development context. If one of these constraints and / or preferences causes a change or an
evolution notified event then it might mean that we do evolve the current configuration either
statically (inactive process) or dynamically (without interrupting the process progress). The
purpose of this activity is proceeding, every time, adaptation of the process support to the various
changes in the development context in order to ensure its deployment to software process. The
functional model description of the configuration method is given in the following figure:
Figure 2. The operational model of the configuration process.
4. THE CONFIGURATION MANAGEMENT OF A GUIDANCE PROCESS
The management discipline within the software engineering process allows to develop a reference
basis to any planned configuration. The configuration management is a complex activity that
covers all the steps in a software process, from the conceptual aspects to its configuration and
installation. It includes the initiation techniques and changes control that manage the software
process progress [14, 15, 16].
Process
support
Event
Configuration
Management
Configuration
server
Development
context
Uses
Is based
Configures
Adapted
system « Ready state »
Activates
Deployment
Evaluate
Change
Apply change
Developer’s
request
Occurs
Notifies change
Provides
Results
8. International Journal of Computer Science & Information Technology (IJCSIT) Vol 8, No 3, June 2016
164
The role of configuration management is to identify the configuration items, manage the sequence
and ensure the evolution and any likely change. These activities are usually treated in different
ways depending on the nature and specificity of the objective [15, 16, 25, 26].
In this context, the configuration management of a software process and particularly a guidance
process is a configuration mechanism rigorously linked to the evolution of all development
context factors. This evolution process is influenced by the temporal and contextual elements.
Therefore, it is necessary to define the participating elements and trigger the configuration of a
guidance process, and clarify their functional interdependencies.
We describe graphically the configuration basis of our guidance process defined through five
interrelated elements in figure 3:
Figure 3. The configuration basis of guidance process.
This evolution basis allows, each time, to answer any manifest changes provoked statically or
dynamically in order to design the most appropriate guidance process related to the current
situation. The configuration management of guidance process is useful both for time optimizing
and for the guidance process quality.
The (Re) configuration is invoked by the basic guidance process actors, namely the guidance
process designer or at the user’s request, with different interests ensuring an equilibrium between
the user’s needs in terms of guidance, with either static adaptation at the guidance conceptual
level or dynamic process related to the development context change. The following illustration
defines the basis description of the guidance invocation
Why
Designer PG
User
Dynamic
Static
Event
« Context Change »
At the user’s
initiative
Configuration
Quality
Time optimizing
When
CONFIGURATIO
N BASIS
How
Who
What
Update
Configuration&
Selection
User initiative
UserContext change
Development context
Platform User profile Activity context
9. International Journal of Computer Science & Information Technology (IJCSIT) Vol 8, No 3, June 2016
165
Figure 4. The basis description of the guidance invocation.
The involved configuration process deployment represents the core of the configuration
management. It describes the steps and the contextual sequencing that should be undertaken to
ensure this goal. Therefore, the deployment cycle of a guidance process configuration is
explained via all activities related to the configuration management and their functional
interdependencies (see figure 5.).
Figure 5. The guidance process configuration.
The first activity concerns the configuration and selection of the most coherent
composition, which best responds to the defined development context. Its objective is to
offer the most appropriate guidance to support the current situation.
For this, we should first deal with the dependencies between the guidance process and
description of the development context, to specify the expected guidance service and
constraints to be respected.
The transfer and activation activity consists in transferring the guidance support. It is
invoked at the initiative of the guidance process designer or at the request of the user.
Once installation and transfer problems solved, the activation operation role is to put the
guidance support in the active state, ready to be executed.
The update activity is to resume, adjust or to complete the guidance support
configuration. It is invoked at the user’s initiative or by the guidance process designer
following a change in the development context.
(Re) Configuration
&
Selection
Support end
Update
Deactivation
Transfer
&
Activation
10. International Journal of Computer Science & Information Technology (IJCSIT) Vol 8, No 3, June 2016
166
This activity is almost similar to the (re) configuration, with the difference that the
guidance support is already installed. Finally, the implementation of the update uses the
deactivation activity.
The ''support end'' activity is relative to the end of guidance service offered to users of the
software process in progress.
Deactivation activity is essential before any configuration, update or support end
activities. Its role is to deactivate the support guidance component so that we can perform
the likely changes of some support components
These activities and their functional interdependencies give a rough estimation on the complexity
of the of the guidance process configuration management. This process aims to set up, in respect
of the development context constraints, a first core adaptation of guidance support. Subsequently,
it will have to activate the dynamic adaptation operation with regard to the likely evolutions of
the development environment.
4.1. THE CONFIGURATION OF GUIDANCE PROCESS META MODEL
Our modeling approach CGPM (Configuration of Guidance Process Meta model) is defined
with reference to studied PSEEs features. The aim of our approach is to better respond to the
factors of the development context defined by the three dimensions, the development context,
adaptation form and offered guidance. Each dimension is described through several basic factors
to develop a coherent configuration strategy and provide the most appropriate guidance support to
the current development context.
In this context, our meta-model is based on a conceptual model of a software process enriched by
a configuration model adapted to the guidance process. The configuration model detects any
event of the development context evolution and launches the configuration of guidance process.
The role of the first activity "configuration and selection" is to prepare the guidance support to the
current situation. The second service “transfer and activation” is to put the guidance support in
the active state. The third service "Update" is to provide a way to modify and / or complete the
guidance configuration following a development context change.
The configuration strategy evolves according to the political autonomy given to the guidance
system respecting the application conditions. The implementation of this policy is based on an
adaptation mode expressed by a set of rules of ECA form (Event, Conditions, Actions). For each
execution in the development context, if required conditions related to the context and the
adaptation form then launch guidance configuration strategy to generate the most appropriate
guidance service.
The proposed meta-model aims at generating the adapted guidance interventions to the
development context in relation to the considered factors and specific data for each defined
dimension (see Figure 6)
11. International Journal of Computer Science & Information Technology (IJCSIT) Vol 8, No 3, June 2016
167
.
Figure 6. Configuration of Guidance Process Meta model.
5. THE PRACTICAL INTERPRETATION
Considering the software process model "Activity test", the process "Activity test" in the software
development is composed of several types of tests such as; Integration test and Unitary test. Each
receives as input a test plan and provides a test report. For each type of test, there is a manager,
responsible of the execution.
A performing tree given in Figure 7 describes the activity process «Activity test». We notice that
the activity test starts the execution of sub activities "Unitary test” then “Integration test". The
unitary test launches in parallel the execution of tasks "Test unit"
Development Context
Performance
Adaptation Form
Performance
Event
GuidanceManagement
Guidance Service
Performance
1 : Use
2 : Select
3 : Provide
Configuration
Strategy
Rules
« E.C.A » Consider
Launch
Caused by
Astrategyfor
Material/software
Platform
Developer profile
Activity context
ConditionsActions
Generate
Corrective
Constructive
Automatic
Adaptive
Contextual
Mixed
Update
Configuration
End support
12. International Journal of Computer Science & Information Technology (IJCSIT) Vol 8, No 3, June 2016
168
Figure 7. The activity test process.
To simplify our example, we consider the execution process of the unitary component test. The
application of the activity “Unitary test", requires the list of components. It calls the tool that will
create the necessary environment to carry out the actual execution of the “Unitary test", as the
state diagram, the test variables, etc. ... the activity "Unitary test" launches in parallel the different
tasks "Test unit" where an event signals the beginning of the “Test unit” execution. Finally, the
ended event is broadcast.
The adaptive execution process of the activity "Unitary test", regarding our adaptive guidance
approach is described in Figure 8.
Figure 8. The adaptive execution process “ Unitary test”.
The adaptive guidance is linked to the manager or to each tester according to the current
development context profile defined by its material/software platform, the activity context and
developer profile. We explain this adaptive approach through the following situation; the testers
have the same role “test unit” with identical activity model. However, the developer’s
qualification and the material/software platform specificity differ from one development context
to another. According to the current context, it would require enrich or reduce the appropriate
guidance intervention or generate several possible forms of guidance services.
We consider three situations with tester’s qualification defined respectively as high, medium, and
low. The study case is related to launch the test unit without having all the input data, by selecting
the appropriate test variables and generating the unit test report. The adaptive guidance process
related to each qualification case is described as follows:
1. For a development context with high qualification tester and a high material platform
performance: the tester starts the test unit process on the basis of the defined plan by taking his
proper initiatives. The development context evaluation allows deducing the adaptation form to
Ordered
control flow
3: 3:3: launch
4: launch2: launch
Activity test
Unitary test Integration test
Test unit Test unit
1: launch
Parallel
control flow
Test unit
3: 3:
Test unit Test unit
Parallel
control
3:
Unitary test
AdaptiveGuidance
Tester
AdaptiveGuidance
AdaptiveGuidance
Tester Tester
AdaptiveGuidance
UT
Manager
Test unit
Activityperfor
mer+
Unitary test
+ControledActivit
y *
*1
*
*
+ ProvideguidanceAdaptiveGuidance
Test
*
Manager
Test unit
Test unit
Test unit
Taskperform
er
+
*1
Tester
13. International Journal of Computer Science & Information Technology (IJCSIT) Vol 8, No 3, June 2016
169
retain and the guidance service to provide. In this case, we adopt the adaptation guidance form
and the provided guidance intervention is thus of a corrective order. The corrective
intervention is provided to inform the manager of the setback and remind him of the
corresponding unitary test diagram. The manager remains free to take into account the
intervention.
2. For a development context with an average skill tester and an acceptable material/software
platform performance: the tester starts the test unit process by applying rigorously the defined
test plan. The evaluation of such context results in a contextual guidance form and the
provided guidance intervention is thus of a constructive order. The guidance system analyzes
the current context of the task, evaluates the impact and consequence of the delay caused in
comparison with possible margins and offers a possible solution to the manager (solution: the
guidance proposes to cancel the launch of the current test unit and generates a new execution
plan according to the rate of delay and possible margins). The construction solution is not
definite; the manager should validate it.
3. For a development context with a low qualification tester and a reduced material/software
platform performance: the tester starts the test unit process by applying reliably the defined
test plan. The development context evaluation results in a mixed guidance adaption form and
the provided guidance intervention is thus of an automatic order. The guidance system
analyzes the current context, cancels the launch of the “test unit” task, evaluates the impact
and consequence of the delay caused in comparison with the possible margins and
automatically updates the execution plan of "unitary test" activity.
5.1. The digital application
The practical definition of the adaptive guidance type for each considered profile is deduced
through a quantitative process of the factors in relation to the basic models (material/software
platform, activity context, developer profile). The considered example is processed as follows :
Each profile is semantically described in table (see Table 2). The project manager under the
specification of an ongoing project [17] determines the semantic evaluation and the weighting. To
scan the semantics evaluation, we associate the weighting related to the interest granted to each
attribute.
Table 2. The profiles evaluation.
Development
context
Factors
Context
Profile 1
Context
Profile 2
Context
Profile 3
Context
Profile 4
Context
Profile 5
W[i]
Material/
software
Platform
Development
System Constraint
Low Medium High High Low P2
Software Tools Low Medium Low Provided Provided P1
Memory
Constraint
High Medium Medium High Medium P3
Developer
Profile
Role No effect Classic Critique Critique No effect P4
Competence High Medium Low Low High P1
Familiarity with
Software Process
Quite
Acceptable
Medium Low Low Acceptable P1
Behavior for
guidance
Most
Appropriat
e
Satisfying
Inadequat
e
Adequate Inadequate P2
Activity
Context
Density of tasks
in the activity
Acceptable
Acceptabl
e
Acceptabl
e
Acceptabl
e
Acceptable P3
Complexity Level Medium Medium Medium Medium Medium P2
With W[i]∈∈∈∈ [1, 5]. Where Pi represents the computing value.
14. International Journal of Computer Science & Information Technology (IJCSIT) Vol 8, No 3, June 2016
170
Considering the similar principle such as the COCOMO model [26], the quantification of each
profile’s feature is on the data range] 0, 2 [, (see Table 3). This quantification is usually based on
the impact of each feature.
It is usually done through three levels, described by high, medium or low contribution, applying
the following rules:
1: middle order impact / <1: positive impact / >1: negative impact.
Table 3. The profiles quantification.
Development
context
Factors
Context
Profile 1
Context
Profile 2
Context
Profile 3
Context
Profile 4
Context
Profile 5
W[i]
Material/
software
Platform
Development
System
Constraint
0.75 1.00 1.30 1.30 0.75 1
Software
Tools 1.20 1.00 1.25 0.80 0.80 3
Memory
Constraint 1.40 1.00 1.00 1.60 1.00 2
Developer
Profile
Role 0.40 1.00 1.90 1.70 0.40 4
Competence 0.20 1.00 1.70 1.70 0.25 3
Familiarity
with
Software
Process
0.40 1.00 1.60 1.60 0.30 3
Behavior for
guidance 0.20 0.80 1.70 0.75 1.60 1
Activity
Context
Density of
tasks in the
activity
0.80 0.80 0.80 0.80 0.80 2
Complexity
Level 1.00 1.00 1.00 1.00 1.00 1
In this stage of profiles’ process, and in case of simple profiles’ samples, we can proceed to
associate each considered development context profile to the appropriate guidance adaptation
form and guidance service.
The guidance profile (GP) associated to each profile class is based on the following formula:
GP (Px) = Σ Ai Wi / 2*Σ Wi avec i=1 to n
With :
Ai: the feature value.
Wi: the associated weighting.
Px : the associated profile.
The adaptation form and the guidance profile of each considered development context profile
based on the evaluation of each model and GP value is given by (see Table 4).
15. International Journal of Computer Science & Information Technology (IJCSIT) Vol 8, No 3, June 2016
171
Table 4. The associate guidance profile.
Context
Profile 1
Context
Profile 2
Context
Profile 3
Context
Profile 4
Context
Profile5
Associated
Adaptation
form
Adaptive Contextual Mixed Mixed Adaptive
Guidance
Profile (GP)
0.333 0.485 0.721 0.673 0.315
Associated
guidance profile
Corrective Constructive Automatic Automatic Corrective
It should be noted that the value of GP ranged from 0 to 1 and the range associated with each type
of guidance is defined by the fixed limits to each guidance type. If the range of corrective
guidance is fixed between 0 and 0.35 and the range of the constructive guidance is between 0.36
and 0.65, we automatically associate a corrective guidance to profile P1 and P5, a constructive
guidance to profile P2 and automatic guidance to profile P3and P4.
However, in case of a very important population, and for the aim of optimizing profile classes, it
is recommended to proceed in the gathering and classification of the provided development
profile and reasoning in relation to generated classes.
6. CONCLUSION
Our main purpose in this article is to propose a configuration management of a guidance process
for software process modeling. This configuration is highlighted through a Y description of our
adaptive guidance. This description will focus on three dimensions defined by the
material/software platform, the adaptation form and the provided service. Each dimension
considers several factors to deduce automatically the appropriate guidance process according to
the current development context. The proposed approach concepts are described through a meta-
model denoted CGPM (Configuration of Guidance Process Meta model). The proposed meta-
model aims to generate the adapted guidance support to the development context in relation to the
considered properties and specific data for each defined model.
The contribution of this approach is to institute the configuration management concepts, in order
to be able to proceed, every time, with the adaptation of the guidance support to the various
changes in the development context to ensure its adaptive deployment to software process.
The configuration strategy for the adaptation is done by the dynamic deployment of the provided
guidance process. Intuitively, we consider the defined guidance process configuration through the
sequencing of contextual activities. The guidance strategy evolves according to the political
autonomy given to the guidance process respecting the application conditions. The
implementation of this policy is based on an adaptation mode expressed by a set of rules of ECA
form.
A perspective to this work concerns, at first, the necessity to estimate the productivity and cost
due to the adaptation of guidance system.
In a second step, we will ensure the development of semantic rules that allow swapping through
different guidance profiles, either statically by adjusting the guidance parameters or dynamically
through the development context changes.
16. International Journal of Computer Science & Information Technology (IJCSIT) Vol 8, No 3, June 2016
172
REFERENCES
[1] Ivan Garcia and Carla Pacheco « Toward Automated Support for Software Process Improvement
Initiatives in Small and Medium Size Enterprises ». Book chapter. Software Engineering Research,
Management and Applications 2009 Volume 253/2009, pp. 51–58. c_ Springer-Verlag Berlin
Heidelberg 2009. ISBN: 978-3-642-05440-2.
[2] Kirk, D.C, MacDonell, S.G., & Tempero, E. 2009 Modeling software processes - a focus on
objectives, in Proceedings of the Onward, 2009. Conference. Orlando FL, USA, ACM Press, pp.941-
948.
[3] Benoît COMBEMALE, Xavier CRÉGUT, Alain CAPLAIN et Bernard COULETTE. Towards a
rigorous process modeling with spem. Dans ICEIS (3), pages 530–533, 2006
[4] Hamid Khemissa, Mohamed Ahmed-Nacer, Mourad Daoudi, 2008. A Generic assistance system of
software process. In International Conference on Software Engineering: Software Engineering. SE
2008, Feb 12-14-2008, Innsbruck, Austria.
[5] Calvary, G., Coutaz, J., Thevenin, D., Limbourg, Q., Souchon, N., Bouillon, L., Florins, M.,
Vanderdonckt, J.: Plasticity of User Interfaces: A Revised Reference Framework. In: TAMODIA
2002 (2002).
[6] Joëlle Coutaz, EICS '10. User interface plasticity: model driven engineering to the limit!.
Proceedings of the 2nd ACM SIGCHI symposium on Engineering interactive computing systems.
June 2010.
[7] Coulette B., Crégut X., Dong T. B. T. and Tran D. T., “RHODES, a Process Component Centered
Software Engineering Environment”, ICEIS2000, 2nd International Conference on Enterprise
Information Systems, Stafford, pp 253-260, July 2000.
[8] Jacky Estublier, Jorge Villalobos, Tuyet Le Anh, Sonia Jamal-Sanlaville and German Vega. An
Approach and Framework for Extensible Process Support System. In Proceedings 9th European
Workshop on Software Process Technology (EWSPT 2003), Helsinki, Finland, 2003-09-01.
[9] Hans-Ulrich Kobialka, « Supporting the Software Process in A Process-centered Software
Engineering environment », Upgrade-cepis.org/issues/2004/5/upgrade-v VOL; V n° 5 October 2004.
[10] OMG. Inc. Software and System Process Engineering Meta-Model Specification version 2.0:
Formal/2008-04-01.
[11] Tran Hanh Nhi, Bernard Coulette, Xavier Crégut, Thuy Dong Thi Bich, Thu Tran Dan. Modélisation
du méta-procédé RHODES avec SPEM. Dans : Recherche Informatique Vietnam-Francophone
(RIVF'03), Hanoi, Vietnam, 2003.
[12] Hamid khemissa, Mohamed ahmed nacer & Mourad Oussalah «Adaptive Guidance System for
SPEM ». The First International Conférence on Information Technology Convergence and Services;
ITCS, SIP, JSE 2012 pp. 429-441, Bangalore, India.
[13] Hamid Khemissa, Mohamed Ahmed-Nacer, Mourad Oussalah «Adaptive Guidance based on
Context Profile for Software Process Modeling». Information Technology and Computer Science, ,
July 2012 in MECS 2012.
[14] C. Lueninghoener. "Getting Started with Configuration Management. ;login: issue: April 2011,
Volume 36, Number 2" (PDF). Retrieved 2012-11-23.
[15] IEEE Std-828-2012 IEEE Standard for Configuration Management in Systems and Software
Engineering. 2012. doi:10.1109/IEEESTD.2012.6170935. ISBN 978-0-7381-7232-3.
[16] Ali, U., Kidd, C. Barriers to effective configuration management. Application in a project context:
An empirical investigation, International Journal of Project Management, 2013b;
http://dx.doi.org/10.1016/j.ijproman.2013.06.005.
[17] Grambow, Gregor and Oberhauser, Roy and Reichert, Manfred (2011) Enabling Automatic Process-
aware Collaboration Support in Software Engineering Projects. In: Selected Papers of the
ICSOFT'11 Conference. Communications in Computer and Information Science(CCIS).
[18] Clarke, Paul and O'Connor, Rory (2011) An approach to evaluating software process adaptation. In:
11th International SPICE Conference on Process Improvement and Capability dEtermination, 30
May - 1 jun 2011, Dublin, Ireland. ISBN 978-3-642-21233-8.
[19] Sottet, J.-S., Calvary, G., Coutaz, J., Favre, J.-M. A Model-Driven Engineering Approach for the
Usability of User Interfaces. In Proc. Engineering Interactive Systems (EIS2007), J. Gulliksen et al.
(eds), LNCS 4940, (2007), 140-157
17. International Journal of Computer Science & Information Technology (IJCSIT) Vol 8, No 3, June 2016
173
[20] Ferry, N. Hourdin, G., Lavirotte, S., Rey, G., Tigli, J.- Y., Riveill, M. Models at Runtime: Service
for Device Composition and Adaptation. In 4th International Workshop Models@run.time, Models
2009(MRT09).
[21] Leif Singer, Fernando Figueira Filho, Margaret-Anne Storey (2014) Software engineering at the
speed of light: how developers stay current using twitter. 36 th International Conference on Software
Engineering, ICSE May 2014. Pages 211-221 ACM New York, USA 2014, ISBN: 978-1-4503-
2756-5.
[22] International Standard ISO/IEC 12207 : (2008). Systems and software engineering -- Software life
cycle processes.
[23] International Standard ISO 10007:2003 for Configuration Management
[24] IEEE Standard 828-2012 - for Configuration Management in Systems and Software Engineering
[25] Lindkvist, C., A. Stasis, and J. Whyte, Configuration Management in Complex Engineering Projects.
Procedia CIRP, 2013, Volume 11(0): p. 173-176.
[26] Barry W. Boehm, Chris Abts, A. Winsor Brown, Sunita Chulani, Bradford K. Clark, Ellis Horowitz,
Ray Madachy, Donald J. Reifer, Bert Steece, 2009. Software Cost Estimation with COCOMO II.
Prentice Hall Edition, ISBN: 0137025769, 978013702576.
Authors’ profile
Hamid Khemissa is a full associate professor at Computer Systems Department, Faculty of Electronics and
Computer Science, USTHB University, Algiers. He is member of the software engineering team at
computer system laboratory LSI, USTHB. His current research interests include Software Process
Modeling and Software Modeling Guidace.
Mourad Chabane Oussalah is a full Professor of Computer Science at the University of Nantes and the
chief of the software architecture modeling Team. His research concerns software architecture, object
architecture and their evolution. He worked on several European projects (Esprit, Ist, ...). He is (and was)
the leader of national project (France Telecom, Bouygues telecom, Aker-Yard-STX, ...). He earned a BS
degree in Mathematics in 1983, and Habilitation thesis from the University of Montpellier in 1992.