CSE Senior Design I Day 1: Getting Organized Instructor: Vassilis Athitsos Based on an earlier presentation by Mike O'Dell, UTA, modified by Vassilis Athitsos.

Slides:



Advertisements
Similar presentations
And Optional Tour of GCCs High Tech Center 1. Advice about how to start an Open Entry course and successfully finish Brief introduction to HTC guidelines.
Advertisements

And Optional Tour of GCC’s High Tech Center 1.  Advice about how to start an Open Entry course and successfully finish  Brief introduction to HTC guidelines.
More CMM Part Two : Details.
Introduction CSCI102 - Systems ITCS905 - Systems MCS Systems.
School of Electrical and Computer Engineering ECE 400 Seminar Fall 2012.
And Optional Tour of GCC’s High Tech Center 1.  Advice about how to start an Open Entry course and successfully finish  Brief introduction to HTC guidelines.
Fall 2004 WWW IS112 Prof. Dwyer Intro1: Overview and Syllabus Professor Catherine Dwyer.
CSE 322: Software Reliability Engineering Topics covered: Course outline and schedule Introduction, Motivation and Basic Concepts.
MIS 470: Information Systems Project Yong Choi School of Business Administration CSU, Bakersfield.
COMP 110 Introduction to Programming Mr. Joshua Stough August 22, 2007 Monday/Wednesday/Friday 3:00-4:15 Gardner Hall 307.
Course Introduction (Lecture #1) ENGR 107 – Intro to Engineering The slides included herein were taken from the materials accompanying Engineering Fundamentals.
COMP 14 – 02: Introduction to Programming Andrew Leaver-Fay August 31, 2005 Monday/Wednesday 3-4:15 pm Peabody 217 Friday 3-3:50pm Peabody 217.
Introduction to Programming Environments for Secondary Education CS 1140 Dr. Ben Schafer Department of Computer Science.
Senior Design Tom Rethard. Courses CSE 4316/4317 Taken by CSE, SE and CS majors CSE 4316 Primarily “Professional Practices” – otherwise known as 3310+
Recitation Week #1 Chem Queens College Spring 2010.
CSE Senior Design I Fall 2014 Day 1: Getting Organized Instructor: Mike O’Dell.
BIT 115: Introduction To Programming1 Sit in front of a computer Log in –Username: 230class –password: –domain: student Bring up the course web.
MATH 112 (Tuesday) Spring 2015 Instructor:. Syllabus Keep your copy of the syllabus handy  Questions will arise throughout the semester  Answers can.
Welcome to CS 3260 Dennis A. Fairclough. Overview Course Canvas Web Site Course Materials Lab Assignments Homework Grading Exams Withdrawing from Class.
COMP Introduction to Programming Yi Hong May 13, 2015.
EECE 310 Software Engineering Lecture 0: Course Orientation.
ACIS 4684/5584 IS Security and Assurance. 2 Dr. Linda Wallace  Office: Pamplin 3092  
CSE 436 Software Engineering Workshop Course Overview Christopher Gill CSE 436 January 2007 Department of Computer Science and Engineering.
Course Introduction CSCI Software Engineering II Fall 2014 Bill Pine.
CSE Senior Design I Fall 2015 Day 1: Getting Organized Instructor: Mike O’Dell.
Hello World! CSE442. Course Summary A semester long group project – You will develop software from idea to implementation You have full freedom to choose.
MIS 300: Introduction to Management Information Systems Yong Choi School of Business Administration CSU, Bakersfield.
Welcome to Physics 1403!!. Class Web Page! There, you can find: 1. Posted (MS Word format): Syllabus,
Teaching Thermodynamics with Collaborative Learning Larry Caretto Mechanical Engineering Department June 9, 2006.
CSC 110 – Intro. to Computing Prof. Matthew Hertz WTC 207D /
Welcome to CS 115! Introduction to Programming. Class URL Write this down!
PHY 1405 Conceptual Physics (CP 1) Spring 2010 Cypress Campus.
IPC144 An Introduction to Programming Using C. Instructor Murray Saul Office: Rm –Office hours are posted on my IPC144 web page or on bulletin board.
Advanced Database Course (ESED5204) Eng. Hanan Alyazji University of Palestine Software Engineering Department.
IT Semester 1 Course Introduction IT Portfolio IT 1140 ( Semester 1) Hong Kong Baptist University IT 1140 – IT Portfolio – Course Introduction.
TIPS FOR EFFECTIVE TEACHING IN STEM HIGHER EDUCATION Benjamin C. Flores, Ph.D. Director, Computing and Electrical and Engineering Division MIE Project.
Principles of Computer Science I Honors Section Note Set 1 CSE 1341 – H 1.
CSE Senior Design I Fall 2011 Day 1: Getting Organized Instructor: Mike O’Dell.
Welcome to the First-Year Engineering Program ENGR 1181 Class 1 – Part 2.
CSE Senior Design II Day 1: Getting Organized Spring 2015 Instructor: Manfred Huber.
CP SC 428/628 D. E. Stevenson 10 Jan 07.
CSE 1105 Week 1 CSE 1105 Course Title: Introduction to Computer Science & Engineering Classroom Lecture Times: Section 001 W 4:00 – 4:50, 202 NH Section.
SE-2030 Software Engineering Tools and Practices SE-2030 Dr. Mark L. Hornick 1.
ACIS 3504 Accounting Systems and Controls. 2 Dr. Linda Wallace  Office: Pamplin 3092  
CPSC 315 Programming Studio Spring 2008 John Keyser.
CS151 Introduction to Digital Design Noura Alhakbani Prince Sultan University, College for Women.
Syllabus Highlights CSE 1310 – Introduction to Computers and Programming Vassilis Athitsos University of Texas at Arlington 1.
COP4020 INTRODUCTION FALL COURSE DESCRIPTION Programming Languages introduces the fundamentals of the design and implementation of programming languages.
Computer Networks CNT5106C
CSE Senior Design II Day 1: Getting Organized Spring 2012 Instructor: Mike O’Dell.
CSE Senior Design II Day 1: Getting Organized Spring 2016 Instructor: Mike O’Dell.
WELCOME TO MICRO ECONOMICS AB 224 Discussion of Syllabus and Expectations in the Class.
WELCOME TO MANAGERIAL ECONOMICS MT 445 Discussion of Syllabus and Expectations in the Class.
Welcome to Physics 1403!!. Class Web Page! There, you can find: 1. Posted (Word format): Syllabus,
CSE6339 DATA MANAGEMENT AND ANALYSIS FOR COMPUTATIONAL JOURNALISM CSE6339, Spring 2012 Department of Computer Science and Engineering, University of Texas.
Day 1: Getting Organized Spring 2014
Computer Network Fundamentals CNT4007C
Spring 2011 Day 1: Getting Organized
Summer 2013 Day 1: Getting Organized
Computer Networks CNT5106C
ACIS 3504 Accounting Systems and Controls
CGS 2100 Lab sections 0029, 0031, 0035, 0045, /9/18.
Day 1: Getting Organized Fall 2011
Computer Networks CNT5106C
Day 1: Getting Organized Fall 2012
Day 1: Getting Organized Summer 2012
Day 1: Getting Organized Fall 2013
Day 1: Getting Organized Spring 2013
ACIS 3504 Accounting Systems and Controls
Day 1: Getting Organized Spring 2011
Presentation transcript:

CSE Senior Design I Day 1: Getting Organized Instructor: Vassilis Athitsos Based on an earlier presentation by Mike O'Dell, UTA, modified by Vassilis Athitsos

1 CSE What’s This Class About? capstone course put it all together. In this course you will:  This is the CSE capstone course, where you put it all together. In this course you will: team  Work on a team with your fellow students software product development cycle  Learn a lot about the software product development cycle by actually experiencing it phased development process  Study and implement a “real world” phased development process  Develop a working product  Develop a working product “from scratch” planning and requirements  In CSE prepare and present planning and requirements documentation for your project. complete the project  In CSE continue and complete the project and demonstrate your working prototype

1 What will we do? CSE Build a TEAM TEAM PLAN PLAN Establish Product REQUIREMENTS & FEASIBILITY Establish Product REQUIREMENTS & FEASIBILITY DESIGN Your Product DESIGN IMPLEMENT & TEST Your ProductIMPLEMENT Product DEMONSTRATE Your Product Your ProductDEMONSTRATE Senior Design 2 Senior Design 1

1 CSE Lectures and Labs  Lectures and Labs mostly mean the same thing this semester.  Lectures on key topics case studies  Class discussion of case studies.  Reviews of major design documents.  Presentation by team, critique by rest of class.  Quizzes

1 CSE "Lab" Activities  Team Status Presentations ENB)  Individual Status Reports and Engineering Notebook (ENB) Reviews  Deliverable Review  Deliverable Review Presentations  Class Exercises, Special Topics

