IEEE Computer Society Certified Software Development Professional ...


Published on

  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

IEEE Computer Society Certified Software Development Professional ...

  1. 1. IEEE Computer Society Certified Software Development Professional (CSDP) Exam _________________ Overview and Discussion Presented to SASQAG By Leonard L. Tripp 18 April 2002
  2. 2. AGENDA <ul><li>Background - What is the IEEE Computer Society? - What is the IEEE Computer Society CSDP? - History of Effort - Examination Results & Future Examinations </li></ul><ul><li>The Process of Becoming an IEEE CS CSDP - Application Steps - Requirements for Certification - Preparation for the Examination - Results from the Examination - Follow-up Activities </li></ul><ul><li>Body of Knowledge </li></ul><ul><li>Discussion Q&A </li></ul>
  3. 3. What is the IEEE Computer Society? <ul><li>The IEEE Computer Society is the world’s oldest and largest association of computing professionals </li></ul><ul><li>Its vision is to be …”the leading provider of technical information and services to the world’s computing professionals.” </li></ul><ul><li>The IEEE CS is the largest of the societies and councils organized under the IEEE. </li></ul>
  4. 4. IEEE CS Products & Services <ul><li>Publications </li></ul><ul><ul><li>11 Magazines & 10 Transactions </li></ul></ul><ul><ul><li>Over 150 Conference Proceedings annually </li></ul></ul><ul><li>157 student and 176 professional chapters worldwide </li></ul><ul><li>Educational Activities, including Computing Curricula, accreditation activities, and continuing education offerings </li></ul><ul><li>Conferences: over 150 sponsored or cosponsored meetings annually </li></ul>
  5. 5. IEEE CS Products and Services (continued) <ul><li>9 Standards Sponsors and over 200 Standards working groups </li></ul><ul><ul><li>Robust software engineering standards activities </li></ul></ul><ul><li>34 technical committees and councils plus plus 9 task forces </li></ul><ul><li>New Member Benefit in 2002 </li></ul><ul><ul><li>100+ Distance Learning Courses free with membership </li></ul></ul>
  6. 6. What is Certification ? <ul><li>Formal recognition that that an individual has demonstrated a proficiency within and comprehension of a specified body of knowledge at a point in time . </li></ul><ul><li>It is peer recognition and not registration or licensure . </li></ul><ul><ul><li>Registration: listing by & with a body of those individuals or organizations that are certified </li></ul></ul><ul><ul><li>Licensure: authorization granted by government body for an individual or organization to practice a business or occupation </li></ul></ul>
  7. 7. Why Become Certified? <ul><li>Mark of Excellence : demonstrates the certified individual has the knowledge to ensure that recognized principles and practices of software engineering are being used </li></ul><ul><li>Competition in the Marketplace: companies and organizations need a work force proficient in principles and practices of software engineering </li></ul><ul><li>Recognition: Customer confidence based on your evidence of qualifications and suitability for the task or project </li></ul>
  8. 8. Why Become Certified? <ul><li>Investment: certification is an investment in your career and the future of your employer </li></ul><ul><li>Continuous improvement: to remain certified requires you to continue your education and involvement in software engineering-related work and activities. Your skills remain current and your flexibility to work on a variety of projects or for a variety of companies improves. </li></ul>
  9. 9. Without Certification <ul><li>Couldn’t I do all this without certification? - Perhaps, if properly motivated. An individual could be a great inventor or writer without a formal education, if properly motivated. Certification is not a guarantee, but rather an indicator. </li></ul>
  10. 10. What is a CSDP? <ul><li>A C ertified S oftware D evelopment P rofessional : </li></ul><ul><li>Possesses fundamental knowledge and understanding of computing principles and concepts and their application to the definition, design, construction, testing, and of software. </li></ul><ul><li>Is able to provide appropriate design with technical and economic tradeoffs of modules, subsystems, and systems in accordance with standards of practice, specifications, and principles of behavior of software as required to perform the functions as stated in the software requirements. </li></ul><ul><li>Has met the IEEE CS CSDP education, experience, and examination requirements </li></ul>
  11. 11. History of Effort <ul><li>1976-1998 - IEEE Transactions on Software Engineering was founded in 1976. - Computer Society organized software engineering standards committee in 1978. - Computer Society founded ad hoc committee to promote the professionalization of software engineering in 1992 - Computer Society conducted pilot program, “Doing Software Right,” to explore options on promoting software engineering practices during 1997-1998 which resulted in the decision to pursue a certification program </li></ul><ul><li>Spring 1999 - Contract with Chauncey Group International was negotiated - Steering committee consisting of Don Bagert, Richard Fairley, and Steve Tockey was formed - Job Analysis workshop was held in April 1999 at Oregon Graduate Institute near Portland involving 13 volunteers. </li></ul>
  12. 12. History of Effort (continued) <ul><li>Summer 1999 - Job analysis was reviewed and refined - Job analysis was distributed to cross-section </li></ul><ul><li>Fall-Winter 1999 - Finalization of tasks and associated knowledge statements that were to be included in the certification examination - Finalization of test content percentages - Linkages between knowledge and task statements were defined to guide test development </li></ul><ul><li>Spring 2000 - Test item writing held in Houston, Texas with about 20 participants. Over 600 test items were developed and completed their initial technical review - Jorge Hererra-Diaz was added to the Steering Committee </li></ul>
  13. 13. History of Effort <ul><li>1976-1998 </li></ul><ul><ul><li>IEEE Trans. On Software Engineering , Software Engineering Standards Committee, Ad Hoc Committee founded to promote professionalism, Pilot Program for “Doing Software Right ” </li></ul></ul><ul><li>Spring 1999-Fall 2000 </li></ul><ul><ul><li>Worked with the Chauncey Group on job analysis, test item writing & test item review </li></ul></ul><ul><ul><li>SWEBOK knowledge areas were used in CSDP bulletin for experience definition and study material list organization </li></ul></ul>
  14. 14. History of Effort (continued) <ul><li>Spring 2001 - 79% of beta test participants achieved a passing score </li></ul><ul><li>- A beta test version of the exam was assembled - Beta test participants were recruited from Argentina, Brazil, Canada, China, India, Japan, Russia, Switzerland, U.S.A and the U.K. - Average age of participants was 41 with 9.8 years of industry experience. </li></ul><ul><li>Spring 2002 - First regular examination </li></ul>
  15. 15. Collateral Project <ul><li>Guide to Software Engineering Body of Knowledge </li></ul><ul><li>Project sponsor – IEEE Computer Society </li></ul><ul><li>Project duration – 1998 – May 2001 </li></ul><ul><li>Editorial team – Alain Abran, James Moore, Robert Dupuis, Pierre Bourque </li></ul><ul><li>Corporate sponsors – ACM, Boeing, CCPE, Construx Software, MITRE, NIST, National Research Council Canada, Rational, Raytheon, SAP Labs </li></ul><ul><li>Project manager – University of Quebec at Montreal </li></ul><ul><li>Review process – three review cycles with over 500 participants from 41 countries produced nearly 10, 000 comments. All comments and their associated dispositions are available at </li></ul>
  16. 16. SWEBOK Objectives <ul><li>Characterize the contents of the Body of Knowledge </li></ul><ul><li>Provide a topical access structure </li></ul><ul><li>Promote a consistent view of software engineering worldwide </li></ul><ul><li>Clarify the place of, and set the boundary with respect to other disciplines </li></ul><ul><li>Provide a foundation for education and licensing </li></ul>
  17. 17. The Process of Becoming a IEEE Computer Society CSDP <ul><li>Application Steps </li></ul><ul><li>Requirements for Certification </li></ul><ul><li>Preparation for Examination </li></ul><ul><li>Examination </li></ul><ul><li>Results from the Examination </li></ul><ul><li>Follow-up Activities </li></ul>
  18. 18. Application Steps <ul><li>Obtain CSDP Candidate Brochure from IEEE Computer Society </li></ul><ul><li>Review Requirements in Brochure </li></ul><ul><li>Complete Application in Brochure </li></ul><ul><li>Send Completed Application to IEEE CS by Deadline with Fee </li></ul><ul><li>Acknowledgement of Payment </li></ul><ul><li>Review of Application </li></ul><ul><li>If Accepted, Authorization to Test sent to Candidate </li></ul>
  19. 19. Requirements for CSDP Certification <ul><li>Education - Baccalaureate or equivalent university degree </li></ul><ul><li>Experience - 9,000 hours of experience in 6 of the 11 software engineering knowledge areas listed in the brochure </li></ul><ul><li>Proof of Professionalism - Review and acknowledge the Software Engineering Code of Ethics and Professional Practice </li></ul><ul><li>Examination - Pass the CSDP written examination </li></ul>
  20. 20. Preparation for the Examination <ul><li>Depends on level of expertise in areas covered by Body of Knowledge </li></ul><ul><li>Focus on areas needing the most review </li></ul><ul><li>Study from the suggested reference material </li></ul><ul><li>Can take a refresher course </li></ul><ul><li>Unless your background covers most of the Body of Knowledge, allow three months of 2-4 hours a week for study </li></ul><ul><li>Last week: assemble test access materials. </li></ul>
  21. 21. Examination <ul><li>Format - Multiple-choice questions selected from a pool of questions across each of the knowledge areas - Total of 180 questions on the examination - Closed book, calculators provided - Computer-based test </li></ul><ul><li>Length </li></ul><ul><ul><li>Four hours </li></ul></ul><ul><li>Administration - Conducted by qualified proctors who will register you and check to ensure all exam admission documentation are acceptable - No copy of questions are allowed, proctor cannot answer any questions concerning the examination </li></ul>
  22. 22. Results from the Examination <ul><li>When - At the end of the examination, the exam results will immediately appear on the computer screen. - A hard copy of the score will be provided at the testing center - Within four weeks after the exam, notification by mail </li></ul><ul><li>Passing Score - Scale scores range from 120 to 200 with passing score of 170 - Systematic procedure, judgment of IEEE CS members and CGI, and IEEE CS Certification Committee all are involved in determining what a passing score is on each individual exam </li></ul>
  23. 23. Results from the Examination (continued) <ul><li>Pass : letter of congratulation from Certification Committee, certificate for framing, your name published in the society’s flagship magazine, Computer and on our web site </li></ul><ul><li>Fail : analysis of the complete exam outline areas on which you should focus studies, allowed to take the exam within [to be determined] </li></ul>
  24. 24. Results from the Examination (continued) <ul><li>Recertification Application - Log all Recertification Units & Continuing Education Units </li></ul><ul><li>Confidentiality - No information concerning scores is distributed to anyone (including you), no analysis given to those who pass, no information about the certification is divulged to third parties (e.g., employers) except at the written request of the person who took the exam </li></ul>
  25. 25. Follow-up Activities <ul><li>Responsibilities of CSDP - Signed statement to acknowledge review of the Software Engineering Code of Ethics and Professional Practice </li></ul><ul><li>Meaning of Certificate - IEEE CS certification is not a license, always refer to IEEE in using the term “CSDP”, for example say IEEE Computer Society CSDP not just CSDP </li></ul><ul><li>Recertification - Every 3 years - Requires 30 recertification credits - Pay fee </li></ul>
  26. 26. Distribution of Questions Per Knowledge Area <ul><li>Business Practices & Engineering Economics (3-4%) </li></ul><ul><li>Software Requirements (13-15%) </li></ul><ul><li>Software Design (22-24%) </li></ul><ul><li>Software Construction (10-12%) </li></ul><ul><li>Software Testing (15-17%) </li></ul><ul><li>Software Maintenance (3-5%) </li></ul><ul><li>Software Configuration Management (3-4%) </li></ul><ul><li>Software Engineering Management (10-12%) </li></ul><ul><li>Software Engineering Process (2-4%) </li></ul><ul><li>Software Tools and Methods (2-4%) </li></ul><ul><li>Software Quality (6-8%) </li></ul>Knowledge Area (% of questions on exam)
  27. 27. General References Either of the following books is recommended as a general overview : Software Engineering: A Practitioner’s Approach , 5th ed., Pressman, Roger S., New York, New York: McGraw-Hill, 2000. Software Engineering , Sommerville, I., 6th ed. Reading, Massachusetts: Addison-Wesley, 2000. The following books are suggested as general supplemental reading: Software Engineering Vol. 1: The Development Process, 2 nd Edition . Dorfman, M. & Thayer, R., eds., Los Alamitos, California: IEEE Computer Society Press, 2002. Software Engineering Vol. 2: The Supporting Processes, 2 nd Edition. Thayer, R. and M. Christensen, eds., Los Alamitos, California: IEEE Computer Society Press, 2002. IEEE Software Engineering Collection, 1999, vols. 1-4.
  28. 28. General Supplemental Reading <ul><li>The following books are suggested as general supplemental reading: </li></ul><ul><li>Software Engineering Vol. 1: The Development Process, 2 nd Edition . Dorfman, M. & Thayer, R., eds., Los Alamitos, California: IEEE Computer Society Press, 2002. </li></ul><ul><li>Software Engineering Vol. 2: The Supporting Processes, 2 nd Edition. Thayer, R. and M. Christensen, eds., Los Alamitos, California: IEEE Computer Society Press, 2002. </li></ul><ul><li>IEEE Software Engineering Collection, 1999, vols. 1-4. Piscataway, New Jersey: IEEE. </li></ul>
  29. 29. Test Schedule <ul><li>2002 15 May – 30 June 5-26 October </li></ul><ul><li>2003 1-30 April 1-31 October </li></ul>
  30. 30. Discussion: Q & A <ul><li>Examination Process </li></ul><ul><li>Examination Materials </li></ul><ul><li>Benefits and Costs </li></ul><ul><li>Comments from IEEE Computer Society </li></ul>
  31. 31. For More Information <ul><li>Stacy Saul, Continuing Education Coordinator </li></ul><ul><li>IEEE Computer Society 1730 Massachusetts Ave., NW Washington, DC 20036-1992 </li></ul><ul><li>Voice: +1 202-371-0101 </li></ul><ul><li>Fax: +1 202-728-0884 </li></ul><ul><li>E-mail address: [email_address] </li></ul><ul><li>Web address: </li></ul>
  32. 32. <ul><li>Background Material </li></ul>
  33. 33. 1. Business Practices and Engineering Economics <ul><li>Engineering Economics </li></ul><ul><li>Ethics </li></ul><ul><li>Professional Practice </li></ul><ul><li>Standards </li></ul>Key References No book-length references are recommended for this topic. The following books are suggested as supplemental reading in this area: Morality and Machines: Perspectives on Computer Ethics, Edgar, S. L., Sudbury, Massachusetts: Jones and Bartlett, 1997. Computer Ethics, 2d Ed., Johnson, Deborah G, Upper Saddle River, NJ: Prentice-Hall, 1994. Smith and Roberson’s Business Law, 11th ed., Mann, Richard A., & Barry S. Roberts, Cincinnati, OH: West Thomson Learning, 2000. Engineering Economy, Thusen, G.J., Prentice-Hall, 2000.
  34. 34. 2. Software Requirements A. Requirements Engineering Process B. Requirements Elicitation C. Requirements Analysis D. Software Requirements Specification E. Requirements Validation F. Requirements Management Key References Any one of the following books is recommended in this area: Software Requirements: Objects, Functions, & States, Davis, Alan. Upper Saddle River, New Jersey: Prentice Hall, 1993. Practical Software Requirements: A Manual of Content and Style, Kovitz, Benjamin L., Manning Publications Company, 1998. Mastering the Requirements Process, Robertson, James and Suzanne Robertson, New York: Dorset House, 2000. Requirements Engineering: A Good Practice Guide, Sommerville, Ian, New York: John Wiley & Sons, 1997. Software Requirements, Wiegers, Karl. Microsoft Press, 1999.
  35. 35. 3. Software Design A. Software Design Concepts B. Software Architecture C. Software Design Quality Analysis and Evaluation D. Software Design Notations and Documentation E. Software Design Strategies and Methods F. Human Factors in Software Design G. Software and System Safety Key References Any one of the following books is recommended in this area: Software Architecture in Practice, Bass, Len, Paul Clements and Rick Kazman. Reading, Massachusetts: Addison-Wesley, 1998. Pattern Oriented Software Architecture: A System of Patterns, Buschmann, Frank, et al, John Wiley & Sons, 1996. Fundamentals of Object-Oriented Design in UML, Page-Jones, Meilir, Addison-Wesley, 1999. The following books are suggested as supplemental reading in this area: Fundamentals of Database Systems, Elmasri, Ramez and Shamkant Navathe, 3d Ed., Reading, Mass.: Addison Wesley, 2000. Software Reuse: Architecture, Process and Optimization for Business Success, Jacobsen, Ivar, Martin Griss, and Patrik Jonson, Reading, Massachusetts: Addison-Wesley, 1997.
  36. 36. 4. Software Construction A. Construction planning B. Code design C. Data design and management D. Error processing E. Source code organization F. Code documentation G. Construction QA H. System integration and deployment I. Code tuning J. Construction tools Key References The following book is recommended on this topic: Code Complete, McConnell, Steve, Microsoft Press, 1993. The following books are suggested as supplemental reading in this area: The Practice of Programming, Kernighan, Brian W. and Rob Pike, Reading, Mass.: Addison Wesley, 1999. The Pragmatic Programmer: From Journeyman to Master, Hunt, Andrew, David Thomas, and Ward Cunningham, Reading, Mass.: Addison Wesley, 1999.
  37. 37. 5. Software Testing A. Types of Tests B. Test Levels C. Testing Strategies D. Test Design E. Test Coverage of Code F. Test Coverage of Specifications G. Test Execution H. Test Documentation I. Test Management Key References Any one of the following books is recommended in this area: Testing Object-Oriented Systems, Binder, Robert V. Reading, Massachusetts: Addison-Wesley, 2000. Complete Guide to Software Testing, 2nd Ed., Hetzel, Bill, New York, New York: John Wiley & Son, 1993. Software Testing : A Craftsman's Approach, Jorgensen, Paul C. CRC Press, 1995. Testing Computer Software, 2nd Ed., Kaner, Clem, Jack Falk, and Hung Quoc Nguyen, New York, New York: John Wiley and Sons, 1999. Software Testing and Continuous Quality Improvement, Lewis, William. CRC Press 2000. The Craft of Software Testing: Subsystems Testing Including Object-Based and Object-Oriented Testing, Marick, Brian. Prentice Hall, 1997.
  38. 38. 6. Software Maintenance A. Software Maintainability B. Software Maintenance Process C. Software Maintenance Measurement D. Software Maintenance Planning E. Software Maintenance Management F. Software Maintenance Documentation Key References The following book is recommended on this topic: Practical Software Maintenance, Pigoski, Thomas M. New York, Wiley Computer Publishing, 1997.
  39. 39. 7. Software Configuration Management A. Management of SCM Process B. Software Configuration Identification C. Software Configuration Control D. Software Configuration Status Accounting E. Software Configuration Auditing F. Software Release Management and Delivery Key References IEEE Standards 828-1990 and 1042-1987
  40. 40. 8. Software Engineering Management A. Measurement B. Organizational Management and Coordination C. Initiation and Scope Definition D. Planning E. Software Acquisition F. Enactment G. Risk Management H. Review and Evaluation I. Project Close Out J. Post-closure Activities Key References Any one of the following books is recommended in this area: Principles of Software Engineering Management, Gilb, Tom, Reading, Mass.: Addison Wesley, 1988. Rapid Development, McConnell, Steve, Microsoft Press, 1996. Software Engineering Project Management, 2d ed, Thayer, Richard H., IEEE Computer Society Press, Los Alamitos, CA 1997 Quality Software Management, Vol. 1, Systems Thinking, Weinberg, Gerald M.. New York: Dorset House, 1992. The following book is suggested as supplemental reading in this area: Developing Managerial Skills in Engineering and Scientist, Badawy, Michael K. Van Hostrand, NY, 1995
  41. 41. 9. Software Engineering Process A. Process Infrastructure B. Process Measurement C. Process Definition D. Qualitative Process Analysis E. Process Implementation and Change Key References Either of the following books is recommended in this area: The Capability Maturity Model: Guidelines for Improving the Software Process, Paulk, Mark, et al (Carnegie Mellon University / Software Engineering Institute). Reading, Mass.: Addison Wesley, 1995. Managing the Software Process, Humphrey, Watts S. Reading, Massachusetts, Addison-Wesley, 1989.
  42. 42. 10. Software Tools and Methods A. Management Tools and Methods B. Development Tools and Methods C. Maintenance Tools and Methods D. Support Tools and Methods Key References No book-length references are recommended for this topic .
  43. 43. 11. Software Quality A. Software Quality Concepts B. Planning for SQA and V&V C. Methods for SQA and V&V D. Measurement Applied to SQA and V&V Key References No book-length references are recommended for this topic. The following books are suggested as supplemental reading in this area: Software Engineering, Dorfman, M. & Thayer, R., eds. Los Alamitos, California: IEEE Computer Society Press, 1997. Software Inspection, Gilb, Tom., and Dorothy Graham, Reading, MA, Addison-Wesley, 1994. Practical Guide to Software Quality Management, Horch, John, Artech House, 1996. A Discipline for Software Engineering, Humphrey, Watts S. Reading, Massachusetts: Addison-Wesley, 1995. Metrics and Models in Software Quality Engineering, Kan, Stephen H. Addison Wesley, 1995.