DOC PREVIEW
Toronto CSC 340 - R1 - Software Requirements Checklist

This preview shows page 1 out of 4 pages.

Save
View full document
View full document
Premium Document
Do you want full access? Go Premium and unlock all 4 pages.
Access to all documents
Download any document
Ad free experience
Premium Document
Do you want full access? Go Premium and unlock all 4 pages.
Access to all documents
Download any document
Ad free experience

Unformatted text preview:

R1 - Software Requirements Checklist (JPL)CLARITY1. Are the goals of the subsystem defined?2. Is the terminology consistent with the users' and/orsponsors' terminology?3. Are the requirements clear and unambiguous?4. Is a functional overview of the program set provided?5. Is an overview of the operational modes, states, and conceptdescribed?6. Have the software environment (co-resident program sets) andhardware environment (specific configurations) beenspecified?7. If assumptions that affect implementation have been made,are they stated?8. Have the requirements been stated in terms of inputs,outputs, and processing for each function?COMPLETENESS1. Are required attributes, assumptions, and constraints of theprogram set completely listed?2. Have all requirements and constraints been assigned apriority?3. Have the criteria for assigning requirement priority levelsbeen defined?4. Have the requirements been stated for each delivery orstaged implementation?5. Have requirements for installation (packaging, sitepreparation, operator training) been specified?6. Have the target language, development environment, andrun-time environment been chosen?COMPLIANCE1. Does the documentation follow project and/or JPL standards?CONSISTENCY1. Are the requirements mutually consistent?2. Are the requirements in this document consistent with therequirements in related documents?3. Are the requirements consistent with the actual operatingenvironment (e.g., check hardware timing, precision, eventsequencing, data rates, bandwidth)?4. Do the requirements stay within the capability of therequirements allocated by the FDD?CORRECTNESS1. Do the requirements seem feasible with respect to cost,schedule, and technology?2. Are the requirements consistent with the actual operatingenvironment (e.g., hardware timing, precision, eventsequencing, data rates, bandwidth)?R1 - Software Requirements Checklist (JPL) (Continued)DATA USAGE1. Have the data type, rate, units, accuracy, resolution,limits, range, and critical values for all internal dataitems been specified?2. Have the data objects and their component parts beenspecified?3. Has the mapping between local views of data and global databeen shown?4. Has the management of stored and shared data been described?5. Has a list of functions that set and/or use stored andshared data been provided?6. Are there any special integrity requirements on the storeddata?7. Have the types and frequency of occurrence of operations onstored data (e.g., retrieve, store, modify, delete) beenspecified?8. Have the modes of access (e.g., random, sequential) for theshared data been specified?FUNCTIONALITY1. Are all described functions necessary and sufficient to meetthe mission/system objectives?2. Are all inputs to a function necessary and sufficient toperform the required operation?3. Does each function clearly describe how outputs (and shareddata) are generated from inputs (and shared data)?4. Are all function states defined?INTERFACE1. Are the inputs and outputs for all the interfaces sufficientand necessary?2. Are all the outputs produced by a function used by anotherfunction or transferred across an external interface?3. Are the interface requirements between hardware, software,personnel, and procedures included?4. Have the contents, formats, and constraints of all thedisplays been described in the SRD or Software Operator'sManual (SOM-1)?5. Are all data elements crossing program set boundariesidentified?6. Are all data elements described here or in the SIS-1?7. Has the data flow between internal software functions beenrepresented?R1 - Software Requirements Checklist (JPL) (Continued)LEVEL OF DETAIL1. Are the requirements free of design?2. Have all "TBDs" been resolved?3. Have the interfaces been described to enough detail fordesign work to begin?4. Have the accuracy, precision, range, type, rate, units,frequency, and volume of inputs and outputs been specifiedfor each function?5. Have the functional requirements been described to enoughdetail for design work to begin?6. Have the performance requirements been described to enoughdetail for design work to begin?MAINTAINABILITY1. Are the requirements weakly coupled (i.e., changing afunction will not have adverse and unexpected effectsthroughout the subsystem)?2. Will the requirements minimize the complexity of the design?3. Have FRD and FDD maintainability requirements been levied tofunctions?4. Have FRD and FDD portability requirements been levied tofunctions?5. Has the use of inherited design or code or pre-selectedtools been specified?PERFORMANCE1. Have the FRD and FDD performance requirements been allocatedto each function?2. Have the resource and performance margin requirements beenstated along with the means for managing them?RELIABILITY1. Have quality factors been specified as measurablerequirements or prioritized design goals?2. Have FRD and FDD reliability requirements been levied tofunctions?3. Have FRD and FDD availability requirements been levied tofunctions?4. Have FRD and FDD security/safety requirements been levied tofunctions?5. Are error checking and recovery required?6. Are undesired events considered and their required responsesspecified?7. Are initial or special states considered (e.g., cold starts,abnormal termination)?8. Have assumptions about intended sequences of functions beenstated? Are these sequences required?R1 - Software Requirements Checklist (JPL) (Continued)TESTABILITY1. Can the program set be tested, demonstrated, analyzed, orinspected to show that it satisfies the requirements?2. Are the individual requirements stated so that they arediscrete, unambiguous, and testable?3. Have the overall program set acceptance criteria beenestablished?4. Have clear pass/fail criteria for the acceptance tests beenestablished?5. Have the test methods (test, demonstration, analysis, orinspection) been stated for each requirement?TRACEABILITY1. Are all functions, structures, and constraints traced torequirements, and vice versa?2. Have the FDD and Integrated Software Functional Diagram(ISFD) requirements been allocated to functions of theprogram set?3. Do the requirements (or traceability matrix) indicatewhether they are imposed by the FDD or whether they arederived to support specific FDD requirements?4. Have the FRD, FDD, and any derived design goals andimplementation constraints been specified and prioritized?5. Is each requirement stated in a manner that it can beuniquely referenced in subordinate


View Full Document

Toronto CSC 340 - R1 - Software Requirements Checklist

Documents in this Course
Scoping

Scoping

10 pages

Load more
Download R1 - Software Requirements Checklist
Our administrator received your request to download this document. We will send you the file to your email shortly.
Loading Unlocking...
Login

Join to view R1 - Software Requirements Checklist and access 3M+ class-specific study document.

or
We will never post anything without your permission.
Don't have an account?
Sign Up

Join to view R1 - Software Requirements Checklist 2 2 and access 3M+ class-specific study document.

or

By creating an account you agree to our Privacy Policy and Terms Of Use

Already a member?