software engineering consortium vancouver, british columbia september 29, 2007 item 3.3 attachment

9
Software Engineering Consortium Vancouver, British Columbia September 29, 2007 Item 3.3 Attachment

Upload: barnard-barker

Post on 16-Jan-2016

212 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: Software Engineering Consortium Vancouver, British Columbia September 29, 2007 Item 3.3 Attachment

Software Engineering Consortium

Vancouver, British Columbia

September 29, 2007

Item 3.3 Attachment

Page 2: Software Engineering Consortium Vancouver, British Columbia September 29, 2007 Item 3.3 Attachment

Software Engineering Consortium

• Purpose

• Members

• NSPE Board Action

• Consortium Actions

• Strategy

Page 3: Software Engineering Consortium Vancouver, British Columbia September 29, 2007 Item 3.3 Attachment

Software Engineering Consortium

• Purpose– Resolved the apparent disagreement among

the stakeholders– Develop tools, resources, and strategy to

implement licensure of software engineers

Page 4: Software Engineering Consortium Vancouver, British Columbia September 29, 2007 Item 3.3 Attachment

Software Engineering Consortium

• Members– IEEE (USA, CS PPC, CS Wireless) [4]– NSPE (PEI, L&QP, Facilitator) [5]– TBPE (BOD, Staff, SWETF) [3]– NCEES (Exam Development) [2]– Delaware BPE Member [1]

Page 5: Software Engineering Consortium Vancouver, British Columbia September 29, 2007 Item 3.3 Attachment

NSPE BOD Actions

• July 28, 2007– Endorsed the actions of the SwE Summit– Resolved to support the path forward in

licensing SwE

• September 29, 2007– Update report on progress to date– Current view of path forward– No BOD action at this time

Page 6: Software Engineering Consortium Vancouver, British Columbia September 29, 2007 Item 3.3 Attachment

Software Engineering ConsortiumActions

• Achieved Consensus (July 27, 2007)– Software Engineering (SwE) is a separate discipline that can

impact public health, safety, and welfare– Software engineering definition– Licensure of SwE should be promoted– Basic path to Licensure

• ABET engineering degree• FE Exam• 4 years engineering experience• SwE P&P exam

– Specifics remain state-by-state process– Certification by IEEE does not replace licensure– Use NCEES model for exam development– Inclusion of related disciplines in the BOK for SwE (PAKS)

Page 7: Software Engineering Consortium Vancouver, British Columbia September 29, 2007 Item 3.3 Attachment

Software Engineering ConsortiumActions

• Conference Calls (8/29, 9/17, and 10/1)• Resources

– IEEE opened the door to use their certification exams as a starting point

– TBPE proposed a cost sharing plan where they would fund one-third of the costs

• Tools– Prepared draft of purpose and justification package– Obtained copy of MOA between NCEES and bioengineering

consortium– Prioritized state boards for consortium overtures– Developing briefing paper and power point presentation

Page 8: Software Engineering Consortium Vancouver, British Columbia September 29, 2007 Item 3.3 Attachment

Software Engineering ConsortiumStrategy

• Need 10 Licensure Boards to Certify as to Need for SWE Licensure Process including Exam Development

• Consortium will:– Develop talking points and approach individual state Licensure

Boards to get the 10 necessary– Work with local members of NSPE and IEEE to approach each

state board– Follow the NCEES process

• Consortium takes the lead on most of the process• NCEES on the rest

Page 9: Software Engineering Consortium Vancouver, British Columbia September 29, 2007 Item 3.3 Attachment

Software Engineering Consortium

• Questions