Democracy 2.0
C.U.P.I.D. Solution Architecture Methodology - 5 Stages
VoteMatrix has developed a unique solutions architecture, systems integration, and agile software development methodology designed to optimize the ROI of Microsoft Stack (Microsoft 365, Power Platform, MS Teams, and SharePoint) solution development and integration projects. CUPID is a prioritized approach to information technology projects with stages in this order: Configure; Upgrade; Prototype; Integrate; and Develop. Arranging the solution approach in this sequence is key to project success. In many cases, this methodology completely eliminates custom Development, resulting in no-code or low-code solutions.
​
Architects analyze business requirements to design and implement solutions using this method.
This saves time and money, ensuring every project is a success!
​​
Click each of the stages below or scroll down for details.
CONFIGURE > UPGRADE > PROTOTYPE > INTEGRATE > DEVELOP
​
CONFIGURE (1) Mandatory
​
Out of the box Configuration is the CUPID Methodology's primary focus. Microsoft 365, SharePoint, and other PaaS (Platform as a Service) projects are ideally suited for this architecture.
​
Platform systems empower advanced users (citizen developers) to build makeshift solutions that become unmaintainable or fail altogether. Configuring well-engineered, comprehensive, secure, and maintainable solutions requires extensive experience. Proper configuration requires a deep understanding of business requirements and how to solve them using the platform's vast feature set. An experienced solutions architect will consider the platform's underlying mechanisms, recent updates, and obscure quirks when designing system specifications.
​​
Solution architects utilizing this methodology should be highly experienced in proper Microsoft 365, Power Platform, OneDrive, and SharePoint (or equivalent platform) configuration, providing high quality and cost-effective solutions.
The CUPID Methodology's configuration first approach ensures cost savings in solution development and support in addition to reducing the cost and effort of future migrations and upgrades.​​
Cost: $ - Duration: 1 to 2 quarters for 2 phases C-P
UPGRADE (2) Typical
​
There are thousands of third-party COTS (Commercial off the Shelf), open source, AI, and vendor provided add-ins and upgrades for Microsoft 365, Teams, and Power platforms (or similar). These upgrades (widgets, plug-ins, apps, services, controls, containers, servers, tools, and add-ins) provide advanced features as well as a reduction in the cost of maintenance and operations. Cost of upgrades may be significant, so these products must pass a cost benefit analysis including licensing and maintenance before adding them to a solution.
​
Architects using this methodology must be familiar with these upgrades including Agentic and Generative AI products. With rapid changes in technology, the marketplace must be continually re-evaluated. Product comparisons and recommendations are refreshed for each new project.​
Cost: $$($) - Duration: 2 to 3 quarters for 3 phases C-U​-P
PROTOTYPE (3) Mandatory
​
Using a rapid prototyping approach uniquely suited to platform services (like Microsoft 365 and SharePoint), a working prototype can be created in days instead of the typical week or month long development cycles.
These prototypes are immediately used to facilitate business analysis, providing experiential context to requirements gathering sessions and acting as a jumping-off point towards defining a complete system.
This method prevents traditional disconnects between end users, SMEs, analysts, project managers, product owners, and developers, ensuring the solution is correct the first time. Platform prototypes also require fewer iterative development and release cycles (continuous delivery savings).
​​
The CUPID Rapid Prototyping step results in significant savings in budget, time, and future maintenance and operations (M&O) allocation.​ Prototyping occurs in every project with the final prototype becoming the live product, released after either a final data migration or reset. After release, a dev environment will be cloned for debugging and implementing additional features without impacting the production environment.
​
C-P, C-U​-P, C-P-I-D, C-U-P-I, C-P-D, C-P-I, C-U-P-D, C-U-P-I-D
​
Most platform projects involve integration, migration, or synchronization with an existing system. Using proper techniques and tools can shave weeks off an integration or migration project.
Delaying integration until after initial prototyping reduces development iteration requests which are infamous for altering requirements, bloating the budget, and delaying go-live. Fringe integrations may be deemed unnecessary after prototypes clarify business requirements. Once integration features become fixed requirements, integration specialists quickly validate compatibility before adding them to the prototypes. This step helps identify issues before they are baked into the solution. Test data migrations may be necessary during the prototyping phases, but full migrations will be performed immediately after integration and prior to production release. For large migrations, this will include delta migrations to minimize data transfer windows.
​
Timing this phase correctly saves resources typically spent redesigning integration affected features.​
Cost: $$$ - Duration: 3 to 4 quarters for 3 or 4 phases C-P-I, C-U-P-I
Custom development is a last resort. This phase will eat up a project's budget faster than any prior phase. However, coding is necessary when specific requirements cannot be met using existing solutions, systems, or configurations. Proper architecture of a custom feature is key to reducing the time to completion and ensuring optimal functionality. Many of the solutions VoteMatrix develops are reusable and some are open source which benefit from collaboration and reduced costs of future enhancements and maintenance.
​​
Minimizing scope for this phase produces better cost-effective solutions that are easier to maintain.​
Cost: $$$$$ - Duration: 4 - 8 quarters for 3 to 5 phases C-P-D, C-P-I-D, C-U-P-D, C-U-P-I-D