IEEE Computer Society Certified Software Development Professional

IEEE Computer SocietyIEEE Computer SocietyCertified Software DevelopmentCertified Software Development

Professional (CSDP) ExamProfessional (CSDP) Exam__________________________________

Overview and DiscussionOverview and Discussion

Presented to SASQAGPresented to SASQAG

By Leonard L. TrippBy Leonard L. Tripp18 April 200218 April 2002

IEEECOMPUTERSOCIETY © 2002, IEEE. Permission is granted to reproduce with modification.

AGENDAAGENDA BackgroundBackground

- What is the IEEE Computer Society?- What is the IEEE Computer Society?- What is the IEEE Computer Society CSDP?- What is the IEEE Computer Society CSDP?- History of Effort- History of Effort- Examination Results & Future Examinations- Examination Results & Future Examinations

The Process of Becoming an IEEE CS CSDPThe Process of Becoming an IEEE CS CSDP- Application Steps- Application Steps- Requirements for Certification- Requirements for Certification- Preparation for the Examination- Preparation for the Examination- Results from the Examination- Results from the Examination- Follow-up Activities- Follow-up Activities

Body of KnowledgeBody of Knowledge Discussion Q&ADiscussion Q&A


What is the What is the IEEE Computer Society?IEEE Computer Society?

The IEEE Computer Society is the world’s The IEEE Computer Society is the world’s oldest and largest association of computing oldest and largest association of computing professionalsprofessionals

Its vision is to be …”the leading provider of Its vision is to be …”the leading provider of technical information and services to the technical information and services to the world’s computing professionals.” world’s computing professionals.”

The IEEE CS is the largest of the societies The IEEE CS is the largest of the societies and councils organized under the IEEE. and councils organized under the IEEE.


IEEE CS Products & IEEE CS Products & ServicesServices

PublicationsPublications 11 Magazines & 10 Transactions11 Magazines & 10 Transactions Over 150 Conference Proceedings annually Over 150 Conference Proceedings annually

157 student and 176 professional chapters 157 student and 176 professional chapters worldwideworldwide

Educational Activities, including Computing Educational Activities, including Computing Curricula, accreditation activities, and Curricula, accreditation activities, and continuing education offeringscontinuing education offerings

Conferences: over 150 sponsored or Conferences: over 150 sponsored or cosponsored meetings annuallycosponsored meetings annually


IEEE CS Products and IEEE CS Products and ServicesServices

(continued)(continued) 9 Standards Sponsors and over 200 Standards 9 Standards Sponsors and over 200 Standards

working groupsworking groups Robust software engineering standards Robust software engineering standards

activitiesactivities 34 technical committees and councils plus 34 technical committees and councils plus

plus 9 task forcesplus 9 task forces New Member Benefit in 2002New Member Benefit in 2002

100+ Distance Learning100+ Distance Learning Courses free with Courses free with membershipmembership


What is CertificationWhat is Certification?? Formal recognition that that an individual has Formal recognition that that an individual has

demonstrated a proficiency within and demonstrated a proficiency within and comprehension of a specified body of knowledge at a comprehension of a specified body of knowledge at a point in timepoint in time. .

It is peer recognition and It is peer recognition and not registration or licensurenot registration or licensure.. Registration:Registration: listing by & with a body of those individuals or listing by & with a body of those individuals or

organizations that are certifiedorganizations that are certified Licensure:Licensure: authorization granted by government body for authorization granted by government body for

an individual or organization to practice a business or an individual or organization to practice a business or occupationoccupation


Why Become Certified?Why Become Certified? Mark of ExcellenceMark of Excellence:: demonstrates the certified demonstrates the certified

individual has the knowledge to ensure that individual has the knowledge to ensure that recognized principles and practices of software recognized principles and practices of software engineering are being used engineering are being used

Competition in the Marketplace:Competition in the Marketplace: companies and companies and organizations need a work force proficient in organizations need a work force proficient in principles and practices of software engineeringprinciples and practices of software engineering

Recognition:Recognition: Customer confidence based on Customer confidence based on your evidence of qualifications and suitability for your evidence of qualifications and suitability for the task or projectthe task or project


Why Become Certified?Why Become Certified? Investment:Investment: certification is an investment in certification is an investment in

your career and the future of your employeryour career and the future of your employer Continuous improvement:Continuous improvement: to remain certified to remain certified

