Software Engineering BSC DS UNIT 1 .pptx
- 1. The Nature of Software • An Overview of Software Concepts, Application Domains, and Legacy Systems
- 2. What is Software? • Software is a collection of programs, procedures, and associated documentation and data.
- 3. Characteristics of Software • • Intangible • • Developed, not manufactured • • Doesn’t wear out • • Custom-built or generic
- 4. Software vs Hardware • • Software: Logical & intangible • • Hardware: Physical & tangible • • Software controls hardware
- 6. Defining Software – IEEE • IEEE defines software as: ‘Computer programs, procedures, and possibly associated documentation and data’.
- 7. Components of Software • 1. Programs • 2. Data • 3. Documentation
- 8. Types of Software • • System Software • • Application Software • • Embedded Software • • AI and Scientific Software
- 9. System vs Application Software • • System: OS, device drivers • • Application: Word processors, games
- 10. Embedded Software • Software embedded in hardware devices like washing machines, cars, routers.
- 11. Web and Mobile Applications • Apps that run on the internet or mobile devices. • E.g., Browsers, Banking apps
- 12. AI and Scientific Applications • Used in machine learning, simulations, and scientific research.
- 13. Software Application Domains • • Business • • Engineering and Scientific • • Embedded Systems • • Web/Mobile Apps
- 14. Business Software Domain • Examples: ERP, CRM, Billing systems. • Supports business operations and decision making.
- 15. Legacy Software • Old software still in use due to functionality and cost of replacement. • Often lacks documentation.
- 16. Challenges of Legacy Software • • Difficult maintenance • • Integration issues • • Poor documentation • • Risky replacement
- 17. Software Engineering: McCall's Quality Factors • Understanding software quality using McCall's model.
- 18. What is Software Quality? • Software quality refers to how well software is designed and how well it conforms to functional requirements.
- 19. Introduction to McCall’s Quality Model • Developed in 1977 by Jim McCall to bridge the gap between users and developers.
- 20. McCall’s Model Structure • Three major perspectives: • • Product Operation • • Product Revision • • Product Transition
- 21. Product Operation Factors • Focus on the operational characteristics of the software: • • Correctness • • Reliability • • Efficiency • • Integrity • • Usability
- 22. Correctness • The extent to which software performs its intended functions.
- 23. Reliability • The ability of software to maintain its performance over time without failure.
- 24. Efficiency • How well software uses system resources and its responsiveness.
- 25. Integrity • Protection of software from unauthorized access or modifications.
- 26. Usability • Ease with which users can learn and operate the software.
- 27. Product Revision Factors • Relate to the ease of modifying the software: • • Maintainability • • Flexibility • • Testability
- 28. Maintainability • Ease with which software can be corrected or modified.
- 29. Flexibility • Ease of changing software to meet new requirements.
- 30. Testability • Ease with which software can be tested to ensure quality.
- 31. Product Transition Factors • Concerned with adapting software to new environments: • • Portability • • Reusability • • Interoperability
- 32. Portability • Ease of transferring software to different environments.
- 33. Reusability • Extent to which software components can be reused in other applications.
- 34. Interoperability • Ability of software to interact with other systems or software.
- 35. Summary of McCall’s Quality Factors • Total of 11 quality factors grouped into 3 categories: • Operation, Revision, Transition.
- 36. Conclusion • McCall’s model provides a foundational framework for evaluating and improving software quality.