Component Name (with link to the document) Description 1.5 Terms/Acronyms and Definitions <State any terms and its definition that are described in the functional specifications. Include any acronyms that are mentioned in the document.> Term/Acronym Definition Description 1.6 Risks and Assumptions <List any assumed factors and identified risks that could affect the functional design of the system. Included can be third-party or commercial components that will be used, issues around the operating environment, or any constraints.> System/ Solution Overview <Provide a short description of the software and solution being specified and its purpose, including relevant benefits, objectives, and goals.> 2.1 Context Diagram/ Interface Diagram/ Data Flow Diagram, Application Screen Flow, Sitemap, Process Flow <Provide any appropriate graphical representations that are relevant to the system and project such as a context/interface/data flow diagram, application screen flow, site map, or process flow. Add as many as needed.> 2.2 System Actors 2.2.1 User Roles and Responsibilities / Authority Requirements Frequency Security/Access, Features User/Role Example Additional Notes of Use Used <include the <include <describes <describe the features of <add any additional specified examples of real how often the system available for the notes or supporting user/role such people in the they use role and any documentation as as Purchasing role> the system. security/access permissions necessary> Manager, Dept State that should be stated> Admin, Faculty, Frequent, Student, etc> Occasional or Rare>
Component Name (with link to the document) Description 1.5 Terms/Acronyms and Definitions <State any terms and its definition that are described in the functional specifications. Include any acronyms that are mentioned in the document.> Term/Acronym Definition Description 1.6 Risks and Assumptions <List any assumed factors and identified risks that could affect the functional design of the system. Included can be third-party or commercial components that will be used, issues around the operating environment, or any constraints.> System/ Solution Overview <Provide a short description of the software and solution being specified and its purpose, including relevant benefits, objectives, and goals.> 2.1 Context Diagram/ Interface Diagram/ Data Flow Diagram, Application Screen Flow, Sitemap, Process Flow <Provide any appropriate graphical representations that are relevant to the system and project such as a context/interface/data flow diagram, application screen flow, site map, or process flow. Add as many as needed.> 2.2 System Actors 2.2.1 User Roles and Responsibilities / Authority Requirements User/Role Example Frequency of Use Security/Access, Features Used Additional Notes <include the specified user/role such as Purchasing Manager, Dept Admin, Faculty, Student, etc> <include examples of real people in the role> <describes how often they use the system. State Frequent, Occasional or Rare> <describe the features of the system available for the role and any security/access permissions that should be stated> <add any additional notes or supporting documentation as necessary>