Certification of Software Engineering Professionals ISO/IEC WD 24773
Certification - is a formal recognition that an individual has demonstrated proficiency within and comprehension of a specified body of knowledge at a point of time. It is not reigstration nor licensure (authrization). It is voluntary.
Why? because it is a mark of excellence, ensures the organization has knowledge to ensure that recognized principles and practices of software engineering are being used. Plus competition in market.
--
BOKs and Organisations
INCOSE
The International Council on Systems Engineering
www.incose.org
Certified Systems Engineering Professional (CSEP)
SE Handbook (g2sebok.incose.org)
Finnish Chapter www.finse.org
IEEE
IEEE Computer Society
Certified Oftware Development Professional (CSDP)
www.computer.org
Software Engineering, eds. ...............SWEBOK
--
Background Requirements (CSDP)
1. Education
- baccalaureate or equivalent university degree
2. Experience
- 9,000 hours of experience in 6 of the 11 software engineering knowledge areas listed in the brochure
3. Proof of Professionalism
- review and acknowledge the Software Engineering Code of Ethics and Proessional Practice
... aaaaahhhhh stupid things and strange numbers... maybe this is irrelevant..:P
--
ok shortly:
there's some CSPD - certified software development professional
- CSPD Cerfitication Examination that lasts 4 hours, on the computer, 180 questions from business practices, software requirements, s. design, s. construction and many others.., software configuration management
- CSDP Recertification every 3 years - if within 3 years no exam, but you have to have 30 points for: employing SW engineer, gradute courses, publish papers, giving a presentation, professional activities...
- software configuration management includes this at: the beginning of the life cycle, or predefined points at the lc, or at the end, and.. blabla
- originally to financially support development of software by credit guarantee, but later also computer security, human resource dvelopment, and others.
began from concern from the industry about shortage of IT engineers,
these engineers wanted recognition of their skills
first examination 1969
they expected 5000 people to take part, but there was 40000, out of whom 12000 passed as senior programmer and the rest with just 'programmer' grade. Becaause it turned out to be so popular it was raised to become a National Examination from 1970
1970 first National Exams held (hey, but in which country?)
1971 new category: systems engineer
1986 JIPDEC and JITEC (Japan IT Examination Center) appointed as the examination body
1994 11 categories
2002 +2 categories
2004 JITEC operation trasferred to IPA
* graph: //don't read this x, y this is just my interpretation :p
y: how many applicants and how many succesful applicants:
x: from 1973 to 2003
how many: from 1983 y=x, from 1990 y=-x, from 1995 y=2x, from 2002 down again
how m. successful: divide upper graph values by 10... actually not much difference over the time compared to the number of applicants... interesting.
* graph... nothing... haha just blank
every year approx 700,000 take the exams (in Japan?)
-----------------
ISO work on certification
-started in 2004
-new IS will be published in 2009
-ISO/EIC 24773
-general idea:
-national sheme<->IS
-national BOK <-> SWEBOK
-IS: Minimum experience
-code of practice / ethics (included)
- examination (depends..)
---
This International Standard applies to schemes intendedd to provide certification for persons working as software engineering professionals. Such certification schemes may be created by national governments, by national or international professional organizations, or by private entities.
---
Knowlegde and skills
- body of knowledge
- the evaluation component of a certification scheme shall be explicitly based on a body of knowledge. For each component of this body of knowledge, the scheme shall state the cognitive level expected of a successful candidate for certification
---
Software Engineering body of knowledge
- the software engineering component of the body of knowledge required shall be explicitlymapped to :
- software engineering - Guide to the Software Engineering Body of Knowledge (SWEBOK) ISO/IEC TR 19759:2005
---
SWEBOK
-www.swebok.org
-.......oh so much text.
BUT haha google: In spite of the millions of software professionals worldwide and the ubiquitous presence of software in our society, software engineering has not reached the status of a legitimate engineering discipline and a recognized profession. Since 1993, the IEEE Computer Society and the ACM have been actively promoting software engineering as a profession, notably through their involvement in the IEEE Computer Society and ACM Software Engineering Coordinating Committee.
guide to SWEBOK
TABLE OF CONTENTS
CHAPTER 2 SOFTWARE REQUIREMENTS
CHAPTER 3 SOFTWARE DESIGN
CHAPTER 4 SOFTWARE CONSTRUCTION
CHAPTER 5 SOFTWARE TESTING
CHAPTER 6 SOFTWARE MAINTENANCE
CHAPTER 7 SOFTWARE CONFIGURATION MANAGEMENT
CHAPTER 8 SOFTWARE ENGINEERING MANAGEMENT
CHAPTER 9 SOFTWARE ENGINEERING PROCESS
CHAPTER 10 SOFTWARE ENGINEERING TOOLS AND METHODS
CHAPTER 11 SOFTWARE QUALITY
CHAPTER 12 RELATED DISCIPLINES OF SOFTWARE ENGINEERING
---
Application area and dependence
-if the software engineering professional subject to certification is to operate in a particular industry or product domain, the certification body shall identify any appropriate knowledge requirements.
--
Generic professional skills
...
--
ThE future:
integration of knowledge on:
- Project (management)
- Process (improvement)
- Product (qualit)
- People (competence)
-next big thing in SW will be connnected to people issues
-because of globalization, internationalization, lacalization (->will consider culture)\
--// END
