Outline Your one-minute feedback from last week Peer reviews

Slides:



Advertisements
Similar presentations
29 September Interactions  There is no “right answer”  Typically people and product are fixed  … can adapt process  (which is where we will.
Advertisements

1 In-Process Metrics for Software Testing Kan Ch 10 Steve Chenoweth, RHIT Left – In materials testing, the goal always is to break it! That’s how you know.
Sixth Hour Lecture 10:30 – 11:20 am, September 9 Framework for a Software Management Process – Artifacts of the Process (Part II, Chapter 6 of Royce’ book)
Financial Systems Needs Assessment Project Update Monthly Research Administrators Meeting March 11, 2010.
Software Engineering.
CSE 784 Software Studio Phil Pratt-Szeliga Fall 2010 Slides Derived From: Dr. Fawcett.
Student Startup Sequence Verify network connection Rotate to Landscape mode Start Presenter 2.0 Maximize Application Role->Student Connect->Classroom 2.
Outline (Mis)communicating expectations Schedule of class-related deliverables Specific final release deliverables Your questions Intellectual activity:
Requirements - Why What and How? Sriram Mohan. Outline Why ? What ? How ?
29 Jul 2005CSE403, Summer'05 Student Startup Sequence Verify network connection Rotate to Landscape mode Start Presenter 2.0 Maximize Application Role->Student.
Administrivia Lifecycle Architecture (LCA) group assignment will go out later today. Informal feedback meetings with LCO groups EasyShare: Mon, 2:45pm-3:15pm,
1 Jul 2005CSE403, Summer'05, Section 02 Section 02: Life Cycle Architecture Review Valentin Razmov.
15 Jul 2005CSE403, Summer'05, Lecture 10 Lecture 10: Incremental Releases Valentin Razmov.
CSE Senior Design II Staged Delivery Instructor: Mike O’Dell.
Xtreme Programming. Software Life Cycle The activities that take place between the time software program is first conceived and the time it is finally.
Outline Your questions Upcoming milestone deliverables Testing in the project lifecycle Analyzing scenarios using inference diagrams Mistakes to avoid.
Readiness Index – Is your application ready for Production? Jeff Tatelman SQuAD October 2008.
1 Walk-in slide. 2 How to Manage a System Upgrade The Good, The Bad and The Ugly of Conversions David Cervelli Managing Consultant April 25, 2006.
COLLABORATION MODULE #3 Planning Good Meetings An online module developed by Pivot Learning Partners for the West Contra Costa Unified School District.
Introduction to RUP Spring Sharif Univ. of Tech.2 Outlines What is RUP? RUP Phases –Inception –Elaboration –Construction –Transition.
1 CSE 403 Software Lifecycle Models Reading: Rapid Development Ch. 7, 25 (further reading: Ch. 21, 35, 36, 20) These lecture slides are copyright (C) Marty.
Continuous Integration and Testing
© Blackboard, Inc. All rights reserved. Back to the Feature: An Agile, User-centric Software Development Lifecycle Cindy Barry Senior Product Manager Martha.
Demo Guidelines Lesson 9. Modules 9.1Demo Video Guidelines 9.2Begin Filming Pitch Video 9.3Continue working on prototype.
22 Jul 2005CSE403, Summer'05, Lecture 12 Lecture 12: Scheduling, Estimation, and Prioritization (Part II) Valentin Razmov.
Distributed Software Development
Capability Maturity Models Software Engineering Institute (supported by DoD) The problems of software development are mainly caused by poor process management.
Writing Functional Specifications
Webster Visualize Webster Financial Team Visual Scrumware Joe Andrusyszyn Mark Bryant Brian Hannan Robert Songer.
Object-oriented Analysis and Design Stages in a Software Project Requirements Writing Analysis Design Implementation System Integration and Testing Maintenance.
1 CSE 403 Software Requirements Reading: Pragmatic Programmer Ch. 7: Before the Project These lecture slides are copyright (C) Marty Stepp, 2007, with.
Video Editing Lesson 11. Modules 11.1Review deliverables 11.2Edit videos 11.3Put together business plan 11.4Continue working on prototype.
1 Dr. Ralph R. Young Director of Software Engineering PRC, Inc. (703) DOORS USER GROUP CONFERENCE Reston, VA September 17,
13-January-2003cse LifeCycle © 2003 University of Washington1 Lifecycle CSE 403, Winter 2003 Software Engineering
Methodologies. Contents Waterfall Model Evolutionary Models Incremental Development.
T Project Review WellIT PP Iteration
1 김 수 동 Dept. of Computer Science Soongsil University Tel Fax
Requirements Gathering: Pragmatic Ways to Meet Real Customer Needs Requirements Gathering: Pragmatic Ways to Meet Real Customer Needs PMI CVC Professional.
September 30, 2010COMS W41561 COMS W4156: Advanced Software Engineering Prof. Gail Kaiser
User Feedback Lesson 10. Modules 10.1Begin filming demo video 10.2Continue working on pitch video 10.3Continue working on prototype.
Software Testing Process
Teaching slides Chapter 9. Chapter 9 Software Testing (Verification & Validation) Introduction Software testing & software engineering methodologies Introduction.
T Iteration Demo Tikkaajat [PP] Iteration
30 Jun 2006CSE403, Summer'06, Section02 Administrivia Individual assignment #1 will go out later today. Upcoming holiday schedules: Mon / Wed? Informal.
Deliverables: Beta Release Installation package Application sources and binaries One-step build for all sources Latest specification & design documents.
Topic:- At the end we will be able to explain:- Why it is called Meta Model ?? Spiral Model Its Advantages & Disadvantages… Phases of Spiral Model...
Starter To complement our notes and learning from last lesson (Topic 10 Introducing Large ICT Systems: Features of Large ICT Systems), fold your piece.
Deliverables: Zero-Feature Release Build process, installation process, code repository, automated testing framework, bug tracking system Maybe no tests.
Refine Preliminary Design. Schedule Week 9 - Refine Preliminary Design Week 10 – Test/Evaluate Design Week 11 – Continue Final Design, Fabrication Updates.
Slide 3.1 © The McGraw-Hill Companies, 2002 SOFTWARE LIFE-CYCLE MODELS.
27 Jul 2006CSE403, Summer'06, Lecture 15 Midterm Exam Statistics Other statistics: Average: 40.6 Median: 42.3 Std Dev: 6.2 Max: 46.5 Min: 28 Easiest Problems:
Outline Your one-minute feedback from last week
Customer Experience: Create a digitally led customer experience
Project Breakdowns HCDE 492/592 Winter 2014.
SOFTWARE ENGINEERING - SOFTWARE LIFECYCLE MODELS
Testing Process Roman Yagodka ISS Test Leader.
Quality Assurance: Early Work Items
Lecture 11: Scheduling, Estimation, and Prioritization
An Intro to ALM Using TFS and Visual Studio for Source Control, Build Automation, Continuous Integration and Deployments.
WEBINAR: Becoming Agile In Software Testing: The Government Edition
The Game Development Process
Strategies For Software Test Documentation
Section 01: Life Cycle Objectives Review
Valentin Razmov Dept. of Computer Science & Engineering
Lecture 15: Scheduling, Estimation, and Prioritization (Part II)
Onboarding and Training
Early Prototype Team D.
PRESENTED BY P.SANDEEP MSc,MTech
Section 01: Life Cycle Objectives Review
Presentation transcript:

Outline Your one-minute feedback from last week Peer reviews Topics of main interest: prototyping, testing Peer reviews How was it? Can we improve the process? Informal team discussions after milestone #1 How industry projects move forward depending on the outcome of presentations / pitches Your questions Upcoming milestone deliverables Prioritization of features Testing in the project lifecycle

Your Questions On class? On project? On homework? On material we’ve discussed? Other?

Next Milestone – Preliminary Release Deliverables: Application sources and binaries One-step build for all sources Latest spec & design documents Release notes Instructions on how to run a (small) demo of your app Known issues with prioritization Automated (unit and acceptance) tests Up-to-date schedule We highly recommend: Have a testing framework established Albeit with few tests present yet Start working on an installer

Prioritizing Features; Testing in the Project Lifecycle CSE403 Section 5: Prioritizing Features; Testing in the Project Lifecycle Valentin Razmov, CSE403, Sp'05

Prioritizing Assume you have 100 features to implement. What are the main factors to consider when prioritizing features for your project? How do you put them together to arrive at a priority level for a given feature?

Testing Testing helps to establish if _____________________________________, because ______________________________. Testing begins (when?)

Testing How much does each dollar invested in early defect tracking save the project later on? (A) $0.25 (B) $1.00 (C) $7.00 (D) $50.00 What does that imply for how much emphasis you need to put on testing?

Favorite Related Quotes “Doing things right is not as important as doing the right things.” (Drucker's Dictum) "Verification == Did we build the product right? Validation == Did we build the right product?" (Barry Boehm) “Doing things at the last minute is much more expensive than just before the last minute.” (Randy Pausch) “If you haven't got time to do it right, you don't have time to do it wrong.” “Good judgement comes from experience. Experience comes from bad judgement.” “Failing to plan is planning to fail.” “Work expands so as to fill the time available for its completion.” (Parkinson's Law, 1957)