Jahziah.
العربية

STUDY GUIDE · GKU 7

Ethical and professional practice study guide (Software Engineering)

This unit is about running a software project as a professional: how a team is organised and kept working together, how engineers write and speak so that the right people understand them, what the Software Engineering Code of Ethics asks when duty to an employer meets duty to the public, what the law says about code, licences and personal data, how a plan, a schedule and a risk register are built and corrected, how life-cycle models and configuration management keep change under control, and how continuous integration and delivery turn a commit into a safe release. The planning section is computational (critical path, PERT, risk exposure); the others are descriptive, and their worked examples are decisions: a scenario, the options, the deciding reasons. Life-cycle models, COCOMO and Git basics are taught in GKU 1, and earned value and risk exposure in GKU 2; this guide builds on them rather than repeating them.

Continue in the app

Structured by the official ETEC subject standard for this topic: every listed topic and learning outcome, with formulas, figures and worked examples. The full sections are available to members in the app.

SKU 7.1 · Software engineering project management

  1. Teamwork and collaboration

    How software teams are structured and assigned roles, how a team matures, why communication paths limit team size, and the practices and tools that let people collaborate on one code base.

  2. Communication and technical writing

    Who needs to hear what, and how: stakeholder analysis and communication plans, the documents a software project produces, the rules of clear technical writing, and the spoken forms — stand-ups, demos, status reports.

  3. Ethics and professional conduct

    The ACM/IEEE-CS Software Engineering Code of Ethics and Professional Practice — its eight principles and the rule that the public interest comes first — and a procedure for deciding what to do when duties conflict.

  4. Intellectual property, licences, privacy and professional credentials

    The legal side of professional conduct: who owns code, how open-source licences differ (permissive against copyleft), what privacy law asks of a design, and the difference between accreditation, certification and licensing.

  5. Project planning, scheduling and risk management

    The vocabulary of project management, the plan from work breakdown to schedule, the critical path method and PERT estimates, and the risk management cycle with a risk register — enough to build a plan and to adjust it when an activity slips.

  6. Life-cycle models in practice and configuration management

    Running a project under a plan-based, iterative or agile model — Scrum's roles, events and artefacts, Kanban, velocity-based release planning — and keeping every change under control with configuration management: items, baselines, change control, status accounting and audits.

  7. Delivery models and DevOps (CI/CD)

    How software reaches its users: continuous integration, continuous delivery and continuous deployment, the stages of a pipeline, release strategies (rolling, blue-green, canary, feature flags), hosting models, and the four DORA measures of delivery performance.

MORE SOFTWARE ENGINEERING GUIDES

All study guides

Read the full guide beside your practice questions.

Open the app