Evaluation of Component-Based Development Methods

2011 ◽  
pp. 323-343 ◽  
Author(s):  
Nicky Boertien ◽  
Maarten W.A. Steen ◽  
Henk Jonkers
Keyword(s):  
Software Engineering ◽  
Software Development ◽  
Complete Solution ◽  
Business Development ◽  
Full Potential ◽  
Time To Market ◽  
Component Based Development ◽  
Unified Process ◽  
Business Engineering ◽  
Development Methods

Component-based development (CBD) has received a lot of attention in software engineering literature over the last few years. Awareness has been raised that CBD is the way to go in software development, especially in the domain of e-business where the benefits of reusing components, i.e., faster time-to-market and quality, are essential. The question now is how to realize the full potential of CBD? Did we achieve reuse yet? In order to answer these questions, we evaluate and compare five popular methods for component-based development, including Catalysis, the Rational Unified Process, and Select Perspective, on their maturity and fitness-for-use in the context of e-business engineering. The evaluation is done based on our own reference framework for e-business development and a list of objective criteria. The methods each emphasize certain aspects of CBD, but as yet none of them offers a complete solution.

An Analysis of Process Characteristics for Developing Scientific Software

2011 ◽  
Vol 23 (4) ◽  
pp. 64-79 ◽  
Author(s):  
Diane Kelly
Keyword(s):  
Software Engineering ◽  
Software Development ◽  
Professional Training ◽  
Scientific Software ◽  
Development Environment ◽  
Engineering Development ◽  
Development Processes ◽  
Agile Software ◽  
Development Methods ◽  
Software Development Methods

The development of scientific software is usually carried out by a scientist who has little professional training as a software developer. Concerns exist that such development produces low-quality products, leading to low-quality science. These concerns have led to recommendations and the imposition of software engineering development processes and standards on the scientists. This paper utilizes different frameworks to investigate and map characteristics of the scientific software development environment to the assumptions made in plan-driven software development methods and agile software development methods. This mapping exposes a mismatch between the needs and goals of scientific software development and the assumptions and goals of well-known software engineering development processes.

Positive and Negative Innovations in Software Engineering

2012 ◽  
pp. 252-263
Author(s):  
Capers Jones
Keyword(s):  
Software Engineering ◽  
Software Development ◽  
Productivity Costs ◽  
Software Applications ◽  
Project Outcomes ◽  
The World ◽  
Development Methods ◽  
Software Development Methods ◽  
The Way

The software engineering field has been a fountain of innovation. Ideas and inventions from the software domain have literally changed the world as we know it. For software development, we have a few proven innovations. The way software is built remains surprisingly primitive. Even in 2008 major software applications are cancelled, overrun their budgets and schedules, and often have hazardously bad quality levels when released. There have been many attempts to improve software development, but progress has resembled a drunkard’s walk. Some attempts have been beneficial, but others have been either ineffective or harmful. This article puts forth the hypothesis that the main reason for the shortage of positive innovation in software development methods is due to a lack of understanding of the underlying problems of the software development domain. A corollary hypothesis is that lack of understanding of the problems is due to inadequate measurement of quality, productivity, costs, and the factors that affect project outcomes.

Practical Experience in Customization for a Software Development Process for Small Companies Based on RUP Process and MSF

2011 ◽  
pp. 71-93 ◽  
Author(s):  
Valerio Fernandes del Maschi ◽  
Luciano S. Souza ◽  
Mauro de Mesquita Spínola ◽  
Wilson Vendramel ◽  
Ivanir Costa ◽  
...  
Keyword(s):  
Software Engineering ◽  
Software Development ◽  
Development Process ◽  
Practical Experience ◽  
Software Development Process ◽  
Small Companies ◽  
Engineering Process ◽  
Software Projects ◽  
Software Engineering Process ◽  
Unified Process

