面向专业认证的软件工程专业建设研究

在当前我国本科工程教育专业认证背景下,本文探讨了在软件工程专业建设和认证过程中的课程建设与人才培养方面遇到的各种问题。针对存在的问题,提出了以专业认证为抓手,以社会需求和产业发展为依托,通过明确专业培养目标,完善课程群体系建设,增强实践教学环节,加强学生专业能力培养,从而达到培养学生的创新思维和实践能力,提升毕业生的市场竞争力的目的,并为推动软件工程专业认证工作的顺利实施提供良好基础。     

软件工程专业的认证标准和课程计划

1.引言为了培养能满足社会各行各业要求的高素质的软件开发人员,1997年IEEE计算机学会和ACM学会联合组织了SWECC(软件工程协调委员会)开展了软件工程教育项目(SWEEP:Software Engineering Educa-tion Project),对软件工程专业的认证标准和课程计划进行研究,以便为企业和教育机构培养相关人才提供指南。开展该项目的背景包括:①软件工程经过三十多年的发展已成为相当成熟的、具有自己独立特征的学     

工程教育认证背景下的软件工程专业建设和实践

针对目前软件工程专业建设和认证过程中存在的各种问题,经过探索和实践,提出了在工程教育专业认证背景下,以专业认证为抓手,通过明确专业培养目标,完善特色课程群体系,加强双师型教师队伍建设,加强条件建设并增强实践教学环节,加强学生工程实践能力培养,建立教学质量保障体系,从而达成专业认证和提高学生培养质量的目标,为下一步推动我校软件工程专业认证工作奠定了良好基础。     

专业认证背景下软件工程专业本科教育重构思考

分析现阶段软件工程专业教学与专业认证所要求的人才培养目标之间的矛盾,明确软件工程专业人才培养目标内涵,从课程教学体系和能力训练体系2个角度介绍专业认证背景下的软件工程专业学科教育框架重构,针对学生培养过程控制提出教学组织和学习方式重构策略,并进一步探讨运用信息技术提升和保障专业人才培养质量的方法.     

软件工程专业“学习情境”建设实践

建构主义(Constructivism)学习理论已逐步成为认知理论中一个新的重要分支。建构主义认为:学习不是将知识从外部搬运到学习者记忆中的简单过程,而是学习者在已有经验基础上,通过与外界的相互作用,建构新知识的过程。建构主义大力提倡"在教师指导下,以学生为中心的学习",从根本上改变传统的"单向灌输式"教育,建立全新的师生关系。"以学生为中心的学习"包含4个基本要素,即"学习情境"、"协作"、"会话"和"意义建构"。     

ISO／IEC认证提升软件工程专业国际认可度

随着软件产业的日益全球化,学软件专业的人们将在不同的国家工作。因此,在这一领域,提高专业证书的国际认可度是非常重要。当外国客户要求软件开发商提供相关证明时,跨国组织或提     

专业认证背景下引入课程思政的软件专业人才培养模式

针对当前软件人才培养中综合能力、人文素养等缺失的现状,提出基于工程教育专业认证标准,构建一个以学生为中心、以毕业要求为目标并融入思政教育的人才培养模式,探讨软件专业毕业要求与思政元素、课程教学和评价考核的映射及实施,介绍思政案例库的建设,并以面向对象的分析与设计课程为例阐述具体教学实施,通过效果说明该教学模式的有效性。     

新工科+工程教育认证背景下软件工程特色专业建设探索

针对新工科建设和工程教育认证对软件工程特色专业建设和人才培养的新要求,以及目前软件工程专业特色和人才培养特点不鲜明、不适应新工科要求等问题,提出了从提炼新理念、改变教育观念、创新培养模式、构建专业培养新体系等方面的专业建设途径。经过建设,我系软件工程于2017年被学校确定为校级重点建设学科,并被评为学校第一批进行工程教育认证的试点专业。     

“对标国外大学,深度融合认证”的软件工程专业人才培养方案

针对现有软件工程专业培养方案不能很好地培养学生的专业能力和职业资格能力的问题,指出制定应用型本科软件工程试点专业人才培养方案必须考虑"对标国外大学、深度融合认证";阐述如何在软件工程试点专业人才培养方案中设置培养学生专业能力与职业资格认证的课程体系,观测指标与毕业要求,如何调研、分析汇总与筛选等;提出形成基于四大专业能力和双证融通的软件工程试点专业人才培养方案及其实施路径。     

Catching the brass ring [software engineering professional]

Eventhough most senior executives in the larger software firms boast engineering, marketing, legal, and business school backgrounds, most engineering organizations aren't led by the software people. We discuss about the factors that govern such selections and what software engineering professionals can do about it. We also discuss about why the software professionals often aren't tapped for top corporate leadership positions and about their role in the business organisations.     

