Skip to main content
CBE Nexus · Undergraduate Software Engineering

Chapter 1: Introduction to Software Engineering

Comprehensive undergraduate introduction to software engineering: software systems, engineering principles, lifecycle models, professional practice, software quality, ethics, teamwork and maintenance.

Back to Software Engineering course guide

Chapter overview and learning outcomes

This chapter develops foundational undergraduate knowledge in introduction to software engineering, connecting theory with practical software engineering decisions. It is designed for active study: read each section, work through the examples, draw the diagrams from memory and complete the revision questions.

1. Meaning, scope and nature of software engineering

Software engineering is the disciplined application of engineering principles to the specification, design, construction, testing, deployment, operation and evolution of software-intensive systems. It is concerned not only with writing code but with delivering systems that satisfy stakeholder needs within constraints of cost, time, safety, security, usability and maintainability. Software includes executable programs, configuration, data, documentation, deployment scripts and operational procedures. A system may also depend on people, devices, networks and external services. Engineering practice therefore considers the whole socio-technical environment in which software is used. The term became prominent as software projects grew in size and complexity and organisations experienced failures caused by unclear requirements, unreliable estimates, poor coordination and inadequate testing. The engineering response is to make decisions explicit, use repeatable methods, manage uncertainty and verify that the delivered product is fit for purpose.

Engineering application and analysis

Apply this concept to a realistic software project. Identify the actors, inputs, outputs, constraints, dependencies and failure conditions. Explain why the selected method is appropriate, what assumptions it makes, and how its success could be evaluated. Compare at least one alternative and discuss the consequences for maintainability, reliability, security, accessibility, performance and cost. Distinguish evidence from opinion, and state what additional information would be needed before making a production decision.

Worked study activity

Construct a small example, annotate each step, and test both an ordinary case and a boundary case. Record the expected result before running the test, compare the observed result, investigate any difference, and explain the lesson. Where a design choice is involved, write down the trade-off and identify who is affected by it.

2. Software products, systems and stakeholders

Software products may be generic products developed for a market or bespoke systems commissioned for a particular organisation. Generic products serve a broad customer base and require product management to balance competing needs. Bespoke products are tailored to a client, but still need clear acceptance criteria and change control. A software system may contain application code, databases, interfaces, APIs, hardware dependencies and operational services. Stakeholders include users, customers, sponsors, developers, testers, operators, regulators, suppliers and people indirectly affected by the system. These groups may have different priorities: users value usability, operators value observability, managers value delivery predictability, and regulators may require auditability. Stakeholder analysis identifies influence, interest, needs and potential conflicts. A responsible engineer does not assume that the person paying for a system represents every person affected by it.

Engineering application and analysis

Apply this concept to a realistic software project. Identify the actors, inputs, outputs, constraints, dependencies and failure conditions. Explain why the selected method is appropriate, what assumptions it makes, and how its success could be evaluated. Compare at least one alternative and discuss the consequences for maintainability, reliability, security, accessibility, performance and cost. Distinguish evidence from opinion, and state what additional information would be needed before making a production decision.

Worked study activity

Construct a small example, annotate each step, and test both an ordinary case and a boundary case. Record the expected result before running the test, compare the observed result, investigate any difference, and explain the lesson. Where a design choice is involved, write down the trade-off and identify who is affected by it.

3. Software engineering principles and professional mindset

Core principles include abstraction, modularity, separation of concerns, information hiding, simplicity, consistency, reuse, traceability and continuous verification. Abstraction focuses attention on essential properties while hiding irrelevant detail. Modularity divides a system into components with defined responsibilities and interfaces. Separation of concerns keeps unrelated responsibilities apart. Information hiding limits dependencies on internal implementation. Simplicity reduces unnecessary complexity, but should not remove essential safeguards. Reuse can reduce duplicated effort when the reused component is suitable, maintained and properly licensed. Traceability links requirements to design, implementation and tests. Engineering judgement balances these principles in context; none is a universal rule that automatically guarantees success.

Engineering application and analysis

Apply this concept to a realistic software project. Identify the actors, inputs, outputs, constraints, dependencies and failure conditions. Explain why the selected method is appropriate, what assumptions it makes, and how its success could be evaluated. Compare at least one alternative and discuss the consequences for maintainability, reliability, security, accessibility, performance and cost. Distinguish evidence from opinion, and state what additional information would be needed before making a production decision.

Worked study activity

Construct a small example, annotate each step, and test both an ordinary case and a boundary case. Record the expected result before running the test, compare the observed result, investigate any difference, and explain the lesson. Where a design choice is involved, write down the trade-off and identify who is affected by it.

4. Software development lifecycle and process models

