DOCSLIB.ORG

PRACTICAL SOFTWARE TESTING Springer New York Berlin Heidelberg Hong Kong London Milan Paris Tokyo PRACTICAL SOFTWARE TESTING

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
PRACTICAL SOFTWARE TESTING Springer New York Berlin Heidelberg Hong Kong London Milan Paris Tokyo PRACTICAL SOFTWARE TESTING PRACTICAL SOFTWARE TESTING Springer New York Berlin Heidelberg Hong Kong London Milan Paris Tokyo PRACTICAL SOFTWARE TESTING A PROCESS-ORIENTED APPROACH ILENE BURNSTEIN Ilene Burnstein Department of Computer Science Illinois Institute of Technology 10 West 31 Street Chicago, IL 60616 USA [email protected] Library of Congress Cataloging-in-Publication Data Burnstein, Ilene. Practical software testing : a process-oriented approach / Ilene Burnstein. p. cm. Includes bibliographical references and index. ISBN 0-387-95131-8 (hc : alk. paper) 1. Computer software—Testing. I. Title. QA76.76.T48 B87 2002 2002024164 005.1Ј4–dc21 ISBN 0-387-95131-8 Printed on acid-free paper. ᭧ 2003 Springer-Verlag New York, Inc. All rights reserved. This work may not be translated or copied in whole or in part without the written permission of the publisher (Springer-Verlag New York, Inc., 175 Fifth Avenue, New York, NY 10010, USA), except for brief excerpts in connection with reviews or scholarly anal- ysis. Use in connection with any form of information storage and retrieval, electronic adapta- tion, computer software, or by similar or dissimilar methodology now known or hereafter developed is forbidden. The use in this publication of trade names, trademarks, service marks, and similar terms, even if they are not identified as such, is not to be taken as an expression of opinion as to whether or not they are subject to proprietary rights. Capability Maturity Model and CMM are registered trademarks of the Software Engineering Institute and Carnegie Mellon University. Testing Maturity Model and TMM are service marks of Illinois Institute of Technology. Printed in the United States of America. 987654321 SPIN 10779083 www.springer-ny.com Springer-Verlag New York Berlin Heidelberg Business Media GmbHםA member of BertelsmannSpringer Science CONTENTS Preface xv INTRODUCTION TO TESTING 1 AS AN ENGINEERING ACTIVITY 1.0 The Evolving Profession of Software Engineering 1 1.1 The Role of Process in Software Quality 4 1.2 Testing as a Process 6 1.3 Overview of the Testing Maturity Model (TMM) 8 1.3.1 TMM Levels 10 List of Key Terms 16 Exercises 16 References 17 2 TESTING FUNDAMENTALS 2.0 Introduction 19 2.1 Basic Definitions 19 vi | Contents 2.2 Software Testing Principles 26 2.3 The Tester’s Role in a Software Development Organization 34 List of Key Terms 36 Exercises 36 References 37 3 DEFECTS, HYPOTHESES, AND TESTS 3.0 Origins of Defects 39 3.1 Defect Classes, the Defect Repository, and Test Design 43 3.1.1 Requirements and Specification Defects 44 3.1.2 Design Defects 46 3.1.3 Coding Defects 48 3.1.4 Testing Defects 51 3.2 Defect Examples: The Coin Problem 51 3.3 Developer/Tester Support for Developing a Defect Repository 57 List of Key Terms 58 Exercises 58 References 59 4 STRATEGIES AND METHODS FOR TEST CASE DESIGN I 4.0 Introduction to Testing Design Strategies 61 4.1 The Smart Tester 62 4.2 Test Case Design Strategies 63 4.3 Using the Black Box Approach to Test Case Design 66 4.4 Random Testing 66 4.5 Equivalence Class Partitioning 67 4.6 Boundary Value Analysis 72 4.7 An Example of the Application of Equivalence Class Partitioning and Boundary Value Analysis 73 4.8 Other Black Box Test Design Approaches 76 4.8.1 Cause-and-Effect Graphing 78 4.8.2 State Transition Testing 82 4.8.3 Error Guessing 85 Contents | vii 4.9 Black Box Testing and Commercial Off-the-Shelf Components (COTS) 86 4.10 Black Box Methods and TMM Level 2 Maturity Goals 88 List of Key Terms 91 Exercises 92 References 95 5 STRATEGIES AND METHODS FOR TEST CASE DESIGN II 5.0 Using the White Box Approach to Test Design 97 5.1 Test Adequacy Criteria 98 5.2 Coverage and Control Flow Graphs 101 5.3 Covering Code Logic 103 5.4 Paths: Their Role in White Box–Based Test Design 108 5.5 Additional White Box Test Design Approaches 111 5.5.1 Data Flow and White Box Test Design 111 5.5.2 Loop Testing 115 5.5.3 Mutation Testing 116 5.6 Evaluating Test Adequacy Criteria 118 5.7 White Box Testing Methods and the TMM 124 List of Key Terms 127 Exercises 127 References 130 6 LEVELS OF TESTING 6.0 The Need for Levels of Testing 133 6.0.1 Levels of Testing and Software Development Paradigms 135 6.1 Unit Test: Functions, Procedures, Classes, and Methods as Units 137 6.2 Unit Test: The Need for Preparation 138 6.3 Unit Test Planning 139 6.4 Designing the Unit Tests 141 6.5 The Class as a Testable Unit: Special Considerations 142 6.6 The Test Harness 148 6.7 Running the Unit Tests and Recording Results 150 viii | Contents 6.8 Integration Test: Goals 152 6.9 Integration Strategies for Procedures and Functions 153 6.10 Integration Strategies for Classes 158 6.11 Designing Integration Tests 159 6.12 Integration Test Planning 162 6.13 System Test: The Different Types 163 6.13.1 Functional Testing 166 6.13.2 Performance Testing 167 6.13.3 Stress Testing 169 6.13.4 Configuration Testing 171 6.13.5 Security Testing 172 6.13.6 Recovery Testing 175 6.14 Regression Testing 176 6.15 Alpha, Beta, and Acceptance Tests 176 6.16 Summary Statement on Testing Levels 178 6.17 The Special Role of Use Cases 179 6.18 Levels of Testing and the TMM 181 List of Key Terms 184 Exercises 184 References 186 7 TEST GOALS, POLICIES, PLANS, AND DOCUMENTATION 7.0 Introductory Concepts 189 7.1 Testing and Debugging Goals and Policies 191 7.2 Test Planning 197 7.3 Test Plan Components 200 7.4 Test Plan Attachments 216 7.4.1 Test Design Specifications 217 7.4.2 Test Case Specifications 218 7.4.3 Test Procedure Specifications 220 7.5 Locating Test Items: The Test Transmittal Report 221 7.6 Reporting Test Results 221 7.7 The Role of the Three Critical Groups in Test Planning and Policy Development 226 Contents | ix 7.8 Process and the Engineering Disciplines: The Role of the Individual as a Process Facilitator 230 List of Key Terms 231 Exercises 231 References 232 8 THE TEST ORGANIZATION 8.0 Introducing the Test Specialist 235 8.1 Skills Needed by a Test Specialist 237 8.2 Building a Testing Group 240 8.3 The Structure of the Testing Group 242 8.4 The Technical Training Program 247 8.5 Career Paths for Testers: An Industry Example 250 8.6 Tester Certification 252 8.7 Integrating Testing Activities in the Software Life Cycle 253 8.8 The Test Organization, Technical Training Program, and Test Integration: Support from the Three Critical Views 257 Exercises 261 References 262 CONTROLLING AND MONITORING 9 THE TESTING PROCESS 9.0 Defining Terms 263 9.1 Measurements and Milestones for Controlling and Monitoring 266 9.1.1 Measurements for Monitoring Testing Status 271 9.1.2 Measurements for Monitoring Tester Productivity 275 9.1.3 Measurements for Monitoring Testing Costs 276 9.1.4 Measurements for Monitoring Errors, Faults and Failures 277 9.1.5 Monitoring Test Effectiveness 279 9.2 Status Meetings, Reports, and Control Issues 283 9.3 Criteria for Test Completion 289 9.4 Software Configuration Management 292 x | Contents 9.5 Controlling and Monitoring: Three Critical Views 296 List of Key Terms 300 Exercises 300 References 302 10 REVIEWS AS A TESTING ACTIVITY 10.0 Expanding the Testing Activity Umbrella 303 10.1 Types of Reviews 307 10.1.1 Inspections as a Type of Technical Review 308 10.1.2 Walkthroughs as a Type of Technical Review 310 10.2 Developing a Review Program 311 10.3 The Need for Review Policies 313 10.4 Components of Review Plans 314 10.4.1 Review Goals 315 10.4.2 Preconditions and Items to be Reviewed 315 10.4.3 Roles, Participants, Team Size, and Time Requirements 317 10.4.4 Review Procedures 320 10.4.5 Review Training 320 10.4.6 Review Checklists 324 10.5 Reporting Review Results 333 10.6 Review, Rework, and Follow-Up 337 10.7 Review Metrics 337 10.8 Support from the Extended/Modified V-Model 340 10.9 The Self-Check or Personal Review 340 10.10 Reviews and the TMM Critical Views 343 List of Key Terms 345 Exercises 345 References 347 A MEASUREMENT PROGRAM TO SUPPORT 11 PRODUCT AND PROCESS QUALITY 11.0 The Need for a Formal Test Measurement Program 349 11.1 Some Measurement-Related Definitions 353 Contents | xi 11.2 Initiating a Measurement Program 354 11.3 Software Quality Evaluation 364 11.4 Measurement and TMM Levels 372 11.4.1 Measurements for TMM Level 1 373 11.4.2 Measurements for TMM Level 2 375 11.4.3 Measurements for TMM Level 3 377 11.4.4 Measurements for TMM Level 4 381 11.4.5 Measurements for TMM Level 5 383 11.5 A Test Measurement Program, Software Quality Valuations and the Three Critical Views 386 List of Key Terms 389 Exercises 389 References 391 EVALUATING SOFTWARE QUALITY: 12 A QUANTITATIVE APPROACH 12.0 Review of Quality Concepts 393 12.1 Quality Costs 395 12.2 What Is Quality Control? 397 12.3 The Role of Operational Profiles and Usage Models in Quality Control 399 12.4 Support for Quality Control: Statistical Testing 407 12.5 Software Reliability 410 12.5.1 Measurements for Software Reliability 413 12.6 Reliability, Quality Control, and Stop-Test Decisions 414 12.6.1 Applying Reliability Models 417 12.7 Confidence Levels and Quality Control 422 12.8 Usability Testing and Quality Control 424 12.9 An Approach to Usability Testing 425 12.9.1 Exploratory Usability Testing 426 12.9.2 Assessment Usability Testing 427 12.9.3 Validation Usability Testing 427 12.9.4 Comparison Test 429 12.9.5 Usability Testing: Resource Requirements 429 12.9.6 Usability Tests and Measurements 430 xii | Contents 12.10 Software Quality Control and the Three Critical Views 433 List of Key Terms 436 Exercises 436 References 437 13 DEFECT ANALYSIS AND PREVENTION 13.0 Processes and Defects 439 13.1 History of Defect Analysis and Prevention
Load more

