Software Requirements Specification for Role-Based Access System Version 1.0 Prepared by Group Name: Group 6 Roger Shealy shealyrd@email.uscupstate.edu Ryan Praytor praytorr@email.uscupstate.edu Bryan Poole poolebm@email.uscupstate.edu Josh Powers Powersi2@email.upscupstate.ed u Instructor; Dr. Amanda Schwartz Course; Software Engineering Date: 9/26/14oftware Requirements Specification for 1.5 Document Conventions This document will follow the IEEE formatting guidelines.ecification for Page 8 Lab echnicia Security Paramedi Bus Companio Guard oc Driver Who has access to what systems?Software Requirements Spe Page 9 Chaplai nSoftware Requirements Specification for __ Page 14 3.2 Functional Requirements 3.2.1 Administrator/Manager 5 An administrator/manager will be able to login and add, remove, and transfer employees. 3.2.2 Non-administrator employees Non-administrator employees will be able to logon and be given a list of applications that they have access to. 3.2.3 Email The software will be able to send an automated email to new employees. 3.2.4 Database The software will be able to access and update a database of employees, 3.2.8 Logout There will be a logout button on the application screen for non-administrator employees and on the main page for administrators. Joyee b ¥o Charae/ manage ac on emer 1 e basi 9 nye e Couctom ow Car Be MANAGE >UHiCh dipglicah MY or 1s tis hoved-cooled inte lf C nv Geet sstom job rol matt coe oO Seren for crent ‘ < 3. Dot c i +> 46 GE Menh orved hore e how ore tt 4. the io roles ised wh Ye Table, | e ¥ j created itic WU \t ner nt a > [x tre system at \ + She hom nh sooweatine OF i &) Numer the screus hotsSoftware Requirements Specification for Page 15 3.3. Behaviour Requirements 3.3.1 Use Case View | ace Ay Administrator . ° View list of usable applications Non-administrator Employee unch out ). Pane Inf Fane oles 2. Custow yoo ° emyplvy ee b x 3 pranage on empl OY eisSoftware Requirements Specification for 3.3.2. Database Layout » Fname Oe ($0 Posten) | | Employee App3 ] 1 ; IsA ey Y Position (Appt0) i pe As App6 oe cnt App9 App7 (Gesevb)_| Custom |_| oe a ero Apps) ( (Appt pee “App2>) aes) Ph. hey Whe at will oe "| 40 Non-functional Requireme' 4.1 Performance Requirements The system should be able to be accessed quickly and smoothly so as to not impede any tasks that the employee needs to complete. The program will need to be able to access the database andSoftware Requirements Specification for ~ List out deteile of cack applicstion ~ CAP Wolloolt - pplrectian ved Priowrily im the ER Lr patieek diagrosio aad reelSoftware Requirements Specifteation for