CSE 90 Systems Engineering and Technical Communications (2012-2013)

CSE 90 Systems Engineering and Technical Communications

(Required for CSE.)
Catalog Data:

CSE 90 Systems Engineering and Technical Communications (Credit Units: 2) Introduces systems engineering concepts, including specification and requirements, hardware and software design, integration, testing, and documentation. Emphasizes organization and writing of reports and effective presentations. (Design units: 0)

Required Textbook:
. Edition, , 1969, ISBN-13 978-0072961492.

. Edition, , 1969, ISBN-13 978-0471027669.

Recommended Textbook:
None
References:

NONE.

Coordinator:
Tony D. Givargis and Amelia C. Regan
Relationship to Student Outcomes
This course relates to Student Outcomes: CAC e, CAC f, CAC g, CAC h, EAC f, EAC g, EAC h, EAC i, EAC j.
Course Learning Outcomes. Students will:

1. Understand the definitions, scope, and distinguishing characteristics of systems engineering.

2. Recognize the different domains prevalent in a typical systems engineering environment.

3. Describe the basic components and/or methodologies used for the definition, design, development, deployment, decommissioning, and disposal of a large-scale system. (CAC g, EAC h)

4. Understand how to research, evaluate, and obtain applicable software/hardware standards. (CAC h, EAC i)

5. Recognize legal issues and responsibilities in engineering contracting (CAC e, EAC f)

6. Understand the value of computing to local, regional, and global institutions (CAC g, EAC h)

7. Identify typical documents used in a systems engineering environment for project milestone deliverables.

8. Understand current issues on computing described in the popular media (EAC j)

9. Recognize ethical engineering practices represented in written and verbal communications in the workplace. (CAC e, EAC f)

10. Demonstrate the effective use of principled reasoning to evaluate/solve ethical, unethical, and non-ethical situations in an engineering environment. (CAC e, EAC f)

11. Demonstrate the ability to make appropriate decisions regarding the form, format, and style of a technical document based on the target audience. (CAC f, EAC g)

12. Recognize effective methodologies for reviewing, editing, and revising a technical document. (CAC f, EAC g)

13. Deliver a dynamic oral presentation of systems engineering technical data to a peer audience. (CAC f, EAC g)

Prerequisites by Topic

College level English

Lecture Topics:
  • Overview of systems engineering principles and concepts
  • Overview of the product development process and product life cycle
  • Overview of systems engineering project management basics
  • Overview of tools and models used in the system design process
  • Basic analysis of alternatives to a system design process
  • Methodological frameworks and systems engineering processes
  • Understanding Legal and ethical responsibilities in engineering
  • Producing effective technical documentation
  • Delivering oral presentations of technical data to peer audiences
Class Schedule:

Meets for 2 hours of lecture and 3 hours of laboratory each week for 10 weeks.

Computer Usage:

Microsoft Office; web research tools

Laboratory Projects:

Research engineering codes of ethics, research design specifications, write system requirements specifications, prepare group design project.

Professional Component

Contributes towards the Computer Science and Engineering major requirements for Engineering Topic courses and Computer Topics courses.

Design Content Description
Approach:
  • Approach:
  • Lectures:
  • Laboratory Portion:
Lectures: 0%
Laboratory Portion: 0%
Grading Criteria:
  • Technical Report: 10%
  • Midterm Exam: 20%
  • Collaborative Research Paper: 30%
  • Oral Presentation of Research Paper: 20%
  • Final Exam: 20%
  • Total: 100%
Estimated ABET Category Content:

Mathematics and Basic Science: 0.0 credit units

Computing: 0.0 credit units

Engineering Topics: 2.0 credit units

Engineering Science: 2.0 credit units

Engineering Design: 0.0 credit units

Prepared:
February 6, 2012
Senate Approved:
February 25, 2003
Approved Effective:
2003 Fall Qtr