Develop a requirements specification with a minimum of 20 requirements.

Project Part 2: Requirements Specification | Graded

Develop a requirements specification with a minimum of 20 requirements. Define in very clear, detailed terms what your system does. While your overview might describe a website as allowing users to log in, a requirements document would take this down to much more detail. For example, “A user is allowed three login attempts” or “customer information will be saved in a database for up to 10 years if no activity occurs on this account.” More importantly, you will want requirements that define your functionality, such as “a user can access their account balance through a summary page and a detailed account page.” You could then have follow-up requirements that explain what a summary and detailed account page mean. Note that requirements might be nested: one could depend on a master requirement. Requirements should be numbered and ideally categorized (e.g., functional/nonfunctional, by interface, by purpose, etc.)

Parameters

Two to three pages (minimum), APA, 12-point font, double spaced