- 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
, “Integrating formal methods tools into undergraduate computer science curriculum”, Proceedings of the 36th ASEE/IEEE Frontiers in Education Conference, October 2006.17. J. Spivey. The Z notation - A Reference Manual (Second Edition). Prentice Hall, 1992.18. J. B. Wordsworth, Software Development with Z, Addison-Wesley, 1992.BiographiesMARK J. SEBERN is a Professor in the Electrical Engineering and Computer Science Department at the MilwaukeeSchool of Engineering (MSOE), and was the founding program director for MSOE's undergraduate softwareengineering program. He has served as an ABET program evaluator for software engineering, computer engineering,and computer science.HENRY L. WELCH is a Professor of computer and software engineering in the
- 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
thatholds learning content for Software Engineering courses, and provides students, project teams,and instructors with advanced tools to create, share, and annotate both the learning content andan organizational structure for that content. Traditional course management systems, teamproject repositories, wikis, etc., usually fragment information into silos (that is, into distinctinformation storage locations which are not integrated). We seek a system to help integrate thefragmented information into a whole across the curriculum and the student’s academic careerand to improve student interaction with learning content and with each other in project teams
- 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
architecture. 12. GSwERC will be international in scope. 13. The development of GSwERC will be broadly based. 14. GSwERC will include exposure to aspects of professional practice as an integral component of the graduate curriculum. 15. GSwERC will include discussions of strategies and tactics for implementation, along Page 13.34.9 with high-level recommendations. 16. The distinction between SE2004 and GSwERC will be clear and apparent. 17. GSwERC will identify prerequisite requirements for students to enter a masters program in software engineering.Expectations at EntryAmong the most challenging decisions is deciding what
- 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
engineering major is two-semester course sequence. The entireclass works on a single project of substantial size. Students are divided into groups and eachgroup is responsible for completion of a portion of the project. Previously, the author had alwayschosen projects with an industry customer. In fall 2006, the author chose a project with thesoftware engineering faculty members as customers. The initial project goal was to produce atool to automate the periodic monitoring of student progress on projects. However, because theclass had 20 students, it was believed that a more comprehensive, integrated product could beattempted to help address concerns with other tools. In particular, the desire was to incorporateaspects of project planning, estimation
- 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
-
Bruce Maxim, University of Michigan - Dearborn
- Tagged Divisions
-
Software Engineering Constituent Committee
paper describes the author’s experiences with teaching an industry-based capstone designcourse. In this course, students work as members of small teams to complete softwaredevelopment projects. These projects proceed from requirements gathering, to analysis, design,implementation, and delivery of products to real-world clients. In recent years, several of theseprojects have involved the development of serious games for real-world clients. Serious gamesare games whose purpose is education in its various forms, rather than entertainment. Seriousgames and simulations can be good candidates for student projects that provide them withopportunities to manage projects with real-world development constraints and deadlines. A finalcumulative written