SAE 549: Systems Architecting (McKendree)
Fall 2009
SYLLABUS (UPDATE 4)
1 (of 13)
Class Sessions:
Day:
Time:
Room:
Class Number:
Tuesday (evening)
6:40 pm – 9:20 pm
RTH 105 (Webcasted Course)
32319D (DEN) and 32349D (on campus)
Contact Information:
Instructor:
Office hours:
Office location:
Phone:
E-mail:
Tom McKendree
Tuesday, 5:00 pm – 6:00 pm, or by appointment
Seaver Science Center (SSC) Room 101 [Phone: 213-740-0867]
(714) 446-4283
tmckendree@raytheon.com
TA:
Office hours:
Office location:
e-mail:
Yvette Torres
Tuesday, 4:00 – 6:00 pm, or by appointment
Via phone (323-428-7216)
ytorres@usc.edu, Please contact by e-mail for appointment
Course website
http://den.usc.edu is the URL of the DEN website
Course 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.

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.

To lay the basis for students to expand and grow in systems architecting and engineering
understanding, skills and capabilities after the class
Readings:
REQUIRED:
First Reader for SAE549: Rechtin, E. (1991). Systems architecting:
Creating and building complex systems. Englewood Cliffs, NJ: Prentice
Hall. ISBN: 0-13-880345-5
The course reader is a reprint of this book, which is otherwise currently
out of print. The first course reader is a reprint of this book, which is
otherwise currently out of print. (Both readers should be listed as
“McKendree”) It is not immediately available from the bookstore. You
will be notified when it is available.
28 September 2009
SAE 549: Systems Architecting (McKendree)
Fall 2009
SYLLABUS (UPDATE 4)
2nd Text:
3rd Text:
2 (of 13)
DoD Architecture Framework version 2.0 (also posted on DEN site)
Volume 1: Introduction, Overview, and Concepts: Manager’s Guide,
28 May 2009
Volume 2: Architectural Data and Models: Architect’s Guide, 28
May 2009
http://lists.oasis-open.org/archives/soa-rmra/200907/msg00011.html
Second Reader for SAE549: McKendree. Systems Architecting: Selected
Readings. It is not immediately available from the bookstore. You will be
notified when it is available.
A collection of chapters and articles selected by Dr. McKendree.
4th Text:
Kesselman-Turkel, J., & Peterson, F. (2003). Research shortcuts
(revised). The University of Wisconsin Press.
5th Text:
Selected readings posted on DEN site or referenced on the web
Select Either Group A or Group B
Group A
Text: [Preferred] Maier, M. W., &
Rechtin, E. (2009). The art of
systems architecting (3rd ed.). Boca
Raton, FL: CRC Press. ISBN-13:
978-1-4200-7913-5
-or[Permitted] Maier, M. W., &
Rechtin, E. (2002). The art of
systems architecting (2nd ed.). Boca
Raton, FL: CRC Press.
ISBN: 0-8493-0440-7
th
5 Text: Tufte, E. R. (2006). The cognitive
style of powerpoint, 2nd ed. Graphics
Press.
ISBN: 0-9613-9216-9
4th
4th
Group B
Text: Senge, P. M. (2006) The fifth
discipline (revised ed.). Currency
ISBN: 0-3855-1725-4
5th Text: Tufte, E. R. (2006). Beautiful
evidence. Graphics Press.
(contains The cognitive style of
powerpoint as a chapter)
ISBN: 0-9613-9217-7
SUGGESTED (Not Required):
Texts from Group not selected (excluding The Cognitive Style of
PowerPoint for students who choose Group B)
Brynteson, R. (2006). Once upon a complex time: using stories to
understand systems. Sparrow Media Group. ISBN: 0-9719-3048-1
Rossiter, J. and K. Dailey (Ed.) (2007), The APA Pocket Handbook: Rules
for Format & Documentation, DW Publishing Co.
ISBN-10: 1-9338-7813-4; ISBN-13: 99 978-1933878133
Notes:
28 September 2009
Weekly class notes/charts will be provided. They will be posted on the
Course website (see above).
SAE 549: Systems Architecting (McKendree)
Fall 2009
SYLLABUS (UPDATE 4)
3 (of 13)
Advice on Readings:
The course is structured around (Rechin 1991). The DoD Architecture Framework (DoDAF) is
available from the DEN site and it provides a structure for describing and decomposing complex
architectures. Since it is a mandated standard for all DoD acquisitions and has been used by both
NASA and NOAA, there are many architectures that use the DoD architecture framework and
provides the system architect with many integration opportunities. In the Fall 2009 semester I
will assess the interest of students in the beginning of the semester in DoDAF, and revise
assignments and reading to align with the interests of the semester’s students.
(Maier and Rechtin 2009) is an update of (Maier and Rechtin 2002) that has more recent
examples from information systems, and thoughts that have led to recent tool developments.
Some students have disliked (Maier and Rechtin 2002), however, because it is expensive and
repeats the heuristics from (Rechin 1991). (Maier and Rechtin 2009) is not an updated edition of
(Rechtin 1991). The major change from the second edition (Maier and Rechtin 2002) is the
addition of 5 case studies. (Rechin 1991) and (Maier and Rechtin 2009) are separate books, and
students who select Group A need both. Due to the error of the Bookstore stocking (Maier and
Rechtin 2002) rather than (Maier and Rechtin 2009), either will be accepted for this semester,
but students are urged to get the third edition (Maier and Rechtin 2009) if they have a choice.
Since (Maier and Rechtin 2002) is acceptable, all of the Case Studies are “Recommended,” not
“Required,” but they are still quite valuable.
In Group B (Senge 2006) is a classic introduction to the field of “systems thinking,” and very
popular with students. The systems it uses as examples are organizations, the environments they
face, and people in those organizations. This course focuses more on physical systems situated
in environments, so some translation is necessary to fully exploit (Senge 2006). Beautiful
Evidence is a lovely book, with a lot of content that would be useful for the advanced systems
architect. It includes useful advice in thinking about diagrams. Being able to develop better
diagrams will help with the course, and is a key skill for systems architecting. In Beautiful
Evidence the chapter “The Cognitive Style of PowerPoint” follows a build-up over several
chapters. The pamphlet suffers in isolation, with arguments against PowerPoint but not all the
background. Students who feel comfortable with the basic Systems Architecting content in this
class are strongly encouraged to read Beautiful Evidence, during or after the course.
(Rechtin 1991) is out of print. You may purchase an expensive, used copy on-line. The USC
Bookstore offers a reprint. This reprint is considered a “Course Reader” rather than a “book,”
and thus is listed under “McKendree,” and not under “Rechtin.” The Readers were not available
from the Bookstore until 1 September. This syllabus is adjusted to reflect the necessary changed
reading schedule.
This course require Research Shortcuts because half the base grade depends on a major research
paper, and many students could improve their grade with better skills in research or in research
logistics. Many of the homework assignments will also draw on these skills. It is short, and can
be read quickly. You may want to skim it quickly early in the semester, and then look up key
chapters. The course schedule includes a suggested reading sequence for students who wish a
structured reading plan, but that is just a suggestion; there is no need to follow that exact
28 September 2009
SAE 549: Systems Architecting (McKendree)
Fall 2009
SYLLABUS (UPDATE 4)
4 (of 13)
sequence and it is easy to read the whole book much sooner.
There are several specific comments to Research Shortcuts. When you consider course time
requirements in chapter 4, remember that this is a 3 unit, graduate level course, and thus you
should expect to spend a minimum of 9 hours a week on the course beyond the class lecture.
“Modern aids to research” (chapter 21) include the internet, but you should not limit yourself to
what you can easily find on the internet, or with public search engines. Most assignments will
require that you have formal references. Remote DEN students may make remote use of USC
libraries and USC library research tools—consider that when identifying “the Right Library”
(chapter 15). The “rule of three” in chapter 23 is an effective rhetorical device, but be warned, it
can be a misleading heuristic when doing research for the purpose of determining the truth about
something.
There may be couple points in the schedule when I recommend reading “As much of
[something] as you can reasonably read.” The point of this advice is to suggest particular items
to read ahead of time, which will generally help avoid major reading crunches later in the
semester. Beyond this specific advice, it is always a good idea to read ahead when you have the
time to do so.
The book Once Upon a Complex Time is a short introduction to systems thinking. The examples
are almost exclusively from biological, organizational and social systems, but should be useful
for students who have difficulty grasping the relevance of non-technical issues to systems
architecting.
The APA Pocket Handbook provides one acceptable standard for formatting your paper,
including citation and reference styles. If you are at all unsure about these questions this is a
good source.
GRADE:
Your grade will be primarily based on a set of RESEARCH PAPERS. Small papers will be due
as homeworks, and will account for fifty percent of your class grade. The primary paper
will be due at the end of the course, and will account for fifty percent of your class grade.
No written MIDTERM or FINAL examination will be given in this course.
Homework is intended to build skills for both the major paper and the course itself. Guidelines
for the research paper are given on this syllabus following the discussion of class participation.
The web site will have suggested guidance for your research paper, including previous student
examples.
MULTIPLE SECTIONS:
This course is being taught concurrently with the Spring 2009 section of SAE 549 taught by
Charles Tang. The class meetings and main lectures are identical, and the general format the
28 September 2009
SAE 549: Systems Architecting (McKendree)
Fall 2009
SYLLABUS (UPDATE 4)
5 (of 13)
same, but the readings and homework can vary between sections, and each instructor will
independently grade his or her own students. Since the homeworks may vary between
instructors, assignments may not be presented during the common class lectures. Homework
assignments may be presented when the assignment is common, but the lack of a homework
assignment presented in class should not be taken to mean that no homework was assigned.
Always check the DEN Blackboard in the Assignments area.
CLASSROOM ATTENDANCE AND PARTICIPATION:
-
As this is a webcasted course, 100% attendance in the classroom is not mandatory.
However, I strongly encourage you to ask questions and participate in discussions regarding
the lectures. Live discussions will engage students from all three sections. If you are
attending the class from a remote site, there will be facilities for interactive voice
communications with the classroom. These have sometimes had technical difficulties. In
addition, many students have effectively used the chat feature of webex during class
presentations. Your classroom participation is an important factor in your final grade.
-
E-MAIL and USE THE DISCUSSION FORUMS ON DEN!!! I strongly encourage your
use of e-mail for questions, comments, etc., and the DEN discussion forum for questions,
discussion and clarification with other students, etc. Of course, if you prefer face-to-face
interaction or telephone conversations — well, that's equally acceptable! For remote
students that cannot attend the class in the DEN Studio, or must view a delayed-broadcast
videotape or webcast, or are frustrated by the telephone process: I consider your e-mail, and
discussion Forum as equivalent classroom participation!
-
WHAT IF YOU MUST MISS A CLASS BECAUSE OF WORK OR TRAVEL??? Use
Blackboard or e-mail 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. You are responsible for the material that was covered.
SPECIAL DEN CLASS PARTICIPATION:
-
The DEN implementation for this class may not make feasible direct class participation by
some DEN students. Therefore, DEN students may submit up to four “Special DEN Class
Participations” worth up to 1/4 of total class participation each. Only ideal class
participations will earn their full class participation potential. Students may not submit more
than one Special DEN Participation before any one class session.
-
Special DEN Class Participation should contribute to the benefits of class participation by
making the student understand and present their position, and by helping other students
better understand Systems Architecting.
-
A Participation should typically be 1-3 original pages of text. A Participation in PowerPoint
should typically be 1-6 charts. Reference Contribution Participations may be significantly
longer. Before submitting a PowerPoint Participation, students must read “The Cognitive
28 September 2009
SAE 549: Systems Architecting (McKendree)
Fall 2009
SYLLABUS (UPDATE 4)
6 (of 13)
Style of PowerPoint” (pamphlet, or Beautiful Evidence chapter). The Participation must be
emailed directly to the Professor in a format readable on a Windows PC by Microsoft
Powerpoint 2003, Microsoft Word 2003, or Adobe Reader 6.0, unless another format is
coordinated with the instructor. Please include your name on all pages. Each may be either
a “Summary Participation” or a “Contribution Participation.”
-
Summary Participation: A short document original to the student that summarizes the key
lesson(s) of a class reading, textbook chapter, or textbook chapter section. Readings from
Research Shortcuts are not allowed without prior coordination with the instructor. All other
readings, including “recommended” readings and articles provided via web URL or on
DEN, are acceptable. Each summary should include at least one ORIGINAL diagram or
graphic conveying the key point(s). The Summary must be emailed directly to the Professor
and arrive before the Sunday before the class meeting on the summarized material. The
ideal Summary will distill the key idea(s) of a reading, chapter or section into the minimum
possible number of original diagrams, and would be good enough to be used by the
Professor to discuss the reading or chapter.
-
Contribution Participation: A document that amplifies, illustrates, expands upon, or
challenges the material presented in a lecture. A Contribution Participation must be emailed
directly to the Professor, and arrive by noon on the Sunday following the class meeting on
the addressed material.
-
A Contribution Participation can be a “Reference Contribution,” a work that is not original
to the student, such as an internal company document on Systems Architecting. The student
must make certain that they have permission to provide any such contribution. A Reference
Contribution is the most likely reason for the instructor to accept another format. Reference
Contributions will only be accepted at the instructor’s discretion, generally for references
that are not already publicly available.
-
More commonly expected is an Original Contribution Participation, an original work
generated by the student. The ideal Original Contribution will provide cogent exposition,
supported by cited evidence, which increases the instructor’s understanding of Systems
Architecting, and would be good enough to be used by the instructor as a class reading.
-
I encourage you to look at the DEN Class Participations provided by other students, which
will be placed on the course website at http://den.usc.edu. Some homeworks may reference
some or all of the participations. Many students in previous classes have said that they
found helpful the DEN Class Participations of other students.
IF YOU WANT HELP:
-
My office hours, phone numbers, and e-mail address are listed at the top of this syllabus.
Please include the Teaching Assistant Yvette Torres on distribution for any emails to
me: ytorres@usc.edu
28 September 2009
SAE 549: Systems Architecting (McKendree)
Fall 2009
SYLLABUS (UPDATE 4)
-
7 (of 13)
I encourage you to e-mail me at any time to discuss research problems, questions, etc. At
some times I will respond very quickly. At some times, I may not respond for many days.
It is not now clear which times will be which, so if you have not received a response within
a few days, please ask again.
RESEARCH PAPER GUIDELINES
WEEKLY HOMEWORKS:
The specific papers will typically be assigned a week before they are due. They
will be posted in the “Assignments” area on DEN. 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 paper will be specified, and is generally limited
to two pages, single-spaced, 10 point (in the normal profile orientation). Students
may always request a waiver if they feel they must go longer.
MAJOR PAPER:
I expect the major paper to be of sufficient quality that it could be submitted
to a refereed journal for publication consideration. The INCOSE Systems
Engineering Journal or the IIE Transactions provide journalistic styles for
your paper.
One of the following:
 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, how those were