requires you to continue your education and requires you to continue your education and involvement in software engineering-related involvement in software engineering-related work and activities. Your skills remain current work and activities. Your skills remain current and your flexibility to work on a variety of and your flexibility to work on a variety of projects or for a variety of companies improves.projects or for a variety of companies improves.


Without CertificationWithout Certification Couldn’t I do all this without certification?Couldn’t I do all this without certification?

- Perhaps, if properly motivated. An - Perhaps, if properly motivated. An individual could be a great inventor or individual could be a great inventor or writer without a formal education, if writer without a formal education, if properly motivated. Certification is not a properly motivated. Certification is not a guarantee, but rather an indicator.guarantee, but rather an indicator.


What is a CSDP?What is a CSDP? A A CCertified ertified SSoftware oftware DDevelopment evelopment PProfessionalrofessional: : Possesses Possesses fundamental knowledge and understanding of fundamental knowledge and understanding of

computing principles and concepts and their applicationcomputing principles and concepts and their application to to the definition, design, construction, testing, and of software. the definition, design, construction, testing, and of software.

Is able to provide Is able to provide appropriate designappropriate design with with technical and technical and economic tradeoffseconomic tradeoffs of modules, subsystems, and systems of modules, subsystems, and systems in in accordance with standards of practice, specifications, and accordance with standards of practice, specifications, and principles of behaviorprinciples of behavior of software as required to perform the of software as required to perform the functions as stated in the software requirements.functions as stated in the software requirements.

Has met the IEEE CS CSDP education, experience, and Has met the IEEE CS CSDP education, experience, and examination requirementsexamination requirements


History of EffortHistory of Effort 1976-19981976-1998

- - IEEE Transactions on Software EngineeringIEEE Transactions on Software Engineering was founded in 1976. was founded in 1976.- Computer Society organized software engineering standards committee in - Computer Society organized software engineering standards committee in 1978.1978.- Computer Society founded ad hoc committee to promote the - Computer Society founded ad hoc committee to promote the professionalization of software engineering in 1992professionalization of software engineering in 1992- Computer Society conducted pilot program, “Doing Software Right,” to - Computer Society conducted pilot program, “Doing Software Right,” to explore options on promoting software engineering practices during 1997-1998 explore options on promoting software engineering practices during 1997-1998 which resulted in the decision to pursue a certification programwhich resulted in the decision to pursue a certification program

Spring 1999Spring 1999- Contract with Chauncey Group International was negotiated- Contract with Chauncey Group International was negotiated- Steering committee consisting of Don Bagert, Richard Fairley, and Steve - Steering committee consisting of Don Bagert, Richard Fairley, and Steve Tockey was formedTockey was formed- Job Analysis workshop was held in April 1999 at Oregon Graduate Institute - Job Analysis workshop was held in April 1999 at Oregon Graduate Institute near Portland involving 13 volunteers.near Portland involving 13 volunteers.


History of EffortHistory of Effort(continued)(continued)

Summer 1999Summer 1999- Job analysis was reviewed and refined- Job analysis was reviewed and refined- Job analysis was distributed to cross-section- Job analysis was distributed to cross-section

Fall-Winter 1999Fall-Winter 1999- Finalization of tasks and associated knowledge statements - Finalization of tasks and associated knowledge statements that were to be included in the certification examinationthat were to be included in the certification examination- Finalization of test content percentages- Finalization of test content percentages- Linkages between knowledge and task statements were - Linkages between knowledge and task statements were defined to guide test developmentdefined to guide test development

Spring 2000Spring 2000- Test item writing held in Houston, Texas with about 20 - Test item writing held in Houston, Texas with about 20 participants. Over 600 test items were developed and participants. Over 600 test items were developed and completed their initial technical reviewcompleted their initial technical review- Jorge Hererra-Diaz was added to the Steering Committee- Jorge Hererra-Diaz was added to the Steering Committee


History of EffortHistory of Effort 1976-19981976-1998

IEEE Trans. On Software EngineeringIEEE Trans. On Software Engineering, Software , Software Engineering Standards Committee, Ad Hoc Engineering Standards Committee, Ad Hoc Committee founded to promote professionalism, Pilot Committee founded to promote professionalism, Pilot Program for “Doing Software RightProgram for “Doing Software Right” ”

