Software Acceptance Form - EPRI
Software Quality Assurance (SQA)
Software Acceptance Form (SAF) Traveler
This form is to be completed throughout your application’s development cycle. The form needs to be fully completed by the time you submit your application to SQA for testing.
Notes on the use of the SAF Traveler:
• All boxes can be completed as your software project is developed and information becomes available.
• Use the same form for your Pre-Production (e.g., Beta) and Production (Final Acceptance) submittal.
• [pic] fields must be completed at the Project Initiation. Submit SAF with SOW for PR approval.
• [pic] fields must be completed prior to submitting your software to SQA for Software Testing.
• [pic] fields allow you to enter additional comments at the end of each section.
Reminders:
• For software development requirements, review the EPRI Software Development website.
• For questions on the development requirements or this form, e-mail SQA@.
• All software must be tested by SQA before distribution to EPRI members or the public.
|A. General Software Information |
|Complete this section to start your application’s development cycle. Complete each field as the information is obtained. If not yet available, leave blank or |
|select “I do not know” and explain in the comments. Any “I do not know” responses must be resolved prior to submitting the Production version to SQA. |
|EPRI Project Manager: |
|Software Name: |Software Life Cycle Type: |
|Software Acronym: |Software Deliverable Type: |
|Software Version: |Pre-Production Submittal Date: |
|Sector: |Production Submittal Date: |
|Nuclear Sector Only |Production |
|Quality Requirements: |Planned Completion Date: |
|Select the highest level that applies. | |
|PR # (e.g., 10001234): |SAP Material ID # (Pre-Production): |
|WBS # (e.g., 1-001234-01-01): |SAP Material ID # (Production): |
|Subscriber Website (SWS) ID # (Only required for web applications): |
| |
|Project Manager acknowledges that: |
|All required approvals from the Web & Mobile Solutions (SWS Design) and Digital Marketing (SWS URL) have been obtained: , Comments: |
|If developing a Nuclear Sector SWS that utilizes a database, the application includes the QMP Compliance Language for Database Applications: , Comments: |
|Software Developer: |
|Contact: |Address: |
| | |
| | |
| | |
|Phone: | |
|Email: | |
|Additional Comments for Section A: | |
|B. Software Development Information |
|Complete this section in the early stages of your application’s development. |
|Expected User Base |
|Is the software for internal use only? |, Comments: |
|Who are the intended users? | |
|Is the project developed strictly for a Billable Services Agreement (BSA)? |, Comments: |
|Project Summary (Life Cycle) Information |
|Short summary of what the product is or the problem that is being solved | |
|Software approach/architecture (e.g. platform, web, database, programming language, | |
|etc.) | |
|How will software be supported and maintained? Are additional releases planned? | |
|Software Distribution |
|Will this Pre-Production (e.g., Beta) release replace a previous Pre-Production |If Yes, list the EPRI Product ID #’s to be replaced: |
|release? | |
|Will this Production release replace a previous release (e.g., Pre-production, |If Yes, list the EPRI Product ID #’s to be replaced: |
|Production)? | |
|How is this software distributed? |, |
| |If Other, explain: |
|Is this software Free to the Public? |, Comments: |
|If Yes, submit the Making EPRI Results FREE – Posting Form (URL Internal to EPRI only) to the appropriate sector contact. |
| |
|Note: Free to the public software deliverables are for the binary/executable, associated documentation, and supporting files only. Source code will NOT be |
|distributed. |
| |
|Project Manager acknowledges that all required approvals to post as FREE have been obtained. , Comments: |
|Is this software Open Source? |, Comments: |
|If Yes, identify the open source license (e.g., BSD): |
|and submit the Making EPRI Results FREE – Posting Form (URL Internal to EPRI only) to the appropriate sector contact. VP approval is required for all open |
|source releases. |
| |
|For guidance, review: Understanding Open Source and Proprietary Software Licenses at EPRI |
|(URL Internal to EPRI only) |
|Project Manager acknowledges that all required approvals to post as Open Source have been obtained. , Comments: |
|Software Development Documentation |
|Required software documentation submitted: |Submitted? , |
|Developer Quality Plan |Comments: |
|Requirements Specifications | |
|Additional software documentation submitted: |If None, explain: |
|Test Plan with test cases and procedures | |
|Verification and Validation Plans | |
|Traceability Matrix | |
|Wireframe (if developing a web application) | |
|Additional Comments for Section B: | |
|C. Corporate Policy Information |
|Complete this section to ensure your software deliverable complies with the following corporate policies. |
|Product Classification |
|Product Classification: |
|“Licensed” products: Select this category if the product contains confidential information and the product requires restrictions on who can see it. Access will|
|be provided when the relevant Research Portfolio Agreement (“RPA”) or Supplemental Project Funding Agreement (“SPFA”) are in place, or when a customer signs a |
|stand-alone license agreement. |
|“Restricted” products: Select this category if the product contains confidential information with restrictions preventing EPRI from sharing the product with |
|anyone in the public, such as third-party license restrictions (e.g., EPRI can only share the product with certain funders). Access will be provided when the |
|relevant RPA/SPFA and Supplemental License Agreement (“SLA”) have been signed. |
|Software releases are not coded as “Copyright” products. |
|3rd Party Software |
|Software utilizes or requires 3rd party software? |, Comments: |
|List all approved 3rd party software required to reproduce the EPRI software product. Select the highest purpose. If distributed, EPRI must own or have a |
|license. |
|3rd Party Software and Version #: |Licensed to: |Purpose (1/2/3): |
| | | |
| | | |
| | | |
| | | |
| | | |
|List additional 3rd party software here: | |
|Cryptography and Encryption |
|Software utilizes Cryptography/Encryption |, Comments: |
|(e.g., key management, etc.)? | |
|If Yes, submit the Cryptography and Encryption Functions Checklist and Definitions form to Export Counsel. |
| |
|Project Manager acknowledges that the required Cryptography and Encryption Functions Checklist and Definitions form has been submitted. |
|Internationalization |
|Support for Internationalization is required for all for all EPRI developed software. |
|1. Software supports international date and number formats? | |
|2. Software supports SI Units (International System of Units)? | |
|3. Software supports other language and culture features? | |
|If you answered No or N/A to question # 1 or # 2 above, explain the reason(s) in the comments field below. You may be required to obtain a Sector Director |
|exemption for this corporate requirement. |
| Internationalization support comments: |
|Additional Comments for Section C: | |
|D. Software Product Abstract and Executive Summary |
|Software Product Abstract |
|The Software Product Abstract is used to: |
|Provide export classification |
|Display in the EPRI Member Center (). This information is public – do not include any proprietary information |
| |
|Your software cannot be activated for distribution until the product description is published and software is export coded. |
|A. Summary description of the software: | |
|B. Benefits and Values - 3 bullet points highlighting the benefits and value | |
|provided by the software: | |
|C. Platform Requirements - List supported Windows operating systems such as | |
|Windows 10, Windows 8.1, Linux, etc.: | |
|D. Keywords - List 3 (or more): | |
|Software Product Executive Summary (Optional) |
|The Software Product Executive Summary: |
|Is used to provide concise detail including the results on the EPRI product. |
|Download of the Executive Summary files is only available to funders of the product in the EPRI Member Center (). |
|The Executive Summary is optional for software products. |
|A. Primary Audience: | |
|Identify primary end user of this research. | |
|B. Secondary Audience: | |
|Identify a secondary end user, if applicable. | |
|C. Key Research Question: | |
|Concise statement (no more than a few sentences) describing the main issue or | |
|research question. This section should answer why this R&D was conducted. | |
|Length: 3-4 sentences. | |
|D. Research Overview: | |
|Briefly describe what was done in this research, how it was done and the form | |
|of the research results. Length: one paragraph, 5 – 6 sentences. | |
|E. Key Findings: | |
|• For software: pull out 4-6 key aspects of the software, use examples. | |
|• Share the key “nuggets” from the report/product. | |
|• Note that only people who have access to the subject report (by virtue of | |
|membership, funding, or free public access) will have access to this summary, | |
|so findings should be specific. | |
|• Best practice: Use bullets and include references and links to specific | |
|locations/sections in the report. | |
|F. Why This Matters: | |
|Research Value: clearly explain the value that members are receiving from the | |
|research or product. Written to a general member audience that covers advisors,| |
|end-users, and senior management. Length: 2-3 sentences. | |
|G. How to Apply Results: | |
|Include information here that would help the end-user implement the research | |
|product. This might be platform requirements for software, reference to a quick| |
|start guide to rapidly derive value from the product, guidance on which | |
|internal/external stakeholders the user should engage to improve changes for | |
|success, etc. Length: 2-3 sentences. | |
|H. Learning and Engagement Opportunities: | |
|• If applicable, list other projects, supplemental activities (such as user | |
|groups), software, webcasts/workshops, etc. that the end-user should be aware | |
|of to optimize the value received. Provide links if available. | |
|• Who might be interested in this product? Any collaborating Organizations, | |
|Agencies, Sectors, or Programs on this deliverable? | |
|I. EPRI Contacts: | |
|Insert PM Name, Title, Email. | |
|J. Program: | |
|Add Program Name and Number here. | |
|K. Implementation Category: | |
|Add Nuclear Product Implementation Category | |
|here. | |
|Additional Comments for Section D: | |
|E. Pre-Production Software Submittal Checklist |
|Complete this section to submit your Pre-Production release to SQA for testing (e.g., Alpha, Beta, Prototype). For the submittal checklist and Pre-Production |
|Splash screen, see: |
|Pre-Production and Production Submittal Package Requirements |
|Pre-Production Splash Screen |
|Indicate that you have confirmed that the software and all supporting documentation is free of Confidential Information by checking the components that have |
|been vetted: |
|Software User Interface |
|Software User Documentation (including screenshots) |
|Example data included with software |
|Other: |
|Submittal Checklist: |
|For Pre-Production software what level of testing is needed: , |
|Pre-Production Software Stage: |
|If Interim Release, have all required approval and licensing been obtained? |
|Location of submittal files? ; if Secure Share, send to SQA@ |
|Hash information: |
|Executable files (e.g., software, manuals): MD5: |
|Source files (e.g., un-compiled source, build instructions): MD5: |
|Additional submittal comments: |
|Items submitted: |
|Software files |
|Software documentation (e.g., Software Manual) |
|Source Code |
|Source Code Build Instructions |
|Developer Quality Plan |
|Requirements Specifications |
|Developer comments to previous SQA report (i.e., Production “Pass” from previous version) |
|Software/Hardware Key/Dongle (if required), Explain: |
|Testing credentials for Subscriber Website (SWS) applications: |
|Testing Server URL: |
|Type (e.g., Admin): / User ID: / Password: |
|Type (e.g., Read only): / User ID: / Password: EPRI ID/Password |
|Production Server URL: |
|Type (e.g., Admin): / User ID: / Password: |
|Type (e.g., Read only): / User ID: / Password: EPRI ID/Password |
|Project Manager Submittal for SQA Pre-Production Testing and Release |
|Type in name and date to release your software deliverable to SQA for testing and subsequent distribution. |
|Project Manager Signature: |Date (MM/DD/YY): |
|Additional Comments for Section E: | |
|F. Production Software Submittal Checklist |
|Complete this section to submit your Production release to SQA for testing (e.g., Final Acceptance). For the submittal checklist, see: |
|Pre-Production and Production Submittal Package Requirements |
|Indicate that you have confirmed that the software and all supporting documentation is free of Confidential Information by checking the components that have |
|been vetted: |
|Software User Interface |
|Software User Documentation (including screenshots) |
|Example data included with software |
|Other: |
|Submittal Checklist: |
|Submittal Process Stage: Production Test (Final Acceptance) |
|Location of submittal files? ; if Secure Share, send to SQA@ |
|Hash information: |
|Executable files (e.g., software, manuals): MD5: |
|Source files (e.g., un-compiled source, build instructions): MD5: |
|Additional submittal comments: |
|Items submitted: |
|Software files |
|Software documentation (e.g., Software Manual) |
|Source Code |
|Source Code Build Instructions |
|Developer Quality Plan |
|Requirements Specifications |
|Developer comments to previous SQA report (i.e., Pre-Production “Pass” for this version) |
|Software/Hardware Key/Dongle (if required), Explain: |
|Testing credentials for Subscriber Website (SWS) applications: |
|Testing Server URL: |
|Type (e.g., Admin): / User ID: / Password: |
|Type (e.g., Read only): / User ID: / Password: EPRI ID/Password |
|Production Server URL: |
|Type (e.g., Admin): / User ID: / Password: |
|Type (e.g., Read only): / User ID: / Password: EPRI ID/Password |
|Project Manager Submittal for SQA Production Testing and Release |
|Type in name and date to release your software deliverable to SQA for testing and subsequent distribution. |
|Project Manager Signature: |Date (MM/DD/YY): |
|Additional Comments for Section F: | |
-----------------------
Green
Blue
White
................
................
In order to avoid copyright disputes, this page is only a partial summary.
To fulfill the demand for quickly locating and searching documents.
It is intelligent file search solution for home and business.
Related download
- u s navy hosting
- checklist template
- risk management plan template
- software acceptance form epri
- recording details of meetings with employees template
- the latest open source software available
- sambrief windows multilingual user interface
- cis 50 computing and information technology
- download
- lab guide windows insider lab for enterprise
Related searches
- aarp guaranteed acceptance life insurance
- global acceptance auto loan
- global acceptance auto finance
- wells fargo financial acceptance auto
- university of scranton acceptance rate
- globe acceptance inc
- acceptance corp auto loan
- global acceptance credit company
- global acceptance credit company lp
- regional acceptance customer service
- scranton acceptance rate
- nature communications acceptance rate