driven by the architecture, and ideally (where available) how the
architecting process led to the architecture that had those results.
 Write a systems architecture research paper based on a minimum of
three papers that have been published in refereed journals.
Subject to my 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: For the MAJOR PAPER: You must submit a one-page proposal regarding your
proposed topic for approval which is due on 29 September 2009.
28 September 2009
SAE 549: Systems Architecting (McKendree)
Fall 2009
SYLLABUS (UPDATE 4)
8 (of 13)
PLAN UPDATE:
For the MAJOR PAPER: You must submit a one-page paper plan update
regarding your plan for completing the paper, including any refinements or
redirections in your planned topic or approach. Append to this plan drafts of all
figures you intend to use (no page limit). This update is due on 27 October
2009.
FORMAT:
Typed. A bibliography and contact list is essential, listing what sources you
used. Be sure to provide the URLs and dates of any Internet sources used in
your research. Be sure to include all necessary citations in the body of your
text. Use clear style for citations and references. The APA Pocket Handbook
provides one acceptable style.
The class website will provide guidelines 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: I do not grade papers by their weight! 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. The point is not
size, rather amount of analytical content.
ADDITIONAL INFORMATION:
-
Course policies and procedures for items like submitting homework (via DEN for all
students) and adequate references are available on the DEN website (Current draft’s filename
is SAE549(F09McK) - ytorres - Policies&Procedures v01.doc). Students are
responsible for understanding and following these policies and procedures. Any changes
will be announced.
-
Please feel free to e-mail me or the TA for help in structuring your research plan. I will
gladly work with you to identify sources, publications, Internet sites, etc.
-
There have been previous attempts of students to copy someone else’s text into their papers
or homework. Never copy text in to your file without marking it with a citation. Never
attempt to copy text into your file and then “edit it into your own word.” All the text that
you turn in that comes from somewhere else must be marked as quotation. All the ideas that
you turn in that come from someone else must be cited. The default punishment for
plagerism by a graduate student is failing the course, and expulsion is possible.
-
If English grammar, spelling and syntax are not your strong points, I strongly suggest that
you obtain help in editing your text. Your grade depends on the clarity of presentation. The
Engineering School has a writing assistance program, but you must engage early to use it.
28 September 2009
SAE 549: Systems Architecting (McKendree)
Fall 2009
SYLLABUS (UPDATE 4)
9 (of 13)
DELIVERY:
The homework, the research paper proposal, and the main research paper
should be submitted to the DEN Blackboard system (at the Course website,
http://den.usc.edu).
GRADING:
Each research paper will be graded on the letter scale: A, A-, B+, B, B-, etc.
Your classroom participation (in person, by telephone, via e-mail or discussion
board) is one factor in this grade, and can move your letter grade up (or down!)
by a plus or a minus. Note, this means that if you have negligible class
participation, this will lower your grade by one step. 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.
Your final paper grade will require writing a paper that would be instructive or
of general interest to systems architects, even ones with no interest in the
particular system you analyze.
Note: if your employer requires a written statement (or a signed postcard) for
reimbursement for this class, then please provide me with the appropriate
paperwork and a self-addressed, stamped-envelope (or postcard) before the end
of the semester.
UNIVERSITY LEVEL ISSUES
STATEMENT FOR STUDENTS WITH DISABILITIES:
Any student requesting academic accommodations based on a disability is required to register
with Disability Services and Programs (DSP) each semester. A letter of verification for approved
accommodations can be obtained from DSP. Please be sure the letter is delivered to me (or to
TA) as early in the semester as possible. DSP is located in STU 301 and is open 8:30 a.m.–5:00
p.m., Monday through Friday. The phone number for DSP is (213) 740-0776.
STATEMENT ON ACADEMIC INTEGRITY:
USC seeks to maintain an optimal learning environment. General principles of academic honesty
include the concept of respect for the intellectual property of others, the expectation that
individual work will be submitted unless otherwise allowed by an instructor, and the obligations
both to protect one’s own academic work from misuse by others as well as to avoid using
another’s work as one’s own. All students are expected to understand and abide by these
principles. Scampus, the Student Guidebook, contains the Student Conduct Code in Section
11.00, while the recommended sanctions are located in Appendix A:
28 September 2009
SAE 549: Systems Architecting (McKendree)
Fall 2009
SYLLABUS (UPDATE 4)
10 (of 13)
http://www.usc.edu/dept/publications/SCAMPUS/gov/. Students will be referred to the Office of
Student Judicial Affairs and Community Standards for further review, should there be any
suspicion of academic dishonesty. The Review process can be found at:
http://www.usc.edu/student-affairs/SJACS/.
28 September 2009
SAE 549: Systems Architecting (McKendree)
Fall 2009
SYLLABUS (UPDATE 4)
11 (of 13)
Schedule of Class Sessions: The exact schedule is very likely to change, based on availability of
guest lecturers. Dates of readings may change to align with other schedule adjustments.
Changes will be announced. “*” Indicates a suggested Reader reading that is required in a later
week, now that the readers are available.
2009
Session number:
Planned topic
Readings & Reminders (In addition, supplementary papers and notes will be
available from the DEN website)
All Students
Group A
Group B
25 Aug 1: Introductions–to
the course, the
instructors, and
systems
architecting
1 Sep 2: The architect &
architecting
Eberhardt Rechtin, Electrical
Engineer, an oral history
conducted in 1995 by Frederik
Nebeker, IEEE History Center,
Rutgers University, New
Brunswick, NJ, USA. (filename:
Rechtin_IEEE_interview_241
.pdf) pp. 29-72
“Preface,” “Part I,” & Ch 1, 2 of (Senge
Ch 1 of (Maier and
2006)
Rechtin, 2002/2009)
Suggested:
Introduction to (Senge
2006); Beautiful
Evidence: Introduction
Recommended: *“Preface,” Ch 1
of (Rechtin, 1991)
*McKendree, T., (1992) “The Role
of the Systems Architect, and How
it Relates to Systems Engineering”
from the second reader
Research Shortcuts All, or Ch. 1,
2, 36.
Rechtin oral history pp. 1-29
8 Sep 3: Boundaries &
interfaces
“The Role and Task of the System
Architect,” Gerrit Muller
(http://www.gaudisite.nl/R
oleSystemArchitectPaper.pd
f)
“Module System Architect
Toolkit,” Gerrit Muller
(http://www.gaudisite.nl/M
oduleSystemArchitectToolki
tPaper.pdf)
Recommended: *Ch 2 of (Rechtin,
1991)
*Raymond, Arthur E., (1951) “The
Well Tempered Aircraft” from the
second reader.
Research Shortcuts Ch. 3, 4, 10, 21
28 September 2009
Ch 2 of (Maier and
Rechtin, 2002/2009)
Recommended: Case
Study 1 of (Maier and
Rechtin, 2009)
Ch 3 of (Senge 2006)
Suggested: Beautiful
Evidence: Mapped
Pictures (pp. 12-27)
SAE 549: Systems Architecting (McKendree)
Fall 2009
SYLLABUS (UPDATE 4)
2009
Session number:
Planned topic
Readings & Reminders (In addition, supplementary papers and notes will be
available from the DEN website)
All Students
15 Sep 4: Modeling,
simulation,
prototyping
12 (of 13)
Ch “Preface,” Ch 2, 3 of (Rechtin,
1991)
Recommended: Research Shortcuts
Ch. 5, 6, 15
Group A
Group B
Both “Part III” and Ch Ch 4 of (Senge 2006)
8 of (Maier and
Suggested: Beautiful
Rechtin, 2002/2009)
Evidence: Mapped
Pictures (pp. 28-45)
Suggested: Ch 1-6 of (Brynteson,
2006)
Ch 1, 4 of (Rechtin, 1991)
22 Sep 5: The architect’s
kit of tools and
Raymond, Arthur E., (1951) “The
Strategic choices Well Tempered Aircraft” from the
second reader.
Recommended: Research Shortcuts
Ch. 7, 11, 16.
Suggested: Ch 6, 8 of (Rechtin,
1991)
29 Sep 6: Information
Systems (Ken
Cureton guest
lecture)
Ch 5 of (Rechtin, 1991)
Recommended: Research Shortcuts
Ch. 8, 12, 17, 22
Ch 9 of (Maier and
Rechtin, 2002/2009)
Ch 5 of (Senge 2006)
Beautiful Evidence:
“Chapter 5 A Shift in Linked and Causal
Mind” from the second Arrows
reader
Recommended: Case
Study 4 of (Maier and
Rechtin, 2009)
“Part II” and Ch 6 of
(Maier and Rechtin,
2002/2009)
Ch 6 of (Senge 2006)
Ch 4 of (Maier and
Rechtin, 2002/2009)
Ch 7 of (Senge 2006)
Beautiful Evidence:
Sparklines
Research Paper Proposal due
6 Oct 7: Building the
system,
manufacturing &
production (Stan
Settles guest
lecture)
13 Oct 8: Systems test,
acceptance, &
operation
Ch 6, 8 of (Rechtin, 1991)
Recommended: DoDAF 1.5 vol 1
pp 1-1 to 1-9
Research Shortcuts Ch. 14, 19, 20,
28.
Ch 7 of (Rechtin, 1991)
Recommended: Case
Study 2 of (Maier and
Rechtin, 2009)
Ch 3 of (Maier and
Rechtin, 2002/2009)
Ch 8 of (Senge 2006)
Recommended: Research Shortcuts
Ch. 23, 24, 25, 29.
Ch 7 of (Maier and
Rechtin, 2002/2009)
Ch 9 of (Senge 2006)
Look at the images and discoveries
at http://www.spitzer.caltech.edu/
Recommended: Case
Study 5 of (Maier and
Rechtin, 2009)
M Kendree, T., (1992) “The Role
of the Systems Architect, and How
it Relates to Systems Engineering”
from the second reader
c
Beautiful Evidence:
Words, Numbers,
Images - Together (pp
82-109)
Recommended: Research Shortcuts
Ch. 9, 13, 18, 27.
20 Oct 9: Space Mission
Architecture and
the SIRTF Story
(Johnny Kwok
guest lecture)
28 September 2009
Beautiful Evidence:
Words, Numbers,
Images - Together (pp
109-121)
SAE 549: Systems Architecting (McKendree)
Fall 2009
SYLLABUS (UPDATE 4)
2009
Session number:
Planned topic
Readings & Reminders (In addition, supplementary papers and notes will be
available from the DEN website)
All Students
27 Oct 10: Technological
Creativity &
Invention
(Behrohk
Khoshnevis guest
lecture)
13 (of 13)
Ch 9 of (Rechtin, 1991)
“Military Innovation in Peacetime”
from the second reader
Recommended: Research Shortcuts
Ch. 26, 30, 31.
Group A
Group B
Ch 5 of (Maier and
Rechtin, 2002/2009)
Ch 10 of (Senge 2006)
Suggested: Ch 12 of
(Maier and Rechtin,
2009)
Beautiful Evidence:
The Fundamental
Principles of Analytic
Design
Research Paper Plan Update due
Ch 12, 13 of (Rechtin, 1991),
3 Nov 11: Economics
policy & political Recommended: Research Shortcuts
process
Ch. 32, 33.
Ch 13 of (Maier and
Rechtin, 2009) or Ch
12 of (Maier and
Rechtin, 2002)
Ch 11 of (Senge 2006)
Beautiful Evidence:
Corruption in
Evidence Presentations
Recommended: Case
Study 3 of (Maier and
Rechtin, 2009)
10 Nov 12: Guest Lecture
Opportunity
Recommended: Research Shortcuts
Ch. 34, 35.
“The Cognitive Style
of PowerPoint”
pamphlet
Suggested: Ch 11 of (Rechtin,
1991)
Ch 12 of (Maier and
Rechtin, 2009)
Ch 10 of (Rechtin, 1991),
Beautiful Evidence:
The Cognitive Style of
PowerPoint
Suggested: Part IV
Introduction, Ch 12 of
Recommended: Ch 10 (Senge 2006)
of (Maier and Rechtin,
2002/2009)
Ch 14, 15 of (Rechtin, 1991)
17 Nov 13: Architect’s
profile; assessing Recommended: Research Shortcuts
architecting
Ch. 37.
Ch 11 of (Maier and
Rechtin, 2002/2009)
Suggested: Ch 13, 14
of (Senge 2006)
24 Nov 14: Guest Lecture
Opportunity
“Part IV” of (Maier
and Rechtin, 2009)
Recommended: Ch 15
of (Senge 2006)
Recommended: Ch 16 of (Rechtin,
1991), Research Shortcuts Ch. 38.
Recommended: Ch 14
of (Maier and Rechtin,
2009) or Ch 13 of
(Maier and Rechtin,
2002)
1 Dec 15: Guest Lecture
Opportunity
28 September 2009
Main research paper due