Talk:Software Engineering Institute

SEI apparently editing this page
Just a heads up about a potential conflict of interest. User:SEI Publications has edited this page in the past. See their contributions. --NightMonkey (talk) 01:30, 16 December 2008 (UTC)

Given that nobody else is editing it, and much of the material is way out of date, it seems like maybe they should be doing so. Sbs9 (talk) 20:43, 17 September 2013 (UTC)

Request for Edit
Hello, I am an employee on the corporate communications team at the Carnegie Mellon Software Engineering Institute (SEI). I’m seeking help in updating the outdated information that is currently in the Wikipedia article. I’ve included links to several resources below that contain information about the SEI and programs, and technologies. Please feel free to consult these sources as you are making updates to the article.

Thank you for your help, Dana

•	Pittsburgh Post-Gazette: http://www.post-gazette.com/pg/10182/1069538-28.stm

•	eWeek: http://www.eweek.com/c/a/Application-Development/Software-Engineering-Institute-Contract-Renewed-466589/

•	Dr. Dobb’s Journal: http://drdobbs.com/222301637

•	PCWorld: http://www.pcworld.com/article/216936/when_trusted_IT_people_go_bad.html?tk=rss_news

•	Government Info Security: http://www.govinfosecurity.com/podcasts.php?podcastID=465

•	Software Integrity Blog: http://blog.coverity.com/uncategorized/interview-with-robert-seacord-head-of-the-secure-coding-initiative-at-cert/

•	Bank Info Security: http://www.bankinfosecurity.com/podcasts.php?podcastID=823

•	On Software Engineering: http://onsoftwareengineering.com/2010/12/03/cmmi-version-1-3-and-agile/

•	About.com: http://adulted.about.com/od/learningorganizations/a/seicertificationatcarnegiemellon.htm

--CMUSEI (talk) —Preceding undated comment added 19:28, 7 April 2011 (UTC).

Outdated Info on This Page
The current entry for the Carnegie Mellon Software Engineering Institute is incomplete and out of date. The article needs to be updated to reflect current Wikipedia Content Criteria that states that “Wikipedia content is intended to be factual, notable, verifiable with cited external sources, and neutrally presented.” The Software Engineering Institute article does not currently meet these criteria.

The page also needs to be updated to reflect the styles and outlines of the Wikipedia entries of fellow Federally Funded Research and Development Centers which include concise introductions, history and origins, and organization. The article outline should follow this or a similar format:

1.	History

2.	Mission and Vision

3.	Capabilities

4.	Organization a. Acquisition Practices b. Process Management c. Security d. Software Development and System Design

5.	Notable Staff a. Watts Humphrey

History The following sources can provide an over view of the Software Engineering Institute and a brief history of the organization and its origins. •	Pittsburgh Post-Gazette: http://www.post-gazette.com/pg/10182/1069538-28.stm

•	eWeek: http://www.eweek.com/c/a/Application-Development/Software-Engineering-Institute-Contract-Renewed-466589/

•	Dr. Dobb’s Journal: http://drdobbs.com/222301637

•	About.com: http://adulted.about.com/od/learningorganizations/a/seicertificationatcarnegiemellon.htm

Mission and Vision

The mission and vision of the SEI is located on the SEI website at http://www.sei.cmu.edu/about/vision/.

Organization

The Wikipedia page currently lists several key areas of specialization within the SEI. However, each section is incorrectly labeled and only lists one or two highly specialized projects or research from that particular area within the Software Engineering Institute.

a) Acquisition Practices

The current section on the SEI’s acquisition practices should include more detail on specific programs and initiatives within the practice. Information about the SEI’s acquisition practices can be found here:

•	http://www.sei.cmu.edu/acquisition/index.cfm

•	http://www.crosstalkonline.org/storage/issue-archives/2010/201011/201011-Blanchette.pdf

b) Management Practices (Should be listed as Process Management)

This section currently focuses on the most widely recognized framework developed by the SEI, the Capability Maturity Model Integration (CMMI). However, there have been significant updates to the CMMI in the last few years including a new version of the model, V1.3. There are also other noteworthy initiatives in the Process Management area at the Software Engineering Institute; these include the Team Software Process (TSP), Personal Software Process (PSP) and the Software Engineering Measurement and Analysis Initiative.

More information about the Process Management area can be found at:

•	http://www.sei.cmu.edu/about/organization/sepm/

•	http://www.informit.com/articles/article.aspx?p=1721487 (Team Software Process and Personal Software Process)

•	http://www.informit.com/articles/article.aspx?p=1614508 (Team Software Process and Personal Software Process)

•	http://www.softtek.com/webinar/60-introduction-and-benefits-of-the-team-software-process (TSP and PSP)

•	http://www.federaltimes.com/article/20110605/ADOP06/106050302/ (CMMI)

•	http://www.thectoforum.com/content/quality-software (CMMI)

c) SQUARE and Security (should be listed as just Security)

SQUARE is only a small portion of the work that is done by the CERT Program within the Software Engineering Institute, and this entry overemphasizes its position within CERT. The CERT Program also specializes in software assurance (secure coding, vulnerability analysis, function extraction), secure systems (cyber security engineering, network situational awareness), organizational security (operational resilience, insider threat, governance), coordinated response (computer security incident response teams, forensics), and training (virtual training environment, CERT exercise network, certification).

More information about CERT Program areas of work can be found at:

•	www.cert.org

•	http://www.bankinfosecurity.com/podcasts.php?podcastID=823 (Computer security incident response teams)

•	http://www.govinfosecurity.com/podcasts.php?podcastID=465 (Insider Threat)

•	http://www.pcworld.com/article/216936/security_fail_when_trusted_it_people_go_bad.html (Insider Threat)

•	http://blog.coverity.com/uncategorized/interview-with-robert-seacord-head-of-the-secure-coding-initiative-at-cert/ (Secure Coding)

•	http://www.continuitycentral.com/news05874.html (Resilience Management)

•	http://searchsecurity.techtarget.in/tip/OCTAVE-risk-assessment-method-examined-up-close?ShortReg=1&mboxConv=searchSecurityIN_RegActivate_Submit& (Resilience Management)

•	http://community.netiq.com/blogs/security_webb/archive/2011/05/03/questions-and-answers-from-the-combat-insider-threat-webinar.aspx (Insider Threat)

•	http://articles.timesofindia.indiatimes.com/2011-08-23/infrastructure/29917886_1_power-grid-power-generation-power-ministry/2 (Smart Grid Maturity Model)

•	http://aisel.aisnet.org/cgi/viewcontent.cgi?article=1033&context=amcis2011_submissions (Software Assurance)

•	http://www.infoq.com/articles/caralli-risk-management-model (Resilience Management)

d) Engineering Practices (Should be listed as Software Development and System Design)

This section only lists two sentences for an area of specialization that covers a wide range of initiatives and research. Three key areas of work are listed on the page; however, this area needs to be expanded to include other practices like architecture-centric engineering, software product lines, system of systems, and ultra-large-scale systems.

More information on Software Development and System Design can be found at:

•	http://www.sei.cmu.edu/about/organization/rtss/

•	http://www.pearsonhighered.com/educator/product/Software-Architecture-in-Practice/9780321154958.page

Thank you for your assistance in improving the Software Engineering Institute Wikipedia page.

DaHanz (talk) 16:38, 29 September 2011 (UTC)