University of Alaska Fairbanks Advanced Search
 
HELP CONTACT DIRECTORY EVENTS NEWS UAF HOME

2005-2006 UAF Catalog


Degrees and Program Index


Software Engineering

SWE 471W 3 Credits
Software Engineering
(Cross-listed with CS 471W)

Introduction to basic software engineering principles, techniques, methods and standards as applied to the engineering of complex software systems. Topics from software system development process models, multiple view system modeling and specification using UML, classification of software systems, project management and legal issues. (Prerequisites: CS 311; ENGL 211X or 213X; or permission of instructor.) (3+0) Offered Fall


SWE 670 3 Credits
Computer Science for Software Engineers
(Cross-listed with CS 670)

An overview and survey of the theoretical underpinnings of computer science. Topics are taken from the areas of algorithms and data structures; computer architecture; computer networks, communications and operating systems; computability and formal languages; languages and compilation. Also available via Independent Learning. Also available via Independent Learning. (Prerequisite: admission to the Master of Software Engineering degree program. Not required for students with a B.S. degree in Computer Science.) (3+0) Offered Fall, Spring


SWE 671 3 Credits
Advanced Software Engineering
(Cross-listed with CS 671)

Advanced software development as an engineering discipline. Includes investigation of current tools, standards, foundation and trends in software engineering from component-ware, software system composition, e-systems, software architecture and CASE tools. (Prerequisites: CS 471 and acceptance into the Master of Software Engineering degree program; or permission of instructor.) (3+0) Offered Spring


SWE 672 3 Credits
Software Process Improvement
(Cross-listed with CS 672)

Commonly applied methods for improving the software development process. Emphasis on the Software Engineering Institute's Capability Maturity Model (CMM) and specifically on the key process areas of Level 2 and Level 3 of that model. These include software configuration management, software quality assurance and software standards. (Prerequisites: CS 671 or permission of instructor. Next offered 2006--07.) (3+0) Offered Alternate Spring


SWE 673 3 Credits
Software Requirements Engineering
(Cross-listed with CS 673)

Focus on the requirements analysis phase of the software development life cycle. Study ways to obtain, analyze, and specify complete and correct sets of requirements. Critique of selected requirements analysis models. Study of current large scale software developments that have failed or are failing. Development of software requirements specifications for large and real software systems via team efforts. Also available via Independent Learning. (Prerequisites: CS 671 or permission of instructor.) (3+0) Offered As Demand Warrants


SWE 674 3 Credits
(Cross-listed with CS 674)
Software Architecture

Software architectural styles are introduced and defined as structural descriptions of software systems. Methods for constructing and binding software systems are introduced and specified as operational views. The architectural approach, as a classical engineering method for describing structure and behavior of technical artifacts, will be applied for the composition of software systems. (Prerequisite: CS 671.) (3+0) Offered Spring


SWE 690 3 Credits
SWE 691 3 Credits
Graduate Seminar and Project
(Cross-listed with CS 690/691)

A two-semester seminar in whiswech students will, individually or in teams, work on and present the results of major programming or literature survey projects in computer science or software engineering. Written and oral reports will be required. (Prerequisites: 12 credits in graduate computer science or software engineering courses; or permission of Computer Science or Software Engineering graduate advisor.) (3+0) 690 Offered Fall, 691 Offered Spring


Catalog Index | Class Schedule | Admissions

Send comments or questions to the UAF Admissions Office .
Last modified July 21, 2005 by University Relations Web Developer.