Computer Engineering Computing Curricula John Impagliazzo Pradip Srimani Andrew McGettrick Robert Sloan IEEE Computer Society / ACM Computing Curricula.

Slides:



Advertisements
Similar presentations
Systems Development Environment
Advertisements

Dept. of Computing and Technology (CaT) School of Science and Technology B.S. in Computer Information Systems (CIS) CIP Code: Program Code: 411.
1 Graduates’ Attributes : EMF, EUR-ACE and Federal Educational Standards Alexander I. Chuchalin, Chair of the RAEE Accreditation Board Graduates’ Attributes.
Graduate Expectations. Critical Thinking & Life Management. IBT graduates are expected to: identify and demonstrate the essential employability skills.
Session F4G - Computing Curricula: Computer Engineering Panel: Pradip K. Srimani, Clemson University David L. Soldan, Kansas State University John Impagliazzo,
Cyber Education Project Accreditation Committee November 2014.
UNIVERSITY OF SOUTH CAROLINA Department of Computer Science and Engineering CSCE 190 Computing in the Modern World CSE Curricula Fall 2014 Marco Valtorta.
© Copyright CSAB 2013 Future Directions for the Computing Accreditation Criteria Report from CAC and CSAB Joint Criteria Committee Gayle Yaverbaum Barbara.
Session F4G - Computing Curricula: Computer Engineering Panel: Pradip K. Srimani, Clemson University David L. Soldan, Kansas State University John Impagliazzo,
Computing Curriculum - Computer Engineering (CCCE) A Model For Computer Engineering Curricula in the Next Decade Victor P. Nelson, David L. Soldan, Andrew.
SE curriculum in CC2001 made by IEEE and ACM: Overview and Ideas for Our Work Katerina Zdravkova Institute of Informatics
Professional Practice and Computing Curricula 2001 Eric Roberts Professor of Computer Science Senior Associate Dean of Engineering Stanford University.
Computer Science Department Program Improvement Plan December 3, 2004.
Computer Engineering Department
IS112 – Chapter 1 Notes Computer Organization and Programming Professor Catherine Dwyer Fall 2004.
Overview of the Rose-Hulman Bachelor of Science in Software Engineering Don Bagert SE Faculty Retreat – New Faculty Tutorial August 23, 2005.
Computer Science Accreditation/Assessment Issues Bolek Mikolajczak UMass Dartmouth, CIS Department Chair IT Forum, Framingham, MA January 10, 2006.
1. An ability to:  Understand the academic requirements you need to obtain your degree  Calculate your GPA  Prepare a draft schedule 2.
UNIVERSITY OF SOUTH CAROLINA Department of Computer Science and Engineering CSCE 190 Computing in the Modern World CSE Curricula Spring 2010 Marco Valtorta.
Software Engineering Education Andy Gravell, Feb 2007.
4 August st Century Computing Curricula 1 Richard J. LeBlanc, Jr. Professor, College of Computing Georgia Institute of Tech nology Atlanta, Georgia,
Program Improvement Committee Report Larry Caretto College Faculty Meeting December 3, 2004.
Bioinformatics Curriculum Guidelines: Toward a Definition of Core Competencies Lonnie Welch School of Electrical Engineering & Computer Science Biomedical.
Orientation to the Social Studies K to 7 Integrated Resource Package 2006.
David L. Spooner1 IT Education: An Interdisciplinary Approach David L. Spooner Rensselaer Polytechnic Institute.
The Influence of the University/College/Department Mission How your university and department’s missions influence your engineering degree requirements.
Moving forward with Scalable Game Design. The landscape of computer science courses…  Try your vegetables (sneak it in to an existing course)  Required.
Georgios Tsirigotis, Electrical Engineering Department, Kavala Institute of Technology, Greece Anna Friesel Electronics and Information Technology, Technical.
OSE2 - 1 Introduction to Software Engineering Professional Issues SWENET OSE2 Module June 2003 Developed with support from the National Science Foundation.
THE NEW TEXAS CORE CURRICULUM (OCTOBER 27, 2011).
Course Overview Course Requirements Knowledge and Skills Student Expectations.
Information Technology
Parallel and Distributed Computing in CS2013 Mehran Sahami Computer Science Department Stanford University.
Updating the Guidelines for Undergraduate Programs in Statistics Nicholas Horton (Amherst College) November 12, 2013 CAUSE Teaching.
Day 1 Session 2/ Programme Objectives
Guide to the Software Engineering Body of Knowledge Chapter 1 - Introduction.
MECE 1101 Introduction to Mechanical Engineering
School of Management & Information Systems
Ciarán O’Leary Wednesday, 23 rd September Ciarán O’Leary School of Computing, Dublin Institute of Technology, Kevin St Research Interests Distributed.
LEFIS W2 Posgraduate Workshop 1 LEFIS, WG 2 Postgraduate studies Meeting, Rotterdam.
Competence Analysis in the Two-subject Study Program Computer Science Jože Rugelj, Irena Nančovska Šerbec Faculty of Education Univesity of Ljubljana 1Beaver.
Designing and implementing of the NQF Tempus Project N° TEMPUS-2008-SE-SMHES ( )
Electrical and Electronic Engineers. Job description/Overview  What a Electronics engineers do is research, design, develop and test precision components.
 CS 5380 Software Engineering. Course Description  This course will survey software engineering methods and processes, including requirements, architecture,
