Conference Session

Software Engineering Constituent Committee Division Technical Session 3

Collection

2016 ASEE Annual Conference & Exposition

Authors

Dan Budny P.E., University of Pittsburgh; Elizabeth E. Vidal, Universidad Nacional de San Agustín

Tagged Topics

Diversity

Tagged Divisions

Software Engineering Constituent Committee

student’s improvements reached by other engineeringprograms is explained and discussed as the jumping board for the development of the newcourse. The goals for initial professional awareness in student’s communication artifactswere related to specific Accreditation Board for Engineering and Technology (ABET)criteria. A new course called Writing Articles and Research Reports (RAII) taught withinthe student’s major department was created emphasizing effective communication and theneed for continuous learning with the understanding of ethics and professionalresponsibility. The constructivist approach was used to design the course and anexposition of the mapping between the design of the course and the skills that are intendedto achieve is outlined in

Conference Session

Software Engineering Outreach: Industry, K-12

Collection

2013 ASEE Annual Conference & Exposition

Authors

Massood Towhidnejad, Embry-Riddle Aeronautical Univ., Daytona Beach; Thomas B Hilburn, Embry-Riddle Aeronautical Univ., Daytona Beach; Richard E Fairley, Software and Systems Engineering Associates (S2EA)

Tagged Divisions

Software Engineering Constituent Committee

CBOK and its extensions, which arestrongly related to the CBOK, DOMAIN, DEPTH, SYS ENG, ETHICS, and RECONCILEoutcomes (see Table 3). Figure 2 depicts the organization of the Core BOK, with percentage ofcurriculum content designated for each core area. Notice that the CBOK occupies approximately50% of the curriculum allowing flexibility and specialization in curriculum design andsupporting its extension to support outcomes DOMAIN and DEPTH.The primary source for developing the CBOK was the SWEBOK4. Knowledge elements werealso derived from SE20045 and other sources6, 7, 8. In the study and analysis of these sources, itwas decided that although the SWEBOK organization and content would dominate, variouschanges in areas and topics were needed to

Conference Session

Software Engineering Constituent Committee Division Technical Session 2

Collection

2014 ASEE Annual Conference & Exposition

Authors

Vignesh Subbian, University of Cincinnati; Carla C. Purdy, University of Cincinnati

Tagged Divisions

Software Engineering Constituent Committee

course. After the session, the students combine their perspectives from both retrospection and Page 24.1301.2 examination to reflect on how they will perform differently in their next co-op rotation or work assignment.Five UnLecture sessions were designed and executed as a part of the course EECE 3093C–Software Engineering during the Summer 2013 semester. The following is the list of sessionthemes:1. Project Management and Team Work2. Requirements Analysis, Design, and Modeling3. Software Implementation Techniques and Practices4. Testing and Code Maintenance5. Ethics and Technology/Patent WarsIt can be observed that session themes are

Conference Session

Software Engineering Constituent Committee Division Technical Session 1

Collection

2015 ASEE Annual Conference & Exposition

Authors

Anna Koufakou, Florida Gulf Coast University

Tagged Divisions

Software Engineering Constituent Committee

first implementation of this courseachieved positive student feedback and performance in the class. Results and lessons learned arealso discussed in the paper.Literature ReviewDespite the importance of Requirements Engineering (RE) in Software Engineering, RE is notemphasized in computing education. In fact, most computer science and software engineeringprograms do not include RE courses and tend to cover this area using a few class periods1,2.Additionally, topics and careers related to RE, and subsequently a related course, are perceivedas uninteresting and not relevant to future career prospects3, 4. This is described very well by(Lethbridge et al.)5 as follows: “Anyone who has tried to teach topics such as ethics, quality, process

Conference Session

Software Engineering Curricula

Collection

2012 ASEE Annual Conference & Exposition

Authors

Susan Darling Urban, Texas Tech University; Joseph E Urban, Texas Tech University; Susan A. Mengel, Texas Tech University; William M. Marcy P.E., Texas Tech University; Patrick E. Patterson, Texas Tech University

Tagged Divisions

Software Engineering Constituent Committee

economics of systems. Similar to computer science, a specialtopics course is also available. Ethics in engineering is also included to emphasize theimportance of ethics in the engineering of complex software systems.The curriculum includes a 3-credit hour capstone design and implementation project. The projectis a group project requiring that students work in teams to address the systems and softwareengineering aspects of the project.             Page 25.1346.6  Table  1:  MSSE  degree  program  with  systems  and  software  engineering  focus  CORE  COURSES  (12  Hours)  CS 5373 Software Modeling and Architecture. This course introduces the theory

