geração (semi)automática de metadados - Universidad Autónoma ...

Conferência IADIS Ibero-Americana WWW/Internet 2007
CIO. 2002. How to use the Balanced Scorecard.
http://www.cio.com/archive/051502/scorecard_content.html?printversion=yes. Acessed 2006.
Commerce, O. o. G. 2005. Managing Successful Projects with PRINCE2, TSO.
Demarco, T. 1997. The Deadline. New York, Dorset House Publishing.
Estublier, J., Leblang, D., Hoek, A. v. d., Conradi, R., Clemm, G., Tichy, W. e Wiborg-Weber, D., 2005. Impact of
Software Engineering Research on the Pratice of Software Configuration Management. ACM Transactions on
Software Engineering and Methodology, Vol. 14, No. 4, pp.383-430.
Ewusi-Mensah, K. 2003. Software Development Failures. Cambridge, MIT Press.
Group, S. 1998. Chaos: A recipe for success. Acessed 2006, from
http://www.standishgroup.com/sample_research/PDFpages/chaos1998.pdf.
Group, S. 2004. Taxa de sucesso de projectos. Acessed 2006, from
http://www.standishgroup.com/sample_research/PDFpages/q3-spotlight.pdf.
Horowitz, B. M. and J. H. Lambert 2006. Assembling Off-the-Shelf Components: “Learn as You Go” Systems
Engineering. IEEE TRANSACTIONS ON SYSTEMS, MAN, AND CYBERNETICS—PART A: SYSTEMS AND
HUMANS 36(2).
Hughes, B. and M. Cotterell 2002. Software Project Management (3rd Ed), McGraw-Hill.
Institute, B. S. 2000. British Standard BS6079-1:2000. Project Management-Part 1: Guide
to project management. UK.
Klein, G., Jiang, J. J. and Tesch, D. B., 2002. Wanted: Project Teams with a Blend of IS Professional Orientations.
Communications of the ACM, Vol. 45, No. 6, pp. pp.81-87.
Kolenso, K. 2001. Do The Right Projects, the Right Way.
http://www.aisc.com/us/lang_en/library/white_papers/Right_Projects_Right_Way.pdf. Acessed 2006.
Krupansky, J. W. 2003. What is Software Agent. http://agtivity.com/agdef.htm. Accessed 2006.
Lamsweerde, A. V. 2000. Formal Specification: A roadmap. The Future of Software Engineering. New York, ACM
Press: 147-159.
Laudon, K. C. and J. P. Laudon 2006. Management Information Systems: Managing the Digital Firm, Prentice Hall.
Linberg, K. 1999. Software developer perceptions about software project failure: A case study. Journal of Systems and
Software Vol. 49(2): 177-192.
Nguyen, T. N., Munson, E. V. e Boyland, J. T., 2005, An Infrastructure for Development of Object-Oriented Multi-level
Configuration Management Services. ICSE'05, St. Louis, Missouri, USA.
Norman Fenton, William Marsh, Martin Neil, Patrick Cates, Simon Forey e Tailor, M., 2004, Proceedings of the 26th
International Conference on Software Engineering (ICSE'04).
PMI 2000. PMBOK - A guide to the Project Management Body of Knowledge. Standards Comittee of The Project
Management Institute (PMI).
PMI 2004. PMBOK - A guide to the Project Management Body of Knowledge. Standards Comittee of The Project
Management Institute (PMI).
Rita Nienaber and E. Cloete 2003. A Software Agent Framework for the Support of Software Project Management.
Proceedings of SAICSIT.
Robinson, W. N., Pawlowski, S. D. and Volkov, V., 2003.Requirements interaction management. ACM Computing
Surveys 35(2): pp.132-190.
Schwalbe, K. 2002. Information Technology Project Management. Course Tecnhology.
Shenhar A, R. J., Wideman R. 1996. Improving PM: Linking Success Criteria to Project Type.
http://www.maxwideman.com/papers/improvingpm/intro.htm.
Standardization, I. O. f. 2006. Quality Management Principles from http://www.iso.org/iso/en/iso9000-
14000/understand/qmp.html.
Standish Group 1996. Unfinished Voyages .http://www.standishgroup.com/sample_research/unfinished_voyages_1.php.
Acessed 2006, from http://www.standishgroup.com/sample_research/PDFpages/chaos1998.pdf.
Susan Brock, Danyal Hendricks, Stephen Linnell, Derek Smith, 2003, A Balanced Approach to IT Management.
Procedings of SAICSIT, pp. 2-10.
Wallace, L. and M. Keil 2004. Software Project Risks and their effect on Outcomes. Communications of the ACM 47(4).
Yetton, P., Martin, A., Sharma, R. e Johnston, K., 2000. A Model of Information Systems Project Performance.
Information Systems Journal, Vol. 10, pp. 263-289.
329