• No results found

Software evolution

Volume 8: ERCIM Symposium on Software Evolution 2007

Volume 8: ERCIM Symposium on Software Evolution 2007

... on Software Evolution, co-located with ICSM in Paris in October ...on Software Evolution, gather- ing researchers from all over the world to identify and discuss recent advancements and ...

5

Dynamic Software Evolution and The K Component Model

Dynamic Software Evolution and The K Component Model

... of software systems that can benefit from dynamic software evolution, including 24x7 systems that require on-line upgrades and adaptive systems that need to adapt to frequent changes in their ...

6

Attribute Series of Software Evolution for Software Quality Assessment

Attribute Series of Software Evolution for Software Quality Assessment

... of software increased from day to day, the software quality assurance must be used to make a balance between quality and ...In software applications defect density and defect prediction are essential ...

7

Volume 8: ERCIM Symposium on Software Evolution 2007

Volume 8: ERCIM Symposium on Software Evolution 2007

... The subjects were 13 students from the course of Laboratory of Software Analysis, in their last year of the master degree in computer science at the University of Trento. The subjects had a good knowledge about ...

13

Managing software evolution through midleware and policy-based software adaptation framework

Managing software evolution through midleware and policy-based software adaptation framework

... term software evolution and software maintenance are used interchangeably in a number of ...between software evolution and software ...that software maintenance comprises ...

38

An evaluation of traceability approaches to support software evolution

An evaluation of traceability approaches to support software evolution

... EB approach assumes that there are already available links between requirements and UML artifacts including test cases. Source code is excluded. The approach then runs its maintenance mechanism upon those artifacts and ...

8

SOFTWARE DATA GRAPHS USING ONTOLOGY-DRIVEN SOFTWARE EVOLUTION AND ITS APPLICATION

SOFTWARE DATA GRAPHS USING ONTOLOGY-DRIVEN SOFTWARE EVOLUTION AND ITS APPLICATION

... Ontology-Driven Software Evolution falls into key areas (views): Context View, Inter-model View, City View, Metric View, Transformation View, Evolution View and Evaluation view [9] and 22 Key ...

10

Volume 8: ERCIM Symposium on Software Evolution 2007

Volume 8: ERCIM Symposium on Software Evolution 2007

... Abstract: Software evolution entails more than just redesigning and reimplement- ing functionality of, fixing bugs in, or adding new features to source ...the evolution of the Linux build ...

17

8-software evolution

8-software evolution

...  Maintenance costs depend on the number of changes and. costs of change depend on maintainability..[r] ...

31

Volume 8: ERCIM Symposium on Software Evolution 2007

Volume 8: ERCIM Symposium on Software Evolution 2007

... Goal: The long-term objective of this research is to evaluate metrics to identify success- ful FLOSS projects, and to provide guidelines to FLOSS developers about practical actions to foster the successful ...

15

Volume 8: ERCIM Symposium on Software Evolution 2007

Volume 8: ERCIM Symposium on Software Evolution 2007

... current software development practice requires efficient model-based iterative ...and evolution during the life cycle of the software can be reduced by using tool-aided iterative ...iterative ...

14

Volume 8: ERCIM Symposium on Software Evolution 2007

Volume 8: ERCIM Symposium on Software Evolution 2007

... A UML model is composed of different diagrams that address different aspects of a software system. The application of model refactorings may generate inconsistencies between these UML diagrams. Future work should ...

16

Volume 8: ERCIM Symposium on Software Evolution 2007

Volume 8: ERCIM Symposium on Software Evolution 2007

... The main objective of the research described is to assess how a system changes through the analysis of packages in the system and to compare that data with corresponding results from refactoring the same system. ...

15

Volume 8: ERCIM Symposium on Software Evolution 2007

Volume 8: ERCIM Symposium on Software Evolution 2007

... oriented software systems and shown that although software grows and changes over time, the structure and scope of both growth and change is, in general, predictable rather than erratic or purely random ...

12

Volume 8: ERCIM Symposium on Software Evolution 2007

Volume 8: ERCIM Symposium on Software Evolution 2007

... To support maintenance scenarios for large software systems, where manual effort is error prone or does not scale, developers are in need of tools. In the past, several engineering techniques have been examined ...

15

Volume 8: ERCIM Symposium on Software Evolution 2007

Volume 8: ERCIM Symposium on Software Evolution 2007

... Client program C1, on the other hand, has a lot of data dependencies with missing copybooks (the black nodes above).. This is the program that retrieves information from other systems to[r] ...

13

Volume 3: Software Evolution through Transformations 2006

Volume 3: Software Evolution through Transformations 2006

... Our second goal is accomplished by demonstrating that the transformation rules can be adapted to the evolution of both applications and techniques being used in the transformation. Such adaptation is facilitated ...

14

Volume 3: Software Evolution through Transformations 2006

Volume 3: Software Evolution through Transformations 2006

... Views have been used in different activities of software construction because they help the developer to delimit the scope of a problem and thus, its complexity. Therefore, the developer can analyze the ...

14

Volume 3: Software Evolution through Transformations 2006

Volume 3: Software Evolution through Transformations 2006

... Following this direction, Model Management [BHP00] is a new emergent discipline that pur- sues an abstract reusable solution for problems of this kind, independently of the metamodel un- der study. The Model Management ...

20

Volume 3: Software Evolution through Transformations 2006

Volume 3: Software Evolution through Transformations 2006

... This contribution tries to narrow the bridge between industrial, code-centric development with C++ and model-centric development employing languages like the Unified Modeling Lan- guage (UML). We discuss a C++ metamodel ...

16

Show all 10000 documents...

Related subjects