Difference between revisions of "Talk:System Assurance"

From SEBoK
Jump to navigation Jump to search
(Replaced content with "{{Review Instructions}}")
 
(2 intermediate revisions by 2 users not shown)
Line 1: Line 1:
Tom Hilburn - Not sure I see the need for separate topcis on Security Engineering and System Assurance. Maybe that is why this topic is blank.
+
{{Review Instructions}}
There is no content in this page.
 
Consideration needs to be given as to whether this page is necessary, in the light of the comment from another author above.
 
If the conclusion is that a page addressing "systems assurance" is necessary in SEBOK then this blank stub should be included in the review so that reviewers can see that we intend to address the issue. The title seems to have suggested to the other author who has commented something related to security, but suggests to me something related to verification and validation test and evaluation. Whatever is put to the review should at least and identify the general subject matter that is intended to this page. ***Moved part on system assurance and software assurance here for the time being.  Concern was that a number of authors insisted this topic be here and so hope is to get more input during the review process, one way or the other, by keeping this topic separate.***
 

Latest revision as of 00:29, 7 November 2011

Review Instructions

Please note that in order to provide review comments, you must first log in to the wiki. Please go to Login or create an account if you do not have a username (less than 1 minute).


Please provide your feedback on this article by responding to the specific discussion points below. In order to respond, please click “Reply” under the appropriate discussion thread. Feel free to read the comments of other reviewers as well (you may also respond directly to these comments). Please note that each article has a place for “Open Discussion” – please place any comments not related to the specific discussion points into this thread.

As the BKCASE author team develops SEBoK 0.75, they will provide an adjudication comment for each ‘‘thread’’ in the discussion – not each individual comment.

Note: We value community feedback and assume that all reviewers will respond in a professional manner. However, if any reviewer uses any form of profanity or consistently posts inflammatory comments or spam messages, that reviewer’s IP address will be blocked. To report any such problems, please email bkcase@stevens.edu.