Conference Session

SE Curriculum and Course Management

Collection

2008 Annual Conference & Exposition

Authors

J. Scott Hawker, Rochester Institute of Technology; Ian Webber, Rochester Institute of Technology; Michael Starenko, Rochester Institute of Technology; Jeremiah Parry-Hill, Rochester Institute of Technology

Tagged Divisions

Software Engineering Constituent Committee

AC 2008-1750: PRELIMINARY EXPERIENCE OF USING A LEARNING ANDKNOWLEDGE MANAGEMENT SYSTEM FOR AN SE-1 COURSEJ. Scott Hawker, Rochester Institute of Technology Dr. Hawker is an Assistant Professor of Software Engineering at the Rochester Institute of Technology (RIT). He graduated with a B.S. and M.S. in Electrical Engineering from Texas Tech University. He graduated with a Ph.D. in Electrical Engineering from Lehigh University. He has over 15 years of industry experience developing large-scale, multi-agent information and control systems for diverse applications including manufacturing, combat pilot mission decision support, robotics, and surveillance. In these areas, he developed and

Conference Session

Software Engineering Course Content

Collection

2008 Annual Conference & Exposition

Authors

Sushil Acharya, Robert Morris University

Tagged Divisions

Software Engineering Constituent Committee

(SE) is one such engineering discipline where curriculum enhancement throughlaboratory sessions will highly benefit its graduates.Software Engineering (SE)Prior to the 1990s SE was not an explicit engineering discipline. Computing Curricula 20051states that during the 1990’s SE began to develop as a discipline unto itself. Since then thisdiscipline has been playing an important role in the multibillion dollar software industry. SE isdefined as the discipline of developing and maintaining software systems that behave reliablyand efficiently, are affordable to develop and maintain, and satisfy all the requirements thatcustomers have defined for them1. Figure 1 depicts the conceptual territory occupied by SE in theproblem space of computing

Conference Session

Software Engineering Course Content

Collection

2008 Annual Conference & Exposition

Authors

Mark Sebern, Milwaukee School of Engineering; Henry Welch, Milwaukee School of Engineering

Tagged Divisions

Software Engineering Constituent Committee

Copyright © 2008, American Society for Engineering EducationZ NotationThere are a large number of notations and languages, with each formal methods research groupor center offering at least a few original contributions or variations on work done by others [8].One well known option is the Z (pronounced “zed”) notation developed at the ProgrammingResearch Group at Oxford University, for which a number of text and reference books areavailable [5,10,17,18]. Z is based on sets and predicate logic and uses mathematical notation tospecify systems and changes of state.To illustrate how Z can be used in software specification, Figure 1 shows a simple example of astate schema for part of an academic course scheduling system. The upper portion of the

Conference Session

SE Curriculum and Course Management

Collection

2008 Annual Conference & Exposition

Authors

Joseph Clifton, University of Wisconsin-Platteville

Tagged Divisions

Software Engineering Constituent Committee

retrieve semester start-up data from a university database and populate the tool’s SQL databaseTool Functionality for StudentsStudents access the tool via the secure web link: https://gamma.uwplatt.edu/SE_Tools/. They Page 13.105.4are prompted for their university e-Directory login name and password. Upon a successful login,the student is presented with drop-down lists to select the course and project within the course.At that point, the project page comes up, defaulted to the Timelog tab as shown below. Figure 1: Student Time Log and PlanTime log entries are generally made using the “Punch In” / “Punch Out

Conference Session

Software Engineering Course Content

Collection

2008 Annual Conference & Exposition

Authors

Bruce Maxim, University of Michigan - Dearborn

Tagged Divisions

Software Engineering Constituent Committee

semesters. These coursesare required of all software engineering majors. Most students taking these courses do not createserious games as part of their capstone design projects. The educational outcomes for thecapstone design experience appear in Table 1.Students enroll in CIS 4961 after they complete all required software engineering courses. Thecapstone projects generally require about 500 hours of student effort to complete. The majoractivities in CIS 4961 are requirements gathering and project planning (including riskmanagement and quality assurance efforts). The major activities in CIS 4962 are product design,implementation, and testing. Serious game projects usually make use of a rapid prototyping

Conference Session

SE Curriculum and Course Management

Collection

2008 Annual Conference & Exposition

Authors

Arthur Pyster, Stevens Institute of Technology; Devanandham Henry, Stevens Institute of Technology; Richard Turner, Stevens Institute of Technology; Kahina Lasfer, Stevens Institute of Technology; Lawrence Bernstein, Stevens Institute of Technology; Kristen Baldwin, Office of the Under Secretary of Defense (Acquisition, Technology, Logistics)

Tagged Divisions

Software Engineering Constituent Committee

written now. More on the specific content of these releases is explainedlater in this paper. The resulting curriculum will be suitable for a university education leading toa Masters Degree in SwE.EngagementFour types of organizations must engage in creating the reference curriculum in order to ensureits correctness and to maximize its usefulness and impact: 1. The industrial and government workforce who are the customers of the curriculum, establish the demand-side requirements for the curriculum. Those requirements take the form of needed SwE competencies in graduating students; i.e., knowledge they expect to be learnt, skills they expect to be mastered, and behaviors they want to be demonstrated. That workforce will be

Conference Session

Software Engineering Course Content

Collection

2008 Annual Conference & Exposition

Authors

Salamah Salamah, Embry-Riddle Aeronautical University, Daytona Beach; Ann Gates, University Of Texas - El Paso

Tagged Divisions

Software Engineering Constituent Committee

a complementary fashion, the behaviors specified by patterns and scopes provideclear and simple examples that can enhance the understanding of these testing techniques. In thispaper, we describe an approach and present general lessons and exercises that demonstrate howpatterns and scopes can be used to teach boundary value analysis and equivalence class testing,which are two of the most commonly used black-box testing techniques. As a side effect of thisapproach, students are exposed to, and become familiar with, formally specifying system behavior.1 Introduction Testing remains the most natural and customary way of verifying a piece of software [6]. Insoftware development, testing ranges from verifying the separate components of the

Conference Session

SE Curriculum and Course Management

Collection

2008 Annual Conference & Exposition

Authors

Joseph Clifton, University of Wisconsin-Platteville; Rob Hasker, University of Wisconsin-Platteville; Mike Rowe, University of Wisconsin-Platteville

Tagged Divisions

Software Engineering Constituent Committee

providing a direct measurement of a specific performance criterion. Course Surveys: Course learning outcomes are included in each course. Students are surveyed in each course and asked whether the course learning outcomes are being met. A mapping of course outcomes to performance criteria is used. This is an indirect assessment measurement. Graduating Senior Exit Surveys: Graduating seniors provide feedback by completing a standard exit survey during the last week of their final semester. The survey is designed using the performance criteria. This is an indirect assessment measurement.As an example, the performance criteria and measurements for Development Outcome B are: B.1: Develops