情報処理学会第74回全国大会 会期:2012年3月6日(火)~8日(木) 会場:名古屋工業大学 一般社団法人情報処理学会 第74回全国大会 会期:2012年3月6日(火)~8日(木) 会場:名古屋工業大学
招待講演-2
John Walz(IEEE Computer Society President)
Reducing the risk in software engineering products and services

日時:3月7日(水)14:15-15:15
会場:第1イベント会場 (51号館 1F 5111)

【講演概要】This talk is divided into two sections of software engineering products and services, first the risk during the product development and second the risk during product usage. Software Engineering (SwE) product development is divided into three sub-sections, where risks are managed and mitigated by a balance of:
1) Well defined processes,
2) Staffed and conducted by talented people,
3) operating within a project management using technology.
The desired attributes during development are full functional products, delivered on-time with excellent quality. The Product quality model, from ISO/IEC 25010 System and Software Quality Models, has two levels, where the first level of eight attributes includes: Functional suitability, Performance efficiency, Compatibility, Usability, Reliability, Security, Maintainability, and Portability.
Complete SwE processes are defined from standards and instantiated by the organization for the SwE project. The web of SwE processes are designed into a SwE Life Cycle Model, showing relationships of processes and their shared Information products. These process model dependancies and information products are reflected in the project management plan. SwE processes minimum outcomes and tasks are defined in IEEE 12207 SwE Life Cycle Processes. For those SwE projects that support system projects, additional system engineering (SE) processes are defined in IEEE 15288 System Engineering Life Cycle Processes. The project life cycle Information Products minimum structure are defined in IEEE 15289 Software and System Engineering (S2E) Life Cycle Information Products. The information products are either customer deliverables or the internal products, sometimes called process artifacts for purposes of project communication and assessments for maturity and capability.
For optimum development risk avoidance, the project life cycle should include the risk management process, whose minimum requirements are in IEEE 16085 Systems and software engineering Risk management process. Along with risk management process, many of software and system engineering (S2E) processes have more detailed defined process definitions in standards. Important supporting processes include the upcoming IEEE 730 Software Quality Assurance Process and IEEE 1012 S2E Verification & Validation Process.
The next sub-section covers talented people conducting the well defined processes.
Project staff should be knowledgable and follow the ACM / IEEE Software Engineering Code of Ethics and Professional Practice. Staff attributes include education, training, and experience. While university degrees and job history are useful, the objective measurable personnel attributes is attainment of IEEE Certified Software Development Professional (CSDP). The CSDP is based on the Software Engineering Body of Knowledge (SWEBOK). The bachelor degree should be acquired from a university or college whose curriculum as been assessed against the ACM / IEEE Software Engineering (SE2004) curriculum guide. Graduate degree should be acquired from a university or college whose curriculum has Curriculum Guidelines for Graduate Degree Programs in Software Engineering (GSwE2009). The SwE project staff should use standard vocabulary from IEEE Software and Systems Engineering (S2E) Vocabulary. For software intensive systems projects, the System Engineering (SE) Body of Knowledge is under development and Version 0.5 is available to the public for comment. SEBOK will be supported by future training offerings similar to SWEBOK knowledge area training courseware. At a later date, staff credentials can be confirmed by certification schemes. For optimum development risk avoidance, the project life cycle should include the human resource process, whose minimum outcomes and tasks are described in both IEEE 12207 and 15288.
The third development sub-section is the project management. The technical management team should rely on the Guide to the Project Management Body of Knowledge (PMBOK Guide). PMBOK presents a set of standard terminology and guidelines for project management. Both PMI and IEEE experts are working together on developing the software extension to PMBOK. Other reference sources for Software Project Management is using IEEE 1058.1 Software Project Management Plans. Lean and agile management techniques are important, some are planned to be added to PMBOK. Project manager qualifications can be demonstrated by achievement of the Project Manager Professional (PMP) certification by PMI.
The second and last section is reducing the risk in using software engineering products and services.

【略歴】John Walz retired from Lucent / AT&T with over 20 years of management/coaching experience, covering positions in hardware and software engineering, quality planning and auditing, standards implementation, and strategic planning. John has co-authored three books covering the use of IEEE Software Engineering Standards to support CMMI ® , ISO 9001, and Lean Six Sigma. He is also a contributor to the CS ReadyNotes products and industry webinar programs.
Walz has served IEEE Computer Society as the Vice President of Technical and Conferences Activities Board and on the Board of Governors. Previously he was Standards Activities Vice President. John also served on the Computer Society’s committees on History, Technology & Conferences New Practitioners, Awards, Membership, Software & Systems Engineering Standards (S2ESC), and the Computer Software Applications Conference (COMPSAC).
Walz held leadership positions in national and international industry and professional organizations, including the U.S. Technical Advisory Group for ISO committee working ISO 9001, American Society for Quality (ASQ) Electronics and Communications Division, ASQ Sarbanes-Oxley Forum, Quality Excellence for Suppliers of Telecommunications (QuEST) Forum, and Information Integrity Coalition.
Walz participated in the IEEE Computer Society Distinguished Visitor Program and is a recipient of the IEEE Computer Society Golden Core, Distinguished Service, and Meritorious Service Awards. He received a Masters of Science in Electrical Engineering from Ohio State University.