The design of software systems is one of the most complex activities in engineering. And since software systems are expected to fulfil an increasing amount of tasks in more sophisticated environments, software designers are faced with handling daunting amounts of complex information during development. Ideally, all the information that is required during any one stage of software development is available without containing any vagueness, ambiguity or conflicting specifications. In practice, the available information generally does not fulfil this ideal. Requirement specifications typically originate from various sources and occur in a myriad of shapes and forms, such as business plans, user manuals and market studies, which do not necessarily form a coherent specification of the software system. The available information therefore at best forms an imperfect specification of requirements for the software architecture.
This workshop aims to bring together researchers in the field of dealing with imperfect information during software architecture design. We sollicit the submission of novel research on how information sources of architecture design can contain imperfect information, how they can be identified and how it can be modelled and analysed. This includes the definition of a catalogue of types of imperfect information and models for describing imperfect information accurately using concepts from, for example, probability and fuzzy set theory. We also invite submissions of experience reports from industry on the causes, consequences and ways of dealing with imperfect information during software architecture design.
|Submissions:||May 17, 2010|
|Notification:||June 7, 2010|
|Event:||August 23, 2010-March 23, 2010|