Cover of Managing software development and maintenance
Read Time: ~3.4 hr

Managing software development and maintenance

by Carma L. McClure (1981)

About this book

Software development has many advantages. These advantages are especially important when designing software for healthcare, SPsoft This kind of software helps the doctors make diagnoses faster, manage patient records and monitor treatment. They also help streamline the communication between the healthcare professionals. Good software overall improves the quality of service and reduces the workload of the staff.

Setting / LocationGlobal
Story EraModern Era
Protagonist / CoreManaging software development and maintenance Lead Character

Readers who enjoyed this also loved

Cover of Twenty-first-century management

Twenty-first-century management

Hesh Kestin

With the idea of writing a magazine article on what had to be the business world's longest-running lucky streak, I came to CA for a week. I stayed the better part of a year. What I found was a company so revolutionary that it had put aside the dusty principles of American business totalitarianism and laughed off all the new panaceas. CA's formula was so simple it seemed ridiculous ... the perpetual elasticity of such relentless self-renewal that even those within CA were too busily involved in it to be aware of what it was. "It's just good people," Charles Wang told me. I though he was being disingenuous. He wasn't. It is. They are. And this is the story of how they got that way.

Cover of Access 2010

Access 2010

Matthew MacDonald

"Go from Access novice to true master with the professional database design tips and crystal-clear explanations in this book. You'll learn all the secrets of this powerful database program so you can use your data in creative ways--from creating product catalogs and publishing information online to producing invoices and reports"--Cover, p. 4.

Cover of More About Software Requirements

More About Software Requirements

Karl E. Wiegers

No matter how much instruction you've had on managing software requirements, there's no substitute for experience. Too often, lessons about requirements engineering processes lack the no-nonsense guidance that supports real-world solutions. Complementing the best practices presented in his book, Software Requirements, Second Edition, requirements engineering authority Karl Wiegers tackles even more of the real issues head-on in this book. With straightforward, professional advice and practical solutions based on actual project experiences, this book answers many of the tough questions raised by.

Cover of Burning the ships

Burning the ships

Marshall Phelps, David Kline

At the start of this decade, Microsoft was on the defensive--beset on all sides by anti-trust suits and costly litigation, and viewed by many in the technology industry as a monopolist and market bully. How was it going to survive and succeed in the emerging new era of "open innovation," where collaboration and cooperation between firms, rather than market conquest, would be the keystones of success? This was the challenge facing Microsoft founder and Chairman Bill Gates. But "like Cortez burning his ships at the shores of the New World," Gates decided to embrace the change that was needed. He recruited Marshall Phelps--the legendary "godfather" of intellectual property who had turned IBM's IP portfolio into a $2 billion-a-year gold mine--out of retirement and into the cauldron of controversy that was Microsoft. Only this time Phelps' mission was infinitely more challenging than simply making money from IP. It was to help reform Microsoft's "man the barricades" culture, encourage the company to abandon its fortress mentality around its technology and share it with others for mutual benefit, and use intellectual property not as a weapon of competitive warfare but as a bridge to collaboration with other firms instead. Here, for the first time (and 500 collaboration deals later), is the inside story of what one analyst has called "the biggest change Microsoft has undergone since it became a multinational company." In this book, authors Marshall Phelps and David Kline take the reader inside the dramatic struggle within Microsoft to find a new direction. They offer an extraordinary behind-the-scenes view of the high-level deliberations of the company's senior-most executives, the internal debates and conflicts among executives and rank-and-file employees alike over the company's new collaborative direction, and the company's controversial top-secret partnership building efforts with major open source companies and others around the world. Nothing was held back from this book save for information specifically prohibited from disclosure by confidentiality agreements that Microsoft signed with other companies. Indeed, the degree of access to Microsoft's inner workings granted to the authors--and the honest self-criticism offered by Microsoft leaders and employees alike--was unprecedented in the company's 34-year history. There are lessons in this book for executives in every industry--most especially on the role that intellectual property can play in liberating previously untapped value in a company and opening up powerful new business opportunities in today's era of "open innovation." Here is a powerful inside account of the dawn of a new era at what is arguably the most powerful technology company on earth.

Managing software development and maintenance by Carma L. McClure | Literally Just Books