Professional & Educational Activities Board
The Professional & Educational Activities Board (PEB) provides leadership in the Society for activities related to the professional activities of practitioners engaged in disciplines such as computer engineering, computer science, information technology, information systems, and software engineering.
PEB is chaired by the Vice President of Professional Activities, Chuck Walrad. Its current roster is here.
PEB is responsible for formulating policies and practices with respect to the society's role in the development and support of professional disciplines such as computer engineering, computer science, information technology, information systems, and software engineering; including body of knowledge characterization, competencies, ethics, performance norms, and terminology. It shall recommend, evaluate, initiate, and nurture programs, products, and services to serve practitioners and their employers.
The PEB currently has five committees.
Information Technology Committee
The Information Technology Discipline-specific Committee makes recommendations to PEB regarding programs to serve the Information Technology community. When appropriate, a liaison relationship with appropriate Technical Councils, Technical Committees, and/or Standards committees is established.
- The PEB-IT committee is working with several partners, from DAMA and IIBA to CEPIS Europe and the Information Technology Promotion Agency in Japan, to produce a Guide to the Enterprise IT Body of Knowledge, due out in 2015 at eitbokwiki.org.
- The IEEE Computer Society has adopted the Skills Framework for the Information Age (SFIA) as the top-level competency model for IT professionals. We are working to extend that model into several areas of specialization. For example, as a founding member of the Federation of Enterprise Architecture Organizations (FEAPO), we have worked with other members to define the skills and career paths for Enterprise Architecture.
Software and Systems Engineering Committee
The Software and Systems Engineering Discipline-specific Committee makes recommendations to PEB regarding programs to serve the Software and Systems Engineering communities. When appropriate, a liaison relationship with appropriate Technical Councils, Technical Committees, and/or Standards committees is established.
- The SWEBOK Guide, adopted by ISO/IEC in 2005 as its umbrella description of software engineering (ISO/IEC TR 19759), is one of our best well-known products. It is soon to be available at swebokwiki.org. The IEEE family of Software Engineering Certification exams are based on the Guide.
- The PEB-SSE collaborated in 2012 to produce the Software Engineering Extension to the PMBOK, as well as with INCOSE, NDIA, and IEE to create the Systems Engineering Body of Knowledge.
- We have drafted a Competency Model for Software Engineering, based on the SWEBOK, that will be harmonized with SFIA in 2015.
- Our two prior certifications (Certified Software Development Professional and Certified Software Development Associate) are being augmented in 2015 with a full suite of certifications based on the individual Knowledge Areas in Guide to the Software Engineering Body of Knowledge (SWEBOK).
Professional Education Product Committee
The Professional Education Product Development Committee works with the discipline-specific committees to support educational efforts by the development of easily usable products that are consistent across disciplines. Products are delivered through a range of options, such as online resources, distance learning courses, continuing education courses, professional development seminars, and tutorials.
- The Product Committee identifies what products may be needed where. In 2014, for example, Indian software industry's representative body Nasscom certified the courseware products developed by IEEE Computer Society for the IT and IT-enabled services sector.
- The IEEE Computer Society, the IEEE Systems Council, the International Council on Systems Engineering (INCOSE), the Institute of Industrial Engineers (IIE), and the National Defense Industrial Association (NDIA) Systems Engineering Division provided authors to create the System Engineering body of Knowledge, now available as a wiki (www.sebokwiki.org).
Curriculum Development Committee
- The IEEE Computer Society has worked over the last decade with the ACM to define model curricula for the 5 areas of computing: Computer Engineering 2004, Computer Science 2013, Software Engineering 2014, Information Systems 2010 and Information Technology 2008. The following curricula are currently undergoing revision (IT2017, expected in 2017, and CE 2016, expected in 2016). CE 2016 should be available for public review this Fall.
- The IEEE Computer Society has recognized the Master of Software Assurance (MSwA) Reference Curriculum as appropriate for a master’s program in software assurance. This curriculum, which is sponsored by the US Department of Homeland Security, is the result of collaboration between researchers in the CERT Program at the Software Engineering Institute (SEI) and a team of educators from Embry-Riddle Aeronautical University, Monmouth University, and Stevens Institute of Technology. It is designed to identify a core body of knowledge that educational institutions can use to develop MSwA degree programs
- The IEEE Computer Society, the IEEE Systems Council, the International Council on Systems Engineering (INCOSE), the Institute of Industrial Engineers (IIE), and the National Defense Industrial Association (NDIA) Systems Engineering Division collaborated to execute the BKCASE Project (Body of Knowledge and Curriculum to Advance Systems Engineering) which produced the Graduate Reference Curriculum for Systems Engineering.
Program Accreditation Committee
The Accreditation Committee identifies targets of accreditation, maintains and updates accreditation criteria; and participates in accreditation of computing programs. It supports the IEEE Educational Activities Board in its participation in CSAB (the Computing Sciences Accreditation Board) and ABET (the Accreditation Board for Engineering and Technology).
How it works:
- Degree program requests an evaluation from ABET and subsequently submits a comprehensive self-study report. A campus visit follows.
- The report and visit are evaluated and conducted, respectively, by a team: a chair and one (possibly two) evaluators.
- The team chair is a member of the CAC (or EAC for software engineering).
- The evaluators are recruited, trained, and assigned by CSAB.
- Based on the findings of the team, the commission issues an accreditation action.
- Cycle from request to action is 18 months.