Texas Tech - IPFW.edu

Design of real time systems with micro-controllers such as the 68HC11 and
68332. Object oriented .... (PSP), examen, test et inspections. Évaluation des ...

Part of the document


COURSE CATALOG
PROSPECTIVE MEMBERS
THE INTERNATIONAL SOFTWARE ENGINEERING UNIVERSITY CONSORTIUM ISEUC: "I SEE, YOU SEE" UNIVERSITY CODE
Butler University [Undergraduate + Graduate] BUT
California Polytechnic University at San Luis Obispo CALPOLY
[Undergraduate + Graduate]
Carnegie-Mellon University [Graduate] CMU
Embry-Riddle Aeronautical University [Graduate] ERAU
Indiana University-Purdue University at Indianapolis IUPUI [Undergraduate + Graduate] Mercer University MER [Graduate] Monmouth University [Undergraduate+Graduate] MON
Murdoch University [Undergraduate] MUR
Purdue University PUR [Undergraduate + Graduate] Rochester Institute of Technology [Undergraduate] RIT
Stevens Institute of Technology [Graduate] SIT
Texas Tech University [Graduate] TTU
University of Michigan-Dearborn UMD [Undergraduate + Graduate] University of Ottawa OTTAWA
VERSION 0.26 LOTS OF CRITIQUING REQUIRED!!! PLEASE CORRECT: MISSING COURSES +: CURRENTLY AVAILABLE VIA DISTANCE LEARNING
*: PLANNED TO BE AVAILABLE VIA DISTANCE LEARNING
-: NO PLANS TO PROVIDE VIA DISTANCE LEARNING
MARCH 5, 2001 KEN MODESITT UNIVERSITY OF MICHIGAN-DEARBORN DISTRIBUTION OF COURSES BY LEVEL NEED
UNIVERSITY UNDERGRAD GRAD TOTAL DETAIL
BUTLER 1 1 1
CALPOLY 5 2 7 3
CMU 12 12
ERAU 10 10 10
IUPUI
MER 18 18
MON 15 20 30 15
MUR 11 11 29
PURDUE 2 1 3
RIT 12 2 14
SIT 11 11
TTU 9 9
UMD 3 16 19
OTTAWA 14(Eng)+14(Fr) 8(Eng)+4(Fr)
TOTAL 63(Eng)+14(Fr) 109 (Eng)+4(Fr) 172(Eng)+18(Fr)
Butler University [Undergraduate] (BUTLER) [www.butler.edu/csse] CS XXX: Software Maintenance, taught by Panagiotis (Panos) K. Linos California Polytechnic University at San Luis Obispo [Undergraduate]
(CALPOLY] [www.csc.calpoly.edu] CSC 205 Software Engineering I (4) (Also listed as CPE 205)
Introduction to the software lifecycle. Methods and tools for the analysis,
design, and specification of large, complex software systems. Project
documentation, organization and control, communication, and time and cost
estimates. Group laboratory project. Graphical User Interface Design.
Technical presentation methods and practice. Software design case studies
and practices. Ethical and societal issues in software engineering.
Miscellaneous course fee may be required- see Class Schedule. 3 lectures, 1
laboratory. Prerequisite: CSC 103. CSC 206 Software Engineering II (4) (Also listed as CPE 206)
Continuation of the software lifecycle. Methods and tools for the
implementation, integration, testing and maintenance of large, complex
software systems. Program development and test environments. Group
laboratory project. Technical presentation methods and practice. Ethical
and societal issues in software engineering. 3 lectures, 1 laboratory.
Prerequisite: CSC 205.
CSC 402 Software Requirements Engineering
In approval process CSC 405 Software Design and Construction
In approval process CSC 406 Software Deployment
In approval process CSC 508 Software Engineering I (4)
In-depth study of requirements engineering, software project management,
formal specifications and object-oriented analysis. 4 seminars.
Prerequisite: CSC 205 and graduate standing, or consent of instructor. CSC 509 Software Engineering II (4)
In-depth study of software modeling and design. Formal design
methodologies. Design patterns. Detailed case studies of existing projects.
Tools and methods for designing large software systems. 4 seminars.
Prerequisite: CSC 508 and graduate standing, or consent of instructor.
Carnegie-Mellon University (CMU) [www.distance.cmu.edu]
The Distance Education Program does not supply textbooks as part of the
course support. Textbooks required for Software Engineering courses may be
purchase from your favorite bookseller. 651. +Models of Software Systems
Scientific foundations for software engineering depend on the use of
precise, abstract models for characterizing and reasoning about properties
of software systems. This course considers many of the standard models for
representing sequential and concurrent systems, such as state machines,
algebras, and traces. It shows how different logics can be used to specify
properties of software systems, such as functional correctness, deadlock
freedom, and internal consistency. Concepts such as composition mechanisms,
abstraction relations, invariants, non-determinism, inductive definitions
and denotational descriptions are recurrent themes throughout the course. This course provides the formal foundations for the other core courses.
Notations are not emphasized, although some are introduced for
concreteness. Examples are drawn from software applications. After completing this course, students will:
. understand the strengths and weaknesses of certain models and logics
including state machines, algebraic and process models, and temporal
logic
. be able to select and describe appropriate abstract formal models for
certain classes of systems, describe abstraction relations between
different levels of description, and
. reason about the correctness of refinements
. be able to prove elementary properties about systems described by the
models introduced in the course Prerequisite: Undergraduate discrete math including first-order logic,
sets, functions, relations, proof techniques (such as induction). If possible, Methods of Software Development should be taken concurrently.
[ASYN] 652. +Methods of Software Development
Practical development of software requires an understanding of successful
methods for bridging the gap between a problem to be solved and a working
software system. This course focuses specifically on methods that guide the
software engineer from requirements to code. The course will provide
students with both a broad understanding of the space of current methods,
and specific skills in using these methods. After completing this course, students will:
. be able to use at least two software engineering methods effectively and
make a critical assessment of the strengths and weaknesses of a broad
range of methods
. understand the dimensions along which methods differ
. understand the tradeoffs in making choices along those dimensions. Prerequisite: Experience with at least one large software system, either
through industrial software development experience or an undergraduate
course in software engineering, compilers, operating systems, or the like. If possible, this course should be taken either concurrently or after
Models of Software Systems and Management of Software Development.
[ASYN] 653.
654. +Managing Software Development
Large scale software development requires the ability to manage resources -
both human and computational - through control of the development process.
This course provides the knowledge and skills necessary to lead a project
team, understand the relationship of software development to overall
product engineering, estimate time and costs, and understand the software
process. Topics include life cycle models, requirements elicitation,
configuration control, environments, and quality assurance, all of which
are used broadly in other core courses and the Studio. After completing this course, students will:
. be able to write a software project management plan, addressing issues of
risk analysis, schedule, costs, team organization, resources, and
technical approach
. be able to define the key process areas of the Capability Maturity Model
and the technology and practices associated with each and a variety of
software development life cycle models and explain the strengths,
weaknesses, and applicability of each
. understand the relationship between software products and overall
products (if embedded), or the role of the product in the organizational
product line
. understand the legal issues involved in liability, warranty,
patentability, and copyright
. understand the purpose and limitations of software development standards
and be able to apply sensible tailoring where needed
. be able to use software development standards for documentation and
implementation
. be able to apply leadership principles
. be able to perform requirements elicitation Prerequisite: Students must have had industrial software engineering
experience with a large project, or a comprehensive undergraduate course in
software engineering.
[ASYN] 671. Software Development Studio I A Sample of Past Studio Projects The Studio provides students with a laboratory for direct application of
concepts learned in coursework. It has produced a variety of software
products. Clients have included Boeing, NASA, Westinghouse, Innovative
Systems, Inc. and the United States Air Force. Here is a