A software development lifecycle (SDLC) describes activities through which a system is conceived, built, evaluated, released and maintained. Common activities include feasibility analysis, requirements, design, implementation, testing, deployment and maintenance. A process model organises these activities. The waterfall model uses staged progression and can be useful where requirements and approvals are stable, but late feedback can make change expensive. Iterative development delivers repeated versions and uses feedback to refine understanding. Incremental development adds capability in manageable slices. The spiral model emphasises risk analysis in repeated cycles. Agile approaches prioritise collaboration, working software, adaptation and frequent feedback. DevOps connects development and operations through automation, shared responsibility and continuous improvement. Real projects often combine approaches rather than following a textbook model exactly.

Engineering application and analysis

Apply this concept to a realistic software project. Identify the actors, inputs, outputs, constraints, dependencies and failure conditions. Explain why the selected method is appropriate, what assumptions it makes, and how its success could be evaluated. Compare at least one alternative and discuss the consequences for maintainability, reliability, security, accessibility, performance and cost. Distinguish evidence from opinion, and state what additional information would be needed before making a production decision.

Worked study activity

Construct a small example, annotate each step, and test both an ordinary case and a boundary case. Record the expected result before running the test, compare the observed result, investigate any difference, and explain the lesson. Where a design choice is involved, write down the trade-off and identify who is affected by it.

5. Agile values, Scrum and Kanban

Agile is a family of approaches, not a single prescribed process. Its values emphasise individuals and interactions, working software, customer collaboration and responding to change while recognising the value of tools, documentation, contracts and plans. Scrum organises work into timeboxed sprints with defined accountabilities, events and artefacts. The Product Owner orders work to maximise value; the Scrum Master supports effective Scrum practice; Developers create a usable increment. Sprint planning establishes a goal and selected work; daily coordination helps inspect progress; reviews gather stakeholder feedback; retrospectives identify process improvements. Kanban visualises work, limits work in progress and manages flow. Agile practices do not remove the need for architecture, testing, documentation, security or governance.

Engineering application and analysis

Apply this concept to a realistic software project. Identify the actors, inputs, outputs, constraints, dependencies and failure conditions. Explain why the selected method is appropriate, what assumptions it makes, and how its success could be evaluated. Compare at least one alternative and discuss the consequences for maintainability, reliability, security, accessibility, performance and cost. Distinguish evidence from opinion, and state what additional information would be needed before making a production decision.

Worked study activity

Construct a small example, annotate each step, and test both an ordinary case and a boundary case. Record the expected result before running the test, compare the observed result, investigate any difference, and explain the lesson. Where a design choice is involved, write down the trade-off and identify who is affected by it.

6. Requirements, design, implementation and verification

Requirements describe capabilities, constraints and qualities expected from a system. They may be functional, such as submitting a payment, or non-functional, such as responding within an agreed time under a stated workload. Design translates requirements into architecture, components, data models and interfaces. Implementation turns design decisions into executable artefacts. Verification asks whether work products meet specified requirements; validation asks whether the resulting system solves the real problem for users. Reviews, static analysis, unit tests, integration tests, system tests and acceptance tests provide different forms of evidence. A successful process connects each important requirement to a design decision and one or more verification activities.

Engineering application and analysis

Apply this concept to a realistic software project. Identify the actors, inputs, outputs, constraints, dependencies and failure conditions. Explain why the selected method is appropriate, what assumptions it makes, and how its success could be evaluated. Compare at least one alternative and discuss the consequences for maintainability, reliability, security, accessibility, performance and cost. Distinguish evidence from opinion, and state what additional information would be needed before making a production decision.

Worked study activity

Construct a small example, annotate each step, and test both an ordinary case and a boundary case. Record the expected result before running the test, compare the observed result, investigate any difference, and explain the lesson. Where a design choice is involved, write down the trade-off and identify who is affected by it.

7. Software quality and quality models

Quality is multidimensional. Functional suitability concerns whether the system provides the required functions. Performance efficiency concerns response time and resource use. Compatibility concerns coexistence and interoperability. Usability concerns learnability and operation. Reliability concerns consistent operation under stated conditions. Security concerns protection of information and systems. Maintainability concerns how effectively the product can be analysed, changed and tested. Portability concerns adaptation to other environments. Quality attributes can conflict: stronger encryption may affect performance; high availability may increase cost; extensive customisation may reduce upgrade simplicity. Teams should define measurable quality objectives and prioritise them according to risk and stakeholder value.

Engineering application and analysis

Apply this concept to a realistic software project. Identify the actors, inputs, outputs, constraints, dependencies and failure conditions. Explain why the selected method is appropriate, what assumptions it makes, and how its success could be evaluated. Compare at least one alternative and discuss the consequences for maintainability, reliability, security, accessibility, performance and cost. Distinguish evidence from opinion, and state what additional information would be needed before making a production decision.

