The complexity of software is continuously growing as a result of today’s interconnected business processes. Governance of architecture and technology strategy helps to ensure coherence of software and avoid excessive complexity. At the same time software development needs room for creativity and empowerment to provide solutions to business problems of increasing complexity. The book looks at this software dilemma from the perspectives of CIOs/CTOs, software architects, and auditors. Each of these groups has different interests which need to be considered, reconciled, and balanced. CIOs/CTOs are provided with the boundary conditions they have to establish assuring the achievement of strategic objectives. Architects and auditors find proven concepts for effectively assessing software projects and architectures, as well as for effectively communicating identified issues to responsible persons. The book is based on the author’s long experience in software engineering, governance, and auditing.

The complexity of software is continuously growing as a result of today’s interconnected business processes. Governance of architecture and technology strategy helps to ensure coherence of software and avoid excessive complexity. At the same time software development needs room for creativity and empowerment to provide solutions to business problems of increasing complexity. The book looks at this software dilemma from the perspectives of CIOs/CTOs, software architects, and auditors. Each of these groups has different interests which need to be considered, reconciled, and balanced. CIOs/CTOs are provided with the boundary conditions they have to establish assuring the achievement of strategic objectives. Architects and auditors find proven concepts for effectively assessing software projects and architectures, as well as for effectively communicating identified issues to responsible persons. The book is based on the author’s long experience in software engineering, governance, and auditing.

Imagine sending a magazine article to 10 friends-making photocopies, putting them in envelopes, adding postage, and mailing them. Now consider how much easier it is to send that article to those 10 friends as an attachment to e-mail. Or to post the article on your own site on the World Wide Web. The ease of modifying or copying digitized material and the proliferation of computer networking have raised fundamental questions about copyright and patentâ€"intellectual property protections rooted in the U.S. Constitution. Hailed for quick and convenient access to a world of material, the Internet also poses serious economic issues for those who create and market that material. If people can so easily send music on the Internet for free, for example, who will pay for music? This book presents the multiple facets of digitized intellectual property, defining terms, identifying key issues, and exploring alternatives. It follows the complex threads of law, business, incentives to creators, the American tradition of access to information, the international context, and the nature of human behavior. Technology is explored for its ability to transfer content and its potential to protect intellectual property rights. The book proposes research and policy recommendations as well as principles for policymaking.

An examination of work—including the organization of work and the market forces that surround it—through the lens of the collaborative practice of game development. Rank-and-file game developers bring videogames from concept to product, and yet their work is almost invisible, hidden behind the famous names of publishers, executives, or console manufacturers. In this book, Casey O’Donnell examines the creative collaborative practice of typical game developers. His investigation of why game developers work the way they do sheds light on our understanding of work, the organization of work, and the market forces that shape (and are shaped by) media industries. O’Donnell shows that the ability to play with the underlying systems—technical, conceptual, and social—is at the core of creative and collaborative practice, which is central to the New Economy. When access to underlying systems is undermined, so too is creative collaborative process. Drawing on extensive fieldwork in game studios in the United States and India, O’Donnell stakes out new territory empirically, conceptually, and methodologically. Mimicking the structure of videogames, the book is divided into worlds, within which are levels; and each world ends with a boss fight, a “rant” about lessons learned and tools mastered. O’Donnell describes the process of videogame development from pre-production through production, considering such aspects as experimental systems, “socially mandatory” overtime, and the perpetual startup machine that exhausts young, initially enthusiastic workers. He links work practice to broader systems of publishing, manufacturing, and distribution; introduces the concept of a privileged “actor-intra-internetwork”; and describes patent and copyright enforcement by industry and the state.

"This book addresses the topic of software design: how to decompose complex software systems into modules (such as classes and methods) that can be implemented relatively independently. The book first introduces the fundamental problem in software design, which is managing complexity. It then discusses philosophical issues about how to approach the software design process and it presents a collection of design principles to apply during software design. The book also introduces a set of red flags that identify design problems. You can apply the ideas in this book to minimize the complexity of large software systems, so that you can write software more quickly and cheaply."--Amazon.

