The technology advancement has forced the user to become more dependent on information technology, and so on software. Software provides the platform for implementation of information technology. Component Based Software Engineering (CBSE) is adopted by software community to counter challenges thrown by fast growing demand of heavy and complex software systems. One of the essential reasons behind adopting CBSE for software development is the fast development of complicated software systems within well-defined boundaries of time and budget. CBSE provides the mechanical facilities by assembling already existing reusable components out of autonomously developed pieces of the software. The paper proposes a novel CBSE model named as O model, keeping an eye on the available CBSE lifecycle.
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.
A software Process model is a standardised format for planning, organising, and runninga new software development project. The need to complete and deliver software projects faster require using a suitable model.
There are several different kind of models being used which have evolved over the years, in this paper we carried out survey on the following main types of model; waterfall model, V-model, Component assembly model, Chaos model, Incremental model, Prototyping model, Spiral model, Rapid application development (RAD) model, Agile model, rational unified process (RUP), Iconix process and Software ecosystem (SECO) model by describing their characteristic features.
We concluded the study by listing the strengths and weaknesses of each of this models.
FRAMEWORKS BETWEEN COMPONENTS AND OBJECTSacijjournal
Before the emergence of Component-Based Frameworks, similar issues have been addressed by other
software development paradigms including e.g. Object-Oriented Programming (OOP), ComponentBased Development (CBD), and Object-Oriented Framework. In this study, these approaches especially
object-oriented Frameworks are compared to Component-Based Frameworks and their relationship are
discussed. Different software reuse methods impacts on architectural patterns and support for
application extensions and versioning. It is concluded that many of the mechanisms provided by
Component-Based Framework can be enabled by software elements at the lower level. The main
contribution of Component-Based Framework is the focus on Component development. All of them can be
built on each other in layered manner by adopting suitable design patterns. Still some things such as
which method to develop and upgrade existing application to other approach.
Integrating profiling into mde compilersijseajournal
Scientific computation requires more and more performance in its algorithms. New massively parallel
architectures suit well to these algorithms. They are known for offering high performance and power
efficiency. Unfortunately, as parallel programming for these architectures requires a complex distribution
of tasks and data, developers find difficult to implement their applications effectively. Although approaches
based on source-to-source intends to provide a low learning curve for parallel programming and take
advantage of architecture features to create optimized applications, programming remains difficult for
neophytes. This work aims at improving performance by returning to the high-level models, specific
execution data from a profiling tool enhanced by smart advices computed by an analysis engine. In order to
keep the link between execution and model, the process is based on a traceability mechanism. Once the
model is automatically annotated, it can be re-factored aiming better performances on the re-generated
code. Hence, this work allows keeping coherence between model and code without forgetting to harness the
power of parallel architectures. To illustrate and clarify key points of this approach, we provide an
experimental example in GPUs context. The example uses a transformation chain from UML-MARTE
models to OpenCL code.
THE UNIFIED APPROACH FOR ORGANIZATIONAL NETWORK VULNERABILITY ASSESSMENTijseajournal
The present business network infrastructure is quickly varying with latest servers, services, connections,
and ports added often, at times day by day, and with a uncontrollably inflow of laptops, storage media and
wireless networks. With the increasing amount of vulnerabilities and exploits coupled with the recurrent
evolution of IT infrastructure, organizations at present require more numerous vulnerability assessments.
In this paper new approach the Unified process for Network vulnerability Assessments hereafter called as
a unified NVA is proposed for network vulnerability assessment derived from Unified Software
Development Process or Unified Process, it is a popular iterative and incremental software development
process framework.
Actually, software products are increasing in a fast way and are used in almost all activities of human life.
Consequently measuring and evaluating the quality of a software product has become a critical task for
many companies. Several models have been proposed to help diverse types of users with quality issues. The
development of techniques for building software has influenced the creation of models to assess the quality.
Since 2000 the construction of software started to depend on generated or manufactured components and
gave rise to new challenges for assessing quality. These components introduce new concepts such as
configurability, reusability, availability, better quality and lower cost. Consequently the models are
classified in basic models which were developed until 2000, and those based on components called tailored
quality models. The purpose of this article is to describe the main models with their strengths and point out
some deficiencies. In this work, we conclude that in the present age, aspects of communications play an
important factor in the quality of software.
STATISTICAL ANALYSIS FOR PERFORMANCE COMPARISONijseajournal
Performance responsiveness and scalability is a make-or-break quality for software. Nearly everyone runs into performance problems at one time or another. This paper discusses about performance issues faced during Pre Examination Process Automation System (PEPAS) implemented in java technology. The challenges faced during the life cycle of the project and the mitigation actions performed. It compares 3 java technologies and shows how improvements are made through statistical analysis in response time of the application. The paper concludes with result analysis.
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.
A software Process model is a standardised format for planning, organising, and runninga new software development project. The need to complete and deliver software projects faster require using a suitable model.
There are several different kind of models being used which have evolved over the years, in this paper we carried out survey on the following main types of model; waterfall model, V-model, Component assembly model, Chaos model, Incremental model, Prototyping model, Spiral model, Rapid application development (RAD) model, Agile model, rational unified process (RUP), Iconix process and Software ecosystem (SECO) model by describing their characteristic features.
We concluded the study by listing the strengths and weaknesses of each of this models.
FRAMEWORKS BETWEEN COMPONENTS AND OBJECTSacijjournal
Before the emergence of Component-Based Frameworks, similar issues have been addressed by other
software development paradigms including e.g. Object-Oriented Programming (OOP), ComponentBased Development (CBD), and Object-Oriented Framework. In this study, these approaches especially
object-oriented Frameworks are compared to Component-Based Frameworks and their relationship are
discussed. Different software reuse methods impacts on architectural patterns and support for
application extensions and versioning. It is concluded that many of the mechanisms provided by
Component-Based Framework can be enabled by software elements at the lower level. The main
contribution of Component-Based Framework is the focus on Component development. All of them can be
built on each other in layered manner by adopting suitable design patterns. Still some things such as
which method to develop and upgrade existing application to other approach.
Integrating profiling into mde compilersijseajournal
Scientific computation requires more and more performance in its algorithms. New massively parallel
architectures suit well to these algorithms. They are known for offering high performance and power
efficiency. Unfortunately, as parallel programming for these architectures requires a complex distribution
of tasks and data, developers find difficult to implement their applications effectively. Although approaches
based on source-to-source intends to provide a low learning curve for parallel programming and take
advantage of architecture features to create optimized applications, programming remains difficult for
neophytes. This work aims at improving performance by returning to the high-level models, specific
execution data from a profiling tool enhanced by smart advices computed by an analysis engine. In order to
keep the link between execution and model, the process is based on a traceability mechanism. Once the
model is automatically annotated, it can be re-factored aiming better performances on the re-generated
code. Hence, this work allows keeping coherence between model and code without forgetting to harness the
power of parallel architectures. To illustrate and clarify key points of this approach, we provide an
experimental example in GPUs context. The example uses a transformation chain from UML-MARTE
models to OpenCL code.
THE UNIFIED APPROACH FOR ORGANIZATIONAL NETWORK VULNERABILITY ASSESSMENTijseajournal
The present business network infrastructure is quickly varying with latest servers, services, connections,
and ports added often, at times day by day, and with a uncontrollably inflow of laptops, storage media and
wireless networks. With the increasing amount of vulnerabilities and exploits coupled with the recurrent
evolution of IT infrastructure, organizations at present require more numerous vulnerability assessments.
In this paper new approach the Unified process for Network vulnerability Assessments hereafter called as
a unified NVA is proposed for network vulnerability assessment derived from Unified Software
Development Process or Unified Process, it is a popular iterative and incremental software development
process framework.
Actually, software products are increasing in a fast way and are used in almost all activities of human life.
Consequently measuring and evaluating the quality of a software product has become a critical task for
many companies. Several models have been proposed to help diverse types of users with quality issues. The
development of techniques for building software has influenced the creation of models to assess the quality.
Since 2000 the construction of software started to depend on generated or manufactured components and
gave rise to new challenges for assessing quality. These components introduce new concepts such as
configurability, reusability, availability, better quality and lower cost. Consequently the models are
classified in basic models which were developed until 2000, and those based on components called tailored
quality models. The purpose of this article is to describe the main models with their strengths and point out
some deficiencies. In this work, we conclude that in the present age, aspects of communications play an
important factor in the quality of software.
STATISTICAL ANALYSIS FOR PERFORMANCE COMPARISONijseajournal
Performance responsiveness and scalability is a make-or-break quality for software. Nearly everyone runs into performance problems at one time or another. This paper discusses about performance issues faced during Pre Examination Process Automation System (PEPAS) implemented in java technology. The challenges faced during the life cycle of the project and the mitigation actions performed. It compares 3 java technologies and shows how improvements are made through statistical analysis in response time of the application. The paper concludes with result analysis.
Comparing Various SDLC Models On The Basis Of Available MethodologyIJMER
There are various SDLC models widely accepted and employed for developing software.
SDLC models give a theoretical guide line regarding development of the software. Employing proper
SDLC allows the managers to regulate whole development strategy of the software. Each SDLC has its
advantages and disadvantages making it suitable for use under specific condition and constraints for
specified type of software only. We need to understand which SDLC would generate most successful
result when employed for software development. For this we need some method to compare SDLC
models. Various methods have been suggested which allows comparing SDLC models. Comparing SLDC
models is a complex task as there is no mathematical theorem or physical device available. The essence
of this paper is to analyse some methodologies that could result in successful comparison of the SDLC
models. For this we have studied various available tools, techniques and methodologies and have tried
to extract most simple, easy and highly understandable method for comparing SDLC models.
A comparison of component-based software engineering and model-driven develop...Nikolay Grozev
Component-based software engineering (CBSE) and model-driven development (MDD) are two approaches for handling software development complexity. In essence, while CBSE focuses on the construction of systems from existing software modules called components; MDD promotes the usage of system models which after a series of transformations result with an implementation of the desired system. Even though they are different, MDD and CBSE are not mutually exclusive. However, there has not been any substantial research about what their similarities and differences are and how they can be combined. In this respect, the main goal of this thesis is to summarize the theoretical background of MDD and CBSE, and to propose and apply a systematic method for their comparison. The method takes into account the different effects that these development paradigms have on a wide range of development aspects. The comparison results are then summarized and analyzed.
The thesis also enriches the theoretical discussion with a practical case study comparing CBSE and MDD with respect to ProCom, a component model designed for the development of component-based embedded systems in the vehicular-, automation- and telecommunication domains. The aforementioned comparison method is refined and applied for this purpose. The comparison results are again summarized, analyzed and proposals about future work on ProCom are made.
MODEL DRIVEN WEB APPLICATION DEVELOPMENT WITH AGILE PRACTICESijseajournal
Model driven development is an effective method due to its benefits such as code transformation, increasing
productivity and reducing human based error possibilities. Meanwhile, agile software development
increases the software flexibility and customer satisfaction by using iterative method. Can these two
development approaches be combined to develop web applications efficiently? What are the challenges and
what are the benefits of this approach? In this paper, we answer these two crucial problems; combining
model driven development and agile software development results in not only fast development and
easiness of the user interface design but also efficient job tracking. We also defined an agile model based
approach for web applications whose implementation study has been carried out to support the answers we
gave these two crucial problems.
Computer literacy and competitive pressures among end users is increasing day by day due to whichthe
need for End-User Programming in software packages is also increasing for rapid, flexible, and user
driven information processing solutions. End User Development out-sources development effort to the end
user by enabling softwaredevelopers to create information systems that can even be adapted by technically
inexperienced endusers and hence are in great demand. If end user decides to pay the price and add
significant programmability to their system, there are additional costs to consider before end user can start
to enjoy the payoff. It is important to calculate accurateand early estimation of software size forcalculating
effort and cost estimation of software systems incorporating EUD features. With the evolution of object
orientation, use cases emerged as a dominant method for structuring requirements. Use cases were
integrated into the Unified Modeling Language (UML) and Unified Process and became the standard for
Software Engineering requirements modelling. The Use Case Point (UCP)methodestimates project size by
assigning points to use cases in the same way that Function Point Analysis (FPA) assigns points to
functions. This paper discusses the concept of end-user programming and Advancement of UCP by adding
end-user development/programming as an additional Effort Estimation Factor (EEF).
A Software System Development Life Cycle Model for Improved Students Communic...IJCSES Journal
Software engineering provides methodologies, concepts and practices, which are used for analyzing,designing, building and maintaining the information in a software industry. Software Development Life Cycle (SDLC) model is an approach used in the software industry for the development of various size
projects: small scale projects, medium scale projects and large scale projects. A software project of any size is developed with the co-ordination of development team. It is therefore important to assign resources intelligently to the different phases of the software project by the project manager. This study proposes a
model for the spiral development process with the use of a simulator (Simphony.NET), which helps the project manager in determining how to increase the productivity of a software firm with the use of minimum resources (expert team members). This model increase the utilization of different development
processes by keeping all development team members busy all the time, which helps in decreasing idle and waste time.
A PROPOSED HYBRID AGILE FRAMEWORK MODEL FOR MOBILE APPLICATIONS DEVELOPMENT ijseajournal
With the increasing in mobile application systems and a high competition between companies, that led to
increase in the number of mobile application projects.
Mobile software development is a group of process for creating software for mobile devices with limited
resources like small screen, low-power. The development of mobile applications is a big challenging
because of rapidly changing business requirements and technical constraints for mobile systems. So,
developers faced the challenge of a dynamic environment and the Changing of mobile application
requirements. Moreover, Mobile applications should adapt appropriate software development methods that
act in response efficiently to these challenges.
However, at the moment, there is limited knowledge about the suitability of different software practices for
the development of mobile applications. According to many researchers ,Agile methodologies was found to
be most suitable for mobile development projects as they are short time, require flexibility, reduces waste
and time to market.
Finally, in this research we are looking for a suitable process model that conforms to the requirement of
mobile application, we are going to investigate agile development methods to find a way, making the
development of mobile application easy and compatible with mobile device features.
BEST PRACTICES FOR IMPROVING USER INTERFACE DESIGN ijseajournal
A rich and effective computational system must have a friendly user interface with appealing usability features that provides excellent user experience. In order to develop interactive systems with the best user experience, an innovative iterative approach to user interface engineering is required because it is one of the most challenging areas given the diversity of knowledge, ideas, skills and creativity needed for building smart interfaces in order to succeed in today’s rapidly paced and tough, competitive marketplace. Many modeling aspects including analytical, intuitive, artistic, technical, graphical, mathematical, psychological and programming models need to be considered in the development process of an effective user interface. This research examines some of the past practices and recommends a set of guidelines for designing effective user interfaces. It also demonstrates how UML use case diagrams can be enhanced by relating user interface elements to use cases.
REALIZING A LOOSELY-COUPLED STUDENTS PORTAL FRAMEWORKijseajournal
Most of the currently available students' portal frameworks are tightly-coupled frameworks. A recent
research done by the authors of this paper has discussed how to distribute the concepts of the traditional
students' portal framework and came out with a distributed interoperable framework. This paper realizes
the distributed interoperable students' portal framework by developing a prototype. This prototype is based
on Service Oriented Architecture (SOA). The prototype is tested using web service testing and compatibility
testing.
Comparing Various SDLC Models On The Basis Of Available MethodologyIJMER
There are various SDLC models widely accepted and employed for developing software.
SDLC models give a theoretical guide line regarding development of the software. Employing proper
SDLC allows the managers to regulate whole development strategy of the software. Each SDLC has its
advantages and disadvantages making it suitable for use under specific condition and constraints for
specified type of software only. We need to understand which SDLC would generate most successful
result when employed for software development. For this we need some method to compare SDLC
models. Various methods have been suggested which allows comparing SDLC models. Comparing SLDC
models is a complex task as there is no mathematical theorem or physical device available. The essence
of this paper is to analyse some methodologies that could result in successful comparison of the SDLC
models. For this we have studied various available tools, techniques and methodologies and have tried
to extract most simple, easy and highly understandable method for comparing SDLC models.
A comparison of component-based software engineering and model-driven develop...Nikolay Grozev
Component-based software engineering (CBSE) and model-driven development (MDD) are two approaches for handling software development complexity. In essence, while CBSE focuses on the construction of systems from existing software modules called components; MDD promotes the usage of system models which after a series of transformations result with an implementation of the desired system. Even though they are different, MDD and CBSE are not mutually exclusive. However, there has not been any substantial research about what their similarities and differences are and how they can be combined. In this respect, the main goal of this thesis is to summarize the theoretical background of MDD and CBSE, and to propose and apply a systematic method for their comparison. The method takes into account the different effects that these development paradigms have on a wide range of development aspects. The comparison results are then summarized and analyzed.
The thesis also enriches the theoretical discussion with a practical case study comparing CBSE and MDD with respect to ProCom, a component model designed for the development of component-based embedded systems in the vehicular-, automation- and telecommunication domains. The aforementioned comparison method is refined and applied for this purpose. The comparison results are again summarized, analyzed and proposals about future work on ProCom are made.
MODEL DRIVEN WEB APPLICATION DEVELOPMENT WITH AGILE PRACTICESijseajournal
Model driven development is an effective method due to its benefits such as code transformation, increasing
productivity and reducing human based error possibilities. Meanwhile, agile software development
increases the software flexibility and customer satisfaction by using iterative method. Can these two
development approaches be combined to develop web applications efficiently? What are the challenges and
what are the benefits of this approach? In this paper, we answer these two crucial problems; combining
model driven development and agile software development results in not only fast development and
easiness of the user interface design but also efficient job tracking. We also defined an agile model based
approach for web applications whose implementation study has been carried out to support the answers we
gave these two crucial problems.
Computer literacy and competitive pressures among end users is increasing day by day due to whichthe
need for End-User Programming in software packages is also increasing for rapid, flexible, and user
driven information processing solutions. End User Development out-sources development effort to the end
user by enabling softwaredevelopers to create information systems that can even be adapted by technically
inexperienced endusers and hence are in great demand. If end user decides to pay the price and add
significant programmability to their system, there are additional costs to consider before end user can start
to enjoy the payoff. It is important to calculate accurateand early estimation of software size forcalculating
effort and cost estimation of software systems incorporating EUD features. With the evolution of object
orientation, use cases emerged as a dominant method for structuring requirements. Use cases were
integrated into the Unified Modeling Language (UML) and Unified Process and became the standard for
Software Engineering requirements modelling. The Use Case Point (UCP)methodestimates project size by
assigning points to use cases in the same way that Function Point Analysis (FPA) assigns points to
functions. This paper discusses the concept of end-user programming and Advancement of UCP by adding
end-user development/programming as an additional Effort Estimation Factor (EEF).
A Software System Development Life Cycle Model for Improved Students Communic...IJCSES Journal
Software engineering provides methodologies, concepts and practices, which are used for analyzing,designing, building and maintaining the information in a software industry. Software Development Life Cycle (SDLC) model is an approach used in the software industry for the development of various size
projects: small scale projects, medium scale projects and large scale projects. A software project of any size is developed with the co-ordination of development team. It is therefore important to assign resources intelligently to the different phases of the software project by the project manager. This study proposes a
model for the spiral development process with the use of a simulator (Simphony.NET), which helps the project manager in determining how to increase the productivity of a software firm with the use of minimum resources (expert team members). This model increase the utilization of different development
processes by keeping all development team members busy all the time, which helps in decreasing idle and waste time.
A PROPOSED HYBRID AGILE FRAMEWORK MODEL FOR MOBILE APPLICATIONS DEVELOPMENT ijseajournal
With the increasing in mobile application systems and a high competition between companies, that led to
increase in the number of mobile application projects.
Mobile software development is a group of process for creating software for mobile devices with limited
resources like small screen, low-power. The development of mobile applications is a big challenging
because of rapidly changing business requirements and technical constraints for mobile systems. So,
developers faced the challenge of a dynamic environment and the Changing of mobile application
requirements. Moreover, Mobile applications should adapt appropriate software development methods that
act in response efficiently to these challenges.
However, at the moment, there is limited knowledge about the suitability of different software practices for
the development of mobile applications. According to many researchers ,Agile methodologies was found to
be most suitable for mobile development projects as they are short time, require flexibility, reduces waste
and time to market.
Finally, in this research we are looking for a suitable process model that conforms to the requirement of
mobile application, we are going to investigate agile development methods to find a way, making the
development of mobile application easy and compatible with mobile device features.
BEST PRACTICES FOR IMPROVING USER INTERFACE DESIGN ijseajournal
A rich and effective computational system must have a friendly user interface with appealing usability features that provides excellent user experience. In order to develop interactive systems with the best user experience, an innovative iterative approach to user interface engineering is required because it is one of the most challenging areas given the diversity of knowledge, ideas, skills and creativity needed for building smart interfaces in order to succeed in today’s rapidly paced and tough, competitive marketplace. Many modeling aspects including analytical, intuitive, artistic, technical, graphical, mathematical, psychological and programming models need to be considered in the development process of an effective user interface. This research examines some of the past practices and recommends a set of guidelines for designing effective user interfaces. It also demonstrates how UML use case diagrams can be enhanced by relating user interface elements to use cases.
REALIZING A LOOSELY-COUPLED STUDENTS PORTAL FRAMEWORKijseajournal
Most of the currently available students' portal frameworks are tightly-coupled frameworks. A recent
research done by the authors of this paper has discussed how to distribute the concepts of the traditional
students' portal framework and came out with a distributed interoperable framework. This paper realizes
the distributed interoperable students' portal framework by developing a prototype. This prototype is based
on Service Oriented Architecture (SOA). The prototype is tested using web service testing and compatibility
testing.
Van de tiep_nhan_van_hoc_duong_dai_va_thi_hieu_tham_my_cua_thanh_nien_ngay_na...Garment Space Blog0
Giá 10k/, tài liệu này đang ở dạng xem trước, vui lòng nạp thẻ cào để được xem full tài liệu www.facebook.com/garmentspace www.facebook.com/garmentspace www.facebook.com/garmentspace
A Review on Quality Assurance of Component- Based Software Systemiosrjce
IOSR Journal of Computer Engineering (IOSR-JCE) is a double blind peer reviewed International Journal that provides rapid publication (within a month) of articles in all areas of computer engineering and its applications. The journal welcomes publications of high quality papers on theoretical developments and practical applications in computer technology. Original research papers, state-of-the-art reviews, and high quality technical notes are invited for publications.
SOFTWARE REQUIREMENT CHANGE EFFORT ESTIMATION MODEL PROTOTYPE TOOL FOR SOFTWA...ijseajournal
In software development phase software artifacts are not in consistent states such as: some of the class artifacts are fully developed some are half developed, some are major developed, some are minor developed and some are not developed yet. At this stage allowing too many software requirement changes may possibly delay in project delivery and increase development budget of the software. On the other hand rejecting too many changes may increase customer dissatisfaction. Software change effort estimation is one of the most challenging and important activity that helps software project managers in accepting or rejecting changes during software development phase. This paper extends our previous works on developing a software requirement change effort estimation model prototype tool for the software development phase. The significant achievements of the tool are demonstrated through an extensive experimental validation using several case studies. The experimental analysis shows improvement in the estimation accuracy over current change effort estimation models.
A sustainable procedural method of software design process improvementsnooriasukmaningtyas
In practice, the software process is an intermediate phase for enhancement and improvements the design for different types of software products and help developers to converts the specified requirements into prototypes that implement the design into reality. The objective of this paper is to provide software developers, designers and software engineers who work in small companies with a standards-based process improvement using a procedural method technique including detailed steps for designing the small software systems into their companies. The method used in this paper includes 1) analysis four different types of commonly design processes used by industry such as CMMI, conventional or software process in ISO 19759, generic and engineering design processes. 2) mapping between those four design processes. 3) collect the dispersed design concepts proposed by those four processes. 4) proposed a sustainable procedural method of software design process improvements 5) Illustration of the applicability of the proposed approach using A template-based implementation. The primary result of this study is a guideline procedure with detailed steps for software design process improvements to help and guide developers in small companies to analyze and design a small software scales with limited cost and duration. In conclusion, this paper proposed a method to improve the design process for different kinds of the software systems using a templatebased implementation to reduce the cost, effort and time needed in the implementation phase in small companies. The scientific implication behind a template-based implementation helps the system and software engineering to use this template easily in their small companies; because most of the time those engineering developers are responsible for analyzing, designing, implementing and testing their software systems during the whole software life cycle.
International Journal of Computational Engineering Research(IJCER) ijceronline
nternational Journal of Computational Engineering Research (IJCER) is dedicated to protecting personal information and will make every reasonable effort to handle collected information appropriately. All information collected, as well as related requests, will be handled as carefully and efficiently as possible in accordance with IJCER standards for integrity and objectivity.
A New Model for Study of Quality Attributes to Components Based Development A...Kiogyf
A New Model for Study of Quality Attributes to Components Based Development Approach
by bstract :
Software development costs, time - to release and quality product are important factors affecting the construction of software. Different types of tools and techniques are suggested by researchers to improve in delivering quality software systems with lower cost and reduce time to delivery. One such practice is development of software using ased Software Development (CBSD) techniques. CBSD recommended Component Bbuilding software systems using existing reusable components, instead of writing from scratch. The main objective of CBSD is to writes once and reuse any number of time with no or modification . Some of the advantages that a company may available by adapting CBSD for the Software development are shorter development time which results in meet tight dead line, increase productivity and Quality Product. CBSD also, s paper is to develop the new model of software support reusability. The aim of thiproduct and describe the characteristics of some selected of attributes of CBSD models that are widely practiced in software industries. We proposed a complete model for or reuse. This Model will cover both Component Based Software Development fcomponent based software development as well as Component development phases for
A - Model. This Model is represent one good solution for Component Based Development with reduce cost and time to deliverable and save the quality of product . Keywords: Component Based Approach, Quality Model, Quality Attributes, , A - Model for CBD .
1. Introduction
Forklift Classes Overview by Intella PartsIntella Parts
Discover the different forklift classes and their specific applications. Learn how to choose the right forklift for your needs to ensure safety, efficiency, and compliance in your operations.
For more technical information, visit our website https://intellaparts.com
Overview of the fundamental roles in Hydropower generation and the components involved in wider Electrical Engineering.
This paper presents the design and construction of hydroelectric dams from the hydrologist’s survey of the valley before construction, all aspects and involved disciplines, fluid dynamics, structural engineering, generation and mains frequency regulation to the very transmission of power through the network in the United Kingdom.
Author: Robbie Edward Sayers
Collaborators and co editors: Charlie Sims and Connor Healey.
(C) 2024 Robbie E. Sayers
Immunizing Image Classifiers Against Localized Adversary Attacksgerogepatton
This paper addresses the vulnerability of deep learning models, particularly convolutional neural networks
(CNN)s, to adversarial attacks and presents a proactive training technique designed to counter them. We
introduce a novel volumization algorithm, which transforms 2D images into 3D volumetric representations.
When combined with 3D convolution and deep curriculum learning optimization (CLO), itsignificantly improves
the immunity of models against localized universal attacks by up to 40%. We evaluate our proposed approach
using contemporary CNN architectures and the modified Canadian Institute for Advanced Research (CIFAR-10
and CIFAR-100) and ImageNet Large Scale Visual Recognition Challenge (ILSVRC12) datasets, showcasing
accuracy improvements over previous techniques. The results indicate that the combination of the volumetric
input and curriculum learning holds significant promise for mitigating adversarial attacks without necessitating
adversary training.
Democratizing Fuzzing at Scale by Abhishek Aryaabh.arya
Presented at NUS: Fuzzing and Software Security Summer School 2024
This keynote talks about the democratization of fuzzing at scale, highlighting the collaboration between open source communities, academia, and industry to advance the field of fuzzing. It delves into the history of fuzzing, the development of scalable fuzzing platforms, and the empowerment of community-driven research. The talk will further discuss recent advancements leveraging AI/ML and offer insights into the future evolution of the fuzzing landscape.
Sachpazis:Terzaghi Bearing Capacity Estimation in simple terms with Calculati...Dr.Costas Sachpazis
Terzaghi's soil bearing capacity theory, developed by Karl Terzaghi, is a fundamental principle in geotechnical engineering used to determine the bearing capacity of shallow foundations. This theory provides a method to calculate the ultimate bearing capacity of soil, which is the maximum load per unit area that the soil can support without undergoing shear failure. The Calculation HTML Code included.
Final project report on grocery store management system..pdfKamal Acharya
In today’s fast-changing business environment, it’s extremely important to be able to respond to client needs in the most effective and timely manner. If your customers wish to see your business online and have instant access to your products or services.
Online Grocery Store is an e-commerce website, which retails various grocery products. This project allows viewing various products available enables registered users to purchase desired products instantly using Paytm, UPI payment processor (Instant Pay) and also can place order by using Cash on Delivery (Pay Later) option. This project provides an easy access to Administrators and Managers to view orders placed using Pay Later and Instant Pay options.
In order to develop an e-commerce website, a number of Technologies must be studied and understood. These include multi-tiered architecture, server and client-side scripting techniques, implementation technologies, programming language (such as PHP, HTML, CSS, JavaScript) and MySQL relational databases. This is a project with the objective to develop a basic website where a consumer is provided with a shopping cart website and also to know about the technologies used to develop such a website.
This document will discuss each of the underlying technologies to create and implement an e- commerce website.
Cosmetic shop management system project report.pdfKamal Acharya
Buying new cosmetic products is difficult. It can even be scary for those who have sensitive skin and are prone to skin trouble. The information needed to alleviate this problem is on the back of each product, but it's thought to interpret those ingredient lists unless you have a background in chemistry.
Instead of buying and hoping for the best, we can use data science to help us predict which products may be good fits for us. It includes various function programs to do the above mentioned tasks.
Data file handling has been effectively used in the program.
The automated cosmetic shop management system should deal with the automation of general workflow and administration process of the shop. The main processes of the system focus on customer's request where the system is able to search the most appropriate products and deliver it to the customers. It should help the employees to quickly identify the list of cosmetic product that have reached the minimum quantity and also keep a track of expired date for each cosmetic product. It should help the employees to find the rack number in which the product is placed.It is also Faster and more efficient way.
Event Management System Vb Net Project Report.pdfKamal Acharya
In present era, the scopes of information technology growing with a very fast .We do not see any are untouched from this industry. The scope of information technology has become wider includes: Business and industry. Household Business, Communication, Education, Entertainment, Science, Medicine, Engineering, Distance Learning, Weather Forecasting. Carrier Searching and so on.
My project named “Event Management System” is software that store and maintained all events coordinated in college. It also helpful to print related reports. My project will help to record the events coordinated by faculties with their Name, Event subject, date & details in an efficient & effective ways.
In my system we have to make a system by which a user can record all events coordinated by a particular faculty. In our proposed system some more featured are added which differs it from the existing system such as security.
‘O’ Model for Component-Based Software Development Process
1. ISSN (e): 2250 – 3005 || Volume, 06 || Issue, 12|| December – 2016 ||
International Journal of Computational Engineering Research (IJCER)
www.ijceronline.com Open Access Journal Page 28
‘O’ Model for Component-Based Software Development Process
Saurabh Rawat1,
Rajesh Kumar2
1
Graphic Era University Dehradun- India,
2
Graphic Era University Dehradun- India,
I. Introduction
Component-Based Development (CBD) is straightaway well ingrained in the IT industry. A component is a
well-defined unit of functionality with a distinct line that grants it to liaison up with other components, and be
separately spread out. The Component-based functions are explicit from the assembling components.
The Component-Based Software Engineering (CBSE) has become outward [1] in the genesis of 1990‟s.
Originally, the ultimate products developed by CBSE were circumscribed to PCs whereas the use of COTS
(Commercial Off-The-Shelf Components) software has inspires CBSE for the evolvement of business
applications [2].
The extensive interests correlated with component-based technologies blend: evolution of condensed system,
brisk induction, lessened cost, amplify quality, and curtailed system evolution and diminished maintenance cost.
The increment in time has given upswing to the development of standard component-based specifications and
the significance of CBD has developed swiftly in the embedded system trade.
A component is related to be autonomous bit of software if it has an open interface, distributes clear
performance and moreover gives plug-and-pay services. Therefore it can be declared that component-based
software evolution advocates the reusability and gives improved software quality. Thus Component-based
software development can point to new ideas for the construction of large and complex software systems.
II. Review of Literature
The diverse kinds of CBSD models are available in the industry as well as in the academic world. We referred to
some of them, in this division some of them are examined that are as follows:
The concept CBSE has actually make the scene after the fruitful set afloat of Microsoft‟s COM+ [3], SUN „s
Enterprise JavaBeans [4], and IBM Component Broker [5] and CORBA [6]. CBSE have burst in among the
conventional software technologies [7]. Furthermore, cumulative transfer of software attributes or stages that
consist of a software product line, is expected to be in the limelight in the imminent years, therefore component-
based software engineering has conclusions for how software engineers achieve, gather and keep up software
systems [8]. Thus, we should see extreme modulations in designers‟ primary roles and required skills for
software development in the imminent time.
ABSTRACT
The technology advancement has forced the user to become more dependent on information
technology, and so on software. Software provides the platform for implementation of information
technology. Component Based Software Engineering (CBSE) is adopted by software community to
counter challenges thrown by fast growing demand of heavy and complex software systems. One of the
essential reasons behind adopting CBSE for software development is the fast development of
complicated software systems within well-defined boundaries of time and budget. CBSE provides the
mechanical facilities by assembling already existing reusable components out of autonomously
developed pieces of the software. The paper proposes a novel CBSE model named as O model, keeping
an eye on the available CBSE lifecycle.
Keywords: Component Based Development (CBD), Software Development Life Cycle, OModel,
COTS, Dependency among components
2. ISSN (e): 2250 – 3005 || Volume, 06 || Issue, 12|| December – 2016 ||
International Journal of Computational Engineering Research (IJCER)
www.ijceronline.com Open Access Journal Page 29
All different stages of the software process are revealing and figuratively depicted by a Software Life
Cycle Model . The phases of the software development cycle [9] are represented by Software development life
cycle (SDLC) model.
The Twin Peaks model [10] also offers for a parallel, around the clock evolution of requirements and
architecture all through expansion. Software can be developed by partial and easy wave. .
In X Model, the mechanisms are initiated by essential engineering and requirement assessment. Reusability in
which software is refined by dwelling reusable components and software evolution from reusable and
testable components, is the main characteristic of this software life cycle model .Develop software
component for reuse and software development with or without modification in reusable component. [11] are
two main ways, it uses in software development.
Software reusability during CBSD is exemplified by the Y Software Life Cycle Model. The Y Shape of the
model weighs up iteration and overlapping. The designed phases of Y model are: domain engineering, frame
working, assembly, archiving, system analysis, design, implementation, testing, deployment and
maintenance. [12], although the principal phases may overlap each other and iteration is granted.
Knot Model recommending on reusability, recognizing risk analysis and feedback in each and whole segment.
This model Knot model is based on three states of the component [13], may be best matched for intermediate or
larger complex system‟s development.
Expansion of new product using component based technology is accomplished by promising software lifecycle
model, the Elite Life Cycle Model (ELCM). This model portrays a general process of Software development
with the help of in built components. [14].
New age with new permutation in Software Development [15] gives the thought of selection, prioritization and
customization to develop, transform and choice of components.
The V model adopted the conventional software development access for constructing a system from reusable
software components [16]. It consists of several steps and supports the details information at the design phases.
The central significance of V-Development is component development lifecycle. Component development
lifecycle was regarded as contrasting process. The selection phase gets input from the independent system that
usually finds and develops the appropriate components to be composed into the system. The rigid conventional
waterfall model for modular system development with little flexibility is the V Model.
The W lifecycle model, amalgam of two V models together. Component based development process comprises
of a component life cycle and a system life cycle, and it is the base of W lifecycle model [17]. The W model
accomplishes all the concerns of component based evolution. The W Model entertains a V model for both
component and system life cycles.
III. ‘O’ Model for Component-Based Software Development
This study propose a new „O‟ model in which the processes start in usual way by requirement engineering and
requirement specification as shown in Figure 5.1. In a non- component-based approach the process would
continue with the unit design, implementation and test. Instead of performing these activities that often are time
and efforts consuming, simply select appropriate components and integrate them in the system. However, two
problems appear here which break this simplicity– Itis not obvious that there is any component to select, and the
selected component only partially fits to our overall design. The main characteristic of this software life cycle
model is reusability in which software is developed by building reusable components for software development,
and software development from reusable and testable components. In software development, this research use
two main approaches, develop software component for reuse and software development with or without
modification in reusable component. Evolution and the production of potentially reusable components are meant
to be useful in future software projects. Reusability not only involves reusing existing components in a new
software system but also producing components meant for reuse. When a software system has been developed,
the software engineer may realize that some components can be generalized for potential reuse in the future.
Reusability implies the use of composition techniques during software development; this is achieved by initially
selecting reusable components and assembling them or by adapting the software to a point where it is possible to
pick out components from a reusable component repository and testable component repository. This study
introduces two main phases first is building reusable components for software development and second is
3. ISSN (e): 2250 – 3005 || Volume, 06 || Issue, 12|| December – 2016 ||
International Journal of Computational Engineering Research (IJCER)
www.ijceronline.com Open Access Journal Page 30
building software from reusable and testable components (Tomar and Gill, 2006) of O model which help in
developing a component-based software.
a. Phases of O Model
1) Component selection/ Modification/ Development
2) Integration of Components
3) Testing of Component
4) Customer/User Evaluation
b. Component Selection/Modification/Development
Once a build scope is established, we need to decide which of the required components can be used (e.g.,
already exist in the organization or can be bought off-the-shelf) and which ones need to be developed. And some
components need modification (see figure 2).
3.1.1. Using existing component
Reusing an existing component may require some adaptation. For example, the component interface might not
be exactly what is required or some of the method behaviors may need alteration. This is achieved through
adaptation, which involves wrapping the component with a thin layer of code that implements the required
changes.
3.1.2. Modify Existing Components (if required)
Developing a new module from scratch is always avoided in CBD. It may highly possible that some existing
components may require some minor or major modifications to accommodate with other components. We can
modify an existing component according to the scope specification.
3.1.3. Development of New Components
Building a new component should always begin with defining the component interface. This represents a
permanent contract between the component and other components. Once the interface is defined and the intent
of each method is established, the component can be designed and implemented.
3.2 Integration of Components
With all the components for a build in place, the components are then integrated and tested. The Integration
process must be done keeping scope specification and design specification in mind. The integration of Elite
model is based on Clustering Approach. We must start integration with bottom level and progresses toward the
Clusters. These different clusters will ultimately form the software. Integration will require the writing of
intermediate code that establishes the interaction between the components.
Figure 1: O Model for Component-Based Development
Component
selection/
Modification/
Development
Integration of
Components
Testing of
Component
Customer/
User
Evaluation
4. ISSN (e): 2250 – 3005 || Volume, 06 || Issue, 12|| December – 2016 ||
International Journal of Computational Engineering Research (IJCER)
www.ijceronline.com Open Access Journal Page 31
3.3 Testing
Testing is the most important activity of the software development process for finding the maximum errors;
therefore without proper testing of the software product, all the efforts will be in vain [SZYP 99, MYER 04, and
GILL 07]. Software Component Testing (SCT) is an approach to finding errors, reducing cost, improving
reliability, and enhancing the quality of software components [MEYE 03, BEIZ 90 and MEYE 98]. In CBD,
testing is applied not only to the individual components but also to the whole integrated software system. This
process not only fulfills the aim of finding errors but also improves the software quality [SITA 94]. SCT
represents a group of activities, which involves component study, quality test design and generation, test
execution, fault detection, and finally testing evaluation [BEIZ 90].
1.4 Customer/User Evaluation
The evaluation environment may be the same as the development environment (for earlier builds that are not
mature), or a pseudo live environment (for later builds that are sufficiently mature). The outcome of the
evaluation influences the direction of subsequent builds. The Evaluation phase involves the answers to these
questions:
Is the user satisfied?
Are the actual resources expenditures versus planned expenditures still acceptable or not.
VI. Conclusion
This chapter recommends a novel O component-based model for CBSD. O model for CBSD work out to
rationalize the evolution of a software system with four major phases-Component Selection, Integration, Testing
and Customer evaluation. There are several sub-phases - software analysis and specifications, design, coding
and archiving, component testing, component wrapping, domain analysis, domain engineering, system testing,
implementation and deployment, and maintenance of software components. O model helps in developing CBS
with the help of two CBSD approaches, namely, development for reuse and development with reuse. Finally, O
model appears to cover the likely phases of large software development and enforces software reusability along
its phases. Likewise, it takes into account previous knowledge that software engineers may have about the
application domain, which has an impact on the prevalent approach to be pursued during the software
development with this model.
References
[1] C. Szyperski, Component Software, Addison-Wesley, 1998.
[2] M. Aoyama, Componentware: Building Applications with Software Components, J. of IPSJ, Vol. 37, No. 1, Jan. 1996, pp. 71-79
(In Japanese).
[3] Microsoft, 2004. COM+, http://www.microsoft.com/com/tech/complus.asp.
[4] SUN, 2004.Enterprise Java Beans, http://www.java.sun.com/products/ejb/index.html.
[5] IBM,2004.Component Broker, http://www.software.ibm.com/ad/cb.
[6] Object Management Group, 2004. The Common Object Request Broker Architecture, http://www.omg.org.
[7] Wallnau, K. C., S.A. Hissam and R.C. Seacord,2002. Building Systems from Commercial Components. Addison-Wesley.
[8] Clements, P. and L. Northrop, 2002. Software Product Lines. Addison-Wesley.
[9] S. Cohen, D. Dori, U. de Haan, “A Software System Development Life Cycle Model for Improved Stakeholders Communication
and Collaboration”, International Journal of Computers, Communications &Control,Vol. V (2010), No. 1, pp. 20-41
[10] Royce, W.W., 1987. “Managing the development of large software systems”. Proceedings of 9th IEEE International Conference
on Software Engineering, pp: 328-338.
[11] Gill N. S. and Tomar P., “X Model: A New Component- Based Model”, MR International Journal of Engineering and
Technology, 2008, Vol. 1, No. 1 & 2, pp. 1-9.
[12] Luiz Fernando Capretz, " Y: A new Component-Based Software Life Cycle Model ", Journals of Computer Science1 (1) : pp.76-
82.
[13] Rajender Singh Chhillar, ParveenKajla, “A New Knot Model for Component Based Software Development”, International
Journal of Computer Science Issues Year: 2011 Vol: 8 Issue: 3 Pp.: 480-484
[14] LataNautiyal, Umesh Kumar Tiwari, Sushil Chandra Dimri, ShivaniBahuguna, “Elite: A New Component-Based Software
Development Model”, International Journal of Computer Technology & Applications (IJCTA), Vol 3, Issue 1, Jan 2012, pp 119-
124
[15] LataNautiyal, UmeshTiwari, SushilDimri&Shashidhar G. Koolagudi, “Component based Software Development- New Era with
new Innovation in Software Development,” International Journal of Computer Applications (IJCA), vol. 51, no. 19, pp. 5-9,
August 2012
[16] IvicaCrnkovic; Stig Larsson; Michel Chaudron, “Component-based Development Process and Component Lifecycle.” Online
Available: http://www.mrtc.mdh.se/publications/0953.pdf
[17] The W Model for Component-based Software Development [online]. Online Available: http://www.cs.man.ac.uk/~kung-
kiu/pub/seaa11b.pdf.