Kevin Carmichael ( NASA HQ Office of Chief Engineer,  Detailee) Jon Verville (NASA GSFC)
<ul><li>Guidance material to help the NASA workforce implement the software engineering requirements in NPR 7150.2A and pr...
<ul><li>NASA Software Community decided to augment the Agency’s Software Engineering requirements by developing a electron...
<ul><li>Software workforce prefers electronic access versus traditional paper references </li></ul><ul><li>Allows guidance...
<ul><li>NASA Software Engineering Requirements (NPR 7150.2A) contain 1 32  requirements that  are applicable in variable d...
<ul><li>Guidance material developed by a dedicated team that has topic expertise or has researched the material which incl...
<ul><li>Software Developers </li></ul><ul><li>Software Managers </li></ul><ul><li>Software Engineering Process Groups </li...
<ul><li>NASA Engineering Network  (NEN)  Software Engineering Community of Practice </li></ul><ul><li>http://nasa7150.onco...
<ul><li>Prototype available on NASA Engineering Network – complete </li></ul><ul><li>Topic areas complete, architecture fu...
<ul><li>Collect and analyze user community requirements  </li></ul>Done, Req’t Doc developed <ul><li>Prioritize inputs bas...
# Feature Location 1 Classification and Safety Critical Assessment Tools  NEN CoP 2 Link requirements to “best in class” e...
# Feature Location 1 Applying requirements to small projects  Handbook 2 Transitioning to a higher class  Handbook 3 Compl...
Jon Verville (GSFC)
<ul><li>New capabilities for navigation/discovery/media </li></ul><ul><ul><li>The hyperlink, Full text search, Attachments...
1.0 2.0 3.0 4.0 1.1 1.2 1.3 1.4 1.5 1.6 1.7 1.8 1.9 1.10 2.1 2.2 2.3 2.4 2.5 2.6 3.1 3.2 3.3 4.1 4.2 4.3 4.4 4.5
1.0 2.0 3.0 4.0 1.1 1.2 1.3 1.4 1.5 1.6 1.7 1.8 1.9 1.10 2.1 2.2 2.3 2.4 2.5 2.6 3.1 3.2 3.3 4.1 4.2 4.3 4.4 4.5
Tools/files links External document External website Rationale, guidance, small projects
1.0 2.0 3.0 4.0 1.1 1.2 1.3 1.4 1.5 1.6 1.7 1.8 1.9 1.10 2.1 2.2 2.3 2.4 2.5 2.6 3.1 3.2 3.3 4.1 4.2 4.3 4.4 4.5
1.2 1.3 1.9 1.10 2.2 2.6 3.2 4.3 4.4 4.5 1.4 1.7 2.1 2.2 2.3 4.3 4.1 4.2 4.3 4.4 4.5 Product Development 1.1 1.2 1.3 1.4 1...
<ul><li>One master PDF with all “static” material </li></ul><ul><li>Individual PDFs for each section with informational he...
<ul><li>http://nasa7150.onconfluence.com/ </li></ul>
<ul><li>Kevin Carmichael </li></ul><ul><li>(216) 433-3966 </li></ul><ul><li>[email_address] </li></ul><ul><li>Jon Verville...
Upcoming SlideShare
Loading in …5
×

Carmichael.kevin

15,004 views

