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

Slides:



Advertisements
Similar presentations
CS3773 Software Engineering Lecture 01 Introduction.
Advertisements

Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall 3.1.
Project Monitoring CS 414 – Software Engineering I Donald J. Bagert Rose-Hulman Institute of Technology January 30, 2003.
Code Inspections CS 414 – Software Engineering I Donald J. Bagert Rose-Hulman Institute of Technology January 23, 2003.
The Role of Software Engineering Brief overview of relationship of SE to managing DSD risks 1.
Web Design! John Paxton Montana State University - Bozeman CCSC Northwestern Region Saturday, October 8 th, 2004.
The Soft Topics in Software Engineering Mark Ardis Stephen Chenoweth Frank Young.
Introduction to Requirements (Chapters 1-3 of the requirements text) CSSE 371, Software Requirements and Specification Don Bagert, Rose-Hulman Institute.
0-1 Team # Status Report (1 of 4) Client Contact –Point 1 –Point 2 Team Meetings –Point 1 –Point 2 Team Organization –Point 1 –Point 2 Team #: Team Name.
General information CSE 230 : Introduction to Software Engineering
1 Usability Testing Roles CSSE 376 Software Quality Assurance Rose-Hulman Institute of Technology April 23, 2006.
Feb. 2, 2004CS WPI1 CS 509 Design of Software Systems Lecture #3 Monday, Feb. 2, 2004.
Lecture 2b: Software Project Management CSCI102 - Introduction to Information Technology B ITCS905 - Fundamentals of Information Technology.
Nov. 13, 2003CS WPI1 CS 509 Design of Software Systems Lecture #11 Thursday, Nov. 13, 2003.
Software Project Planning CS 414 – Software Engineering I Donald J. Bagert Rose-Hulman Institute of Technology December 12, 2002.
Overview of the Rose-Hulman Bachelor of Science in Software Engineering Don Bagert SE Faculty Retreat – New Faculty Tutorial August 23, 2005.
Quality is about testing early and testing often Joe Apuzzo, Ngozi Nwana, Sweety Varghese Student/Faculty Research Day CSIS Pace University May 6th, 2005.
Diversity of Interaction in a Quality Assurance Course Mark Ardis, Rose-Hulman Institute Cheryl Dugas, Indiana State University FIE 2005.
System Testing CS 414 – Software Engineering I Don Bagert January 21, 2003.
Engineering H193 - Team Project Gateway Engineering Education Coalition P. 1 Spring Quarter 2007 Progress Reports Week 4 Day 1.
COMP4710 Senior Design Richard Chapman. Outline What is Senior Design? What is Senior Design? Course Structure Course Structure End of Cycle Binder End.
Risk Management CS 414, Software Engineering I Mark Ardis, Rose-Hulman Institute January 28, 2003.
Software Engineering Project Management (CS - 413)
Software Process CS 414 – Software Engineering I Donald J. Bagert Rose-Hulman Institute of Technology December 17, 2002.
 Getting started  Syllabus  Objectives and Evaluation  Teams and Mentors  Topics Covered  Learning Outcomes  Exams Regulations  Presentations.
Introduction to Project Management. What is a Project? “A planned undertaking of related activities to reach an objective that has a beginning and an.
Software Project Management By Assistant Prof. Samana Zehra
Diploma of Project Management Course Outline NSW Course Number Qualification Code BSB51407.
PROJECT MANAGEMENT FUNDAMENTALS Page 2 Course Overview 1. Introduction to Project Management 2. Project Roles and Expectations 3. Project Management.
Software Project Management Course Instructor Samana Zehra (Assistant Professor)
Introduction Course outline / Recommended books Course objectives Marks distribution / Schedule Basic concepts of SE and PM Project management framework.
Introduction. Classes: Tuesdays & Thursdays 8:30 – 10:00 am Groups: We will work in a group of 3 Sessions will be highly interactive! Prior learning is.
Process: A Generic View n A software process  is a roadmap to building high quality software products.  provides a framework for managing activities.
GE105: Introduction to Engineering Design Course Information College of Engineering King Saud University Feb 1, 2012.
Diploma of Project Management Course Outline NSW Course Number Qualification Code BSB51407.
Certificate IV in Project Management Course Structure Course Number Qualification Code BSB41507.
CMSC 345, Spring CMSC 345 Software Design and Development Spring 2003 Section 0101 Ms. Susan Mitchell “Welcome to the School of Hard Knocks”
Basic of Project and Project Management Presentation.
Quality Activity Matrix Presented by Sandra Toalston President, SanSeek 1.
Certificate IV in Project Management Certificate IV in Project Management Course Structure Course Number Qualification Code BSB41507.
INFO 424 Team Project Practicum Week 2 - Launch report, Project tracking, Review report Glenn Booker Notes largely from Prof. Hislop.
CMSC 345, Fall CMSC 345 Software Design and Development Fall 2003 Section 0101 Ms. Susan Mitchell Leave Your Ego at the Door!
CEN First Lecture CEN 4010 Introduction to Software Engineering Instructor: Masoud Sadjadi
Facilitators: Dr. Wanda Zagozdzon-Wosik Dr. Dr. Jung-Uk Lim ECE 4336: CAPSTONE DESIGN II.
PUBLIC INVOLVEMENT & TEAMING IN PLANNING US Army Corps of Engineers.
 Course Introduction.  Financial Planning (FIN 551 – 552 – 553) o Third in Series FIN 551 Overview of Financial Planning, Insurance, and Tax Planning.
1 Introduction to Software Engineering Wen-Yang Lin Dept. of Computer Science and Information Engineering National University of Kaohsiung February, 2007.
Meghe Group of Institutions Department for Technology Enhanced Learning 1.
CS 501: Software Engineering Fall 199 Lecture 1 a) Administration b) Introduction to Software Engineering.
Wilmer Arellano  Getting started  Syllabus  Objectives and Evaluation  Teams and Mentors  Topics Covered  Learning Outcomes  Exams Regulations.
Managing Agile Software Development Teams Using Scrum AKA: Wrangling Developers for Fun and Profit!
By: Wilmer Arellano.  1. Form a team  2. Find a Team Leader  3. Find Three Potential Topics  4. Find a Mentor  5. Select a Topic.
Requirements Engineering Lecture 13
Introduction to Software Engineering Course Outline
CS616 Software Engineering I BoNY
Advanced Programming Dr. Sadi Seker.
Lecture 0 Software Engineering Course Introduction
CMPE 412 Software Engineering
ECE361 Engineering Practice
DT249/4 Information Systems Engineering Lecture 0
Project Management.
Software Engineering B.E IT Sem-VII
Chapter 3 Managing the Information Systems Project
9/18/2018 Department of Software Engineering and IT Engineering
Training Officers Consortium
Project Management Process Groups
Overview of BSSE at Rose-Hulman Institute of Technology
Software Engineering.
SDLC (Software Development Life Cycle) Role Play
Presentation transcript:

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, 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 Example of Time Recording DateStartStopInterruptTotal Time ActivityComments 11/271:352:25 50classlecture 6:257:451565readchapters 1 and 2 of Pressman 11/281:352:25 50classlecture 11/301:352:25 50classlecture 6:409:2510, 25, 5125readproject descriptions, Finkelstein 9:2510:00 35writeresume and project choices 12/11:352:25 50classlecture

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

20 Introductions