Systems Architecting
SAE 549: 3 Units
Meeting 6:30-9:10 pm Tuesday,
in Ronald Tutor Hall (RTH) 109
simultaneous webcast
Viterbi School of Engineering
University of Southern California
Fall 2008
Contents
Contact Information ............................................................................................................ 2
Objectives ........................................................................................................................... 2
Readings .............................................................................................................................. 3
Interaction ........................................................................................................................... 5
Evaluation & Grading ......................................................................................................... 6
Projects ................................................................................................................................ 7
Short Assignments: ......................................................................................................... 7
Major Paper:.................................................................................................................... 7
Other Considerations .......................................................................................................... 9
Class Schedule .................................................................................................................. 10
Syllabus (D. Howard)
Systems Architecting, 2008(3)
Contact Information
Instructor
Denise Howard
Office
Office hours
Office phone
FAX (ISE Dept)
Off-campus phone
e-mail
GER 235
5-6 pm, Tuesday
(213) 740-2433
(213) 740-1120
(661) 947-3566
sdenishoward@msn.com
We encourage you to contact us by e-mail, or to stop by in person for office hours: these
interactions may make a more significant contribution to your overall learning than you
initially suppose. Topics might include research problems, questions, ideas, or
interesting readings.
TA
Yvette Torres
Office
Office hours
Office phone
e-mail
Course website:
GER 207
5-7pm, Wednesday
(213) 740-6664
ytorres@usc.edu
http://den.usc.edu
Objectives

To improve the student’s capability to create, develop, deliver, and support
innovative complex systems that are successful and market leaders in the
student’s domain by means of an interactive educational process

To improve the student’s understanding of the roles of systems architects and
their relationship to systems engineering

To enhance the systems thinking capability and appreciation of the student
rev. 2008.Aug.21
2 (of 10)
Syllabus (D. Howard)
Systems Architecting, 2008(3)
Readings
Primary Text
(Course Reader):
The USC Course Reader, Systems Architecting by Eberhardt
Rechtin which is a reprint of this classic book, otherwise currently
out of print:
[Rechtin, E. (1991). Systems architecting: Creating and building
complex systems. Englewood Cliffs, NJ: Prentice Hall.
ISBN: 0-13-880345-5
This is the original hardcover text, available on the used book
market for around ~$450. We prefer our USC Course Reader,
which has exactly the same content, for ~$30.]
Supporting
materials:
Kesselman-Turkel, J., & Peterson, F. (1982). Research shortcuts
(Rev. ed.). Madison, WI: University of Wisconsin Press.
ISBN: 0-299-19164-8. 136 pages, reading time: about 4 hours.
A small book of helpful strategies for the major research paper.
Rossiter, J. (2007). The APA Pocket Handbook: APA rules for
format and documentation. DW Publishing.
ISBN-13: 978-1933878133
ISBN-10: 1933878134. 54 pages, reading time: as needed or about
2 hours.
A short soft-cover which answers may questions about referencing
and preparing your term report manuscript.
Brynteson, R. D. (2006). Once upon a complex time: Using stories
to understand systems. Farmington, MN: Sparrow Media Group.
ISBN: 0-9719304-8-1. 80 pages, reading time: about 4 hours.
A short introduction to systems thinking.
Tufte, E. R. (2006). Beautiful evidence. Cheshire, CT: Graphics
Press.
ISBN: 0-9613921-7-7
Visual thinking with precision and insight; emphasizes the structure
of design.
Optional:
rev. 2008.Aug.21
Maier, M. W., & Rechtin, E. (2002). The art of systems
architecting (2nd ed.). Boca Raton, FL: CRC Press.
ISBN: 0-8493-0440-7
3 (of 10)
Syllabus (D. Howard)
Supplementary
papers:
Notes:
rev. 2008.Aug.21
Systems Architecting, 2008(3)
A short supplementary article may be assigned as a springboard for
one of the short assignments (see Research Guidelines, below).
These readings will typically be the length of an article in Scientific
American or American Scientist.
Weekly lecture slides will be provided. They will be posted on the
DEN Blackboard course website (see above) in advance.
4 (of 10)
Syllabus (D. Howard)
Systems Architecting, 2008(3)
Interaction
Attendance
This course is webcast and recorded so 100% attendance in the
classroom is recommended but not strictly mandatory. However, we
note that the students who do well are likely to attend the class
synchronously (either in class or remotely) for most sessions. I
strongly encourage you to ask questions and participate in discussions
about the lectures.
If you are taking the class remotely, there will be provisions for
interactive voice communications with the classroom. Your classroom
participation is a factor in your final grade.
NOTE:
Nonparticipation
Once again, staying engaged is essential if you intend to be
successful in this class.
If we have had no contact with you prior to the fourth week of the
class, to protect you, we may exercise the instructor-initiated drop.
Should your non-participation slip by us however, failing to properly
withdraw puts you in jeopardy of failing the class — not a good
outcome and one we do not like to see happen.
Occasional
absences
What if you must miss a class because of work or travel? Use
Blackboard to submit items on time, if you can. If not, please contact
me in advance to negotiate excused late submittal. I suggest that you
make use of the archived class session as soon as possible; if you don’t,
it is very easy to fall irredeemably behind. You are responsible for the
material that was covered. If you have a circumstance that makes it
difficult for you to fully engage with the class, notify us as soon as you
can; we are likely to have more options to help then.
E-mail
I strongly encourage your use of e-mail for questions, comments, and
short idea-generating conversations. Of course, if you prefer face-toface interaction or telephone conversations — those are most welcome
also. Stop by during office hours and discuss architecting with us. For
remote students who cannot attend the class in the DEN Studio, or
who must view a delayed-broadcast videotape or webcast, or are
frustrated by the telephone process: I consider your e-mail as a means
for classroom participation.
If you want
help …
My office hours, phone numbers, and e-mail address are listed at the
top of this syllabus.
I encourage you to e-mail me to discuss the course: topics might be
research problems, questions, ideas, and interesting readings.
rev. 2008.Aug.21
5 (of 10)
Syllabus (D. Howard)
Systems Architecting, 2008(3)
Evaluation & Grading
-
No MIDTERM or written FINAL examination will be given.
Your grade will be based on these projects:
 Short assignments will be due weekly (or sometimes biweekly), and will account