Current accreditation, certification, and licensure activities related to software engineering

The issues associated with the accreditation, certification, and licensure of software engineers are, or at least should be, of great concern to the software engineering community. Perhaps as a result of publicity about safety-critical software disasters in the news media, some state legislatures have considered regulating the practice of software engineering, and some professionals believe that accreditation, certification, and licensure are inevitable. Yet there is no agreed-upon body of knowledge for software engineering on which to base accreditation, certification, or licensure, which makes implementing them difficult at best. In addition, it is not clear that these processes and possible mechanisms to support them are well understood within the software engineering community. This paper surveys how these three processes are conducted in other professions, summarizes the processes as they currently exist for computing in general, identifies some issues that are involved in implementing the processes for software engineering, and suggests possible actions that can be taken by the software engineering profession. The implications of accreditation, certification, and licensure for education are also discussed.     

Third-party testing and stirrings of the new software engineering

As the discipline of software engineering prepares for the ever-increasing development of applications based on preproduced software components, it is time to reflect on the emergence of the engineering profession in the United States. A brief review of bridge construction-one of the earliest engineering endeavors-can help, as bridges are required for interrelationships among people and governments, the growth of commerce, and the proliferation of new ideas     

Academic degrees and professional certification

We ask how one should invest one's time and money in a lifelong learning program, and if hiring personnel, what training and expertise should be looked for. In this article, we discuss general professional certifications and compare and contrast them with a bachelor's degree to help decide which is most appropriate.     

A software product certification model

Certification of software artifacts offers organizations more certainty and confidence about software. Certification of software helps software sales, acquisition, and can be used to certify legislative compliance or to achieve acceptable deliverables in outsourcing. In this article, we present a software product certification model. This model has evolved from a maturity model for product quality to a more general model with which the conformance of software product artifacts to certain properties can be assessed. Such a conformance assessment we call a ‘software product certificate’. The practical application of the model is demonstrated in concrete software certificates for two software product areas that are on different ends of the software product spectrum (ranging from a requirements definition to an executable). For each certificate, a concrete case study has been performed. We evaluate the use of the model for these certificates. It will be shown that the model can be used satisfactorily for quite different kinds of certificates.     

A new programming paradigm for engineering design software

Currently available programming and database systems are insufficient for engineering applications. The authors contend that a logical progression from a formal conceptual model of the engineering domain to a computational model will lead to new programming paradigms capable of directly supporting engineering applications in a rigorous, concise manner. A formal domain model devised by the authors, theHybrid Model (HM) of design information, is briefly introduced. It is an extension of axiomatic set theory and is discussed in detail elsewhere. HM forms the basis ofDesigner, a prototype-based object-oriented programming language supporting a signature-based canonical message-passing mechanism and multiple inheritance. Designer is implemented using the Scheme programming language. Because Designer satisfies a formal conceptual model, and because it is based on a formally specified language, its robustness and logical validity are superior to those of other languages not founded on formal principles. Designer combines concepts of functional and object-oriented programming to provide the formal rigor and flexibility to capture the complex and strongly interrelated information that designers use. Examples demonstrate how Designer represents design information. The results of the authors' research indicate that Designer can capture design information (including aspects of functional requirements and design intent) effectively and efficiently.     

Developing a usage-based software certification process

The author proposes an alternative to process-based methods of assuring software quality: a certification process that will provide product-based and trustworthy quality guarantees for commercial software packages. I call the agencies that perform such certification “software certification laboratories” (SCLs). The beauty of establishing independent SCLs is that they provide a fair playing field for each publisher, assuming that each product under review receives equal treatment     

Foundations of a new software engineering method for real-time systems

The design of a fault-tolerant distributed, real-time, embedded system with safety-critical concerns requires the use of formal languages. In this paper, we present the foundations of a new software engineering method for real-time systems that enables the integration of semiformal and formal notations. This new software engineering method is mostly based upon the ”COntinuuM” co-modeling methodology that we have used to integrate architecture models of real-time systems (Perseil and Pautet in 12th International conference on engineering of complex computer systems, ICECCS, IEEE Computer Society, Auckland, pp 371–376, 2007) (so we call it “Method C”), and a model-driven development process (ISBN 978-0-387-39361-2 in: From model-driven design to resource management for distributed embedded systems, Springer, chap. MDE benefits for distributed, real time and embedded systems, 2006). The method will be tested in the design and development of integrated modular avionics (IMA) frameworks, with DO178, DO254, DO297, and MILS-CC requirements.