1 CSE Class Syllabus  YOU  YOU are responsible for understanding the information in the class syllabus  Ask questions if you are unclear on things  The syllabus may evolve web copy of the syllabus  The web copy of the syllabus is the current version

1 CSE Class Attendance It is a part of your grade  Attendance is expected at any and all scheduled activities: class, lab, team meetings, etc. It is a part of your grade.  Attendance is highly correlated with contributions to team and project.  It’s better to come to class late than miss the class altogether.  N.B. - If you don’t come to class, you can’t participate in the learning process.  Do you get to skip work when you don’t want to go?

1 Course Plan Rules: Senior Design substantially completed  Must have substantially completed upper- division courses prior to CSE 4316  Specified prerequisites: CSE 3310, 3320, 3322  Co-requisite: CSE 3316 (beginning Fall 2010) on same project and team  Must complete CSE 4316 followed by CSE 4317 in a two consecutive semester sequence (on same project and team)  Must pass CSE 4316 to enroll in CSE 4317 CSE

1 9 Grading: Components/Weights  See syllabus for details  Individual Deliverables (35%)  Items for which you are individually responsible  Team Deliverables (35%):  Items for which the team is responsible  Attendance (20%)  Participation (10%)

1 CSE Homework & Lab Assignments  Due as specified on the course web page.  Must be submitted on Blackboard.  Will be accepted late until 10 hours after due date, with a late penalty of 10% per hour. For submissions more than 10 hours late, grade is zero.  All out-of-class work must be “typed” – handwritten work is not acceptable.

