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

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 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