No abstract

The last twenty years has seen the development of demand for a new type of computing professional, which has resulted in the emergence of the academic discipline of Information Technology (IT). Numerous colleges and universities across the country and abroad have responded by developing programs without the advantage of an existing model for guidance. Efforts to define a model curriculum for IT began at the first Conference on Information Technology curriculum (CITC-1) in December 2001, which included representatives from 15 IT programs at four-year universities across the United States. Membership in SIGITE (Special Interest Group Information Technology Education) has grown to over 400 representing many of the four-year IT programs in the United States and abroad and some of the two-year IT programs in the United States. Continued development of the curriculum and subsequent funding by the Education Board of ACM enabled the completion of a first draft of the model curriculum for IT establishing program outcomes and a body of knowledge defining the discipline. This paper presents an overview of the process followed and the results achieved.

Abstract. The practice of software development has evolved considerably in recent decades, with new programming technologies, the affordability of hardware, pervasive internet access and mobile computing all contributing to the emergence of new software development processes. The newer process initiatives, which include those which are sometimes referred to as agile or lean methods, have brought with them new terms, which sometimes reflect the introduction of novel concepts. Other times, new terms correspond to long established concepts that have been repackaged. The net position is that we have a proliferation of language and term usage in the software development process domain, a problem which has implications for assessors and assessment frameworks, and for the broader community. In this paper, we explore this problem, finding that it is worthy of further research. Plus, we identify a technique suited to addressing this concern: the establishment of a canonical software process ontological model.

Abstract. In work that is ongoing, the authors are examining the extent of software development process terminology drift. Initial findings suggest there is a degree of term confusion, with the mapping of concepts to terms lacking precision in some instances. Ontologies are concerned with identifying the concepts of relevance to a field of endeavour and mapping those concepts to terms such that term confusion is reduced. In this paper, we discuss how ontologies are developed. We also identify various sources of software process terminology. Our work to date indicates that the systematic development of a software development process ontology would be of benefit to the entire software development community. The development of such an ontology would in effect represent a systematic refactoring of the terminology and concepts produced over four decades of software process innovation.

Efforts to define IT curriculum and accreditation standards began at the first Conference on Information Technology Curriculum (CITC-1) in December 2001, which included representatives from 15 Information Technology (IT) programs at four-year schools in the United States, and representatives from the Association for Computing Machinery (ACM), the Institute for Electrical and Electronic Engineers (IEEE), and the Accreditation Board for Engineering and Technology (ABET). Since this conference, this work has been ongoing at CITC-2 (April 2002), CITC-3 (September 2002), and CITC-4 (October 2003), and through committee work which has progressed between these conferences. The three main thrusts of this work have been to define standards for accreditation of IT programs, to define a model curriculum for IT programs, and to distinguish IT programs from the most closely-related academic programs, such as Information Systems and Computer Science. Membership in SIGITE (Special Interest Group on Information Technology Education) of the ACM is now over 300 members and represents most 4-year IT programs and several 2-year IT programs in the United States; the outcome of these three main thrusts should therefore be of wide interest to all those in related programs or at institutions considering forming a similar program. This paper gives some of the details of the results of the work on these three thrusts.

Efforts to define IT curriculum and accreditation standards began at the first Conference on Information Technology Curriculum

No abstract

Abstract. The boundaries of systems engineering are evolving as system related needs evolve. These 'fuzzy' boundaries result in gaps between what users in the systems engineering community need and what the body of knowledge of systems engineering provides. This paper covers various use cases of the body of knowledge of systems engineering and explores gaps in the existing knowledge base in two areas: 1) related disciplines, and 2) emerging systems engineering topics.