1 CSE Your first assignment  See course web page for details.  Papers should be formatted according to Senior Design Standard 001 (see website)  Submit on Blackboard

1 CSE Engineering Notebook  You are required to maintain an Engineering/ Project Notebook throughout the project. your grade on Individual deliverables  Your records are an integral part of your project, therefore it will be used as a component of your grade on Individual deliverables.  Good record keeping is necessary for process improvement, and process improvement is necessary to be a good engineer/developer. brought with you  Your notebook should be brought with you to all lab/class sessions. inspection and grading  Notebooks are subject to inspection and grading by the GTA/Instructor at any time, without notice.  Team leader will be asked to review occasionally

1 CSE Ethics assume that you all are honest and ethical  Today, I assume that you all are honest and ethical  If you give me reason to believe that you are not, the UTA Engineering College Code of Ethics will be enforced. may assist your fellow students  You may assist your fellow students, (in fact, this is encouraged and expected)  You may not allow your fellow students to copy your work, or copy theirs.  Unauthorized  Unauthorized shared work will be treated as cheating.

1 CSE Class Website every class day  Check it at least every class day  All presentations and class materials are posted there  Assignments will be posted there when assigned.  Also: supporting info, relevant standards, required forms, etc.

1 CSE The Projects – General Guidelines  Maximum size of a project is one cubic yard – 3’ x 3’ x 3’ (guideline only, verify)  Projects MUST be approved and assigned by me before work begins.  Each team has a budget of $800 for required product components

