|
| This Article | ||
| ||
| Share | ||
| Bibliographic References | ||
| Add to: | ||
 Digg  Furl  Spurl  Blink  Simpy  Google  Del.icio.us  Y!MyWeb | ||
| Search | ||
| ||
Oi, Analyst
November/December 2009 (vol. 26 no. 6)
pp. 13-14
| ASCII Text | x | ||
| Neil Maiden, "Oi, Analyst," IEEE Software, vol. 26, no. 6, pp. 13-14, November/December, 2009. | |||
| BibTex | x | ||
| @article{ 10.1109/MS.2009.181, author = {Neil Maiden}, title = {Oi, Analyst}, journal ={IEEE Software}, volume = {26}, number = {6}, issn = {0740-7459}, year = {2009}, pages = {13-14}, doi = {http://doi.ieeecomputersociety.org/10.1109/MS.2009.181}, publisher = {IEEE Computer Society}, address = {Los Alamitos, CA, USA}, } | |||
| RefWorks Procite/RefMan/Endnote | x | ||
| TY - MGZN JO - IEEE Software TI - Oi, Analyst IS - 6 SN - 0740-7459 SP13 EP14 EPD - 13-14 A1 - Neil Maiden, PY - 2009 KW - requirements analysts KW - certification KW - IREB KW - specification VL - 26 JA - IEEE Software ER - | |||
DOI Bookmark: http://doi.ieeecomputersociety.org/10.1109/MS.2009.181
Certification for requirements analysts requires focusing on a small, possibly unrepresentative, set of tasks that might not reflect domain knowledge and could lead to good analysts not getting certified because the don't do well on the exam.
1. B. Paech, "What Is a Requirements Engineer?" IEEE Software, vol. 25, no. 4, 2008, pp. 16–17.
2. B. Curtis, H. Krasner, and N. Iscoe, "A Field Study of the Software Design Process for Large Systems," Comm. ACM, vol. 31, no. 11, 1988, pp. 1268–1287.
3. T. DeMarco Letter to the Editors, Cutter IT J., June 1998; www.systemsguild.com/GuildSite/TDMcertification.html .
Index Terms:
requirements analysts, certification, IREB, specification
Citation:
Neil Maiden, "Oi, Analyst," IEEE Software, vol. 26, no. 6, pp. 13-14, Nov.-Dec. 2009, doi:10.1109/MS.2009.181
Usage of this product signifies your acceptance of the Terms of Use.