Solution Requirements.
Solution requirements can be described as functional and non-functional.
Determine the functional requirements of the solution. These describe what the software solution should do. This involves specific details such as input required,
output developed and functions of the solution, including data manipulation and validation.
Determine the non-functional requirements. These describe the quality attributes of the solution, including usability, reliability, portability, robustness and
maintainability.
Use tools to assist in determining solution requirements, including context diagrams, data flow diagrams and use case diagrams
Solution constraints.
Solution constraints can be described as the conditions or limitations that must be considered when designing a solution.
Determine the constraints of the solution. These include economic (cost and time), technical (speed of processing, capacity, availability of equipment,
compatibility, security), social (level of expertise of users), legal (intellectual property, ownership of data, privacy of data), and usability (accessibility, usefulness,
ease of use).
Solution scope.
Solution scope describes the boundaries or parameters of the solution.
Identify what will be and/or what will not be addressed by the solution.
Skills for analysis stage.
Collect data using a range of techniques to determine and clarify user needs, solution requirements, constraints and scope.
Collect primary and secondary data and prepare data for identifying trends, patterns and relationships.
Critically analyse the sources of data and information to determine reliability, validity and relevance.
Draft and evaluate questions to critically analyse requirements, problems, needs or opportunities.
Develop strategies for asking follow-up questions to further clarify the data and information collected
