This is a continuation post on the Analysis and Development series, have a look at Part -1 of this post for a better understanding. After properly analyzing the existing system, we might be in a good position to start the development. Let’s see the list of things that should be followed while developing, If the development is started from the […]
While development is a small part of the software life cycle model it is merely an output of the analysis made from the existing system or new requirement.
When it comes to migrating from existing technologies, a thorough study has to be done on the legacy tool starting from how the controls are used, what are the actions frequently used, things which are available in source and not available in the destination, etc. Solutions for these scenarios must be in handy for saving time while developing. Once the clock starts there will not be any time to do the POC for the requirement.
If the application is going to be created from a new requirement, we can focus only on the Power Platform by analyzing the use cases of the requirement and a feasibility study should suffice for common scenarios like approval, functions, references, CRUD operations, integrations, performance, limitations has to be taken care.
Microsoft has Power Platform, a combination of four software PowerApps, Power Automate, Power BI and Virtual Agents, like the other BPM tools it is not only built for SharePoint it can work as a standalone app or it can be connected to numerous connectors from which it can store and retrieve data.