<div dir="ltr">I think you need to submit this using "git format-patch". <div><br></div><div>Do your work on a branch and submit the patches on that branch.</div><div>Something like:</div><div><br></div><div>git checkout master</div><div>git checkout -b am</div><div>git add FILES</div><div>git commit # pops up an editor to write message</div><div><br></div><div>git format-patch -o am master</div><div># puts patch in direcctory am, send that.</div><div><br></div><div>Email the patch. git has a lot of features. The above it a very minimal</div><div>subset and not a complete workflow. </div><div><br></div><div>--joel</div></div><br><div class="gmail_quote"><div dir="ltr">On Sat, Dec 1, 2018 at 10:30 AM Marçal Comajoan Cara <<a href="mailto:mcomajoancara@gmail.com">mcomajoancara@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Convert text to a table, TBDs into comments and add missing<br>
formatting.<br>
<br>
This work was part of GCI 2018.<br>
---<br>
eng/appendix-a.rst | 152 +++++++++++++++++++++++++++++++--------------<br>
1 file changed, 104 insertions(+), 48 deletions(-)<br>
<br>
diff --git a/eng/appendix-a.rst b/eng/appendix-a.rst<br>
index 633996b..cfad927 100644<br>
--- a/eng/appendix-a.rst<br>
+++ b/eng/appendix-a.rst<br>
@@ -8,7 +8,7 @@ Appendix: Core Qualification Artifacts/Documents<br>
************************************************<br>
<br>
An effort at NASA has been performed to suggest a core set of artifacts<br>
-(as defined by BOTH NASA NPR 7150.2B and DO-178B) that can be utilized<br>
+(as defined by **BOTH** NASA NPR 7150.2B and DO-178B) that can be utilized<br>
by a mission as a baselined starting point for “pre-qualification”<br>
for (open-source) software that is intended to be utilized for flight<br>
purposes. This effort analyzed the overlap between NPR 7150.2B<br>
@@ -20,60 +20,116 @@ Along with the specific artifact, the intent of the artifact was also<br>
captured; in some cases open-source projects, such as RTEMS, are already<br>
meeting the intent of the artifacts with information simply needing<br>
organized and formalized. The table below lists the general category,<br>
-artifact name, and its intent. Please note that this table does NOT<br>
+artifact name, and its intent. Please note that this table does **NOT**<br>
represent all the required artifacts for qualification per the standards;<br>
instead, this table represents a subset of the most basic/core artifacts<br>
that form a strong foundation for a software engineering qualification<br>
effort.<br>
<br>
-TBD convert to a table; see original PDF for guidance on desired look<br>
-TBD The PDF is in <a href="https://ftp.rtems.org/pub/rtems/people/joel/sw_eng_hb/" rel="noreferrer" target="_blank">https://ftp.rtems.org/pub/rtems/people/joel/sw_eng_hb/</a><br>
+.. COMMENT: TBD convert to a table; see original PDF for guidance on desired look<br>
+.. COMMENT: TBD The PDF is in <a href="https://ftp.rtems.org/pub/rtems/people/joel/sw_eng_hb/" rel="noreferrer" target="_blank">https://ftp.rtems.org/pub/rtems/people/joel/sw_eng_hb/</a><br>
<br>
-.. COMMENT: ====================================== BEGIN<br>
-Table 1. Core Qualification Artifacts<br>
+.. table:: Table 1. Core Qualification Artifacts<br>
+ :class: rtems-table<br>
<br>
-Category Artifact Intent<br>
-Requirements Software Requirements Specification (SRS)<br>
-<br>
-Requirements Management The project shall document the software requirements.<br>
- <br>
-The project shall collect and manage changes to the software requirements.<br>
- <br>
-The project shall identify, initiate corrective actions, and track until closure inconsistencies among requirements, project plans, and software products.<br>
- Requirements Test and Traceability Matrix The project shall perform, document, and maintain bidirectional traceability between the software requirement and the higher-level requirement.<br>
- Validation The project shall perform requirements validation to ensure that the software will perform as intended in the customer environment.<br>
- <br>
- <br>
-Design and Implementation Software Development or Management Plan A plan for how you will develop the software that you are intent upon developing and delivering.<br>
- <br>
-The Software Development Plan includes the objectives, standards and life cycle(s) to be used in the software development process. This plan should include: Standards: Identification of the Software Requirements Standards, Software Design Standards, and Software Code Standards for the project.<br>
- <br>
- Software Configuration Management Plan To identify and control major software changes, ensure that change is being properly implemented, and report changes to any other personnel or clients who may have an interest.<br>
- <br>
- Implementation The project shall implement the software design into software code.<br>
- <br>
-Executable Code to applicable tested software.<br>
- <br>
- Coding Standards Report The project shall ensure that software coding methods, standards, and/or criteria are adhered to and verified.<br>
- Version Description Document (VDD) The project shall provide a Software Version Description document for each software release.<br>
- <br>
-Testing and Software Assurance Activities Software Test Plan Document describing the testing scope and activities.<br>
- Software Assurance/Testing Procedures<br>
- To define the techniques, procedures, and methodologies that will be used.<br>
- <br>
- Software Change Report / Problem Report The project shall regularly hold reviews of software activities, status, and results with the project stakeholders and track issues to resolution.<br>
- <br>
- Software Schedule Milestones have schedule and schedule is updated accordingly.<br>
- <br>
- Software Test Report / Verification Results The project shall record, address, and track to closure the results of software verification activities.<br>
- <br>
-Problem report - Describes the process non-compliance with plans, output deficiency, or software anomalous behavior, and the corrective action taken.<br>
- <br>
-The project shall ensure that the software code is unit tested per the plans for software testing.<br>
- <br>
- <br>
-Usability Software User’s Manual The Software User Manual defines user instructions for the software.<br>
-.. COMMENT: ====================================== END<br>
+ +----------------+-----------------------+---------------------------------+<br>
+ | Category | Artifact | Intent |<br>
+ +================+=======================+=================================+<br>
+ | Requirements | Software Requirements | The project shall document the |<br>
+ | | Specification (SRS) | software requirements. |<br>
+ | | | |<br>
+ | | | The project shall collect and |<br>
+ | | | manage changes to the software |<br>
+ | | | requirements. |<br>
+ | | Requirements | |<br>
+ | | Management | The project shall identify, |<br>
+ | | | initiate corrective actions, |<br>
+ | | | and track until closure |<br>
+ | | | inconsistencies among |<br>
+ | | | requirements, project plans, |<br>
+ | | | and software products. |<br>
+ | +-----------------------+---------------------------------+<br>
+ | | Requirements Test and | The project shall perform, |<br>
+ | | Traceability Matrix | document, and maintain |<br>
+ | | | bidirectional traceability |<br>
+ | | | between the software |<br>
+ | | | requirement and the |<br>
+ | | | higher-level requirement. |<br>
+ | +-----------------------+---------------------------------+<br>
+ | | Validation | The project shall perform |<br>
+ | | | validation to ensure that the |<br>
+ | | | software will perform as |<br>
+ | | | intended in the customer |<br>
+ | | | environment. |<br>
+ +----------------+-----------------------+---------------------------------+<br>
+ | Design and | Software Development | A plan for how you will develop |<br>
+ | Implementation | or Management Plan | the software that you are |<br>
+ | | | intent upon developing and |<br>
+ | | | delivering. |<br>
+ | | | |<br>
+ | | | The Software Development Plan |<br>
+ | | | includes the objectives, |<br>
+ | | | standards and life cycle(s) to |<br>
+ | | | be used in the software |<br>
+ | | | development process. This plan |<br>
+ | | | should include: Standards: |<br>
+ | | | Identification of the Software |<br>
+ | | | Requirements Standards, |<br>
+ | | | Software Design Standards, |<br>
+ | | | and Software Code Standards for |<br>
+ | | | the project. |<br>
+ | +-----------------------+---------------------------------+<br>
+ | | Software | To identify and control major |<br>
+ | | Configuration | software changes, ensure that |<br>
+ | | Management Plan | change is being properly |<br>
+ | | | implemented, and report changes |<br>
+ | | | to any other personnel or |<br>
+ | | | clients who may have an |<br>
+ | | | interest. |<br>
+ | +-----------------------+---------------------------------+<br>
+ | | Implementation | The project shall implement the |<br>
+ | | | software design into software |<br>
+ | | | code. |<br>
+ | | | |<br>
+ | | | Executable Code to applicable |<br>
+ | | | tested software. |<br>
+ | +-----------------------+---------------------------------+<br>
+ | | Coding Standards | The project shall ensure that |<br>
+ | | Report | software coding methods, |<br>
+ | | | standards, and/or criteria are |<br>
+ | | | adhered to and verified. |<br>
+ | +-----------------------+---------------------------------+<br>
+ | | Version Description | The project shall provide a |<br>
+ | | Document (VDD) | Software Version Description |<br>
+ | | | document for each software |<br>
+ | | | release. |<br>
+ +----------------+-----------------------+---------------------------------+<br>
+ | Testing and | Software Test Plan | Document describing the testing |<br>
+ | Software | | scope and activities. |<br>
+ | Assurance +-----------------------+---------------------------------+<br>
+ | Activities | Software | To define the techniques, |<br>
+ | | Assurance/Testing | procedures, and methodologies |<br>
+ | | Procedures | that will be used. |<br>
+ | +-----------------------+---------------------------------+<br>
+ | | Software Change | The project shall regularly |<br>
+ | | Report / Problem | hold reviews of software |<br>
+ | | Report | activities, status, and results |<br>
+ | | | with the project stakeholders |<br>
+ | | | and track issues to resolution. |<br>
+ | +-----------------------+---------------------------------+<br>
+ | | Software Schedule | Milestones have schedule and |<br>
+ | | | schedule is updated |<br>
+ | | | accordingly. |<br>
+ | +-----------------------+---------------------------------+<br>
+ | | Software Test | The project shall record, |<br>
+ | | Report / Verification | address, and track to closure |<br>
+ | | Results | the results of software |<br>
+ | | | verification activities. |<br>
+ +----------------+-----------------------+---------------------------------+<br>
+ | Usability | Software User’s | The Software User Manual |<br>
+ | | Manual | defines user instructions for |<br>
+ | | | the software. |<br>
+ +----------------+-----------------------+---------------------------------+<br>
<br>
In an effort to remain lightweight and sustainable for open-source<br>
projects, Table 1 above was condensed into a single artifact outline<br>
-- <br>
2.17.1<br>
<br>
_______________________________________________<br>
devel mailing list<br>
<a href="mailto:devel@rtems.org" target="_blank">devel@rtems.org</a><br>
<a href="http://lists.rtems.org/mailman/listinfo/devel" rel="noreferrer" target="_blank">http://lists.rtems.org/mailman/listinfo/devel</a></blockquote></div>