|
| This Article | ||
| ||
| Share | ||
| Bibliographic References | ||
| Add to: | ||
| | ||
| Search | ||
| ||
| ASCII Text | x | ||
| Ramkumar Ramaswamy, "Mentoring Object-Oriented Projects," IEEE Software, vol. 18, no. 3, pp. 36-40, May/June, 2001. | |||
| BibTex | x | ||
| @article{ 10.1109/52.922723, author = {Ramkumar Ramaswamy}, title = {Mentoring Object-Oriented Projects}, journal ={IEEE Software}, volume = {18}, number = {3}, issn = {0740-7459}, year = {2001}, pages = {36-40}, doi = {http://doi.ieeecomputersociety.org/10.1109/52.922723}, publisher = {IEEE Computer Society}, address = {Los Alamitos, CA, USA}, } | |||
| RefWorks Procite/RefMan/Endnote | x | ||
| TY - MGZN JO - IEEE Software TI - Mentoring Object-Oriented Projects IS - 3 SN - 0740-7459 SP36 EP40 EPD - 36-40 A1 - Ramkumar Ramaswamy, PY - 2001 VL - 18 JA - IEEE Software ER - | |||
DOI Bookmark: http://doi.ieeecomputersociety.org/10.1109/52.922723
Mentors are crucial for an organization that is learning object orientation, particularly when much of the learning must occur on live projects. The mentor must be architect, design consultant, and educator on process and language issues. This multifaceted role presents unique challenges. The author describes issues he has faced as a mentor on a number of OO application development projects.
Citation:
Ramkumar Ramaswamy, "Mentoring Object-Oriented Projects," IEEE Software, vol. 18, no. 3, pp. 36-40, May-June 2001, doi:10.1109/52.922723
Usage of this product signifies your acceptance of the Terms of Use.