The quality in software projects is related the deliveries that are adjusted to the use, and that they take care of to the objectives. In this way, Brazilian organizations of software development, especially the small and medium ones, need to demonstrate to future customers whom an initial understand of the business problem has enough. This chapter has as objective to demonstrate methodology, strategy, main phases and procedures adopted beyond the gotten ones of a small organization of development of software in the implantation of a Customized Software Engineering Process and of a Tool of Support to the Process in the period of 2004 to 2006 on the basis of rational unified process (RUP) and in the Microsoft solutions framework (MSF).

Software Engineering in Australasia

2021 ◽  
Vol 46 (2) ◽  
pp. 16-17
Author(s):  
Sherlock A. Licorish ◽  
Christoph Treude ◽  
John Grundy ◽  
Kelly Blincoe ◽  
Stephen MacDonell ◽  
...  
Keyword(s):  
New Zealand ◽  
Software Engineering ◽  
Software Development ◽  
Current Position ◽  
Engineering Community ◽  
Development Methods ◽  
Software Development Methods ◽  
The Way

Six months ago an important call was made for researchers globally to provide insights into the way Software Engineering is done in their region. Heeding this call, we hereby outline the position Software Engineering in Australasia (New Zealand and Australia). This article first considers the software development methods, practices and tools that are popular in the Australasian software engineering community. We then briefly review the particular strengths of software engineering researchers in Australasia. Finally, we make an open call for collaborators by reflecting on our current position and identifying future opportunities.

scholarly journals Rebuilding Cultural and Heritage Space of Corregidor Island using GPS-Based Augmented Reality

2019 ◽  
Vol 8 (2S11) ◽  
pp. 2799-2804
Keyword(s):  
Software Engineering ◽  
Augmented Reality ◽  
Software Development ◽  
Mobile Applications ◽  
Evaluation Tool ◽  
Tour Guide ◽  
Historical Information ◽  
Development Tools ◽  
Unified Process ◽  
Software Development Tools

One of the biggest impact of Augmented reality was on the architectural and construction industries. The AR ability to design and construct beyond visualization by virtually walking through the completed model draws inspiration among the researchers the desire to preserve memories behind the war-ravaged buildings that have not been restored, and left as they were after the war in reverence to the Filipino and American soldiers . The software engineering tool , rational unified process , was used as a guide in developing the application with the aid of Android Studio, Unity, Vofuria, Lumion8 and sketch-up as software development tools. The application was tested and evaluated by IT experts and tourists of Corregidor using the SUS evaluation tool. Based on the overall satisfaction, usefulness and ease of used among the tourists of Corregidors is “Excellent” which means that the developed mobile applications is more immersive and engaging that will make tourist journey more exciting at the Corregidor Island. This application can assist tourist in experiencing more interactive, fun and engaging journey in Corregidor. Furthermore, this application can served as a mobile tour guide application made for the tourist of Corregidor Island that shall help them learn more about the history and the significance of Corregidor Island by the use of augmented reality to show the original setup of the ruins. The application will help NCCA cascade the historical information about the island and its significance during the war.

An Analysis of Process Characteristics for Developing Scientific Software

2012 ◽  
pp. 347-363
Author(s):  
Diane Kelly
Keyword(s):  
Software Engineering ◽  
Software Development ◽  
Professional Training ◽  
Scientific Software ◽  
Development Environment ◽  
Engineering Development ◽  
Process Characteristics ◽  
Development Processes ◽  
Development Methods ◽  
Software Development Methods

The development of scientific software is usually carried out by a scientist who has little professional training as a software developer. Concerns exist that such development produces low-quality products, leading to low-quality science. These concerns have led to recommendations and the imposition of software engineering development processes and standards on the scientists. This paper utilizes different frameworks to investigate and map characteristics of the scientific software development environment to the assumptions made in plan-driven software development methods and agile software development methods. This mapping exposes a mismatch between the needs and goals of scientific software development and the assumptions and goals of well-known software engineering development processes.

The What, How, and When of Formal Methods

2019 ◽  
pp. 1600-1614
Author(s):  
Aristides Dasso ◽  
Ana Funes
Keyword(s):  
Software Engineering ◽  
Software Development ◽  
Formal Methods ◽  
Development Process ◽  
Software Requirements ◽  
Software Development Process ◽  
Security And Reliability ◽  
Development Methods