Spring 1999-Fall 2000Spring 1999-Fall 2000 Worked with the Chauncey Group on job analysis, Worked with the Chauncey Group on job analysis,

test item writing & test item reviewtest item writing & test item review SWEBOK knowledge areas were used in CSDP SWEBOK knowledge areas were used in CSDP

bulletin for experience definition and study material bulletin for experience definition and study material list organizationlist organization


History of EffortHistory of Effort (continued)(continued) Spring 2001Spring 2001

- 79% of beta test participants achieved a passing score- 79% of beta test participants achieved a passing score- A beta test version of the exam was assembled- A beta test version of the exam was assembled- Beta test participants were recruited from Argentina, - Beta test participants were recruited from Argentina, Brazil, Canada, China, India, Japan, Russia, Brazil, Canada, China, India, Japan, Russia, Switzerland, U.S.A and the U.K.Switzerland, U.S.A and the U.K.- Average age of participants was 41 with 9.8 years of - Average age of participants was 41 with 9.8 years of industry experience.industry experience.

Spring 2002Spring 2002- - First regular examinationFirst regular examination


CollateralCollateral Project ProjectGuide to Software Engineering Body of

Knowledge• Project sponsor – IEEE Computer Society• Project duration – 1998 – May 2001• Editorial team – Alain Abran, James Moore, Robert

Dupuis, Pierre Bourque• Corporate sponsors – ACM, Boeing, CCPE, Construx

Software, MITRE, NIST, National Research Council Canada, Rational, Raytheon, SAP Labs

• Project manager – University of Quebec at Montreal• 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 www.swebok.org


SWEBOK ObjectivesSWEBOK Objectives Characterize the contents of the Body of Characterize the contents of the Body of

KnowledgeKnowledge Provide a topical access structureProvide a topical access structure Promote a consistent view of software Promote a consistent view of software

engineering worldwideengineering worldwide Clarify the place of, and set the boundary with Clarify the place of, and set the boundary with

respect to other disciplinesrespect to other disciplines Provide a foundation for education and Provide a foundation for education and

licensinglicensing


The Process of Becoming aThe Process of Becoming aIEEE Computer Society CSDPIEEE Computer Society CSDP

Application StepsApplication Steps Requirements for Requirements for

CertificationCertification Preparation for ExaminationPreparation for Examination ExaminationExamination Results from the Results from the

ExaminationExamination Follow-up ActivitiesFollow-up Activities


Application StepsApplication Steps Obtain CSDP Candidate Brochure from IEEE Obtain CSDP Candidate Brochure from IEEE

Computer SocietyComputer Society Review Requirements in BrochureReview Requirements in Brochure Complete Application in BrochureComplete Application in Brochure Send Completed Application to IEEE CS by Send Completed Application to IEEE CS by

Deadline with FeeDeadline with Fee Acknowledgement of PaymentAcknowledgement of Payment Review of ApplicationReview of Application If Accepted, Authorization to Test sent to CandidateIf Accepted, Authorization to Test sent to Candidate


Requirements for CSDP Requirements for CSDP CertificationCertification

EducationEducation- Baccalaureate or equivalent university degree- Baccalaureate or equivalent university degree

ExperienceExperience- - 9,000 hours of experience in 6 of the 11 software 9,000 hours of experience in 6 of the 11 software engineering knowledge areas listed in the brochureengineering knowledge areas listed in the brochure

Proof of ProfessionalismProof of Professionalism- Review and acknowledge the Software Engineering - Review and acknowledge the Software Engineering Code of Ethics and Professional PracticeCode of Ethics and Professional Practice

ExaminationExamination- Pass the CSDP written examination- Pass the CSDP written examination


Preparation for the Preparation for the ExaminationExamination

Depends on level of expertise in areas covered Depends on level of expertise in areas covered by Body of Knowledgeby Body of Knowledge

Focus on areas needing the most reviewFocus on areas needing the most review Study from the suggested reference materialStudy from the suggested reference material Can take a refresher courseCan take a refresher course Unless your background covers most of the Unless your background covers most of the

Body of Knowledge, allow three months of 2-4 Body of Knowledge, allow three months of 2-4 hours a week for studyhours a week for study

Last week: assemble test access materials.Last week: assemble test access materials.


ExaminationExamination FormatFormat

