Group Project: Functional and Non-Functional System Requirements
Analysts must do a great deal of translation between the users description of new or updated application software and the detailed specifications for building that software. The Case Study provides descriptions from which your group may develop appropriate functional system requirements. You will not find explicit statements about non-functional requirements. Instead, your group must infer what the system should include. Focus on items related to hardware, software, security, and cost. You may leave some of these non-functional requirements somewhat open-ended and refine them later in the project as you gain a more complete understanding of the system.
To prepare for this assignment, meet and brainstorm ideas with your group members using your knowledge from previous courses. Decide whether to divide functional requirements among group members by subsystem, or to share equally across the system. Consider how group members will review the functional requirements and ensure that they are complete and consistent. Consider when and how the group will determine non-functional requirements.
As a group, compile and agree on the complete list of functional requirements. Define at least four modules (sub-systems) to organize the main functions of the system. Common modules include Financial (General Ledger, Accounts Payable, Accounts Receivable) Human Resources (Time Entry, Payroll, Benefits Administration, Position Management), and Manufacturing (Shop Floor Control, Quality Control, Bill of Materials, Inventory).
Define non-functional requirements for the technology. These requirements might include: cloud vs. on-premises, database, operating system, programming languages, computing hardware, network components, interface or integration requirements to other applications, and IT support staff estimates. Project the cost of building, implementing, and maintaining the system for the next 57 years.