https://ansangah.github.io/en/tags/projectmanagement/ProjectManagementHugo Blox Builder (https://hugoblox.com)enFri, 17 Oct 2025 00:00:00 +0000https://ansangah.github.io/media/sharing.pnghttps://ansangah.github.io/en/tags/projectmanagement/https://ansangah.github.io/en/blog/subjects/se/Fri, 17 Oct 2025 00:00:00 +0000https://ansangah.github.io/en/blog/subjects/se/<h2 id="1-overview">1. Overview</h2> <ul> <li>Software engineering applies disciplined, systematic methods to build complex systems.</li> <li>Goals: deliver <strong>high-quality software</strong> on predictable cost/schedule while keeping maintenance and evolution in mind.</li> <li>Pillars: <strong>Process</strong>, <strong>Method</strong>, <strong>Tooling</strong>, and <strong>Quality</strong>.</li> </ul> <hr> <h2 id="2-software-development-life-cycle-sdlc">2. Software Development Life Cycle (SDLC)</h2> <h3 id="21-waterfall-requirements--design--implementation--verification--maintenance">2.1 Waterfall (Requirements → Design → Implementation → Verification → Maintenance)</h3> <ul> <li>Fully sequential. Works for contract-heavy or change-resistant projects.</li> <li>Pros: strong documentation, straightforward management.</li> <li>Cons: slow feedback, poor at absorbing requirement changes.</li> </ul> <h3 id="22-iterative--incremental">2.2 Iterative &amp; Incremental</h3> <ul> <li>Repeated cycles of design/build/test deliver small increments and expose risk early.</li> <li>Examples: Spiral model (risk-driven), RUP, incremental delivery.</li> </ul> <h3 id="23-agile">2.3 Agile</h3> <ul> <li>Emphasises customer collaboration and rapid iteration: <strong>Scrum</strong>, <strong>Kanban</strong>, etc.</li> <li>Each sprint covers planning → development → review → retrospective.</li> <li>Prioritises working software over exhaustive documents, yet minimal artefacts are still maintained.</li> </ul> <hr> <h2 id="3-requirements-engineering">3. Requirements Engineering</h2> <h3 id="31-types">3.1 Types</h3> <ul> <li><strong>Functional:</strong> behaviours and use cases the system must perform.</li> <li><strong>Non-functional:</strong> performance, security, availability, compliance—quality attributes.</li> <li><strong>Domain-specific:</strong> rules tied to particular industries or organisations.</li> </ul> <h3 id="32-elicitation-techniques">3.2 Elicitation Techniques</h3> <ul> <li>Interviews, workshops, surveys, observation, prototyping.</li> <li>Agile-friendly user stories (“As a … I want … so that …”) capture intent.</li> </ul> <h3 id="33-analysis--specification">3.3 Analysis &amp; Specification</h3> <ul> <li>Resolve conflicts, prioritise (MoSCoW, WSJF).</li> <li>Document with UML use-case diagrams, structured templates, and SRS documents.</li> <li>Govern changes via Change Control Boards and versioning.</li> </ul> <hr> <h2 id="4-system-and-software-design">4. System and Software Design</h2> <h3 id="41-architecture-design">4.1 Architecture Design</h3> <ul> <li>Define structures to satisfy quality attributes.</li> <li>Patterns: layered, client–server, microservices, event-driven.</li> <li>Styles: REST, SOA, pipe-and-filter.</li> <li>Artefacts: C4 model diagrams, Architecture Decision Records (ADRs).</li> </ul> <h3 id="42-detailed-design">4.2 Detailed Design</h3> <ul> <li>Specify modules, classes, interfaces, and data structures.</li> <li>UML diagrams (class, sequence, state, activity).</li> <li>Principles: SOLID, dependency injection, GoF patterns (strategy, observer, factory, etc.).</li> </ul> <h3 id="43-reuse">4.3 Reuse</h3> <ul> <li>Leverage libraries, components, frameworks.</li> <li>Product line engineering derives variants from a shared asset base.</li> </ul> <hr> <h2 id="5-project-planning-and-management">5. Project Planning and Management</h2> <h3 id="51-estimation">5.1 Estimation</h3> <ul> <li>Use COCOMO II, Function Points, Story Points.</li> <li>Management artefacts: WBS, Gantt charts, Critical Path Method.</li> </ul> <h3 id="52-risk-management">5.2 Risk Management</h3> <ul> <li>Identify → analyse (probability/impact) → mitigate/avoid/transfer/accept.</li> <li>Focus on staffing, schedule, and technical uncertainties.</li> </ul> <h3 id="53-configuration-management">5.3 Configuration Management</h3> <ul> <li>Track versions of code, docs, build artefacts with Git/SVN.</li> <li>Adopt branching strategies (Git Flow, trunk-based) and peer reviews.</li> </ul> <hr> <h2 id="6-implementation--quality-techniques">6. Implementation &amp; Quality Techniques</h2> <h3 id="61-coding-standards">6.1 Coding Standards</h3> <ul> <li>Naming conventions, style guides (PEP8, Google style).</li> <li>Automate quality via linters, formatters, static analyzers.</li> </ul> <h3 id="62-refactoring">6.2 Refactoring</h3> <ul> <li>Improve structure without changing behaviour. Remove smells (long method, large class, feature envy).</li> <li>Use CI pipelines and regression tests to ensure safety.</li> </ul> <h3 id="63-performance-tuning">6.3 Performance Tuning</h3> <ul> <li>Profile to locate bottlenecks. Apply caching, async processing, data-structure optimisations.</li> <li>Reference models include Amdahl’s and Little’s laws.</li> </ul> <hr> <h2 id="7-testing--qa">7. Testing &amp; QA</h2> <h3 id="71-test-levels">7.1 Test Levels</h3> <ul> <li><strong>Unit:</strong> functions/classes, often TDD.</li> <li><strong>Integration:</strong> interactions between components.</li> <li><strong>System:</strong> end-to-end functional/non-functional checks.</li> <li><strong>Acceptance:</strong> confirm user needs (UAT).</li> </ul> <h3 id="72-techniques">7.2 Techniques</h3> <ul> <li>White-box: path, branch coverage.</li> <li>Black-box: equivalence partitioning, boundary analysis.</li> <li>Static reviews: peer review, walkthrough, inspection.</li> </ul> <h3 id="73-automation--cicd">7.3 Automation &amp; CI/CD</h3> <ul> <li>Frameworks: JUnit, pytest, Cypress.</li> <li>CI tools: GitHub Actions, Jenkins for build/test/deploy automation.</li> <li>Track coverage and quality gates (e.g., SonarQube).</li> </ul> <hr> <h2 id="8-operations-and-maintenance">8. Operations and Maintenance</h2> <h3 id="81-maintenance-types">8.1 Maintenance Types</h3> <ul> <li><strong>Corrective:</strong> fix defects.</li> <li><strong>Adaptive:</strong> respond to environment changes.</li> <li><strong>Perfective:</strong> enhance performance/features.</li> <li><strong>Preventive:</strong> eliminate latent issues.</li> </ul> <h3 id="82-devops">8.2 DevOps</h3> <ul> <li>Integrates development and operations with CI/CD, monitoring, IaC.</li> <li>Tooling: Docker, Kubernetes, Terraform, Prometheus, Grafana.</li> <li>Close feedback loop via logs, APM, feature flags.</li> </ul> <hr> <h2 id="9-quality-models-and-standards">9. Quality Models and Standards</h2> <ul> <li><strong>ISO/IEC 25010:</strong> functionality, reliability, usability, efficiency, maintainability, portability, security, compatibility.</li> <li><strong>CMMI:</strong> organisational process maturity (levels 1–5).</li> <li><strong>ISO/IEC 12207:</strong> software life-cycle processes.</li> <li><strong>IEEE standards:</strong> templates for SRS (IEEE 830), test documentation (IEEE 829), etc.</li> </ul> <hr> <h2 id="10-tools-and-collaboration">10. Tools and Collaboration</h2> <ul> <li>Requirements tracking: Jira, Azure DevOps, Trello.</li> <li>Documentation: Confluence, Notion, MkDocs; diagrams with PlantUML, Mermaid.</li> <li>Code collaboration: GitHub, GitLab; adopt PR reviews, pair/mob programming.</li> <li>Metrics: defect density, MTBF, defect discovery rate, lead time.</li> </ul> <hr> <h2 id="11-ethics-and-professionalism">11. Ethics and Professionalism</h2> <ul> <li>Follow ACM/IEEE codes of ethics.</li> <li>Address privacy, accessibility, algorithmic fairness, licence compliance.</li> <li>Conduct postmortems and root-cause analyses to foster organisational learning.</li> </ul>