ASPECT-ORIENTED SPECIFICATION: A CASE STUDY IN SPACE DOMAIN

Author(s):  
SÉRGIO AGOSTINHO ◽  
ANA MOREIRA ◽  
ANDRÉ MARQUES ◽  
JOÃO ARAÚJO ◽  
RICARDO FERREIRA ◽  
...  

Aspect-oriented software development claims to improve several software engineering principles, such as modularization, abstraction and composition. The Aspect for the Space Domain project (ASSD) developed a metadata-driven approach for aspect-oriented requirements analysis. The main objectives of the ASSD project, funded by the European Space Agency , were to study the applicability and usefulness of aspect-orientation for the space domain (ground segment software projects in particular), focusing on the early stages of the software development life cycle. Therefore, this paper describes a rigorous representation for requirements analysis concepts, refines an approach for handling early aspects, and proposes a client/server architecture based on a metadata repository. The ASSD approach has been validated with two space domain case studies.

Author(s):  
Mrwan BenIdris ◽  
Hany Ammar ◽  
Dale Dzielski

Do developers postpone fixing Technical Debt (TD) in software systems? TD is a metaphor that refers to short-term decisions in software development that may affect the cost of the software development life cycle. The bad smell is an imperfect solution in the software system that negatively impacts the internal software quality and maintainability. In this paper, we will study five open-source software projects (OSSPs) that have several releases and also estimate the numbers of architecture smells (ASs), design smells (DSs), and code smells (CSs) for every release. Designite will be used to detect smells. We describe a case study conducted to explore the following: (1) What is the average smells density for architecture, design, and code smells in an OSSP? (2) Does the density of each smell type increase over multiple releases? (3) What percentage of each smell-type density is eliminated by refactoring? We collected around 2 million LOC from five OSSPs that have multiple releases from the GitHub repository to statistically analyze the software concerning the smells as indicators of TD. We find 36% of Architecture Technical Debt (ATD) is Cyclic Dependency, while 33% of Design Debt (DD) is Cyclically-dependent Modularization. More than 70% of Code Debt (CD) is Magic Number. Even though the developers do refactoring between releases, the TD density in general increases. On average, by refactoring, developers remove around 48%, 16%, and 22% from the introduced ATD, DD, and CD from their next release, respectively.


2011 ◽  
Vol 41 (2) ◽  
pp. 123-178 ◽  
Author(s):  
Arturo Russo

Mars Express is the first planetary mission accomplished by the European Space Agency (ESA). Launched in early June 2003, the spacecraft entered Mars's orbit on Christmas day of that year, demonstrating the new European commitment to planetary exploration. Following a failed attempt in the mid-1980s, two valid proposals for a European mission to Mars were submitted to ESA's decision-making bodies in the early 1990s, in step with renewed international interest in Mars exploration. Both were rejected, however, in the competitive selection process for the agency's Science Programme. Eventually, the Mars Express proposal emerged during a severe budgetary crisis in the mid-1990s as an exemplar of a “flexible mission” that could reduce project costs and development time. Its successful maneuvering through financial difficulties and conflicting scientific interests was due to the new management approach as well as to the public appeal of Mars exploration. In addition to providing a case study in the functioning of the ESA's Science Programme, the story of Mars Express discussed in this paper provides a case study in the functioning of the European Space Agency's Science Programme and suggests some general considerations on the peculiar position of space research in the general field of the history of science and technology.


2019 ◽  
Vol 21 (2) ◽  
pp. 51-64
Author(s):  
Priyanka Chandani ◽  
Chetna Gupta

Accurate time and budget is an essential estimate for planning software projects correctly. Quite often, the software projects fall into unrealistic estimates and the core reason generally owes to problems with the requirement analysis. For investigating such problems, risk has to identified and assessed at the requirement engineering phase only so that defects do not seep down to other software development phases. This article proposes a multi-criteria risk assessment model to compute risk at a requirement level by computing cumulative risk score based on a weighted score assigned to each criterion. The result of comparison with other approaches and experimentation shows that using this model it is possible to predict the risk at the early phase of software development life cycle with high accuracy.


2019 ◽  
Vol 13 (2) ◽  
pp. 179-186
Author(s):  
Paul Macarof ◽  
Florian Statescu ◽  
Cristian Iulian Birlica ◽  
Paul Gherasim

