|
|
| (2 intermediate revisions by 2 users not shown) |
| Line 1: |
Line 1: |
| − | Ken Zemrowski:
| + | {{Review Instructions}} |
| − | I think it might be worthwhile to note that an organization developing a process suite will need to deal with standards developed by organizations with different cultures, such as the SE standards groups, PMI, security organizations, etc. Consider risk management for example. “Everybody” seems to have processes and terminology for risk. This can get more complicated with different industries and regulatory authorities. This issue could be addressed before the final sentence of the problems paragraph by adding: "There are also instances in which standards groups for program management, safety, or other disciplines create standards on topics addressed within SE but use different terminology, culture, etc. One such example is risk management, which has been dealt with by many professional societies from different perspectives.
| |
| − | | |
| − | (Davidz, 08/22)
| |
| − | *The figures are not readable in Internet Explorer 7.
| |
| − | *From what I can see, it looks like the figures in this section are useful for seeing the comparison and alignment of the standards.
| |
| − | *For the "Approach" section, "Figure XA" should probably be "Figure 2."
| |
| − | *More than one citation should probably be noted, particularly since all the standards are referenced.
| |
| − | *Are the industry associations working collaboratively to align the systems standards with just the software engineering standards, or are there efforts to align SE standards with standards for other domains (maybe project management, mechanical engineering, etc.)?
| |
| − | *For the "Practical Considerations" section, do you want to just point to the other topic, or are you planning to talk more about "key pitfalls and good practices?"
| |
Latest revision as of 18:21, 6 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.