UNIVERSITY OF SOUTH CAROLINA Department of Computer Science and Engineering CSCE 190 Careers in Computer Science, Computer Engineering, and Computer Information.
The Engineering Body of Knowledge Joint Engineers Conference 07 November 2014 Helena, MT Robert A. Green, P.E., F. NSPE President National Society.
ISECON Feinstein1 IM’ LATE FROM THERE TO HERE – FROM HERE TO THERE A FEW BITS AND BYTES David Feinstein Educator of the year 2004.
Automata, Computability, and Complexity Lecture 1 Section 0.1 Wed, Aug 22, 2007.
KFUPM-COE Industrial Advisory Council Meeting 31/5/ Department of Computer Engineering (COE) College of Computer Sciences and Engineering (CCSE)
 Introduction Introduction  Contents of the report Contents of the report  Assessment : Objectives OutcomesObjectivesOutcomes  The data :
The Balance Between Theoretical and Practical Work Within Electrical and Computer Engineering Courses Dr. Bahawodin Baha March Development Partnerships.
EE & CSE Program Educational Objectives Review EECS Industrial Advisory Board Meeting May 1 st, 2009 by G. Serpen, PhD Sources ABET website: abet.org Gloria.
ALUMNI SURVEY AT QUB SCHOOL OF MECHANICAL & MANUFACTURING ENGINEERING QUEEN’S UNIVERSITY BELFAST.
CEN ABET Mini- Retreat March 4, CEN ABET Mini-Retreat Agenda: –State of the Assessments –Discussion on loop closings. –CSE Program Objectives/Outcomes.
Plenary Discussion John Impagliazzo Computing Curricula 2005.
COMPUTER HARDWARE ENGINEERING Created by: Spencer Cho Period 6 Intro to Engineering Design.
1 Trends in Computer Science Education ABU, Zaria, July 17, 2006 Trends in Computer Science Education Sahalu Junaidu, PhD Information and Computer Science.
CEN Faculty MeetingMarch 31, ABET Accreditation Brief history. –1980’s: faculty qualifications sufficed. –1990s: quality of courses, materials, and.
CISE IAB MeetingOctober 15, ABET Accreditation Brief history. –1980’s: faculty qualifications sufficed. –1990s: quality of courses, materials, and.
Foundations in Business - Fall 2006 Foundations in Business.
Presentation of Curricula THE SCHOOL OF ELECTRICAL AND COMPUTER ENGINEERING OF APPLIED STUDIES ELECTRONICS AND TELECOMMUNICATIONS DBBT project meeting,
Study program: Computer Engineering (Računarsko inženjerstvo)
Fundamentals & Ethics of Information Systems IS 201
OUTCOME BASED EDUCATION
Day 1 Session 2/ Programme Objectives
Accepted Students Program
Meeting LIS Competences to Serve Inclusive Community through Curriculum: Case Study in LIS Study Program UIN Sunan Kalijaga Yogyakarta Indonesia Marwiyah.
Department of Computer Science The University of Texas at Dallas
Introduction To software engineering
Objectives & Outcomes Chuck Cone ERAU Oct 30, 2010.
Presentation transcript:

