System solution requirements analysis outlines the conditions and capabilities a system solution has to have in order to meet system solution needs, or solve a problem and provide clarity around the solution delivery needs. Furthermore, the analysis defines how the solution will solve the problem both functionally and technically. The system solution requirements must meet or support system project requirements and business objectives, in addition to meeting stakeholder objectives. When developing system solutions or solution concepts, stakeholders commonly focus first on identifying and writing software requirements and then tackle technical details. But doing that without really knowing which features or functions will be most valuable in meeting the business and stakeholder requirements means your team may end up building some cool stuff without actually solving business problems. An organization can’t be sure what capabilities will be truly valuable until the overarching system solution vision is clear. This vision precedes all system solution analysis, or is part of the analysis if it has not been clearly communicated by the organization. This is also true of an emerging technology assessment, and making sure that any emerging technologies have business value for the organization.
IT Architects provides a service to conduct a complete and robust system solution analysis or emerging technology assessment, and provide recommendations for suitable system and/or technology introductions. This may also include the introduction of bolt-on solutions, plugins, add-ons, and customized components. IT Architects uses a proven system solution requirements analysis framework, which also provides a framework for the assessment of emerging technologies, to break down the solution requirements into two different distinct categories of solution analysis: functional and non-functional requirements.
- Functional requirements define the specific behaviors, responses, information, rules, or operations of a system solution. They answer the following questions:
- What functions or functionality does the system solution support?
- What specific stakeholder activities must be supported or experiences realized by the system solution?
- What information or data needs to be managed?
- Under what circumstances do expected behaviours and responses happen (or not) in order to ensure the required results and outcome are achieved?
(Note, although functional requirements are usually specified in the context of software and technical system capabilities, manual solutions also have functional requirements.)
- Non-functional requirements specify the manner or the environment in which a system solution is intended to operate. They describe the qualities a system solution must possess and any supplemental expectations or conditions it must support. The following non-functional requirements
- Usability: How easy the solution must be to understand or figure out. Also known as User-Friendly.
- Reliability: To what extent users can rely on the solution to be accessible and work when needed, which is usually during and outside work hours (e.g. 24/7).
- Performance: How quickly and efficiently the solution works and how it responds to commands and requests for action.
- Security: The level of protection the system, data, and networks are expected to have in place.
- Design: The visual and “user-experience” elements expected from the solution.
- Accessibility: The support that must be provided for users with disabilities, including hearing or vision loss, typically in compliance with relevant regulations such as the Americans with Disabilities Act of 1990.
- Documentation: The type and extent of written documentation expected or needed. Today, chatbot and other artificial intelligence response is required to optimize system usability.
- Information capacity: Requirements for the amount of data or media to be stored, including the expected growth of the information over time, must be fulfilled.
- Information architecture: Any needs for the arrangement or organization of the information in the solution must be met (through reports, queries, and decision-support capabilities).
- Technical capabilities: What complementary technical capabilities stakeholders require of the system solution (e.g. BI & analytics, mobility, workflow, complex event processing, etc).
IT Architects is in the business of understanding system solution requirements and developing an awareness of emerging technologies, and provides a proven system solution requirements analysis framework and expertise to ensure your systems and technologies are compatible and integrated.