Worked study activity

Construct a small example, annotate each step, and test both an ordinary case and a boundary case. Record the expected result before running the test, compare the observed result, investigate any difference, and explain the lesson. Where a design choice is involved, write down the trade-off and identify who is affected by it.

8. Project constraints, estimation and risk

Software projects operate under constraints such as scope, time, budget, people, technology, regulation and quality. Estimation is uncertain because requirements, dependencies and technical complexity may be incompletely understood. Estimates should state assumptions and ranges rather than imply false precision. Decomposition breaks large work into smaller tasks; historical data and expert judgement can improve estimates. Risk is an uncertain event or condition that may affect objectives. A risk register records description, probability, impact, owner, response and review status. Responses include avoiding, reducing, transferring or accepting threats, and exploiting or enhancing opportunities. Risks should be reviewed throughout delivery rather than documented once and forgotten.

Engineering application and analysis

Apply this concept to a realistic software project. Identify the actors, inputs, outputs, constraints, dependencies and failure conditions. Explain why the selected method is appropriate, what assumptions it makes, and how its success could be evaluated. Compare at least one alternative and discuss the consequences for maintainability, reliability, security, accessibility, performance and cost. Distinguish evidence from opinion, and state what additional information would be needed before making a production decision.

Worked study activity

Construct a small example, annotate each step, and test both an ordinary case and a boundary case. Record the expected result before running the test, compare the observed result, investigate any difference, and explain the lesson. Where a design choice is involved, write down the trade-off and identify who is affected by it.

9. Teamwork, communication and configuration management

Software development is collaborative. Teams coordinate through planning, design discussions, code reviews, issue tracking, documentation and demonstrations. Effective communication records decisions, assumptions, responsibilities and unresolved questions. Configuration management identifies and controls versions of code, documents, test data, infrastructure definitions and releases. Version control records changes and supports branching, merging, review and rollback. A baseline is an agreed reference point against which changes can be assessed. Change control is not intended to prevent all change; it ensures that impacts on cost, schedule, interfaces, security and quality are understood before decisions are made.

Engineering application and analysis

Apply this concept to a realistic software project. Identify the actors, inputs, outputs, constraints, dependencies and failure conditions. Explain why the selected method is appropriate, what assumptions it makes, and how its success could be evaluated. Compare at least one alternative and discuss the consequences for maintainability, reliability, security, accessibility, performance and cost. Distinguish evidence from opinion, and state what additional information would be needed before making a production decision.

Worked study activity

Construct a small example, annotate each step, and test both an ordinary case and a boundary case. Record the expected result before running the test, compare the observed result, investigate any difference, and explain the lesson. Where a design choice is involved, write down the trade-off and identify who is affected by it.

10. Professional ethics, law, safety and social impact

Software engineers have responsibilities to the public, clients, employers, colleagues and the profession. Ethical practice includes honesty about capability and uncertainty, respect for privacy, protection of confidential information, avoidance of discrimination, responsible disclosure of vulnerabilities and refusal to misrepresent test results. Legal duties vary by jurisdiction and may cover data protection, intellectual property, accessibility, consumer protection, safety and sector regulation. A system can be technically correct yet harmful if it excludes users, exposes sensitive data or enables misuse. Engineers should assess foreseeable impacts, provide appropriate safeguards and escalate serious risks through legitimate channels.

Engineering application and analysis

Apply this concept to a realistic software project. Identify the actors, inputs, outputs, constraints, dependencies and failure conditions. Explain why the selected method is appropriate, what assumptions it makes, and how its success could be evaluated. Compare at least one alternative and discuss the consequences for maintainability, reliability, security, accessibility, performance and cost. Distinguish evidence from opinion, and state what additional information would be needed before making a production decision.

Worked study activity

Construct a small example, annotate each step, and test both an ordinary case and a boundary case. Record the expected result before running the test, compare the observed result, investigate any difference, and explain the lesson. Where a design choice is involved, write down the trade-off and identify who is affected by it.

11. Software maintenance, evolution and technical debt

Maintenance begins when software enters use and continues as needs and environments change. Corrective maintenance fixes defects; adaptive maintenance responds to environmental change; perfective maintenance improves functionality or performance; preventive maintenance reduces future problems. Technical debt is the future cost created by expedient design or implementation choices. Some debt is deliberate and justified, but hidden debt accumulates through duplication, obsolete dependencies, missing tests and undocumented assumptions. Sustainable systems require monitoring, backups, dependency updates, refactoring, support processes and a plan for eventual retirement or data migration.

Engineering application and analysis

Apply this concept to a realistic software project. Identify the actors, inputs, outputs, constraints, dependencies and failure conditions. Explain why the selected method is appropriate, what assumptions it makes, and how its success could be evaluated. Compare at least one alternative and discuss the consequences for maintainability, reliability, security, accessibility, performance and cost. Distinguish evidence from opinion, and state what additional information would be needed before making a production decision.

