Software Requirements Specification Global Alert Resolution
Contents
1. LED Electronic Messaging Systems Systems The figure above provides a high level vision of the GARNET system The vision includes the idea of having multiple mechanisms available to create and activate alert notifications Some sample creation mechanisms include computers with network access phones and even wireless devices such as a Personal Digital Assistants PDAs Software Requirements Specification for GARNET Page 3 Once an authorized person creates an alert the GARNET system is responsible for determining whom to notify and how to contact the affected people There are numerous potential notification mediums that could be integrated including computer desktops E mail messages pagers and phones The personal computer provides an excellent way to contact people quickly One of the key benefits of notifying people via their desktops 1s the ability to require a person to acknowledge the alert When a critical alert is received a window will pop up in front of all the other windows on the user s desktop requiring a user to minimize or close the window in order to continue working The GARNET infrastructure will be utilize the strengths of existing alert systems augmented by desktop computer alerts By using multiple alerting mechanisms GARNET can contact people including the hearing and sight impaired at their computers as well as within meeting rooms bathrooms and halls An IT based alerting system provides these benefits2. be in order for it to be archived REQ 0108140 The System shall allow the addition of users from the x 500 directory REQ 0108150 The system shall include the last name first name middle initial e mail address building organizational code mail code and uniquelD from the x 500 directory REQ 0108160 The system shall update the last name first name middle initial e mail address building organizational code and mail code based on the uniquelD as changes are made to the x 500 directory REQ 0108170 The system shall assign users to required building groups based on their building assigned in the x 500 directory Software Requirements Specification for GARNET REQ 0108180 The system shall update building and code lists based on x 500 updates REQ 0108190 The administrator shall be able to based on the users code building or name ID Description Justification REQ 0108200 The system shall delete users that are no longer found in the x 500 directory REQ 0108210 The system shall create and update categories based on buildings found in x 500 3 9 Documentation and Help 3 9 1 High Level 13 Description Justification REQ 0109000 The system shall provide on line While a user is using the system they help shall be able to access help documentation via a system function REQ 0109010 The system shall provide a How to login How to manage your profile complete user manual How to create an al
3. e Makes use of infrastructures and systems already in place e g computer networks desktop computers e Provides multiple ways to create an alert and multiple mediums to distribute an alert No dependency on a single alert mechanism e Contacts more people including the disabled more quickly by using multiple alert mediums e Targets alerts based on criteria such as a specific building geography alert type and alert severity e Provides fine grained control to notify only those people affected by the alert as determined by subscriber profiles e Includes details regarding the nature of the alert and recommended actions instructions e Requires a small amount of resources to perform tasks such as backups system upgrades security audits etc 2 2 User Classes and Characteristics The system shall provide multiple system privileges Each user in the system can be granted privileges Note a user may belong to multiple user classes and therefore will be granted multiple sets of privileges For example a user may be granted alert creation privileges in addition to being able to subscribe to alerts Additionally for a smaller deployment of a GARNET system a single user may take on both system administrative duties such as system upgrades and security audits in addition to administrative tasks such as user account management GARNET will support the following types of user privileges e System Administrator A user who had been g
4. notification rules contained in his her user profile REQ 0103181 A user shall have the ability to send Reduces the need for tech support a test message to the notification mediums added to the user s profile Page 8 Software Requirements Specification for GARNET Page 9 ID Requirement Justification REQ 0103190 A user shall be able to add edit remove view E mail notification mediums from his her user profile REG 0109200 Reseved O ToS REQ 0103210 JA user profile shall contain user credentials including a first name last name middle initial password secret question secret answer and E mail address 0 REQ 0103211 A user profile shall contain user This user information allows notification information including organization rules to be set based on the person s code mail code facility building building organization code mail code 0 room phone number EQ REQ 0103220 JA user shall be able to change his her password contained in his her user credentials REQ 0103230 A user shall be able to set edit his her secret question and secret answer in his her user credentials REQ 0103240 REQ 0103250 3 4 Alert Creation Alert creation is a critical system function that particular users are granted privilege to perform The following outlines the requirements surrounding alert creation 3 4 1 High Level Requirement Justification 13 REQ 0104000 JAn authorized user shall be able to Hig
5. Page 19 4 System Nonfunctional Requirements 4 1 Performance Requirements The following is a list of minimal performance requirements of the prototype GARNET 2 0 system The purpose of specifying these requirements 1s to establish a baseline performance needed for an effective implementation of GARNET 4 1 1 GARNET 2 0 Description Justification ID REQ 0201000 The GARNET system shall not be Provide some time for maintenance This inoperable more than 8 hours per requirement may be difficult to prove we year satisfy this REQ 0201010 The GARNET system shall The upper bound is based on predicted accommodate up to 10 000 users storage capacity REQ 0201020 The GARNET system shall The upper bound is based on predicted accommodate up to 40 000 storage capacity notification clients regardless of medium REQ 0201030 The GARNET system shall be This upper bound is based on predicted capable of transmitting 50 alerts computing capacity simultaneously 4 2 Security Requirements This section details security functions and characteristics needed to maintain system integrity confidentiality and availability Many requirements listed here are derived from NPG 28010 1 4 2 1 High Level ID Description Justification REQ 0202000 Network access to the alert creationINPG2810 1 Section A 7 1 server shall be restricted to unauthorized machines REQ 0202010 System shall ensure that passwords NPG2810 1 Section A 6 3 7 are stored co
6. browsers needed platforms and web browsers PC Windows 2000 SP3 and XP SP2 IE 6 x and Netscape 7 0 Red Hat 8 0 Netscape 7 0 Mac OSX 10 2 x IE 5 2 CON 0101050 The minimum hardware This specifies minimum hardware needed requirements of the GARNET client jto implement a GARNET 2 0 desktop software for PC based clients are client on a PC CPU Intel Pentium 4 512MB RAM 80GB Harddisk CDRom drive CON 0101051 The minimum hardware This specifies minimum hardware needed requirements of the GARNET client to implement a GARNET 2 0 desktop software for MAC based clients are client on a Mac CPU__ 512MB RAM 80GB Harddisk CDRom drive CON 0101052 The minimum hardware This specifies minimum hardware needed requirements of the GARNET client jto implement a GARNET 2 0 desktop software for Unix based clients are client on a Unix machine CPU Intel Pentium 4 512MB RAM 80GB Harddisk CDRom drive ID Description Justification
7. contains information pertaining to the alert For example relevant to the alert weather com REQ 0104070 The user must supply a single alert An alert severity is critical information that severity should be available to alert recipients The designation of an alert severity provides information necessary to determine who should be notified and also relays the level of importance to the user Each alert will only have a single severity REQ 0104080 The user must supply one or more An alert category provides the information alert categories necessary to determine who should be notified Each alert with have one or more associated categories REQ 0104090 The user shall only be able to create Some users will have privilege to create an alert for categories severities thatian alert for a particular category and he she has privileges for severity level REQ 0104100 The user must review an alert prior An attempt to reduce errors during alert to submitting it creation REQ 0104110 The system shall store the alert The specifics of what the system needs to timestamp creator title description store associated with the alert for security URL category s and severity reasons and searches 3 5 Alert Notifications This section of requirements outlines details pertaining to capabilities the system provides associated with alert notifications A key goal of the system is to provide fine grained notification control so that onl
8. is an SMS SMS protocol which restricts the size of device the message received REG 010SI00 Reseved SOS sS REO 0103110 Reseed ToS REQ 0103120 JA user profile shall contain a Some users may need to be notified prior notification priority that determines lto other users For example a building the order in which users are FOM should be notified of emergencies notified before other building occupants and therefore will receive a high priority REQ 0103130 The system shall provide a Default out of the box system provides a notification priority NORMAL notification priority NORMAL REQ 0103140 The system shall provide a Default out of the box system provides a notification priority HIGH notification priority NORMAL REQ 0103160 JA user shall be able to Some rules in a user profile may be setup add edit remove view notification by an administrator and will not be able to rules that he she has privilege to be modified by anyone other than an change in his her user profile administrator Addressed in the administrative requirements REQ 0103170 JA user shall be able to view the In the case that some users should not categories and associated have an option to be subscribed to certain severities and notification mediums severities and categories that are required in his her user profile The user will not be able to remove these rules REQ 0103180 A user may optionally add additional notification mediums to the required
9. of the system 3 6 1 High Level Requirement ID REQ 0106000 JA user must successfully log in to the system to access alert search functionality REQ 0106010 The user shall be able to search through historical alerts that s he has privilege to view Justification Alert search is a privileged system function Initially users will have privilege to view any historical alert regardless of whether they received the original alert Once an alert is archived it is not longer normal means REQ 0106020 The system shall provide a means for a user to search alerts that have javailable to be searched through the not been archived 3 6 2 GARNET 2 0 1D REQ 0106030 Reserved A user shall be able to search for previously issued alerts based on a data time range category severity and title Requirement REQ 0106040 Justification Initially users will have privilege to view any historical alert regardless of whether they received the original alert Software Requirements Specification for GARNET 3 7 GARNET Desktop Client Page 14 The GARNET desktop client will be notification medium that runs on users desktop computers It will receive alerts from the GARNET system and make then available directly as a users desktop computer 3 7 1 High Level D Requirement REQ 0107000 JA user shall be able to manually start the GARNET desktop client on their desktop machine REQ 0107005 The GARNET deskt
10. sets uppercase letters lowercase letters numbers and special characters ID Description Justification 4 3 Fault Tolerance This section describes required system features to detect faults in an operational system and features necessary to maintain system availability in the event of the occurrence of such faults 4 3 1 GARNET 2 0 ID Description Justification e Pe er minimum detection time must be shall be detected within 1 minute _jestablished detected within 1 minute established a een oC minimum detection time must be detected within 1 minute established REQ 0203040 Recovery from single hardware A minimum recovery time must be system failures shall take less than jestablished 30 seconds REQ 0203050 Recovery from any single point of A minimum recovery time must be failure shall take less than 15 established minutes Software Requirements Specification for GARNET 4 4 Software Quality Attributes 4 4 1 High Level Description REQ 0204000 The system architecture shall be extensible to be able to support multiple methods to create an alert REQ 0204010 The system architecture shall be extensible to be able to issue notifications to multiple mediums REQ 0204020 The system architecture shall be designed to be scaleable and reliable ID REQ 0204030 with disabilities according to Section 508 of the Rehabilitation Act REQ 0204040 The GARNET computer desktop aan shall run on multiple pla
11. Software Requirements Specification For Global Alert Resolution NETwork GARNET Version 2 0 Prepared by NASA Goddard Space Flight Center Advanced Architectures and Automation Branch Code 588 Julie Breed Code 558 Branch Head Stephanie Nickens Code 588 GARNET ATR Corinne Irwin Code 585 GARNET System Architect December 21 2004 Software Requirements Specification for GARNET Page ti Table of Contents L Introduction srra E a a A a E E o I ra Sas TANO o Ta OTENE EEE A 1 1 1 PU DOSE ree eE E a E E S l 1 2 Intended Audience and Reading Suggestions 0 0 0 0 cceecessccceccceseessseeceeeeeaaeeeeecceseeeaaeeeeeeeeeeeas i 1 3 POKEC N IO Oena a E E E acd santo uaeaotaee aceon l 1 4 PO E O a a E a SCT eee EM Oe 2 1 5 RE E a E S S N N eer emer een rt ee 2 Zi Overall Descriptio M sssrin a a EASE SES 2 ZA Product FC AUILC Sasso ci ceactsaccteetGaciecss bocce N beak Shetinnute lanmabetanseanelandaeaeetes 2 Ded User Classes AIG Cdl AC OTIS UC Senier saat orale Goadedie cent te adh dedanadind Canculshavelen tonics utaemaendcantumeveale eas 3 3 System Functional Requiremenntls ssscccccccccsssssssssssscccccccsssssssscccccssccssssssssscccssssssssssssees 4 3 1 PISCE DSM 5558s hed Goa racrce eek a ea acca cated veaeieeoadae tans 4 3 2 EA ata ota ssa genet se ssc E E 6 3 3 User Profile Manageme ntsc situa ansrh E uhenlwacacnoseadueaa an cunieienash aves iatensudentodee 7 3 4 AEL AON 6c shir esst sharers a A lanl ets Jue oascMa
12. available to alert recipients to express the level of importance of the alert The designation of an alert severity provides information necessary to determine who should be notified A short descriptive name for the category that will be used to classify alerts The short name is used to classify alerts for SMS devices Outlines what the category includes and when how it should be used Example categories include weather IT Code 588 Security and Safety etc This person is the keeper of the category REQ 0101100 JAn alert category has a creation When the category was created time REQ 0101110 JAn alert severity has a name REQ 0101111 An alert severity has a short name REQ 0101120 JAn alert severity has a description REQ 0101130 JAn alert severity has a unique priority order The highest priority shall be 1 The system shall have a CRITICAL LIFE THREATENING severity priority 1 REQ 0101150 A short descriptive name for the severity that will be used to classify alerts The short name is used to classify alerts for SMS devices Outlines what the severity means and when how it should be used Example severities include Informational Warning Critical Life threatening This description should provide a clear description such that the severity ordering is obvious to the user This forces an ordering to the different severities Critical is higher priority than informational Level of importance S
13. ert Etc REQ 0109020 There shall be a GARNET desktop client user manual containing instructions for each platform REQ 0109030 The system shall have a security Outlines the technical defenses the plan system has to provide security in addition to procedures associated with keeping the system secure and audit plans REQ 0109040 The system shall have a system Outlines things such as how to perform administrators guide upgrades installation deployment etc REQ 0109050 The system shall have a system For ongoing maintenance and add on architecture and design guide functionality Explains how the system is extensible and how best to add new ways to create alerts and new notification medium support REQ 0109060 The system shall have an How to create edit remove user account Administrators user manual How to grant privileges How to manage subscription groups including alert categories How to reset user passwords Page 17 Software Requirements Specification for GARNET Page 18 3 10 Logging The following list of requirements describes the necessary capabilities of the logging system Logs are invaluable for assessing security effectiveness assessing system health and documenting user and system activities 3 10 1 High Level ID Description Justification REQ 0110000 Faults in the operation of the All fault must be accounted for system shall be logged at the time they were detected REQ 0110010 All system logs s
14. h level description of how a user create an alert and target the alert j creates an alert criteria including alert category and severity REQ 0104010 The system shall store details about We need a history of the alert created in each alert created the system for multiple reasons First for security purposes so that misuse of the system can be tracked and secondly so that users can search for historical alerts Software Requirements Specification for GARNET Page 10 3 4 2 GARNET 2 0 ID Requirement Justification REQ 0104020 Alert creation shall be accessible For the initial production release via a supported web browser over a GARNET will provide a web front end for secure socket alert creation REQ 0104030 The user must successfully log in to Only authorized users are allowed to the system and have the create alerts appropriate privileges to access alert creation REQ 0104040 The user must supply an alert title Some mediums the alert is issued to may only include the title rather than the full alert description Title should be short and relay the main idea of the alert in a short concise manner REQ 0104050 The user must supply an alert An alert description is critical information description that should be available to alert recipients Should include the complete details instructions related to the alert REQ 0104060 The user may optionally supply a__ Points the user to additional information URL that
15. hall be tamper We need to make sure we maintain log resistant integrity 3 10 2 GARNET 2 0 Description Justification Log entries shall contain a This is a list of minimal critical information timestamp a description and a for tracing severity level such as error warning info etc Events occurring as a result of user actions shall also contain the user s identifier R REQ 0110030 Any alteration of data through We should log changes to user profiles administrative functions shall be groups categories severities to create an R logged audit trail REQ 0110040 JAll failed login attempts shall be Required for security incident detection logged and response REQ 0110050 JAll alerts created shall be logged We need to keep an record of alerts REQ 0110070 JAll logs shall be archived weekly This will save space on the primary storage device RE If the log capacity has been We may need to occasionally rotate the reduced to 20 free space the logs when they overflow due to large system shall send an alert toa bursts in activity If the logs continually system administrator indicating the joverflow the log capacity should be logs need maintenance increased ID EQ 0110020 EQ 0110060 Only authorized No other users need to view the logs It administrators operators shall have keeps users from misusing the logs the ability to view logs through espionage Q 0110080 Software Requirements Specification for GARNET
16. ide to password to attempt logging into logon to the system he system REQ 0102040 JA user may have his her password Handles the case when a user forgets reset to a random password and E Jhis her password mailed to him her by using his her username and answering his her secret question correctly Software Requirements Specification for GARNET Page 7 ID Requirement Justification REQ 0102050 The system shall not grant access Security NPG2810 1 o a privileged system function to a user who has failed login five consecutive times using the same username five consecutive times 3 3 User Profile Management A user profile contains information to outline what type of alerts a user wishes to receive and through what media s he would like to receive them User profiles are a critical piece of the application because they allow the system to determine whom to notify with an alert The following set of requirements outline the capabilities the system will provide to a user to manager his her profile 3 3 1 High Level ID Requirement Justification REQ 0103000 JA user shall be required to havea Necessary otherwise a user would not be user profile able to receive any alerts REQ 0103010 JA user shall be required to log in to access his her user profile information REQ 0103020 JA user profile contains alert High level explanation of what is included subscriptions describing the type of jin a user profile alerts a user is inte
17. ion via E mail affected parties of an alert REQ 0105050 The system shall support issuing an Text messaging provides a easy way to alert notification to an SMS device notify affected parties of an alert such as alphanumeric pager or cell phone via an E mail interface REQ 0105060 The system shall support issuing an A desktop computer that is connected to alert notification to a GARNET a network provides a quick easy way to computer desktop client notify people of an alert It also provides a means for the client to have to recognize the alert REQ 0105070 The system shall issue a notification A key point to the system is quick to an affected party within 5 minutes notification The system needs to be able from when the alert was created to send out alert notifications as quickly as possible ID Requirement Justification REQ 0105080 The system shall support notifying Required by many firewall users via a GARNET desktop client implementations GARNET desktop client must have outgoing internet access on at least one undedicated TCP UDP port Software Requirements Specification for GARNET REQ 0105090 The system shall determine notification rules contained within user profiles Specifically the alert category and severity must match the category and severity of a rule contained in the user s profile in order for the user to be issued a notification s REQ 0105100 The system shall issue notifications based
18. n to controlling how an alert can be targeted to interested users only 3 8 1 High Level REQ 0108000 An authorized administrator shall be able to create edit remove user accounts and profiles REQ 0108010 JAn authorized administrator shall be able to create edit remove user alert subscriptions A user shall not be able to alter an administrator specified alert subscription REQ 0108020 JAn authorized user may grant privileges to a user 3 8 2 GARNET 2 0 ID Description Justification REQ 0108030 JAn authorized administrator may Details what is necessary to create a user create a user account with the account following data First name Last Name E mail address REQ 0108040 JAn authorized administrator may We don t want to permanently delete user mark a user account as inactive accounts but rather mark them as inactive for security purposes and historical alert REQ 0108045 JAn authorized administrator may activate a user account that was disabled inactive REQ 0108050 JAn authorized administrator may edit a user profile by modifying the following data first name last name middle initial e mail address organization code mail code facility building room required notification rules notification medium configurations and notification priority REQ 0108060 JAn authorized administrator may create edit remove alert categories REQ 0108070 JAn authorized administrator may reset a password for any user 13 De
19. nfidentially REQ 0202020 The system shall ensure the NPG2810 1 Section A 7 4 3 confidentiality and integrity of communication between the system and remote clients REQ 0202030 Security logs shall record security NPG2810 1 Section A 6 1 3 relevant events REQ 0202040 Critical system data modifications NPG2810 1 Section A 6 1 3 shall be recorded Software Requirements Specification for GARNET Page 20 REQ 0202050 The system shall prevent High level authentication requirement unauthorized users from accessing the system REQ 0202060 The system shall implement High level requirement for confidentiality controls to ensure the privacy of information and individuals are not compromised REQ 0202070 The system shall implement High level requirement for integrity controls to ensure that the authenticity of data is preserved ID Description Justification 4 2 2 GARNET 2 0 REQ 0202100 User secret answers shall be stored NPG2810 1 Section A 6 3 7 confidentially REQ 0202110 The system shall deter one or more Prevent DoS attacks users from successfully using a denial of service attack by flooding the system with new alert requests REQ 0202120 __ After five consecutive failed login NPG2810 1 Section A 6 4 2 attempts a user account shall be disabled Only a privileged administrator may reactivate a user account REQ 0202130 The system shall use the Data NGP2810 1 Section A 6 9 Encryption Standard DES to secu
20. nformation to all affected people in the case of an emergency such as a national security concern an intrusion or severe weather event The following is a list of high level goals of the GARENT alerting system e Rapidly distribute alerts with detailed information and instructions e Broadly distribute alerts to users regardless of physical location available technologies and personal physical disabilities Software Requirements Specification for GARNET Page 2 e Target the distribution of alerts to pertinent individuals preventing users from receiving irrelevant alerts e Provide high reliability e Function at low cost in terms of both funding and system resources 1 4 Project Scope The current project scope encompasses the functionality of GARNET for the initial rollout to GSFC s Greenbelt facility This document outlines high level requirements that are considered core and generic to the GARNET system Additionally the document specifies requirements for GARNET 2 0 In the case that a customer wishes to alter and or extend GARNET 2 0 an additional requirements document should be produced outlining the altered and or new functionality 1 5 References The GARNET Operational Concept Document OCD outlines how the GARNET system will operate The document describes high level user interactions and system behaviors 2 Overall Description 2 1 Product Features Issue Create Alert Notifications GARNET Web Phone
21. oftware Requirements Specification for GARNET Page 6 ID Requirement Justification REQ 0101180 The system shall have an INFORMATIONAL severity with priority 4 3 2 Login Login is one way in which the system takes security measures to control access to privileged system functions Login functionality is a high system priority A user must log in to the system to gain access to perform a privileged system function such as alert creation user profile changes etc Upon successful login the system will allow the user to perform system functions for which s he has privileges If a user is unable to successfully login the system will not allow the user to perform any system functions that require privileges 3 2 1 High Level Requirement Justification ID REQ 0102000 The system shall require a user to Expresses at a high level that a user successfully log in to the system and needs to log in to perform any system have appropriate privileges to unctions that require privilege Also perform alert creation view edit outlines at a high level what those profile and or search for historical functions include REQ 0102010 a privileged system function to a provide a method for user authentication user who has failed to be and system control over access to authenticated to perform the privileged functions 3 2 2 GARNET 2 0 Requirement Justification ID REQ 0102020 JA user shall supply a username and Explains what a user needs to prov
22. on the notification priority contained in each user profiler A user with notification priority HIGH will be issued notifications prior to a user with a notification priority of NORMAL REQ 0105110 The system shall determine the notification mediums to issue notifications to based on the notification media associated with the matching notification rule REQ 0105120 JA user shall not receive duplicate alerts on the same notification medium REQ 0105130 JAn alert issued via E mail will contain the alert title description URL if provided timestamp severity and category s A URL to the GARNET system to retrieve the full details about the alert will also be included D Requirement will contain the alert title timestamp REQ 0105140 JAn alert issued to an SMS device severity and category s Some amount of the description will be included up to the SMS limit REQ 0105141 The total number of characters for an alert sent to an SMS device will not exceed 140 characters including the e mail headers Page 12 Justification Matching alert characteristics to user notification recipients based on user profiles provides the mechanism to only contact the affected people or those whom would be interested in the alert FOMs and other emergency response personnel should be notified of an alert before all others Us the user notification rules to determine which medium s to issue the alert to In the case tha
23. op client shall be able to be configured to start automatically upon desktop startup boot REQ 0107010 JA user shall be able to specify their GARNET user login criteria to the client REQ 0107020 The GARNET computer desktop client shall require a user to acknowledge a critical alert that it received prior to resuming work on his her computer REQ 0107030 Alerts received via the GARNET desktop client that require acknowledgement shall not alter affect actively running programs and shall allow users to return to previous work after acknowledgement 3 7 2 GARNET 2 0 ID Requirement REQ 0107040 The system shall provide for password synchronization between the GARNET Server and the desktop client The system shall provide an automatic update capability to ease delivery of enhancements to the desktop client REQ 0107050 Justification When starting the desktop client the user can enter their GARNET username and password so that the desktop client can receive alerts for the specified user We need to make it clear that GARNET will not conflict with other running applications The other applications data will not be altered in any way when an alert is received Justification The user should not have to change his her password in two places Software Requirements Specification for GARNET Page 15 3 8 Administrative GARNET has several administrative functions that are necessary to manage users in additio
24. ple Priority level of an alert priority severity level of the alert 3 1 2 GARNET 2 0 ID Requirement Justification REQ 0101000 JAn alert contains a title Brief title for the alert that relays the main idea reason for the alert REQ 0101010 JAn alert contains a description An alert description is critical information that should be available to alert recipients REQ 0101020 JAn alert contains an optional URL to For example if a weather alert is being extra info and or details pertaining issued the creator may also provide a to the alert link to weather com REQ 0101030 JAn alert contains a creation A timestamp represents when an alert timestamp was received by the system to be sent to affected parties REQ 0101040 JAn alert contains a creator Identification criteria which specifies who created and submitted the alert to the system Software Requirements Specification for GARNET Requirement REQ 0101050 JAn alert contains at least one associated category REQ 0101060 JAn alert contains a severity REQ 0101070 JAn alert category has a name REQ 0101071 An alert category has a short name ID REQ 0101080 JAn alert category has a description REQ 0101090 JAn alert category has a point of contact including a name phone E mail Page 5 Justification An alert category provides the information necessary to determine who should be notified An alert severity is critical information that should be
25. ranted system administrator privileges shall be able to gain access to the server machine s to perform maintenance upgrades security audits GARNET desktop client installations etc e Administrator A user who has been granted administrative privileges shall be able to create edit remove user accounts create edit remove subscription groups grant user privileges and create edit remove alert categories and severities Software Requirements Specification for GARNET Page 4 e Alert Creator A user who has been granted alert creation privileges shall be able to create alerts for a specific alert category and severity A user may be granted privileges to create alerts for multiple category severity pairs e Alert Subscriber A user who has alert subscriber privileges can subscribe to receive alerts for alert categories severities for which s he has been granted access S he may also search for historical alerts by categories severities for which s he has been granted access 3 System Functional Requirements This section of the document outlines the functional requirements broken down by functional area 3 1 Alert Definition 3 1 1 High Level 13 Requirement Justification REQ 0101000 JAn alert contains information High level description of an alert Key explaining the details of alert points include details about the alert including information to target the Ability to target the alert to affected alert to affected people and the peo
26. re communications between the system and remote clients 13 Description Justification REQ 0202140 The system shall ensure users do NPG2810 1 Section A 6 3 3 not choose trivial passwords as defined in NPG2810 1 Section A 6 3 3 REQ 0202150 The system shall not display users INPG2810 1 Section A 6 3 8 password when typed REQ 0202160 Password changes shall be logged INPG2810 1 Section A 6 3 8 User ID and date time of changes made shall be recorded REQ 0202170 The system shall ensure a user NPG2810 1 Section A 6 3 9 changes his her password after the first login after a password reset REQ 0202180 The system shall ensure users read NPG2810 1 Section 4 10 and agree to usage terms specified in a warning banner upon logon Software Requirements Specification for GARNET Page 21 REQ 0202190 Successful and failed logons logoffs INPG2810 1 Section A 6 1 3 shall be recorded REQ 0202200 The system shall ensure that only NPG2810 1 Section A 6 1 5 authorized personnel shall shutdown the system REQ 0202210 The system shall remind users to NPG2810 1 Section A 6 2 4 change passwords at least every 90 days REQ 0202220 The system shall ensure that user NPG2810 1 Section A 6 2 4 accounts are suspended if passwords are not changed at least every 120 days REQ 0202230 User passwords shall be a NPG2810 1 Section A 6 3 2 minimum of eight characters containing at least one character each from at least three of the following
27. rested in being notified about and the mediums through which the user would like to be notified REQ 0103030 JA user profile contains login credentials REQ 0103040 JA user may only edit the information in his her profile that he she is permitted to change 3 3 2 GARNET 2 0 ID Requirement Justification REQ 0103060 JA user profile contains notification Outlines the categories of alerts a user rules A notification rule contains a wants to receive The system will use this category severity and one or more info to determine if an alert is relevant to notification mediums Software Requirements Specification for GARNET ID Requirement Justification REQ 0103070 JA user profile contains notification A notification medium is a tool that can be medium configurations used by the GARNET system to a contact a user with alert details A notification medium configuration supplies the information necessary to a specific medium in order for GARNET to be able to contact the user REQ 0103080 JAn E mail notification medium Information required for a user to receive configuration requires an E mail alerts via E mail address REQ 0103090 JA user profile may optionally include A user may wish to receive alerts at multiple E mail configurations multiple E mail accounts REQ 0103091 An E mail notification medium Many alphanumeric pagers and cell configuration allows a user to select phones use Small Message System whether the medium
28. scription Justification Software Requirements Specification for GARNET Description Justification ID The system will warn the administrator if an e mail informing the user of a reset password could ee not be sent successfully REQ 0108080 JAn authorized administrator shall be able to grant and revoke administrative and alert creation per categories severities privileges to any user REQ 0108090 JAn authorized administrator may Used to make it easy for an administrator create edit remove a subscription __ to create a user account and assign the group A subscription group has a_jalert categories they have privilege to name description and one or more Instead of assigning each individual related alert categories category the administrator will be able to assign by specific category and also assign a user to a subscription group s REQ 0108100 JAn authorized administrator may We need to decide if we are going to do assign a user to a subscription this May be useful to have for FOMs group s and the user will then have Directors of etc privilege to subscribe to all alert categories associated with the subscription group REQ 0108110 The system shall store a maximum of ten million alerts If there are more than ten million alerts stored a portion of the alerts shall be archived starting with the oldest ones first REQ 0108120 A system administrator shall be able to configure how old an alert must
29. t Rand sebban taeedda wet cada tant 9 3 5 Alere INO UTCAUONS 55 2552 2esnssSeqsnasvaes naan neatipasuacaenencen dou seenn acne anh uenectmacee cess donseennaceeseboemsedmaceencsbse 10 3 6 Alere SO Ar CMOS eaaa a e E E rE 13 3 7 CARNET DESKON CHEI co a seca a a vod E A 14 3 8 aaar NE E ED S R A rn I A E A A A E A A AE E rer E A E re 14 3 9 Docummenan on AnH eena aks let cuatianasetend ion send atuncaneeaeesaacetiaceeeseneloakacnsestoraresaneans 17 IAO LOSSE sss seerertee ta nare nine t et ee nent neni se su ee nite Seine emer Cnt trea rr nce Tey nine Metre ee There NTs 18 4 System Nonfunctional Requirements cccccccccssssssssssccccssssssssscscccccssssssssssscccssssesssssssees 19 4 1 Peri Ormance Regue men S san uaniat seats Giialanvebial be Cavamian deacons sual an Saher bondaddansint 19 4 2 DCC Ui REGU re MEN Sarani E E aden 19 4 3 Fault Tolerance ssion nE E E A 21 4 4 Software Quality AIDU 155 ss ecease stints onisnatunsrencdansnsteusiawansss e EE es 22 5 Oher ReguirementS ossessione e asa aee Eao ETARE RES 22 5 1 SV Stem C ONSE Sars E N a A a 22 Revision History Reason For Changes 72772003 _ Initial Release rf 2 6 2003 Integrated feedback from Stephanie Nickens LT 2 12 03 Integrated feedback from Julie Breed ree 12 21 2004 Update for Production version of GARNET Software Requirements Specification for GARNET Page 1 1 Introduction 1 1 Purpose The purpose of this document is to describe the functional and system req
30. t an alert is associated with multiple categories and a single client user matches multiple times only one notification will be issued to each relevant alert notification medium Details what information is included in an E mail notification Details what information is included in an SMS device notification SMS devices are restricted to as little as 140 characters per message Software Requirements Specification for GARNET ID Requirement REQ 0105150 JAn alert issued to a GARNET desktop client will contain the alert title URL if provided timestamp severity and category s Some TBD amount of the description will be included A URL to the GARNET system to retrieve the full details about the alert will also be included REQ 0105160 An alert notification issued to a Page 13 Justification Details what information is included in a GARNET client desktop notification For security purposes alert notification will GARNET desktop client will be sent be encrypted whenever possible during over a secure communication medium 3 6 Alert Searches transmission Not feasible via E mail and alphanumeric pager notifications Alert searches provide the ability for a user to get the details about a historical alert For example if an alert about road closings is issued a user may need to refer back to the alert for the specific dates Additionally alert searches will be needed for security reasons to track any misuse
31. tforms REQ 0204050 The system shall provide failover peer ee to ensure reliability REQ 0204060 The GARNET desktop client shall support end users with disabilities according to the final version of the draft Notice of Proposed Rulemaking on Standards for Electronic and Information Technology implementing Section 508 of the Rehabilitation Act 5 Other Requirements 5 1 System Constraints Page 22 Justification The overall architecture should be designed such that it will be able to be extended to support multiple mechanisms to create an alert For example via http phone etc Notify via GARNET desktop client E mail pager CCTV phone fire alarm and other futuristic mediums The number of users can grow and the system will be able to scale to handle them if we add more machines to handle them The system shall be available when necessary and must provide a fail over This section lists constraints set upon the implementation of GARNET 2 0 The intent of system constraints is to establish known limitations on operation system characteristics Software Requirements Specification for GARNET Page 23 5 1 1 GARNET 2 0 CON 0101040 The GARNET system client This specifies minimum operating applications shall be supported on systems needed to implement GARNET the following platforms PC 2 0 Windows 2000 SP3 and XP SP2 Red Hat 8 0 Mac OSX 10 2 x CON 0101030 The GARNET system user interface This specifies minimum
32. uirements for the Global Alert Resolution Network GARNET The requirements specified in this document encompass the functionality for the first production release of GARNET The document contains two levels of requirements The first level of requirements outlines broad user and system functionality that is necessary to achieve the overall goals of GARNET The second level of requirements details the specific functionality that will be included in GARNET 2 0 GARNET 2 0 encompasses the system functionality necessary for initial rollout to the Goddard Space Flight Center s GSFC s Greenbelt Facility In the case that a customer wishes to alter and or extend GARNET 2 0 an additional requirements document should be produced outlining the altered and or new functionality 1 2 Intended Audience and Reading Suggestions Each section of requirements in this document is separated into two sections high level and GARNET 2 0 The intended audience for the high level requirements includes the following Project Managers Marketing Staff System Analysts Developers Testers The second level of requirements GARNET 2 0 provides detailed system requirements and is intended for the following audiences e Project Managers e Developers e Testers e User manual authors Those not interested in the detailed requirements may skip the GARNET 2 0 sections of the document 1 3 Project Vision The ultimate goal of GARNET is to deliver time critical i
33. y users affected by or interested in the alert with receive the alert Additionally another goal of the system includes sending detailed information with the alert Software Requirements Specification for GARNET Page 11 3 5 1 High Level REQ 0105000 The system shall provide fine Users only subscribe to categories they grained alert notification control to jare interested in Besides general site only notify those users affected by wide alerts this prevents users from the alert by matching the alert being inundated with inconsequential criteria with user profiles notifications REQ 0105010 The system shall issue detailed alertilt is possible for e mail notifications to information including alert contain elaborate detailed information description and severity to mediums since it can be represented by text where it is feasible However there is no means for fire alarms to represent information with such fidelity they simply ring and strobe We are limited by the capabilities of the alert REQ 0105020 desktop client E mail and SMS devices REQ 0105030 The system shall provide away to Some users should be notified of an alert prioritize the order in which users _ jprior to other users For example FOMs are issued notifications should be notified of an alert first 13 Requirement Justification 3 5 2 GARNET 2 0 REQ 0105040 The system shall support issuing an E mail provides a quick easy way to notify alert notificat
Download Pdf Manuals
Related Search