Differences
This shows you the differences between two versions of the page.
|
cfp [2014/03/20 14:10] labsoft |
cfp [2014/06/20 19:36] (current) labsoft [Important Dates] |
||
|---|---|---|---|
| Line 4: | Line 4: | ||
| - | === Important Dates === | + | ===== Important Dates ===== |
| - | * Paper Submission: //To be defined// | + | * Paper Submission: 30 June 2014 ([[http://www.timeanddate.com/worldclock/usa/baker-island|Anywhere on Earth]]) |
| - | * Authors Notification: //To be defined// | + | * Authors Notification: 15 July 2014 |
| - | * Final version of the Papers (camera-ready): //To be define// | + | * Final version of the Papers (camera-ready): 23 July 2014 |
| - | * Workshop: 09/28/2014 | + | * Workshop: 28 September 2014 |
| + | ===== Motivation ===== | ||
| - | ===== Overview ===== | ||
| + | The growing need to maintain and evolve software systems is a major challenge in modern software engineering. Several studies show that software evolution or maintenance tasks have been responsible for a considerable cost on the development process, reaching in some cases, 90% of the total cost. Evolving complex software systems, however, requires advanced means for understanding the software artifacts to be modified. Software comprehension is a non-trivial task. Software visualization relies on the use of visual resources to facilitate software comprehension, either through the analysis of a single system version or the system entire version history. Due to this clear intersection of the research challenges involving the areas of Software Visualization, Software Evolution, and Software Maintenance, there is a need for a joint forum to discuss these challenges together. The second Workshop on Software Visualization, Maintenance, and Evolution (VEM 2014) aims at bringing together the research communities interested in topics related to Software Visualization, Software Evolution, and Software Maintenance to share and discuss ideas, strengthen research group collaborations and identify new research opportunities. | ||
| - | With the steady growth of software projects, along with the vast processing power of computers, new research has been developed to allow a better understanding of the structure, behavior and evolution of software process and product. This research makes use of visualization tools and techniques applied in the context of software, encouraging the rise of the software visualization field. | ||
| - | Software visualization uses visual abstractions to represent various properties of software systems, in order to reveal patterns and behaviors that otherwise would remain hidden. For this reason, the design and use of visual resources are very important for software engineering. | + | ===== Topics of interest===== |
| + | Topics of interest are related to several research challenges in Software Visualization, Software Evolution, and Software Maintenance. They include, but are not limited to: | ||
| - | It is noteworthy that software visualization is an area of direct or indirect interest of to a large part of the software community. Some software engineering areas, such as testing, configuration management, architecture, development environments, among others, are potential users of techniques for visualizing software. | + | * Processes of software maintenance and evolution |
| - | + | * Metrics and assessment of evolving software | |
| - | Software visualization is a specialization of information visualization. The synergy with the information visualization community is a successful strategy for using resources already established in the latter. For this reason, issues related to information visualization are also included in the workshop topics of interest. | + | * Empirical studies about software visualization, evolution, and maintenance |
| - | Topics of Interest | + | * Maintenance and evolution of Web applications |
| - | + | * Maintenance and evolution of applications in the cloud | |
| - | VEM topics of interest include, amongst others: | + | * Software architecture, product lines, components and frameworks |
| - | + | * Aspect orientation, feature orientation, and generative programming | |
| - | * Modern processes of maintenance and evolution of software | + | * Tools and environments for software maintenance and evolution |
| - | * Metrics and quality for the maintenance and evolution of software | + | * Reverse engineering, reengineering, and refactoring |
| - | * Maintenance and evolution of "unconventional" systems, such as Web applications, aspect-oriented programs, based on models, lines of software products and applications in the cloud | + | * Static and dynamic analysis |
| - | * Tools and environments for the maintenance and evolution of software | + | * Migration of legacy software systems |
| - | * Reverse engineering, reengineering and system migration | + | * Static and dynamic software visualization |
| - | * Static analysis and dynamic analysis software | + | * Views in integrated development environments |
| - | * Visualization techniques to the understanding and support of programs | + | * Computational Reflection and Metaprogramming |
| - | * Teaching display, maintenance or evolution of software | + | * Education of software visualization, evolution, and maintenance |
| - | * Experimentation in visualization, maintenance or evolution of software management software (risk management, configuration management, planning and estimates) | + | |
| - | * Legacy systems test | + | |
| - | * Economic aspects of the maintenance and evolution of software (cost of maintenance previous estimate of effort, etc.). | + | |
| - | * Static and dynamic source code view | + | |
| - | * Viewing aspects of software evolution | + | |
| - | * View software engineering activities, such as engineering requirements, testing and maintenance | + | |
| - | * View workflow and business processes | + | |
| - | * Viewing software development environments | + | |
| - | * View databases | + | |
| - | * Flow visualization of networks | + | |
| - | * 3D visualization software | + | |
| | | ||
