SEBoK Article Review
This form provides a mechanism for you to share your thoughts and feedback on articles in the SEBoK. We encourage all members of the systems community to share their reviews.

We ask for your name and email address for two reasons: first, we would like to be able to follow up with you if we have questions or feel your review requires further discussion before we take action. Second, you have the option to receive an annual acknowledgment of the articles that you reviewed and we require your contact information in order to provide this.

Thank you for your support of the SEBoK and we look forward to hearing from you. Please reach out to us at sebok@incose.net if you have further questions.
Sign in to Google to save your progress. Learn more
Name
Email
Role *
What is the title of the article that you are reviewing? *
How knowledgeable are you on this topic? *
I am a novice
I am a recognized expert
READABILITY
The article is easy to read and understand. *
I strongly disagree
I strongly agree
Please provide insights into parts of the article that were difficult or that worked particularly well for you.
CONTENT
The article is primarily original content that appropriately references the literature. *
I strongly disagree
I strongly agree
The article is written in a descriptive manner. In other words, it describes the topic but does not give opinions on how things "should" be. *
I strongly disagree
I strongly agree
The article presents multiple perspectives as appropriate, reflecting the true body of knowledge throughout the SE community. It does not present one author’s opinion or a strongly biased perspective.
*
I strongly disagree
I strongly agree
The article linked to other SEBoK articles as appropriate.
*
I strongly disagree
I strongly agree
The article is written in a professional manner.
*
I strongly disagree
I strongly agree
What other comments do you have on the content? For example, do you feel there are links to other SEBoK articles we should add? 
GLOSSARY
Is the first instance of each glossary term linked to the glossary? *
If no, what term(s) need to be linked to the glossary?
Do you have any thoughts about the glossary terms for this article? For example, do you have strong support for or disagreement with any of the terms? Are there terms you feel we should add?
REFERENCES/CITATIONS
All references are complete, i.e. contain all the information I need to be able to find the reference for myself. *
If no, what references need to be updated?
In the reference list, all Primary References should be linked to a page that describes the reference. Do all primary references for this article link to a primary reference page? *
Please provide any additional references you think we should include. If you believe one of these references is critical to the field, please include *primary* at the end of the reference.
ADDITIONAL FEEDBACK
Please make note of any typographical errors, grammatical issues, or areas that lack clarity here.
We want to continue to improve the SEBoK. One of our current initiatives is to improve the media content.  Please provide links or references to any good videos, figures, webinars, lectures, recordings, etc. on this topic that the Editorial Board should consider including.
Are there topics that you would like to see added to the SEBoK that we do not currently have? Please provide a list of recommended topics here.
Please share any other comments with us here (whether about this article in particular or the SEBoK more broadly).
THANK YOU!
Thank you for your review of the SEBoK! The SEBoK is an effort of the global systems engineering community and we greatly appreciate your support. 
Do we have permission to contact you if we have questions about your review (e.g. if we would like additional insight based on your comments)? *

Would you like an email acknowledging your review? We will send out an email acknowledgment once a year that includes all articles reviewed (your email address is used to identify which articles you reviewed).

*
Submit
Clear form
Never submit passwords through Google Forms.
This content is neither created nor endorsed by Google. Report Abuse - Terms of Service - Privacy Policy