In this study was analyzed zones affected by drought using Vegetation Condition Index (VCI), that is based on Normalized Difference Vegetation Index (NDVI). This fact, drought, is one of the most wide -spread and least understood natural phenomena. In this paper was used remote sensing (RS) data, kindly provided by The European Space Agency (ESA), namely Sentinel-2 (S-2) Multispectral Instrument (MSI) and wellkonwn images Landsat 8 Operational Land Imager (OLI). The RS images was processed in SNAP and ArcMap. Study Area, was considered the eastern of Iasi county. The main purpose of paper was to investigating if Sentinel images can be used for VCI analysis.


2021 ◽  
Vol 9 (3) ◽  
pp. 262
Author(s):  
Florin Onea ◽  
Liliana Rusu ◽  
Gabriel Bogdan Carp ◽  
Eugen Rusu

The aim of the present work is to identify the expected nearshore and offshore impact of a marine energy farm that would be implemented in the coastal environment of Portugal. Several layouts of Wave Dragon devices were considered, the distance between each system being gradually adjusted. By processing 27–years of combined wave data coming from the European Space Agency and ERA5, the most relevant conditions have been identified. The centre of each farm layout was set to approximately 3.5 km from the coast, where a more significant attenuation of wave heights in the middle of the target area was noticed, which can go up to 16% in the case of extreme events. From the analysis of the longshore currents, it was noticed that even an arrow farm layout defined by five systems may have a significant impact, by changing the peak or by smoothing the currents profile. Wave energy is an emerging renewable sector that can also contribute tocoastal protection and, therefore, the Portuguese coast represents a suitable candidate for this type of project.


2014 ◽  
Vol 52 ◽  
Author(s):  
Daniel Acton ◽  
Derrick Kourie ◽  
Bruce Watson

As long as software has been produced, there have been efforts to strive for quality in software products. In order to understand quality in software products, researchers have built models of software quality that rely on metrics in an attempt to provide a quantitative view of software quality. The aim of these models is to provide software producers with the capability to define and evaluate metrics related to quality and use these metrics to improve the quality of the software they produce over time. The main disadvantage of these models is that they require effort and resources to define and evaluate metrics from software projects. This article briefly describes some prominent models of software quality in the literature and continues to describe a new approach to gaining insight into quality in software development projects. A case study based on this new approach is described and results from the case study are discussed.


Author(s):  
Maciej Łabędzki ◽  
Patryk Promiński ◽  
Adam Rybicki ◽  
Marcin Wolski

Aim:Aim: The purpose of this paper is to identify common mistakes and pitfalls as well as best practices in estimating labor intensity in software projects. The quality of estimations in less experienced teams is often unsatisfactory, as a result of which estimation as part of the software development process is abandoned. The decision is usually justified by misunderstanding "agility". This article is part of the discussion on current trends in estimation, especially in the context of the new "no estimates" approach.Design / Research methods: The publication is a case study based on the experience of a mature development team. The author, on the basis of literature-based estimation techniques, shows good and bad practices, as well as common mistakes in thinking and behavior.Conclusions / findings: The key to correct estimation is: understanding the difference between labor intensity and time, ability to monitor performance, as well as how to analyze staff requirements for the team.Originality / value of the article: The publication helps to master confidence-boosting techniques for any estimation (duration, and indirectly, the cost of software development) where requirements are known, but mainly at the stage of project implementation (design and implementation).Limitations of the research: The work does not address the problems of initial estimation of projects, i.e. the estimation made in the early stages of planning.


2012 ◽  
Vol 11 (01) ◽  
pp. 1250001
Author(s):  
David P. Stevens ◽  
Sonya H. Y. Hsu ◽  
Zhiwei Zhu

The acquisition and management of knowledge is increasingly more important in today's economy because of the large proportion of the workforce eligible for retirement in the next 10 years. Companies have long understood that reusing explicit knowledge in the form of policies, documentation and procedures produces tremendous savings, reduces variability, decreases costs, and improves overall quality. Unfortunately, a considerable portion of corporate knowledge is tacit or known at a non-verbal level, and does not lend itself to reuse. This research examines "how" and "why" questions regarding a specific process used for managing and sharing tacit knowledge related to the software development life cycle. The issues related to acquiring, preserving and disseminating the tacit knowledge are discussed in detail, and the advantages and managerial implications of the results of the method are described, together with implications for knowledge workers and managers in other industries.


Sign in / Sign up

Export Citation Format

Share Document