1 CSE The Projects – General Guidelines  What you may not have:  Security systems or parts thereof i.e., anything that might ‘mess with” campus network  Research projects  Remote-control vehicle projects This does not include remote-controlled testing of autonomous vehicles, or autonomous additions to RC vehicles.

1 CSE Sponsored Projects  It is expected that you will have an external “customer” for your project.  Encourages a more realistic project  Injects outside feedback  Some sponsors may even fund project

1 CSE Lab/Work Area  Senior Design Lab is 208 ERB  Each team will have:  a dedicated area (cubicle) of about 160 sq. ft. for your team activities.  adequate chairs and table space  a lockable cabinet for storage of parts, etc.  a team computer  READ and understand “Lab Rules of Etiquette” paper

1 CSE Lab/Work Area  For lab access you will need your badge/ ID and your self service PIN number.  Swipe your badge, then key in 5-digit PIN  If you don’t know your PIN, you can get it by:  going to  clicking “VIEW INFORMATION ABOUT YOUR ACCOUNTS”,  logging in with your MavID and password  Your PIN will be shown with other account information

1 CSE Tools  You may be required to learn and use the current versions of the following:  MS Office  MS Project  Others may be required to complete your specific project

1 CSE Project Team Composition  4-5 members  Multidisciplinary – an equitable distribution of male/female, CS/CSE/SwEng will be enforced, except as specified for special projects  No dating/married couples allowed on teams  The instructor will form the teams.  You can specify people you do not want to work with.

1 CSE How We’re Going to Do Things Superior Designs, Inc.  This a small company: “Superior Designs, Inc. ”  You are the development department  Divided into teams for various projects (products)  Each team has a team lead  We use a proven, phased development process  You develop and get approval for the roadmap to deliver your product on time  Weekly “staff” meetings to review project status/progress (generally, Friday lab period)  Failure of one team => failure of company

1 CSE How We’re Going to Do Things  I am the “boss” (development manager)  I will mentor you & help you learn how to do your job  I will approve your plans  I will approve your project expenses  I believe every question is worth answering  I don’t do your work for you  I don’t do your research for you  I don’t know everything about anything  I expect you to do your job, and will measure you on how well you do it

1 CSE How We’re Going to Do Things  This semester you will: build your team  Establish and build your team project  Be assigned to a team project (product) plan  Establish your plan (schedule, budget, etc.) Requirements  Complete your Requirements Specification (SRS) and a successful Requirements Gate Review feasibility analysis  Conduct feasibility analysis Architecture  Get started on Architecture/Design  Next semester you will complete the project  Detailed design, implementation, test, prototype delivery and final acceptance

1 CSE Work Load 5-6 months of calendar working time  You have roughly 5-6 months of calendar working time for your project.  That’s, at most, 500 man-hours per team member  A 5 person team has 2500 man-hours to complete the project (4 people => 2000 man-hours) Equivalent of about one man-year, or 5 K delivered lines of source code by typical metrics  Don’t pad your schedule trying to make it easy on yourself outside of the classroom  Expect to spend hours every week outside of the classroom on the project  Failure to expend the required time will result in failure to complete the project (with a similar effect on your course grade)

1 CSE Work Load  Planthen work  Plan your work, then work your plan tools  Learn your tools well, and the work load will be lighter. less time  Do it the way we talk about in class, and you’ll spend less time redoing things. by industry  Remember: the methods we discuss are time-tested by industry… they work!

1 CSE ABET ABET  Must pass all ABET (Accrediting Board for Engineering and Technology) Outcome Assessments to pass this class.  SD I ABET Outcome is: multi-disciplinary team  Ability to function on a multi-disciplinary team Will be assessed by peer evaluation at end of semester