Most presentations were postered.
Software development takes place in a dynamic context of frequently changing technologies, and limited
resources. Development teams world-wide are under ever-increasing pressure to deliver trustworthy software
products more quickly and with higher levels of quality. At the same time, global competition is forcing software
development organizations to cut costs by rationalizing processes, outsourcing part or all of their activities,
reusing existing software in new or modified applications and evolving existing systems to meet new needs,
whilst still minimizing the risk of projects failing to deliver. To address these difficulties, new or modified
processes are emerging including lean and agile methods, plan-based product line development, and increased
integration with systems engineering processes. For ICSP 2009, articles addressing process support to develop
trustworthy software are of particular interest.
ICSP 2009 invites papers describing completed research or advanced work-in-progress in all areas of software
and systems development process including: agile software processes, CMMI, novel techniques for software
process representation and analysis; process tools and metrics; and the simulation and modeling of software
and systems processes. As in previous years, ICSP 2009 will organize a special track for papers on software
and systems process simulation. Contributions reflecting industrial experience are particularly welcome.
ICSP 2009 continues a long tradition of software process research positioning itself as the new leading edge
event for systems and software process research. ICSP 2009 will be co-located with ICSE 2009 in Vancouver,
The increasing challenges faced by the software industry combine to increase demands on software processes.
As a result, a number of practical questions arise, such as:
What are success factors for trustworthy software development?
What is the interface between software process and business process?
What are the implications of adopting systems engineering processes and integrating them with software processes?
What is the right degree of process agility in different contexts for the development of trustworthy?
What defines a process-based competitive advantage?
How do changes in process need to be reflected and supported in the organization?
What is the return on investment for CMMI, Six-Sigma, Spice, ISO and other SPI paradigms and industry standards?
How can we predict the effects of process improvement initiatives?
Meanwhile, to address these practical questions, a corresponding set of research questions arise, such as:
Which aspects of trustworthiness (e.g., security, and quality) are more important in the software industry?
How can more precise micro-process capabilities be better integrated with more strategic macro-process capabilities?
How can process representation and analysis capabilities better support expression and reasoning about unavoidably
incomplete, inconsistent, ambiguous, or emergent process definitions?
How can software processes and associated methods, tools, and metrics better scale up to complex software-intensive
systems of systems, and scale down to support small-to-medium sized enterprises?
How can software processes be better supported by and linked to underlying theories of successful SW development?
How can various forms of simulation and modeling methods and tools be better integrated with each other and with other
process representations and reasoning tools?
How can useful process assets (including process models and process simulations) be safely composed and organized
into useful asset libraries?