Software development is driven by the development team's decisions. Communicating the rationale behind these decisions is essential for the projects success. Although the software engineering community recognizes the need and importance of rationale, there has been a lack of in-depth study of rationale for code changes. To bridge this gap, this dissertation examines the rationale behind code changes in-depth and breadth. This work includes two studies and an experiment. The first study aims to understand software developers' need. It finds that software developers need to investigate code changes to understand their rationale when working on diverse tasks. The study also reveals that software developers decompose the rationale of code commits into 15 separate components that they could seek when searching for rationale. The second study surveys software developers' experiences with rationale. It uncovers issues and challenges that software developers encounter while searching for and recording rationale for code changes. The study highlights rationale components that are needed and hard to find. Additionally, it discusses factors leading software developers to give up their search for the rationale of code changes. Finally, the experiment predicts the documentation of rationale components in pull request templates. Multiple statistical models are built to predict if rationale components' headers will not be filled. The trained models are effective in achieving high accuracy and recall. Overall, this work's findings shed light on the need for rationale and offer deep insights for fulfilling this important information need. / Doctor of Philosophy / Software developers build software by creating and changing the software's code. In this process, developers make decisions and other developers need to understand these decisions. The rationale behind code changes is an important piece of information that leads to development success if well explained and understood. In this work, we study the developers' need for rationale by conducting two studies and an experiment. In the first study, we found that software developers often need to look into the rationale behind code changes to understand them better while working on different tasks. We identified 15 different parts of rationale that developers seek when searching for rationale for code changes. The second study focused on the experiences of software developers when looking for and recording rationale. We discovered some challenges that developers face, like difficulty in finding specific rationale parts and the factors that make developers give up searching for rationale. The experiment predicts if developers would document rationale in specific templates. We built models to predict if certain parts of rationale would be left empty, and the models were effective. Overall, this research provides a better understanding of software developers' need, and it provides valuable insights to help fulfill this important information need.

Maintenance has evolved over centuries and has played significant role for growth of organizations. Maintenance history is differentiated by three generations, the development of maintenance considered from being “necessary evil” to “profit contributor”. Many literatures have discussed maintenance for optimization and increasing profitability but little on the factors which influence on the future of maintenance. Maintenance should be considered as a “competitive factor” in the future. Many trends have evolved in production and every trend had a major contribution towards production development. The successful implementation of the trends is considered to be a major challenge. Little literatures have talked on the emerging trends and challenges in production. The thesis reviews the historical development of maintenance over generations and presents the key factors which play a major role during the fourth generation, and also identifies the emerging trends and challenges to be faced by production. The literature review, interviews and surveys were used in this thesis. Academic researchers and industrial experts from both maintenance and production department answered the interview and survey questions for this research. The key factors for the proposal of fourth generation of maintenance and the emerging trends and challenges to be faced by production are presented. The result from the research questions and the empirical findings are summarized in a framework that will enable readers to know the historical development of maintenance, the key factors to be considered for the fourth generation of maintenance and the emerging trends and challenges to be faced by production in future. In addition, the thesis also discusses the impact of information technology on the future of maintenance and the effect of sustainability in the future of production.