Computer Engineering Computing Curricula John Impagliazzo Pradip Srimani Andrew McGettrick Robert Sloan IEEE Computer Society / ACM Computing Curricula – Computer Engineering Task Force SIGCSE Symposium 2003 February 22

2 Presentation Overview (J.I) l 08:45 John - Introductions (5 mins) l 08:50 Pradip - CCCE and connection with CC2001 project (5 mins) l 08:55 Pradip - Computer engineering & report overview (10 mins) l 09:05 John - Importance of professionalism and history (10 mins) l 09:15 Andrew - Breadth of topic areas in report (15 mins) l 09:30 Robert - Focus on one area in detail (15 mins) l 09:45 Pradip & John - Questions (15 mins) l 10:00 Session ends

3 What is Computer Engineering? Computer engineering embodies the science and the technology of design, construction, implementation and maintenance of the hardware and the software components of modern computing systems and computer-controlled equipment. Computer engineers are solidly grounded in the theories and principles of computing, mathematics and engineering, and apply these theoretical principles to design hardware, software, networks, and computerized equipment and instruments to solve technical problems in diverse application domains.

4 Background: CC2001 (1) (P.S.) l Computing Curricula 2001  Joint effort of IEEE – CS and ACM  Started in 1998  Revise and update 1991 model curricula  Address developments of past decade and endure through the next decade  Separate volumes for Computer Science, Computer Engineering, Software Engineering, Information Systems  Computer Science Volume completed in Dec. 2001

5 Background: CC2001 (2) l Computer Engineering Task Force  Established 2001  16 members currently  Representation of diverse interests/institutions l Curricular Guidelines  Science & math, engineering core  Intersections with EE and CS  Emphasize design and creativity  Laboratory experience  Industry-standard modern tools

6 Outline of the CCCE Volume Woodenman Version Chapter 1. Introduction Chapter 2. Computer Engineering Principles Chapter 3. Professionalism and Computer Engineering Chapter 4. Overview of the Computer Engineering Body of Knowledge Chapter 5. Integration of Engineering Practice into the Computer Engineering Curriculum Chapter 6. Curriculum Implementation Issues Chapter 7. Characteristics of Computer Engineering Graduates Chapter 8. Management Issues Chapter 9. Conclusions Bibliography Appendix A Knowledge Units Appendix B Course Descriptions

7 Professionalism (1) (J.I.) l Computer engineers design and implement computing systems that affect the public l Computer engineers should hold a special sense of responsibility l Almost every aspect of their work can have a public consequence

8 Professionalism (2) l Consequences of professional practice should focus on the public good l Computer engineers must consider the professional, societal, and ethical context in which they practice

9 Practice and Conduct l Do the right thing l Foster best practices l Understand ethical practices l Understand legal issues

10 Codes of Ethics and Practices (1) National Society of Professional Engineers - NSPE Code of Ethics for Engineers Institute of Electrical and Electronic Engineers (IEEE): IEEE Code of Ethics Association for Computing Machinery (ACM): ACM Code of Ethics and Professional Conduct

11 Codes of Ethics and Practices (2) ACM/IEEE-Computer Society: Software Engineering Code of Ethics and Professional Practice International Federation for Information Processing (IFIP): Harmonization of Professional Standards and also Ethics of Computing Association of Information Technology Professionals (AITP): AITP Code of Ethics and the AITP Standards of Conduct

