{"id":511,"date":"2015-07-07T16:45:26","date_gmt":"2015-07-07T11:45:26","guid":{"rendered":"http:\/\/www.stonemillkids.com\/?p=511"},"modified":"2016-09-01T21:33:07","modified_gmt":"2016-09-01T16:33:07","slug":"qms-walking-through-the-project","status":"publish","type":"post","link":"http:\/\/www.stonemillkids.com\/index.php\/2015\/07\/07\/qms-walking-through-the-project\/","title":{"rendered":"QMS &#8211; Walking through the Project"},"content":{"rendered":"<p>I am finally starting the app based of the existing Quality Management System (<a href=\"http:\/\/www.stonemillkids.com\/index.php\/2015\/06\/09\/qms-drafted-infrastructure-up-ready-to-start\/\">QMS)<\/a>.\u00a0 This post will log what feels unnatural or needs to change as I tried to implement the QMS with in my game.<\/p>\n<p><em>Note: This post is not complete, it will\u00a0be updated as I work through this project.\u00a0 However, since I am starting the walkthrough of the QMS, this is the right chronological position for this post.\u00a0<\/em><\/p>\n<p>Each section will document the <del>findings<\/del> observations that I make while trying to use it.\u00a0 If something is titled &#8220;QMS&#8221; it means that it applies to the whole QMS.\u00a0 If something has a document mnemonic in is specific to that document and it will be fixed as I find it.\u00a0 Anything that I am choosing to fix later, I am\u00a0tagging it with &#8220;TODO&#8221;<\/p>\n<p>Let&#8217;s get started&#8230;<\/p>\n<h3>Project Charter<\/h3>\n<p><strong>QMS:\u00a0It feels I <\/strong>need a Memo to explain that I am pushing through trying to find holes in the project and the QMS<\/p>\n<p><strong>QMS\u00a0TODO:<\/strong> I need a Doc numbering workflow.\u00a0 I am simple using the &#8220;SHP&#8221; mnemonic in front of the original QMS document.\u00a0 It will work for now, but adjusting it in the future may be a little cumbersome.<\/p>\n<p><strong>PC-901:<\/strong> Between the Scope, Executive Summary and Quality Objectives, the Objectives section seems like a duplicate information.\u00a0 Remove it.<\/p>\n<p><strong>PC-901:<\/strong> Move the Assumptions section from the SDD to here.<\/p>\n<p><strong>PC-901:<\/strong> Move the Target Customer from the SDD to here.<\/p>\n<h3>Requirements\u00a0&amp; Acceptance Test<\/h3>\n<p><strong>Req-901: <\/strong>Need to add a Product and Version to the title.<\/p>\n<p><strong>Req-901: <\/strong>Change the &#8220;Requirements&#8221; to &#8220;Customer Requirements&#8221;<\/p>\n<p><strong>Req-901: <\/strong>Add a &#8220;System, Performance, Legal, or Regulatory&#8221; etc. requirements. section.\u00a0 Make sure we cover all of the other requirements needed to define system performance, etc.<\/p>\n<p><strong>QMS:<\/strong>\u00a0Update the copyright notice on the templates.\u00a0 Copyright \u00ae 2015 Greg Schallert<\/p>\n<h3>Software Design Document<\/h3>\n<p><strong>SDD-901: <\/strong>Move Assumptions to the Project Charter<\/p>\n<p><strong>SDD-901: <\/strong>Make sure we have an &#8220;Other Design Requirements&#8221; section.\u00a0 This will allow the developers to document any additional requirements that are needed for the design but have not been stated by the customer.<\/p>\n<p><strong>QMS TODO: <\/strong>Since we added a requirements section to the SDD, we need to find a place to add the verification for them.\u00a0 This might be in the SDD, Project Map, Unit Tests, or Iteration Plan.\u00a0 I could also add a traceability matrix, but I&#8217;m going to wait to decide on this one until I get closer to completing the process so I can determine where this feels natural.<\/p>\n<p><strong>QMS\u00a0TODO: <\/strong>Now that I am using git, I should create a git repository. &#8211; I expect I can do this with my cloud storage and not cause too much disruption.<\/p>\n<p>SDP-902: The SDD seems a little out of place here.\u00a0 I was able to complete a fair amount of the background, but I think I really need the Project Map to be completed first.\u00a0 I am going to complete the Project Map, then come back<\/p>\n<p><strong>SDD-901:\u00a0<\/strong>Add the Project\u00a0Map (now called Project Plan) as a reference.<\/p>\n<p><strong>SDD-901:\u00a0<\/strong>Add LibGDX as a dependency and adjust the the verification accordingly.<\/p>\n<p>SDD-901: Move the Product details to the Project Charter<\/p>\n<p>The Software Development Procedure.\u00a0 There needs to be some initial\u00a0thought into the\u00a0design to generate the Project Map, but the Project Map should be completed prior to the SDD being complete.\u00a0 We will make sure the SDP is clear that the first iteration may be something like an iteration 0 were much of the investigation and initial design allows for a Project Map to be put together.\u00a0One additional item of note is that each time an iteration is completed, the Project Map, Requirements, and SDD may need to be adjusted.\u00a0 This is expected in an iterative development.\u00a0 Our goal is to take our best guess at what the next logical steps are and move forward quickly while continually asking the question &#8220;are we on the right track.&#8221;<\/p>\n<p>(Additional comments after completing a draft)<\/p>\n<p>SDD-901 TODO: The Design section towards the end needs instructions that say &#8220;Modify as Needed.&#8221;\u00a0 Some projects would be more logical if they followed a different format.\u00a0 Think MVC -vs- Procedural.<\/p>\n<p>SDD-901 TODO: Consider changing this to a more free-form document with a git repository of the design and a readme then creating a more detailed Verification plan instead.<\/p>\n<h3>Project <del>Map<\/del> Plan<\/h3>\n<p><strong>PM: <\/strong>Change the name from Project Map (PM)\u00a0to Project Plan (PP).\u00a0 It will make more sense to a larger audience.<strong>\u00a0 From this point on in the post I will be calling it a Project Plan.<\/strong><\/p>\n<p>PP: Remove the Assumptions section as it is covered in the Project Charter<\/p>\n<p>PP: Add sections to describe the Verification and Validation efforts<\/p>\n<p><strong>QMS\u00a0TODO:<\/strong> Currently most of the changeable items in the templates as well as the instructions are highlighted yellow an in italics.\u00a0 A review of all of the documentation should make this easier to use.\u00a0 For example, in many cases editing an italics text creates an extra step of formatting the text back to normal.\u00a0 Current thoughts are all instructions that should be deleted are in italics and highlighted.\u00a0 Text that could stay in the document and simply be highlighted.<\/p>\n<p><strong>PP:<\/strong> Adjusted the timeline.\u00a0 Streamline the columns so that the Plan is always forward looking (see next comment).<\/p>\n<p><strong>PP TODO:<\/strong> Review the timeline based on first and second projects.\u00a0 The first plan has time for the QMS built into it.\u00a0 The second should be a more normal timeframe.\u00a0 Once this is understood, a default &#8220;Timeline&#8221; section should offer better guidance for future products than it does today.<\/p>\n<p><strong>QMS TODO:<\/strong> Need to add a Iteration Plan so that the Project Plan, etc. does not change. &#8211; Consider simply doing Iteration Plans on GitLab.\u00a0 This way there is no duplication of effort.\u00a0 I like the idea of GitLab maintaining a timeline (maybe just monitoring the backlog) so no additional documents are required.<\/p>\n<h3>Hazards and Risk Procedure<\/h3>\n<p><strong>HA TODO:\u00a0<\/strong> Audit the HA to determine what other QMS procedures should have a HA.<\/p>\n<p><strong>HA TODO:<\/strong> Add Definitions.<\/p>\n<p><strong>HA TODO:<\/strong> Revisit towards the end or the Dev Cycle<\/p>\n<h3>Hazards and Risk Template<\/h3>\n<p><strong>QMS TODO:<\/strong> Create a standard Excel Chart &#8220;Document Template&#8221;<\/p>\n<p><strong>HAT TODO:<\/strong>\u00a0 Add instructions and a Summary page.<\/p>\n<p><strong>HAT TODO:<\/strong> Revisit towards the end or the Dev Cycle<\/p>\n<h3>Design and Development Procedure<\/h3>\n<p><strong>DDP: This has been outlined.\u00a0 It is being written as each step of the process is being executed.\u00a0<\/strong><\/p>\n<h3>General<\/h3>\n<p>All Docs:\u00a0 Confirm Dates, Versions, Copyright and TOC\u00a0are correct after all of the required edits.<\/p>\n<p>QMS: Audit the DPP, and the SDP after Shapes! has been released.<\/p>\n<h3>\u00a0Summary of Actions<\/h3>\n<p>Create the Project Charter<\/p>\n<p>Agree on the Product Requirements<\/p>\n<p>Dev does initial Design Brainstorming and comes up with the Acceptance Tests<\/p>\n<p>Acceptance Tests are reviewed by the team.<\/p>\n<p>(repeats until Req and Acpt Tests are approved)<\/p>\n<p>Dev Team creates a GitLab project and determines approximate schedule.<\/p>\n<p>&#8211; GitLab wiki is created.<\/p>\n<p>Project Plan is drafted and reviewed (repeats until approved)<\/p>\n<p>Dev ends any pilot projects<\/p>\n<p>SDD is drafted by the Dev Team (not approved yet).<\/p>\n<p>HA is drafted.\u00a0 Adjustments to the Req and SDD are made.<\/p>\n<p>HA and SDD are approved.<\/p>\n<p>V&amp;V is adjusted based on the HA and SDD.<\/p>\n<p>&nbsp;<\/p>\n<p>&nbsp;<\/p>\n","protected":false},"excerpt":{"rendered":"<p>I am finally starting the app based of the existing Quality Management System (QMS).\u00a0 This post will log what feels unnatural or needs to change as I tried to implement the QMS with in my game. Note: This post is not complete, it will\u00a0be updated as I work through this project.\u00a0 However, since I am [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":739,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[44,12],"tags":[45,46],"_links":{"self":[{"href":"http:\/\/www.stonemillkids.com\/index.php\/wp-json\/wp\/v2\/posts\/511"}],"collection":[{"href":"http:\/\/www.stonemillkids.com\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/www.stonemillkids.com\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/www.stonemillkids.com\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/www.stonemillkids.com\/index.php\/wp-json\/wp\/v2\/comments?post=511"}],"version-history":[{"count":2,"href":"http:\/\/www.stonemillkids.com\/index.php\/wp-json\/wp\/v2\/posts\/511\/revisions"}],"predecessor-version":[{"id":814,"href":"http:\/\/www.stonemillkids.com\/index.php\/wp-json\/wp\/v2\/posts\/511\/revisions\/814"}],"wp:featuredmedia":[{"embeddable":true,"href":"http:\/\/www.stonemillkids.com\/index.php\/wp-json\/wp\/v2\/media\/739"}],"wp:attachment":[{"href":"http:\/\/www.stonemillkids.com\/index.php\/wp-json\/wp\/v2\/media?parent=511"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.stonemillkids.com\/index.php\/wp-json\/wp\/v2\/categories?post=511"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.stonemillkids.com\/index.php\/wp-json\/wp\/v2\/tags?post=511"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}