Conference Session

Software Engineering Constituent Committee Division Technical Session 1

Collection

2014 ASEE Annual Conference & Exposition

Authors

Vignesh Subbian, University of Cincinnati; Carla C. Purdy, University of Cincinnati

Tagged Divisions

Software Engineering Constituent Committee

Code of Ethics to class work (d, f).A few supplementary student learning outcomes are as follows:6. Identify and relate real-world/cooperative education experiences to coursework, and reflect on the connection between classroom learning and software engineering practice (i).7. Comprehend global software engineering concepts and challenges (a, h).Course DesignLectures: The course material primarily focuses on the first five Knowledge Areas (KAs) of theSoftware Engineering Body of Knowledge (SWEBOK)3: software requirements, design,construction, testing, and maintenance. While the remaining KAs are covered in a newlydeveloped upper-level course (CS 6028- Large Scale Software Engineering), a brief introductionis given to a few topics such as

Conference Session

Software Engineering Course Content

Collection

2008 Annual Conference & Exposition

Authors

Bruce Maxim, University of Michigan - Dearborn

Tagged Divisions

Software Engineering Constituent Committee

thirty-minute seminar discussions on ethics or professional issues papers requiring independent library and/or Internet research.Classes meet for two hours each week for 56 semester contact hours over a period of 8 months.The ACM/IEEE Computing Curricula 2004 recommendations suggest that 11 lecture hours bedevoted to social, ethical and professional issues. We include this material in our capstone designexperience. The recommended topics associated with these knowledge units come from fourbroad groups of topics:• Historical and social context of computing this includes: definition of computing subject matter, comparison with other disciplines and computing technology uses/limitations.• Topics associated with responsibilities of the

Conference Session

SE Curriculum and Course Management

Collection

2009 Annual Conference & Exposition

Authors

Zulfa Zakaria, IIUM

Tagged Divisions

Software Engineering Constituent Committee

problems in this particularsituation. For the present purpose, an online survey was implemented during a five-month periodfrom the middle of February until June 2007. It covered 16 Australian universities that offeredaccredited BSE programs in Australian universities and was undertaken after being successfullysubjected to the required ethical review process (see the form in the Appendix below). Obtainingthe relevant information from these universities began with emails being sent to the respectiveBSE coordinators requesting details of their Software V&V courses and the lecturers involved. Afollow-up phone call was made if a coordinator did not reply. Once such information wasobtained, an email was sent to all the lecturers nominated to invite

Conference Session

Software Engineering Topics

Collection

2012 ASEE Annual Conference & Exposition

Authors

Lakshmi Ramachandran; Edward F. Gehringer, North Carolina State University

Tagged Divisions

Software Engineering Constituent Committee

clearly describe the changes to be made to the system? Table 3: Rubric used for submissions of technical articles or papers. 1 Do the pages stick to the topic? 2 Are there an appropriate number of links to outside sources? 3 Does the analysis clearly identify the ethical issues? 4 Do the pages treat differing viewpoints fairly? 5 Is the organization of page(s) logical? 6 Do the pages identify several issues that are important in learning about the topic?For the analysis in this paper we collected project review data from two software projects.Students were asked to evaluate the entire project based on rubrics in Tables 1 and 2, one rubricfor each software project. We follow an informal, blind review process, where

Conference Session

SE Curriculum and Projects

Collection

2010 Annual Conference & Exposition

Authors

James Long, Oregon Institute of Technology

Tagged Divisions

Software Engineering Constituent Committee

outsource to the outsource understanding of understanding of of outsource coder as coder situations the outsource outsource coder coders culture, displayed through and an coder situation situation and a work ethic, and communications unwillingness to and a willingness willingness to economic issues. and in lecture/lab adapt to differences to accommodate learn more about conversation. in work ethic and differences in the environment in geographic work ethic and which the coder limitations. geography

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

, prototyping, design, implementation, testing, maintenance activities and management of risks involved in software and embedded systems. C. Process: Graduates know various classical and evolving software engineering methods, can select appropriate methods for projects and development teams, and can refine and apply them to achieve project goals. D. Professionalism: Graduates are knowledgeable of the ethics, professionalism, and cultural diversity in the work environment. E. Quality: Graduates can apply basic software quality assurance practices to ensure that software design, development, and maintenance meets or exceeds applicable standards. F. Presentation: Graduates have effective written and oral communication

