Computer Science

Units: 1

Fulfills General Education Requirement (FSSR)

Formal deduction in propositional logic. The fundamentals of computer architecture. An elementary exploration of the extent to which symbolic reasoning can be automated, including a consideration of related results in fields such as neuroscience and artificial intelligence. Three lecture hours and one laboratory hour per week.

Units: 1

Fulfills General Education Requirement (FSSR)

Solving problems by writing computer programs. Introduction to computer architecture. Emphasis on symbolic reasoning using examples from a particular computing context. For non-majors. Not open to students who have completed any computer science course that fulfills major requirements. Three lecture hours and one laboratory hour per week.

Units: 1

Fulfills General Education Requirement (FSSR)

Techniques for writing computer programs to solve problems. Topics include elementary computer organization, object-oriented programming, control structures, arrays, methods and parameter passing, recursion, searching, sorting, and file I/O. Three lecture hours and two laboratory hours per week. Students who have received credit for courses numbered CMSC 221 or higher may not take CMSC 150 for credit. Note: Knowledge of the topic of CMSC 150 is a prerequisite to all higher numbered Computer Science courses.

Units: .25-1

Special topics satisfying neither major nor minor requirements.

Units: 1

Fulfills General Education Requirement (FSSR)

Introduction to data structures, including stacks, queues, linked lists, and binary trees. Topics include abstraction, object-oriented programming, recursion, and computational complexity. Three lecture hours and two laboratory hours per week.

CMSC 150.

Units: 1

Sets, functions, elementary propositional and predicate logic, elementary graph theory, recurrence relations, proof techniques (including mathematical induction and proof by contradiction), combinatorics, probability, and random numbers, with applications to computing. Three hours lecture and one hour lab per week.

CMSC 150.

Units: 1

Introduction to techniques necessary for development of large-scale software systems. Topics include the development life cycle; design considerations including OOP, patterns, reuse, and usability; repository management; testing, debugging, and static/dynamic analysis; and group work. Also includes introduction to Unix/Linux environments, and to the C++ programming language, including classes, inheritance, and polymorphism; pointers and dynamic memory allocation; and the C++ Standard Template Library (STL). Three lecture hours and one laboratory hour per week.

CMSC 221.

Units: .25-.5

Participation in development of software, with supervision of computer science faculty. Does not count for computer science major or minor. No more than a total of 1.5 units of CMSC 288 may count toward the total number of units required for a degree.

Units: 1

Fundamentals of computer organization. Topics include instruction and, data representations, assembly language, processor data path design, memory systems and I/O. Also includes examination of how software characteristics impact hardware design and optimization. Three lecture hours and one laboratory hour per week.

CMSC 221 and CMSC 240 (CMSC 240 may be taken concurrently)

Units: 1

Design, analysis, and implementation of advanced computer algorithms. Emphasis is given to problem-solving techniques, including the greedy method, divide-and-conquer, and dynamic programming. Specific problem domains vary. Topics may include sorting, graphs, networks, computational geometry, NP-completeness, approximation algorithms, text processing, distributed systems, and numerical algorithms. Three lecture hours and one laboratory hour per week.

CMCS 221 and CMSC 222.

Units: 1

Structure of operating systems, process management, memory management, file systems, and case studies. Three lecture hours and one laboratory hour per week.

CMSC 222 and CMSC 301.

Units: 1

Project-oriented course. Principles of software engineering will be emphasized throughout. Three lecture hours and one laboratory hour per week.

Two courses at the 300 level that have CMSC 301 or CMSC 315 as a prerequisite, or permission of instructor.

Units: 1

Concepts in design and implementation of programming languages, including compile-time and run-time issues. Support for block-structured procedural languages, object-oriented languages, and functional languages. Three lecture hours and one laboratory hour per week.

Senior standing and CMSC 301 and CMSC 315, or permission of instructor.

Units: 1

Introduction to systematic management of data: design and implementation of relational databases, data modeling, normalization, indexing, relational algebra, query processing, and transaction management. Programming projects include substantial use of SQL and its extensions. Three lecture hours and one laboratory hour per week.

CMSC 221 and CMSC 222.

Units: 1

Introduction to simulation. Discrete-event simulation, Monte Carlo simulation, simulation of queuing and inventory systems, random number generation, discrete and continuous stochastic models, elementary statistics, point and interval parameter estimation, and input modeling techniques. Three lecture hours and one laboratory hour per week.

CMSC 222 and CMSC 240.

Units: 1

The mathematics and computer programming underlying practical machine learning applications, and how to construct and evaluate the quality of such systems. Linear and logistic regression, artificial neural networks, support vector machines, K-means clustering. Other topics within Artificial Intelligence as time permits. Programming projects. Three lecture hours and one laboratory hour per week.

CMSC 221, MATH 211 or MATH 212 or MATH 235, and MATH 245.

Units: 1

(See MATH 328.)

Units: 1

Finite state machines, regular languages, push-down automata, and context-free languages. Turing machines, recursive functions, and related topics. Three lecture hours and one laboratory hour per week.

CMSC 315.

Units: 1

Regular languages, context-free languages, finite automata, push-down automata, lexical analysis, parsing, intermediate representation, and code generation. Three lecture hours and one laboratory hour per week.

CMSC 222 and CMSC 301.

Units: 1

Principles and techniques for data communication between computers. Topics include design and analysis of communication protocols, routing, congestion control, network-centric applications, and recent advances. Three lecture hours and one laboratory hour per week.

CMSC 301.

Units: 1

Principles and techniques for programming computers that have multiple processors. Writing programs for parallel computers that enhance run-time efficiency, portability, correctness, and software modifiability. Three lecture hours and one laboratory hour per week.

CMSC 222 and CMSC 301.

Units: 1

Theory, mechanisms, and implementation of computer security and data protection. Topics include encryption and authentication, program and language security, operating system security, and network security. Three lecture hours and one laboratory hour per week.

CMSC 301 , or permission of instructor.

Units: 1

Device independent two- and three-dimensional computer graphics, interactive graphics, user interfaces, and human factors. Consideration of advanced modeling and rendering. Three lecture hours and one laboratory hour per week.

MATH 245 and CMSC 222 and CMSC 301.

Units: .25-1

To enable well-qualified students who have completed basic requirements for major to work independently in areas not included in curriculum.

Permission of department chair and instructor.

Units: .25-1

No more than 1.5 units of internship in any one department and 3.5 units of internship overall may be counted toward required degree units.

Permission of department chair.

Units: .5-1

Selected topics in Computer Science

Permission of instructor.

Units: 0

Documentation of the work of students who receive summer fellowships to conduct research [or produce a creative arts project] in the summer. The work must take place over a minimum of 8 weeks, the student must engage in the project full-time (at least 40 hours per week) during this period, and the student must be the recipient of a fellowship through the university. Graded S/U.

Approval for summer Arts and Sciences fellowship by faculty mentor.