for half of your class grade.
 A major paper will be due at the end of the course, and will account for the other
half of your class grade.
Classroom participation (in person or via e-mail or telephone) and a
Class
participation positive engagement with the course are factors in your course grade, as
well; together they can move your letter grade up (or down!) by a plus or
a minus.
Short
assignments
Short assignments are intended to build skills for both the major paper
and the course itself. Research paper guidelines for the major paper are
given on the next few pages of this syllabus.
Major paper The class website has guidance on how to write your research papers.
The major paper will be graded on the letter scale: A, A-, B+, B, B-, etc. The set of short
assignments will be mapped to a letter grade as well.
I view graduate education as a two way street. This means that I expect students to teach
me as a part of the experience. As an incentive to do so I do not believe that a student has
earned an “A” in a graduate course of this nature unless they have taught me something
during the semester.
NOTE:
Employerrequired
documentation
rev. 2008.Aug.21
If your employer requires documentation for tuition re-imbursement
beyond that normally provided by the University and OASIS, then
please let me know as soon as possible — at least three weeks prior
to the last class session — so that I have enough time to check on the
arrangements with the Department. I will ask you to provide me with
any appropriate paperwork and a self-addressed, stamped-envelope (or
postcard) if necessary.
6 (of 10)
Syllabus (D. Howard)
Systems Architecting, 2008(3)
Projects
Short Assignments:
The specific assignments will be made available at least a week before
they are due.
For example: Describe and analyze the architecture of a selected system
in terms of any or all of the class concepts presented in Lecture XYZ.
Your analysis should provide a quantitative and qualitative evaluation of
the characteristics, benefits, and limitations of that system. Exploration
of heuristics relative to that system is strongly encouraged.
Length:
The length available for a weekly assignment is usually limited to two
pages, single-spaced, 10 point (in the normal profile orientation). We will
aim for one page, occasionally slightly less, and sometimes a bit more.
Major Paper:
I expect the major paper to be of sufficient quality that it could be
submitted to a refereed journal for publication. Journals like the
INCOSE Systems Engineering Journal or the IIE Transactions may
yield exemplars for your paper.
You may choose one of the following approaches:
 Describe and analyze the architecture of a selected system in
terms of any or all of the class concepts presented in lectures.
Your analysis should provide a quantitative and qualitative
evaluation of the characteristics, benefits, and limitations of that
system.
 Write a systems architecture research paper based on a minimum
