Chapter 1 Introduction to Software Engineering.pdf
- 3. Topic to be Cover Definition and Importance of Software Engineering Professional Software Development Software Development Life Cycle (SDLC) Software Engineering Ethics.
- 4. Software Software is computer programs and associated documentation. Software products may be developed for a particular customer or may be developed for a general market. Characteristics of good software ■ Reliability. ■ Scalability. ■ Portability. ■ Usability. Reusability. dependable functionality performance maintainable
- 5. Chapter 1 Introduction Software Engineering Software engineering is the process of developing, testing and deploying computer applications to solve real-world problems by adhering to a set of engineering principles and best practices. Software engineering also encompasses project management, quality assurance, and the use of various tools and methodologies to manage the complexity of large software projects, ensuring to complete on time, within budget, and to the required quality standards.
- 6. Importance of Software Engineering Ensures High-Quality Software: Through rigorous testing, quality assurance, and adherence to best practices, software engineering helps produce reliable, efficient, and maintainable software. Meets User and Stakeholder Needs: Requirements analysis and system design ensure that the software aligns with user expectations and business objectives, reducing misunderstandings and setting clear expectations. Facilitates Efficient Project Management: Structured methodologies and project management techniques help in organizing resources, timelines, and budgets, ensuring projects are completed on time and within budget. Supports Ongoing Maintenance and Adaptability: Continuous maintenance and documentation keep the software functional and relevant over time, allowing for updates and new features to be implemented effectively. Manages Complexity and Change: Configuration management and development methodologies provide tools and processes to handle the complexities and changes in software development, ensuring consistency and integrity throughout the software lifecycle.
- 7. Challenges facing software engineering Challenges facing software engineering including ■ Advancement in Rapid Technologies ■ Change in Culture ■ Cyber security ■ Artificial Intelligence and Automation ■ Lack of Alignment between the User and Sponsor Needs ■ Mismanaged Timelines ■ Quality Assurance ■ Delays in Release
- 8. Software Products Software engineers are concerned with developing software products. there are two kinds of software products: 1. Generic products stand-alone systems that are produced by a development organization and sold on the open market to any customer who is able to buy them. in generic products, the organization that develops the software controls the software specification. 2. Customized products: are systems that are commissioned by a particular customer. A software contractor develops the software, especially for that customer. the specification is usually developed and controlled by the organization that
- 9. Fundamental Software Engineering activities There are four fundamental activities that are common to all software processes. These activities are: Software specifications, where customers and engineers define the software that is to be produced and the constraints on its operation. Software development, where the software is designed and programmed. Software validation, where the software is checked to ensure that it is what the customer requires. Software evolution, where the software is modified to reflect changing customer and market requirements.
- 10. The Software Development Life Cycle (SDLC) ■ The Software Development Life Cycle (SDLC) is a structured process used by software engineers and developers to design, develop, test, and maintain high-quality software. It provides a systematic approach to software development through a series of well-defined phases include: 1. Planning: Define the scope and purpose of the project. Identify resources, timelines, and potential risks. Conduct feasibility studies to ensure the project is viable.
- 11. Cont... 2. Requirements Analysis: Gather and document detailed requirements from stakeholders. Create a requirements specification document that outlines functional and non-functional requirements. Validate and manage requirements to ensure they meet stakeholders' needs. 3. Design Create architectural designs and system models. Develop detailed design specifications for system components, including data models, user interfaces, and system interfaces. Use design patterns and best practices to ensure scalability and maintainability.
- 12. Cont… 4. Implementation (Coding): Write code based on the design specifications. Use appropriate programming languages and tools. Follow coding standards and guidelines to ensure code quality. 5. Testing: Perform various testing activities, including unit testing, integration testing, system testing, and acceptance testing. Identify and fix defects to ensure the software meets quality standards. Conduct performance and security testing as needed.
- 13. Cont… 6. Deployment: Prepare the software for release, including packaging and distribution. Deploy the software to the production environment. Provide training and documentation for users and support staff. 7. Maintenance: Provide ongoing support and maintenance for the software. Address any issues, bugs, or enhancements identified after deployment. Implement updates and upgrades to keep the software current and secure.
- 14. Professional Software Development Adherence to Best Practices and Standards Use of Development Methodologies Emphasis on Quality Assurance Effective Project Management Collaboration and Communication Continuous Integration and Deployment (CI/CD) Maintenance and Support Ethics and Professionalism
- 15. Issues Affected Software Engineering 1. Heterogeneity Increasingly different types of Technology 2. Business and social change Incredibly quickly of new technologies become available. 3. Security and trust General risk of network reliability
- 16. Chapter 1 Introduction Software Engineering Diversity 1. Stand-lone applications run on a local computer, such as a PC. 2. Interactive transaction-based applications Execute on a remote computer and accessed by users from their own PCs 3. Embedded control systems software systems that control and manage hardware devices. 4. Batch processing systems business systems that are designed to process data in large batches. 7 16
- 17. Cont…. 5. Entertainment systems for personal use and which are intended to entertain the user eg games 6. modeling and simulation Systems Developed by scientists and engineers to model physical processes or situations. 7. Data collection systems collect data from their environment using a set of sensors 8. Systems of systems composed of a number of other software systems.
- 18. Software Engineering Ethics Software engineering ethics involves the application of moral principles and professional standards to the practice of software engineering. It ensures that software engineers act responsibly and ethically in their professional activities, considering the impact of their work on society, users, and stakeholders. Software engineers must behave in an honestly, ethically and responsible way. Ethical behavior is more than simply upholding the law but involves following a set of principles that are morally correct. 18
- 19. Issues of Professional Responsibility Confidentiality Engineers should normally respect the confidentiality of their employers or clients irrespective of whether or not a formal confidentiality agreement has been signed. Competence Engineers should not misrepresent their level of competence. Intellectual property rights Engineers should be aware of local laws governing the use of intellectual property such as patents, copyright, etc. They should be careful to ensure that the intellectual property of employers and clients is protected. Computer misuse Software engineers should not use their technical skills to misuse other people’s computers. 19
- 20. THANK YOU!