Research & Development Software Training

Transcription

1 Research & Development Software Training Software Excellence Network March 15, 2016

2 Overview Introduction: why are we here? swdev.epri.com & you: review of website resources 2015 trends & lessons learned Major changes for Projects: Which software type should I develop? Can I get my software to my users faster for their review? Questions & discussion 2

3 Introduction Who should be here? Any staff member or contractor who conceives of, plans, develops or otherwise supports R&D software 3

4 Introduction Why exactly are we here? Free food? Learn processes & tools for effective R&D software development & delivery R&D software a powerful tool and part of EPRI R&D Technology transfer Data gathering Calculational aid R&D software policy fully supports this goal But 4

5 Introduction: Why exactly are we here? The EPRI Project Manager is ultimately accountable for assuring the software performs adequately. Training provides tools to help. 5

6 Introduction Training Objectives Awareness & overview: EPRI s R&D software requirements Familiarization: software development website swdev.epri.com Discussion: questions & answers Knowledge: where to go for more information The EPRI Nuclear Quality Assurance (NQA) program supplements the corporate software requirements; if there is a conflict, then the NQA program will take precedence. Please see NQA for questions. 6

7 Introduction What changed in 2016? Major website changes Streamlined review of 3 rd party / open source software; development of an approved software list 7

8 Introduction What happens next? Potential automation of forms (linked to Enterprise Content Management project) itunes / App Store Other suggestions? 8

9 2015 Trends & Lessons Learned 9

10 Trends & Lessons Learned: What types of software are being developed

11 Trends & Lessons Learned: New products vs. Upgrades New Products vs. Upgrades Lessons What makes an acceptable software? Risk Factors Upgrades can be tricky New technology (at least for EPRI) 11

12 Demonstration of the updated Software Development Website URL: 12

13 2016 Projects Picking the right software types 13

14 Planning Phase Software Type (from 2015 Training) Special software types: emedia - Desktop (includes simple spreadsheets) emedia - Web Computer-Based Training (CBT) Common software types: Complicated spreadsheets Desktop Server/Enterprise Software Implemented via a Commercial Software Platform Software Extension Web Application / Web Service Mobile Application Exception: Business Service Agreement (BSA) requirements are contract-driven 14

15 TRL Level Definition TRL 1-2: Concept formulated, but unproven TRL 3-5: Concepts proven in controlled exercises TRL 6-9: Concepts proven in limited environments and ready for wider distribution Software Type Prototype Proof-of- Concept Production Release Strategy Usually released internally or in controlled environment. External release limited in audience and time. External release limited in time to prove concepts External release follows lifecycle plan 15

16 Summary Be thoughtful about the software type you choose your project will thank you. New project types acknowledge the diversity of the work we do at EPRI Protoype & Proof-of-Concept are used to move R&D along production is used for technology transfer. 16

17 2016 Projects Early pre-release 17

18 Engaging Users in Software Development Frequent Stakeholder engagement leads to better software products. Identify value of the product Gauge ease-of-use Verify software works in customer environment Early identification of issues, such as IT limitations Optimal engagement varies depending on the project and the customers Typical beta process is valuable More frequent interaction may be warranted Challenges Customers who are willing to provide meaningful feedback in short period of time Users who are cooperative Communication of quality level Management of perceptions EPRI Legal / Licensing Issues Maintaining EPRI s research role 18

19 Interim Release Process (summary) Determine whether a more active customer engagement is appropriate for the project Identify risks Not suitable for all projects Identification of key stakeholders that can form the development group Best done very early in the project Usually not more than 2 or 3 Director approval ( ) Legal Participants will be required to sign a separate license agreement, specifically laying out the risks/limitations Each release to customers will still require SQA review before release to users Software will be provided by SQA directly electronically (e.g. secure ) Participants are required to uninstall the software (or web access will be removed) once the product is complete See for more detail 19

20 Upcoming Changes to Processes for the Use of 3 rd Party Software 20

21 Reasons for upcoming changes Clarifying policy and process Helps to minimize risk of violating license terms Insure that we are using correct version that is properly patched 21

22 Approved Software List Continue with SQA Process Development Software Complete Inbound Software Documentation Form YES NO EPRI Approved Software Master List & consistent w/ use? Inbound Software Approval Process Software Whitelist is maintained by Information Security (InfoSEC) & will be on InsideEPRI 22

23 Inbound Software Process Contact Legal Third Party Proprietary Not on Approved List License Type? Open Source Evaluate Open Source License Inbound Software Documentation Form 23

24 Evaluate Open Source License Inbound Software Process OSS Partially Reciprocal Partially Evaluation Reciprocal Ex: MPL, CDDL, Eclipse Ex: Apache, MIT, Berekley Software Distribution Permissive or Academic OSS Type Inbound Software Documentation Form Reciprocal or Copyleft Ex: GPL, GPL3, PL2 NO Released Under Same Type? YES Contact Legal 24

25 OSS Partially Reciprocal Evaluation Inbound Software Documentation Form Linking Linking or Embedding Partially Reciprocal Code Contact Legal Embedding Code Evaluate OSS License 25

26 Summary There is no standard Third-party license (i.e. Open Source or other 3 rd Party License) The application of software varies from project to project and may be outside of scope of license Open-source comes in different flavors leading to various intellectual property considerations 26

27 ithenticate 27

28 ithenticate Plagiarism Detection Service Run end-user documentation (for example, software manuals) through ithenticate, unless it: Is export controlled (licensable) Contains third party intellectual property (IP) Contact your sector representative for specific procedural information: Environment: Becca Madsen, Generation: Adele Fowler, Nuclear: Amy Vrabely, PDU: Brad Connatser, Review supporting documents about ithenticate from Technical Publications Tip: Search your sector s site on InsideEPRI for information 28

29 ithenticate Plagiarism Detection Service Supports the following file types:.doc,.docx,.docm,.dot,.dotx.pdf.txt.html,.htm.rtf Tip: For PowerPoint files, convert to PDF Max pages: 400 File size: Max 40 MB including graphics < 2 MB raw text (no graphics).zip file: Max size 200 MB Max 1,000 files 29

30 Summary 30

31 BACKUP Website Screenshots 31

32 EPRI Software Development Website URL: 32

33 EPRI Software Development Website What is new for 2016? 33

34 EPRI Software Development Website Let s Get Started is the quickest way to answer your most commonly asked questions. Give it a try! 34

35 EPRI Software Development Website Development process steps split into Key Elements, Overview and Resources! 35

36 EPRI Software Development Website Product requirements grouped into Corporate, General, Excel-specific and Web-specific. 36

37 EPRI Software Development Website Forms! Forms! Forms and the Appendix! 37