A good application for an IT invention starts with the technical problem, not with a description of the product. The question to answer first is what changes in the operation of the computing system: speed, robustness, accuracy, security, memory use, throughput, or the quality of signal processing.
The architecture is then broken down into features. What matters is not the names of the modules but how they interact, what data they receive, how they transform it, and why that leads to the technical effect.
The practical test is simple: if a feature cannot be verified against the implementation, the logs, the documentation or a test, it almost certainly needs to be reworked.