Final Draft Syllabus as of 20-01-2004 10:08:51 AM

Syst 302 - 001 -- Spring 2004

 

Subject to revision to correct errors and omissions and/or in the interest of fairness. GMU policies and procedures take precedence should there be a discrepancy between any of them and this syllabus.

 

Instructor

William Adams, PE, PhD

wadams1@gmu.edu

DO NOT SEND ANY ATTACHMENTS to any of my email addresses

Homework is not accepted by email

Other contact information will be given in class.

Office: TBD - best to see me before or after class

 

Teaching Assistant

TBD

 

Contact the TA for MATLAB questions.

Contact me for any course administration questions.

 

Schedule

Tues Thurs

Time: 12h00 - 13h15J **

Bldg.- Room -- IN - 137

(but see schedule of classes for recess, reading day, holiday closings, one time exceptions, snow cancellations, reschedulings and final exam. )

Check the GMU phone number for late breaking snow cancellation information.

 

(Click to see Planned Detailed schedule : Lecture and assignments.

Some generic assignment dates will be instantiated in class

 

The schedule shows the planned sequence and date. Weather delays and guest lectures may cause changes. If we are able to move faster, items may be done sooner and additional topics or review be done at the end of the semester.

 

Schedule Strategy

To follow the schedule below as closely as appropriate.

Selected parts of the textbook will be covered as noted.

Additional topics will be discussed where they most closely relate to the text sequence.

 

Communications

Students must ensure that their GMU email is active and working in order to receive announcements and other information broadcasts for this course.

 

Information may also be given in class.

 

Course Description

This course will extend and use the systems engineering and related skills normally developed through previous classes and as would be used in a business teamwork environment. Soft skills as well as technical ones will be exercised.

 

Analysis methods of systems engineering design and management are covered.

 

Lab exercises to be solved with software tools ( eg MATLAB) will be assigned.

 

Objective/Outcomes

Be exposed to a wide number of processes, tools, methods, approaches, and analysis methods. Use a number of them to develop skills in analysis.

 

Key items covered include:

        Analysis approaches

        Design

        Management

        Decisions

        Economic analysis - Life Cycle Cost

        Optimisation

        Probability and Statistics

        Queueing Theory

        Management Control

        Reliability and Maintenance

        Overview of Six Sigma Tools

        Transforms and Duals, morphisms

        Introduction to LP and Game Theory

        Teamwork - Team Project

 

Textbook and Reference Materials

Text: Blanchard & Fabrycky

Systems Engineering and Analysis 3E (selected sections)

 

 

Other Assistance

Research

For help with research, Kelly Jordan, Information Technology and Engineering Librarian, is a useful resource. Stop by the Fenwick library or email her at kjordan2@gmu.edu.

 

Writing

For help with writing, the GMU writing center may be useful. There are many web sites that provide writing and grammar assistance. Many universities have on line writing centers (OWL = online writing lab) for assistance. The GMU center is at

http://writingcenter.gmu.edu/owl/

 

Others are listed at

http://owl.english.purdue.edu/internet/owls/writing-labs.html

http://www.writerswrite.com/writinglinks/ucenters.htm

http://www.departments.dsu.edu/owl/labs_oth.html

http://owl.wsu.edu/otherowls.asp

http://writing.colostate.edu/links/index.cfm?category=owls

 

Group Writing - Recommended!

http://writing.colostate.edu/references/processes/group/index.cfm?guides_active=processes

 

Peer Review Writing Process

http://writing.colostate.edu/references/processes/peerreview/index.cfm?guides_active=processes

 

 

NOTE

Whilst grammar and style are important, quality content is the first priority. Do not get sidetracked with mechanics before the content has been instantiated. But allow time to create a quality document.

 

Course Requirements

A project will be handed out in class to be done by a team.

All students will be assigned to a team.

 

Additional lab problems will be handed out in class.

Most of these will be for individual effort.

There may be more than one team problem in total.

 

There will be a three short hour exams and a final exam.

Additional individual problems will be assigned and collected.

 

All students are required to grade and critique their teammates performance.

 

A lessons learned after action (AALL) report is required of all students to address what worked and what can be improved with the course.

 

There may be random unannounced quizzes. The probability of which is inversely proportional to class attendance. I.E. the more people missing the more likely a quiz will be given.

 

Homework will be collected each due date and at least one problem graded at random.

 

Grading Criteria

Grades will be per GMU policy.

 

Students will be required to turn in a self assessment as well as one for their team. Students will assess the other presentations.

 

Grades will be based on the following items - with the noted relative weighting factors.

 

        Final exam & AALL report - 30%

        Hourly exams - 20/3 each - NB exam scores can be increased some by a better score on the final

        Team Project - 25 Writing/content

        Individual team based grades may be adjusted up or down based on teammates recommendation andor instructor's observations

        Quizzes and special problems - 15

        Class participation Daily (textbook) assignments - 10

        Bonus points may be awarded for

exceptionally outstanding work

previously approved additional work

 

Some parts of exams may be take home, other parts done in class.

 

Late work

Late work is NOT accepted .

If you are late to class, your work is late too.

All assignments are due at the beginning of class and must be handed in.

No E-Mail submissions will be accepted.

 

Exceptions

If you anticipate any religious holidays, employer mandated travel, health appointments, or critical personal issues (tax audits, court appearances, funerals, weddings, etc.), that will require you to miss class or be late with work please notify the instructor as early as possible. And coordinate with your team so they are not impacted too. Confirming documentation is required.

 

Scale

A+ 98-100+

A 93-97

A- 90-92

B+ 87-89

B 83-86

B- 80-82

C+ 77-79

C 73-76

C- 70-72

Etc.

 

Grades are computed by Excel based on the scores earned for the items listed above.

 

Honor Code

Attention should be paid to the honor code provisions.

 

Exams and individual problems are to be done individually.

You may discuss individual problems but you must actually do the solution yourself. Specifics of exam solutions are not to be discussed.

 

All other work is open book, open notes, as would occur in an industrial environment. For academic purposes though, acknowledgement must be made of sources used including help from classmates.

 

Except for exams, all work is to be done collaboratively with their team, and/or the class. Teams may help each other but acknowledgement is to be given to such help.

 

Proper credit is to be given to any other information sources used by citing them in the Team Report.

 

Style and usage

Use the GPO or Chicago style manuals for citation format.

Use the Columbia guide for web based content citations.

Harbrace College Handbook or Hacker are good guides for grammar usage.

The Chicago Manual of Style 13E (or later)

Chicago

U of Chicago 1982

 

Style Manual rev.

US GPO

Washington

GPO 1973 (or later)

http://www.gpoaccess.gov/stylemanual/browse.html

 

Rules for Writer 3E (or later)

Diana Hacker

Boston

St Martin's Press 1991

 

The Columbia Guide to Online Style by Janice R. Walker and Todd Taylor (Columbia UP, 1998)

http://www.columbia.edu/cu/cup/cgos/idx_basic.html

 

Class Policies and Approach

All applicable laws and GMU policies are hereby included by reference.

Students are responsible for knowing the school policies as documented in the Catalog.

 

Smoking is not allowed in the classroom.

 

All notes should be annotated with a timestamp and the source. Acknowledgement of all sources is expected if material from a textbook, website, inter-team collaboration, or class discussions is used.

 

Students are expected to

        attend all sessions on time.

        Turn in assignments at the beginning of class

        be prepared

        participate actively

        be alert, having had adequate sleep and rest

        manage their time effectively

   plan their work and budget their time

   keep a log of all resources expended - this will not be collected for syst302 unlike syst371 where it is mandatory

   do not get behind

        coordinate and work with their team effectively and collegially

        first attempt to do all the work by themselves

   ask for help when necessary

 

You may synchronise your watches by telephone at 202 762 1401.

 

Teamwork is an integral factor of this course. All students are expected to work in a collaborative and cooperative manner both on their project team and in the class as a whole. Planning and coordination are expected to minimise duplication of efforts.

 

Communication is vital to success and will be emphasised through in‑class briefings concerning the team projects and written status reports.

 

Accommodations

Any student needing accommodation for a handicap will be given whatever course modifications they need as determined appropriate by the DRC staff. The DRC form is required.

 

Project/Assignments

Specific assignments will be given in class relating to the text book problems

 

Additional items will be assigned in class for individual solution.

The team project problem(s) will be handed out in class.

 

Exams may include a take home component.

 

Formats

Please provide hardcopy of all assignments. Softcopy is also required for the final report and presentation. MS Project files need to be in MSP-98 format not 2000 or XP. Other files should be readable by Office-97 versions of word, excel, access, powerpoint, etc.

 

Please use a font that is 12-14 points, with 2-3 points of leading for text.

Do not justify.

 

Use 1.5" left margin and all other margins set at 1".

If headers/footers are used and/or page numbers, then they should be spaced 1/2" from the text body.

 

Do not use Garamond or (new) times roman or similar fonts with small x‑height or tight tracking.

 

Please use American Typewriter aka Editor, or Dark Courier. Other large x-height fonts with uniform stroke weight may be used; but, please confirm readability with the professor first. Georgia, Trebuchet, Antiqua are other MS fonts that may be used.

 

Fonts can be provided to those who do not have them and are unable to download them from Microsoft, HP, or public domain sites.

 

Spreadsheets and similar items should use Arial Narrow 8-10 point.

 

---------

notes:

 

** J = local time. We change from EST to DST in April.

 

 

 

==========================================

Return to course requirements

Project Description - Detailed course Requirements

 

Syst 302 - Project - Spring 2004

 

Due by 12h00 15 April 2004

 

The team project problem(s) will be given out in class.