Software Engineering: Components & Processes

• Software is more than just code; it's executable code serving a computational purpose.
• Software includes executable programming code, associated libraries, and documentation.
• A software product is software made for a specific requirement.

Software System Components

• Users add/request information
• Procedures are tasks performed by human components
• Information is meaningful, stored, and processed data
• Documents are manuals and data files that may not be stored electronically
• Hardware includes computers, networks, input devices, and output devices
• Software includes computer applications for recording, processing, and regulating information access

Software Engineering Process Steps

• Requirements: Identify what the software needs to do.
• System Analysis: Study feasibility and refine requirements.
• System Design: Plan architecture and components.
• Code Design: Define coding structure and logic.
• Testing: Identify and fix bugs to ensure quality.
• Deployment: Release the software for use.
• Maintenance: Fix issues and improve performance.
• Updates: Add new features and enhance security.

Engineering

• Engineering develops products based on scientific principles and methods.
• Engineering applies science and math to solve problems, using discoveries and innovations.
• Software engineering is an engineering branch for developing software products using scientific principles, methods, and procedures.
• The outcome of software engineering is an efficient and reliable software product.

Software Engineering Defined by IEEE

• The Institute of Electrical and Electronics Engineers (IEEE) defines software engineering as the application of a systematic, disciplined, quantifiable approach to the development, operation and maintenance of software.
• Software engineering uses engineering concepts to produce efficient, durable, scalable, in-budget, and on-time software products.

Software Paradigm

• Software paradigms include the methods and steps to design software.
• There are many software engineering paradigms.

Software Development Paradigm

• Software development is a broad concept encompassing all engineering principles applied to software development, involving systematic research and gathering requirements to build a reliable software product.
• Key stages of software development include requirements gathering, software design, and programming.

Software Design Paradigm

• Software design is a subset of software development, how it is structured, maintained, and coded..
• Key stages of software design include design, maintenance, and programming.

Programming Paradigm

• Programming focuses on coding, testing, and integrating software to ensure it functions as expected.
• Key stages of programming include coding, testing, and integration.

Need for Software Engineering

• Software engineering is essential due to rapid changes in user needs and the evolving environment.
• Without a structured engineering approach, software development would be inefficient, costly, and difficult to maintain.
• As software grows in complexity, a systematic engineering approach ensures manageability similar to constructing a building.
• Engineering principles make it easier to scale existing software.
• A structured approach optimizes costs.
• Software must continuously evolve based on changing environments and user needs, with engineering methods facilitating updates.
• A disciplined development process ensures high-quality software that meets user expectations.

Characteristics of Good Software

• A well-designed software product performs, adapts, and is maintained over time.

Operational Characteristics

• How well the software works in real-world conditions.
• Should be cost-effective and provide value for money
• Should be easy to use and navigate.
• Should run smoothly with minimal resource consumption.
• Should provide accurate and expected results.
• Should perform its intended tasks effectively.
• Should work reliably without frequent failures.
• Should protect user data from threats.
• Should prevent errors that could cause harm, especially in critical systems.

Transitional Characteristics

• How well software adapts to different environments
• Should work across different devices and operating systems
• Should integrate easily with other software
• Parts of the code should be reusable
• Should be easy to modify and extend for future needs

Maintenance Characteristics

• How easily the software can be updated and improved.
• Should be designed in small, independent parts for easier updates.
• Should be easy to fix bugs and improve functionality.
• Should support modifications and enhancements.
• Should handle an increasing number of users without performance issues.
• Software engineering creates high-quality, cost-effective, scalable, and maintainable software, meeting user needs and adapting to changes.
• Software is prone to failures, high costs, and inefficiencies without proper engineering.