Technical Requirements

The Solution

This section will contain functionalities and features of the solution. The proponent will basically describe their solution, its features, what it can do for the buyer and how best it fits the given description. For example, if a proposal is for a CMS, the basic functionalities must be mentioned like the extensions ecosystem, pages and categories management, the file/media manager, drag and drop editor, granular permissions and the search features. See how Drupal has showcased its features.

The government agencies usually prefer solutions that:

  • Are modular, extensible and portable;
  • These modules have a high degree of cohesion such that each module deals with a separate task, being tightly integrated at the same time;
  • Has been developed in a centralized architecture with large number of concurrent users handling;
  • Are upgradeable, configurable and easily maintainable;
  • Can scale depending on the load, the application demand and the number of sites;
  • Can support all the major web browsers e.g. Chrome & Edge, Firefox, Safari etc;
  • Are based on Cloud i.e. Saas. This helps reduce long-term maintenance work and costs related to application upgrades, security patches, component updates, and server-related updates and upgrades;
  • Must provide the deliverables in a way that respect user’s dignity and independence and in a manner that complies with Web Content Accessibility Guidelines (WCAG 2.0) Level AA standards. Since public is the main outside user of the solution its pertinent to accommodate all kinds of users including the ones with disabilities;
  • Work properly on mobile devices since search engines prioritize the sites that are mobile-compatible, making it increasingly difficult to find non-mobile sites;
  • RBAC ability to add, remove and manage site, manage global configurations, and open support tickets;
  • have the ability to produce reports and metrics that will be used to measure research performance based on various data. In addition, the solution should be able to integrate with business intelligence tools like PowerBI;
  • utilizes AI in the proposed solution. (ex. chatbots, predictive analytics or integration with other AI products).

Architecture Diagrams

Humans are a species of visual imagination. Diagrams are used to better understand the architecture and the solution stack of a proposed solution.

Technology Roadmap

The buyers are also interested in the solution’s technology roadmap. They want to know if it’s a viable project, one that will sustain their needs in the next 5 to 10 years and also what’s next for the project in terms of features and functionalities. See how Joomla has released their development roadmap.

User community

The purpose for mentioning user community is similar to the technology roadmap. The project backed by a user community is continuously upgraded, fixed and debugged. It is also the most innovative one, as many developers are working on it in a collaborative environment, it generates new ideas and hence is a source of latest developments. See how Tiki Wiki CMS Groupware Tiki Wiki CMS Groupware runs its community.