Skip to content

Commit d92d9a4

Browse files
authored
Merge pull request MicrosoftDocs#4423 from MicrosoftDocs/edit_2252133
edit for task 2252133
2 parents f08f99b + 6f043aa commit d92d9a4

12 files changed

+743
-736
lines changed

powerapps-docs/guidance/fusion-dev-ebook/01-what-is-fusion-dev-approach.md

Lines changed: 10 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: "Chapter 1: What is the fusion development approach? | Microsoft Docs"
2+
title: "1: What is the fusion development approach? | Microsoft Docs"
33
description: "Learn more about the fusion development approach to app building in Power Apps."
44
author: spboyer
55
ms.service: powerapps
@@ -13,35 +13,34 @@ ms.reviewer: kvivek
1313

1414
# Chapter 1: What is the fusion development approach?
1515

16-
Effective application development depends on accurate and efficient communication of business requirements, and ideas for addressing these requirements. Many software engineering strategies promote the concept of the end users of applications being highly involved throughout the lifetime of the development process. However, there is frequently a *glass wall* between the end users and the software creators. Both parties can see each other and talk through their perspectives of how a new system should work, but the terminology spoken by one party might be different from that understood by the other. The need to translate language and ideas into a grammar that all members involved in the development process can agree on is fundamental to success. Additionally, in a rapidly changing business environment, time is of the essence. Failure to be agile enough to exploit a narrow window of opportunity can be costly. By building Microsoft Power Apps you can create and deploy working solutions that meet users' needs very quickly.
16+
Effective application development depends on accurate and efficient communication of business requirements, and ideas for addressing these requirements. Many software engineering strategies promote the concept of the users of applications being highly involved throughout the lifetime of the development process. However, there's frequently a "glass wall" between the users and the software creators. Both parties can see each other and talk through their perspectives of how a new system should work, but the terminology used by one party might not be understood by the other. The need to translate language and ideas into a grammar that all members involved in the development process can agree on is fundamental to success. Additionally, in a rapidly changing business environment, time is of the essence. Failure to be agile enough to exploit a narrow window of opportunity can be costly. By using Power Apps, you can create and deploy working solutions that meet users' needs very quickly.
1717

18-
![Basic PowerApps app](media/image1.png)
18+
![Basic app created with Power Apps](media/image1.png)
1919

20-
Power Apps enables a business user to quickly innovate and experiment with ways to improve their business processes. Using Power Apps, *citizen developers* who understand the business requirements can quickly put together the basics of a solution, with the minimum of coding effort. A citizen developer uses the graphical tooling provided by Power Apps Studio to create the business user's interface to a new system and some elemental logic that describes the functionality---typically involving data entry forms, displays, and reports. It's relatively easy to generate a working app from the data connectors that are supplied with Power Apps. These connectors enable the user interface to connect to many data sources, such as Microsoft SQL Server, Microsoft SharePoint, Oracle, Microsoft Excel, Twitter, Microsoft Dynamics, and several hundred others.
20+
Power Apps enables a business user to quickly innovate and experiment with ways to improve their business processes. Using Power Apps, "citizen developers" who understand the business requirements can quickly put together the basics of a solution, with a minimum of coding effort. A citizen developer uses the graphical tooling provided by Power Apps Studio to create the business user's interface to a new system and some elemental logic that describes the functionality—typically involving data entry forms, displays, and reports. It's relatively easy to generate a working app from the data connectors that are supplied with Power Apps. These connectors enable the user interface to connect to many data sources, such as SQL Server, SharePoint, Oracle, Excel, Twitter, Dynamics, and several hundred others.
2121