Conference Session

Software Engineering Outreach: Industry, K-12

Collection

2013 ASEE Annual Conference & Exposition

Authors

W Eric Wong, University of Texas, Dallas

Tagged Divisions

Software Engineering Constituent Committee

,but also evaluate the deliverables turned in by students, for a software engineering project course. Such apartnership has been very well received by both the students and the industry affiliates. Page 23.742.2 1In addition, a success in the software engineering project course is also critical for ABET accreditationof the Computer Science department and the Software Engineering Program at UTD. Through thiscourse, students have learned, practiced, and improved their skills in communication, teamwork, ethics,and professionalism, as well as received knowledge of contemporary issues

Conference Session

Software Engineering Topics

Collection

2012 ASEE Annual Conference & Exposition

Authors

Walter W. Schilling Jr., Milwaukee School of Engineering; Eric Durant, Milwaukee School of Engineering

Tagged Divisions

Software Engineering Constituent Committee

, attackingSecurity and testing computer networks. 2. Design a threat scenario and implement defenses to mitigate potential attacks. 3. Perform a penetration test of a live network and assess the results. 4. Discuss the legal and ethical issues involved with assessing and testing a network for vulnerabilities and weaknesses. 5. Discuss the roles and responsibilities of network security professionals.A key component of the lecture material for this course is demonstrations of network securitytools and in-class activities to promote active learning. The first time this course was offeredthere was considerable student feedback that supported an additional focus

Conference Session

Software Engineering Curricula

Collection

2012 ASEE Annual Conference & Exposition

Authors

A. Frank Ackerman, Montana Tech of the University of Montana; Sushil Acharya, Robert Morris University

Tagged Divisions

Software Engineering Constituent Committee

required totransform the then current, mostly haphazard, production of software products into a responsiblebranch of engineering. [note 12] In a follow-up piece in Computer [7] Mr. Buckley enunciatedthree major objectives that needed to be met: 1. the establishment of software engineering as an approved [academic] program, included the associated accreditation issues; 2. the establishment of a separate set of software engineering ethics; and 3. the establishment of software engineering as a certified or registered field of engineering.Not mentioned in his Computer piece, but also discussed by the IEEE Board was the need for 4. the creation of a comprehensive set of widely accepted Software Engineering standards.All of these

Conference Session

Software Engineering Topics

Collection

2007 Annual Conference & Exposition

Authors

Marcelo Jenkins, University of Costa Rica

Tagged Divisions

Software Engineering Constituent Committee

management. Other CSQE subjects are covered in the other MScourses shown in Figure 1 above. Table 1. CSQE BOK Subjects covered in our SQM course SUBJECT COVERED IN OUR COURSE? I. GENERAL, KNOWLEDGE, CONDUCT, and ETHICS (10%) A. Quality philosophy and principles Yes 1. Benefits of software quality (Comprehension) Yes 2. Prevention vs. detection

Conference Session

Software Engineering Constituent Committee Division Technical Session 1

Collection

2015 ASEE Annual Conference & Exposition

Authors

Barbara Victoria Bernal, Kennesaw State University, Marietta; Jeffrey Chastine, Southern Polytechnic State University

Tagged Topics

Diversity

Tagged Divisions

Software Engineering Constituent Committee

. She received her M. Ed. and B.S. from Georgia State University (1979, 1981). Prof. Bernal teaches the User-Centered Design, Ethics, and Software Engineering courses at SPSU. The areas of Software Engineering, User-Centered Design and Software Engineering are the focus endeavors. She is a co-founder of the SPSU Usability Research Lab (ULAB) and is directly involved in corporate-sponsor ULAB projects. She has given numerous papers, tutorials and presentations locally and internationally on User-Centered Design, Usability and Software Engineering topics. Barbara is engaged in educational support through her company Software Education and Support (SES). She does specialized software de- velopment and evaluation as a

Conference Session

Tools and Support for Software Education

Collection

2006 Annual Conference & Exposition

Authors

Barbara Gannod, Arizona State University; Kevin Gary, Arizona State University; Harry Koehnemann, Arizona State University

Tagged Divisions

Software Engineering Constituent Committee

Defensive Programming Use Cases Estimation System testing Refactoring User Stories Risk Management Metric tools Code Reviews Requirements Quality Inspections Metrics Requirements Analysis Test Planning Overview Configuration RUP Analysis Release Management Management Professionalism & Ethics Structured Analysis Postmortem Usability

