15 units · 73 lessons

Software Engineering

Software Engineering from the first idea to exam level: every lesson builds on the one before, with a worked example, a step-through diagram where it helps, a quick check and practice that adapts to what you know. Follows Pressman & Maxim, Software Engineering: A Practitioner's Approach, 8th ed..

Software Engineering at a glance

What does Software Engineering cover?

Software & Process Models, Agile, Scrum & XP, Requirements & User Stories, From Requirement to Release, Software Architecture, User Interface Design, Use-Case Diagrams, ER Diagrams, Class Diagrams, Sequence Diagrams, Sprint Planning & Monitoring, CI/CD & DevOps and Quality Assurance & Testing. It follows Pressman & Maxim, Software Engineering: A Practitioner's Approach, 8th ed..

How many lessons does the Software Engineering course on Studious have?

15 units and 73 lessons, from "Software engineering" to "The V-model: a test level for every phase". Each lesson has a worked example, a quick check and practice that adapts to what you know, and many have step-by-step diagrams.

Course outline

  1. Unit 1 · Week 1

    Background and introduction

    1. Software engineering
    2. The nature of software
    3. Software engineering and the process framework
    4. Umbrella activities
    5. Software myths
  2. Unit 2 · Weeks 1–2

    Software process models

    1. Software process models
    2. Waterfall and the V-model
    3. Incremental and prototyping models
    4. The Unified Process
    5. The spiral model and choosing a model
  3. Unit 3 · Week 3

    Introduction to agile models

    1. Agile development
    2. The Agile Manifesto
    3. Scrum: roles, events and artifacts
    4. A Scrum sprint, step by step
    5. Extreme Programming (XP)
  4. Unit 4 · Week 4

    Requirement engineering, user stories and acceptance criteria

    1. Requirements engineering
    2. Requirements engineering tasks
    3. Functional and non-functional requirements
    4. Writing user stories with INVEST
    5. Acceptance criteria: Given / When / Then
  5. Unit 5 · Weeks 5–6

    From requirement to release

    1. From an idea to a release
    2. Epics, stories, tasks and the product backlog
    3. Prioritising the backlog with MoSCoW
    4. Release planning, MVP and the definition of done
    5. The Definition of Done
  6. Unit 6 · Week 6

    Software architecture

    1. Software architecture
    2. Architectural styles
    3. Layered architecture
    4. Client–server architecture
    5. Pipe and filter
    6. MVC: model, view and controller
  7. Unit 7 · Week 7

    User interface design

    1. User interface design
    2. The golden rules of interface design
    3. Redesigning a login form
    4. Error messages and feedback
    5. The UI design process
  8. Unit 8 · Week 8

    Use-case diagrams

    1. Use-case diagrams
    2. Actors, use cases and the system boundary
    3. Include, extend and generalization
    4. Use-case descriptions
  9. Unit 9 · Weeks 9–10

    Entity relationship diagrams

    1. Entity relationship diagrams
    2. Entities, attributes and keys
    3. Relationships and cardinality
    4. From ER diagram to tables
  10. Unit 10 · Week 10

    Class diagrams

    1. Class diagrams
    2. Classes, attributes, operations and visibility
    3. Relationships and multiplicity
    4. Aggregation and composition
    5. Inheritance and dependency
  11. Unit 11 · Week 11

    Sequence diagrams

    1. Sequence diagrams: messages in order
    2. Lifelines and messages
    3. Drawing one: registering a course
    4. Combined fragments: alt, opt and loop
  12. Unit 12 · Week 12

    Sprint planning and monitoring

    1. Planning and tracking a sprint
    2. Story points and planning poker
    3. Velocity over several sprints
    4. Velocity, capacity and sprint planning
    5. Monitoring with burndown charts
    6. Task boards and burnup charts
  13. Unit 13 · Week 13

    CI/CD and DevOps

    1. Delivering software with CI/CD
    2. Continuous integration
    3. Continuous delivery, deployment and DevOps
    4. The DevOps loop
  14. Unit 14 · Week 14

    Software quality assurance

    1. Software quality
    2. Quality, SQA and reviews
    3. Formal technical reviews
    4. Verification and validation
    5. Writing test cases
  15. Unit 15 · Weeks 15–16

    Testing techniques and levels of testing

    1. Software testing
    2. Black-box testing: partitions and boundaries
    3. White-box testing and cyclomatic complexity
    4. Levels of testing
    5. The V-model: a test level for every phase

Study every lesson with diagrams, practice and Buddy, your AI tutor.

Start studying free