The current mobile paradigm is in many ways fundamentally different from the conventional desktop paradigm due to many factors such as multi-touch gesture interaction, usage of sensors, single-task focused model, etc. These factors mean several new challenges for the interaction designers with regard to communicating their ideas and thoughts during early design activities, which they might be unable to tackle properly using traditional prototyping techniques. Therefore, we envision that research must address the need for a change in existing prototyping techniques as well as focus on novel prototyping approaches and frameworks that would support not only the interaction design process but also the whole development process of mobile app development. In the footsteps of the first workshop, PID-MAD 2014 provides a platform to the interested communities for discussing issues and will bring together researchers and practitioners for sharing their knowledge and experience in order to tackle the upcoming challenges.

One of the challenges in maintaining legacy systems is to be able to locate business logic in the code, and isolate it for different purposes, including implementing requested changes, refactoring, eliminating duplication, unit testing, and extracting business logic into a rule engine. Our new idea is an iterative method to identify the business logic in the code and visualize this information to gain better understanding of the logic distribution in the code, as well as developing a domain-specific business vocabulary. This new method combines and extends several existing technologies, including search, aggregation, and visualization. We evaluated the visualization method on a large-scale application and found that it yields useful results, provided an appropriate vocabulary is available.

Evaluating interface usability and system functionality is time-consuming and effort-intense. The short time-span involved in development iterations, such as those in agile development, makes it challenging for software teams to perform ongoing interface usability evaluation and system functionality testing. We propose a way to perform product ongoing evaluation, thus enabling software teams to perform interface usability evaluation alongside automated system functionality testing. We use formal task models, created in our defined TaMoGolog task modeling language, to conduct product evaluation experiments through TaMUlator. TaMUlator is a tool we developed for use at the Integrated Development Environment (IDE) level. Our case study revealed that software teams can easily engage in system evaluation by using TaMUlator on an iterative basis.

A proliferation of travel-related web sites enable people to share their travel plans, review hotels, offer advice, and more. In this paper we study social travel planning in the enterprise. While business travelers and leisure travelers have different preferences and needs, employees may benefit from sharing information and travel plans within the enterprise. We present a study collecting the requirements for social travel from employees, detail the design principles of a social travel application in the enterprise, and present Voyage, the outcome. We evaluated Voyage based on qualitative and quantitative data and discuss the results using four perspectives: collaborative activities, social information impact, usage patterns, and sharing behavior. Employees expressed their growing satisfaction from the social information contributed by fellow employees. Moreover, we observed that Voyage shortens the reservation time, thus saving costs for the enterprise.

Special issue on global software engineeringOver the past 10 years, Global Software Engineering (GSE) and Development has traversed through several stages commonly experienced by new practices.Industry began the practice first as a way to manage development costs and then later with the hope that it could provide workforce flexibility and better allocation of expertise.Researchers began by categorizing different versions of the practice and exploring whether GSE could generally be successful or not.As the practice continued, successes and failures were studied to determine the conditions that led to each, and these results were melded with practical, Industry experience into guidelines for successful use.The utilization of GSE is now relatively mature, and the study of it has evolved into a more sophisticated and nuanced discipline.Although once, the big research question was: does GSE work?-the questions now are much more varied and utilize a much wider set of approaches and viewpoints.Moreover, current research sits atop and draws from a much larger history of established empirical findings.The seven papers in this Special Issue on GSE provide a good representation of the current state of GSE practice and research and demonstrate recent trends.Earlier and more abbreviated versions of these articles appeared in the 5th Annual International Conference on Global Software Engineering, held in Princeton, USA in August, 2010.As a discipline matures, it often finds important general principles by studying unique, specialpurpose instances; the unique instance can free the researcher for important insights that might seem too commonplace if discovered in the mainstream process.The paper by Smite and Wohlin entitled "Lessons Learned from Transferring Software Products to India" is a good example of this research methodology.The paper focuses on projects that begin in one country and then are moved to another, typically for reasons of cost and expertise-flexibility.However, from this specific practice comes a set of guidelines that apply to many aspects of GSE, for example, adjusting processes to people and transferring people to maintain work continuity.The paper by da Silva, Prikladnicki, França, Monteiro, Costa and Rocha entitled "An Evidencebased Model of Distributed Software Development Project Management: Results from a Systematic Mapping Study" demonstrates two recent methodological trends in GSE research.First, with a more substantial literature base from which to draw conclusions, GSE researchers can now analyze trends across whole groupings of studies.This paper provides a systematic and in-depth analytic review of 70 research papers in the field with an eye toward understanding the unique challenges faced by project managers in a distributed software development context as well as the tools and practices most often used to meet those challenges.A second current trend in GSE research has to do with the desire to generalize findings from individual studies into a broader conceptual model, and this paper attempts to model global project management by casting challenges, tools, and practices into a cause and effect relationships.These authors' model proposes how the effectiveness of project management practices might be influenced by geographic, temporal, social, and personal distances through mediators, such as trust, cooperation, and information sharing.The methodological trend of systematic review is again demonstrated in the paper by Jalali and Wohlin entitled "Global Software Engineering and Agile Practices: A Systematic Review".In this case, the topical focus is the employment of Agile methods in a globally distributed context.It is worth noting that this combination at one point seemed nearly impossible because of Agile method's emphasis on frequent face-to-face communication.But like most engineering methods, Agile represents a broad suite of practices, and this paper shows that some can be effective in a distributed environment, whereas others are often not.One advantage of the systematic review methodology is that it can analyze what kinds of studies contribute to conclusions.In this case, the

