---
title: "Discussion on \"Power Platform requirements: the non-functional ones decide the architecture\" | Hashnode"
description: "Discussion on \"Power Platform requirements: the non-functional ones decide the architecture\". Most Power Platform projects capture the functional requirements carefully and the non-functional ones barely at all, then discover at go-live that the solution does everything it was asked to do and still fails, because it cannot handle th"
url: "https://hashnode.com/posts/power-platform-requirements-the-non-functional-ones-decide-the-architecture/6a53c4737370acb71858f45c"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Power Platform requirements: the non-functional ones decide the architecture](https://sapotacorpvn.hashnode.dev/power-platform-requirements-the-non-functional-ones-decide-the-architecture?utm_source=hashnode&utm_medium=feed)

Most Power Platform projects capture the functional requirements carefully and the non-functional ones barely at all, then discover at go-live that the solution does everything it was asked to do and still fails, because it cannot handle th

Jul 12 · 6 min read · sapotacorpvn.hashnode.dev  
Read the article

-   [#power-platform](https://hashnode.com/tag/power-platform)
-   [#solution-architecture](https://hashnode.com/tag/solution-architecture)
-   [#requirements](https://hashnode.com/tag/requirements)
-   [#non-functional-requirements](https://hashnode.com/tag/non-functional-requirements)
-   [#dataverse](https://hashnode.com/tag/dataverse)

## Written by

[SapotaCorp](https://hashnode.com/@sapotacorpvn)

@sapotacorpvn · Hanoi, Vietnam

  
[View profile](https://hashnode.com/@sapotacorpvn)

## Responses

Markdown supported · ⌘↵ to post

No responses yet.