Published on

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
15,004
On SlideShare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
7
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • Will be speaking to this slide at least 50% of Jon’s time allotment
  • We are used to having documents laid out in a linear fashion, but often times sections of material do not neatly fit into one area
  • Any often there are complex relationships among the sections that are not immediately apparent
  • And each section has associated material externally
  • With tagging, there are multiple ways of describing each section with metadata, which is just one more way of discovering and navigating the information contained
  • Displaying sections which match certain criteria, easy to browse, will show screen shots to clarify later
  • Carmichael.kevin

    1. 1. Kevin Carmichael ( NASA HQ Office of Chief Engineer, Detailee) Jon Verville (NASA GSFC)
    2. 2. <ul><li>Guidance material to help the NASA workforce implement the software engineering requirements in NPR 7150.2A and promote best practices across the Agency in software engineering. </li></ul><ul><li>Addresses topics of interest identified by the Software Engineering community of practice </li></ul><ul><li>Provide guidance for all of the software enginering requirements contained in NASA’s NPR 7150.2A </li></ul><ul><li>Contains guidance and rationale associated with requirements, examples, best practices, lessons learned, references, tools and templates </li></ul>
    3. 3. <ul><li>NASA Software Community decided to augment the Agency’s Software Engineering requirements by developing a electronic version of a Handbook </li></ul><ul><li>Inputs regarding Handbook content collected from the software community </li></ul><ul><li>Inputs sorted into “features” and “guidance” and prioritized </li></ul><ul><li>Guidance material was further sorted into topics and related to the existing NASA Software Engineering requirements </li></ul><ul><li>NASA Engineering Network (NEN) was selected as the access point for the Handbook and NEN currently host a number of features such as Ask-an-Expert and the Software Engineering NASA Process Asset Library </li></ul><ul><li>Team formed to develop content, architect the electronic aspect of the system and implement it </li></ul>
    4. 4. <ul><li>Software workforce prefers electronic access versus traditional paper references </li></ul><ul><li>Allows guidance material to be “published” as it is developed vs. when it is all finished </li></ul><ul><li>Allows easy updates and corrections </li></ul><ul><li>Easily searchable </li></ul><ul><li>Delivers targeted material with easily access to reference material. </li></ul><ul><li>Integrated into the NEN Software Engineering Community of Practice (CoP) </li></ul>
    5. 5. <ul><li>NASA Software Engineering Requirements (NPR 7150.2A) contain 1 32 requirements that are applicable in variable degrees to NASA’s 8 classes of software (diminishing requirements for less critical software) </li></ul><ul><li>Guidance material provides further explanation of the requirements and the rationale for why they exist. </li></ul><ul><li>Best-in-Class examples, templates, and tools are provided to help developers get started quickly and maintain compliance with NASA’s Software Engineering Requirements. </li></ul><ul><li>Allows developers to easily focus on specific information necessary to comply with requirements. </li></ul>
    6. 6. <ul><li>Guidance material developed by a dedicated team that has topic expertise or has researched the material which includes interviews with experts. </li></ul><ul><li>References are provided to related material both internal and external to NASA. </li></ul><ul><li>All material is approved for inclusion in the handbook by the Program Executive for Software Engineering in the HQ OCE. </li></ul>
    7. 7. <ul><li>Software Developers </li></ul><ul><li>Software Managers </li></ul><ul><li>Software Engineering Process Groups </li></ul><ul><li>Software Process Improvement Personnel </li></ul><ul><li>Software Assurance Personnel </li></ul><ul><li>Software Safety and Reliability Engineers </li></ul><ul><li>Systems Engineers </li></ul><ul><li>Hardware Engineers </li></ul><ul><li>Project Managers </li></ul>
    8. 8. <ul><li>NASA Engineering Network (NEN) Software Engineering Community of Practice </li></ul><ul><li>http://nasa7150.onconfluence.com/display/7150/Home </li></ul>
    9. 9. <ul><li>Prototype available on NASA Engineering Network – complete </li></ul><ul><li>Topic areas complete, architecture functional, features in place on the Software Engineering NASA Engineering Network Community of Practice – March 2011 </li></ul><ul><li>Guidance for the NASA Software Engineering requirements 80% complete – September 2011 </li></ul><ul><li>Target for Handbook complete – January 2012 </li></ul>
    10. 10. <ul><li>Collect and analyze user community requirements </li></ul>Done, Req’t Doc developed <ul><li>Prioritize inputs based on need and ease of development (low hanging fruit approach) </li></ul>Done <ul><li>Generate concept and get community buy-in </li></ul>Done <ul><li>Generate requirements, allocate to phases </li></ul>Done <ul><li>Develop architecture and prototypes </li></ul>Done <ul><li>Collect guidance, examples, templates, links, references, checklists, tools </li></ul>Underway <ul><li>Build it in phases </li></ul>Underway <ul><li>Beta test it with user community </li></ul>Underway <ul><li>Publish it as content is developed </li></ul>Underway <ul><li>Monitor use </li></ul>Underway <ul><li>Control changes and improve it based on feedback </li></ul>
    11. 11. # Feature Location 1 Classification and Safety Critical Assessment Tools NEN CoP 2 Link requirements to “best in class” examples and templates Handbook 3 Lifecycle products linked to major milestones, integrated with 7120 and 7123 Handbook 4 Present all requirements associated with a software class and include applicable safety critical and assurance requirements Handbook 5 Traceability of 7150 requirements to 7120 and 7123 related requirements Handbook 6 Gateway to agency tools, training, and agency and center experts NEN CoP 7 Ability to search the NPR from different user perspectives Handbook 8 Definitions of terms Handbook 9 Links to agency and center processes and PALs NEN CoP 10 Compliance matrices NEN CoP
    12. 12. # Feature Location 1 Applying requirements to small projects Handbook 2 Transitioning to a higher class Handbook 3 Compliance to requirements Handbook 4 Tailoring of project assets, with examples Handbook 5 Use of COTS, GOTS, MOTS and Open Source Handbook 6 Acquisition of software Handbook 7 Flow down of the software engineering requirements on to contracts and use on multi center projects Handbook 8 Waiver processes Handbook 9 Guidance on requirement tailoring and on handling safety critical code Handbook 10 Qualification of flight software Handbook
    13. 13.
    14. 14. Jon Verville (GSFC)
    15. 15. <ul><li>New capabilities for navigation/discovery/media </li></ul><ul><ul><li>The hyperlink, Full text search, Attachments </li></ul></ul><ul><li>Structure for complex relationships in material </li></ul><ul><ul><li>Tagging </li></ul></ul><ul><li>Social interaction around material </li></ul><ul><ul><li>Feedback directly around content </li></ul></ul><ul><li>New paradigm for handbook creation and updates </li></ul><ul><ul><li>Workflow on web, One source for latest version, Incremental release </li></ul></ul>
    16. 16. 1.0 2.0 3.0 4.0 1.1 1.2 1.3 1.4 1.5 1.6 1.7 1.8 1.9 1.10 2.1 2.2 2.3 2.4 2.5 2.6 3.1 3.2 3.3 4.1 4.2 4.3 4.4 4.5
    17. 17. 1.0 2.0 3.0 4.0 1.1 1.2 1.3 1.4 1.5 1.6 1.7 1.8 1.9 1.10 2.1 2.2 2.3 2.4 2.5 2.6 3.1 3.2 3.3 4.1 4.2 4.3 4.4 4.5
    18. 18. Tools/files links External document External website Rationale, guidance, small projects
    19. 19. 1.0 2.0 3.0 4.0 1.1 1.2 1.3 1.4 1.5 1.6 1.7 1.8 1.9 1.10 2.1 2.2 2.3 2.4 2.5 2.6 3.1 3.2 3.3 4.1 4.2 4.3 4.4 4.5
    20. 20. 1.2 1.3 1.9 1.10 2.2 2.6 3.2 4.3 4.4 4.5 1.4 1.7 2.1 2.2 2.3 4.3 4.1 4.2 4.3 4.4 4.5 Product Development 1.1 1.2 1.3 1.4 1.5 1.6 2.3 2.4 3.1 3.2 3.3 4.5
    21. 21. <ul><li>One master PDF with all “static” material </li></ul><ul><li>Individual PDFs for each section with informational header page </li></ul><ul><li>All PDFs have embedded links back to web equivalent </li></ul><ul><li>Optimize “static” material release cycle (potentially have workflow on web) </li></ul><ul><li>Website with all dynamic content and majority of “static” content </li></ul><ul><li>Interactive site for extensive collaboration, contribution, and commenting </li></ul><ul><li>Database driven layout to enable slicing data many different ways </li></ul><ul><li>Also used for material development of both products </li></ul><ul><li>Extensive links between CoP and Handbook site </li></ul>
    22. 22.
    23. 23.
    24. 24.
    25. 25. <ul><li>http://nasa7150.onconfluence.com/ </li></ul>
    26. 26. <ul><li>Kevin Carmichael </li></ul><ul><li>(216) 433-3966 </li></ul><ul><li>[email_address] </li></ul><ul><li>Jon Verville </li></ul><ul><li>(301) – 286-8741 </li></ul><ul><li>[email_address] </li></ul>

    ×