of three papers that have been published in refereed journals.
Subject to my direction and approval, you get to choose the topic:
- It can be something that you have been personally involved in, or something that
interests you.
- It can be ongoing, a future system, or it can be past history.
Approval:
rev. 2008.Aug.21
For the MAJOR PAPER: You must submit an abstract regarding your
proposed topic for approval. Abstracts are typically a half page in
length. Abstracts are due no later than Lecture Session 6, and are
typically submitted to the DEN Blackboard system at the class website,
unless otherwise directed.
7 (of 10)
Syllabus (D. Howard)
Format:
Systems Architecting, 2008(3)
I prefer to have all written work submitted in Microsoft Word files,
unless you are directed otherwise.
If you refer to outside sources in written work, list all of your sources in
a reference list and contact list. It is essential. If you are uncertain
about how to do this, please contact me or the TA; we will gladly help.
Be sure to provide the URLs and dates of access for any Internet sources
used in your research.
The course materials provide some guidance on how to write a research
paper, with suggestions for format, organization, structure, and content
of good research papers.
Length:
Experience to date shows that the best size for the MAJOR PAPER is
somewhere around 10-to-15 pages, single-spaced, in 10 or 12-point
type.
NOTE: The point is the quality of thought in the paper, not its length
or volume and especially not in photos or graphics taken from other
sources. Take as long as it takes to tell the story clearly, present an
analysis in terms of the course concepts but keep the analysis tight, stay
organized and don't ramble. Very few papers of size less than 10 pages
have been worthy of an “A” grade in this class.
Submitting
assignments:
Short assignments, the abstract, and the major paper should be submitted
to the DEN Blackboard system (at the course website,
http://den.usc.edu), in Microsoft Word 2003 format unless you are
directed otherwise.
 The short assignments are due no later than the start of the following
class. (Expect any unexcused late submissions to be penalized, or
not to be accepted at all after two weeks.)
 The major paper is due no later than the start of the last class.
ADDITIONAL GUIDANCE:
-
Please feel free to e-mail me for help in structuring your research plan. I will gladly
work with you to identify sources, publications, Internet sites, and so on.
-
If English grammar, spelling and syntax are areas you need to work on, please
contact us for suggestions for improving your writing, or resources that might be
available to help. Your grade depends on the clarity of your expression.
rev. 2008.Aug.21
8 (of 10)
Syllabus (D. Howard)
Systems Architecting, 2008(3)
Other Considerations
Time
To learn systems architecting and to architect well, you need time to
think, time to “incubate” creative responses, time to strike up a
friendly partnership with your adaptive unconscious.
If you are in a situation where you do not feel that you have personal
time to reflect, consider making some adjustments, perhaps by
shedding some other tasks, so that you will have the time to “take a
walk” with this material at least once a week. It will likely make a
significant difference in your experience of this course.
Honor
We know that as students of systems architecting, you hold
yourselves to the highest standards of conduct and we, too, will
expect that from you.
We also expect you to abide by the expectations of the University; to
familiarize with those, please see the USC publication SCampus,
which can be found online.
rev. 2008.Aug.21
9 (of 10)
Syllabus (D. Howard)
Systems Architecting, 2008(3)
Class Schedule
(subject to change, as necessary, including all guest speaker arrangements)
6:30 pm – 9:10 pm, Tuesday
SAE 549, Systems Architecting
Wk
1
2008
26
Aug
2
2
Topic
Readings & Assignments Due
Introduction -- to the course, the instructors, and
systems architecting
Architect & architecting
pp. 1-5 & Ch 1 (Rechtin, 1991)
“Facing the Freshwater Crisis” (1hr)
Complex Time, stories 1-6 (0.5 hrs)
Sep
3
9
Boundaries & interfaces
Ch 2 (Rechtin, 1991)
Research Shortcuts, Part I (1hr)
Sep
4
16
Modeling, simulation, prototyping
Ch 3 (Rechtin, 1991)
APA Rules (2hr scan, at least)
Sep
Complex Time, stories 7-11 (0.5 hrs)
5
23
Strategic choices & the architect’s kit of tools
Ch 4 (Rechtin, 1991)
Research Shortcuts, Parts II, III (1hr)
Sep
“Scale-Free Networks” (1hr)
6
30
Sept
7
7
Building the system, manufacturing & production
Ch 6 (Rechtin, 1991)
(Guest) Dr. Stan Settles on mfg architecting
Research Shortcuts, Parts IV, V (1hr)
Abstract due prior to lecture
Systems test, acceptance, & operation
Ch 7 (Rechtin, 1991)
Complex Time, 17-23 (0.5 hrs)
Oct
8
14
Oct
9
21
Oct
10
28
Oct
11
4
Nov
12
11
Nov
13
18
Nov
14
25
Nov
15
2
(Guest) Dr. Gerald Nadler on systems & questions
TBA
Information systems
Ch 5 (Rechtin, 1991)
(Guest) Dr. Johnny Kwok on architecting
Tufte, “Sparklines” (2hrs)
(Guest) Dr. Behrokh Khoshnevis on creativity
Complex Time, 24-27 (0.5 hrs)
TBA
Economics and policy; organizational structure
Ch 12, 13 (Rechtin, 1991)
(Guest) Marilee Wheaton on economics
Tufte, “Corrupt techniques” (3hrs)
(Guest) Scott Jackson on resilience
Tufte, “Fundamental Principles”
(2hrs)
TBA
(Guest) Dr. Barry Boehm on software engineering
TBA
Architect’s profile; assessing architecting
Tufte, “Links & causal arrows”
(3hrs)
Ch 14, 15 (Rechtin, 1991)
(Guest) Dr. Elliot Axelband on systems of systems
An ethical framework
Main research paper due
Dec End of course
TBA: To Be Arranged.
rev. 2008.Aug.21
10 (of 10)