The International Conference on Software Engineering Advances (ICSEA 2013) continues a series of events covering a broad spectrum of software-related topics. The conference covers fundamentals on designing, implementing, testing, validating and maintaining various kinds of software. Several tracks are proposed to treat the topics from theory to practice, in terms of methodologies, design, implementation, testing, use cases, tools, and lessons learned. The conference topics cover classical and advanced methodologies, open source, agile software, as well as software deployment and software economics and education.
Other advanced aspects are related to on-time practical aspects, such as run-time vulnerability checking, rejuvenation process, updates partial or temporary feature deprecation, software deployment and configuration, and on-line software updates. These aspects trigger implications related to patenting, licensing, engineering education, new ways for software adoption and improvement, and ultimately, to software knowledge management.
There are many advanced applications requiring robust, safe, and secure software: disaster recovery applications, vehicular systems, biomedical-related software, biometrics related software, mission critical software, E-health related software, crisis-situation software. These applications require appropriate software engineering techniques, metrics and formalisms, such as, software reuse, appropriate software quality metrics, composition and integration, consistency checking, model checking, provers and reasoning.
The nature of research in software varies slightly with the specific discipline researchers work in, yet there is much common ground and room for a sharing of best practice, frameworks, tools, languages and methodologies. Despite the number of experts we have available, little work is done at the meta level, that is examining how we go about our research, and how this process can be improved. There are questions related to the choice of programming language, IDEs and documentation styles and standard. Reuse can be of great benefit to research projects, yet reuse of prior research projects introduces special problems that need to be mitigated. The research environment is a mix of creativity and systematic approach which leads to a creative tension that needs to be managed or at least monitored. Much of the coding in any university is undertaken by research students or young researchers. Issues of skills training, development and quality control can have significant effects on an entire department. In an industrial research setting the environment is not quite that of industry as a whole, nor does it follow the pattern set by the university. The unique approaches and issues of industrial research may hold lessons for researchers in other domains.
We solicit both academic, research, and industrial contributions. We welcome technical papers presenting research and practical results, position papers addressing the pros and cons of specific proposals, such as those being discussed in the standard fora or in industry consortia, survey papers addressing the key problems and solutions on any of the above topics short papers on work in progress, and panel proposals.
Industrial presentations are not subject to the format and content constraints of regular submissions. We expect short and long presentations that express industrial position and status.
Tutorials on specific related topics and panels on challenging areas are encouraged.
The topics suggested by the conference can be discussed in term of concepts, state of the art, research, standards, implementations, running experiments, applications, and industrial case studies. Authors are invited to submit complete unpublished papers, which are not under review in any other conference or journal in the following, but not limited to, topic areas.
All topics and submission formats are open to both research and industry contributions.
Track 1: Advances in fundamentals for software development
Fundamentals in software development
Track 2: Advanced mechanisms for software development
Track 3: Advanced design tools for developing software
Formal specifications in software
Track 4: Advanced facilities for designing/accessing software
Track 5: Software performance
Software performance modeling
Track 6: Software security, privacy, safeness
Security requirements, design, and engineering
Track 7: Advances in software testing
Formal approaches for test specifications
Track 8: Specialized software advanced applications
Database related software
Track 9: Web Accessibility
Track 10: Open source software
Open source software (OSS) methodologies
Track 11: Agile software techniques
Agile software methodologies and practices (extreme programming, scrum, feature-driven, etc.)
Track 11: Software deployment and maintenance
Software in small and large organizations
Track 13: Software engineering techniques, metrics, and formalisms
Track 14: Business technology
Enterprise Content Managements (ECMs); Business Intelligence (BI); Enterprise Portals; Business Process Management (BPM); Corporate Performance Management (CPM); Enterprise Data Warehouse; Web Publishing; Cloud Computing; Virtualisation; Data Mining; Workflows; Business Rules Management (BRM); Data Capturing
Track 15: Software economics, adoption, and education
Track 16: Improving productivity in research on software engineering
Developing frameworks to support research
INSTRUCTION FOR THE AUTHORS
Authors of selected papers will be invited to submit extended versions to one of the IARIA Journals.
Only .pdf or .doc files will be accepted for paper submission. All received submissions will be acknowledged via an automated system.
Regular Papers (up to 6-10 page article)
Final author manuscripts will be 8.5" x 11", not exceeding 6 pages; max 4 extra pages allowed at additional cost. The formatting instructions can be found on the Instructions page. Helpful information for paper formatting can be found on the here.
Your paper should also comply with the additional editorial rules.
Once you receive the notification of paper acceptance, you will be provided by the publisher an online author kit with all the steps an author needs to follow to submit the final version. The author kits URL will be included in the letter of acceptance.
We would recommend that you not use too many extra pages, even if you can afford the extra fees. No more than 2 papers per event are recommended, as each paper must be separately registered and paid for. At least one author of each accepted paper must register to ensure that the paper will be included in the conference proceedings.
Work in Progress (short paper up to 4 pages long)
Work-in-progress contributions are welcome. Please submit the contributions following the instructions for the regular submissions using the "Submit a Paper" button and selecting the contribution type as work in progress. Authors should submit a four-page (maximum) text manuscript in IEEE double-column format including the authors' names, affiliations, email contacts. Contributors must follow the conference deadlines, describing early research and novel skeleton ideas in the areas of the conference topics. The work will be published in the conference proceedings.
For more details, see the Work in Progress explanation page
Posters (poster or collection of 6 to 8 slides)
Posters are intended for ongoing research projects, concrete realizations, or industrial applications/projects presentations. Acceptance will be decided based on a 1-2 page abstract and/or 6-8 .pdf slide deck submitted through the conference submission website. The poster may be presented during sessions reserved for posters, or mixed with presentation of articles of similar topic. The slides must have comprehensive comments. One big Poster and/or the associated slides should be used for discussions, once on the conference site.
For more details, see the Posters explanation page.
Ideas (2 page proposal of novel idea)
This category is dedicated to new ideas in their early stage. Contributions might refer to PhD dissertation, testing new approaches, provocative and innovative ideas, out-of-the-box, and out-of-the-book thinking, etc. Acceptance will be decided based on a maximum 2 page submission through the conference submission website. The contributions for Ideas will be presented in special sessions, where more debate is intended. The Idea contribution must be comprehensive, focused, very well supported (details might miss, obviously). A 6-8 slide deck should be used for discussions, once on the conference site.
For more details, see the Ideas explanation page.
Technical marketing/industrial/business/positioning presentations
The conference initiates a series of business, technical marketing, and positioning presentations on the same topics. Speakers must submit a 10-12 slide deck presentations with substantial notes accompanying the slides, in the .ppt format (.pdf-ed). The slide deck will not be published in the conference’s CD Proceedings. Presentations' slide decks will be posted on the IARIA's site. Please send your presentations to email@example.com.
Tutorials provide overviews of current high interest topics. Proposals should be for three hour tutorials. Proposals must contain the title, the summary of the content, and the biography of the presenter(s). The tutorials' slide decks will be posted on the IARIA's site. Please send your proposals to firstname.lastname@example.org
The organizers encourage scientists and industry leaders to organize dedicated panels dealing with controversial and challenging topics and paradigms. Panel moderators are asked to identify their guests and manage that their appropriate talk supports timely reach our deadlines. Moderators must specifically submit an official proposal, indicating their background, panelist names, their affiliation, the topic of the panel, as well as short biographies. The panel's slide deck will be posted on the IARIA's site.
For more information, email@example.com
We welcome workshop proposals on issues complementary to the topics of this conference. Your requests should be forwarded to firstname.lastname@example.org.
Copyright (c) 2006-2013, IARIA