Dave- I was wondering that also. I was using the text on pages 277 through 278 as a reference. I believe Dr. Nance wants through a DID 2 diagram which means a DID 1 as well. I was going to do it for slide set 5 but set 3 might be more appropriate. Here's my thinking. Where are we at in our development of the product. (analysis, design)? With our iterative, agile process we should have the design complete at this point. We could re-shuffle some slides at the end. Also, it may not be a bad idea to add a few more diagram slides. We should keep in mind that the focus of the course is software development. One idea might be a class diagram (since we are doing OOP p. 205 in text). Don't get me wrong - I don't want to make this complicated, but I have a feeling that more modeling = better grade. Just a thought. We can always finish what we have and if time permits, add some modeling slides. Paul -----Original Message----- From: msit620-bluegroup-bounce@xxxxxxxxxxxxx [mailto:msit620-bluegroup-bounce@xxxxxxxxxxxxx] On Behalf Of DelGaudio, Dave Sent: Tuesday, June 26, 2007 10:00 To: msit620-bluegroup@xxxxxxxxxxxxx Subject: [msit620-bluegroup] Re: slide set 3 posted Paul, Like the safehome examples I've been reading about in the book everything comes off of the control panel. Maybe you can start with the automobile cockpit with branches coming off of it for the modeling - (dashboard being a main one and its subcomponents, lights being another main one and which lights as subcomponents...). I would probably do a DFD basic model like that on page 195 and a DFD level 2 like the example of page 197. I'm wondering if the DFD basic level should be in slide set 3 instead of having you doing both in set 5? Maybe just a DFD level 2 would be sufficient. -Dave -----Original Message----- From: Barnswell, Lashawn CTR MDA/DOCN [mailto:Lashawn.Barnswell.ctr@xxxxxxx] Sent: Tuesday, June 26, 2007 9:29 AM To: Paul Gillespie; Paul Gillespie; DelGaudio, Dave Cc: msit620-bluegroup@xxxxxxxxxxxxx; LaShawn Barnswell Subject: RE: slide set 3 posted Paul, I agree. Sounds good you could also include turn signals, right and left turns, lane changing, stop signs, 4-way stop, passing, 2-lane, 4 lane highways, blind spots, spacing avoiding a crash, speed, shifting gears, Park, netural, backing-up, etc. Hope this helps... LaShawn Those commands and the sensors all sound good and appropriate. For some more ideas I think you could also include clutch, automatic or manual transmission types, actual key start, automatic windows. However creative you want to get. Voice command could be neat if you were driving in the simulation and just said winter and snow came down instead of having to restart simulation with new season. I think you are on the right track. Take a stab at it and see what you come up with. -Dave -----Original Message----- From: msit620-bluegroup-bounce@xxxxxxxxxxxxx [mailto:msit620-bluegroup-bounce@xxxxxxxxxxxxx] On Behalf Of paul.d.gillespie1@xxxxxxxx Sent: Monday, June 25, 2007 7:49 AM To: msit620-bluegroup@xxxxxxxxxxxxx Subject: [msit620-bluegroup] Re: slide set 3 posted The following note has been forwarded to you by Paul D Gillespie from conference 'MSIT630 Section 9040'. ------------------------------------------ These slides look really good. Some notes would help as Dave suggested. The context DFD is important to me as I'm a doing the DFD Level 1 and 2 slides. Notes would help in watching the evolution of the DFD's. My major concern is the basic layout of the system. What user commands do we want to incorporate? The sensors I figure, would be gas pedal, brake, and steering wheel. User commands could be start, stop, weather conditions, ec. (voice recognition ??). We could get the design team together or I could just take a stab at the models and bounce it off every one else. This email and any file transmitted with it may be confidential and is intended solely for the use of the individual or entity to whom it is addressed. If you received this email in error please reply to the sender and delete this message. This email has been scanned by McAfee Group Shield antivirus service for the presence of viruses. This email and any file transmitted with it may be confidential and is intended solely for the use of the individual or entity to whom it is addressed. If you received this email in error please reply to the sender and delete this message. This email has been scanned by McAfee Group Shield antivirus service for the presence of viruses.