{"title":"A plea for lean software process models","authors":"Philippe B Kruchten","doi":"10.1145/1987875.1987919","DOIUrl":"https://doi.org/10.1145/1987875.1987919","url":null,"abstract":"Over the last 30 years we have tried very hard the rich process models approach, and we have not been extremely successful at it. Maybe we should try \"lean and mean\" software process models, rather than making them \"richer.\" At minimum, we should try to analyze why the rich approaches have not worked; where they failed. Could it be that we were trying to solve the wrong problem? or that the real problems by far overshadow the process model issue? Or maybe the whole construction paradigm we use for software development is not suitable anymore? My position is that we should try the route of very simple software process models, to ensure a wider applicability, greater versatility, and acceptance. Possibly these new process models would be based on other paradigms of software or system development than the \"technical-rational\" construction idea. I would be wary of richer process models.","PeriodicalId":296714,"journal":{"name":"International Conference on Software and Systems Process","volume":"3 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2011-05-21","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"116928951","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
I. Espinosa-Curiel, Josefina Rodríguez-Jacobo, José Alberto Fernández-Zepeda
{"title":"A competency framework for the stakeholders of a software process improvement initiative","authors":"I. Espinosa-Curiel, Josefina Rodríguez-Jacobo, José Alberto Fernández-Zepeda","doi":"10.1145/1987875.1987898","DOIUrl":"https://doi.org/10.1145/1987875.1987898","url":null,"abstract":"The competencies (a set of specific knowledges, skills, attitudes and behaviors; e.g. stress handling, commitment, collaboration and identification of conflicts) of the employees of software organizations are a fundamental element for the success of a Software Process Improvement (SPI) initiative. We performed three case studies to identify the competencies required for the stakeholders in an SPI initiative. To identify these competencies, we observed the activities that each stakeholder performs and the interactions among them. We also identified the competencies that are required to perform those activities. We performed a classification of the identified competencies and integrated them into a framework. This framework defines the competencies for seven roles involved in an SPI initiative and defines the level of expertise required by each role for each competency. To evaluate the framework, we performed ten interviews and two empirical tests. Preliminary results show that this framework is relevant in SPI initiatives, the use of this framework can raise the awareness about the competencies, and it can support some SPI activities.","PeriodicalId":296714,"journal":{"name":"International Conference on Software and Systems Process","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2011-05-21","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"123021295","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"Defense acquisition system simulation studies","authors":"J. R. Wirthlin, Dan X. Houston, R. Madachy","doi":"10.1145/1987875.1987906","DOIUrl":"https://doi.org/10.1145/1987875.1987906","url":null,"abstract":"A systems engineering process model for the acquisition of large, complex systems for the U.S. Department of Defense (DoD) is being adapted for ongoing experiments in acquisition process policies. The discrete-event simulation model of the larger \"enterprise of acquisition\" for weapon systems has a broad scope from program beginning through development. It reveals some of the challenges and risks in weapon system acquisition.\u0000 Initially the model was used to evaluate potential policies as interventions and/or system changes in an Air Force context. The simulation results showed varying degrees of influence on program outcomes and suggested no single antidote exists for solving acquisition problems. Many of the negative outcomes reflected through cost and schedule overruns are due to the behavior of the acquisition system itself.\u0000 A collaboration between the Air Force Institute of Technology (AFIT), the Naval Postgraduate School (NPS), and The Aerospace Corporation is underway to translate the model and adapt it for new considerations. Shortly we will propagate new model versions and results to the public, and use it for additional Air Force and Navy programs of concern.","PeriodicalId":296714,"journal":{"name":"International Conference on Software and Systems Process","volume":"77 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2011-05-21","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"126917220","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"Special panel: towards a manifesto for rich process models","authors":"A. Rausch, M. Kuhrmann","doi":"10.1145/1987875.1987916","DOIUrl":"https://doi.org/10.1145/1987875.1987916","url":null,"abstract":"In the agile community, there is a strong commitment to the few and simple principles and values that are collected in the agile manifesto. Those are a common guideline and a value system for agile methods. Rich process models suffer in having such principles and values. In this special panel, we aim at initiating a discussion on commonly agreed principles and values in rich process models, and at starting the work on a \"Manifesto for Rich Process Models\".","PeriodicalId":296714,"journal":{"name":"International Conference on Software and Systems Process","volume":"24 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2011-05-21","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"114725698","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"Formally founded, plan-based enactment of software development processes","authors":"Jan Friedrich, K. Bergner","doi":"10.1145/1987875.1987908","DOIUrl":"https://doi.org/10.1145/1987875.1987908","url":null,"abstract":"The management of a software development project is a demanding task. To plan and control the actions of the project participants, the existence of a suitable project plan is of critical importance. However, elaborating and maintaining such a project plan based on the employed process model typically requires a lot of manual effort, comprising many tedious and error-prone activities. This paper shows how plan-based enactment of processes can improve this situation, providing a basis for adequate method and tool support. The paper presents our approach for an integrated formal model covering process models, project plans and real life project actions. The model is simple, has a well-defined semantics and supports initial planning as well as plan refinement, re-planning and controlling. Furthermore, the paper sketches how the model can be put to practice and integrated into existing tools.","PeriodicalId":296714,"journal":{"name":"International Conference on Software and Systems Process","volume":"6 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2011-05-21","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"130748188","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Frank Elberzhager, Jürgen Münch, H. D. Rombach, B. Freimut
{"title":"Optimizing cost and quality by integrating inspection and test processes","authors":"Frank Elberzhager, Jürgen Münch, H. D. Rombach, B. Freimut","doi":"10.1145/1987875.1987880","DOIUrl":"https://doi.org/10.1145/1987875.1987880","url":null,"abstract":"Inspections and testing are two of the most commonly performed software quality assurance processes today. Typically, these processes are applied in isolation, which, however, fails to exploit the benefits of systematically combining and integrating them. Expected benefits of such process integration are higher defect detection rates or reduced quality assurance effort. Moreover, when conducting testing without any prior information regarding the system's quality, it is often unclear which parts or which defect types should be prioritized. Existing approaches do not explicitly use information from inspections in a systematical way to focus testing processes. In this article, we present an integrated two-stage approach that routes inspection data to test processes in order to prioritize code classes and defect types. While an initial version of the approach focused on prioritizing code classes, this article focuses on the prioritization of defect types for testing. Results from a case study where the approach was applied on the code level show that those defect types could be prioritized before the testing that afterwards actually showed up most often during the test process. In addition, an overview of related work and an outlook on future research directions are given.","PeriodicalId":296714,"journal":{"name":"International Conference on Software and Systems Process","volume":"32 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2011-05-21","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"129710350","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"Automatic mining of change set size information from repository for precise productivity estimation","authors":"Hui Huang, Qiusong Yang, Junchao Xiao, Jian Zhai","doi":"10.1145/1987875.1987889","DOIUrl":"https://doi.org/10.1145/1987875.1987889","url":null,"abstract":"Productivity is a crucial concern for most software organizations. It can help project managers to make project plan, supervise project progress, and measure the project members' performance. Thus it has been widely measured and analyzed by both industry and researchers. But in the actual software project management, the project data filled by the developers may be incomplete and imprecise. Especially it is very hard for the developers to give the precise work product scale of each task. Therefore, the productivity calculated basing on those data is also imprecise. To solve the problem, this paper presents a method for precise productivity estimation. The method calculates work product scale of each task using change set size information by rebuilding relationships between the tasks and the SVN commits, and then calculates the productivity. And an experimental study has been done basing on Qone. Qone is an integrated system for project management developed by Institute of Software Chinese Academy of Sciences (ISCAS). It has been used in more than 200 software companies in China.","PeriodicalId":296714,"journal":{"name":"International Conference on Software and Systems Process","volume":"4 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2011-05-21","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"125196586","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"Towards richer process principles","authors":"B. Boehm","doi":"10.1145/1987875.1987918","DOIUrl":"https://doi.org/10.1145/1987875.1987918","url":null,"abstract":"Today's and tomorrow's complex, interdependent, dynamic systems require richer process principles than the simplistic principles in the Agile Manifesto or in simplistic sequential waterfall or Vee models. The resulting principles should capitalize on the strengths of these while avoiding their weaknesses.","PeriodicalId":296714,"journal":{"name":"International Conference on Software and Systems Process","volume":"6 3 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2011-05-21","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"126122549","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"Concepts in the definition of an enterprise development process","authors":"S. Sutton","doi":"10.1145/1987875.1987914","DOIUrl":"https://doi.org/10.1145/1987875.1987914","url":null,"abstract":"Integrated Product Development - IPD - is an enterprise-wide process used by IBM to develop technology products including hardware, software, and services. IPD has been in use at IBM for over a decade and has been very effective at increasing efficiency and reducing costs across the whole product life cycle. Within IBM Software Group, IPD at the top level is defined informally through natural-language documents, ad hoc diagrams, and a database of well-defined deliverables. Some key concepts in the SWG IPD definition include a clear statement of the principles on which the process is based, widespread references to business goals, frequent use of governance-oriented formulations, a clearly defined structure for the high levels of the process, a relative lack of concern about lower levels of the process structure, and an emphasis on the characterization of participant roles. The relative lack of formal and semantic rigor in the SWG IPD definition might seem to open the door to a number of problems in process specification and execution. However, this seems to have allowed the process definers to focus on those aspects of the process that are most important and to present those in a natural way. In the context of an organization that is dedicated to the success of the process, this has been an effective approach.","PeriodicalId":296714,"journal":{"name":"International Conference on Software and Systems Process","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2011-05-21","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"129707525","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"Analyzing software process models with AVISPA","authors":"J. Alegría, M. Bastarrica, Alexandre Bergel","doi":"10.1145/1987875.1987882","DOIUrl":"https://doi.org/10.1145/1987875.1987882","url":null,"abstract":"Software process models are sophisticated and large specifications aimed at organizing and managing software development. Their formal specification demands an enormous effort, but once specified there are few approaches and even fewer tools that aid the process engineer to analyze the quality of the process. For the last five years we have aided software companies in specifying their software processes and we have found a series of error patterns that indicate the potential presence of misconceptions or misspecifications. This paper presents these patterns, characterizes the kinds of errors they potentially reveal, and details how errors could be localized within a software process model. To assist process engineers to analyze the quality of their processes, we provide Avispa, a tool that graphically renders different aspects of a process model and highlights potential errors as intuitive and comprehensible indicators. The approach and the supporting tool are illustrated by applying them for analyzing the software process models of three Chilean software companies.","PeriodicalId":296714,"journal":{"name":"International Conference on Software and Systems Process","volume":"39 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2011-05-21","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"126574203","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}