Asee peer logo
Well-matched quotation marks can be used to demarcate phrases, and the + and - operators can be used to require or exclude words respectively
Displaying results 1 - 30 of 104 in total
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 Constituent Committee Division Technical Session 1
Collection
2016 ASEE Annual Conference & Exposition
Authors
J. Scott Hawker, Rochester Institute of Technology (COE); Robert Kuehl, Rochester Institute of Technology; Mehdi Mirakhorli
Tagged Divisions
Software Engineering Constituent Committee
havecollected over the years. In addition, we have built in opportunities for students to specify,design, and assess the quality of their own work.The merged requirements and architecture course leads into a two-semester capstone seniorproject. This senior project engages students and external sponsors in an end-to-end,requirements-to-delivery project. Requirements engineering and architecture design are centralto this team-based senior project, and the merged requirements and architecture course givesstudents the system-wide problem-space/solution-space mindset necessary to succeed in theirsenior projects.Course StructureThe merged requirements and architecture course is designed with three main threads that occurin parallel, as Figure 1 shows. We use
Conference Session
Software Engineering Constituent Committee Division Technical Session 1
Collection
2016 ASEE Annual Conference & Exposition
Authors
Pat Smith, Oklahoma Christian University of Science and Arts
Tagged Divisions
Software Engineering Constituent Committee
he worked with Cisco customers designing and deploying core Internet designs and technologies. In 2005 Mr. Smith earned a master’s degree in Computer Science from Colorado State and 1 year later left industry to teach engineering at Oklahoma Christian University. Mr. Smith’s emphasis is in first year student success, mentoring young engineers, and data communications. He consistently scores well in student feedback and enjoys regular strong relationships with his students and classes. c American Society for Engineering Education, 2016Adding Software Engineering Emphasis to an ECE curriculumAbstractThis paper describes a project conducted at Oklahoma Christian (OC) University to add
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
, describes the project, and connects these concepts to studentlearning and a summary of the outcomes.2 Software engineering foundationSoftware engineering is a vast collection of theory and practice with the goal of producing thehighest-quality software at the lowest cost. It shares many characteristics with traditionalengineering design processes, but for the purposes of this work, the following elements are theemphasis. In particular, this course promotes the Agile methodology, which is supposed toachieve the same results without imposing onerous, administration-heavy overhead.1 Agile is nota substitute for proper planning and execution, however, so this freedom demands discipline,which is generally lacking in students at this stage of their
Conference Session
Software Engineering Constituent Committee Division Technical Session 1
Collection
2016 ASEE Annual Conference & Exposition
Authors
Walter W Schilling Jr., Milwaukee School of Engineering
Tagged Divisions
Software Engineering Constituent Committee
systemwas worthwhile.The general process for asynchronous multimedia feedback is shown in Figure 1. Studentssubmit their assignments in a traditional manner using a course management system, in this case,Blackboard. The instructor then grades the assignment, capturing in real time their computerscreen and audio commentary. This is accomplished using one of many readily availablesoftware packages, including but not limited to Camtasia Studio, Microsoft Expression, Jing, orSnagit. As the program is executing or the code is being reviewed, annotations are made on thescreen in real time using a tool such as Epic pen, which allows annotations to be made on top of Figure 1: Asynchronous Multimedia Feedback flow.any desktop. These
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
theprevious semester). The course objectives are listed below: Learn techniques, processes, and challenges involved in requirements elicitation, analysis, validation and management; Be able to work in a group environment to perform activities and provide documentation related to all phases of software development, focusing on requirements analysis, while also carrying out design, implementation, and testing; Be able to construct UML diagrams (e.g. Sequence Diagram, State Diagram); Conduct an oral presentation and demonstration of a software project developed by a group.Table 1 shows a general outline of course topics. For example, “Writing Requirements” includesFormal/Informal/Semi-Formal techniques, SRS standards and recommended
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
is paramount for software engineers to develop the skills and background necessaryto effectively work, communicate and innovate on an international scale. Employers’expectation for collaboration with international counterparts is an increasing computing industrystandard. The effects of the globalization have been felt in the software engineering arenathrough software engineering projects realized by diverse professionals located in differentcontinents with different industrial background, culture, time zone, and language. 1-2International student exchange programs provide educational, personal, and long-term benefits. Page 26.1387.2As a result
Conference Session
Software Engineering Constituent Committee Division Technical Session 1
Collection
2015 ASEE Annual Conference & Exposition
Authors
Raymond Scott Pettit, Abilene Christian University; John D. Homer, Abilene Christian University ; Kayla Michelle McMurry, Abilene Christian University; Nevan Simone, Abilene Christian University; Susan A. Mengel, Texas Tech University
Tagged Divisions
Software Engineering Constituent Committee
. Page 26.230.1 c American Society for Engineering Education, 2015 Are Automated Assessment Tools Helpful in Programming Courses?AbstractAutomated assessment tools (AATs) are growing in popularity in introductory programmingcourses, but researchers may have a difficult time synthesizing valid data to draw conclusionsabout the tools’ usefulness. Our first step addressing this issue was to break down our overridingquestion—are automated assessment tools helpful in programming courses?—into four morespecific questions: (1) Have AATs proven to be helpful in improving student learning? (2) Dostudents think that AATs have improved their performance? (3) After having used the tools
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
in contemporary softwareengineering principles, the experimental version of the course incorporated the followingvariations:1. The laboratory project now involves open-source mobile application development;2. The hybrid design methodology (waterfall and XP) is further explored by incorporating two or more development cycles into the project, while additional classroom activities further understanding of connections between the development process and application needs;3. Five active-learning sessions are included to enable reflection on past co-operative education or internship experiences and relate them to classroom learning. The objective of this novel pedagogical strategy, which we call UnLecture, is to bridge the gap between
Conference Session
Software Engineering Constituent Committee Division Technical Session 1
Collection
2014 ASEE Annual Conference & Exposition
Authors
J. Jenny Li, Kean University; Patricia Morreale, Kean University
Tagged Divisions
Software Engineering Constituent Committee
studentsfor future software engineering courses. The two concepts are integrated developmentenvironment (IDE) and basic software testing. We observed the students’ progress and found thaton average students can program similar projects 80% faster after learning and using the twosoftware engineering concepts. 1. Introduction Introductory software programing is an important first-year course that brings students to thedoor step of the CS major, which we consider as a CS1 course based on the definition given in[1]. It is also a requisite course for many students majored in Science, Technology, Engineeringand Math (STEM). The majority of the curriculum of this course is to teach a specificprograming language without any introductory concepts of
Conference Session
Software Engineering Constituent Committee Division Technical Session 1
Collection
2014 ASEE Annual Conference & Exposition
Authors
Tanmay Bhowmik, Mississippi State University; Nan Niu, Mississippi State University; Donna Reese, Mississippi State University
Tagged Divisions
Software Engineering Constituent Committee
a plan, implement the plan, and evaluate the so-lution. We find that students show significant deficiency in the overall problem solving pro-cess, whereas many professionals follow unique and effective tracing techniques in definingthe problem, and in developing and implementing the plan. We identify the improvement ar-eas and propose a set of learning activities for Software Engineering students to enhance theirtracing skills. We implement two learning activities in a Software Engineering course andreport our experience. Our study contributes to the improvement of training students in per-forming ART and other information-intensive tasks in Software Engineering.1 IntroductionA recent study by Begel and Simon1 shows that new college
Conference Session
Software Engineering Topics
Collection
2007 Annual Conference & Exposition
Authors
Valentin Razmov, University of Washington
Tagged Divisions
Software Engineering Constituent Committee
components that worked verywell, then present the ones that did not work so well, and finish with a few that raised eyebrows.3.1.1. What Worked WellStudents appreciated large team sizes (but not too large) that allowed them to work with severalpeers while learning how to do effective group work on non-trivial projects. The class averagesfor this aspect were 1.55, 1.40, 1.62, and 1.38 for the terms when the team sizes were in therange 5-8, and 0.43, 0.12, 1.00, and 0.29 for the terms when team sizes were either bigger orsmaller (Figure 1(a)). In a free-form response, one student noted, “The experience in a largegroup project was great,” echoing the feelings of many others.Another much appreciated aspect was the incremental delivery approach. Class
Conference Session
Software Engineering Topics
Collection
2007 Annual Conference & Exposition
Authors
Mark Sebern, Milwaukee School of Engineering; Mark Hornick, Milwaukee School of Engineering
Tagged Divisions
Software Engineering Constituent Committee
colleagues, Recently, this latter tool has been extended to better supportdevelopment teams and customized process definitions. As a result, the Process Dashboard maywell become a de facto standard for software process data management support.Metrics, Process Design, and Support Tool FunctionalityIn designing or applying data management tools to a chosen software process, one of the firststeps is to choose appropriate product and process measures. Watts Humphrey and his SEIcolleagues, while defining the PSP and TSP processes, developed a set of four base measures,from which many derived measures can be calculated (Table 1). Base Measures Derived Measures Product size (e.g., LOC
Conference Session
Software Engineering Topics
Collection
2007 Annual Conference & Exposition
Authors
Steve Chenoweth, Rose-Hulman Institute of Technology; Mark Ardis, Rochester Institute of Technology; Cheryl Dugas, Rochester Institute of Technology
Tagged Divisions
Software Engineering Constituent Committee
constitutes cooperative learning, it generally incorporates theseelements2,3: 1. Positive interdependence: Team members rely on each other to achieve the common goal. 2. Face-to-face interaction: Team members do most of the work together. They provide assistance, encouragement and feedback to the other team members. 3. Individual accountability and personal responsibility: Each team member is responsible for doing his/her share of the work, and is expected to master all necessary material. 4. Interpersonal and small-group skills: Team members use effective communication and conflict-management skills. 5. Group processing: Team members set common goals, reflect on team accomplishments and make adjustments as
Conference Session
Software Engineering Topics
Collection
2007 Annual Conference & Exposition
Authors
Marcelo Jenkins, University of Costa Rica
Tagged Divisions
Software Engineering Constituent Committee
graduate level.1. IntroductionSoftware quality management (SQM) is defined as the set of activities to direct and control asoftware organization with regard to the quality of its processes, products, and services. SQMencompasses the planning, control, assurance, and improvement of the organizational qualitysystem, defined as the collection of policies, objectives, procedures, measurements, methods, andtools that are established and maintained by the organization to fulfill the requirements of thecustomer14.A good SQM system is an essential ingredient for software organizations to be competitive intoday’s global information technology market, but at the same time SQM is certainly one of themost complicated subjects to teach at any level for the
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 Teaching Techniques
Collection
2009 Annual Conference & Exposition
Authors
J. Scott Hawker, Rochester Institute of Technology
Tagged Divisions
Software Engineering Constituent Committee
part of the course is devoted to software processmodeling concepts. This section describes and gives example models of that portion of thecourse content. The teaching approach leverages the student’s understanding of using UML tomodel systems, in general, and in particular makes parallels between software product models inUML and software process models in UML.Figure 1 is a UML diagram that illustrates the relationships between roles, activities, and workproducts in a software engineering process, and Figure 2 is the same diagram, using the SPEMUML stereotype notation. 0..* Activity Performs 0
Conference Session
Software Engineering Teaching Techniques
Collection
2009 Annual Conference & Exposition
Authors
Clifton Kussmaul, Muhlenberg College
Tagged Divisions
Software Engineering Constituent Committee
model, and a series of relatedactivities, assignments, and projects. Third, it concludes with benefits and future directions.1. IntroductionSoftware projects play a major role in software engineering (SE) education, and have a longhistory and extensive literature7. General principles for instructional design can help instructorsto design more effective projects and project-based courses. These principles suggest that Freeand Open Source Software (FOSS) can be used to support and enhance SE projects and projectcourses. This paper proposes that faculty can help students by using a five step “USABL” modelin which students use FOSS projects, study the project as a worked example, add minorenhancements, build larger components, and finally leverage
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
delivering the educational outcomes promised to its students and as a mechanism toprovide feedback to the students so that they may improve as discussed in McGourty et al.1. Inthis section, a survey of papers related to the assessment of individual students participating inteam projects is presented.In Kaufman et al.2, 3, the authors present an assessment technique for evaluating individuals incooperative learning teams based on a modified version of Autorating, as defined by Brown4.For this technique, students were asked to assess their peers using a pre-defined set of linguisticterms for a variety of criteria. A numeric value is assigned to each linguistic term. Eachstudent’s contribution factor is then calculated as their rating average divided
Conference Session
Software Engineering Teaching Techniques
Collection
2009 Annual Conference & Exposition
Authors
Salamah Salamah, Embry-Riddle Aeronautical University, Daytona Beach; Steve Roach, University of Texas, El Paso; Omar Ochoa, University of Texas, El Paso; Veronica Medina, University of Texas, El Paso; Ann Gates, University of Texas, El Paso
Tagged Divisions
Software Engineering Constituent Committee
languages. The paper presents study that was conducted at two institutionsto compare the new approach with the traditional one in teaching formal specifications. The newapproach uses a model checker and a specification tool to teach Linear Temporal Logic (LTL), aspecification language that is widely used in a variety of verification tools.1 Introduction In software engineering, formal techniques such as software runtime monitoring [5], and modelchecking [3, 8] require formal specifications that are based on mathematics. Formally specifying thebehavior of a software system, however, is a difficult task because it requires mathematical sophis-tication to accurately specify, read, and understand properties written in a formal language
Conference Session
Software Engineering Teaching Techniques
Collection
2009 Annual Conference & Exposition
Authors
Janusz Zalewski, Florida Gulf Coast University; Andrew Kornecki, Embry-Riddle Aeronautical University; Jerzy Nogiec, Fermi National Accelerator Lab
Tagged Divisions
Software Engineering Constituent Committee
. For example, for thedata acquisition system, the task was to use a VMI/VME-4514A analog I/O board andVMI/VME-2532 digital I/O board with the processing on VME Motorola target board runningVxWorks, to use a PT-326 process trainer and accomplish a close-loop proportional control. Thedata acquisition implemented via sample sequencing of operations used for software designpurposes is presented in Fig. 1, as a sequence diagram developed by a student team in a designphase. Figure 1. Sequence Diagram for Data Acquisition and Control Experiment The experiments outlined above, as well as simple team projects, although meeting theirindividual objectives, are not sufficient for comprehensive education of software engineers whowould like to
Conference Session
SE Curriculum and Course Management
Collection
2009 Annual Conference & Exposition
Authors
Zulfa Zakaria, IIUM
Tagged Divisions
Software Engineering Constituent Committee
. The survey’s results and analysis facilitate thediscussion of further details concerning what is lacking in the teaching of each topic for eachcategory. An initial suggestion that would contribute to overcoming this educational shortfall isexplained briefly in the Future Work section.1. IntroductionSoftware testing comprises a process of revealing any errors that may exist within a particularpiece of software [1]. The Verification and Validation (V&V) procedures applied involve bothstatic and dynamic techniques of system checking designed to ensure that the tested programsatisfies its specifications and meets the expectations of the stakeholders [2]. It is the softwaretester who is responsible for constructing and executing such tests. As
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
in the US is growing. In 2007, therewere almost 2,000 students enrolled in software engineering programs and approximately 625bachelor’s degrees were awarded.Concomitantly, bachelor degree programs in Information Technology (IT) and InformationSciences (IS) are expanding more rapidly. The graduates of these programs will be an increasingproportion of the technical, professional labor force. Their backgrounds will be different fromthose hired with degrees in either computer science or engineering. They will seek out differentcontinuing professional development opportunities and aspire to different target positions. Theincreasing popularity of accredited IT, IS and SE programs is reflected in the data of Figure 1.Many influences affect the
Conference Session
Software Engineering Curriculum Support
Collection
2006 Annual Conference & Exposition
Authors
James McDonald, Monmouth University
Tagged Divisions
Software Engineering Constituent Committee
be considering employer surveys for this purpose.Program Educational ObjectivesIn 2000 the faculty established a set of educational outcomes for the program. They werefirst developed by the department faculty. Near the end of that academic year wesurveyed all of our MSSE alumni and the members of our Industrial AdvisoryCommittee, asking them to comment on the appropriateness of objectives and requestingsuggestions for improvement. We received numerous responses and modified theobjectives using that input. The resulting list of objectives follows.The BSSE program alumni will, within the first three to five years after graduation, 1. Become members of organizations that develop or use software and/or enter graduate school
Conference Session
Tools and Support for Software Education
Collection
2006 Annual Conference & Exposition
Authors
Ben Garbers, University of Wisconsin-La Crosse; Kasi Periyasamy, University of Wisconsin-La Crosse
Tagged Divisions
Software Engineering Constituent Committee
problem and then write the software requirements specification (SRS)document. Since the SRS serves as the basis for design, testing and maintenance of the softwareproduct, the students are expected to follow some standard such as IEEE 830-19981 whiledeveloping the SRS. A sample functional requirement in IEEE standard format is shown inFigure 1. Index: ATM.2 Name: Deposit Purpose: To deposit an amount into an account Priority: High Input parameters: account number, amount Output parameter: None Action: Ensure that account number exists. Ensure that amount is greater than zero
Conference Session
Software Engineering Teaching Methods and Practice
Collection
2006 Annual Conference & Exposition
Authors
Frank Tsui, Southern Polytechnic State University; Orlando Karam, Southern Polytechnic State University
Tagged Divisions
Software Engineering Constituent Committee
presentations. All necessary clarifications orreclassifications of data were resolved during these weekly status presentations.Each software project team was graded on the basis of the following criteria. - meeting the functional requirements - meeting the schedule (both intermediate and final) - monitoring the project effectivelyThe teams may earn similar letter grade such as B, but they were also given numericalgrades to retain a finer level of granularity. Project team success is defined in terms of theproject team grade, and the numerical grade served as the measuring scale for success.The following are the specific questions that we will address in this paper. 1. Does the amount of communications affect