Questions such as what are formal methods, how are formal methods implemented, how are they used in software engineering, and when should they be used, among other related questions are the main objective of this chapter. Some definitions are given to answer some of these questions; the chapter also states the aims of FM as well as giving their main characteristics. An example that shows how formal methods can be used for specifying not only software requirements but also the rest of the stages in a software development process is given. A discussion about when they should be used, explaining the reasons why they should be applied when security and reliability are important requirements of the software under development, is presented. Finally, some arguments about how they can also be used as a complement to traditional development methods are provided.

scholarly journals Rational United Process Part - II Best Practices for Software Development Team

2003 ◽  
Vol 1 (2) ◽  
pp. 69-81
Author(s):  
Manoj Tharian
Keyword(s):  
Best Practices ◽  
Software Development ◽  
Business Processes ◽  
Use Cases ◽  
Development Effort ◽  
Business Object ◽  
Software Development Effort ◽  
Unified Process ◽  
Business Engineering ◽  
Common Understanding

One Of the major problems with most business engineering efforts, is frat the software engineering and the business engineering community do not communicate properly With each other. This leads to that the Output from business engineering is not used properly as input to the software development effort, and viceversc. The Rational Unified Process addresses this by providing a common language and process for both communities, cs we" os showing how to create and maintain direct traceability between and soft-wore rnodels. In Business Modeling we document business processes using so called business use cases. This assures a common understanding among a" stakeholders Of What business process needs to be supported in the organization. The business use cases cre analyzed to understand how the business should support the I O business processes. This is documented in a business object-model. Many projects may choose not do modéing. Requirements The goal Of the Requirements workaow is 'o describe What the system should do and allows the agree on that description. TO achieve

The What, How, and When of Formal Methods

2018 ◽  
pp. 7609-7621
Author(s):  
Aristides Dasso ◽  
Ana Funes
Keyword(s):  
Software Engineering ◽  
Software Development ◽  
Formal Methods ◽  
Development Process ◽  
Software Requirements ◽  
Software Development Process ◽  
Security And Reliability ◽  
Development Methods

Questions such as what are Formal Methods, how are Formal Methods implemented, how are they used in Software Engineering and when should they be used, among other related questions, are the main objective of this article. Some definitions are given to answer some of these questions; the article also states the aims of FM as well as it gives their main characteristics. An example that shows how Formal Methods can be used for specifying not only software requirements but also the rest of the stages in a software development process is given. A discussion about when they should be used, explaining the reasons why they should be applied when security and reliability are important requirements of the software under development, is presented. Finally, some arguments about how they can also be used as a complement to traditional development methods are provided.

scholarly journals The Adoption of Agile Software Methodology with Team Software Process (TSPI) Practices in the Software Engineering Undergraduate Course

2018 ◽  
Vol 7 (1) ◽  
pp. 1-8
Author(s):  
Nurfauza Jali ◽  
Azman Bujang Masli ◽  
Wai Shiang Cheah ◽  
Yanti Rosmunie Bujang ◽  
Abdul Rahman Mat ◽  
...  
Keyword(s):  
Software Engineering ◽  
Software Development ◽  
Undergraduate Students ◽  
Engineering Students ◽  
Software Process ◽  
Software Methodology ◽  
Team Software Process ◽  
Agile Software ◽  
Methodological Aspects ◽  
Development Methods

In computer science, software engineering courses expose the undergraduate students to both the technical and methodological aspects of software development. The traditional software development methods and techniques represent a huge proportion of the courses and hence contribute an essential part of software engineering students’ development process. This plan-driven development is dependent on a set of predefined phases and ongoing documentation which found to be problematic; such as time-consuming, slipped requirements and complicated processes. The main aim of this paper is to study and review the adoption of Agile Software Methodology and Team Software Process (TSPi) practices in the undergraduate course focus on software development. The framework and course plan will be designed to apply and observe the implementation. Furthermore, this study will help to gather the teams’ viewpoint regarding the importance of Agile and TSPi practices in handling small projects with real clients.

Sign in / Sign up

Export Citation Format

Share Document