- - Multiple-choice questions selected from a pool of Multiple-choice questions selected from a pool of questions across each of the knowledge areasquestions across each of the knowledge areas- Total of 180 questions on the examination- Total of 180 questions on the examination- Closed book, calculators provided- Closed book, calculators provided- Computer-based test- Computer-based test

LengthLength Four hoursFour hours

AdministrationAdministration- Conducted by qualified proctors who will register you - Conducted by qualified proctors who will register you and check to ensure all exam admission and check to ensure all exam admission documentation are acceptabledocumentation are acceptable- No copy of questions are allowed, proctor cannot - No copy of questions are allowed, proctor cannot answer any questionsanswer any questions concerning the examinationconcerning the examination


Results from the ExaminationResults from the Examination WhenWhen

- - At the end of the examination, the exam results will At the end of the examination, the exam results will immediately appear on the computer screen.immediately appear on the computer screen.- A hard copy of the score will be provided at the - A hard copy of the score will be provided at the testing centertesting center- Within four weeks after the exam, notification by - Within four weeks after the exam, notification by mailmail

Passing ScorePassing Score- - Scale scores range from 120 to 200 with passing Scale scores range from 120 to 200 with passing score of 170score of 170- Systematic procedure, judgment of IEEE CS - Systematic procedure, judgment of IEEE CS members and CGI, and IEEE CS Certification members and CGI, and IEEE CS Certification Committee all are involved in determining what a Committee all are involved in determining what a passing score is on each individual exampassing score is on each individual exam


Results from the Results from the ExaminationExamination

(continued)(continued)

PassPass:: letter of congratulation from letter of congratulation from Certification Committee, certificate for Certification Committee, certificate for framing, your name published in the society’s framing, your name published in the society’s flagship magazine, flagship magazine, Computer Computer and on our web and on our web sitesite

FailFail:: analysis of the complete exam outline analysis of the complete exam outline areas on which you should focus studies, areas on which you should focus studies, allowed to take the exam within [to be allowed to take the exam within [to be determined]determined]


Results from the ExaminationResults from the Examination(continued)(continued)

Recertification ApplicationRecertification Application- - Log all Recertification Units & Continuing Log all Recertification Units & Continuing Education UnitsEducation Units

ConfidentialityConfidentiality- No information concerning scores is distributed - No information concerning scores is distributed to anyone (including you), no analysis given to to anyone (including you), no analysis given to those who pass, no information about the those who pass, no information about the certification is divulged to third parties (e.g., certification is divulged to third parties (e.g., employers) except at the written request of the employers) except at the written request of the person who took the examperson who took the exam


Follow-up ActivitiesFollow-up Activities Responsibilities of CSDPResponsibilities of CSDP

- Signed statement to acknowledge review of the Software - Signed statement to acknowledge review of the Software Engineering Code of Ethics and Professional PracticeEngineering Code of Ethics and Professional Practice

Meaning of CertificateMeaning of Certificate- IEEE CS certification is not a license, always refer to - IEEE CS certification is not a license, always refer to IEEE in using the term “CSDP”, for example say IEEE IEEE in using the term “CSDP”, for example say IEEE Computer Society CSDP not just CSDPComputer Society CSDP not just CSDP

RecertificationRecertification- Every 3 years- Every 3 years- Requires 30 recertification credits- Requires 30 recertification credits- Pay fee- Pay fee


Distribution of Questions Per Knowledge Distribution of Questions Per Knowledge AreaArea

1.1. Business Practices & Engineering Economics (3-4%)Business Practices & Engineering Economics (3-4%)2.2. Software Requirements (13-15%)Software Requirements (13-15%)3.3. Software Design (22-24%)Software Design (22-24%)4.4. Software Construction (10-12%)Software Construction (10-12%)5.5. Software Testing (15-17%)Software Testing (15-17%)6.6. Software Maintenance (3-5%)Software Maintenance (3-5%)7.7. Software Configuration Management (3-4%)Software Configuration Management (3-4%)8.8. Software Engineering Management (10-12%)Software Engineering Management (10-12%)9.9. Software Engineering Process (2-4%)Software Engineering Process (2-4%)10.10. Software Tools and Methods (2-4%)Software Tools and Methods (2-4%)11.11. Software Quality (6-8%)Software Quality (6-8%)