2222
> [!NOTE]
23-
> For a full list of connectors, see [Connectors reference](/connectors/connector-reference/).
23+
> For a full list of connectors, go to [Connectors reference](/connectors/connector-reference/).
2424
25-
Many apps built like this may fulfill an immediate business need quickly and cheaply, but there will always be situations where more complexity is involved that cannot be satisfied in this way. For example, your organization might have existing systems and databases with which the app needs to interact, and for which no connector is currently available. There may be additional business logic that needs to be enforced to ensure that data remains consistent. An app might need to implement a complex, dynamic business flow. This is where *professional developers* come into play. After a citizen developer has produced the front-end prototype for a system, the professional developer can work with them to create any appropriate custom connectors that they may require. A custom connector doesn't just provide a path to a data source; a professional developer can create custom connectors that give access to other services, such as Azure Logic Apps, which in turn can invoke Azure Functions. Connectors such as these enable the citizen developer to incorporate complex business logic into their apps without requiring that they understand how it's implemented.
25+
Many apps built like this can fulfill an immediate business need quickly and cheaply, but there will always be more complex situations that can't be satisfied in this way. For example, your organization might have existing systems and databases with which the app needs to interact, and for which no connector is currently available. There might be additional business logic that needs to be enforced to ensure that data remains consistent. An app might need to implement a complex, dynamic business flow. This is where professional developers come into play. After a citizen developer has produced the front-end prototype for a system, the professional developer can work with them to create any appropriate custom connectors that they might require. A custom connector doesn't just provide a path to a data source; a professional developer can create custom connectors that give access to other services, such as Azure Logic Apps, which in turn can invoke Azure Functions. Connectors such as these enable the citizen developer to incorporate complex business logic into their apps without requiring that they understand how it's implemented.
2626

2727
![App with custom connector](media/image2.png)
2828

29-
A common use case for a custom connector is to enable a app to access other systems and services inside and outside of an organization. A professional developer can create a Web API that wraps the operations exposed by these systems and services, host the Web API as an Azure Web App, and then make this web app available to a custom connector through Azure API Management (APIM).
29+
A common use case for a custom connector is to enable an app to access other systems and services inside and outside of an organization. A professional developer can create a Web API that wraps the operations exposed by these systems and services, host the Web API as a web app, and then make this web app available to a custom connector through Azure API Management.
3030

3131
![Web API with custom connector](media/image3.png)
3232

3333
> [!NOTE]
34-
> Other parts of Microsoft Power Platform can benefit from a similar approach. For example, a citizen developer might implement business logic in a low code manner through Microsoft Power Automate and Robotic Process Automation, then utilize Web APIs to integrate other services into this logic. You can also build chatbots using Microsoft Power Virtual Agents that combine AI capabilities with data and services exposed through Web APIs.
34+
> Other parts of Microsoft Power Platform can benefit from a similar approach. For example, a citizen developer might implement business logic in a low-code manner through Power Automate and robotic process automation, then use Web APIs to integrate other services into this logic. You can also build chatbots by using Power Virtual Agents that combine AI capabilities with data and services exposed through web APIs.
3535
36-
Fusion development with Power Apps is about combining the worlds of the citizen developer, the professional developer, and the other parties instrumental in building and using applications to further the objectives of the business. A citizen developer can express the business need quickly by building an app, and work with a professional developer to *fill in the gaps*. End users can provide feedback on missing functionality and any changes required. The whole process is highly iterative, perhaps more so than many other Agile processes, with the velocity of possibly several iterations a day.
36+
Fusion development with Power Apps is about combining the worlds of the citizen developer, the professional developer, and the other parties instrumental in building and using applications to further the objectives of the business. A citizen developer can express the business need quickly by building an app, and work with a professional developer to "fill in the gaps." Users can provide feedback on missing functionality and any changes required. The whole process is highly iterative, perhaps more so than many other agile processes, with the velocity of possibly several iterations a day.
3737

3838
> [!NOTE]
3939
> Gartner describes *digital fusion teams* as "distributed and multidisciplinary digital business teams that blend technology and other types of ___domain expertise. At least 84% of companies and 59% of government entities have fusion teams." (Source: 2019 Gartner Digital Business Teams Survey)
4040
4141
![Fusion development process](media/image4.png)
4242

43-
44-
For a detailed introduction to the fusion development process, and how it can accelerate development times, see [Citizen developers use Microsoft Power Apps to build an intelligent launch assistant](https://aka.ms/AAbvfzj).
43+
For a detailed introduction to the fusion development process and how it can accelerate development times, go to [Citizen developers use Microsoft Power Apps to build an intelligent launch assistant](https://aka.ms/AAbvfzj).
4544

4645
> [!div class="step-by-step"]
4746
> [Previous](prereqs-setup.md)

0 commit comments

Comments
 (0)