{"title":"Identifying and proactively managing architecture risk","authors":"William J. Koscho, W. Ries","doi":"10.1109/LMSA.2009.5074857","DOIUrl":"https://doi.org/10.1109/LMSA.2009.5074857","url":null,"abstract":"To help the architect deliver a feasible architecture within given time, cost, and quality constraints, architecture methods such as the ADD, ATAM, QAW, and others have been developed and adopted. The leadership ability of the architect greatly influences the outcome of the application of these methods. We discuss how that leadership ability can be strengthened by leveraging a broad range of risk management techniques, and show how to incorporate a risk-driven architecture management philosophy into mainstream architecture processes. Bringing skills in standardized architecture toolsets, patterns, and methods alone to the table is no longer a significant differentiator for architects. Augmenting these skills with a robust set of risk management practices allows the architect to develop into an organizational leader and add unique and repeatable value in risk- and control-conscious business environments.","PeriodicalId":446468,"journal":{"name":"2009 ICSE Workshop on Leadership and Management in Software Architecture","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2009-05-19","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"129691646","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":"Conflict management","authors":"K. Popovic, Ž. Hocenski","doi":"10.1109/LMSA.2009.5074859","DOIUrl":"https://doi.org/10.1109/LMSA.2009.5074859","url":null,"abstract":"Project managers must learn to recognize the signs and symptoms of disruptive conflict. Such signs would include poor communication among team members, a lack of openness, a lack of respect, unclear requirements, change between managers and employees, broken boundaries of social norms or groups, different backgrounds (educational, economic, cultural, political, etc.). The worst cases can disintegrate into personal stress, burnout, and workplace travesties. Once conflict has reached this stage, it will require a large amount of management time in order to deal with it. This will cause an additional decrease in productivity and efficiency rates, along with the accompanying added costs, risks, and duration delays. If left unmanaged, this type of conflict can even lead to employee sabotage and sometimes workplace violence. This position paper provides insight into qualities and social role that project manager as mediator and leader must possess because sometimes team members can't resolve conflicts collectively.","PeriodicalId":446468,"journal":{"name":"2009 ICSE Workshop on Leadership and Management in Software Architecture","volume":"59 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2009-05-19","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"114951723","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}
Wenting Ma, Lin Liu, Wenzhong Feng, Yuhui Shan, Fei Peng
{"title":"Analyzing project risks within a cultural and organizational setting","authors":"Wenting Ma, Lin Liu, Wenzhong Feng, Yuhui Shan, Fei Peng","doi":"10.1109/LMSA.2009.5074858","DOIUrl":"https://doi.org/10.1109/LMSA.2009.5074858","url":null,"abstract":"Risk management and assessment of software project is highly relevant to the social and culture context of the development activities. This paper proposes a risk analysis approach which represents the organizational settings of a project as a social dependency network, and identifies risks originated from broken role dependency relations, unsatisfied goals, unfinished tasks, and unavailable resources amongst the network. Survey results on Chinese culture implications to software projects are incorporated as an example scenario to illustrate how to evaluate the influences of culture related factors to software project risk management using the proposed approach.","PeriodicalId":446468,"journal":{"name":"2009 ICSE Workshop on Leadership and Management in Software Architecture","volume":"8 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2009-05-19","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"115544588","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":"Leveraging leadership lessons from software process improvement efforts for architecture leadership & management","authors":"S. Garcia","doi":"10.1109/LMSA.2009.5074860","DOIUrl":"https://doi.org/10.1109/LMSA.2009.5074860","url":null,"abstract":"There are many behavioral themes related to leadership and management for architecture practice. This paper deals primarily with leadership in terms of responsibilities for sponsoring improved architectural practice, leveraging from at least two decades of work that has been done in the more general software process improvement community. In addition to a discussion of relevant sponsorship practices and leverage points for leaders, the paper includes an annotated bibliography of selected resources that come from the reference section of the author's book, CMMI Survival Guide: Just Enough Process Improvement. The annotations help readers to understand how the leadership literature that is not specifically aimed at them can be of benefit to their efforts.","PeriodicalId":446468,"journal":{"name":"2009 ICSE Workshop on Leadership and Management in Software Architecture","volume":"20 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2009-05-19","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"133860395","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":"The impact of non-technical factors on Software Architecture","authors":"R. Ferrari, N. Madhavji, M. Wilding","doi":"10.1109/LMSA.2009.5074862","DOIUrl":"https://doi.org/10.1109/LMSA.2009.5074862","url":null,"abstract":"Most of the research and pedagogical literature in Software Architecture is on technical issues. Recently, however, there has been increasing interest on the importance of non-technical factors such as leadership, communication, inter-personal skills, work habits etc. in architecting. In this paper, we continue this line of research by conducting an empirical study examining the impact of non-technical factors in Software Architecture from the viewpoint of academia. We analysed non-technical problems encountered from 15 student architecting teams to determine the types of problems students have, and also their impact on the quality of the architecture. Furthermore, we analyzed the IEEE/ACM Software Engineering and Computer Science curriculums to determine any correspondence between these curriculums and the student's architecting performance. Based on this analysis, we make recommendations for the improved education of student software architects.","PeriodicalId":446468,"journal":{"name":"2009 ICSE Workshop on Leadership and Management in Software Architecture","volume":"103 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2009-05-19","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"122619995","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":"The software architect as the guardian of system performance and scalability","authors":"A. Bondi","doi":"10.1109/LMSA.2009.5074861","DOIUrl":"https://doi.org/10.1109/LMSA.2009.5074861","url":null,"abstract":"System performance and scalability issues often have their roots in architectural and design choices that are made early in the software life cycle. Because he must communicate with developers, designers, product managers, business stake holders, application domain experts, testers, and requirements engineers, the software architect is uniquely placed to play a leadership role in linking performance requirements to business and engineering needs. Ideally, the architectural, technology, and design choices that are made should take performance requirements and artifacts into account. This means that the architect should be equipped with at least a rudimentary understanding of performance engineering concepts. Ideally, an architect should be directly involved in performance concerns. Failing that, he should overtly give a mandate to and remain in close contact with a performance engineer to do this instead, because close architectural involvement with performance concerns is key to the success of the project.","PeriodicalId":446468,"journal":{"name":"2009 ICSE Workshop on Leadership and Management in Software Architecture","volume":"94 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2009-05-19","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"125212944","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":"Software architecture: Organizational perspectives","authors":"Paul L. Bannerman","doi":"10.1109/LMSA.2009.5074863","DOIUrl":"https://doi.org/10.1109/LMSA.2009.5074863","url":null,"abstract":"This position paper examines software architecture through the lenses of four organizational perspectives and identifies opportunities for research to improve the positioning and support of the discipline within organizations. It concludes that while software architecture may rest on solid technical foundations, its position in the organization is not as firm.","PeriodicalId":446468,"journal":{"name":"2009 ICSE Workshop on Leadership and Management in Software Architecture","volume":"29 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2009-05-19","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"117023157","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}