An empirical analysis of risk components and performance on software projects

Han, Wen-Ming; Huang, Sun-Jen

doi:10.1016/j.jss.2006.04.030

Cited by 168 publications

(116 citation statements)

References 19 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Usability is increasingly recognized as an important consideration during software development; however, many wellknown software products suffer from usability issues that cannot be repaired without major changes to the software architecture of these products. Studies (Hana and Huang, 2007) confirm that a significant large part of the maintenance costs of software systems is spent on dealing with usability issues. Generally, a motivational reason can be a requirement, a goal, an It is important to represent motivational reasons explicitly as inputs to the decisions so that they are given proper attention in the decision making process.…”

Section: Design Decision and Knowledge-rules Specificationmentioning

confidence: 97%

Decision Based Development of Productline: A Quintessence Usability Approach

Balan¹,

Punithavalli²

2011

Journal of Computer Science

View full text Add to dashboard Cite

Problem statement:A well designed user interface is comprehensible and controllable, helping users to complete their work successfully and efficiently and to feel competent and satisfied. To improve the usability of a software system, usability patterns can be applied. However, there are short comes shows that the software architecture of a system restricts certain usability patterns from being modified after implementation. Several of these usability patterns are "architecture sensitive", such modifications are costly to implement due through their structural impact on the system. So we practice the pattern oriented usability design with considering the dependencies between the design decisions relevant to the product line business objects which has its impact on the usability criterion. Dependencies between the rationale decisions for the architecture sensitive usability patterns can be maintained for future reference. Approach: While going for the usability patterns, the decisions behind the pattern selection should be specified. We address the issues by analyzing the quality based models that determines the design rationale and their dependencies. We use QDK methodology to preserve the specifications of decisions and all their inter dependencies along with the knowledge rule. Results: Preserving the specifications of decisions and all their inter dependencies with knowledge rules will support the evolution and maintenance of such productline systems. Explicit evaluation of usability during architectural design prevents part of the high costs incurred by adaptive maintenance activities once the system has been implemented. Conclusion: Capturing knowledge by this means provides the basis for justification, learning and re-uses of the knowledge rules for further design decisions.

show abstract

Section: Design Decision and Knowledge-rules Specificationmentioning

confidence: 97%

Decision Based Development of Productline: A Quintessence Usability Approach

Balan¹,

Punithavalli²

2011

Journal of Computer Science

View full text Add to dashboard Cite

show abstract

“…These factors are commonly cited in 'top ten' checklists of risk/success/failure factors that must be managed to ensure the project succeeds. Example lists are provided by Alter and Ginzberg (1978), Keil et al (1998), Boehm (1991), Heemstra and Kusters (1996), Sumner (2000), Houston et al (2001), Johnson et al (2001), Schmidt et al (2001), Addison and Vallabh (2002), and Han and Huang (2007). Risk factors include, for example, clear objectives, firm requirements, user involvement, senior management commitment, and skilled resources.…”

Section: Risk Management As Factor Analysis (Contingency School)mentioning

confidence: 99%

“…Risk identification, therefore, seeks to uncover the critical categories of threats that might affect the project. Examples of source categories are provided by Boehm and Ross (1989), Barki et al (1993), Carr et al (1993), Chittister and Haimes (1993), Heemstra and Kusters (1996), Keil et al (1998), Cule et al (2000), Ropponen and Lyytinen (2000), Jiang et al (2002), Tiwana and Keil (2004), Wallace and Keil (2004), Wallace et al (2004b), and Han and Huang (2007). Examples of source categories include requirements, technology, client, people, organization, and environment.…”

Section: Risk Management As Factor Analysis (Contingency School)mentioning

confidence: 99%

“…Assessing the project against the scale of each dimension-often in the form of a radar (or spider) chart-enables the risk profile of the project to be plotted for analysis of where risk treatments might be best applied. Examples of this approach are provided by McFarlan (1981), Ropponen and Lyytinen (2000), Wallace et al (2004a), Shenhar and Dvir (2004), Han and Huang (2007), Howell et al (2010), and Taylor et al (2012). Shenhar and Dvir, for example, identify four key project dimensions against which project risk can be assessed: product novelty, technological uncertainty, complexity, and pace.…”

Section: Risk Management As Factor Analysis (Contingency School)mentioning

