Effort Estimation in Model-Based Software Development

Vitkin, Lev; Dong, Susan; Searcy, Rick; Manjunath, BC

doi:10.4271/2006-01-0309

Cited by 4 publications

(6 citation statements)

References 7 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…e.g. [17]), they make it possible to improve the overall model-based development and quality assurance approach.…”

Section: Discussionmentioning

confidence: 99%

“…For that reason, the else-branch (lines [15][16][17][18][19] of the second if-statement can never be executed and therefore contains dead code (bold). The identical if-statements in line 10 and 11 were caused by inappropriate Flowchart modeling.…”

Section: Examplementioning

confidence: 99%

“…The complexity number computed is incremented by 1 for atomic subsystems and Stateflow charts [17]. CYC Mod of the IM amounts to 1284.…”

Section: Implementation Modelmentioning

confidence: 99%

See 2 more Smart Citations

Experiences with model and autocode reviews in model-based software development

Stürmer

Conrad

Fey

et al. 2006

Proceedings of the 2006 International Workshop on Software Engineering for Automotive Systems

View full text Add to dashboard Cite

Through the introduction of model-based development, paradigm models became first class citizens in the development of invehicle software and are thus also object to strict quality assurance. Just as code reviews are widespread in classical software development, models also have to undergo a stringent review procedure -particularly if they serve as a basis for automatic software implementation by means of model-based code generators. In addition to model reviews, the generated production code (autocode) must be reviewed by performing so-called autocode reviews. This paper presents our procedure for a combined model and autocode review and provides examples, lessons learned, as well as significant experimental results drawn from a typical automotive embedded software development project.

show abstract

“…e.g. [17]), they make it possible to improve the overall model-based development and quality assurance approach.…”

Section: Discussionmentioning

confidence: 99%

Section: Examplementioning

confidence: 99%

See 1 more Smart Citation

Experiences with model and autocode reviews in model-based software development

Stürmer

Conrad

Fey

et al. 2006

Proceedings of the 2006 International Workshop on Software Engineering for Automotive Systems

View full text Add to dashboard Cite

show abstract

“…No direct method to compute such a metric is known to exist in research literature; the closest approach was that followed by Vitkin et al [8], who derived structural metrics from Simulink models for the purpose of estimating autocoding effort. In the following discussion, their approach is first summarized, and then the customizations needed to reflect an appropriate metric of modifiability are detailed.…”

Section: Extracting Structural Information From Functional Modelsmentioning

confidence: 99%

Integrating Functional and Non-Functional Design Verification for Embedded Software Systems

Ackermann

Ray

Cleaveland³

et al. 2009

SAE Technical Paper Series

View full text Add to dashboard Cite

This paper describes an approach to integrating functional and non-functional design verification for embedded control software. The method uses functional models, which have traditionally been used in functional verification processes, to drive non-functional verification also. This is achieved by defining strategies for extracting non-functional models, which contain structural and quantitative information about nonfunctional characteristics such as performance and modifiability, from functional ones. Non-functional verification tools may then be used on the resulting models to check that desired non-functional properties, such as ease of modification, are catered for in the design. An extended example involving the analysis of a model for modifiability is presented, as is tool support for extracting non-functional models from functional ones.

show abstract

“…Model-based software development is a way to overcome the increasing complexity of software products and their changeability (Vitkin et al, 2006). It is based on dividing the software development into two separated processes: domain engineering and application engineering.…”

Section: Introductionmentioning

confidence: 99%

A Model-based Software Technology Proposal

Kotkas

Penjam

Kalja

et al. 2013

Proceedings of the 1st International Conference on Model-Driven Engineering and Software Development

View full text Add to dashboard Cite

Keywords:Model-based Software Development, Application Engineering. Abstract:In this paper we propose a technology for model-based software development. The technology separates domain engineering and application engineering and automates the actual executable code generation. This approach has been used extensively for simulations and we believe it is also applicable for more general software development.A Model-based Software Technology Proposal.

show abstract

Effort Estimation in Model-Based Software Development

Cited by 4 publications

References 7 publications

Experiences with model and autocode reviews in model-based software development

Experiences with model and autocode reviews in model-based software development

Integrating Functional and Non-Functional Design Verification for Embedded Software Systems

A Model-based Software Technology Proposal

Contact Info

Product

Resources

About