CS352 Software Engineering Project (Software Engineering in the Small) Michael Oudshoorn and Ray Babcock.

Slides:



Advertisements
Similar presentations
John Hurley Cal State LA
Advertisements

CS1313 SCCC/ATS COURSE SYLLABUS Programming Fundamentals Revised 12/2/2014 Online 12/14 revision Ed Hall Instructor.
5/19/2015CS 2011 CS 201 – Data Structures and Discrete Mathematics I Syllabus Spring 2014.
Introduction to Financial Management. Overview of Financial Management Introduction Keys to Success Stay up in class (complete assignments on time each.
Introduction to CS170. CS170 has multiple sections Each section has its own class websites URLs for different sections: Section 000:
CS460 Senior Design Project I (Software Engineering in the Large)
General information CSE 230 : Introduction to Software Engineering
CMSC 132: Object-Oriented Programming II
CS 201: Introduction To Programming With Java
CS351 Software Engineering (Software Engineering in the Small)
CS 152 & CS 154 Bill Crum, Lecturer Bill White, Instructional Coordinator Earth Chandrraungphen, Lab TA.
Instructor: Dr. Radwan E. Abdel-Aal Office: Tel Web page:
CS-2852 Data Structures LECTURE 1A Andrew J. Wozniewicz Image copyright © 2010 andyjphoto.com.
A Brief Calculus Course
CS 450: COMPUTER GRAPHICS COURSE AND SYLLABUS OVERVIEW SPRING 2015 DR. MICHAEL J. REALE.
CSE 1111 Week 1 CSE 1111 Introduction to Computer Science and Engineering.
Welcome to CS 115! Introduction to Programming. Class URL Please write this down!
Introduction to MA Day 1. Name: Charlotte Bailey Office: MATH 802 Office Phone: (765)
Introduction to MA Introduction to Calculus
Conquering Complex and Changing Systems Object-Oriented Software Engineering Chapter 1, Introduction to Software Engineering.
Paul Bourke DT211/3 & DT228/3 Team Project Paul Bourke Module Web Page:
1 MSCS 237 Distributed Computing Spring 2006 INSTRUCTOR: Dr. Sheikh Iqbal Ahamed Office: Cudahy Hall 386 Phone: Office Hours: Monday 2:00-3:00pm.
COMP 111 Programming Languages 1 First Day. Course COMP111 Dr. Abdul-Hameed Assawadi Office: Room AS15 – No. 2 Tel: Ext. ??
Welcome to CS 3260 Dennis A. Fairclough. Overview Course Canvas Web Site Course Materials Lab Assignments Homework Grading Exams Withdrawing from Class.
Lecture 1 Page 1 CS 111 Summer 2015 Introduction CS 111 Operating System Principles.
Object Oriented Programming (OOP) Design Lecture 1 : Course Overview Bong-Soo Sohn Assistant Professor School of Computer Science and Engineering Chung-Ang.
Object Oriented Programming (OOP) Design Lecture 1 : Course Overview Bong-Soo Sohn Associate Professor School of Computer Science and Engineering Chung-Ang.
Course Introduction Software Engineering
CS352 Software Engineering (Software Engineering in the Small) Michael Oudshoorn and Ray Babcock.
COMP 465W Software Engineering Fall Components of the Course The three main components of this course are: The study of software engineering as.
MIS 300: Introduction to Management Information Systems Yong Choi School of Business Administration CSU, Bakersfield.
CS1201: Programming Language 2 C++(Course Introduction) Level 2 Nouf Aljaffan 1 st Term Nouf Aljaffan (C) CSC 1201 Course at KSU.
English 370 Thursdays 6:05-8:50 PM Melissa Gunby.
Bilgisayar Mühendisliği Bölümü CENG 102 – Computer Programming Melek OKTAY Syllabus Administrative Information.
Welcome to CS 115! Introduction to Programming. Class URL Write this down!
MAT 360 – Lecture 0 Introduction. About me  Moira Chas   Work phone :  Office Location:
BSc Final Year Projects in Computing Computer Science, Creative Computing, Games Programming, Business Computing Dr Rodger Kibble.
Fall 2o12 – August 27, CMPSC 202 First Day Handouts  Syllabus  Student Info  Fill out, include all classes and standard appointments  Return.
CSEP 545 Transaction Processing for E-Commerce Course Information Spring (March – May) 2007.
Lecture Section 001 Spring 2008 Mike O’Dell CSE 1301 Computer Literacy.
CS-2851 Dr. Mark L. Hornick 1 CS-2852 Data Structures Dr. Mark L. Hornick Office: L341 Phone: web: people.msoe.edu/hornick/
Object Oriented Programming (OOP) Design Lecture 1 : Course Overview Bong-Soo Sohn Associate Professor School of Computer Science and Engineering Chung-Ang.
BA 4226 Managing Organizational Change Introduction Course syllabus available at Instructor: Ça ğ rı Topal 1.
CPS120: Introduction to Computer Science Winter 2002 Instructor: Paul J. Millis.
King Saud UniversityCSC112 - First Semester CSC 112 Java Programming I Introduction.
Fall 2011 Course Syllabus Instructor: Sergiu Dascalu Department of Computer Science and Engineering August 30,
CS451 Software Engineering II CS451 Software Engineering II Michael Oudshoorn and Ray Babcock.
CS Welcome to CS 5383, Topics in Software Assurance, Toward Zero-defect Programming Spring 2007.
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.
INTRODUCTION TO PROGRAMMING ISMAIL ABUMUHFOUZ | CS 146.
ICS202 Data Structures King Fahd University of Petroleum & Minerals College of Computer Science & Engineering Information & Computer Science Department.
WELCOME to CS244 Brent M. Dingle, Ph.D Game Design and Development Program Mathematics, Statistics and Computer Science University of Wisconsin -
CSE 1105 Week 1 CSE 1105 Introduction to Computer Science & Engineering Time: Wed 4:00 – 4:50 Thurs 9:30 – 10:20 Thurs 4:00 – 4:50 Place: 100 Nedderman.
IENG 450 INDUSTRIAL MANAGEMENT Bakiye YALINC MSc- Consulting and Business Policy.
English 370 Monday – Thursday 10:00 – 11:50 Melissa Gunby.
MAD2053 – WEB DESIGN WEEK 1 - INTRODUCTION. CLASS DAY TUESDAY 4pm to 6pm – Lecture/In Class Discussions/ Consultations at AR0002 WEDNESDAY (Mr. Imran)
Welcome to Numerical Analysis Math 448/548 Cpt S 430/530 Fall 2016 Instructor: John Miller, West 134E Class web page can be found.
James Tam Introduction To CPSC 233 James Tam Java Object-Orientation Event driven software.
Introduction to Financial Management. Overview of Financial Management Introduction Keys to Success Recitations Class Structure - Syllabus Text – Financial.
Course Information CSE 2031 Fall Instructor U. T. Nguyen /new-yen/ Office: CSEB Office hours:  Tuesday,
PROBLEM SOLVING AND PROGRAMMING ISMAIL ABUMUHFOUZ | CS 170.
CS351 Software Engineering (Software Engineering in the Small) Michael Oudshoorn and Ray Babcock.
CS351 Software Engineering I Michael Oudshoorn and Denbigh Starkey.
Computer Science I ISMAIL ABUMUHFOUZ | CS 180. CS 180 Description BRIEF SUMMARY: This course covers a study of the algorithmic approach and the object.
Welcome to CS 1010! Algorithmic Problem Solving.
CS 201 – Data Structures and Discrete Mathematics I
Welcome to CS 1010! Algorithmic Problem Solving.
Welcome to CS 1010! Algorithmic Problem Solving.
CS460 Senior Design Project I (Software Engineering in the Large)
Analysis of Algorithms
Presentation transcript:

CS352 Software Engineering Project (Software Engineering in the Small) Michael Oudshoorn and Ray Babcock

CS351 - Software Engineering (AY2004)2 Introduction This course is taught by Michael Oudshoorn and Ray Babcock Ray’s consulting times will be advertised outside of his door. Please make an appointment with Jeannette if you want to see Michael. The lecture time for this course is Tuesday and Thursday 5- 6pm. The course will have few, if any, formal lectures and this time will be used for group meetings and class-wide discussions. It will also be used for any class-wide announcements.

CS351 - Software Engineering (AY2004)3 Assumptions We will assume that you have completed CS351 Software Engineering last semester. CS352 is a project-based course that will give you the opportunity to use all of the skills you learned last semester. There will be 2 major assignments that must be completed this semester.

CS351 - Software Engineering (AY2004)4 Objectives The objectives for CS352 are that you have the opportunity to apply your skills from CS351 in a setting that models the real- world within the confines of the subject plans and objectives, and within the boundaries of a university course. We aim to develop and fine-tune your individual software engineering skills. [CS460/461 aims to develop your team-work]. –This means you will take sole responsibility for your work, but you will need to cooperate with others.

CS351 - Software Engineering (AY2004)5 Our hopes By the time students finish this course they should have real- world experiences that will see them well placed to get employment after taking CS460/461. Students should be able to talk to employers about the problems and issues involved in building large complex systems.

CS351 - Software Engineering (AY2004)6 Project 1 There are two projects for CS352. Each project has multiple parts and you will need to cooperate with your classmates in order to be successful. The first project is an Othello program. It will provide an opportunity to practise your skills in: –Software design specifications –Coding –Software management –Testing –Communication

CS351 - Software Engineering (AY2004)7 Project 2 You will be given a project description and various interfaces to adhere to. You will need to select a fixed number (say 3) of the modules to build yourself, and you will need to acquire the remainder from your classmates. You will buy and sell the modules. You will need to maintain the software you sell. Each person will start the semester with 100 zorkmids to use for the purchase of software. You will need to advertise your products (web pages) and give a short presentation. There is an entrepreneurial element through selling and buying your software. You will learn: –Business skills –Subcontracting issues –Software acquisition and maintenance

CS351 - Software Engineering (AY2004)8 Individual-based The projects are individual based. You will not be working a component as part of a group. You will however be cooperating with others in order to succeed. The aim is to develop appropriate skills for you to develop high quality correct code within a software development environment. Plagarism will not be tolerated. Even though solutions may be available on the internet (i.e., Othello) you may not utilize them. You must design, build and test your own system. Penalties for cheating will be a score of 0 for that component and a 10% loss of available points for the project. Deadlines are firm. 20% of the available points are forfeited for each day (or part thereof) that a component is late. You can think of these are contractual penalties that apply to the project you are working on.

CS351 - Software Engineering (AY2004)9 Assessment There are 2 projects. Each project is worth 50% of the grade. A serious attempt must be made in both projects. There is no mid-term or final exam. There are no quizzes. Expectation: –High standards in the project work, i.e., high levels of professionalism. –Treat this as though you are employed and an aiming to make an impression.

CS351 - Software Engineering (AY2004)10 Resources available Web pages found at These include the CS351 lecture materials. The projects will use the lecture time to allow for the cooperation to take place. Ray and/or Michael will be available to provide help and assistance at these times.

CS351 - Software Engineering (AY2004)11 Consulting help There is no TA to assist you in this course! Like the real-world, you need to demonstrate a degree of self sufficiency and initiative. We expect you to solve most of your own problems! –Read the textbook –Use the library –Use the internet –Talk to your peers A consultant will be available in a consulting room to offer limited assistance with coding problems.

CS351 - Software Engineering (AY2004)12 Textbooks There are no fixed textbooks for this course. Like real-life, you need to decide if you need one, and if so, which book best suits you.

CS351 - Software Engineering (AY2004)13 Hint “Design for change” should be your mantra. Expect it, plan for it, design for it. Quality is an important part of any software system. To achieve that you have to know what you are doing well and what you are not doing well. –Keep a journal and observe what you do. –Record how long it takes to repair errors. –Observe where you introduced the error into the system. –Think about how you could improve to be: More productive More accurate. More efficient.