1. Fall 2006 1 CS-EE 480 Lillevik 480f06-l7 University of Portland School of Engineering Senior Design Lecture 7 Functional specifications Technical meetings MS word template (optional)

2. Fall 2006 2 CS-EE 480 Lillevik 480f06-l7 University of Portland School of Engineering Functional specifications Front: title page, revision history, TOC, LOF Body –Summary –Introduction –Background –Requirements –Conclusions Back: appendices

3. Fall 2006 3 CS-EE 480 Lillevik 480f06-l7 University of Portland School of Engineering Requirements section Contents: vary with technical discipline Overview: discuss the big picture Examples –Physical, environmental, hardware, software –Core functionality, security, user preferences, text editor, chat area, file transfer, portlets, user inteface –Inputs, outputs, display, power, physical, environmental

4. Fall 2006 4 CS-EE 480 Lillevik 480f06-l7 University of Portland School of Engineering FS hints Describe your project in as much detail as possible  most important !! If you are not sure about something, make a best guess Cluster requirements into logical groups Start with an overview, then describe the groups

5. Fall 2006 5 CS-EE 480 Lillevik 480f06-l7 University of Portland School of Engineering FS hints, continued. Use tables and figures, but reference and discuss them Every project’s requirements are different Don’t force your project into an example or the template >> This is the biggest single problem! <<

6. Fall 2006 6 CS-EE 480 Lillevik 480f06-l7 University of Portland School of Engineering Any FS questions?

7. Fall 2006 7 CS-EE 480 Lillevik 480f06-l7 University of Portland School of Engineering Technical Meetings We will hold a number of formal meetings with your advisor and industry rep Our goal is to hold a professional meeting that accomplishes the goal We represent the University to the technical community

8. Fall 2006 8 CS-EE 480 Lillevik 480f06-l7 University of Portland School of Engineering Technical meeting components Chair Presenters Participants: required and optional Purpose: reason for meeting Agenda: topics to discuss Minutes: document meeting and results

9. Fall 2006 9 CS-EE 480 Lillevik 480f06-l7 University of Portland School of Engineering Meeting types 1.Decision: make a decision 2.Informative: communicate timely status 3.Brain Storming: develop alternative solutions to some problem Your team will hold all of these, many informal Approvals

10. Fall 2006 10 CS-EE 480 Lillevik 480f06-l7 University of Portland School of Engineering Decision meeting Purpose: make a decision What decision(s) must be acted on? Who are the decision makers (voters)? When must the decision be made? Who receives notice of the decision? Example: approval meeting

11. Fall 2006 11 CS-EE 480 Lillevik 480f06-l7 University of Portland School of Engineering Informative meeting Purpose: communicate timely status What subjects are to be covered? Who should review what subjects? Who needs to hear it? Example: team meeting, program review

12. Fall 2006 12 CS-EE 480 Lillevik 480f06-l7 University of Portland School of Engineering Brain storming meeting Purpose: develop alternative solutions to some problem What is the subject/problem? Who should participate? What has been done so far? Who should be informed? Example: group problem solving

13. Fall 2006 13 CS-EE 480 Lillevik 480f06-l7 University of Portland School of Engineering Meeting agenda List the topics, order, and presenter –Update status of previous action items (if any) –Past subjects –New subjects –Open items Time limits may be required

14. Fall 2006 14 CS-EE 480 Lillevik 480f06-l7 University of Portland School of Engineering Role of chair? Facilitate meeting Time keeper Quality control, don’t waste time Make sure everyone attends

15. Fall 2006 15 CS-EE 480 Lillevik 480f06-l7 University of Portland School of Engineering Role of presenter? Field questions Stay on topic To inform Keep material interesting Send out material in advance Stay within your time limit Make sure people follow you Sell and idea

16. Fall 2006 16 CS-EE 480 Lillevik 480f06-l7 University of Portland School of Engineering Role of participant? Listen Provide feedback Ask questions Be punctual, RSVP\ Come prepared, read document in advance Don’t fall asleep

17. Fall 2006 17 CS-EE 480 Lillevik 480f06-l7 University of Portland School of Engineering Meeting minutes Start with summary List date, time, purpose Identify all attendees (affiliation, title) Review each subject discussion Action items: owner, action, due date, status Announce next meeting, agenda Put minutes in body of email, add to web

18. Fall 2006 18 CS-EE 480 Lillevik 480f06-l7 University of Portland School of Engineering Optional Lecture Material

19. Fall 2006 19 CS-EE 480 Lillevik 480f06-l7 University of Portland School of Engineering FS template, MS Word 2003 Copy template document from web Modify text only Use Styles and Formatting buttons, don’t modify or reinvent Don’t change the formating !!