Recommended publications
  • Software Company Edition
    Data Sheet Software Company Edition NetSuite Software Company Edition offers the industry’s first and only: NetSuite—The One Integrated Application To Manage Your Software Business • Integrated revenue recognition and advanced billing With NetSuite, your software company can manage its entire front-office and back-office • Role-based, customizable dashboards operations with a single, flexible, powerful business application — integrating customer relation- • Integrated CRM, Accounting/ERP, ecommerce ship management, customer service, financials, inventory management, ecommerce, and more. NetSuite Software Company Edition Hundreds of software companies run their business on NetSuite — and we do too. Here’s why features include: NetSuite is the best application for software companies. • Customer Relationship Management - Sales Force Automation Advanced Financials with Revenue Management and Revenue Recognition - Marketing Automation Financials are complex in any industry, and they are arguably the most complex in the software - Customer Support and Service industry. The stumbling block for most software companies is managing revenue recognition - Incentive Management* - Offline Sales Client* and billing schedules—and ensuring compliance. Few financial packages provide these tools, - Issue Management* forcing companies to manage these complexities offline in spreadsheets or in third party stand- - Partner Relationship Management alone packages. With NetSuite you have one financial system that manages accounting, complex billing and revenue recognition—so there’s no more double entry. • Accounting/ERP - Revenue Recognition NetSuite supports AICPA, FASB and SEC regulations (including SOP 81-1, SAB 101, and EITF - Advanced Billing 00-21). NetSuite also accommodates the requirements specified in SOP 97-2 & 98-9 relating - General Ledger to Vendor Specific Objective Evidence or VSOE, including the accommodation of the Residual - Accounts Receivable, Accounts Payable Method and a separate VSOE price for every item.
    [Show full text]
  • Software Developers Working from Home During the COVID-19 Pandemic
    A Tale of Two Cities: Software Developers Working from Home During the COVID-19 Pandemic DENAE FORD, Microsoft Research MARGARET-ANNE STOREY, University of Victoria, Canada THOMAS ZIMMERMANN, Microsoft Research CHRISTIAN BIRD, Microsoft Research SONIA JAFFE, Microsoft Corp. CHANDRA MADDILA, Microsoft Research JENNA L. BUTLER, Microsoft Research BRIAN HOUCK, Microsoft Corp. NACHIAPPAN NAGAPPAN, Facebook The COVID-19 pandemic has shaken the world to its core and has provoked an overnight exodus of developers that normally worked in an office setting to working from home. The magnitude of this shift and the factors that have accompanied this new unplanned work setting go beyond what the software engineering community has previously understood to be remote work. To find out how developers and their productivity were affected, we distributed two surveys (with a combined total of 3,634 responses that answered all required questions) —weeks apart to understand the presence and prevalence of the benefits, challenges, and opportunities to improve this special circumstance of remote work. From our thematic qualitative analysis and statistical quantitative analysis, we find that there isa dichotomy of developer experiences influenced by many different factors (that for some are a benefit, while for others a challenge). For example, a benefit for some wasbeing close to family members but for others having family members share their working space and interrupting their focus, was a challenge. Our surveys led to powerful narratives from respondents
    [Show full text]
  • Critical Review of Extended Waterfall Model
    International Journal of Scientific & Engineering Research, Volume 6, Issue 11, November-2015 425 ISSN 2229-5518 Critical Review of Extended Waterfall Model Rajesh H. Kulkarni, P.Padmanabham, K.K.Baseer Abstract—Software product quality improvement is a desired attribute and a strenuous effort is required to achieve that.Usability is also a desired attribute as it helps in identifying how effectively user achieves product goals.Concrete efforts to integrate Software Engineering and Human Computer Interaction exist in the form of models by many researchers. Better user experience is an oft expressed and desired quality of the products designed nowadays.Many efforts in this regard lead to various proposals of smooth integration of SE (software engineering) processes with HCI (human computer integration) for product development. One such effort is extended waterfall process model. This paper presents a critical review of extended waterfall model. It also suggests means to bring nearer the two diverse communities of SE and HCI. Index Terms— Usability, SE, HCI, Extended Waterfall Process Model. —————————— —————————— 1 INTRODUCTION He model of waterfall process refer Figure 1 in the field of T software engineering [1] has been playing a chief role Waterfall model is classic SDLC model. This model is also from the past. This model was put forth in 1950s and later, called as a heavyweight process. The lifecycle is long say six it has turned out to be a renowned model in 1970s. Its struc- months. This classic model consists of the phases: Require- ture takes the form of a cascade involving phases and it can be ment, Design, Analyze, Code, Test,and Maintain.
    [Show full text]
  • Proven Business Value of the Borland® Application Lifecycle Management (ALM) Solution
    Proven Business Value of the Borland® Application Lifecycle Management (ALM) Solution A Consynity white paper Principal, Terry Theisen www.consynity.com Proven Business Value of the Borland® Application Lifecycle Management (ALM) Solution Proven Business Value of the Borland® Application Lifecycle Management (ALM) Solution Introduction 3 Challenges and Opportunities in Application Development and Deployment 4 The Borland ALM Solution 5 Borland ALM Value Proposition 5 Application Lifecycle Quantified Benefits 5 Define Design Develop Test Deploy Manage Borland ALM Customer Results 8 Case Study #1: Deployment Across Large Enterprise 8 Implementation Details Case Study Findings ROI Analysis Case Study #2: Standardizing on Common Solution 10 Implementation Details Case Study Findings Case Study #3: Migration to Borland ALM Solution 11 Implementation Details Case Study Findings ROI Analysis Benefits of an Integrated Suite of Solutions 12 Conclusion: Dramatic ROI with Borland ALM 14 2 2003 Consynity All Rights Reserved Proven Business Value of the Borland® Application Lifecycle Management (ALM) Solution Introduction In an extremely competitive global economy where advantage is short-lived, companies in all industries continually strive for an edge over the competition. One way for companies to achieve that edge is to deliver better software, faster – software applications that strengthen customer relationships, software that increases operational efficiency, software that creates market leaders. Increasingly companies develop new applications on Java™ systems and Microsoft® .NET platforms, requiring development environments that support both as well as other platforms. Gartner’s “Leading Programming Languages for IT Portfolio Planning” report of September 2002 forecasts that by 2005, over 4.5 million programmers will use Java and .NET languages to build software applications.
    [Show full text]
  • Emerging Trends in Management, IT and Education ISBN No.: 978-87-941751-2-4
    Emerging Trends in Management, IT and Education ISBN No.: 978-87-941751-2-4 Paper 12 IMPLEMENTING PRODUCT DIVERSIFICATION STRATEGIES FOR THE SUSTAINABILITY OF A TECHNOLOGY COMPANY - A CASE OF MICROSOFT CORPORATION Vinayachandra1 & Krishna Prasad K2 1Research Scholar, College of Computer Science and Information Science, Srinivas University, Mangalore, India 2 College of Computer Science and Information Science, Srinivas University, Mangalore, India E-mail : [email protected] Abstract Started in 1975, with a view to develop and vend BASIC interpreter, today, Microsoft develop, produce, license, support and sell worldwide software, user-level electronics, personal computers, and allied services. The company is world-famous because of its best software products Windows operating systems, Office suits, IE and Edge. The company’s notable hardware pieces are Xbox and Microsoft Surface family touch-screen computers. The company is listed as the top software company by Forbes Global for many years. From its inception to date, the company is maintaining top ranking technology-wise, product-wise, service-wise, revenue-wise, and growth-wise. It is possible for the company to sustain growth because of the integration and implementation of product diversification strategy. Over the years the company transformed from just a developer and seller of interpreter to producer & marketer of wide variety of software-hardware products. This paper analyses the strategies the company adopted and incorporated in diversifying product and services lineup to sustain growth and maintain market stability. It also analyses the relevance and acceptability of different Microsoft products, its customer base, and software market share and near future strategies. Keywords: Microsoft, strategies, product diversification, Windows, generic, intensive.
    [Show full text]
  • Agile Software Development Processes
    Agile Software Development Jinjin Li Technische Universitt Berlin Berlin, Germany E-mail:[email protected] Abstract—With the further development of computer technol- customer requirements in the process, in the process people ogy, the software development process has some new goals and will invest resources and then convert it to outputs of project. requirements. In order to adapt to these changes, people has Before the 1960s, computers had just put into practical use, optimized and improved the previous method. At the same time, some of the traditional software development methods have been the software design was often only for a particular application unable to adapt to the requirements of people. Therefore, in re- in the specified design and preparation. The scale of software cent years there have been some new lightweight software process was relative small and usually didn’t have documentation, development methods, That is agile software development, which rarely use a systematic metohd to development. Design and is widely used and promoted. In this paper the author will firstly programming was often equated. introduces the background and development about agile software development, as well as comparison to the traditional software In mid-1960s, large capacity, high speed computers have development. Then the second chapter gives the definition of agile enabled the rapid expansion of computer applications, the software development and characteristics, principles and values. quantity of software development has increased dramatically. In the third chapter the author will highlight several different The Appearance of High-level programming language and agile software development methods, and characteristics of each operating system, causing of changes in the way of computer method.
    [Show full text]
  • How to Become a Programmer Everything (Non-Technical) You Need to Know to Start Making Money Writing Code Rob Walling V1.0
    How to Become a Programmer Everything (Non-Technical) You Need to Know to Start Making Money Writing Code www.SoftwareByRob.com Rob Walling v1.0 Contents Introduction .................................................................................................................................... 4 What is Computer Programming? .................................................................................................. 5 Why Should I Become a Programmer? ........................................................................................... 7 What Are Some Reasons Not to Become a Programmer? ........................................................... 10 What are the Different “Worlds” of Programming? ..................................................................... 11 What Programming Language Should I Learn? ............................................................................ 13 Where Do I Start?.......................................................................................................................... 16 I’ve Built a Project and Decided I Like Programming, What Next? .............................................. 18 I Just Graduated from School, How Can I Get Experience? .......................................................... 20 How Can I Become a Programmer Without Going to College? .................................................... 22 What About Offshoring – Will I have a Job in 5 years? ................................................................ 23 Do I Have to Know Math to be a Programmer?
    [Show full text]
  • Software Development a Practical Approach!
    Software Development A Practical Approach! Hans-Petter Halvorsen https://www.halvorsen.blog https://halvorsen.blog Software Development A Practical Approach! Hans-Petter Halvorsen Software Development A Practical Approach! Hans-Petter Halvorsen Copyright © 2020 ISBN: 978-82-691106-0-9 Publisher Identifier: 978-82-691106 https://halvorsen.blog ii Preface The main goal with this document: • To give you an overview of what software engineering is • To take you beyond programming to engineering software What is Software Development? It is a complex process to develop modern and professional software today. This document tries to give a brief overview of Software Development. This document tries to focus on a practical approach regarding Software Development. So why do we need System Engineering? Here are some key factors: • Understand Customer Requirements o What does the customer needs (because they may not know it!) o Transform Customer requirements into working software • Planning o How do we reach our goals? o Will we finish within deadline? o Resources o What can go wrong? • Implementation o What kind of platforms and architecture should be used? o Split your work into manageable pieces iii • Quality and Performance o Make sure the software fulfills the customers’ needs We will learn how to build good (i.e. high quality) software, which includes: • Requirements Specification • Technical Design • Good User Experience (UX) • Improved Code Quality and Implementation • Testing • System Documentation • User Documentation • etc. You will find additional resources on this web page: http://www.halvorsen.blog/documents/programming/software_engineering/ iv Information about the author: Hans-Petter Halvorsen The author currently works at the University of South-Eastern Norway.
    [Show full text]
  • Interviewing Software Testing Job Candidates
    KANER.COM Cem Kaner, Ph.D., J.D. [email protected] P.O. Box 1200 408-244-7000 (Voice) Santa Clara, CA 95052 www.kaner.com 408-244-2181 (FAX) RECRUITING SOFTWARE TESTERS INTERNATIONAL QUALITY WEEK SAN JOSE, CA, JUNE, 1999 This paper is a work in progress. Eventually, it will become a chapter in the 3rd Edition of Testing Computer Software (under development by Cem Kaner, Bob Johnson, Brian Lawrence, Jack Falk, & Hung Quoc Nguyen. This is a multi-year project. Please don't ask me when it will be done. It certainly won't be done in 1999.) I'd appreciate comments and suggestions. (Send them to [email protected].) I don't claim to be an expert on recruiting, but I have been reasonably successful at recruiting testers (and other software workers) over the last 15 years, have made a lot of mistakes, and learned a few lessons. This paper collects some of those lessons. Managers get work done through other people. The people that a manager chooses are the people who will achieve, or fail to achieve, the mission of the group and the tasks assigned by the manager. Recruiting staff is one of the hardest jobs for any manager. Hiring the wrong staff is, I believe, the worst mistake that a manager can make. A good treatment of recruiting would consider the following issues: . A behavioral approach to gathering information . Legal issues . Consensus-driven hiring . A strategy for gathering information . Characteristics of the person you're seeking . Defining the position and characteristics needed for it .
    [Show full text]
  • Why Software Firms Build Hardware – and What Microsoft Is Doing About It
    Why Software Firms Build Hardware – And What Microsoft Is Doing About It by Ryan M. Shaffer B.S. Electrical Engineering Grove City College, 2008 M.S. Computer Science Boston University, 2011 SUBMITTED TO THE SYSTEM DESIGN AND MANAGEMENT PROGRAM IN PARTIAL FULFILLMENT OF THE REQUIREMENTS FOR THE DEGREE OF MASTER OF SCIENCE IN ENGINEERING AND MANAGEMENT AT THE MASSACHUSETTS INSTITUTE OF TECHNOLOGY FEBRUARY 2015 © Ryan M. Shaffer. All rights reserved. The author hereby grants to MIT permission to reproduce and to distribute publicly paper and electronic copies of this thesis document in whole or in part in any medium now known or hereafter created. Signature of Author: _____________________________________________________ System Design and Management Program January 9, 2015 Certified by: ____________________________________________________________ Michael Cusumano Sloan Management Review Professor in Management Thesis Supervisor Accepted by: ___________________________________________________________ Patrick Hale Director, System Design and Management Fellows Program Why Software Firms Build Hardware – And What Microsoft Is Doing About It by Ryan M. Shaffer Submitted to the System Design and Management Program on January 9, 2015 in Partial Fulfillment of the Requirements for the Degree of Master of Science in Engineering and Management ABSTRACT Many software companies build first-party hardware products due to the trend toward smaller, more highly-integrated devices, along with the fast pace of innovation in the technology industry. Building hardware products does not always lead to success and actually creates a financial risk for the company by significantly reducing profit margins as compared to the traditional profit margins to which large software companies are accustomed. Three specific strategies are observed which firms have used successfully in this area.
    [Show full text]
  • Agile Software Development: a Case Study in a Software Company
    Agile Software Development: A Case Study in a Software Company L. Ashkenazi*, A. Shmilovici**, I. Ben-Gal* *Dept. of Industrial Engineering, Tel-Aviv University **Dept. of Information Systems Engineering, Ben-Gurion University In this case study we accompanied a software development project which was performed using the Agile SCRUM method for software development. Subjective parameters of the design and code quality were collected and analyzed and a comparison was performed to an equivalent non-Agile project. We analyzed the software development process from the following aspects: Initial Effort Estimation process compared to the Effort Estimation given for the project by the COCOMO-II model; Control and management process compared to the one suggested by the PERT/CPM and Critical Chain methods. Results and conclusions: The COCOMO II model showed the smallest deviation in its effort estimation from the real required effort; The PERT/CPM method is not recommended as in most cases the real result was out of the PERT/ CPM allowed variance. 1. Introduction and Goals Software development is though from a project management point of view: too many software development projects overrun their schedules, their budgets, and deliver a low quality product. Scrum is an iterative incremental process of software development that focuses on a subset of project management and requirements management. It is one of the new Agile methods for software development [1, 2]. In this case study we accompanied a software development project which was performed using the Scrum method. Subjective and objective parameters of the design and code quality were collected and analyzed and a comparison was performed to an equivalent non-agile project.
    [Show full text]
  • Assessing Application Lifecycle Management Potentials: an Exploratory Industrial Case Study
    ASSESSING APPLICATION LIFECYCLE MANAGEMENT POTENTIALS: AN EXPLORATORY INDUSTRIAL CASE STUDY A THESIS SUBMITTED TO THE GRADUATE SCHOOL OF NATURAL AND APPLIED SCIENCES OF ÇANKAYA UNIVERSITY BY ZÜLEYHA AKGÜN IN PARTIAL FULFILLMENT OF THE REQUIREMENTS FOR THE DEGREE OF MASTER OF SCIENCE IN THE DEPARTMENT OF COMPUTER ENGINEERING JANUARY 2019 iii ABSTRACT ASSESSING APPLICATION LIFECYCLE MANAGEMENT POTENTIALS: AN EXPLORATORY INDUSTRIAL CASE STUDY AKGÜN, Züleyha M.Sc., Department of Computer Engineering Supervisor: Dr. Instructor Murat YILMAZ January 2019 Software projects require a good management system to achieve a successful result because they are risky and often spread over a long period. The most important element of a good management is controlled planning. Within the scope of the project, all necessary stages of the software development life cycle need to be accurately and consistently planned and documented to complete the requirements, analysis, design, development process, estimations, risk and change control methods, test and maintenance processes in a complete and accurate manner. The notion of software lifecycle management requires the incorporation of effective software engineering processes that encompass not only development but also deployment and maintenance. Although new methodologies for software engineering continue to emerge, still software development continues to experience a significant amount of failure rates. To overcome the complexities of modern software development, agile development philosophy suggests that software developers should remain involved with the application and working continuously with stakeholders to make required changes incrementally by tracking application changes. Application Lifecycle Management (ALM) is an emerging trend that reflects a novel attitude towards software development also expressed as the DevOps, which blends the tasks performed by a firm’s software development and systems operations teams, monitor software artifacts from inception to completion while changes are noted.
    [Show full text]