Journal Information
Journal of Software: Evolution and Process
http://onlinelibrary.wiley.com/journal/10.1002/%28ISSN%292047-7481
Impact Factor:
0.606
Publisher:
John Wiley & Sons, Ltd
ISSN:
2047-7481
Viewed:
3609
Tracked:
3

Advertisment
Call For Papers
The “Journal of Software: Evolution and Process” is an archival journal that publishes high quality, state-of-the-art research and practice papers dealing with the conception, development, testing, management, quality, maintenance, and evolution of software, systems, and services, as well as the continuous improvement of processes and capabilities surrounding them. The journal continues the tradition of “The Journal of Software Maintenance and Evolution: Research and Practice” and “Software Process: Improvements and Practice”. We will therefore continue to cover the traditional topics related to software maintenance and evolution as well as software process improvement and practice. At the same time, the concept behind the journal has evolved into a unified vision that recognizes the fundamental changes and transformations that are occurring in the fields of software and systems engineering and the need for us to adapt by broadening the topics that we address and the research methods that are used coupled with the perspectives that are utilised.

Fundamental changes are occurring in the variety, scale and scope of software, systems and services that are being developed from new web and mobile computing to battle theatre technologies and everything in between.

Areas of interest include but are not limited to:

    How software, systems and enabled services are conceived, justified, created, managed, maintained and evolved over time
    How new underlying technologies (which are constantly changing) can be elegantly integrated and dealt with as systems evolve over time
    How new platforms and architectures are developed, tested, modified, and evolved to create the variety of applications needed now, and in the future
    How new processes and tools can be utilised in all phases of the development lifecycle (from system concept to test) in order to conceive, justify, create, modify and evolve these new technologies, platforms, systems and services
    How high-level representations of existing software, systems and services can be reverse engineered and used to support maintenance and evolution
    How people issues regarding cross disciplinary or geographically dispersed virtual teams can be addressed
    How the skill sets needed to participate and manage these projects will be developed
    How globally dispersed projects should be managed
    How new models of collaboration and participation will be deployed and managed
    What models will be used to estimate costs and predict performance of projects and process changes
    The technical, schedule, budgetary and other risks associated with developing and evolving new systems and how they will be managed
    How to improve organisational capability and maturity
    How maturity assessments and evaluations can contribute to organisations
    How to continuously improve processes associated with software, systems and services
    The new business models that are needed for the software, systems, and services
    What the performance impact of process changes will be
    How process change efforts impacting systems and services will be managed and organised
    How justification, sourcing and technical development decisions will be made as software and systems evolve from products to services, or more likely a combination of both, along with tiered levels of service based on a “pay as you go” and “value in use” business models
    How the impacts of agile development and management of new software, systems and services will impact
    systems, services and organisations

The journal publishes research papers, empirical studies and state-of-the-art surveys. Occasionally, we publish special issues on topics of particular interest; proposals for such issues are welcome. 
Last updated by Dou Sun in 2013-10-03
Special Issues
Special Issue on Sound and Practical Unanticipated Reuse of Software (SPURS)
Submission Date: 2017-06-17

Classical software reuse demands that we predict well the future needs of software systems so that some of their functionality can be modularized in an easily reused form; this is anticipated reuse, including such standard industrial technologies as object-oriented inheritance, software components, and software product lines. Since our ability to predict the future is less than perfect, there occur cases where a developer cannot find a modularized, reusable artifact that meets their needs. To deal with these cases, other options that support unanticipated reuse are also needed. The most obvious approach supporting unanticipated reuse is copy-and-modify: for example, when a software developer is faced with a development problem, they will often search the web for coding solutions that appear to solve their problem, and then they will modify this code to fit their particular needs. Due to the high costs associated with other alternatives, copy-and-modify is often seen as a viable, pragmatic choice in industry. Copy-and-modify has benefits: customizability is not limited to an interface provided by a 3rd party and there is no need to depend on unwanted functionality. But copy-and-modify also has drawbacks: the reuser can make poor decisions about what to reuse; the lack of tool support for these tasks makes them error-prone; and there is little assurance that constraints on the originating system remain in force in the target system. On a large scale, the result can be high error rates, poor comprehensibility, and poor performance. Improvements are needed to make this industrially relevant process less risky. This special issue solicits original contributions presenting approaches that are both practical (meaning, potentially scalable to industrial-sized systems; potentially usable by industrial developers in a realistic setting) and soundness-aware (meaning, either formally sound or that limit the developer’s attention to portions of the work that are not provably sound, requiring manual intervention) for any or all of the classic phases in the reuse process: artifact selection; adaptation to and integration with the target environment; and verification that the final system conforms to pertinent constraints on the original system. To provide a common basis for comparison of techniques, two motivational examples and four case studies are provided in which some feature is to be extracted from an industrial system and reused within a target system. Authors should demonstrate how their work is practical and soundness-aware with respect to at least one of these case studies.
Last updated by Dou Sun in 2016-07-09
Related Publications
Advertisment
Related Conferences
CCFCOREQUALISShortFull NameSubmissionNotificationConference
baa2ICSMEInternational Conference on Software Maintenance and Evolution2017-03-302017-06-122017-09-17
ESMSEInternational Conference Embedded System and Mobile Software Engineering2017-03-202017-04-052017-01-07
RAMInternational Conference on Robotics, Automation and Mechatronics2015-01-312015-03-312015-07-15
ICISAInternational Conference on Information Science and Applications2014-11-272014-12-182015-02-24
ICNISCInternational Conference on Network and Information Systems for Computers2017-04-05 2017-04-14
baa2ISSTAInternational Symposium on Software Testing and Analysis2017-02-032017-04-292017-07-09
IoT-SPIEEE International Conference on Internet of Things and Pervasive Systems2016-05-152016-06-152016-09-22
ICEUCInternational Conference on Embedded and Ubiquitous Computing2015-05-202015-05-302015-07-17
baa2ICPPInternational Conference on Parallel Processing2017-03-132017-05-082017-08-14
ICTIRACM SIGIR International Conference on the Theory of Information Retrieval2015-05-112015-07-132015-09-27
Recommendation