Dilbert Scott Adams. CSc 233 Spring 2012
|
|
- Tiffany Howard
- 5 years ago
- Views:
Transcription
1 Dilbert Scott Adams CSc 233 Spring 2012
2 Dilbert Scott Adams CSc 233 Spring
3 Dilbert Scott Adams CSc 233 Spring
4 prerequisites CSc 233 Spring 2012 I thought we had agreed long ago that the Department Policy was that all instructors would check for the completion of all prerequisites in the prerequisite chain. This may have been requested, but I don't recall it ever becoming policy. I don't check prerequisites. We are a 21st century computer science department at a university with an expensive CMS system. I would think that this is a university-wide problem and requires a university-wide solution that is better than having hundreds of faculty do such busy-work. 4
5 CSc 233 Spring 2012 How hard would it be for CMS to make a second prerequisite check after grades have been submitted but before the semester begins? A few hours work by a talented programmer should suffice, don't you think? A day in the life 5
6 Life Cycle: Chapter 3: Using Life Cycles The way you and the team organize the work of product development. When to define requirements, design, develop, and test, as well as concurrently. There is no one right way it depends. On what? 6
7 What process? Evidence shops that had no well-defined process were unable to deliver on-time with expected features. There is no Best Practice process. Necessary but not necessarily sufficient Every project is different, every team is unique the Project Manager decides what works & what does not. The methodology chosen should include periodic reevaluation and inclusion of practices that fit your project and your team. Ship It! A Practical Guide to Successful Software Projects. Richardson & Gwaltney. Pragmatic Bookshelf,
8 Figure 3.1 Type Serial Iterative Incremental Iterative / Incremental Ad hoc Examples Waterfall, Phase gate Spiral, evolutionary prototyping Design to schedule, staged delivery Agile (such as Scrum, XP) Code & fix Strengths & necessary conditions for success Project Priorities Prognosis for success Manages cost risk. 1. Features set Successful with feedback Known and agreed upon 2. Low defects Well-understood system architecture 3. Time to release Requirements stable over the project Project team stable over the project Manages technical risk 1. Features set Successful assuming the Ever-evolving requirements 2. Low defects finishing parts are 3. Time to release and occur. Manages schedule risk. 1. Time to release Successful Can absorb small requirements 2. Low defects changes but not enough changes that 3. Feature set affect the architecture. Manages both schedule & technical risk 1. Time to release Successful Difficult to do well without a 2. Feature set integrated team. 3. Low defects You guys start coding; 1. Time to release Unsuccessful I ll get the requirements 2. Feature set 3. Low defects 8
9 Serial Figure 3.2 Requirements Analysis Design Code Integration Iterative Requirements Prototype: Analysis, Design, Code Prototype: Analysis, Design, Code Prototype: Analysis, Design, Code Integration Incremental Some Requirements Analysis to choose overall architecture Design, Code, Integrate & Design, Code, Integrate & Final Integration Final Agile Some requirements / Planning Repeat as needed Each timebox results in running tested features. 9
10 Serial Figure 3.2 CSc 233 Spring 2012 Requirements Analysis Design Code Integration Iterative Requirements Prototype: Analysis, Design, Code Prototype: Analysis, Design, Code Prototype: Analysis, Design, Code Integration Incremental Some Requirements Analysis to choose overall architecture Design, Code, Integrate & Design, Code, Integrate & Final Integration Final Agile Some requirements / Planning Repeat as needed Each timebox results in running tested features. 10
11 Serial Figure 3.2 CSc 233 Spring 2012 Requirements Analysis Design Code Integration Iterative Requirements Prototype: Analysis, Design, Code Prototype: Analysis, Design, Code Prototype: Analysis, Design, Code Integration Incremental Some Requirements Analysis to choose overall architecture Design, Code, Integrate & Design, Code, Integrate & Final Integration Final Agile Some requirements / Planning Repeat as needed Each timebox results in running tested features. 11
12 Serial Figure 3.2 CSc 233 Spring 2012 Requirements Analysis Design Code Integration Iterative Requirements Prototype: Analysis, Design, Code Prototype: Analysis, Design, Code Prototype: Analysis, Design, Code Integration Incremental Some Requirements Analysis to choose overall architecture Design, Code, Integrate & Design, Code, Integrate & Final Integration Final Agile Some requirements / Planning Completed features at the end of each iteration Repeat as needed Each timebox results in running tested features. 12
13 Combination: Iterative & Incremental Initial pass at requirements Prototype what we do know about. Get feedback. Select an architecture Fully implement 3 features, integrating as we go. architecture Demo what we have. Keep implementing, integrating as we go. Final test. Feedback needed: To assess remaining project risks To assess project s state To assess how quickly the team can produce working software The more you know, the better you can predict done. 13
14 CSc 233 Spring 2012 Incremental development Scheduling and staging strategy in which the various parts of the system are developed at different times or rates, and integrated as they are completed. It does not imply, require nor preclude iterative development or waterfall development - both of those are rework strategies. The alternative to incremental development is to develop the entire system with a "big bang" integration. 14
15 CSc 233 Spring 2012 Iterative development Rework scheduling strategy in which time is set aside to revise and improve parts of the system. It does not presuppose incremental development, but works very well with it. Typical difference is that the output from an increment is not necessarily subject to further refinement, and its testing or user feedback is not used as input for revising the plans or specifications of the successive increments. The output from an iteration is examined for modification, and especially for revising the targets of the successive iterations. 15
16 Fig 3.7 One Large Project Life Cycle Developer Life Cycle Prototype architecture and select product architecture Design, code, integrate and test features A, B, C: add to smoke tests were makes sense Design, code, integrate and test features D, E, F, G, H More stages of Design, code, integrate and test, including add more smoke tests Initial Definition of Requirements Select test architecture Develop whole product smoke tests Develop first pass of system tests to verify release criteria Develop system tests to test features A, B, C in more depth More iterations of adding more detailed system tests and adding more tests to verify release criteria Final integration Final test er Life Cycle 16
17 Feedback Design Debug Code 17
18 Code & Refactor Loop Start a feature Refactor Code Build at least daily 18
19 Waterfall CSc 233 Spring 2012 Agile 19
20 CSc 233 Spring 2012 Waterfall Project Team Agile Project Team 20
21 CSc 233 Spring 2012 Waterfall Project Scope Change Agile Project No Scope Change 21
22 Architectural Risk Risk is that the architecture will not work for all features. Why would the Waterfall life cycle be the riskiest for managing architectural risks? The only way to really manage architectural risk is to implement something and test it. 22
23 Stuck with a serial lifecycle! Plan to iterate on everything (planning, requirements & prototyping) Prototype and show your customer as much as possible as early as possible. Feedback!!! Integrate testing from the beginning work with the testers. Implement by feature, integrating and testing Documentation? Yes, but it s not the deliverable. 23
24 The author s favorite Life Cycle Agile is her first choice but!! If the customer is not readily available, If the team members are not into collaborating, If the team members are not disciplined, forget it! Regardless, staged delivery is recommended. Finished features get pushed out as soon as possible. 24
Introduction To Software Development CSC Spring 2019 Howard Rosenthal
Introduction To Software Development CSC 295-01 Spring 2019 Howard Rosenthal Course References Materials for this course have utilized materials in the following documents. Additional materials taken from
More informationSoftware Development Process Models
Software Development Process Models From classical notions to more agile approaches th@cs.toronto.edu, BA8134 Code & Fix or Cowboy Coding 1) Write program 2) Test and fix program Problems: program users
More informationThe requirements engineering process
3 rd Stage Lecture time: 8:30-12:30 AM Instructor: Ali Kadhum AL-Quraby Lecture No. : 5 Subject: Software Engineering Class room no.: Department of computer science Process activities The four basic process
More informationUser-Centered Development
Software Lifecycle CS470 User-Centered Development User-centered development refers to a design process for creating a system that meets the needs of the user Users should be included in the design process
More informationHow Can a Tester Cope With the Fast Paced Iterative/Incremental Process?
How Can a Tester Cope With the Fast Paced Iterative/Incremental Process? by Timothy D. Korson Version 7.0814 QualSys Solutions 2009 1 Restricted Use This copyrighted material is provided to attendees of
More informationCS 490 Design Exhibition Fall 2010
CS 490 Design Exhibition Fall 2010 Sanjeev Setia http://www.cs.gmu.edu/~setia/cs490/ Course Objectives Provide students an opportunity to work on a semester long project Project more substantial than a
More informationSystem Development Life Cycle Methods/Approaches/Models
Week 11 System Development Life Cycle Methods/Approaches/Models Approaches to System Development System Development Life Cycle Methods/Approaches/Models Waterfall Model Prototype Model Spiral Model Extreme
More informationSOFTWARE LIFE-CYCLE MODELS 2.1
SOFTWARE LIFE-CYCLE MODELS 2.1 Outline Software development in theory and practice Software life-cycle models Comparison of life-cycle models 2.2 Software Development in Theory Ideally, software is developed
More informationAdministrivia. Added 20 more so far. Software Process. Only one TA so far. CS169 Lecture 2. Start thinking about project proposal
Administrivia Software Process CS169 Lecture 2 Added 20 more so far Will limit enrollment to ~65 students Only one TA so far Start thinking about project proposal Bonus points for proposals that will be
More informationTopic 01. Software Engineering, Web Engineering, agile methodologies.
Topic 01 Software Engineering, Web Engineering, agile methodologies. 1 What is Software Engineering? 2 1 Classic Software Engineering The IEEE definition: Software Engineering is the application of a disciplined,
More informationLecture 7: Software Processes. Refresher: Software Always Evolves
Lecture 7: Software Processes What is a Software Development Process? The Lifecycle of a Software Project Agile vs. Disciplined Some common approaches: RUP, SCRUM, XP, ICONIX, Where UML fits in (next lecture)
More informationObjectives. Connecting with Computer Science 2
Objectives Learn how software engineering is used to create applications Learn some of the different software engineering process models Understand what a design document is and how it should be used during
More informationIncremental development A.Y. 2018/2019
Incremental development A.Y. 2018/2019 Incremental development Interleaves the activities of specification, development, and validation. The system is developed as a series of versions (increments), with
More informationQuality Management Plan (QMP)
Quality Management Plan (QMP) UDM United Direct Marketing Team 09 Fall Semester Chun-Ling Chen Project manager/ Prototyper Chun-Pei Su Lifecycle Planner Shao-yen Cheng System Architect Yuan-Chang Chang
More informationIntroduction to Software Engineering
Chapter 1 Introduction to Software Engineering Content 1. Introduction 2. Components 3. Layered Technologies 4. Generic View of Software Engineering 4. Generic View of Software Engineering 5. Study of
More informationAgile Tester Foundation E-learning Course Outline
Foundation E-learning Course Outline General Description This course provides testers and test managers with an understanding of the fundamentals of testing on agile projects. Attendees will learn how
More informationSystems Analysis & Design
Systems Analysis & Design Dr. Ahmed Lawgali Ahmed.lawgali@uob.edu.ly Slide 1 Systems Analysis & Design Course Textbook: Systems Analysis and Design With UML 2.0 An Object-Oriented Approach, Second Edition
More informationSoftware Life Cycle. Main issues: Discussion of different life cycle models Maintenance or evolution
Software Life Cycle Main issues: Discussion of different life cycle models Maintenance or evolution Introduction software development projects are large and complex a phased approach to control it is necessary
More informationAgile Testing Course: 15 16/11
Agile Testing Dr. Ronen Bar-Nahor ronen@agilesparks.com 1 AgileSparks We help companies improve by Adopting agile principles and practices. We provide training and coaching to all organizational levels,
More informationCS 320 Introduction to Software Engineering Spring February 06, 2017
CS 320 Introduction to Software Engineering Spring 2017 February 06, 2017 Recap: Software development process models Traditional models Waterfall model Iterative and incremental Prototyping Spiral model
More informationCOSC 310: So*ware Engineering. Dr. Bowen Hui University of Bri>sh Columbia Okanagan
COSC 310: So*ware Engineering Dr. Bowen Hui University of Bri>sh Columbia Okanagan 1 Admin A2 is up Don t forget to keep doing peer evalua>ons Deadline can be extended but shortens A3 >meframe Labs This
More informationAgile Accessibility. Presenters: Ensuring accessibility throughout the Agile development process
Agile Accessibility Ensuring accessibility throughout the Agile development process Presenters: Andrew Nielson, CSM, PMP, MPA Ann Marie Davis, CSM, PMP, M. Ed. Cammie Truesdell, M. Ed. Overview What is
More information*ANSWERS * **********************************
CS/183/17/SS07 UNIVERSITY OF SURREY BSc Programmes in Computing Level 1 Examination CS183: Systems Analysis and Design Time allowed: 2 hours Spring Semester 2007 Answer ALL questions in Section A and TWO
More information18-642: Software Development Processes
18-642: Software Development Processes 9/6/2017 Coding Is Essentially 0% of Creating Software http://e.ubmelectronics.com/2013embeddedstudy/index.html 2 Old-School Waterfall Development Cycle Bugs SPECIFY
More informationCONFERENCE PROCEEDINGS QUALITY CONFERENCE. Conference Paper Excerpt from the 28TH ANNUAL SOFTWARE. October 18th 19th, 2010
PACIFIC NW 28TH ANNUAL SOFTWARE QUALITY CONFERENCE October 18th 19th, 2010 Conference Paper Excerpt from the CONFERENCE PROCEEDINGS Permission to copy, without fee, all or part of this material, except
More informationSoftware Process. Software Process
Software Process What is SW process? Definition, Development, Support phases Process models: Waterfall Prototyping Spiral, Incremental & iterative (best practices) UP process model What is it? How does
More informationSOFTWARE LIFE-CYCLE PROCESSES From Waterfall to Extreme Programming
SOFTWARE LIFE-CYCLE PROCESSES From Waterfall to Extreme Programming Slide 1 Lesson Objectives Understand major activities of software projects Understand the place of these in different lifecycle models
More informationSE420 - Software Quality Assurance
SE420 - Software Quality Assurance http://dilbert.com/strips/comic/2006-01-29/ Lecture 3 Unit Testing, Part-2 January 21, 2019 Sam Siewert Reminders Assignment #2 Posted Thursday [Unit Re-Use] Explore
More informationTesting in the Agile World
Testing in the Agile World John Fodeh Solution Architect, Global Testing Practice 2008 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. Outline
More informationFoundation Level Syllabus Usability Tester Sample Exam Answers
Foundation Level Syllabus Usability Tester Sample Exam s Version 2017 Provided by German Testing Board Copyright Notice This document may be copied in its entirety, or extracts made, if the source is acknowledged.
More informationCS487 Midterm Exam Summer 2005
1. (4 Points) How does software differ from the artifacts produced by other engineering disciplines? 2. (10 Points) The waterfall model is appropriate for projects with what Characteristics? Page 1 of
More informationDSDM Agile Professional Candidate Guidelines October I do it right
DSDM Agile Professional Candidate Guidelines October 2016 I do it right 1 INTRODUCTION 3 2 DSDM AGILE PROFESSIONAL CERTIFICATION I do it right 3 2.1 General 3 2.2 DSDM Version and Examinable Topics 3 2.3
More informationTesting in Agile Software Development
Testing in Agile Software Development T 76.5613, Software Testing and Quality Assurance Slides by Juha Itkonen Lecture delivered by 4.10.2006 V-model of testing Benefits of the V-model Intuitive and easy
More informationQuality Management Plan (QMP)
Quality Management Plan (QMP) UDM United Direct Marketing Team 09 Chun-Ling Chen Project manager/ Prototyper Chun-Pei Su Lifecycle Planner/ Feasibility Analyst Shao-yen Cheng System Architect Yuan-Chang
More informationSoftware Development Methodologies
Software Development Methodologies Lecturer: Raman Ramsin Lecture 8 Agile Methodologies: XP 1 extreme Programming (XP) Developed by Beck in 1996. The first authentic XP book appeared in 1999, with a revised
More informationCertifiedAT - Version: 1. ISTQB Certified Agile Tester Foundation Level Extension
CertifiedAT - Version: 1 ISTQB Certified Agile Tester Foundation Level Extension ISTQB Certified Agile Tester Foundation Level Extension CertifiedAT - Version: 1 3 days Course Description: We are facing
More informationSample Exam. Certified Tester Foundation Level
Sample Exam Certified Tester Foundation Level Answer Table ASTQB Created - 2018 American Stware Testing Qualifications Board Copyright Notice This document may be copied in its entirety, or extracts made,
More informationIntroduction - SENG 330. Object-Oriented Analysis and Design
Introduction - SENG 330 Object-Oriented Analysis and Design SENG 330 Fall 2006 Instructor: Alex Thomo Email: thomo@cs.uvic.ca Office hours: Office Hours: TWF 12:30-1:30 p.m. Location: ECS 556 Objective:
More informationSoftware Engineering Lifecycles. Controlling Complexity
Software Engineering Lifecycles Class url:http://laser.cs.umass.edu/courses/cs320.spring11/ Controlling Complexity Separation of Concerns Planning Ahead Do a little work now to make later work easier The
More informationTesting in an Agile Environment Understanding Testing role and techniques in an Agile development environment. Just enough, just in time!
Testing in an Agile Environment Understanding Testing role and techniques in an Agile development environment. Just enough, just in time! Today s Topics How the Tester s Role Changes in Agile Testing in
More informationAdopting Agile Practices
Adopting Agile Practices Ian Charlton Managing Consultant ReleasePoint Software Testing Solutions ANZTB SIGIST (Perth) 30 November 2010 Tonight s Agenda What is Agile? Why is Agile Important to Testers?
More informationAGILE. Getting Started on Your Team. Davisbase. Copyright 2011 Davisbase LLC. Licensed for Classroom Use to ASPE for Webinar Use Only
AGILE Getting Started on Your Team Copyright 2011 LLC. Licensed for Classroom Use to ASPE for Webinar Use Only INTRO AND AGENDA Your Instructor: Christy Clement Agile Trainer and Coach Agenda: Picking
More informationFoundation Level Syllabus Usability Tester Sample Exam
Foundation Level Syllabus Usability Tester Sample Exam Version 2017 Provided by German Testing Board Copyright Notice This document may be copied in its entirety, or extracts made, if the source is acknowledged.
More informationReducing the costs of rework. Coping with change. Software prototyping. Ways to Cope with change. Benefits of prototyping
Coping with change Change is inevitable in all large software projects. Business changes lead to new and changed system requirements New technologies open up new possibilities for improving implementations
More informationSoftware processes. Objectives. Contents
2 Software processes Objectives The objective of this chapter is to introduce you to the idea of a software process a coherent set of activities for software production. When you have read this chapter
More informationSoftware Testing Interview Question and Answer
Software Testing Interview Question and Answer What is Software Testing? A process of analyzing a software item to detect the differences between existing and required conditions (i.e., defects) and to
More informationTesting Agile Projects Stuart Reid
ing Agile Projects Stuart Reid ing Solutions Group 117-119 Houndsditch London EC3A 7BT UK sreid@ing-solutions.com www.ing-solutions.com Stuart Reid, 2011 Scope Agile Manifesto and Principles An Agile Development
More informationCreating an Intranet using Lotus Web Content Management. Part 2 Project Planning
Creating an Intranet using Lotus Web Content Management Introduction Part 2 Project Planning Many projects have failed due to poor project planning. The following article gives an overview of the typical
More informationExam Questions
Exam Questions 70-498 Delivering Continuous Value with Visual Studio 2012 Application Lifecycle Management https://www.2passeasy.com/dumps/70-498/ 1. You are the application architect on your team. You
More informationDESIGN. (Chapter 04)
DESIGN (Chapter 04) THE PROCESS OF INTERACTION DESIGN Overview What is involved in Interaction Design? Importance of involving users Degrees of user involvement What is a user-centered approach? Four basic
More informationQuality Management Plan (QMP)
Quality Management Plan for LEMA Family Accountability System Version 3.3 Quality Management Plan (QMP) PROJECT TITLE LEMA FAMILY ACCOUNTABILITY SYSTEM TEAM NO #04 TEAM MEMBERS & ROLES NAME ROLES Teawon
More informationSoftware Verification and Validation (VIMMD052) Introduction. Istvan Majzik Budapest University of Technology and Economics
Software Verification and Validation (VIMMD052) Introduction Istvan Majzik majzik@mit.bme.hu Budapest University of Technology and Economics Dept. of Measurement and Information s Budapest University of
More informationImproved Database Development using SQL Compare
Improved Database Development using SQL Compare By David Atkinson and Brian Harris, Red Gate Software. October 2007 Introduction This white paper surveys several different methodologies of database development,
More informationDesigned in collaboration with Infosys Limited
Proposal for Introduction of New Industry Course in Engineering Curriculum Agile Software Development - Deliver Software Better Everyday Designed in collaboration with Infosys Limited Version 1-2016 Contents
More informationExtreme programming XP 6
Extreme programming XP 6 Planning Game 3 Planning Game Independent: Stories should be as independent as possible. When thinking of independence it is often easier to think of order independent. In other
More informationCIS 3730 FALL 2008 Database Management System Project
CIS 3730 FALL 2008 Database Management System Project Project Grade (40 points) The project will be graded at the end of the course with the following breakdown: Initial Project Proposal - 4 points Weekly
More informationBridge Course On Software Testing
G. PULLAIAH COLLEGE OF ENGINEERING AND TECHNOLOGY Accredited by NAAC with A Grade of UGC, Approved by AICTE, New Delhi Permanently Affiliated to JNTUA, Ananthapuramu (Recognized by UGC under 2(f) and 12(B)
More informationPrevious Capstone Project
Capstone Projects RoviSys (http://www.rovisys.com) located in Aurora Ohio, has 4 project that we will help them develop. In the process you will have an opportunity to experience how software is developed
More informationRequirements and User-Centered Design in an Agile Context
Requirements and User-Centered Design in an Agile Context The Volvo Group Business Areas AB Volvo Volvo Trucks Renault Trucks Mack Trucks Nissan Diesel Buses Construction Equipment Volvo Penta Volvo Aero
More informationProcess Models. Projects Process. Common Process Models. Typical Student Process Model. Waterfall Model
Process Models A process model specifies a general process, usually as a set of stages This model will be suitable for a class of projects i.e. a model provides generic structure of the process that can
More informationModern Software Engineering Methodologies Meet Data Warehouse Design: 4WD
Modern Software Engineering Methodologies Meet Data Warehouse Design: 4WD Matteo Golfarelli Stefano Rizzi Elisa Turricchia University of Bologna - Italy 13th International Conference on Data Warehousing
More informationSoftware Processes. Ian Sommerville 2006 Software Engineering, 8th edition. Chapter 4 Slide 1
Software Processes Ian Sommerville 2006 Software Engineering, 8th edition. Chapter 4 Slide 1 Objectives To introduce software process models To describe three generic process models and when they may be
More informationAdvanced Software Engineering: Software Testing
Advanced Software Engineering: Software Testing COMP 3705(L4) Sada Narayanappa Anneliese Andrews Thomas Thelin Carina Andersson Web: http://www.megadatasys.com Assisted with templates News & Project News
More informationProcess of Interaction Design and Design Languages
Process of Interaction Design and Design Languages Process of Interaction Design This week, we will explore how we can design and build interactive products What is different in interaction design compared
More informationAnalysis and Design with UML
Analysis and Design with UML Page 1 Agenda Benefits of Visual Modeling History of the UML Visual Modeling with UML The Rational Iterative Development Process Page 2 What is Visual Modeling? Item Order
More informationl e a n Lean Software Development software development Faster Better Cheaper
software development Lean Software Development Faster Better Cheaper mary@poppendieck.com Mary Poppendieck www.poppendieck.com Characteristics of Lean Companies: 1. They don t call themselves Lean The
More informationTest Automation Strategies in Continuous Delivery. Nandan Shinde Test Automation Architect (Tech CoE) Cognizant Technology Solutions
Test Automation Strategies in Continuous Delivery Nandan Shinde Test Automation Architect (Tech CoE) Cognizant Technology Solutions The world of application is going through a monumental shift.. Evolving
More informationDevelopment Processes Agile Adaptive Planning. Stefan Sobek
Development Processes Agile Adaptive Planning Stefan Sobek Agile Planning Process Adaptive Planning In agile projects frequently issues and changes will be discovered. Go into these projects with expectations
More informationAgile Software Development Agile UX Work. Kati Kuusinen TUT / Pervasive / IHTE
Agile Software Development Agile UX Work Kati Kuusinen Researcher @ TUT / Pervasive / IHTE kati.kuusinen@tut.fi Contents 1. Introduction / Motivation 2. Agile software development 3. User experience work
More informationCTAL. ISTQB Advanced Level.
ASTQB CTAL ISTQB Advanced Level TYPE: DEMO http://www.examskey.com/ctal.html Examskey ASTQB CTAL exam demo product is here for you to test the quality of the product. This ASTQB CTAL demo also ensures
More informationThe Agile Unified Process (AUP)
The Agile Unified Process (AUP) Scott W. Ambler Senior Consultant, Ambysoft Inc. www.ambysoft.com/scottambler.html Copyright 2001-2005 Scott W. Ambler 1 Scott W. Ambler Methodologist, Author, Consultant
More informationExamples. Object Orientated Analysis and Design. Benjamin Kenwright
Examples Object Orientated Analysis and Design Benjamin Kenwright Outline Revision Questions Group Project Review Deliverables Example System Problem Case Studey Group Project Case-Study Example Vision
More informationGoing Agile. UK TMF April 2011
Going Agile (without tears or lactic acid) UK TMF April 2011 Mark Crowther Empirical Pragmatic Tester About this slide pack. This slide pack was presented at the UK Test Management Forum. It discusses
More information((MARKS)) (1/2/3...) ((QUESTIO N)) ((OPTION_ A)) What is Software?
SNJB s Late Sau. KBJ COE, Chandwad Department of Computer Engg PART I : Software development process, language and software development environments, language and software design methods, languages and
More informationSecond. Incremental development model
3 rd Stage Lecture time: 8:30 AM-2:30 PM Instructor: Ali Kadhum AL-Quraby Lecture No. : 4 Subject: Software Engineering Class room no.: Department of computer science Second. Incremental development model
More informationXP: Planning, coding and testing. Planning. Release planning. Release Planning. User stories. Release planning Step 1.
XP: Planning, coding and testing Annika Silvervarg Planning XP planning addresses two key questions in software development: predicting what will be accomplished by the due date determining what to do
More informationSoftware Testing part II (white box) Lecturer: Giuseppe Santucci
Software Testing part II (white box) Lecturer: Giuseppe Santucci 4. White box testing White-box (or Glass-box) testing: general characteristics Statement coverage Decision coverage Condition coverage Decision
More informationProject Plan. SISCalendar. for. Prepared by Zach Masiello. Ethan Mick Michael Caputo Shawn Thompson Organization: SIS.io
Project Plan for SISCalendar Prepared by Zach Masiello Ethan Mick Michael Caputo Shawn Thompson Organization: SIS.io Revision History Name Date Reason For Changes Version Initial 10/1/13 First version
More informationKanban One-Day Workshop
Kanban One-Day Workshop Copyright Net Objectives, Inc. All Rights Reserved 2 Copyright Net Objectives, Inc. All Rights Reserved 3 Lean for Executives Product Portfolio Management Business Product Owner
More informationThis course includes 14 lessons and 5 Course Activities. Each lesson contains one or more Lesson Activities. The lessons cover the following topics:
Syllabus Computer Science 1B Overview This one-semester course is intended as a practical, hands-on guide to help you understand various phases of the Software Development Life Cycle (SDLC). This course
More informationShift Left Testing: are you ready? Live Webinar, Sept 19
Shift Left Testing: are you ready? Live Webinar, Sept 19 Guy Arieli CTO, Experitest 01 What exactly is Shift Left? Agenda 02 03 How Shift Left affects application development & testing organizational structures
More informationBDSA Introduction to OOAD. Jakob E. Bardram
BDSA Introduction to OOAD Jakob E. Bardram Programming is Fun Developing Quality Software is Hard. Craig Larman in [OOAD] book 2 Object-Oriented Analysis & Design (OOAD) This Lecture Unified Modeling Language
More informationAgile Manifesto & XP. Topics. Rapid software development. Agile methods. Chapter ) What is Agile trying to do?
Topics 1) What is trying to do? Manifesto & XP Chapter 3.1-3.3 2) How to choose plan-driven vs? 3) What practices go into (XP) development? 4) How to write tests while writing new code? CMPT 276 Dr. B.
More informationmywbut.com Software Life Cycle Model
Software Life Cycle Model 1 Basics of Software Life Cycle and Waterfall Model 2 Specific Instructional Objectives At the end of this lesson the student will be able to: Explain what is a life cycle model.
More informationBest Practices for Collecting User Requirements
Federal GIS Conference February 9 10, 2015 Washington, DC Best Practices for Collecting User Requirements Gerry Clancy Glenn Berger Requirements Provide direction for program success Why Requirements are
More informationIntroduction to Software Engineering
Introduction to Software Engineering Gérald Monard Ecole GDR CORREL - April 16, 2013 www.monard.info Bibliography Software Engineering, 9th ed. (I. Sommerville, 2010, Pearson) Conduite de projets informatiques,
More informationI am Stephen LeTourneau from Sandia National Laboratories Sandia s National Security Missions include: Nuclear Weapons Defense Systems & Assessments
I am Stephen LeTourneau from Sandia National Laboratories Sandia s National Security Missions include: Nuclear Weapons Defense Systems & Assessments Energy, Climate & Infrastructure Security International,
More informationSenior Design - Spring 2014 EE/CpE 424. Class 2 3/4/14
- Spring 2014 EE/CpE 424 Class 2 3/4/14 Outline Spring 2014 tasks Reimbursement Upcoming priorities Tasks Spring 14 build, debug, test Publish interim project report Develop final report Submit final report
More informationThe Design Space of Software Development Methodologies
The Design Space of Software Development Methodologies Kadie Clancy, CS2310 Term Project I. INTRODUCTION The success of a software development project depends on the underlying framework used to plan and
More informationThis tutorial also elaborates on other related methodologies like Agile, RAD and Prototyping.
i About the Tutorial SDLC stands for Software Development Life Cycle. SDLC is a process that consists of a series of planned activities to develop or alter the Software Products. This tutorial will give
More informationA CONFUSED TESTER IN AGILE WORLD
A CONFUSED TESTER IN AGILE WORLD QA A LIABILITY OR AN ASSET THIS IS A WORK OF FACTS & FINDINGS BASED ON TRUE STORIES OF ONE & MANY TESTERS!! J Presented By Ashish Kumar, A STORY OF TESTING. WHAT S AHEAD
More informationSoftware Quality Assurance
Arizona Information Technology Skills Training Initiative (AITSTI) Software Quality Assurance Bob Fowler Oris Friesen January 14, 2009 Table of Contents Introduction Software Development Software Quality
More informationGradational conception in Cleanroom Software Development
Gradational conception in Cleanroom Software Development Anshu Sharma 1 and Shilpa Sharma 2 1 DAV Institute of Engineering and Technology, Kabir Nagar, Jalandhar, India 2 Lovely Professional University,
More informationDisciplined Agile Delivery The Foundation for Scaling Agile
Disciplined Agile Delivery The Foundation for Scaling Agile Scott W. Ambler Senior Consulting Partner scott [at] scottambler.com @scottwambler Scott Ambler + Associates 1 Let s explore a few important
More informationThree Ways to Reduce Product Delivery Risk and to Lower Software Lifecycle Costs
Three Ways to Reduce Product Delivery Risk and to Lower Software Lifecycle Costs Jeffrey Fortin Product Manager for VectorCAST V2.2 2017-10-02 Why does quality matter? Two Examples 2 Why does quality matter?
More informationIntroduction to User Stories. CSCI 5828: Foundations of Software Engineering Lecture 05 09/09/2014
Introduction to User Stories CSCI 5828: Foundations of Software Engineering Lecture 05 09/09/2014 1 Goals Present an introduction to the topic of user stories concepts and terminology benefits and limitations
More informationSoftware Engineering
CSC40232: SOFTWARE ENGINEERING Professor: Jane Cleland Huang : Introduction Wednesday, January 18 th sarec.nd.edu/courses/se2017 Department of Computer Science and Engineering Software Engineering Software
More informationCertified Tester Foundation Level(CTFL)
Certified Tester Foundation Level(CTFL) ISTQB : International Software Testing Qualifications Board Heading: The International Software Testing Qualifications Board (ISTQB) is an internationally recognized
More informationRequirement Engineering within an Agile Environment BY KEJI GIWA. Digital Bananas Technology
Requirement Engineering within an Agile Environment BY KEJI GIWA HLR Workshop Requirement Catalogue Product Planning Sprint Planning Meeting Keyscreens Use Case / Epic Stories Implement Wireframes DBT
More informationSystems Analysis and Design
Systems Analysis and Design Michael Brydon Summer 2003 Slide 1 Introduction to the Course Course structure Lectures: material from the Dennis text Labs: in-lab assignments, demonstrations, and consulting
More information