This document outlines the information to be provided in a Solution Design Document (SAD), Design Approach Document (DAD), Management Approach Document (MAD), and Preliminary Requirements List (PRL) to help a project team understand what the proposed solution is, how it will be designed and built, how the project will be managed, and the initial requirements. The SAD would provide details on the current and proposed systems, processes, impacts, and scenarios. The DAD describes the design approach and quality standards without being overly prescriptive. The MAD explains the project governance, stakeholder engagement, communication, reporting, roles and responsibilities, and risk management approach. The PRL contains initial feasibility requirements and foundational requirements with estimates
This document outlines the information to be provided in a Solution Design Document (SAD), Design Approach Document (DAD), Management Approach Document (MAD), and Preliminary Requirements List (PRL) to help a project team understand what the proposed solution is, how it will be designed and built, how the project will be managed, and the initial requirements. The SAD would provide details on the current and proposed systems, processes, impacts, and scenarios. The DAD describes the design approach and quality standards without being overly prescriptive. The MAD explains the project governance, stakeholder engagement, communication, reporting, roles and responsibilities, and risk management approach. The PRL contains initial feasibility requirements and foundational requirements with estimates
This document outlines the information to be provided in a Solution Design Document (SAD), Design Approach Document (DAD), Management Approach Document (MAD), and Preliminary Requirements List (PRL) to help a project team understand what the proposed solution is, how it will be designed and built, how the project will be managed, and the initial requirements. The SAD would provide details on the current and proposed systems, processes, impacts, and scenarios. The DAD describes the design approach and quality standards without being overly prescriptive. The MAD explains the project governance, stakeholder engagement, communication, reporting, roles and responsibilities, and risk management approach. The PRL contains initial feasibility requirements and foundational requirements with estimates
This document outlines the information to be provided in a Solution Design Document (SAD), Design Approach Document (DAD), Management Approach Document (MAD), and Preliminary Requirements List (PRL) to help a project team understand what the proposed solution is, how it will be designed and built, how the project will be managed, and the initial requirements. The SAD would provide details on the current and proposed systems, processes, impacts, and scenarios. The DAD describes the design approach and quality standards without being overly prescriptive. The MAD explains the project governance, stakeholder engagement, communication, reporting, roles and responsibilities, and risk management approach. The PRL contains initial feasibility requirements and foundational requirements with estimates
Contributes towards the project understanding the Solution ‘What’.
Some examples of content.
Current hardware (remain/replace)
Software Process context Operational/environment context Process scenarios External impacts Internal impacts The customers organisational impacts Staff training It should paint a picture that helps describes the As Is that will support the SDT in achieving the To Be. DAD Contributes to the project understanding the ‘How’ but with not too much detail that could be seen as instructional. More detail will emerge that is led to by the SDT. Quality standards and testing expectations Record keeping incl PM Platforms, Information Radiators Release intent Approach to work Tools to consider within approaches MAD Explains to the project how the project will be managed. Governance & review strategy Stakeholder analysis and engagement Internal/external communication strategy Tailored reporting Roles & responsibilities Approach to risk, change and escalations Milestones and objectives PRL The ‘To Do’ list of Requirements Feasibility, no more than 10. Not baselined or MoSCoWd in Feas Foundations. No more than 100. Baselined and MoSCoWd in Founds. Includes Acceptance Criteria Estimates Resources Status/SoP during ED