Governance has emerged in the last few years as critical to the success of software development, a result of an increased focus on team work. Governance of software teams includes practices of defining and executing decision rights and mechanisms to empower the development process to be governed. We report on an empirical survey of team members of global development projects in six companies. Using factor analysis, we classify four governance mechanisms as follows: governance definition, governance enactment, business awareness, and goal achievement. The results reveal among others that high levels of governance definition and goal achievement in a team are related to a lower level of team conflict. These significant relationships as well as the lack of significant relationships between the other governance mechanisms and team conflict, offers important insight into enhancing the effectiveness of global teams through governance.

This is the introduction of the 3rd workshop on Software Development Governance (SDG), which will take place as part of ICSE 2010. This year we have combined two successful workshops (SDG - software development governance and LMSA -- leadership and management in software architecture) since both workshops deal with decisions that are part of the development process e.g., business and organizational decisions that impact the technical decisions concerned with the product architecture and the product quality.

In this paper, we present a HOT --- Human, Organizational and Technological --- framework for software engineering and describe its application in a full one-semester software engineering course on agile software development. We suggest and illustrate how this framework has the potential to widen and deepen the students' understanding of software engineering processes.

Our tutorial for ICSE 2010 focuses on coaching agile software teams.

One of the challenges in software development is to collect and analyze the end users' feedback in an effective and efficient manner. In this paper we present a tool to manage user evaluation alongside the process of software development. The tool is based on the idea that user evaluation should be managed iteratively from within the integrated development environment (IDE) in order to provide high quality user interface. The main capabilities include creating the experiment object as part of the software project; deriving development tasks from the analysis of evaluation data; and tracing these tasks to and from the code. Further, we provide a library to enable development of Java aspects for creation of automatic measures to increase the body of the evaluation data. Using this tool, development teams can manage user-centered design (UCD) activities at the IDE level, hence developing software products with an adequate level of usability.

In this paper we suggest a framework for teaching software development methods (SDMs). Specifically, based on our accumulative research and in-practice experience of teaching SDMs, a set of principles, that guides our teaching of SDMs in different settings and teaching experiences, has been formulated. The teaching framework consists of 14 principles that their actual implementation is varied and adjusted in different teaching environments. This paper outlines the principles and addresses their contribution to learners' understanding of the said software development method.

This paper discusses the suitability of the qualitative research approach to computer science education research. It is based on the following two observations: First, only a small proportion of works presented in the computer science education literature contain some experimental component (Fincher and Petre, 2004; Valentine, 2004). Second, those research works conducted in computer science education that do, usually employ a quantitative research approach. This paper focuses on the qualitative research approach, presenting its nature, discussing its relationships to the quantitative research approach and addressing its application in general and in the context of computer science education in particular.

A project-based capstone course aims at using software development skills while performing a project in the course domain. One of our main challenges is to simulate a real world environment so to provide our students with the experience they need. Planning this experience we should consider academic constraints as well as the students' schedule and skills. In this paper we describe how we implement an agile software development method in a project-based capstone course in the domain of operating systems. We elaborate on how we simulate a real world environment and present a role scheme that is used by the students to manage the process. We suggest a discussion on how to use the role scheme as an assessment tool to measure the development process in general and students' contribution in particular. We expect to extend and refine the comprehension regarding process measurement in students' teams at the academia.

No abstract available.

This article focuses on the teaching of software development methodologies. It presents ten principles of teaching such a topic, while examining each from both a pedagogical and an organizational viewpoint. The teaching principles are demonstrated using the methodology of extreme programming (XP).

The paper introduces a protocol for rerouting calls in an ATM network, referred to as the flexible trerouting protocol (FRP). Failure of a VP triggers construction of an alternate VP out of VPs that are not in use, named stand-by VPs, by simple operations at the endpoints of the stand-by VPs. VC rerouting from the failed VP to the alternate VP is performed concurrently. FRP is designed to also allow recovery from repeated failures that may occur during the construction and rerouting process.