Satisfy all user requirements

[RETprojects]

• UF-A: The end user should receive a list of recommended design patterns after submitting a software design problem in textual form. One of these patterns should be distinguished as “most recommended.”
• UF-B: The client wants three case studies which demonstrate that the system can correctly classify design patterns from textbooks like GoF. Each case study can recommend 30 or more patterns.
• UF-C: The client wants three case studies which demonstrate that the system can correctly classify design patterns from websites like sourcemaking.com. Each case study can recommend 30 or more patterns.
• UF-D: The client wants the system to have at least 100 design patterns (30 design patterns related to each case study).
• UF-E: The client wants to make a pattern collection/repository once at a time and store the patterns in a database. (Do not need to use crawler for each user submission.)
• UNP-A: The system must be easy to use for a wide variety of users, including students.
• UNP-B: When the user interacts with the system (such as via mouse click), it must respond within a reasonable amount of time.
• UNP-C: The system must be available for use at any time of day.
• UNE-A: The system must comply with local and national laws governing software systems.