| |||||||||||||
CAiSE 2011 : 23rd International Conference on Advanced Information Systems EngineeringConference Series : Conference on Advanced Information Systems Engineering | |||||||||||||
Link: http://www.caise2011.com | |||||||||||||
| |||||||||||||
Call For Papers | |||||||||||||
CAISE 2011 Call for papers
23rd International Conference on Advanced Information Systems Engineering (CAiSE 2011) London, June 2011, 20th-24th Details can be found at: http://www.caise2011.com Important Dates * Tutorials & workshops submission deadline: 20th October 2010 * Paper submission deadline: 30th November 2010 * Notification of acceptance: 18th February 2011 * Workshops & Conference: 20th - 24th June 2011 ******************************************************************************* Conference Theme - IS Olympics: Information Systems in a diverse world We link this year's CAiSE conference theme with the coming Olympic and Paralympic Games, two international multi-sport events, which bring together athletes from all the continents to celebrate sporting excellence but also human diversity. Diversity is an important concept for modern information systems. Information Systems (IS) are diverse by nature ranging from basic systems to complex and from small to large. The process of constructing such systems is also diverse ranging from ad-hoc methods, to structured and formal methods. Diversity is also present amongst information systems developers, from novice to experienced. Moreover, the wide acceptance of information systems and their usage in almost every aspect of the human life has also introduced diversity amongst users. Users range from novice to experience and they demonstrate differences related to race, ethnicity, gender, socio-economic status, age, physical abilities, religious beliefs, and so on. It is therefore the responsibility of the Information Systems Engineering community to engineer information systems that operate in such diverse world. On the other hand, looking at the issues of the modern Olympic Games, we can identify a number of issues that rapidly make their appearance in the area of Information Systems. The kind of systems that are implemented and used in Olympic Games are varied and many. Every type of system that a well established multinational organisation uses is also established by the Local Organising Committee (OCOG), for example, ERP, private telecoms, HR recruitment, CAD/CAM etc. Many types of system that local governments use, such a town planning, transportation, refuge collection, medical services, also play a significant role. Many types of system that national governments use are also present such as accreditation, physical security systems. Moreover, the Olympic Games have a fixed starting date; everything needs to work perfectly from the first day; there is a large number of distributed (geographically) systems that need to be supported; requirements come from different sources (IOC, sport event specific, central administration, laws, sponsors etc). Similarly, an increasing number of information systems need to start operation on a specific day (restricted by laws and international agreements); important information is stored so full operation is required from day one; the need for international collaboration systems means that systems are becoming larger and highly distributed; various stakeholders are involved introducing different and sometimes conflicting requirements. All these issues introduce a number of challenges for the Information Systems Engineering community related to engineering, quality and interconnectivity of information systems. CAiSE'11 invites papers that address all these challenges. We also specifically encourage submissions that address diversity issues, either in terms of the information systems, the development team or the information systems users. The topics of interests include, but are not restricted to: Methodologies and Approaches for IS Engineering: * Enterprise architecture and enterprise modelling; * Knowledge patterns and ontologies for IS engineering; * Requirements engineering; * Methodologies and Languages for Secure IS * Business process modelling and management; * IS engineering approaches for adaptive and flexible information systems; * Simulation; * IS in networked & virtual organizations; * Model, component, and software reuse; * Method engineering; * IS reengineering; * Quality of models and of modelling languages; * Adaptive IS engineering approaches; * Usability, trust, flexibility, interoperability; * Knowledge, information, and data quality Innovative platforms, architectures and technologies for IS engineering: * Service-oriented architectures; * Innovative database technology; * Model-driven architectures; * Semantic web; * Component based development; * IS and ubiquitous technologies; * Software Agents architectures; * Adaptive and context-aware IS; * Distributed, mobile, and open architectures; Engineering of specific kinds of IS: * eGovernment; * Enterprise systems (ERP, CRM); * Data warehousing; * Workflow systems; * Knowledge management systems; * Content management systems; Emerging Areas of IS: * IS & Digital Ecologies * IS & Smart Buildings; * IS & Digital Devices * IS & their Economies ******************************************************************************* Author Guidelines We invite four types of original and scientific papers: * Formal and/or technical papers describe original solutions (theoretical, methodological or conceptual) in the field of IS engineering. A technical paper should clearly describe the situation or problem tackled, the relevant state of the art, the position or solution suggested and the potential - or, even better, the evaluated - benefits of the contribution. * Empirical evaluation papers evaluate existing problem situations or validate proposed solutions with scientific means, i.e. by empirical studies, experiments, case studies, simulations, formal analyses, mathematical proofs, etc. Scientific reflection on problems and practices in industry also falls into this category. The topic of the evaluation presented in the paper as well as its causal or logical properties must be clearly stated. The research method must be sound and appropriate. * Experience papers present problems or challenges encountered in practice, relate success and failure stories, or report on industrial practice. The focus is on 'what' and on lessons learned, not on an in-depth analysis of 'why'. The practice must be clearly described and its context must be given. Readers should be able to draw conclusions for their own practice. * Exploratory Papers can describe completely new research positions or approaches, in order to face to a generic situation arising because of new ICT tools or new kinds of activities or new IS challenges. They must describe precisely the situation and demonstrate how current methods, tools, ways of reasoning, or meta-models are inadequate. They must rigorously present their approach and demonstrate its pertinence and correctness to addressing the identified situation. ******************************************************************************* Submission and Publication Papers should be submitted in PDF format. The results described must be unpublished and must not be under review elsewhere. Submissions must conform to Springer's LNCS format and should not exceed 15 pages, including all text, figures, references and appendices. Submissions not conforming to the LNCS format, exceeding 15 pages, or being obviously out of the scope of the conference, will be rejected without review. Information about the Springer LNCS format can be found at http://www.springer.de/comp/lncs/authors.html.Three to five keywords characterising the paper should be indicated at the end of the abstract. Accepted papers will be presented at CAiSE'11 and published in the conference proceedings, which are published in the Springer Lecture Notes in Computer Science (LNCS). A small selection of best papers will be recommended for inclusion in a special issue of Information Systems (latest impact factor: 1.966) dedicated to this conference. At least one of the authors of an accepted paper must register for the conference and attend the conference to present the paper. |
|