Named one of 100 Leadership & Success Books to Read in a Lifetime by Amazon Editors An innovation classic. From Steve Jobs to Jeff Bezos, Clay Christensen’s work continues to underpin today’s most innovative leaders and organizations. The bestselling classic on disruptive innovation, by renowned author Clayton M. Christensen. His work is cited by the world’s best-known thought leaders, from Steve Jobs to Malcolm Gladwell. In this classic bestseller—one of the most influential business books of all time—innovation expert Clayton Christensen shows how even the most outstanding companies can do everything right—yet still lose market leadership. Christensen explains why most companies miss out on new waves of innovation. No matter the industry, he says, a successful company with established products will get pushed aside unless managers know how and when to abandon traditional business practices. Offering both successes and failures from leading companies as a guide, The Innovator’s Dilemma gives you a set of rules for capitalizing on the phenomenon of disruptive innovation. Sharp, cogent, and provocative—and consistently noted as one of the most valuable business ideas of all time—The Innovator’s Dilemma is the book no manager, leader, or entrepreneur should be without.

The Founder's Dilemmas examines how early decisions by entrepreneurs can make or break a startup and its team. Drawing on a decade of research, including quantitative data on almost ten thousand founders as well as inside stories of founders like Evan Williams of Twitter and Tim Westergren of Pandora, Noam Wasserman reveals the common pitfalls founders face and how to avoid them.

In this revolutionary bestseller, innovation expert Clayton M. Christensen says outstanding companies can do everything right and still lose their market leadership—or worse, disappear altogether. And not only does he prove what he says, but he tells others how to avoid a similar fate. Focusing on “disruptive technology,” Christensen shows why most companies miss out on new waves of innovation. Whether in electronics or retailing, a successful company with established products will get pushed aside unless managers know when to abandon traditional business practices. Using the lessons of successes and failures from leading companies, The Innovator’s Dilemma presents a set of rules for capitalizing on the phenomenon of disruptive innovation. Find out: When it is right not to listen to customers. When to invest in developing lower-performance products that promise lower margins. When to pursue small markets at the expense of seemingly larger and more lucrative ones. Sharp, cogent, and provocative, The Innovator’s Dilemma is one of the most talked-about books of our time—and one no savvy manager or entrepreneur should be without.

Observing how business management is obsessed with analysis and numbers, Dealing with Dilemmas shows there is an entire class of problems that cannot be solved by analysis: business dilemmas. Dilemmas, representing a large part of strategic decision-making, require the opposite approach of analysis; synthesis. Dealing with Dilemmas shows how popular performance management methodologies can be used in new and previously unexplored ways. It authoritatively shows you how your business can move forward strategically in ways previously impossible. Shows dangers in current thinking around analytics and performance management Includes practical case examples and interviews with C-level executives and government officials world-wide, both in commercial enterprise and public sector Makes the most nebulous of management processes, strategy formulation, insightful and links it tightly to strategy execution and performance management. Filled with case studies and examples, this book reveals how your business can start solving dilemmas and move forward strategically.

Software Engineering: A Methodical Approach (Second Edition) provides a comprehensive, but concise introduction to software engineering. It adopts a methodical approach to solving software engineering problems, proven over several years of teaching, with outstanding results. The book covers concepts, principles, design, construction, implementation, and management issues of software engineering. Each chapter is organized systematically into brief, reader-friendly sections, with itemization of the important points to be remembered. Diagrams and illustrations also sum up the salient points to enhance learning. Additionally, the book includes the author’s original methodologies that add clarity and creativity to the software engineering experience. New in the Second Edition are chapters on software engineering projects, management support systems, software engineering frameworks and patterns as a significant building block for the design and construction of contemporary software systems, and emerging software engineering frontiers. The text starts with an introduction of software engineering and the role of the software engineer. The following chapters examine in-depth software analysis, design, development, implementation, and management. Covering object-oriented methodologies and the principles of object-oriented information engineering, the book reinforces an object-oriented approach to the early phases of the software development life cycle. It covers various diagramming techniques and emphasizes object classification and object behavior. The text features comprehensive treatments of: Project management aids that are commonly used in software engineering An overview of the software design phase, including a discussion of the software design process, design strategies, architectural design, interface design, database design, and design and development standards User interface design Operations design Design considerations including system catalog, product documentation, user message management, design for real-time software, design for reuse, system security, and the agile effect Human resource management from a software engineering perspective Software economics Software implementation issues that range from operating environments to the marketing of software Software maintenance, legacy systems, and re-engineering This textbook can be used as a one-semester or two-semester course in software engineering, augmented with an appropriate CASE or RAD tool. It emphasizes a practical, methodical approach to software engineering, avoiding an overkill of theoretical calculations where possible. The primary objective is to help students gain a solid grasp of the activities in the software development life cycle to be confident about taking on new software engineering projects.