Conference Session

Accreditation and Assessment in SE Programs

Collection

2011 ASEE Annual Conference & Exposition

Authors

Massood Towhidnejad, Embry-Riddle Aeronautical University, Daytona Beach; Thomas B. Hilburn, Embry-Riddle Aeronautical University, Daytona Beach; Salamah Salamah, Embry-Riddle Aeronautical University, Daytona Beach

Tagged Divisions

Software Engineering Constituent Committee

in computing ethics, software project planning, software requirements analysis, teambuilding, design patterns, and software processes analysis. These cases were helpful in teaching“small-scale” software and computing topics, and students were motivated and seemed to enjoythis type of learning activity. However, the case studies addressed issues ranging over a disparateset of problem domains, software engineering practices, and scenario elements; this resulted instudents learning about software engineering practices in bits and pieces - there was very littlecoupling between the case studies and hence no accumulation of scenario experience thatallowed progress toward more substantial and complex problems.The SRS Inspection Case Module (and

Conference Session

Software Engineering Technical Session 2

Collection

2016 ASEE Annual Conference & Exposition

Authors

Stefan Christov, Quinnipiac University; Mark Hoffman, Quinnipiac University

Tagged Divisions

Software Engineering Constituent Committee

managers. The collaboration between the two courses was mainlydriven by the managers’ initiative (based on assignments in the SPM course described below) andoccasional requests for advice by the teams from the ISD course.The assignments of the SPM students (except for one assignment on ethics in software projectmanagement) consisted of two parts. One part of the assignment asked the SPM students to meetwith their teams, to discuss issues related to the current stage of the team project, and to provideadvice, if necessary. The SPM students were expected to provide advice in various areas, such asmaking suggestions about how their teams should approach customers to elicit projectrequirements and how to phrase the elicited requirements; helping teams

Conference Session

Software Engineering Course Content

Collection

2008 Annual Conference & Exposition

Authors

Sushil Acharya, Robert Morris University

Tagged Divisions

Software Engineering Constituent Committee

6: An understanding of Evaluation Tools: CD, HE professional and ethical Assessed Tasks: Collaborative problem solving, Role responsibilities. plays, Inspection meeting, Pair programming. Assessment: 100% of the class scored 80% or more Outcome 7: An ability to Evaluation Tools: CD, PD, HE, RP communicate effectively. Assessed Tasks: Class participation, Project report and presentation, Role Plays, Inspection meetings, Pair programming, Research paper analysis. Assessment

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

appropriate software engineering solutions that address ethical, social, legal, and economic concerns. 7. Understand and appreciate the importance of feasibility analysis, negotiation, effective work habits, leadership, and good communication with stakeholders in a typical software development environment. Page 13.34.11Page 13.34.12Body of KnowledgeThe most difficult task in the entire curriculum effort is creating the Body of Knowledge (BOK)– deciding what is the core knowledge needed for a software engineer at the masters level. If thecore knowledge is too large, universities will not have the flexibility needed to tailor

Conference Session

SE Curriculum and Course Management

Collection

2009 Annual Conference & Exposition

Authors

Richard Stansbury, Embry-Riddle Aeronautical University; Massood Towhidnejad, Embry-Riddle Aeronautical University

Tagged Divisions

Software Engineering Constituent Committee

2 Project Plan 10 Test case 2 Completeness 5 Test execution 2 Traceability Accuracy 3 metrix 2 On time delivery 2 Social/economical/ethic 3 Requirement 12 Completeness 2 Acquisition 3 Quality 1 Operation/Demo Completeness 4 (HW) 8

Conference Session

SE Curriculum and Course Management

Collection

2009 Annual Conference & Exposition

Authors

Francis Lutz, Monmouth University; James McDonald, Monmouth University

Tagged Divisions

Software Engineering Constituent Committee

, chemistry and biology)towards applied, hands-on learning aimed at preparation for the workplace instead of research isgaining national support.3 Implications for existing programs in software engineering are minor,because the field turned from a theoretical framework to an applied framework at its outset. Butother disciplines may begin to expand master’s offerings that are more directly related to theneeds of the workplace, including computer science and mathematics, among others. Programelements would be more likely to include internships and industry sponsored projects,interdisciplinary components, business studies, and emphases on communication, teamwork,project management and business ethics. Such program changes may offer the opportunity

Conference Session

Pedagogical Approaches for Software Engineering

Collection

