Software System Development Plan

From GM-RKB
Jump to navigation Jump to search

A Software System Development Plan is a system development plan that outlines how the [[software requirement\\s will be turned into working software system.

  • Context:
    • It can (typically) be created during the Software Development Planning Task.
    • It can (typically) cover: planning, ideation, development, documentation, deployment, launch, and maintenance details.
    • It can (typically) answer questions such as:
      • What technologies will be required?
      • Who will manage the project?
      • Which teams and resources will be involved?
      • Who are the key stakeholders?
      • What are the external dependencies?
      • What are the success criteria?
      • What are the timelines and how have they been estimated?
      • What are the estimated costs and what assumptions have been used to calculate them?
    • It can (often) be a part of Software Development Lifecycle (SDLC) Document.
    • It can be used as a guide for all stakeholders throughout the development process.
    • ...
  • Example(s):
    • the one for a banking software project, outlining specific functionalities, the timeline for development, and resource allocation.
    • the one for a social media app project, defining key features, stakeholders, and success criteria.
  • Counter-Example(s):
    • A Marketing Plan: This is a strategy for promoting and selling products or services, not a plan for software development.
    • A Project Charter: While this document defines the scope, objectives, and stakeholders of a project, it is more general and not specifically focused on software development.
  • See: Software Development, Software Development Lifecycle, Software Development Planning Task, Software Requirements Specification.


References

2022

  • https://www.softkraft.co/software-development-planning/
    • QUOTE: A software development plan outlines how the project requirements will be turned into working software. It covers planning, ideation, development, documentation, deployment, launch, and maintenance details.
    • To get started putting together a software development plan, you should answer questions such as:
      • What technologies will be required?
      • Who will manage the project?
      • Which teams and resources will be involved?
      • Who are the key stakeholders?
      • What are the external dependencies?
      • What are the success criteria?
      • What are the timelines and how have they been estimated?
      • What are the estimated costs and what assumptions have been used to calculate them?