Software architecture design is an important step of software development. Currently, there are various design methods
available and each is focusing on certain perspective of architecture design. Especially, quality-based methods have received a lot of
attentions and have been well developed for single system architecture design. However, the use of quality-based design methods is
limited in software product line (SPL) because of the complexity and variabilities existing in SPL architecture. With the increasing
attention to software safety, improving software safety has already become a more important issue, especially for safety-critical
systems. This study aims at surveying existing research on Software Product Line Architecture (SPLA) design based on quality
attributes, and to give an overview of the intersection of the areas of software product line architecture design and Safety Driven
Design in order to classifying existing work, and discover open issues for further research. Also this study investigates safety analysis
at the architectural level, and Safety-based Software Product Line Architecture Design (SSPLAD) approaches. Safety-driven software
product line architecture design seems to be a ‘‘discussion” topic. The study shows that there are a large number of SPLA design
methods. However, the use of safety-based design methods is limited in software product lines (SPL) due to the variability property
that can potentially result in a large number of possible systems and because of the complexity existing in safety attribute itself.
A COMPARATIVE ANALYSIS ON SOFTWARE ARCHITECTURE STYLESijfcstjournal
Software architecture is the structural solution that achieves the overall technical and operational requirements for software developments. Software engineers applied software architectures for their software system developments; however, they worry the basic benchmarks in order to select software architecture styles, possible components, integration methods (connectors) and the exact application of each style. The objective of this research work was a comparative analysis of software architecture styles by its weakness and benefits in order to select by the programmer during their design time. Finally, in this study, the researcher has been identified architectural styles, weakness, and Strength and application areas with its component, connector and Interface for the selected architectural styles.
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.
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.
International Journal of Engineering Research and Applications (IJERA) aims to cover the latest outstanding developments in the field of all Engineering Technologies & science.
International Journal of Engineering Research and Applications (IJERA) is a team of researchers not publication services or private publications running the journals for monetary benefits, we are association of scientists and academia who focus only on supporting authors who want to publish their work. The articles published in our journal can be accessed online, all the articles will be archived for real time access.
Our journal system primarily aims to bring out the research talent and the works done by sciaentists, academia, engineers, practitioners, scholars, post graduate students of engineering and science. This journal aims to cover the scientific research in a broader sense and not publishing a niche area of research facilitating researchers from various verticals to publish their papers. It is also aimed to provide a platform for the researchers to publish in a shorter of time, enabling them to continue further All articles published are freely available to scientific researchers in the Government agencies,educators and the general public. We are taking serious efforts to promote our journal across the globe in various ways, we are sure that our journal will act as a scientific platform for all researchers to publish their works online.
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.
A reliability estimation framework for OO design complexity perspective has been developed inthis paper. The proposed framework correlates the object oriented design constructs with complexity and also correlates complexity with reliability. No such framework has been available in the literature that estimates software reliability of OO design by taking complexity into consideration. The framework bridges the gap between object oriented design constructs, complexity and reliability. Framework measures and minimizes the complexity of software design at the early stage of software development life cycle leading to a reliable end product. Reliability and complexity estimation models have been proposed by following the proposed framework. Complexity estimation model has been developed which takes OO design constructs into consideration and proposed reliability estimation models take complexity in consideration for estimating reliability of OO design.
A COMPARATIVE ANALYSIS ON SOFTWARE ARCHITECTURE STYLESijfcstjournal
Software architecture is the structural solution that achieves the overall technical and operational requirements for software developments. Software engineers applied software architectures for their software system developments; however, they worry the basic benchmarks in order to select software architecture styles, possible components, integration methods (connectors) and the exact application of each style. The objective of this research work was a comparative analysis of software architecture styles by its weakness and benefits in order to select by the programmer during their design time. Finally, in this study, the researcher has been identified architectural styles, weakness, and Strength and application areas with its component, connector and Interface for the selected architectural styles.
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.
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.
International Journal of Engineering Research and Applications (IJERA) aims to cover the latest outstanding developments in the field of all Engineering Technologies & science.
International Journal of Engineering Research and Applications (IJERA) is a team of researchers not publication services or private publications running the journals for monetary benefits, we are association of scientists and academia who focus only on supporting authors who want to publish their work. The articles published in our journal can be accessed online, all the articles will be archived for real time access.
Our journal system primarily aims to bring out the research talent and the works done by sciaentists, academia, engineers, practitioners, scholars, post graduate students of engineering and science. This journal aims to cover the scientific research in a broader sense and not publishing a niche area of research facilitating researchers from various verticals to publish their papers. It is also aimed to provide a platform for the researchers to publish in a shorter of time, enabling them to continue further All articles published are freely available to scientific researchers in the Government agencies,educators and the general public. We are taking serious efforts to promote our journal across the globe in various ways, we are sure that our journal will act as a scientific platform for all researchers to publish their works online.
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.
A reliability estimation framework for OO design complexity perspective has been developed inthis paper. The proposed framework correlates the object oriented design constructs with complexity and also correlates complexity with reliability. No such framework has been available in the literature that estimates software reliability of OO design by taking complexity into consideration. The framework bridges the gap between object oriented design constructs, complexity and reliability. Framework measures and minimizes the complexity of software design at the early stage of software development life cycle leading to a reliable end product. Reliability and complexity estimation models have been proposed by following the proposed framework. Complexity estimation model has been developed which takes OO design constructs into consideration and proposed reliability estimation models take complexity in consideration for estimating reliability of OO design.
Multiagent Based Methodologies have become an
important subject of research in advance Software Engineering.
Several methodologies have been proposed as, a theoretical
approach, to facilitate and support the development of complex
distributed systems. An important question when facing the
construction of Agent Applications is deciding which
methodology to follow. Trying to answer this question, a
framework with several criteria is applied in this paper for the
comparative analysis of existing multiagent system
methodologies. The results of the comparative over two of them,
conclude that those methodologies have not reached a sufficient
maturity level to be used by the software industry. The
framework has also proved its utility for the evaluation of any
kind of Multiagent Based Software Engineering Methodology
Systems Analysis,
Systems Design,
Systems Modelling,
Systems Architecture,
System Development and Testing,
System Maintenance and Evolution,
SDLC example (Cloud Service life cycle)
Object-Oriented Analysis techniques covering requirements elicitation and object analysis model development delivered to post-graduate students of Object Oriented Software Engineering
Architectural approaches for implementing Clinical Decision Support Systems i...Luis Felipe Tabares Pérez
Clinical Decision Support Systems (CDSS) were explicitly introduced with the aim of providing knowledge to clinicians in order to influence its decisions and, therefore, improve patients’ health care. Its architectural approaches are based on Cloud Computing, which provides on-demand computing resources over internet. The goal of this presentation is to determine and discuss key issues and approaches involving architectural designs of a CDSS using cloud computing.
The objective of this paper is to provide an insight preview into various
agent oriented methodologies by using an enhanced comparison
framework based on criteria like process related criteria, steps and
techniques related criteria, steps and usability criteria, model related or
“concepts” related criteria, comparison regarding model related criteria
and comparison regarding supportive related criteria. The result also
constitutes inputs collected from the users of the agent oriented
methodologies through a questionnaire based survey.
An interactive approach to requirements prioritization using quality factorsijfcstjournal
As the prevalence of software increases, so does the complexity and the number of requirements assoc
iated
to the software project. This presents a dilemma for the developers to clearly identify and prioriti
ze the
most important requirements in order to del
iver the project in given amount of resources and time.
A
number of prioritization methods have been proposed which provide consistent results, but they are v
ery
difficult and complex to implement in practical scenarios as well as lack proper structure to
analyze the
requirements properly. In this study, the users can provide their requirements in two forms: text ba
sed
story form and use case form.
Moreover, the existing prioritization techniques have a very little or no
interaction with the users. So, in t
his paper an attempt has been made to make the prioritization process
user interactive by adding a second level of prioritization where after the developer has properly a
nalyzed
and ranked the requirements on the basis of quality attributes in the first le
vel, takes the opinion of distinct
user’s about the requirements priority sequence. The developer then calculates the disagreement valu
e
associated with each user sequence in order to find out the final priority sequence.
Fundamentals of object orientation, objects, classes, classification and object models delivered to post-graduate students of Object Oriented Software Engineering.
Multi Agent Based Software Engineering Models : A Review ijseajournal
Software testing is a critical and labor-intensive activity in software engineering. Much research has been
done to help automate test case generation. This research proposes a new approach to structural test case
generation. It uses a specialized genetic algorithm called Dynamic-radius Species-conserving Genetic
Algorithm (DSGA) to find a structurally complete set of test cases for the Triangle Classification algorithm.
DSGA is a Niche Genetic Algorithm (NGA) that uses a short-term memory structure to store optima. Each
individual of the NGA represents the inputs for a test case. The fitness function encourages the algorithm to
locate test cases that cover large areas of the structure of the program. A shared fitness encourages the
NGA to locate other areas of the structure. DSGA is a novel approach to structurally complete test case
generation
DEPENDABLE PRIVACY REQUIREMENTS BY AGILE MODELED LAYERED SECURITY ARCHITECTUR...cscpconf
Software Engineering covers the definition of processes, techniques and models suitable for its
environment to guarantee quality of results. An important design artifact in any software
development project is the Software Architecture. Software Architecture’s important part is the
set of architectural design rules. A primary goal of the architecture is to capture the
architecture design decisions. An important part of these design decisions consists of
architectural design rules In an MDA (Model-Driven Architecture) context, the design of the
system architecture is captured in the models of the system. MDA is known to be layered
approach for modeling the architectural design rules and uses design patterns to improve the
quality of software system. And to include the security to the software system, security patterns
are introduced that offer security at the architectural level. More over, agile software
development methods are used to build secure systems. There are different methods defined in
agile development as extreme programming (XP), scrum, feature driven development (FDD),
test driven development (TDD), etc. Agile processing is includes the phases as agile analysis,
agile design and agile testing. These phases are defined in layers of MDA to provide security at
the modeling level which ensures that security at the system architecture stage will improve the
requirements for that system. Agile modeled Layered Security Architectures increase the
dependability of the architecture in terms of privacy requirements. We validate this with a case
study of dependability of privacy of Web Services Security Architectures, which helps for secure
service oriented security architecture. In this paper the major part is given to model
architectural design rules using MDA so that architects and developers are responsible to
automatic enforcement on the detailed design and easy to understand and use by both of them.
This MDA approach is implemented in use of Agile strategy in three different phases covering
three different layers to provide security to the system. With this procedure a premise
conclusion has been given that with the system security the requirements for that system are
improved. This paper summarizes that security is essential for every system at initial stage and
upon introduction of security at middle stage must lead to the change in the system i.e., an
improvement to system requirements.
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.
Quality Attributes and Software Architectures Emerging Through Agile Developm...Waqas Tariq
Software architectures play an important role as an intermediate stage through which system requirements are translated into full scale working system. The idea of what a system does, what it does not, and different concerns and requirements can be negotiated and expressed clearly through the software architecture. Software architectures exist to enhance and provide quality attributes, while they are quality attributes and their required level of achievement which can offer numerous number of software architectures for a single software system.
We believe that the agile approach to architecting is problematic because of agilists’ beliefs about how to architect a software system, and how critical quality attributes are to achieve a stable yet flexible architecture. Through this research we clarify these issues, and discuss consequences of agile architecting on achieved level of quality attributes. We are going to pursue the answer to how to architect to achieve required level of quality attributes, while adopting an agile process.
Multiagent Based Methodologies have become an
important subject of research in advance Software Engineering.
Several methodologies have been proposed as, a theoretical
approach, to facilitate and support the development of complex
distributed systems. An important question when facing the
construction of Agent Applications is deciding which
methodology to follow. Trying to answer this question, a
framework with several criteria is applied in this paper for the
comparative analysis of existing multiagent system
methodologies. The results of the comparative over two of them,
conclude that those methodologies have not reached a sufficient
maturity level to be used by the software industry. The
framework has also proved its utility for the evaluation of any
kind of Multiagent Based Software Engineering Methodology
Systems Analysis,
Systems Design,
Systems Modelling,
Systems Architecture,
System Development and Testing,
System Maintenance and Evolution,
SDLC example (Cloud Service life cycle)
Object-Oriented Analysis techniques covering requirements elicitation and object analysis model development delivered to post-graduate students of Object Oriented Software Engineering
Architectural approaches for implementing Clinical Decision Support Systems i...Luis Felipe Tabares Pérez
Clinical Decision Support Systems (CDSS) were explicitly introduced with the aim of providing knowledge to clinicians in order to influence its decisions and, therefore, improve patients’ health care. Its architectural approaches are based on Cloud Computing, which provides on-demand computing resources over internet. The goal of this presentation is to determine and discuss key issues and approaches involving architectural designs of a CDSS using cloud computing.
The objective of this paper is to provide an insight preview into various
agent oriented methodologies by using an enhanced comparison
framework based on criteria like process related criteria, steps and
techniques related criteria, steps and usability criteria, model related or
“concepts” related criteria, comparison regarding model related criteria
and comparison regarding supportive related criteria. The result also
constitutes inputs collected from the users of the agent oriented
methodologies through a questionnaire based survey.
An interactive approach to requirements prioritization using quality factorsijfcstjournal
As the prevalence of software increases, so does the complexity and the number of requirements assoc
iated
to the software project. This presents a dilemma for the developers to clearly identify and prioriti
ze the
most important requirements in order to del
iver the project in given amount of resources and time.
A
number of prioritization methods have been proposed which provide consistent results, but they are v
ery
difficult and complex to implement in practical scenarios as well as lack proper structure to
analyze the
requirements properly. In this study, the users can provide their requirements in two forms: text ba
sed
story form and use case form.
Moreover, the existing prioritization techniques have a very little or no
interaction with the users. So, in t
his paper an attempt has been made to make the prioritization process
user interactive by adding a second level of prioritization where after the developer has properly a
nalyzed
and ranked the requirements on the basis of quality attributes in the first le
vel, takes the opinion of distinct
user’s about the requirements priority sequence. The developer then calculates the disagreement valu
e
associated with each user sequence in order to find out the final priority sequence.
Fundamentals of object orientation, objects, classes, classification and object models delivered to post-graduate students of Object Oriented Software Engineering.
Multi Agent Based Software Engineering Models : A Review ijseajournal
Software testing is a critical and labor-intensive activity in software engineering. Much research has been
done to help automate test case generation. This research proposes a new approach to structural test case
generation. It uses a specialized genetic algorithm called Dynamic-radius Species-conserving Genetic
Algorithm (DSGA) to find a structurally complete set of test cases for the Triangle Classification algorithm.
DSGA is a Niche Genetic Algorithm (NGA) that uses a short-term memory structure to store optima. Each
individual of the NGA represents the inputs for a test case. The fitness function encourages the algorithm to
locate test cases that cover large areas of the structure of the program. A shared fitness encourages the
NGA to locate other areas of the structure. DSGA is a novel approach to structurally complete test case
generation
DEPENDABLE PRIVACY REQUIREMENTS BY AGILE MODELED LAYERED SECURITY ARCHITECTUR...cscpconf
Software Engineering covers the definition of processes, techniques and models suitable for its
environment to guarantee quality of results. An important design artifact in any software
development project is the Software Architecture. Software Architecture’s important part is the
set of architectural design rules. A primary goal of the architecture is to capture the
architecture design decisions. An important part of these design decisions consists of
architectural design rules In an MDA (Model-Driven Architecture) context, the design of the
system architecture is captured in the models of the system. MDA is known to be layered
approach for modeling the architectural design rules and uses design patterns to improve the
quality of software system. And to include the security to the software system, security patterns
are introduced that offer security at the architectural level. More over, agile software
development methods are used to build secure systems. There are different methods defined in
agile development as extreme programming (XP), scrum, feature driven development (FDD),
test driven development (TDD), etc. Agile processing is includes the phases as agile analysis,
agile design and agile testing. These phases are defined in layers of MDA to provide security at
the modeling level which ensures that security at the system architecture stage will improve the
requirements for that system. Agile modeled Layered Security Architectures increase the
dependability of the architecture in terms of privacy requirements. We validate this with a case
study of dependability of privacy of Web Services Security Architectures, which helps for secure
service oriented security architecture. In this paper the major part is given to model
architectural design rules using MDA so that architects and developers are responsible to
automatic enforcement on the detailed design and easy to understand and use by both of them.
This MDA approach is implemented in use of Agile strategy in three different phases covering
three different layers to provide security to the system. With this procedure a premise
conclusion has been given that with the system security the requirements for that system are
improved. This paper summarizes that security is essential for every system at initial stage and
upon introduction of security at middle stage must lead to the change in the system i.e., an
improvement to system requirements.
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.
Quality Attributes and Software Architectures Emerging Through Agile Developm...Waqas Tariq
Software architectures play an important role as an intermediate stage through which system requirements are translated into full scale working system. The idea of what a system does, what it does not, and different concerns and requirements can be negotiated and expressed clearly through the software architecture. Software architectures exist to enhance and provide quality attributes, while they are quality attributes and their required level of achievement which can offer numerous number of software architectures for a single software system.
We believe that the agile approach to architecting is problematic because of agilists’ beliefs about how to architect a software system, and how critical quality attributes are to achieve a stable yet flexible architecture. Through this research we clarify these issues, and discuss consequences of agile architecting on achieved level of quality attributes. We are going to pursue the answer to how to architect to achieve required level of quality attributes, while adopting an agile process.
Detecting of routng misbehavion in hybrid wireless networks used and acknowle...AAKASH S
The succeeding wireless network is Hybrid Wireless Networks. It can provide Quality of Service (QoS) requirements in real time
transmission for wireless application. But it stream including critical mission application like military use or emergency
recovery. Hybrid wireless networks is unified mobile ad-hoc network (MANET) and wireless infrastructure networks. It inherits
invalid reservation and race condition problem in Mobile ad-hoc network (MANET). Whereas open medium and wide
distribution of node make vulnerable to malicious attackers in Hybrid wireless networks. How to secure routing in Hybrid
wireless networks. In this paper, we propose a Enhanced Adaptive ACKnowledgment (EAACK)-implement a new intrusiondetection
system for Hybrid wireless networks. It protect Hybrid wireless networks from attacks that have higher malicious
behavior detection rate. Analytical and simulation result based on the real human mobility mode. EAACK can provide high secure performance in terms of Intrusion-detection, overhead, transmission delay
SECURING SOFTWARE DEVELOPMENT STAGES USING ASPECT-ORIENTATION CONCEPTSijseajournal
In the past 10 years, the research community has produced a significant number of design notations to
represent security properties and concepts in a design artifact. The need to improve the security of software
has become a key issue for developers.The security function needs to be incorporated into the software
development process at the requirement, analysis, design, and implementation stages as doing so may help
to smooth integration and to protect systems from attack. Security affects all aspects ofa software program,
which makes the incorporation of security features a crosscutting concern. Therefore, this paper looks at
the feasibility and potential advantages of employing an aspect orientation approach in the software
development lifecycle to ensure efficient integration of security.These notations are aimed at documenting
and analyzing security in a software design model. It also proposes a model called the Aspect-Oriented
Software Security Development Life Cycle (AOSSDLC), which covers arrange of security activities and
deliverables for each development stage. It is concluded that aspect orientation is one of the best options
available for installing security features not least because of the benefit that no changes need to be made to
the existing software structure.
RELIABILITY EVALUATION OF SOFTWARE ARCHITECTURE STYLEScscpconf
In process of software architecture design, different decisions with system-wide impacts are made. An important decision of design stage is the selection of appropriate software architecture style. Since quantitative impacts of styles on quality attributes have not been
studied yet, their application is not systematic. Since Reliability is one of the essential quality requirements of software systems, especially for life-critical ones, one of the main criteria in choosing architecture style of these systems is high reliability. The goal of this study is to
quantify the impact of architecture styles on software reliability that is desired quality of life-critical software. We evaluate styles through reliability block diagram method. First, the reliability equation of each architectural style was computed using of Reliability block diagram
approach. Then, reliability rank of architectural styles is computed by the setting of the number of effective components in a transaction parameter in reliability equation of architectural styles. The main innovation of this article is quantification of impact of styles on software reliability
that is essential for style selection
RELIABILITY EVALUATION OF SOFTWARE ARCHITECTURE STYLEScsandit
In process of software architecture design, different decisions with system-wide impacts are made. An important decision of design stage is the selection of appropriate software
architecture style. Since quantitative impacts of styles on quality attributes have not been studied yet, their application is not systematic. Since Reliability is one of the essential quality
requirements of software systems, especially for life critical ones, one of the main criteria in choosing architecture style of these systems is high reliability. The goal of this study is to
quantify the impact of architecture styles on software reliability that is desired quality of life critical software. We evaluate styles through reliability block diagram method. First, the
reliability equation of each architectural style was computed using of Reliability block diagram approach. Then, reliability rank of architectural styles is computed by setting of the number of effective components in a transaction parameter in reliability equation of architectural styles.
The main innovation of this article is quantification of impact of styles on software reliability that is essential for style selection.
An Empirical Study of the Improved SPLD Framework using Expert Opinion TechniqueIJEACS
Due to the growing need for high-performance and low-cost software applications and the increasing competitiveness, the industry is under pressure to deliver products with low development cost, reduced delivery time and improved quality. To address these demands, researchers have proposed several development methodologies and frameworks. One of the latest methodologies is software product line (SPL) which utilizes the concepts like reusability and variability to deliver successful products with shorter time-to-market, least development and minimum maintenance cost with a high-quality product. This research paper is a validation of our proposed framework, Improved Software Product Line (ISPL), using Expert Opinion Technique. An extensive survey based on a set of questionnaires on various aspects and sub-processes of the ISPLD Framework was carried. Analysis of the empirical data concludes that ISPL shows significant improvements on several aspects of the contemporary SPL frameworks.
EVALUATION OF THE SOFTWARE ARCHITECTURE STYLES FROM MAINTAINABILITY VIEWPOINTcscpconf
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.
A COMPARATIVE ANALYSIS ON SOFTWARE ARCHITECTURE STYLESijfcstjournal
Software architecture is the structural solution that achieves the overall technical and operational
requirements for software developments. Software engineers applied software architectures for their
software system developments; however, they worry the basic benchmarks in order to select software
architecture styles, possible components, integration methods (connectors) and the exact application of
each style.
The objective of this research work was a comparative analysis of software architecture styles by its
weakness and benefits in order to select by the programmer during their design time. Finally, in this study,
the researcher has been identified architectural styles, weakness, and Strength and application areas with
its component, connector and Interface for the selected architectural styles.
A COMPARATIVE ANALYSIS ON SOFTWARE ARCHITECTURE STYLESADEIJ Journal
Software architecture is the structural solution that achieves the overall technical and operational
requirements for software developments. Software engineers applied software architectures for their
software system developments; however, they worry the basic benchmarks in order to select software
architecture styles, possible components, integration methods (connectors) and the exact application of
each style.
The objective of this research work was a comparative analysis of software architecture styles by its
weakness and benefits in order to select by the programmer during their design time. Finally, in this study,
the researcher has been identified architectural styles, weakness, and Strength and application areas with
its component, connector and Interface for the selected architectural styles.
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.
AGILE SOFTWARE ARCHITECTURE INGLOBAL SOFTWARE DEVELOPMENT ENVIRONMENT:SYSTEMA...ijseajournal
In recent years, software development companies started to adopt Global Software Development (GSD) to
explore the benefits of this approach, mainly cost reduction. However, the GSD environment also brings
more complexity and challenges. Some challenges are related to communication aspects like cultural differences, time zone, and language. This paper is the first step in an extensive study to understand if the
software architecture can ease communication in GSD environments. We conducted a Systematic Literature Mapping (SLM) to catalog relevant studies about software architecture and GSD teams and identify
potential practices for use in the software industry. This paper’s findings contribute to the GSD body of
knowledge by exploring the impact of software architecture strategy on the GSD environment. It presents
hypotheses regarding the relationship between software architecture and GSD challenges, which will guide
future research.
Reverse Engineering for Documenting Software Architectures, a Literature ReviewEditor IJCATR
Recently, much research in software engineering focused on reverse engineering of software systems which has become one
of the major engineering trends for software evolution. The objective of this survey paper is to provide a literature review on the
existing reverse engineering methodologies and approaches for documenting the architecture of software systems. The survey process
was based on selecting the most common approaches that form the current state of the art in documenting software architectures. We
discuss the limitations of these approaches and highlight the main directions for future research and describe specific open issues for
research.
ANALYZABILITY METRIC FOR MAINTAINABILITY OF OBJECT ORIENTED SOFTWARE SYSTEMIAEME Publication
Analyzability is one of the major factors in the prediction of maintainability aspect that can improve the quality of the intended software solution in an appropriate manner. In fact, the right analyzability measure will go a long way in decreasing the inadequacies and deficiencies through identification of the modified parts and failure causes in the software system. The analyzability metric identification is not possible in every software solution because of its non- functional nature in the real world, but in object-oriented software system there is an opportunity to find out the analyzability metric in the form of class inheritance hierarchies. In this research paper, the researcher measured the analyzability factor for the object-oriented software systems and also validated in accordance with the famed weyker’s properties. The proposed analyzability metric here is intended to lead the new developments in object-oriented software maintainability parameter in future and help the new researchers do their research the right way thus eventually achieving the quality aspect of the objectoriented software system and fulfilling the needs of the users.
DEPENDABLE WEB SERVICES SECURITY ARCHITECTURE DEVELOPMENT THEORETICAL AND PRA...cscpconf
This research “Designing Dependable Web Services Security Architecture Solutions” addresses
the innovative idea of Web Services Security Engineering using Web Services Security
Architecture with a research motivation of Secure Service Oriented Analysis and Design. It deals
with Web Services Security Architecture for Web Services Secure application design, for
Authentication and authorization, using Model Driven Architecture (MDA) based Agile Modeled
Layered Security Architecture design, which eventually results in enhanced dependable (privacy)
management. All the above findings are validated with appropriate case studies of Web 2.0
Services, its extension to Web 2.0 Mashups Spatial Web Services and various financial
applications. In this paper we discuss about Research Methodology for Designing Dependable Agile Layered Security Architectures, with validations on Spatial Web Services Case study.
A REVIEW OF SECURITY INTEGRATION TECHNIQUE IN AGILE SOFTWARE DEVELOPMENTijseajournal
Agile software development has gained a lot of popularity in the software industry due to its iterative and
incremental approach as well as user involvement. Agile has also been criticized due to lack of its ability to
deliver secure software. In this paper, extensive literature has been performed, in order to highlight the
existing security issues in agile software development. Majority of challenges reported in literature,
occurred due to lack of involvement of security expert. Improving security of a software system without
damaging the real essence of Agile can achieved with the continuous involvement of security engineer
throughout development lifecycle with its defined role and responsibilities.
Similar to Safety-driven Software Product Line architectures Design, A Survey Paper (20)
Text Mining in Digital Libraries using OKAPI BM25 ModelEditor IJCATR
The emergence of the internet has made vast amounts of information available and easily accessible online. As a result, most libraries have digitized their content in order to remain relevant to their users and to keep pace with the advancement of the internet. However, these digital libraries have been criticized for using inefficient information retrieval models that do not perform relevance ranking to the retrieved results. This paper proposed the use of OKAPI BM25 model in text mining so as means of improving relevance ranking of digital libraries. Okapi BM25 model was selected because it is a probability-based relevance ranking algorithm. A case study research was conducted and the model design was based on information retrieval processes. The performance of Boolean, vector space, and Okapi BM25 models was compared for data retrieval. Relevant ranked documents were retrieved and displayed at the OPAC framework search page. The results revealed that Okapi BM 25 outperformed Boolean model and Vector Space model. Therefore, this paper proposes the use of Okapi BM25 model to reward terms according to their relative frequencies in a document so as to improve the performance of text mining in digital libraries.
Green Computing, eco trends, climate change, e-waste and eco-friendlyEditor IJCATR
This study focused on the practice of using computing resources more efficiently while maintaining or increasing overall performance. Sustainable IT services require the integration of green computing practices such as power management, virtualization, improving cooling technology, recycling, electronic waste disposal, and optimization of the IT infrastructure to meet sustainability requirements. Studies have shown that costs of power utilized by IT departments can approach 50% of the overall energy costs for an organization. While there is an expectation that green IT should lower costs and the firm’s impact on the environment, there has been far less attention directed at understanding the strategic benefits of sustainable IT services in terms of the creation of customer value, business value and societal value. This paper provides a review of the literature on sustainable IT, key areas of focus, and identifies a core set of principles to guide sustainable IT service design.
Policies for Green Computing and E-Waste in NigeriaEditor IJCATR
Computers today are an integral part of individuals’ lives all around the world, but unfortunately these devices are toxic to the environment given the materials used, their limited battery life and technological obsolescence. Individuals are concerned about the hazardous materials ever present in computers, even if the importance of various attributes differs, and that a more environment -friendly attitude can be obtained through exposure to educational materials. In this paper, we aim to delineate the problem of e-waste in Nigeria and highlight a series of measures and the advantage they herald for our country and propose a series of action steps to develop in these areas further. It is possible for Nigeria to have an immediate economic stimulus and job creation while moving quickly to abide by the requirements of climate change legislation and energy efficiency directives. The costs of implementing energy efficiency and renewable energy measures are minimal as they are not cash expenditures but rather investments paid back by future, continuous energy savings.
Performance Evaluation of VANETs for Evaluating Node Stability in Dynamic Sce...Editor IJCATR
Vehicular ad hoc networks (VANETs) are a favorable area of exploration which empowers the interconnection amid the movable vehicles and between transportable units (vehicles) and road side units (RSU). In Vehicular Ad Hoc Networks (VANETs), mobile vehicles can be organized into assemblage to promote interconnection links. The assemblage arrangement according to dimensions and geographical extend has serious influence on attribute of interaction .Vehicular ad hoc networks (VANETs) are subclass of mobile Ad-hoc network involving more complex mobility patterns. Because of mobility the topology changes very frequently. This raises a number of technical challenges including the stability of the network .There is a need for assemblage configuration leading to more stable realistic network. The paper provides investigation of various simulation scenarios in which cluster using k-means algorithm are generated and their numbers are varied to find the more stable configuration in real scenario of road.
Optimum Location of DG Units Considering Operation ConditionsEditor IJCATR
The optimal sizing and placement of Distributed Generation units (DG) are becoming very attractive to researchers these days. In this paper a two stage approach has been used for allocation and sizing of DGs in distribution system with time varying load model. The strategic placement of DGs can help in reducing energy losses and improving voltage profile. The proposed work discusses time varying loads that can be useful for selecting the location and optimizing DG operation. The method has the potential to be used for integrating the available DGs by identifying the best locations in a power system. The proposed method has been demonstrated on 9-bus test system.
Analysis of Comparison of Fuzzy Knn, C4.5 Algorithm, and Naïve Bayes Classifi...Editor IJCATR
Early detection of diabetes mellitus (DM) can prevent or inhibit complication. There are several laboratory test that must be done to detect DM. The result of this laboratory test then converted into data training. Data training used in this study generated from UCI Pima Database with 6 attributes that were used to classify positive or negative diabetes. There are various classification methods that are commonly used, and in this study three of them were compared, which were fuzzy KNN, C4.5 algorithm and Naïve Bayes Classifier (NBC) with one identical case. The objective of this study was to create software to classify DM using tested methods and compared the three methods based on accuracy, precision, and recall. The results showed that the best method was Fuzzy KNN with average and maximum accuracy reached 96% and 98%, respectively. In second place, NBC method had respective average and maximum accuracy of 87.5% and 90%. Lastly, C4.5 algorithm had average and maximum accuracy of 79.5% and 86%, respectively.
Web Scraping for Estimating new Record from Source SiteEditor IJCATR
Study in the Competitive field of Intelligent, and studies in the field of Web Scraping, have a symbiotic relationship mutualism. In the information age today, the website serves as a main source. The research focus is on how to get data from websites and how to slow down the intensity of the download. The problem that arises is the website sources are autonomous so that vulnerable changes the structure of the content at any time. The next problem is the system intrusion detection snort installed on the server to detect bot crawler. So the researchers propose the use of the methods of Mining Data Records and the method of Exponential Smoothing so that adaptive to changes in the structure of the content and do a browse or fetch automatically follow the pattern of the occurrences of the news. The results of the tests, with the threshold 0.3 for MDR and similarity threshold score 0.65 for STM, using recall and precision values produce f-measure average 92.6%. While the results of the tests of the exponential estimation smoothing using ? = 0.5 produces MAE 18.2 datarecord duplicate. It slowed down to 3.6 datarecord from 21.8 datarecord results schedule download/fetch fix in an average time of occurrence news.
Evaluating Semantic Similarity between Biomedical Concepts/Classes through S...Editor IJCATR
Most of the existing semantic similarity measures that use ontology structure as their primary source can measure semantic similarity between concepts/classes using single ontology. The ontology-based semantic similarity techniques such as structure-based semantic similarity techniques (Path Length Measure, Wu and Palmer’s Measure, and Leacock and Chodorow’s measure), information content-based similarity techniques (Resnik’s measure, Lin’s measure), and biomedical domain ontology techniques (Al-Mubaid and Nguyen’s measure (SimDist)) were evaluated relative to human experts’ ratings, and compared on sets of concepts using the ICD-10 “V1.0” terminology within the UMLS. The experimental results validate the efficiency of the SemDist technique in single ontology, and demonstrate that SemDist semantic similarity techniques, compared with the existing techniques, gives the best overall results of correlation with experts’ ratings.
Semantic Similarity Measures between Terms in the Biomedical Domain within f...Editor IJCATR
The techniques and tests are tools used to define how measure the goodness of ontology or its resources. The similarity between biomedical classes/concepts is an important task for the biomedical information extraction and knowledge discovery. However, most of the semantic similarity techniques can be adopted to be used in the biomedical domain (UMLS). Many experiments have been conducted to check the applicability of these measures. In this paper, we investigate to measure semantic similarity between two terms within single ontology or multiple ontologies in ICD-10 “V1.0” as primary source, and compare my results to human experts score by correlation coefficient.
A Strategy for Improving the Performance of Small Files in Openstack Swift Editor IJCATR
This is an effective way to improve the storage access performance of small files in Openstack Swift by adding an aggregate storage module. Because Swift will lead to too much disk operation when querying metadata, the transfer performance of plenty of small files is low. In this paper, we propose an aggregated storage strategy (ASS), and implement it in Swift. ASS comprises two parts which include merge storage and index storage. At the first stage, ASS arranges the write request queue in chronological order, and then stores objects in volumes. These volumes are large files that are stored in Swift actually. During the short encounter time, the object-to-volume mapping information is stored in Key-Value store at the second stage. The experimental results show that the ASS can effectively improve Swift's small file transfer performance.
Integrated System for Vehicle Clearance and RegistrationEditor IJCATR
Efficient management and control of government's cash resources rely on government banking arrangements. Nigeria, like many low income countries, employed fragmented systems in handling government receipts and payments. Later in 2016, Nigeria implemented a unified structure as recommended by the IMF, where all government funds are collected in one account would reduce borrowing costs, extend credit and improve government's fiscal policy among other benefits to government. This situation motivated us to embark on this research to design and implement an integrated system for vehicle clearance and registration. This system complies with the new Treasury Single Account policy to enable proper interaction and collaboration among five different level agencies (NCS, FRSC, SBIR, VIO and NPF) saddled with vehicular administration and activities in Nigeria. Since the system is web based, Object Oriented Hypermedia Design Methodology (OOHDM) is used. Tools such as Php, JavaScript, css, html, AJAX and other web development technologies were used. The result is a web based system that gives proper information about a vehicle starting from the exact date of importation to registration and renewal of licensing. Vehicle owner information, custom duty information, plate number registration details, etc. will also be efficiently retrieved from the system by any of the agencies without contacting the other agency at any point in time. Also number plate will no longer be the only means of vehicle identification as it is presently the case in Nigeria, because the unified system will automatically generate and assigned a Unique Vehicle Identification Pin Number (UVIPN) on payment of duty in the system to the vehicle and the UVIPN will be linked to the various agencies in the management information system.
Assessment of the Efficiency of Customer Order Management System: A Case Stu...Editor IJCATR
The Supermarket Management System deals with the automation of buying and selling of good and services. It includes both sales and purchase of items. The project Supermarket Management System is to be developed with the objective of making the system reliable, easier, fast, and more informative.
Energy-Aware Routing in Wireless Sensor Network Using Modified Bi-Directional A*Editor IJCATR
Energy is a key component in the Wireless Sensor Network (WSN)[1]. The system will not be able to run according to its function without the availability of adequate power units. One of the characteristics of wireless sensor network is Limitation energy[2]. A lot of research has been done to develop strategies to overcome this problem. One of them is clustering technique. The popular clustering technique is Low Energy Adaptive Clustering Hierarchy (LEACH)[3]. In LEACH, clustering techniques are used to determine Cluster Head (CH), which will then be assigned to forward packets to Base Station (BS). In this research, we propose other clustering techniques, which utilize the Social Network Analysis approach theory of Betweeness Centrality (BC) which will then be implemented in the Setup phase. While in the Steady-State phase, one of the heuristic searching algorithms, Modified Bi-Directional A* (MBDA *) is implemented. The experiment was performed deploy 100 nodes statically in the 100x100 area, with one Base Station at coordinates (50,50). To find out the reliability of the system, the experiment to do in 5000 rounds. The performance of the designed routing protocol strategy will be tested based on network lifetime, throughput, and residual energy. The results show that BC-MBDA * is better than LEACH. This is influenced by the ways of working LEACH in determining the CH that is dynamic, which is always changing in every data transmission process. This will result in the use of energy, because they always doing any computation to determine CH in every transmission process. In contrast to BC-MBDA *, CH is statically determined, so it can decrease energy usage.
Security in Software Defined Networks (SDN): Challenges and Research Opportun...Editor IJCATR
In networks, the rapidly changing traffic patterns of search engines, Internet of Things (IoT) devices, Big Data and data centers has thrown up new challenges for legacy; existing networks; and prompted the need for a more intelligent and innovative way to dynamically manage traffic and allocate limited network resources. Software Defined Network (SDN) which decouples the control plane from the data plane through network vitalizations aims to address these challenges. This paper has explored the SDN architecture and its implementation with the OpenFlow protocol. It has also assessed some of its benefits over traditional network architectures, security concerns and how it can be addressed in future research and related works in emerging economies such as Nigeria.
Measure the Similarity of Complaint Document Using Cosine Similarity Based on...Editor IJCATR
Report handling on "LAPOR!" (Laporan, Aspirasi dan Pengaduan Online Rakyat) system depending on the system administrator who manually reads every incoming report [3]. Read manually can lead to errors in handling complaints [4] if the data flow is huge and grows rapidly, it needs at least three days to prepare a confirmation and it sensitive to inconsistencies [3]. In this study, the authors propose a model that can measure the identities of the Query (Incoming) with Document (Archive). The authors employed Class-Based Indexing term weighting scheme, and Cosine Similarities to analyse document similarities. CoSimTFIDF, CoSimTFICF and CoSimTFIDFICF values used in classification as feature for K-Nearest Neighbour (K-NN) classifier. The optimum result evaluation is pre-processing employ 75% of training data ratio and 25% of test data with CoSimTFIDF feature. It deliver a high accuracy 84%. The k = 5 value obtain high accuracy 84.12%
Hangul Recognition Using Support Vector MachineEditor IJCATR
The recognition of Hangul Image is more difficult compared with that of Latin. It could be recognized from the structural arrangement. Hangul is arranged from two dimensions while Latin is only from the left to the right. The current research creates a system to convert Hangul image into Latin text in order to use it as a learning material on reading Hangul. In general, image recognition system is divided into three steps. The first step is preprocessing, which includes binarization, segmentation through connected component-labeling method, and thinning with Zhang Suen to decrease some pattern information. The second is receiving the feature from every single image, whose identification process is done through chain code method. The third is recognizing the process using Support Vector Machine (SVM) with some kernels. It works through letter image and Hangul word recognition. It consists of 34 letters, each of which has 15 different patterns. The whole patterns are 510, divided into 3 data scenarios. The highest result achieved is 94,7% using SVM kernel polynomial and radial basis function. The level of recognition result is influenced by many trained data. Whilst the recognition process of Hangul word applies to the type 2 Hangul word with 6 different patterns. The difference of these patterns appears from the change of the font type. The chosen fonts for data training are such as Batang, Dotum, Gaeul, Gulim, Malgun Gothic. Arial Unicode MS is used to test the data. The lowest accuracy is achieved through the use of SVM kernel radial basis function, which is 69%. The same result, 72 %, is given by the SVM kernel linear and polynomial.
Application of 3D Printing in EducationEditor IJCATR
This paper provides a review of literature concerning the application of 3D printing in the education system. The review identifies that 3D Printing is being applied across the Educational levels [1] as well as in Libraries, Laboratories, and Distance education systems. The review also finds that 3D Printing is being used to teach both students and trainers about 3D Printing and to develop 3D Printing skills.
Survey on Energy-Efficient Routing Algorithms for Underwater Wireless Sensor ...Editor IJCATR
In underwater environment, for retrieval of information the routing mechanism is used. In routing mechanism there are three to four types of nodes are used, one is sink node which is deployed on the water surface and can collect the information, courier/super/AUV or dolphin powerful nodes are deployed in the middle of the water for forwarding the packets, ordinary nodes are also forwarder nodes which can be deployed from bottom to surface of the water and source nodes are deployed at the seabed which can extract the valuable information from the bottom of the sea. In underwater environment the battery power of the nodes is limited and that power can be enhanced through better selection of the routing algorithm. This paper focuses the energy-efficient routing algorithms for their routing mechanisms to prolong the battery power of the nodes. This paper also focuses the performance analysis of the energy-efficient algorithms under which we can examine the better performance of the route selection mechanism which can prolong the battery power of the node
Comparative analysis on Void Node Removal Routing algorithms for Underwater W...Editor IJCATR
The designing of routing algorithms faces many challenges in underwater environment like: propagation delay, acoustic channel behaviour, limited bandwidth, high bit error rate, limited battery power, underwater pressure, node mobility, localization 3D deployment, and underwater obstacles (voids). This paper focuses the underwater voids which affects the overall performance of the entire network. The majority of the researchers have used the better approaches for removal of voids through alternate path selection mechanism but still research needs improvement. This paper also focuses the architecture and its operation through merits and demerits of the existing algorithms. This research article further focuses the analytical method of the performance analysis of existing algorithms through which we found the better approach for removal of voids
Decay Property for Solutions to Plate Type Equations with Variable CoefficientsEditor IJCATR
In this paper we consider the initial value problem for a plate type equation with variable coefficients and memory in
1 n R n ), which is of regularity-loss property. By using spectrally resolution, we study the pointwise estimates in the spectral
space of the fundamental solution to the corresponding linear problem. Appealing to this pointwise estimates, we obtain the global
existence and the decay estimates of solutions to the semilinear problem by employing the fixed point theorem
DevOps and Testing slides at DASA ConnectKari Kakkonen
My and Rik Marselis slides at 30.5.2024 DASA Connect conference. We discuss about what is testing, then what is agile testing and finally what is Testing in DevOps. Finally we had lovely workshop with the participants trying to find out different ways to think about quality and testing in different parts of the DevOps infinity loop.
Software Delivery At the Speed of AI: Inflectra Invests In AI-Powered QualityInflectra
In this insightful webinar, Inflectra explores how artificial intelligence (AI) is transforming software development and testing. Discover how AI-powered tools are revolutionizing every stage of the software development lifecycle (SDLC), from design and prototyping to testing, deployment, and monitoring.
Learn about:
• The Future of Testing: How AI is shifting testing towards verification, analysis, and higher-level skills, while reducing repetitive tasks.
• Test Automation: How AI-powered test case generation, optimization, and self-healing tests are making testing more efficient and effective.
• Visual Testing: Explore the emerging capabilities of AI in visual testing and how it's set to revolutionize UI verification.
• Inflectra's AI Solutions: See demonstrations of Inflectra's cutting-edge AI tools like the ChatGPT plugin and Azure Open AI platform, designed to streamline your testing process.
Whether you're a developer, tester, or QA professional, this webinar will give you valuable insights into how AI is shaping the future of software delivery.
Builder.ai Founder Sachin Dev Duggal's Strategic Approach to Create an Innova...Ramesh Iyer
In today's fast-changing business world, Companies that adapt and embrace new ideas often need help to keep up with the competition. However, fostering a culture of innovation takes much work. It takes vision, leadership and willingness to take risks in the right proportion. Sachin Dev Duggal, co-founder of Builder.ai, has perfected the art of this balance, creating a company culture where creativity and growth are nurtured at each stage.
Neuro-symbolic is not enough, we need neuro-*semantic*Frank van Harmelen
Neuro-symbolic (NeSy) AI is on the rise. However, simply machine learning on just any symbolic structure is not sufficient to really harvest the gains of NeSy. These will only be gained when the symbolic structures have an actual semantics. I give an operational definition of semantics as “predictable inference”.
All of this illustrated with link prediction over knowledge graphs, but the argument is general.
State of ICS and IoT Cyber Threat Landscape Report 2024 previewPrayukth K V
The IoT and OT threat landscape report has been prepared by the Threat Research Team at Sectrio using data from Sectrio, cyber threat intelligence farming facilities spread across over 85 cities around the world. In addition, Sectrio also runs AI-based advanced threat and payload engagement facilities that serve as sinks to attract and engage sophisticated threat actors, and newer malware including new variants and latent threats that are at an earlier stage of development.
The latest edition of the OT/ICS and IoT security Threat Landscape Report 2024 also covers:
State of global ICS asset and network exposure
Sectoral targets and attacks as well as the cost of ransom
Global APT activity, AI usage, actor and tactic profiles, and implications
Rise in volumes of AI-powered cyberattacks
Major cyber events in 2024
Malware and malicious payload trends
Cyberattack types and targets
Vulnerability exploit attempts on CVEs
Attacks on counties – USA
Expansion of bot farms – how, where, and why
In-depth analysis of the cyber threat landscape across North America, South America, Europe, APAC, and the Middle East
Why are attacks on smart factories rising?
Cyber risk predictions
Axis of attacks – Europe
Systemic attacks in the Middle East
Download the full report from here:
https://sectrio.com/resources/ot-threat-landscape-reports/sectrio-releases-ot-ics-and-iot-security-threat-landscape-report-2024/
Connector Corner: Automate dynamic content and events by pushing a buttonDianaGray10
Here is something new! In our next Connector Corner webinar, we will demonstrate how you can use a single workflow to:
Create a campaign using Mailchimp with merge tags/fields
Send an interactive Slack channel message (using buttons)
Have the message received by managers and peers along with a test email for review
But there’s more:
In a second workflow supporting the same use case, you’ll see:
Your campaign sent to target colleagues for approval
If the “Approve” button is clicked, a Jira/Zendesk ticket is created for the marketing design team
But—if the “Reject” button is pushed, colleagues will be alerted via Slack message
Join us to learn more about this new, human-in-the-loop capability, brought to you by Integration Service connectors.
And...
Speakers:
Akshay Agnihotri, Product Manager
Charlie Greenberg, Host
"Impact of front-end architecture on development cost", Viktor TurskyiFwdays
I have heard many times that architecture is not important for the front-end. Also, many times I have seen how developers implement features on the front-end just following the standard rules for a framework and think that this is enough to successfully launch the project, and then the project fails. How to prevent this and what approach to choose? I have launched dozens of complex projects and during the talk we will analyze which approaches have worked for me and which have not.
LF Energy Webinar: Electrical Grid Modelling and Simulation Through PowSyBl -...DanBrown980551
Do you want to learn how to model and simulate an electrical network from scratch in under an hour?
Then welcome to this PowSyBl workshop, hosted by Rte, the French Transmission System Operator (TSO)!
During the webinar, you will discover the PowSyBl ecosystem as well as handle and study an electrical network through an interactive Python notebook.
PowSyBl is an open source project hosted by LF Energy, which offers a comprehensive set of features for electrical grid modelling and simulation. Among other advanced features, PowSyBl provides:
- A fully editable and extendable library for grid component modelling;
- Visualization tools to display your network;
- Grid simulation tools, such as power flows, security analyses (with or without remedial actions) and sensitivity analyses;
The framework is mostly written in Java, with a Python binding so that Python developers can access PowSyBl functionalities as well.
What you will learn during the webinar:
- For beginners: discover PowSyBl's functionalities through a quick general presentation and the notebook, without needing any expert coding skills;
- For advanced developers: master the skills to efficiently apply PowSyBl functionalities to your real-world scenarios.
Essentials of Automations: Optimizing FME Workflows with ParametersSafe Software
Are you looking to streamline your workflows and boost your projects’ efficiency? Do you find yourself searching for ways to add flexibility and control over your FME workflows? If so, you’re in the right place.
Join us for an insightful dive into the world of FME parameters, a critical element in optimizing workflow efficiency. This webinar marks the beginning of our three-part “Essentials of Automation” series. This first webinar is designed to equip you with the knowledge and skills to utilize parameters effectively: enhancing the flexibility, maintainability, and user control of your FME projects.
Here’s what you’ll gain:
- Essentials of FME Parameters: Understand the pivotal role of parameters, including Reader/Writer, Transformer, User, and FME Flow categories. Discover how they are the key to unlocking automation and optimization within your workflows.
- Practical Applications in FME Form: Delve into key user parameter types including choice, connections, and file URLs. Allow users to control how a workflow runs, making your workflows more reusable. Learn to import values and deliver the best user experience for your workflows while enhancing accuracy.
- Optimization Strategies in FME Flow: Explore the creation and strategic deployment of parameters in FME Flow, including the use of deployment and geometry parameters, to maximize workflow efficiency.
- Pro Tips for Success: Gain insights on parameterizing connections and leveraging new features like Conditional Visibility for clarity and simplicity.
We’ll wrap up with a glimpse into future webinars, followed by a Q&A session to address your specific questions surrounding this topic.
Don’t miss this opportunity to elevate your FME expertise and drive your projects to new heights of efficiency.
How world-class product teams are winning in the AI era by CEO and Founder, P...
Safety-driven Software Product Line architectures Design, A Survey Paper
1. International Journal of Computer Applications Technology and Research
Volume 5–Issue 10, 627-640, 2016, ISSN:-2319–8656
www.ijcat.com 627
Safety-driven Software Product Line architectures
Design, A Survey Paper
Mozamil Ebnauf Elgodbe
College of Graduate Studies, Computer Science and
Information Technology
Sudan University of science & technology,
Khartoum, Sudan
Hany H. Ammar
Lane Department of Computer Science and
Electrical Engineering, College of Engineering and
Mineral Resources West Virginia University
Morgantown, USA
Abstract: Software architecture design is an important step of software development. Currently, there are various design methods
available and each is focusing on certain perspective of architecture design. Especially, quality-based methods have received a lot of
attentions and have been well developed for single system architecture design. However, the use of quality-based design methods is
limited in software product line (SPL) because of the complexity and variabilities existing in SPL architecture. With the increasing
attention to software safety, improving software safety has already become a more important issue, especially for safety-critical
systems. This study aims at surveying existing research on Software Product Line Architecture (SPLA) design based on quality
attributes, and to give an overview of the intersection of the areas of software product line architecture design and Safety Driven
Design in order to classifying existing work, and discover open issues for further research. Also this study investigates safety analysis
at the architectural level, and Safety-based Software Product Line Architecture Design (SSPLAD) approaches. Safety-driven software
product line architecture design seems to be a ‘‘discussion” topic. The study shows that there are a large number of SPLA design
methods. However, the use of safety-based design methods is limited in software product lines (SPL) due to the variability property
that can potentially result in a large number of possible systems and because of the complexity existing in safety attribute itself.
Keywords: Software Architecture Quality attributes; Safety analysis; Architectural Design; Software Product Line Architectures;
Safety-driven software product line architecture design.
1. INTRODUCTION
A software architecture is the structure of the software system.
"It describes the software elements, their characteristics and
they interact with each other" [1],[2]. A qualified software
architecture provides a blueprint for system construction and
composition. It is a main factor to a successful software
development [3]. There are many challenges in software
architecture design for example, modeling the non-functional
requirements, especially those requirements on the quality of
the software.
Non-functional requirements and quality attributes (e.g.
maintainability, performance, reliability, safety and product
evolution) are important parameters of software products.
Quality requirements of a system serve as a bridge between
business goals and software architectures [3]. There is a major
role of Software architecture in the determination of software
quality [4][5].
Importance of software architecture “Software architecture
is not only concerned with structure and behavior, but also
with usage, functionality, performance, resilience, reuse,
comprehensibility, economic and technology constraints and
tradeoffs” - The Rational Unified Process, 2002.
Software Product Line Architectures design The main task
of the software product line architecture design is to develop
the reference architecture which represents the base structure
of the member products [6]. There are several methods have
been established to create PLAs[7].
Safety-driven SPLA Design The current work in systems
engineering methods has focused on supporting a safety-
centric design process [8]. The General idea of these
approaches is that safety should be a driver for design.
Problem Description and Motivation Software architecture
design is an important or a critical step of software
development. The software architecture community generally
believes that quality attributes (such as performance, usability,
security, reliability and modifiability) of a software system are
primarily achieved through attention to software architecture.
This means that the design decisions embodied by software
architecture are strongly influenced by the need to achieve
quality attribute goals.
Nowadays, there are various design methods available and
each is focusing on certain perspective of architecture design.
The quality-based methods have received a lot of attentions
and have been well developed for single system architecture
design. However, the use of quality-based design methods is
limited in software product line (SPL) because of the
complexity and variabilities existing in SPL architecture [9].
There are increasing in the attention of software safety, so
how to improve software safety has already become a more
important concerned issue, especially for the safety-critical
systems [10]. Currently, the influence of architecture in
assurance of software safety is being increasingly recognized.
The design of the safety at the architecture level can
effectively improve software or system safety [10].
Consequently, the research activities are scattered across
many research communities, system domains (such as
embedded systems or information systems), and quality
2. International Journal of Computer Applications Technology and Research
Volume 5–Issue 10, 627-640, 2016, ISSN:-2319–8656
www.ijcat.com 628
attributes. Similar approaches are proposed in multiple
domains without being aware of each other.
This study aims at surveying existing research on Software
Product Line Architecture (SPLA) design based on quality
attributes, and to give an overview of the intersection of the
areas of software product line architecture design and Safety
Driven Design in order to classifying existing work, and
discover open issues for further research.
Research Approach and Contribution
To connect the knowledge and provide a comprehensive
overview of the current state of the art, this article provides a
systematic literature review of the existing research on
Software Product Line Architecture (SPLA) design based on
quality attributes in order to identify useful approaches and
needs for future research. Also this study investigates safety
analysis at the architectural level, and safety-based software
Product Line Architecture Design (SSPLAD) approaches.
Also, the purpose of this investigation was to study and
compare the existing methods or approaches for the design of
software product line architectures. The intention of this paper
is not to provide an exhaustive survey on the area but provide
a state-of-the-art of current PLA practices and help others to
understand and contrast alternative approaches to product line
design. This paper does neither guide in selecting the right
approach for PLA design but opens up a basis for creation of
such a decision tool.
In general, with the survey we aim to achieve the following
objectives:
to give an overview of the intersection of the areas
of software product line architecture design and
Safety attribute.
provide a basic classification framework in form of
a taxonomy to classify existing architecture design
approaches.
provide an overview of the current state of the art in
the product line architecture design domain.
point out current trends, gaps, and directions for
future research.
Organization. The rest of the paper is organized as follows.
First, Section 2 presents the Overview of PLA design, The
Quality-based Design, and Safety-driven design. The section
3 outlines the research method and the underlying protocol for
the systematic literature review. The first contribution of this
article, a taxonomy or architecture design approaches that has
been derived from an iterative analysis of the existing
research literature is presented in Section 4. The second
contribution, a classification of existing architecture design
approaches according to this taxonomy, is presented in
Section 5. Finally, Section 6 identifies future research
directions based on the survey results and Section 7 presents
the conclusions.
2. OVERVIEW
In this section we present an overview of the main concepts
that are frequently relevant in the context of software
architecture, architecture design, software PLA, quality
attributes, and safety attribute.
2.1 PLA design
What is Software Product Line? Software product line is
defined as “A set of software-intensive systems sharing a
common managed set of features that satisfy the specific
needs of a particular market segment or mission [11]”. These
Systems are developed from a common core of assets (e.g. a
common architecture) in a prescribed way.
Software Product Line (SPL) engineering is about developing
a collection of systems which share great
commonalities[3],[14],[15]. The idea of SPL was initiated by
Parnas [16] and has been further developed by Kang et al
[17]. The concept of SPL is to discover both commonalities
and variabilities among member products of the product
family.
(Liliana Dobrica, Eila Niemela,2003) [9].Product-line (PL)
and reusable software components are suitable approaches for
embedded systems, which are often re-engineered from
existing systems. Important issues in the development and
maintenance of these software systems are functionality and
quality. Although there are some similarities between
embedded systems regarding quality attributes, there are also
differences. If a quality attribute is important to one product-
line domain, it does not necessarily mean it is important to
another one.
Developing a reference architecture which represent the base
structure of the member products is the main task of the
software product line architecture design [3].
The Software Product Line Architecture (SPLA) [3] provides
a coarse grain picture of structure in the software product
family. It initiates the architecture design for the member
product. In the architecture design of a product line, it must
accommodate the variability and dependency of functionality
in the components that is derived from the feature model [3].
In the last two decades, software product line Architectures
have been used successfully in industry for building families
of systems of related products, maximizing reuse, and
exploiting their variable and configurable options
[10],[12],[13].
The creation and validation of product line software
architectures are inherently more complex than those of
software architectures for single systems.
3. International Journal of Computer Applications Technology and Research
Volume 5–Issue 10, 627-640, 2016, ISSN:-2319–8656
www.ijcat.com 629
Figure 1 illustrates examples of product line architecture for
embedded system [18], which is the Product Line
Architecture for a Microwave Oven.
Definition of Terms Used in the Example Class Diagram:
Kernel: Kernel in product lines represents the mandatory
features for the product line members. i.e.: they cannot be
omitted in products.
– The stereotype <<kernel>> is used to
specify Kernel in UML class diagrams.
Optional: Optionality in product lines means that some
features are elective for the product line members, which
means they can be omitted in some products and included in
others.
– The stereotype <<optional>> is used to
specify optionality in UML class
diagrams.
– The optionality can concern classes,
packages, attributes or operations. So the
<<optional>> stereotype can be applied to
Classifier, Package and Feature meta-
classes.
Variant: Variant classes are modeled using UML inheritance
and stereotypes. Each variation point will be defined by an
abstract class and a set of subclasses.
– The abstract class will be defined with the
stereotype <<variant>> and
– each subclass will be stereotyped
<<variant>>, or <<optional>>, the default
value being variant.
2.2 The Quality-based PLA Design
It is evident that there are several architecture design methods
available for Software Product Line. Among all the current
popular design methods, there are a few quality oriented
architecture design method. In the next lines we briefly
present and discuss some works.
(Len Bass et al., November 2001)[20] Their works is related
to the quality attributes and design of software architecture.
They presented an approach to characterizing quality
attributes and capturing architectural patterns that are used to
achieve these attributes. For each pattern, it is important not
only how the pattern achieves a quality attribute goal but also
what impact the pattern has on other attributes. They
embodied this investigation of quality into the Attribute
Driven Design Method for designing software architecture.
They have embarked on an effort to identify and codify
architectural patterns that are primitive with respect to the
achievement of quality attributes. They called this set of
architectural patterns attribute primitives. They embodied this
relationship in a design method for software architecture.
Their work in brief, they have a characterization for six
important attributes, they have a list and an organization for
attribute primitives to achieve these attributes, and they have
modified the Attribute Driven Design method (ADD) to
utilize both the attribute characterizations and the attribute
primitives.
However, this work concern with how to use or modify the
architectural patterns in term of achievement of quality
attributes at the architectural design level, No new method is
develop with consideration of specific attribute.
(Bosch et al., 2000) [21] Presents a design method that
elevates quality attributes from being almost totally ignored to
an important player in the design process. This method,
however, still places functional requirements as primary and
quality requirements as secondary. The method begins with a
design that achieves the functional requirements and this
design is iteratively transformed into one that achieves quality
requirements.
( Lei Tan, Yuqing Lin, Huilin Ye, 2012) [22]. Quality-driven
Architecture Design and quality Analysis (QADA) is a
traceable quality based method to design and evaluate
software architecture. QADA contains scenario-based quality
analysis to evaluate if the architecture design options meet the
quality requirements. QADA consists of three viewpoints:
structural view, behavior view, and deployment view at two
levels of abstractions: conceptual level and concrete level. It
contains several views at different levels to separate concerns
and it provides a quality-driven link between software
requirement and architecture. This work extended QADA
method by adding an extra view to improve this quality based
PLA design method.
In this framework, the quality attributes of a software system
will be taken into account in the early stage of architecture
design and the reference architecture of SPL will be elicited
based on quality-related consideration.
However, their work is just extending to QADA method by
adding an extra view to improve this quality based PLA
design method. This work may be a direction of more open
researches, especially in field of product line, that by focusing
on a specific quality attribute or other architectural attributes.
DoorSensor
<<kernel>>
+Door Opened()
+Door Closed()
WeightSensor
<<kernel>>
Keypad
<<kernel>>
+Cooking Time Selected()
+Cooking Time Entered()
+Start()
HeatingElement
<<kernel>>
Lamp
<<optional>>
Display
<<kernel>>
Beeper
<<optional>>
Turntable
<<optional>>
BooleanWeightSensor
<<default>>
+ItemPlaced()
+ItemRemoved()
AnalogWeightSensor
<<variant>>
One-levelHeatingElement
<<default>>
Multi-levelHeatingElement
<<variant>>
One-lineDisplay
<<default>>
+Read()
Multi-lineDisplay
<<variant>>
MicrowaveOvenSystem
Figure1: Product Line Architecture for a Microwave
Oven [18]
4. International Journal of Computer Applications Technology and Research
Volume 5–Issue 10, 627-640, 2016, ISSN:-2319–8656
www.ijcat.com 630
2.3 The safety-based design
Software safety assurance refers to a series of quality
assurance activities during software development life cycle,
which aims to eliminate the potential dangers.
The specification of safety constraints is the first step of the
safety-constraint centered design approach [29].
2.3.1 The design and safety
While modeling software safety it is important to note that no
software works in isolation. The entire system must be
designed to be safe. The system components may be software,
hardware, users, and the environment. All must be given
consideration when developing software. All parts of the
system must be safe. Functional and operational safety starts
at the system level. Safety cannot be assured if efforts are
focused only on software. The software can be totally free of
'bugs' and employ numerous safety features, yet the
equipment can be unsafe because of how the software and all
the other parts interact in the system [27].
2.3.2 Safety analysis at the architectural level
“From a safety viewpoint, the software architecture is where
the basic safety strategy is developed in the software.” It is
very significant to study how the non-functional attribute
“safety” to be described, analyzed and verified during the
architecture construction process [10].
Although a considerable number of safety analysis techniques
have been proposed to aid software design such as Software
Hazard Analysis and Resolution in Design (SHARD) [28],
there is little analysis work focusing on an architectural level
to aid software architecture design. In particular, safety is the
entire property of a system; it is almost impossible to analyze
software safety effectively without considering system or
platform safety. We thus need a safety analysis approach that
is able to model the integration of software with hardware or
other system components and to characterise the architectural
elements at different architectural levels.
2.3.3 Safety attribut and Product line Architecture
design
As product-line engineering becomes more widespread, more
safety-critical software product lines are being built [23].
The study shown that, Nowadays, there are various design
methods available and each is focusing on certain perspective
of architecture design. Especially, safety-based methods have
received a lot of attentions and have been well developed for
single system architecture design. However, the use of safety-
based design methods is limited in software product line
(SPL) because of the complexity and variabilities existing in
SPL architecture. In the next lines we briefly present and
discuss some of the related works.
(Donald Firesmith, 2004) [24]. His work concerned with the
Engineering Safety Requirements, Safety Constraints, and
Safety-Critical Requirements. He used the concept of a
quality model to define safety as a quality factor. Thus, safety
(like security and survivability) is a kind of defensibility,
which is a kind of dependability, which is a kind of quality.
Next, He discussed the structure of quality requirements and
showed how safety requirements can be engineered based on
safety’s numerous quality subfactors. Then, He defined and
discussed safety constraints (i.e., mandated safeguards) and
safety-critical requirements (i.e., functional, data, and
interface requirements that can cause accidents if not
implemented correctly).
However, no tasks or attentions related to how design the
software product line architecture based on safety analysis.
(David C. Jensen, Irem Y. Tumer, 2013) [25]. their work
presented a method of explicit inclusion of safety into a
model-based design for cyber physical systems. This approach
enables an analysis where component-level failures can be
mapped to potential system-level hazards. This work
presented a method of representing the safety property of a
system by the introduction of the concept termed "safety
function". Further, the function of achieving safety is mapped
to the performance functions of the system. They presented a
process of concurrently developing a system concept from the
safety and functional perspective. The end result of this
process is a system architecture where components of the
system are explicitly mapped to both the functions they
perform and the role they play in ensuring safe system
operation. The benefit of this approach is having a system
representation that allows for analysis of critical events and
off-nominal component behavior to identify potential losses in
function and safety constraint violations. The perspective of
these approaches is that safety should be a driver for design.
Thus the objective of this work is to introduce a safety-centric
method of developing a design based on the functional
modeling paradigm.
However, this work does not address the design of software
architecture. The proposed method focus on inclusion of
safety into design level in general without focusing on a
specific design activity.
(Yuling Huang, 2013) [26]. Safety design at the architecture
level can effectively improve software or system safety. This
work address the problem of how to consider safety in
software architecture design phase and proposed a safety-
oriented software architecture design approach. Through the
system hazard analysis, this design approach uses the selected
combination of safety tactics to effectively improve the
software or system safety, providing a new way of thinking
for software safety architecture design.
However, this work does not take in account the concepts of a
family of architectures, namely, Product line Architectures.
3. RESEARCH METHOD
A survey is a method for collecting data about features,
behavior or opinions of a specific group of people, pointed out
as representative from a target population (Pinsonneault and
Kraemer, 1993).
The stages involved in our literature review are structured into
three phases: planning, conducting, and reporting the review,
based on the guidelines proposed by Kitchenham [30].
A systematic mapping study is launched to find as much
literature as possible, and the 22 papers found are classified
with respect to focus, research type and contribution type.
Based on the guidelines, Kitchenham [30], this section details
the research questions, the performed research steps, and the
protocol of the literature review. First, Section 2.1 describes
the research questions underlying our survey. Then, Section
2.2 derives the research tasks we conducted, and thus
describes our procedure. Section 2.3 then details the literature
search step and highlights the inclusion and exclusion criteria.
Finally, Section 2.4 discusses threats to the validity of our
study.
However, the reported results are fragmented over different
research communities, multiple system domains, and multiple
5. International Journal of Computer Applications Technology and Research
Volume 5–Issue 10, 627-640, 2016, ISSN:-2319–8656
www.ijcat.com 631
quality attributes. Based on this survey, a taxonomy has been
created which is used to classify the existing research.
Furthermore, the systematic analysis of the research literature
provided in this review aims to help the research community
in consolidating the existing research efforts and deriving a
research agenda for future developments.
3.1 Research Questions
Based on the objectives described in the introduction, the
following research questions have been derived, which form
the basis for the literature review:
RQ1 How can the current research on software
architecture design be classified?
RQ2 What is the current state of the art of software
architecture design research with respect to this
classification? And the SPLA design, Quality-
driven SPLA design, Safety-driven SPLA design
methods in the existing methods?
RQ3 What can be learned from the current research
results that will lead to topics for further
investigation?
3.2 Research Tasks
To answer the three research questions RQ1-3, numbers of
tasks have been conducted: one task to set up the literature
review, and others research tasks dedicated to the identified
research questions.
3.3 Literature Search Process
The search strategy for the review was primarily directed
toward finding published papers in journals and conference
proceedings via the widely accepted literature search engines
and databases Google Scholar, IEEE Explore, and Elsevier
ScienceDirect. For the search we focused on selected
keywords, based on the aimed scope of the literature review.
Examples of the keywords are: Software Architecture, Quality
attributes, Safety analysis, Architectural Design, Software
Product Line Architectures, Safety-driven software product
line architecture design.
The keywords were refined and extended during the search
process. In the subsequent phase, we reviewed the abstracts
(and keywords) of the collected papers with respect to the
defined set of inclusion and exclusion criteria (Sections 2.3.1
and 2.3.2 below), and further extended the collection with
additional papers based on an analysis of the cited papers and
the ones citing it (forward and backward citation search).
3.3.1 Inclusion Criteria
The focus of this literature review is on software architecture
quality attributes, safety analysis, architectural design,
software product line architectures, and safety-driven software
product line architecture design. A summary of the inclusion
and criteria is: Peer reviewed publications with a clear focus
on some aspect of software product line architecture design.
3.3.2 Exclusion Criteria
We excluded papers that: (a) design a software with no
relation to software architecture, (b) focus on an architecture-
irrelevant problem, (c) focus on software architecture design
for single program without considering any quality attribute,
(d) focus on a product line-irrelevant problem.
We did not exclude papers for quality reasons, because the
quality of the papers was generally acceptable. A summary of
the exclusion criteria is: Publications where either architecture
design focus or software product line focus is lacking.
3.4 Threats to Validity
One of the main threats to the validity of this literature review
is the incompleteness. The risk of this threat highly depends
on the selected list of keywords and the limitations of the
employed search engines. To decrease the risk of an
incomplete keyword list, we have used an iterative approach
to keyword-list construction. A well-known set of papers was
used to build the initial taxonomy which evolved over time.
New keywords were added when the keyword list was not
able to find the state-of-the-art in the respective area of study.
Another important issue is whether our taxonomy is robust
enough for the analysis and classification of the papers. To
avoid a taxonomy with insufficient capability to classify the
selected papers, we used an iterative content analysis method
to continuously evolve the taxonomy for every new concept
encountered in the papers. New concepts were introduced into
the taxonomy and changes were made in the related taxonomy
categories. Furthermore, in order to make the taxonomy a
better foundation for analyzing the selected papers, we
allowed multiple abstraction levels for selected taxonomy
concepts.
4. TAXONOMY AND CLASSIFICATION
The quality of a literature review project highly depends on
the selected taxonomy scheme, which influences the depth of
knowledge recorded about each studied approach [31].This
section, present the identification of the taxonomy categories
and provide an answer to the first research question (RQ1).
In this article we provided a basic classification framework in
form of taxonomy to classify existing architecture design
approaches. As mentioned in the previous sections, here we
present two schemes of broad classifications of software
architecture design approaches, the two sections bellow are
illustrate that.
4.1 First classification scheme
As the first step of our survey, we classify existing approaches
for software architecture design into three broad categories
depending on whether they attempt to address the architecture
of single product or product line or quality attributes of
architecture.
Each of these categories contains one or more subcategories
based on the high-level strategies used to realize its goal.
Some of these sub-categories are further divided indicating
the specific intention adopted. Fig.2 and Fig.3 illustrates this
classification framework through which the results of the
survey are presented.
Software Architecture Design Methods
Architectural Design
Methods for a Single
Software
Product Line
Architecture
Design Methods
Quality-oriented
Architecture Design
Methods
Figure2: High level taxonomy of Architecture Design Approaches
6. International Journal of Computer Applications Technology and Research
Volume 5–Issue 10, 627-640, 2016, ISSN:-2319–8656
www.ijcat.com 632
The papers are published between 1998 and 2014, and
summarized in Table 1. Tables 2 and 3. The total number of
classification items in Table 1 is 28.
Table 1 lists all papers on term of architecture design
approaches. Table 2 lists all papers on quality-oriented
architecture design approaches. Table 3 lists all papers on
software product line architecture design approaches.
4.2 The second classification scheme in
term of SPLA design
Here, the publications are classified into categories in three
different dimensions: research focus, type of contribution and
research type. This structure is presented by Petersen et al.
[52], [53]. However we adopt different categories in our
study. We established a scheme and mapped publications
iteratively and added them as new primary studies. When the
scheme was finally set, we reviewed all classifications again.
We identified Three categories of research focus: (i) SPLA
design, (ii) quality-based SPLA design, (iii) safety-based
SPLA design, Contribution type is classified into five
categories: Tool, Method, Model, Metric, and Open Items.
The classification of research types is based on a scheme
proposed by Wieringa et al. [53] [54]. And we classified the
research into six categories: (i) validation research, (ii)
evaluation research, (iii) solution proposals, (iv) conceptual
proposals, (v) opinion papers, and (vi) experience papers.
SPLA Design Approaches
Quality-oriented Architecture DesignQuality-less Architecture Design
Multi-quality attributes Architecture Design
Single-quality attribute
Safety-based Architecture Design
Figure 3. the taxonomy Related to SPLA Design Approaches
7. International Journal of Computer Applications Technology and Research
Volume 5–Issue 10, 627-640, 2016, ISSN:-2319–8656
www.ijcat.com 633
Table 1.Papers on architecture design approaches (high level taxonomy/a broad classification)
No Authors [Ref] Paper Title year Architectural
Design for a
Single
Software
Product
Line
Architecture
Design
Quality-
oriented
Architecture
Design
1 David C. Jensen, Irem Y. Tumerb[25] Modeling and Analysis of Safety in Early Design 2013
2 Lei Tan, Yuqing Lin and Huilin Ye [3] Modeling Quality Attributes in Software Product Line
Architecture
2012
3 Yuling Huang [26] Safety-Oriented Software Architecture Design
Approach
2013
4 Len Bass, Mark Klein, and Felix
Bachmann [20]
Quality Attribute Design Primitives and the Attribute
Driven Design Method
2001
5 Made Murwantara Tangerang, Indonesia
[19]
Hybrid ANP: Quality Attributes Decision Modeling of a
Product Line Architecture Design
2012
6 Qian Feng, Robyn R. Lutz [23] Bi-Directional Safety Analysis of Product Lines 2005
7 Joachim Bayer, Oliver Flege, and Cristina
Gacek [32]
Creating Product Line Architectures 2000
8 Lei Tan, Yuqing Lin, Huilin Ye [22] Quality-Oriented Software Product Line Architecture
Design
2012
9 Weihang Wu, Tim Kelly [33] Safety Tactics for Software Architecture Design 2004
10 Liliana Dobrica, EILA Niemela [9] Attribute-based product-line architecture development
for embedded systems
2003
11 Bass, L.; Clements, P.; & Kazman, R. [34] Software Architecture in Practice. Reading , Attribute
Driven Design method (ADD)
2003
12 John Ryan O’Farrell [35] Development of A Software Architecture Method for
Software Product Families and its Application to the
AubieSat Satellite Program
2009
13 J¨urgen Meister, Ralf Reussner, Martin
Rohde [36]
Applying Patterns to Develop a Product Line
Architecture for Statistical Analysis Software
2004
14 P. America, H. Obbink, J. Muller, and R.
van Ommering [37]
COPA: A Component-Oriented Platform Architecting
Method for Families of Software Intensive Electronic
Products
2000
15 D. Weiss, C. Lai, and R. Tau [38] a family-based software development process. 1999
16 K. C. Kang, S. Kim, J. Lee, K. Kim, E.
Shin, and M. Huh [39]
FORM: A Feature-Oriented Reuse Method with
Domain- Specific Reference Architectures
1998
17 C. Atkinson et al [40] Component-based product line engineering with UML 2002
18 Mikael Svahnberg, Claes Wohlin, Lars
Lundberg, Michael Mattsson [41]
A Quality-Driven Decision-Support Method for
Identifying Software Architecture Candidates
2003
19 M. Matinlassi, E. Niemel,ن and L.
Dobrica[42]
Quality-driven architecture design and quality analysis
method
2002
20 F. Bachmann, L. Bass, G. Chastek, P.
Donohoe, and F. Peruzzi [43]
The Architecture Based Design Method 2000
21 Hassan Gomaa[44] Designing Software Product Lines with UML 2.0: From
Use Cases to Pattern-Based Software Architectures
2006
22 Jianli Dong, Jianzhou Wang, Donghuai
Sun, Haiyan Lu [45]
The Research of Software Product Line Engineering
Process and Its Integrated Development Environment
Model
2008
23 Jiayi Zhu, Xin Peng, Stan Jarzabek,
Zhenchang Xing, Yinxing Xue, Wenyun
Zhao [46]
Improving Product Line Architecture Design and
Customization by Raising the Level of Variability
Modeling
2011
24 M.Sharafi, S.Dadollahi [47] A Scenario-Based Approach for Architecture
Reconstruction of Product Line
2013
25 Hataichanok Unphon [48] Making Use of Architecture throughout the Software
Life Cycle – How the Build Hierarchy can Facilitate
Product Line Development
2009
8. International Journal of Computer Applications Technology and Research
Volume 5–Issue 10, 627-640, 2016, ISSN:-2319–8656
www.ijcat.com 634
26 Jing Liu, Josh Dehlinger, Robyn Lutz [49] Safety analysis of software product lines using state-
based modeling
2007
27 Jan Bosch [8] Software Product Lines and Software Architecture
Design
2001
28 Thelma Elita Colanzi, Silvia Regina
Vergilio[50]
Representation of Software Product Line Architectures
for Search-Based Design
2013
29 Broerse, C., Riva, C., Gall, H., Wijnstra,
J.g., Girard, J.F., Knodel, J., Pinzger, M.,
Pasman, W. [58]
Architecture Recovery for Product Family 2004
Table 2.Papers on quality-oriented architecture design approaches
No Authors [Ref] Paper year Single/Product
line
1 M. Matinlassi, E. Niemel, and L.
Dobrica[42]
Quality-driven architecture design and quality analysis
method
2002 Product line
2 L. Bass, M. Klein, and F. Bachmann
[51]
Quality Attribute Primitives and the Attribute Driven
Design Method
2002 Support all
3 David C. Jensen, Irem Y.
Tumerb[25]
Modeling and Analysis of Safety in Early Design 2013 Single
4 Lei Tan, Yuqing Lin and Huilin Ye
[3]
Modeling Quality Attributes in Software Product
Line Architecture
2012 Product line
5 Yuling Huang [26] Safety-Oriented Software Architecture Design Approach 2013 Single
6 Len Bass, Mark Klein, and Felix
Bachmann [20]
Quality Attribute Design Primitives and the Attribute
Driven Design Method
2001 Single
7 Made Murwantara
Tangerang, Indonesia [19]
Hybrid ANP: Quality Attributes Decision Modeling of a
Product Line Architecture Design
2012 Product line
8 Qian Feng, Robyn R. Lutz [23] Bi-Directional Safety Analysis of Product Lines 2005 Product line
9 Lei Tan, Yuqing Lin, Huilin Ye
[22]
Quality-Oriented Software Product Line Architecture
Design
2012 Product line
10 Weihang Wu, Tim Kelly [33] Safety Tactics for Software Architecture Design 2004 Single
11 LILIANA DOBRICA, EILA
NIEMELÄ [9]
Attribute-based product-line architecture development for
embedded systems
2003 Product line
12 Mikael Svahnberg, Claes Wohlin,
Lars Lundberg, Michael Mattsson
[41]
A Quality-Driven Decision-Support Method for
Identifying Software Architecture Candidates
2003 Single
13 Jing Liu, Josh Dehlinger, Robyn
Lutz [49]
Safety analysis of software product lines using state-
based modeling
2007 Product line
14 Jan Bosch [8] Software Product Lines and Software Architecture
Design
2001 Product line
9. International Journal of Computer Applications Technology and Research
Volume 5–Issue 10, 627-640, 2016, ISSN:-2319–8656
www.ijcat.com 635
Table 3.Papers on software product line architecture design approaches
No Authors [Ref] Paper Title Date Quality-less
Architecture
Design
Quality-
oriented
Architecture
Design
Single-
quality
attribute
Multi-quality
attributes
Architecture
Design
1 P. America, H. Obbink,
J. Muller, and R. van
Ommering [37]
COPA: A Component-Oriented
Platform Architecting Method for
Families of Software Intensive
Electronic Products
2000
2 D. Weiss, C. Lai, and R.
Tau [38]
Software product-line engineering: a
family-based software development
process.
1999
3 K. C. Kang, S. Kim, J.
Lee, K. Kim, E. Shin,
and M. Huh [39]
FORM: A Feature-Oriented Reuse
Method with Domain- Specific
Reference Architectures
1998
4 C. Atkinson et al. [40] Component-based product line
engineering with UML
2002
5 Lei Tan, Yuqing Lin and
Huilin Ye [3]
Modeling Quality Attributes in
Software Product Line Architecture
2012
6 Len Bass, Mark Klein,
and Felix Bachmann
[20]
Quality Attribute Design Primitives
and the Attribute
Driven Design Method
2001
7 Made Murwantara
Tangerang, Indonesia
[19]
Hybrid ANP: Quality Attributes
Decision Modeling of a Product Line
Architecture Design
2012
8 Qian Feng, Robyn R.
Lutz [23]
Bi-Directional Safety Analysis of
Product Lines
2005
9 Joachim Bayer, Oliver
Flege, and Cristina
Gacek [32]
Creating Product Line Architectures 2000
10 Lei Tan, Yuqing Lin,
Huilin Ye [22]
Quality-Oriented Software Product
Line Architecture Design
2012
11 Liliana Dobrica, Eila
NIEMELÄ [9]
Attribute-based product-line
architecture development for
embedded systems
2003
12 John Ryan O’Farrell
[35]
Development of A Software
Architecture Method for Software
Product Families and its Application
to the AubieSat Satellite Program
2009
13 J¨urgen Meister, Ralf
Reussner, Martin Rohde
[36]
Applying Patterns to Develop a
Product Line Architecture for
Statistical Analysis Software
2004
14 Hassan Gomaa [44] Designing Software Product Lines
with UML 2.0:
From Use Cases to Pattern-Based
Software Architectures
2006
15 Jianli Dong, Jianzhou
Wang, Donghuai Sun,
Haiyan Lu [45]
The Research of Software Product
Line Engineering Process and Its
Integrated Development Environment
Model
2008
16 Jiayi Zhu, Xin Peng,
Stan Jarzabek,
Zhenchang Xing,
Yinxing Xue, Wenyun
Zhao [46]
" Improving Product Line
Architecture Design and
Customization by Raising the Level of
Variability Modeling
2011
17 M.Sharafi, S.Dadollahi
[47]
A Scenario-Based Approach for
Architecture Reconstruction of
Product Line
2013
18 Hataichanok Unphon
[48]
Making Use of Architecture
throughout the Software Life Cycle –
How the Build Hierarchy can
Facilitate Product Line Development
2009
19 M. Matinlassi, E.
Niemel,ن and L. Dobrica
[42]
Quality-driven architecture design and
quality analysis method
2002
20 F. Bachmann, L. Bass,
G. Chastek, P. Donohoe,
and F. Peruzzi [43]
The Architecture Based Design
Method
2000
21 Jing Liu, Josh
Dehlinger, Robyn Lutz
[49]
Safety analysis of software product
lines using state-based modeling
2007
22 Jan Bosch [8] Software Product Lines and Software
Architecture Design
2001
23 Thelma Elita Colanzi,
Silvia Regina Vergilio
[50]
Representation of Software Product
Line Architectures for Search-Based
Design
2013
24 Broerse, C., Riva, C.,
Gall, H., Wijnstra, J.g.,
Girard, J.F., Knodel, J.,
Pinzger, M., Pasman, W.
[58]
Architecture Recovery for Product
Family
2004
10. International Journal of Computer Applications Technology and Research
Volume 5–Issue 10, 627-640, 2016, ISSN:-2319–8656
www.ijcat.com 636
Table 4. Distribution over research focus
Research focus 1998-2008 2009-2014 Total
SPLA design 10 5 15
Quality-based SPLA design 4 3 7
Safety-based SPLA design 2 - 2
Total 16 8 24
Table 5. Papers on SPLA design.
Authors [Ref] Title Paper Type Contribution
type
John Ryan O’Farrell [35] Development of A Software Architecture Method for Software Product
Families and its
Application to the AubieSat Satellite Program
Conceptual proposal Method
Joachim Bayer, Oliver Flege, and Cristina
Gacek [32]
Creating Product Line Architectures Solution proposal Method
J¨urgen Meister, Ralf Reussner, Martin Rohde
[36]
Applying Patterns to Develop a Product Line Architecture for
Statistical Analysis Software
Experience report Tool
Hassan Gomaa [44] Designing Software Product Lines with UML 2.0:
From Use Cases to Pattern-Based Software Architectures
Solution proposal Model
Jianli Dong, Jianzhou Wang, Donghuai Sun,
Haiyan Lu [45]
The Research of Software Product Line Engineering Process and Its
Integrated Development Environment Model
Opinion paper Model
Jiayi Zhu, Xin Peng, Stan Jarzabek, Zhenchang
Xing, Yinxing Xue, Wenyun Zhao [46]
Improving Product Line Architecture Design and Customization by
Raising the Level of Variability Modeling
Conceptual proposal Open items
M.Sharafi, S.Dadollahi [47] A Scenario-Based Approach for Architecture Reconstruction of Product
Line
Conceptual proposal Method
Hataichanok Unphon [48] Making Use of Architecture throughout the Software Life Cycle – How
the Build Hierarchy can Facilitate Product Line Development
Opinion paper Open items
P. America, H. Obbink, J. Muller, and R. van
Ommering [37]
COPA: A Component-Oriented Platform Architecting Method for
Families of Software Intensive Electronic Products
Conceptual proposal Model
D. Weiss, C. Lai, and R. Tau [38] Software product-line engineering: a family-based software
development process.
Conceptual proposal Open items
K. C. Kang, S. Kim, J. Lee, K. Kim, E. Shin,
and M. Huh [39]
FORM: A Feature-Oriented Reuse Method with Domain- Specific
Reference Architectures
Conceptual proposal Model
C. Atkinson et al. [40] Component-based product line engineering with UML Conceptual proposal Tool
F. Bachmann, L. Bass, G. Chastek, P. Donohoe,
and F. Peruzzi [43]
The Architecture Based Design Method Solution proposal Model
Thelma Elita Colanzi, Silvia Regina Vergilio
[50]
Representation of Software Product Line Architectures for Search-
Based Design
Experience report Open items
Broerse, C., Riva, C., Gall, H., Wijnstra, J.g.,
Girard, J.F., Knodel, J., Pinzger, M., Pasman,
W. [58]
Architecture Recovery for Product Family Solution proposal Method
Table 6. Papers on Quality-based SPLA design.
Authors [Ref] Title Paper Type Contributio
n Type
Lei Tan, Yuqing Lin and Huilin
Ye [3]
Modeling Quality Attributes in Software Product
Line Architecture
Conceptual
proposal
Method
I Made Murwantara
Tangerang, Indonesia [19]
Hybrid ANP: Quality Attributes Decision Modeling of a Product
Line Architecture Design
Conceptual
proposal
Model
Lei Tan, Yuqing Lin, Huilin Ye
[22]
Quality-Oriented Software Product Line Architecture Design Solution
proposal
Method
Liliana Dobrica, Eila Niemela [9] Attribute-based Product-line Architecture Development for
Embedded Systems
Solution
proposal
Method
Len Bass, Mark Klein, and Felix
Bachmann [20]
Quality Attribute Design Primitives and the Attribute Driven Design
Method
Opinion paper Open items
M. Matinlassi, E. Niemel, and L.
Dobrica [42]
Quality-driven architecture design and quality analysis method Conceptual
proposal
Method
Jan Bosch [8] Software Product Lines and Software Architecture Design Experience
report
Method
Table 7. Papers on Safety-based SPLA design.
Authors [Ref] Title Paper Type Contribut
ion type
Qian Feng, Robyn R.
Lutz [23]
Bi-Directional Safety Analysis of Product Lines Conceptual
proposal
Method
Jing Liu, Josh
Dehlinger, Robyn Lutz
[49]
Safety analysis of software product lines using state-based
modeling
Solution
proposal
Method
11. International Journal of Computer Applications Technology and Research
Volume 5–Issue 10, 627-640, 2016, ISSN:-2319–8656
www.ijcat.com 637
5. MAPPING
In Fig. 4, we show, based on the second classification in
section 4.2, a mapping between the research focus and the
contribution type and the research type. The research focus
items include SPLA design, Quality-based SPLA design, and
Safety-based SPLA design. The contributions types include
tools, methods, models, and metrics. The research types
include experience reports, opinion papers, conceptual or
solution proposals, and validation and evaluation research.
The Research focus is on the Y axis, the contribution type is
on the left side of the X axis, and research type on the right
side of the X axis.
6. Discussion and Results
The surveyed research work indicates safety based software
product line design being rather an immature area.
Safety-driven software product line architecture design seems
to be a ‘‘discussion” topic. There is a well established
understanding about challenges. However, when looking for
solutions to these challenges, we mostly find proposals. The
mapping shows that 74% of the papers found include
proposals, which contain ideas for solutions of the identified
challenges.
The study shows that there are various design methods
available and each is focusing on certain perspective of
architecture design and there is a large number of SPLA
design methods. Especially, quality-based methods have
received a lot of attention. However, the use of safety-based
design methods is limited in software product lines (SPL) due
to the variability property that can potentially result in a large
number of possible systems.
7. CONCLUSION AND FUTURE
WORKS
Because a product line reference software architecture is the
central artifact in product line engineering which provides the
framework for developing and integrating shared assets [47],
the creation and validation of such architecture are inherently
much more complex. This study aims at surveying existing
research on Software Product Line Architecture (SPLA) based
on quality attributes in order to identify useful approaches and
needs for future research. We investigated safety analysis at
the architectural level, and Safety-driven Software Product
Line Architecture Design (SSPLAD) approaches.
The paper show that there are various design methods
available and each is focusing on certain perspective of
architecture design. The quality-based methods have received
a lot of attentions and have been well developed for single
system architecture design. However, the use of quality-based
design methods is limited in software product line (SPL)
because of the complexity and variability existing in the SPL
reference architecture [22]. With the increasing attention to
software safety, improving software safety has already
become a much more important issue, especially for safety-
critical systems [26]. We identify the following open issues,
open research issues as related to specific key publications
surveyed in this paper.
The methodology presented by Jensen and Tumer
[25] focuses on the inclusion of safety into design
level in general without focusing on a specific
design activity such as the design of reference
architectures.
In [22], Lei Tan et al, presented a framework for
Quality-Oriented Software Product Line
Architecture Design. The framework is defined at a
high level without specifying any modeling
techniques or tools.
The work of Huang in [26] provides a rather
complex process for safety-oriented design using
Fault Tree Analysis techniques and safety tactics
Figure 4. Map of research focus on software product line design. Research focus on the Y axis; contribution type on the
left side of the X axis, and research type on the right side of the X axis.
2
SPLA design
Quality-based
SPLA design
Safety-based
SPLA design
Contribution Type Research Focus Research Type
Tool
Method
Model
Metric
Openitems
Experiencereport
Solutionproposal
Conceptualproposal
Evaluationresearch
Validationresearch
Opinionpaper
11
42 54
115
2 47
1 23
2
1
12. International Journal of Computer Applications Technology and Research
Volume 5–Issue 10, 627-640, 2016, ISSN:-2319–8656
www.ijcat.com 638
that would be difficult or intractable to use with the
concept of variability in product lines where the
space of possible faults is very large. It remains an
open issue to research if the FTA techniques
combined with safety tactics can be used with fault
classification techniques for safety-driven design of
reference architectures.
8. ACKNOWLEDGMENTS
This work was made possible by NPRP grant # [7-662-2-247]
from Qatar Research Fund (a member of Qatar Foundation).
The findings achieved herein are solely the responsibility of
the authors. We also thank "Department of Computer Science,
Sudan University of Science and Technology" for its support
which helped us to complete this paper successfully.
9. REFERENCES
[1] L. Bass, P. Clements and R. Kazman, Software
Architecture in Practice, 2nd ed. Addison-Wesley, 2003.
[2] IEEE-Std-1471-2000. IEEE recommended practice for
architectural description of software-intensive systems.
1471-2000.
[3] Lei Tan, Yuqing Lin and Huilin Ye, Modeling Quality
Attributes in Software Product Line Architecture, 978-1-
4577-1964-6/12/$31.00 IEEE, 2012.
[4] Nenad Medvidovic, Sam Malek, Marija Mikic-Rakic,
Software Architectures and Embedded Systems, 2003.
[5] Peter Wallin , Stig Larsson, Joakim Frِberg, Jakob
Axelsson, Problems and their mitigation in system and
software architecting, Information and Software
Technology 54 (2012) 686–700, 2012.
[6] Emelie Engstrm, Per Runeson, Software product line
testing – A systematic mapping study, Information and
Software Technology 53 (2011) 2–13, 2010.
[7] Mari Matinlassi, Comparison of Software Product Line
Architecture Design Methods: COPA, FAST, FORM,
KobrA and QADA, in 26th International Conference on
Software Engineering (ICSE’04) 0270-5257/04 $20.00,
IEEE, 2001.
[8] Jan Bosch, Software Product Lines and Software
Architecture Design, Proceedings of the 23rd
International Conference on Software Engineering
(ICSE’01) 0270-5257/01 2001.
[9] Liliana Dobrica, Eila Niemea, Attribute-Based Product-
Line Architecture Development for Embedded Systems,
2003.
[10] Rafael Capilla, Jan Bosch, Pablo Trinidad, Antonio Ruiz-
Cortés, Mike Hinchey, An overview of Dynamic
Software Product Line architectures and techniques:
Observations from research and industry, The Journal of
Systems and Software 91 (2014) 3–23, 2013.
[11] Pär J Ågerfalk, Brian Fitzgerald, Brian Lings, Björn
Lundell, Liam O’Brien, and Steffen Thiel, Open Source
in the Software Product Line: An Inevitable Trajectory,
2006.
[12] Razieh Behjati, Tao Yue, Lionel Briand, Bran Selic,
SimPL: A product-line modeling methodology for
families of integrated control systems, Information and
Software Technology 55 (2013) 607–629, 2013.
[13] Jules White, José A. Galindo, Tripti Saxena, Brian
Dougherty ,David Benavidesb, Douglas C. Schmid,
Evolving feature model configurations in software
product lines, The Journal of Systems and Software 87
(2014) 119– 136, 2013.
[14] J. Bosch, Design and Use of Software Architectures:
Adopting and Evolving a Product-Line Approach,
Addison-Wesley, 2000.
[15] Andreas Pleuss, Goetz Botterweck, Deepak Dhungana,
Andreas Polzer, Stefan Kowalewski, Model-driven
support for product line evolution on feature level, The
Journal of Systems and Software 85 (2012) 2261– 2274,
2011.
[16] D. Parnas, On the Design and Development of Program
Families, IEEE Transactions on Software Engineering,
vol. 2, 1-9, 1976.
[17] K. C. Kang, S. Kim, J. Lee, K. Kim, E. Shin and M. Huh,
FORM: A Feature-Oriented Reuse Method with Domain-
Specific Reference Architectures, Annals of Software
Engineering, vol. 5, 143-168, 1998.
[18] Prof Hany H. Ammar, Lectures :The Software Product
Line Architectures, PhD Graduate Program, Sudan
University of Science and Technology, Khartoum,
Sudan, 2013.
[19] I Made Murwantara, Hybrid ANP: Quality Attributes
Decision Modeling of a Product Line Architecture
Design, 2012 International Conference on Uncertainty
Reasoning and Knowledge Engineering, 2012.
[20] Len Bass, Mark Klein, and Felix Bachmann, Quality
Attribute Design Primitives and the Attribute Driven
Design Method, Software Engineering Institute Carnegie
Mellon University Pittsburgh, Pa 15213 USA, supported
by the U.S. Department of Defense and Robert Bosch,
GmbH 2001.
[21] Bosch, J. Design & Use of Software Architectures,
Addison Wesley, 2000.
[22] Lei Tan, Yuqing Lin, Huilin Ye, Quality-Oriented
Software Product Line Architecture Design, Journal of
Software Engineering and Applications, 5, 472-476, ,
2012.
[23] Qian Feng, Robyn R. Lutz, Bi-Directional Safety
Analysis of Product Lines, JSSF, 2005.
[24] Donald Firesmith, Engineering Safety Requirements,
Safety Constraints, and Safety-Critical Requirements,
JOURNAL OF OBJECT TECHNOLOGY JOURNAL
OF OBJECT TECHNOLOGY, Vol. 3, No. 3, 2004.
[25] David C. Jensen, Irem Y. Tumer, Modeling and Analysis
of Safety in Early Design, Conference on Systems
Engineering Research (CSER' 13), Eds.: C.J.J. Paredis,
C. Bishop, D. Bodner, Georgia Institute of Technology,
Atlanta, GA, March 19-22, 2013.
[26] Yuling Huang, Safety-Oriented Software Architecture
Design Approach, International Conference on
Information Science and Computer Applications (ISCA
2013, Published by Atlantis Press, 2013.
[27] M. Ben Swarup and P. Seetha Ramaiah, A Software
Safety Model for Safety Critical Applications,
International Journal of Software Engineering and Its
Applications Vol. 3, No.4, October 2009.