Knowledge Area (% of questions on exam)


General ReferencesGeneral ReferencesEither 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, 2nd Edition. Dorfman, M. & Thayer, R., eds., Los Alamitos, California: IEEE Computer Society Press, 2002.Software Engineering Vol. 2: The Supporting Processes, 2nd Edition. Thayer, R. and M. Christensen, eds., Los Alamitos, California: IEEE Computer Society Press, 2002.

IEEE Software Engineering Collection, 1999, vols. 1-4.


General Supplemental General Supplemental ReadingReading

The following books are suggested as general supplemental reading:

Software Engineering Vol. 1: The Development Process, 2nd Edition. Dorfman, M. & Thayer, R., eds., Los Alamitos, California: IEEE Computer Society Press, 2002.

Software Engineering Vol. 2: The Supporting Processes, 2nd Edition. Thayer, R. and M. Christensen, eds., Los Alamitos, California: IEEE Computer Society Press, 2002.

IEEE Software Engineering Collection, 1999, vols. 1-4. Piscataway, New Jersey: IEEE.


Test ScheduleTest Schedule

2002200215 May – 30 June15 May – 30 June5-26 October5-26 October

200320031-30 April1-30 April1-31 October1-31 October


Discussion: Q & ADiscussion: Q & A Examination ProcessExamination Process

Examination MaterialsExamination Materials

Benefits and CostsBenefits and Costs

Comments from IEEE Computer SocietyComments from IEEE Computer Society


For More InformationFor More Information Stacy Saul, Continuing Education CoordinatorStacy Saul, Continuing Education Coordinator IEEE Computer SocietyIEEE Computer Society

1730 Massachusetts Ave., NW1730 Massachusetts Ave., NWWashington, DC 20036-1992 Washington, DC 20036-1992

Voice: +1 202-371-0101Voice: +1 202-371-0101 Fax: +1 202-728-0884Fax: +1 202-728-0884 E-mail address: E-mail address: [email protected]@computer.org Web address: http://computer.org/certificationWeb address: http://computer.org/certification

mailto:[email protected]


Background MaterialBackground Material


1. Business Practices and 1. Business Practices and Engineering EconomicsEngineering Economics

A.A. Engineering Economics Engineering Economics B.B. EthicsEthicsC.C. Professional Practice Professional Practice D.D. StandardsStandards

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.


2. Software Requirements2. Software RequirementsA. Requirements Engineering Process B. Requirements Elicitation C. Requirements Analysis D. Software Requirements Specification E. Requirements Validation F. Requirements Management

Key ReferencesAny 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.


3. Software Design3. Software DesignA. Software Design ConceptsB. Software ArchitectureC. Software Design Quality Analysis and EvaluationD. Software Design Notations and Documentation E. Software Design Strategies and MethodsF. Human Factors in Software Design G. Software and System Safety

Key ReferencesAny 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.


4. Software Construction4. Software ConstructionA. Construction planningB. Code designC. Data design and managementD. Error processingE. Source code organizationF. Code documentationG. Construction QAH. System integration and deploymentI. Code tuningJ. Construction tools

Key ReferencesThe 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.


5. Software Testing5. Software TestingA. 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 ReferencesAny 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.


6. Software Maintenance6. Software MaintenanceA. 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.


7. Software Configuration 7. Software Configuration ManagementManagement

A. Management of SCM ProcessB. Software Configuration IdentificationC. Software Configuration ControlD. Software Configuration Status AccountingE. Software Configuration AuditingF. Software Release Management and Delivery

Key References

IEEE Standards 828-1990 and 1042-1987


8.8. Software Engineering Software Engineering ManagementManagement

A. Measurement B. Organizational Management and CoordinationC. Initiation and Scope DefinitionD. PlanningE. Software AcquisitionF. EnactmentG. Risk ManagementH. Review and EvaluationI. Project Close OutJ. Post-closure Activities

Key ReferencesAny 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


9. Software Engineering 9. Software Engineering ProcessProcess

A. Process Infrastructure B. Process MeasurementC. Process DefinitionD. Qualitative Process AnalysisE. 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.


10. Software Tools and 10. Software Tools and MethodsMethods

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.


11. Software Quality11. Software QualityA. 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 ReferencesNo 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.

Documents

IEEE Computer Society Certified Software Development Professional