20. Fall 2006 20 CS-EE 480 Lillevik 480f06-l7 University of Portland School of Engineering Styles and Formatting Highlight text and click desired format

21. Fall 2006 21 CS-EE 480 Lillevik 480f06-l7 University of Portland School of Engineering Headings Use three levels of headings –Heading 1, Heading 2, Heading 3 –A fourth level is too confusing to follow Headings are used to create TOC

22. Fall 2006 22 CS-EE 480 Lillevik 480f06-l7 University of Portland School of Engineering Headings

23. Fall 2006 23 CS-EE 480 Lillevik 480f06-l7 University of Portland School of Engineering Sections Document divided into sections Each chapter is a section Each section has its own headers and footers Most headers and footers are the same as the previous section

24. Fall 2006 24 CS-EE 480 Lillevik 480f06-l7 University of Portland School of Engineering Insert a section Insert  Break  Next page

25. Fall 2006 25 CS-EE 480 Lillevik 480f06-l7 University of Portland School of Engineering Headers/footers Each section has its own header/footer Each first page or odd/even page header/footer may different Headers/footers may be the same as the previous

26. Fall 2006 26 CS-EE 480 Lillevik 480f06-l7 University of Portland School of Engineering Viewing headers/footers View  Headers and Footer Link to previous Switch between header and footer Show previous, next Page setup

27. Fall 2006 27 CS-EE 480 Lillevik 480f06-l7 University of Portland School of Engineering Page setup: header/footer control

28. Fall 2006 28 CS-EE 480 Lillevik 480f06-l7 University of Portland School of Engineering Edit/create a header/footer View the header or footer Type in the text Check previous, next

29. Fall 2006 29 CS-EE 480 Lillevik 480f06-l7 University of Portland School of Engineering Header edits

30. Fall 2006 30 CS-EE 480 Lillevik 480f06-l7 University of Portland School of Engineering Footer edits

31. Fall 2006 31 CS-EE 480 Lillevik 480f06-l7 University of Portland School of Engineering TOC/LOF/LOT creation Word generates –TOC based on Heading tags –LOF, LOT based on Caption tags Use the insert command to enter Use update to adjust for changes

32. Fall 2006 32 CS-EE 480 Lillevik 480f06-l7 University of Portland School of Engineering TOC, LOF, LOT Insert  Reference  Index and Tables

33. Fall 2006 33 CS-EE 480 Lillevik 480f06-l7 University of Portland School of Engineering Captions Caption used for titles –Figures: below object –Tables: above object Word automatically numbers Allows for easy insert or delete Re-generate with TOC, LOF, LOT update

34. Fall 2006 34 CS-EE 480 Lillevik 480f06-l7 University of Portland School of Engineering Insert caption Insert  Reference  Captions

35. Fall 2006 35 CS-EE 480 Lillevik 480f06-l7 University of Portland School of Engineering Cross reference Refers to another part of your document –Figure n –Table n May be entered into text and updated when figures and tables added/deleted Example: Figure 3 discusses the relationship between ….

36. Fall 2006 36 CS-EE 480 Lillevik 480f06-l7 University of Portland School of Engineering Insert cross reference Insert  Reference  Cross-reference

37. Fall 2006 37 CS-EE 480 Lillevik 480f06-l7 University of Portland School of Engineering Document changes Goal: make it easier to review documents between revisions Use the track changes tool 1.Save document at revision n 2.Copy document and rename n + 1 3.Turn on track changes tool 4.Accept all changes 5.Make changes

38. Fall 2006 38 CS-EE 480 Lillevik 480f06-l7 University of Portland School of Engineering Track changes enables Accept/reject

39. Fall 2006 39 CS-EE 480 Lillevik 480f06-l7 University of Portland School of Engineering Accepting all changes

40. Fall 2006 40 CS-EE 480 Lillevik 480f06-l7 University of Portland School of Engineering

41. Fall 2006 41 CS-EE 480 Lillevik 480f06-l7 University of Portland School of Engineering Role of chair? Call the meeting (date, time, location) Invites attendees Distribute presentations in advance Keep meeting on track (focus) –Summarize, then introduce next subject –Time limits, cut off discussion Assign action items Prepares/distributes minutes

42. Fall 2006 42 CS-EE 480 Lillevik 480f06-l7 University of Portland School of Engineering Role of presenter? Professional-quality collateral material Distribute to participants in advance Understand your purpose, time limit Know your audience Encourage discussion Never be defensive No bad jokes, belittle participants

43. Fall 2006 43 CS-EE 480 Lillevik 480f06-l7 University of Portland School of Engineering Role of participant? Be on time Be prepared Assume responsibility Be objective