1 / 20

Introduction

Introduction. CS 414, Software Engineering I Mark Ardis and Don Bagert Rose-Hulman Institute December 2, 2002. Outline. Short demo of Tcl/Tk Overview of Course Introductions. Tcl/Tk Demo. Course Syllabus. Available from course web page Required text:

oni
Download Presentation

Introduction

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Introduction CS 414, Software Engineering I Mark Ardis and Don Bagert Rose-Hulman Institute December 2, 2002

  2. Outline • Short demo of Tcl/Tk • Overview of Course • Introductions

  3. Tcl/Tk Demo

  4. Course Syllabus • Available from course web page • Required text: Software Engineering: A Practitioner's Approach (fifth edition), by Roger S. Pressman, McGraw-Hill, 2000. • Recommended text: Practical Programming in Tcl and Tk (third edition), by Brent B. Welch, Prentice Hall, 2000.

  5. Course Objectives • Communication skills • Management skills • Technical skills • Knowledge areas • Professionalism skills

  6. Communication Skills • Reading • Writing • Oral presentation

  7. Management Skills • Leadership • Time management • Meeting facilitation • Estimating • Risk • Planning • Monitoring

  8. Technical Skills • Analysis • Design • Coding • Testing

  9. Knowledge Areas • Requirements • Analysis • Design • Implementation • Quality Assurance • Evolution • Process • Project management

  10. Professionalism Skills • Ethical and social issues • Intellectual property • Professional behavior • Contractual issues • Client relationships

  11. Cartoon of the Day

  12. Project Work • Teams • Phases and roles • Reviews • Presentations • Deliverables

  13. Project Teams • 7 or 8 students per team • team composition will be decided by instructors • some students may change teams at beginning of each phase

  14. Project Presentations • At end of each term • Each team member must participate

  15. Project Retrospectives • At end of each term • Review of successes and failures • Plan for next phase

  16. Engineering Notebook • Record of all work done on a project • Demonstrates that standard engineering practices have been followed • Evidence of creation of intellectual property • patents often refer to engineering notebooks

  17. Keeping Track of Your Time • Need to know how you spend your time before you can estimate how much time a task will take • Use a standard form in your engineering notebook • We will review these notes throughout the term

  18. Date Start Stop Interrupt Total Time Activity Comments 11/27 1:35 2:25 50 class lecture 6:25 7:45 15 65 read chapters 1 and 2 of Pressman 11/28 1:35 2:25 50 class lecture 11/30 1:35 2:25 50 class lecture 6:40 9:25 10, 25, 5 125 read project descriptions, Finkelstein 9:25 10:00 35 write resume and project choices 12/1 1:35 2:25 50 class lecture Example of Time Recording

  19. Hints on Logging Time • Keep your engineering notebook with you at all times • Estimate incomplete data as soon as possible

  20. Introductions

More Related