1 / 9

Understanding Software: Elements, Myths, and Challenges

Chapter 1 of the book delves into the fundamental aspects of software, including instructions, data structures, and documentation. It explores how software is a logical system element and discusses myths related to software management, customers, and practitioners. The chapter also highlights the challenges posed by software changes.

quana
Download Presentation

Understanding Software: Elements, Myths, and Challenges

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Chapter 1The Product

  2. What is Software? • 1) instructions (programs) that when executed provide desired function and performance • 2) data structures that enable the programs to adequately manipulate information • 3) documents that describe the operation and use of the programs • A logical rather than physical system element

  3. What is Software? • software is engineered • software doesn’t wear out • software is custom built • software is complex

  4. Failure (“Bathtub”) Curve for Hardware Infant mortality Wear out Failure Rate Time

  5. Wear vs. Deterioration

  6. Software Applications • system software • real-time software • business software • engineering/scientific software • embedded software • PC software • WebApps (Web applications) • AI software

  7. Software Myths • Management • We have standards • We have new computers • We’ll add more people to catch up • I outsourced it, I’m done • Customer • We have general objectives, let’s start • Change is easily accommodated • Practitioner • We’ll write it and be done • I can’t assess quality until it is running • I only need deliver code • Software engineering is about meaningless documents

  8. The Cost of Change

  9. Software Poses Challenges

More Related