12 Industry Needs National Association of Colleges and Employers (NACE) Conducts annual survey to determine what qualities employers consider most important in applicants seeking employment. What do you think employers want??

13 Top Ten Factors in Communication skills (verbal and written) 2. Honesty/integrity 3. Teamwork skills 4. Interpersonal skills 5. Motivation/initiative 6. Strong work ethic 7. Analytical skills 8. Flexibility & adaptability 9. Computer skills 10. Self-confidence

14 Breadth of Topic Areas (A.M.) l Elements of Hardware l Elements of Software l Elements of Computer Theory l Elements of Mathematics l Elements of Science l Elements of General Education

15 The Body of Knowledge l Hierarchical Structure  Disciplinary subfields (e.g., digital logic)  Units or thematic modules (e.g., switching theory)  Topics (e.g., number systems) l Core vs. Elective Units  Core = should be included in all programs  Elective = inclusion based on program objectives and/or student interest l Organization of BOK does not imply organization of a curriculum

16 Body of Knowledge Topics (1) l Core Topic Areas (15) (Woodenman Version) SPRSocial and Professional Issues CSEComputer Systems Engineering CAOComputer Architecture and Organization SWESoftware Engineering HCIHuman Computer Interaction ESYEmbedded Systems OPSOperating Systems CSYCircuits and Systems (continued)

17 Body of Knowledge Topics (2) NWKNetworks ELEElectronics DIGDigital Logic PRFProgramming Fundamentals ALGAlgorithms and Complexity DSCDiscrete Structures PRSProbability and Statistics

18 Body of Knowledge Topics (3) l Elective Topic Areas (7) (Woodenman Version) DSPDigital Signal Processing VLSVLSI/ASIC Design DGADesign Automation ACPAlternative Computing Paradigms TFTTesting and Fault Tolerance INSIntelligent Systems IHMInformation Management

19 Comp. Systems Engineering (R.S) CSE 0. History and overview of computer systems design [core] CSE 1. Overview of systems engineering [core] CSE 2. Theoretical considerations [elective] CSE 3. Life cycle [core] CSE 4. Requirements analysis and elicitation [core] CSE 5. Specification [core] CSE 6. Architectural design [core] CSE 7. Implementation CSE 8. Testing CSE 9. Maintenance CSE 10. Project management CSE 11. Specialist systems CSE 12. Hardware and software co-design

20 CSE 3: Life Cycle [core] (1) Minimum core coverage : 2 hours Topics: 1.Nature of life cycle, role of life cycle model. Quality in relation to the life cycle. 2.Influence of system size on choice of life cycle model and nature of system – agility issues. 3.Different models of the life cycle – strengths and weaknesses of each. 4.The concept of process. Process improvement. Basis for this is information. 5.Gathering information. 6.Maturity models. Standards and guidelines.

21 CSE 3: Life Cycle [core] (2) Learning objectives: 1.Recognize the need for a disciplined approach to system development and explain the elements of this in particular contexts. 2.Explain how data should be gathered to inform process improvement.

22 What Happens Next? (P.S.) l Strawman Body of Knowledge (2002 June)  Preliminary draft  Public review and comment via website  Solicited review by topic experts  Wide participation sought, including international l Woodenman CCCE Volume (2003 February)  Review of BOK and text chapters l Ironman CCCE Volume (2003 Summer) l Submission to IEEE-CS and ACM (2003 Dec)

23 WHAT SHOULD COMPUTER ENGINEERS KNOW? The Woodenman version of the Body of Knowledge from the “Computing Curricula: Computer Engineering” volume is now available for public review. This is a draft and input from the entire professional community is being solicited. This is your opportunity to voice opinions, comments, and concerns and to help shape the final document. IEEE-CS / ACM Computing Curricula: Computer Engineering Task Force

24 Questions ???