A+B. Intro_SJ.1 - University of Maryland University College

MSWE 635 Software Systems Development (3)
Prerequisite: MSWE 603 and either TMAN 640 or MSWE
640; permission of program director is required if the prerequisites
cannot be met. The purpose of this course is to provide
a thorough understanding of the development life cycle as it
applies to large software systems. The course discusses various
a p p roaches to determining if the system implementation is corre c t
during the traditional waterfall model (system analysis, system
design, system implementation, and system use and evaluation),
spiral model, and rapid prototyping. An important aspect of this
course is the integration of the principles of project management,
engineering, and quality concepts to illustrate how the principles
of prevention of defects may be applied across the development
life cycle.
MSWE 640 Software Project Management (3)
This course explores the current theory and practice of software
development project management. Fundamental elements
include integration, scope, time, cost, quality, human resources,
communications, risk, and procurement management as defined
in the Institute of Electrical and Electronics Engineers (IEEE)
standard for project management, which is an adoption of the
Project Management Institute Guide to the Project Ma n a g e m e n t
Body of Know l e d g e . The relationship between each knowledge are a
and the detailed processes required to manage software projects
is explored. Various approaches to software project planning,
software project estimating, networks and scheduling, tracking
and control, and technical and support processes are analyzed.
Students apply the principles covered in this course by developing
a software project management plan for a complex system.
MSWE 645 System and Software Standards and
Requirements (3)
Prerequisite: Either MSWE 601, CSMN 601, or permission of
faculty member. Major models of software requirements and
specifications (sequential and concurrent systems), existing software
standards and practices, and formal methods of software
d e velopment are examined. A comparative survey of various languages
and methods serves to emphasize similarities and significant
differences. Additional topics covered include writing
system and software requirements, formal specification analysis,
formal description reasoning, models of “standard” paradigms,
and translations of such models into formal notations.
MSWE 646 Software Design and Implementation (3)
Pre requisite: Either MSWE 601, CSMN 601, or permission of
faculty member. This course guides the student in the transition
f rom programming-in-the-small to pro g r a m m i n g -in-the-large.
Software development processes and the role of design as applied
in those processes are discussed. Major design methods and
available computer-aided software engineering (CASE) tools,
the proper application of design methods, and techniques for
estimating the magnitude of the development effort are re v i ewe d .
Strengths and weaknesses of the development methods are covered,
along with traceability to requirements and code.
MSWE 647 Software Verification and Validation (3)
Prerequisite: Either MSWE 601, CSMN 601, or permission of
faculty member. The evaluation of software for correctness, efficiency,
performance, and reliability is addressed. Specific skills
covered include program proving, code inspection, unit-level
testing, and system-level analysis. The difficulty and cost of
some types of analysis are examined in addition to the need for
automation of tedious tasks. Problem-solving skills are stressed,
especially in analysis of code. The textbook world is contrasted
with the real world using case studies from the book and personal
experiences. Industry attitudes toward reliability and performance
are also discussed.
MSWE 648 Software Maintenance (3)
Prerequisite: Either MSWE 601, CSMN 601, or permission of
faculty member. This course provides a guide for the transition
from programming for the short term to programming for the
long term. The role of creation and maintenance in the software
development process, as well as analysis and implementation
of a software design, is re v i ewed. The need for software maintenance
and evolution, software maintenance process and perf o r m-
ance issues, planning for extended software life, and effective
mechanisms to control software change are additional topics of
discussion.
w w w. u m u c . e d u / g r a d
Un i versity of Ma r yland Un i versity College | 137 |