f-COCOMO: fuzzy constructive cost model in software engineering

2003 ◽  
Author(s):  
Z. Fei ◽  
X. Liu
Keyword(s):  
Software Engineering ◽  
Cost Model

The Technical Debt in Cloud Software Engineering

2015 ◽  
pp. 24-42 ◽  
Author(s):  
Georgios Skourletopoulos ◽  
Rami Bahsoon ◽  
Constandinos X. Mavromoustakis ◽  
George Mastorakis
Keyword(s):  
Software Engineering ◽  
Cost Estimation ◽  
Cost Model ◽  
Service Selection ◽  
Cloud Service ◽  
Cloud Services ◽  
Software As A Service ◽  
Technical Debt ◽  
Selection Decisions ◽  
The Cost

Predicting and quantifying promptly the Technical Debt has turned into an issue of significant importance over recent years. In the cloud marketplace, where cloud services can be leased, the difficulty to identify the Technical Debt effectively can have a significant impact. In this chapter, the probability of introducing the Technical Debt due to budget and cloud service selection decisions is investigated. A cost estimation approach for implementing Software as a Service (SaaS) in the cloud is examined, indicating three scenarios for predicting the incurrence of Technical Debt in the future. The Constructive Cost Model (COCOMO) is used in order to estimate the cost of the implementation and define a range of secureness by adopting a tolerance value for prediction. Furthermore, a Technical Debt quantification approach is researched for leasing a cloud Software as a Service (SaaS) in order to provide insights about the most appropriate cloud service to be selected.

Abstraction: An alternative neurocognitive account of recognition, prediction, and decision making

2020 ◽  
Vol 43 ◽  
Author(s):  
Valerie F. Reyna ◽  
David A. Broniatowski
Keyword(s):  
Decision Making ◽  
Software Engineering ◽  
Systems Engineering ◽  
Evidence Based ◽  
Extensive Literature ◽  
Trace Theory ◽  
Fuzzy Trace Theory ◽  
Abstract Representations ◽  
Technical Systems

Abstract Gilead et al. offer a thoughtful and much-needed treatment of abstraction. However, it fails to build on an extensive literature on abstraction, representational diversity, neurocognition, and psychopathology that provides important constraints and alternative evidence-based conceptions. We draw on conceptions in software engineering, socio-technical systems engineering, and a neurocognitive theory with abstract representations of gist at its core, fuzzy-trace theory.

A Spreadsheet Life Cycle Cost Model for System Modernization Studies

1994 ◽  
Vol 11 (1) ◽  
pp. 47-56
Author(s):  
Virginia C. Day ◽  
Zachary F. Lansdowne ◽  
Richard A Moynihan ◽  
John A. Vitkevich
Keyword(s):  
Life Cycle ◽  
Life Cycle Cost ◽  
Cost Model

Software Engineering for Real Time Systems

IEE Review ◽  
1992 ◽  
Vol 38 (3) ◽  
pp. 112
Author(s):  
Stuart Bennett
Keyword(s):  
Software Engineering ◽  
Real Time ◽  
Real Time Systems ◽  
Time Systems

Rationale and Design Considerations for a Semantic Mediator in Health Information Systems

1998 ◽  
Vol 37 (04/05) ◽  
pp. 518-526 ◽  
Author(s):  
D. Sauquet ◽  
M.-C. Jaulent ◽  
E. Zapletal ◽  
M. Lavril ◽  
P. Degoulet
Keyword(s):  
Information Systems ◽  
Software Engineering ◽  
Health Information ◽  
Rapid Development ◽  
Heterogeneous Systems ◽  
Health Information Systems ◽  
Semantic Interoperability ◽  
Point Of View ◽  
Current State ◽  
Engineering Environment

AbstractRapid development of community health information networks raises the issue of semantic interoperability between distributed and heterogeneous systems. Indeed, operational health information systems originate from heterogeneous teams of independent developers and have to cooperate in order to exchange data and services. A good cooperation is based on a good understanding of the messages exchanged between the systems. The main issue of semantic interoperability is to ensure that the exchange is not only possible but also meaningful. The main objective of this paper is to analyze semantic interoperability from a software engineering point of view. It describes the principles for the design of a semantic mediator (SM) in the framework of a distributed object manager (DOM). The mediator is itself a component that should allow the exchange of messages independently of languages and platforms. The functional architecture of such a SM is detailed. These principles have been partly applied in the context of the HEllOS object-oriented software engineering environment. The resulting service components are presented with their current state of achievement.

Sign in / Sign up

Export Citation Format

Share Document