Schedule Tuesday April 17: First public code checkin – Initial dominion implementation; MUST define all functions, have a “working” (not bug free!) dominion.

Slides:

Advertisements

Similar presentations

Software Testing mae. Admin Need schedule of meeting with graders for user test Rubrics for Arch Eval posted Scheduled for next Tuesday will be posted.

Advertisements

CMPT 275 Software Engineering

Feedback.  Yes = 9  No = 3  Yes = 11  No = 1  No did not stipulate what they could not access.

Intro to CIT 594

Secure Operating Systems Lesson 1: Introductions and Expectations.

CSCE 145: Algorithmic Design I Introduction Muhammad Nazmus Sakib.

Intro to CIT 594

Welcome to MAT 142. Basic Course Information Instructor Office Office Hours Beth Jones PSA 725 Tuesday 10:30 am – 12 noon Thursday 10:30 am – 12 noon.

Logistics: –My office hours: T, Th 4-5pm or by appointment –Class Web page:

COMS W1004 Introduction to Computer Science June 25, 2008.

Finance 5040 Spring 2011 Welcome Dr. James Conover.

Welcome to MAT 142. Basic Course Information Instructor Office Office Hours Beth Jones PSA 725 Tuesday 10:30 am – 12 noon Thursday 10:30 am – 12 noon.

Revisions If you received the grade: “R” If you received the grade: “R” You must do a revision to receive a grade for lab 2. You must do a revision to.

EE 220 (Data Structures and Analysis of Algorithms) Instructor: Saswati Sarkar T.A. Prasanna Chaporkar, Programming.

CS 182 Sections 101 & 102 Joseph Makin Jan 19, 2004 Slides created by Eva Mok Thanks, Eva!

How to make a SIGGRAPH paper while having all the fun 

IS 320: Data Structures Spring Quarter DESCRIPTION This class is an introduction to data structures. The primary data structures—list, stack, queue,

1 CPT S 223: Advanced Data Structures (section 01) Fall 2010 School of EECS Washington State University, Pullman MWF 10:10-11 Sloan 5.

COMP 111 Programming Languages 1 First Day. Course COMP111 Dr. Abdul-Hameed Assawadi Office: Room AS15 – No. 2 Tel: Ext. ??

Data Structures and Programming.  Today:  Administrivia  Introduction to 225, Stacks  Course website: 

ENGR xD52 Computer Architecture Fall Hi, I’m Eric VanWyk, Class of ’07.

ISC/GAM 4322 ISC 6310 Multimedia Development and Programming Introduction.

CS 858 – Hot Topics in Computer and Communications Security Winter 2009 Introduction.

LAB.  Name : Maram ALdakheel   Web page:  O.H : --  My schedule:

Trustworthy Semantic Web Dr. Bhavani Thuraisingham The University of Texas at Dallas Review for the Final Exam December 8, 2008.

CSCE 496/896 Self-Managing Computer Systems Ying Lu 106 Schorr Center

Introduction to ECE 2401 Data Structure Fall 2005 Chapter 0 Chen, Chang-Sheng

Black box (Finite State Machine) testing Design for testability Coverage measures Random testing Constraint-based testing Debugging and test case minimization.

Excellence is a Habit Feb Lecture 14 We are what we repeatedly do. Excellence, then, is not an act, but a habit.” - Aristotle.

Test Corrections You may correct your test. You will get back 1/3 of the points you lost if you submit correct answers. This work is to be done on your.

Course Overhead. 1.2 Silberschatz, Galvin and Gagne ©2005 Operating System Concepts – 9 th Edition, Jan 12, 2012.

AOSC Discussion 0102 & My Info Greg Porter Office: 3107 Jule Hall Office Hours: Tuesday or by appointment. Always.

Black box (Finite State Machine) testing Design for testability Coverage measures Random testing Constraint-based testing Debugging and test case minimization.

Intro to CIT 594

1 CS 101 Today’s class will begin about 5 minutes late We will discuss the lab scheduling problems once class starts.

BUS 4720 Supply and Demand in Small Businesses. Host and Application Security Lesson 1: Introductions and Expectations.

Course Overview 1 FCM 710 Architecture of Secure Operating Systems Prof. Shamik Sengupta Office 4210 N

James Tam Introduction To CPSC 233 James Tam Java Object-Orientation Graphical-user interfaces.

Welcome to College Composition 1 for Paralegal Studies Majors CM114 Instructor: Tara King.

CSCE 990 Advanced Distributed Systems Seminar Ying Lu 104 Schorr Center

ICS 151 Digital Logic Design Spring 2004 Administrative Issues.

1 BIT 5495 Introduction Syllabus Instructor:Dr. Lance A. Matheson Office:Pamplin 1017 Office Hours:By appointment is best way to contact me Phone:

CS 360 Lab 1 Professor: Krzysztof Nowak TA: Mark Boady.

Web Syndication Formats Seminar Week 1 Old Dominion University Department of Computer Science CS 791/891 Spring 2008 Michael L. Nelson 1/16/08.

BIT 115: Introduction To Programming. 2 Today Midterm feedback Getting User Input.

CS 182 Sections 101 & 102 Leon Barrett Jan 17, 2007

Continuous Improvement for Writing

Economics of Information Week 1

DS595/CS525: Urban Network Analysis Prof. Yanhua Li

What do you learn in this class?

COMS S1007 Object-Oriented Programming and Design in Java

CS 111 Digital Image Processing

Continuous Improvement for Writing

BIT 115: Introduction To Programming

Intro to CIT 594

CS 250, Discrete Structures, Fall 2014 Nitesh Saxena

Intro to CIT 594

Continuous Improvement for Writing

Administrative Issues

Continuous Improvement for Writing

Continuous Improvement for Writing

Continuous Improvement for Writing

Homework Reading Machine Projects Labs

Spring 2014 Internships.

Project Iterations.

Continuous Improvement for Writing

Lecture 1 Class Overview

Continuous Improvement for Writing

Home work 2 Jie.

Presentation transcript:

Schedule Tuesday April 17: First public code checkin – Initial dominion implementation; MUST define all functions, have a “working” (not bug free!) dominion – Place in PROJECT/dominion-code/ Tuesday April 24: First test report due – Report goes in PROJECT/report1/ – Tester code goes in PROJECT/tester-code/ Tuesday May 15: Second test report due – You can guess where report goes. Update tester-code. Tuesday June 5th: “Late Midterm” in class June 11: FINAL TEST REPORT DUE, PROJECT MUST BE COMPLETED

Grading & Other Admin Stuff Project: 75% Late “midterm”: 15% (Possibly-in-class) quizzes/exercises/homework: 10% My office hours: Wed, 11-12:30 or by appointment! Or just me (fastest turnaround for simple things) KEC 3067

Testing Project Start with: interface and a chunk of (buggy) code – Implement one function – Start writing tests! Have a “clean” suite that will run for your/others’ code Apply tests to other students’ code and submit bug reports in the repository – Write periodic test reports informing “management” what you’ve done – More info in project-info slides

Testing Project Grading criteria – Effectiveness of your testing approach: coverage, bugs found, depth/interest, originality of ideas! – Quality of test/bug reports Can I figure out how you tested the system? Can I figure out what wasn’t tested? Can I figure out how reliable you think the code is?