2012 ASEE Annual Conference & Exposition

Authors

Colin J. Neill, Pennsylvania State University; Joanna F. DeFranco, Pennsylvania State University, Great Valley; Raghvinder S. Sangwan, Pennsylvania State University, Great Valley

Tagged Divisions

Software Engineering Constituent Committee

Engineering, IEEE Computer, Journal or Systems and Software, Software Process: Improvement and Practice, and IEEE Software. He is the author of Antipatterns:Managing Software Organizations and People and Associate Editor-in-Chief of Innovations in Systems and Software Engineering.Dr. Joanna F. DeFranco, Pennsylvania State University, Great Valley Joanna DeFranco earned her Ph.D. in computer and information science from New Jersey Institute of Technology, M.S. in computer engineering from Villanova University, and B.S. in electrical engineer- ing from Penn State University Park. She teaches graduate courses including: Problem Solving, Project Management, Software Systems Design, Computer Forensics, Ethics and Values in

Conference Session

Software Engineering Constituent Committee Division Technical Session 3

Collection

2016 ASEE Annual Conference & Exposition

Authors

Linda M Laird, Stevens Institute of Technology (School of Systems & Enterprises); Nicholas S Bowen, Stevens Institute of Technology

Tagged Topics

Diversity

Tagged Divisions

Software Engineering Constituent Committee

: Engineering Design VII HumanitiesTG403: Senior Innovation I TG404: Senior Innovation IIII. Program Outcomes and Assessment:Graduates of this program will: • Employ sound principles and practices to design and implement software for complex engineered systems. • Assume a variety of roles on multidisciplinary engineering teams. • Communicate effectively with stakeholders in oral, written, and newly developing modes and media. • Demonstrate professionalism, including continued learning and professional activities. • Contribute to society by behaving ethically and responsibly.The achievement of these outcomes and the interpretation of results will be assessed using thestandard Stevens processes for

Conference Session

Pedagogical Approaches for Software Engineering

Collection

2012 ASEE Annual Conference & Exposition

Authors

Heidi J.C. Ellis, Western New England University; Gregory W. Hislop, Drexel University; Josephine Sears Rodriguez, Western New England University; Ralph Morelli, Trinity College

Tagged Divisions

Software Engineering Constituent Committee

.1. IntroductionSoftware engineering education has a broad emphasis on students gaining experience with a real-world project and on obtaining an understanding of professional practice including such skills asteamwork, communication, work ethic, self confidence and more. The SE 2004 curriculumguidelines state “The education of all software engineering students must include studentexperiences with the professional practice of software engineering.”1, (pg 9) Indeed, the ComputerScience CC 2005 guidelines2 suggest that students gain both technical knowledge andprofessional skills via participation in a real-world project. Part of the program criteria forSoftware Engineering programs for ABET3 includes the need for students to work in at least

Conference Session

SE Curriculum and Projects

Collection

2010 Annual Conference & Exposition

Authors

Susan Conry, Clarkson University

Tagged Divisions

Software Engineering Constituent Committee

Computing II 77.8% Operating Systems 72.2% Data Structures 66.7% Algorithms 61.1% Programming Languages 50.0% Introduction to Software Engineering 33.3% Software Ethics 33.3% Computer Architecture 27.8% Computer Organization & Assembly Language 22.2% Database Systems 22.2

Conference Session

Software Engineering Topics

Collection

2012 ASEE Annual Conference & Exposition

Authors

Sushil Acharya, Robert Morris University; Walter W. Schilling Jr., Milwaukee School of Engineering

Tagged Divisions

Software Engineering Constituent Committee

: Measured ABET Outcomes Outcome 1: An ability to apply knowledge of mathematics, science and engineering. Outcome 2: An ability to design and conduct experiments, as well as to analyze and interpret data. Outcome 3: An ability to design a system, component or process to meet desired needs. Outcome 4: An ability to function on multi-disciplinary teams. Outcome 5: An ability to identify, formulate, and solve engineering problems. Outcome 6: An understanding of professional and ethical responsibilities. Outcome 7: An ability to communicate effectively. Outcome 8: The broad education necessary to understand the impact of engineering solutions in a global and societal context. Outcome 9: Recognition of the need for and an ability to engage in life-long

Conference Session

Software Engineering Constituent Committee Division Technical Session 1

Collection

2016 ASEE Annual Conference & Exposition

Authors

Dan Tappan, Eastern Washington University

Tagged Divisions

Software Engineering Constituent Committee