Worked study activity

Construct a small example, annotate each step, and test both an ordinary case and a boundary case. Record the expected result before running the test, compare the observed result, investigate any difference, and explain the lesson. Where a design choice is involved, write down the trade-off and identify who is affected by it.

Figure 1. Software lifecycle
Discover needs and feasibility→Specify requirements→Design and implement→Verify and validate→Deploy, operate and evolve

Conceptual learning diagram; adapt it to the system or example being studied.

Figure 2. Quality attribute trade-offs
Stakeholder goals→Measurable quality scenarios→Architectural decisions→Verification evidence

Conceptual learning diagram; adapt it to the system or example being studied.

Figure 3. Risk management loop
Identify uncertainty→Estimate likelihood and impact→Plan response and owner→Monitor and review

Conceptual learning diagram; adapt it to the system or example being studied.

Practical laboratory / project activity

  1. Choose a bounded problem relevant to this chapter and describe the intended users and context.
  2. Write down assumptions, constraints, inputs, outputs and measurable success criteria.
  3. Develop a small prototype, model, algorithm, specification or test artefact.
  4. Use version control and document tools, versions and important decisions.
  5. Test normal, boundary and failure conditions; retain reproducible evidence.
  6. Review the result for usability, accessibility, security, reliability and maintainability.
  7. Submit a concise report explaining the method, findings, limitations and next steps.

Only test systems and datasets for which you have permission. Protect personal information and follow institutional academic-integrity and laboratory rules.

Worked reasoning and self-assessment

Begin with a precise problem statement. Separate known facts from assumptions. Identify the relevant concepts and choose a method that fits the problem constraints. Work through a small example manually, then verify the result using a suitable tool or test. Explain why the approach works, where it may fail, and what evidence would be needed to trust it in a larger system. For a design decision, state the alternatives and the trade-offs rather than presenting one choice as universally best.

Examination and revision questions

Attempt each question before opening the answer guidance. Use examples, diagrams and precise definitions in longer responses.

  1. Define software engineering.

    Show answer guidance

    The disciplined application of engineering principles to specify, design, build, test, deploy, operate and evolve software systems.

  2. Differentiate software engineering from programming.

    Show answer guidance

    Programming implements instructions; software engineering covers the broader lifecycle, quality, teamwork, risk and operational concerns.

  3. Name four software stakeholders.

    Show answer guidance

    Examples include users, customers, sponsors, developers, testers, operators and regulators.

  4. What is abstraction?

    Show answer guidance

    Representing essential properties while hiding irrelevant implementation detail.

  5. Differentiate verification and validation.

    Show answer guidance

    Verification checks conformance to specification; validation checks whether the system meets real stakeholder needs.

  6. Name three software lifecycle models.

    Show answer guidance

    Waterfall, iterative, incremental, spiral and agile approaches.

  7. What is technical debt?

    Show answer guidance

    Future cost created by expedient choices or accumulated design and maintenance weaknesses.

  8. Name four software quality attributes.

    Show answer guidance

    Reliability, security, usability, performance efficiency, maintainability and portability.

  9. What is configuration management?

    Show answer guidance

    Identifying and controlling versions and changes to software work products and environments.

  10. What is a risk register?

    Show answer guidance

    A record of risks, likelihood, impact, owners, responses and review status.

  11. What is a software baseline?

    Show answer guidance

    An agreed reference version used to assess and control changes.

  12. Why is stakeholder analysis important?

    Show answer guidance

    It reveals differing goals, influence, constraints and people affected by the system.

  13. Name two forms of software maintenance.

    Show answer guidance

    Corrective, adaptive, perfective and preventive maintenance.

  14. What is the purpose of a retrospective?

    Show answer guidance

    To inspect team processes and agree improvements for subsequent work.

  15. State two ethical responsibilities of software engineers.

    Show answer guidance

    Protect privacy and safety, be honest about limitations, respect intellectual property and disclose risks responsibly.

Revision checklist

Further reading and academic practice

Use current university textbooks, peer-reviewed software engineering research, recognised standards and official technical documentation. Verify edition, version, publication date and applicability before citing a source. Cite quotations, data, diagrams, software and ideas according to your institution's required referencing style. Do not invent references, results or test evidence. Compare sources critically and note where professional guidance differs by context or jurisdiction.

Academic note: These notes are an educational study resource, not a substitute for your institution's current course outline, assessment brief, professional standards or supervisor guidance. The course guide is an illustrative international framework.

Return to the complete Software Engineering course guide

Official Education References

Use these official organisations for curriculum guidance, examinations and further learning information.