- Conference Session
- Software Engineering Division Technical Session 1
- Collection
- 2017 ASEE Annual Conference & Exposition
- Authors
-
Mark Hoffman, Quinnipiac University; Stefan C. Christov, Quinnipiac University
- Tagged Divisions
-
Software Engineering Division
. The software development project manager needs frequent reporting on each team’sprogress to compile reporting for upper management. A key component of the workplacescenario is the need to provide clear, concise, and accurate technical information to the softwaredevelopment project manager that quickly and easily satisfies the manager’s reporting needs. Inthis way, a workplace scenario integrates technical and communications tasks. The workplacescenario and the maintenance of the handed-off software system drive the demands of the course.A workplace scenario embeds students in a technical workplace task [12]. Workplace scenariosmay be limited to a single assignment within a course or frame an entire course, as they do forthe ISD course. A
- Conference Session
- Software Engineering Division Technical Session 2
- Collection
- 2017 ASEE Annual Conference & Exposition
- Authors
-
Sushil Acharya, Robert Morris University; Walter W Schilling Jr., Milwaukee School of Engineering
- Tagged Topics
-
Diversity
- Tagged Divisions
-
Software Engineering Division
to meet 7 outcomes.Outcome 4 states “Design appropriate solutions in one or more application domains usingsoftware engineering approaches that integrate ethical, social, legal, and economic concerns”. Itis through this outcome we expect students to design solutions that address ethical, social, legal,security, and economic concerns. The importance of security in the curriculum guidelines can benoted from the change in SE education Knowledge Areas. In the 2004 Curriculum Guidelines forUndergraduate Degree Programs in Software Engineering [4] security was listed as an area ofstudy. However in the 2014 Curriculum Guidelines for Undergraduate Degree Programs inSoftware Engineering [5] there is now an increase in the visibility of software
- Conference Session
- Software Engineering Division Technical Session 2
- Collection
- 2017 ASEE Annual Conference & Exposition
- Authors
-
Venkata Rama Chaitra Thota, University of Cincinnati; Nan Niu, University of Cincinnati; Wentao Wang, University of Cincinnati; Carla C. Purdy, University of Cincinnati
- Tagged Divisions
-
Software Engineering Division
, waterfall-style development, we chose an existing software system for ourstudents to build upon. Both baseline systems are relatively mature: iTrust was established in2007 and Mapbox started its development in 2010. Although written mainly in Java, iTrust is aWeb application, whereas Mapbox is a mobile app. This leads to distinct integrated developmentenvironments for our students to use: Eclipse for iTrust and Android Studio for Mapbox. Table 1. Basic course information Semester Spring 2015 Spring 2016Enrollment # of students 62 103information # of teams 15
- Conference Session
- Software Engineering Division Technical Session 2
- Collection
- 2017 ASEE Annual Conference & Exposition
- Authors
-
Walter W Schilling Jr., Milwaukee School of Engineering; Brad Dennis, Milwaukee School of Engineering
- Tagged Divisions
-
Software Engineering Division
performance related issues.The IEEE Software Engineering SE2014 document encourages software engineering programsto cover multiple forms of testing, ranging from unit tests through performance tests. Unittesting, at one extreme of this range, is easily taught as it focuses on small scopes and detailedfunctionality. Another type of testing, integration tests, can also be easily expressed based uponsequence diagrams. These two items must have deep coverage per the curriculum guidelines.However, at the other end of this spectrum is performance testing. Performance testing is muchharder to teach, while also needing much less coverage per the IEEE SE2014 guidelines. Thisarticle will define a set of active learning exercises which were developed to aid in