Enterprise Engineering

1
Enterprise Engineering
Larry Whitman whitman_at_imfge.twsu.edu (316)
691-5907 (316) fax
Industrial Manufacturing Enterprise
Department The Wichita State University http//www
.mrc.twsu.edu/enteng
2
IE880I - Topics

• Overview of Enterprise Engineering (3 weeks)
• Basic overview of what is enterprise engineering
  and its benefits. Students will learn the
  advantages of EntEng and associated terminology
  and philosophy.
• IE880I - Exam 1 - February 19, 1999.
• Test will be closed book/notes - fill in the
  blank/essay format.
• One hour long, then we continue Enterprise
  Models.
• We will have class Feb 26, 1999
• Dr. Malzahn will be guest speaker on Activity
  Based Costing
• Then 330-430 Dorothy Moore at the Ablah Library
  will review research capabilities at the library
  in room 217
• Extra Credit Option
• One-Two page summaries of five articles
• Worth 10 points on any exam (You made a 90 on an
  exam, you do the five articles and I like your
  summaries, you get credited for a 100 on the
  exam.)
• Only for ONE exam (you can do it for the final if
  you want!)

3
Paper

• Select Topic
• Turn in by April x, 1999
• If you have a draft (or outline) I will talk to
  you, if we have talked before, bring in the
  previous mark up.
• Requirements - at least two papers I have not
  seen and turn in copies of those papers.
• Save on IE880I directory and give paper copy.
• Register topic on the website.
• Use the writing lab prior to talking with me.

4
Opportunities for Improvement

• Writing Center - LAS Building 6th Floor 601
• Talk with a student assistant about drafts of
  your paper.
• Also use computer assistance to develop skills
• Free
• Conversation Class for non-native speakers
• Informal practice group to gain confidence in
  speaking
• Thursdays 130-220pm (you can start any week)
• Learning Resource Center Grace Wilkie East
• Free

5
IDEF0 (Boxes and Arrows)

• Boxes
• Activities
• Named with Verbs or Verb Phrases
• No fewer than three and no more than six per
  diagram
• Dominance not precedence
• Arrows
• Represent things
• Connect boxes together
• Branches
• not explicitly labeled assumed to contain all
  things on label before branch
• Joins

6
IDEF0 (Diagrams)

• Named with Title
• Author
• Project
• Date
• Status
• C-Numbers
• xxx put kit cover page on here

7
IDEF0 (continued)

• Bound the top level box (system)
• Top Level (Context Diagram)
• Node numbers
• C Numbers
• ICOMs (Plug and Play)

8
Arrow (special details)

• Decomposable
• Tunnel
• parenthetical
• control appearance of details (reduce complexity)
• Input vs Control
• Mechanisms (how it happens)
• Control and Dataflow feedback

9
Diagrams

• Natural language
• Purpose
• Viewpoint (emphasis)
• Law of Seven

10
Decomposition

• Strategies
• Based on functional relatedness (what vs how)
• By roles
• Subsystem (less desirable)
• Life Cycle
• By Physical Process (least desirable)
• Which one?
• Varied
• When to stop?
• Desired precision

11
Domain Knowledge Capture

• Sources
• Reading Documents
• Observing Existing Operations
• Surveying with a Questionnaire
• Using your own knowledge (Aaaahhhh!)
• Inventing a Description (get it corrected)

12
Interview Process

• Preparation
• Conducting the Interview
• define purpose
• do not contradict
• ask open ended questions
• can you give me an example?
• how long ago did this happen?
• are there any special cases?
• what is the source?
• are there numbers for that?
• take notes
• follow-up

13
More interviewing tips

• Determine if it is fact or opinion (ask
  qualifying questions)
• Always ask for numbers and units
• Always ask for sources and destinations of data
  (format, use)
• Silence can be good!
• Dont lead
• Dont become a stenographer

14
Lets start a model!!!

• Determine purpose and viewpoint
• Generate data list
• Generate activity list
• Draw A0
• lay out boxes
• draw primary constraint arrows
• draw external arrows
• draw remaining arrows
• Summarize (A-0)

15
Continuing the Model (Decompose)

• Pick a box
• Consider the subject
• create new diagram
• criticize the new diagram
• try alternate decompositions
• revise the new diagram
• revise all related diagrams

16
Review (questions)

• Question the boxes
• Question the connections
• Question internal arrows
• Split differently
• Bundle differently
• Test it
• Sketch next level decomps (very helpful)
• Reevaluate dominance
• position arrows (minimize crossing)
• good box name (not elaborate)
• Explanations (text)

17
Author/Reader Cycle
18
Kit Preparation
Kits with Reactions
Author
Readers
Kits with Comments
19
Kit Cover Page
20
Kit Organization (important slide)

• Contents
• Cover page
• diagrams
• text
• diagram
• text
• glossary
• Kit size - diagram and decomp of one box (6 max)
• To kit or not to kit (enough new info?)

21
Reading

• look at single diagram
• read title and node number
• read each box
• read internal arrows
• read author notes
• read associated text
• look at context
• read parent box and its arrows
• read ICOMs
• read how it connects to parents
• read supporting material

22
Reading (continued)

• focus on how diagram fits into model
• criticize
• question syntax
• question your understanding of message
• agree with authors message

23
Commenting

• USE RED!!!!
• Record work times
• check frame contents
• simple agreement disagreement marks (tell that it
  was read)
• tick marks and circles
• use reference language
• reread the kit
• not just nothing wrong (but is everything there?)

24
Reacting to Comments

• In BLUE
• First quick read all comments
• Check reader times
• respond to each comment
• author/reader talk
• consolidating reader comments
• redraw per accepted comments

25
When to Stop?

• No model is deep in its entirety (selective
  decomp)
• Break in to several projects
• when sufficient detail
• all models should be as simple as possible, but
  no simpler

26
When to Stop? Examples

• when sufficient detail
• a change in abstraction level is required to
  detail the box
• change in viewpoint (terminology)
• similar functions
• trivial functions
• (10 -30) diagrams rule of thumb

27
Growth of models
Level in Model
Total boxes in Model
4 boxes/diagram
6 boxes/diagram
28
Supplementing Diagrams

• Text - Narrative of diagram
• Figures - FEO
• Glossary - defining terms (every term on idagram
  should appear in glossary)
• Node Tree
• Main Path in a diagram
• Activation Rules

29
Managing an SADT (IDEF) Project
Project Manager
Review Committee
Librarian
Authors
Experts
Readers
30
Levels of Consensus
Technical Review Committee
Recommend
Subsequent Drafts
Subsequent Drafts
Many Experts
Subsequent Drafts
Subsequent Drafts
First Draft
First Draft
One Expert
Working
31
Limits to making a diagram
Task
Brand New
New Version