confidence: 99%

See 1 more Smart Citation

Robust Optimization for the Discrete Time-Cost Tradeoff Problem with Cost Uncertainty

Hazır

Haouari

Erel

2014

Handbook on Project Management and Scheduling Vol. 2

View full text Add to dashboard Cite

This work is subject to copyright. All rights are reserved by the Publisher, whether the whole or part of the material is concerned, specifically the rights of translation, reprinting, reuse of illustrations, recitation, broadcasting, reproduction on microfilms or in any other physical way, and transmission or information storage and retrieval, electronic adaptation, computer software, or by similar or dissimilar methodology now known or hereafter developed. Exempted from this legal reservation are brief excerpts in connection with reviews or scholarly analysis or material supplied specifically for the purpose of being entered and executed on a computer system, for exclusive use by the purchaser of the work. Duplication of this publication or parts thereof is permitted only under the provisions of the Copyright Law of the Publisher's location, in its current version, and permission for use must always be obtained from Springer. Permissions for use may be obtained through RightsLink at the Copyright Clearance Center. Violations are liable to prosecution under the respective Copyright Law. The use of general descriptive names, registered names, trademarks, service marks, etc. in this publication does not imply, even in the absence of a specific statement, that such names are exempt from the relevant protective laws and regulations and therefore free for general use. While the advice and information in this book are believed to be true and accurate at the date of publication, neither the authors nor the editors nor the publisher can accept any legal responsibility for any errors or omissions that may be made. The publisher makes no warranty, express or implied, with respect to the material contained herein.Printed on acid-free paper Springer is part of Springer Science+Business Media (www.springer.com) PrefaceThis handbook is devoted to scientific approaches to the management and scheduling of projects. Due to their practical relevance, project management and scheduling have been important subjects of inquiry since the early days of Management Science and Operations Research and remain an active and vibrant field of study. The handbook is meant to provide an overview of some of the most active current areas of research. Each chapter has been written by well-recognized scholars, who have made original contributions to their topic. The handbook covers both theoretical concepts and a wide range of applications. For our general readers, we give a brief introduction to elements of project management and scheduling in the first chapter, where we also survey the contents of this book. We believe that the handbook will be a valuable and comprehensive reference to researchers and practitioners in project management and scheduling and hope that it might stimulate further research in this exciting and practically important field.Short-listing and selecting the contributions to this handbook and working with more than one hundred authors have been a challenging and rewarding experience for us. We are grateful to Günter Sch...

show abstract

“…Os assuntos variam desde tipologias de incertezas (NIDUMOLU, 1996;SHENHAR, 1993;SHENHAR, 2001;SONG;DI BENEDETTO, 2001;TATIKONDA;ROSENTHAL, 2000); até estratégias de gerenciamento de incertezas (CHUN, 1994;DOCTOR;NEWTON;PEARSON, 2001;HUCHZERMEIER;LOCH, 2001;SOLT;BAILEY, 2008;NIDUMOLU, 1995;SOMMER;LOCH, 2004;THOMKE;REINERTSEN, 1998). E dentro do assunto de incertezas, surge também o assunto de gerenciamento de riscos, e da mesma forma, um amplo leque de temas se apresenta: como técnicas e ferramentas de gestão de riscos (COX, 2008;DEL CANO;DE LA CRUZ, 2002;DEY;OGUNLANA, 2004;KUMAR, 2002;WANG E CHOU, 2003;SADEH, 2007) e fatores de riscos SALM;LOVE, 2004;BANNERMAN, 2008;HUANG, 2007; ROPPONEN; LYYTINEN, 1997;SICOTTE et al, 2006).…”

Section: Lista De Figurasunclassified

Gestão de incertezas em projetos complexos: quadro conceitual e estudos de caso.

Zheng¹

View full text Add to dashboard Cite

An empirical analysis of risk components and performance on software projects

Cited by 168 publications

References 19 publications

Decision Based Development of Productline: A Quintessence Usability Approach

Decision Based Development of Productline: A Quintessence Usability Approach

Robust Optimization for the Discrete Time-Cost Tradeoff Problem with Cost Uncertainty

Gestão de incertezas em projetos complexos: quadro conceitual e estudos de caso.

Contact Info

Product

Resources

About