Systems Development Methodologies 3rd semester Autum 2014.

Slides:



Advertisements
Similar presentations
AGILE DEVELOPMENT Outlines : Quick Look of agile development Agility
Advertisements

SOFTWARE DEVELOPMENT METHODOLOGIES Methodologies Waterfall Prototype model Incremental Iterative V-Model Spiral Scrum Cleanroom RAD DSDM RUP.
Principles of Agile management of software development project 28 November 2014.
NAUG NAUG Knowledge Evening – th February 2007.
 User assignments (product owner)  ‘circle’  1 st sprint: ◦ Scrum Boards (informative workspace)  Product -, release -, sprint -, defect backlog 
© ThoughtWorks, 2008 Improving Productivity and Quality With Agile Patrick Kua.
1 Software Testing and Quality Assurance Lecture 34 – SWE 205 Course Objective: Basics of Programming Languages & Software Construction Techniques.
Slide 1 Requirements Wrap-up (Chapter 31 of requirements text) and Interaction Design: Introduction (Chapters 1 of Interaction Design text) CSSE 371 Software.
Computer Engineering 203 R Smith Agile Development 1/ Agile Methods What are Agile Methods? – Extreme Programming is the best known example – SCRUM.
Programming with eyes wide open. Your host today Subby Angelov Team
Software SYSTEMS DEVELOPMENT
Agile Methodologies for Project Management By – Komal Mehta.
ITEC 370 Lecture 27 Life-cycles(3). Life-cycles Review Questions? F give update on project (demo optional) Case study –Actual focus of project (long/short.
A Partner in service to maximize value on your Microsoft Assets AFFLUENT GLOBAL SERVICE – Corporate.
Agile Software Development What is Agile? And How are we implementing Agile?
Chapter 3 – Agile Software Development 1Chapter 3 Agile software development.
Method comparison: for Situational Method Engineering Mohssen Ali.
Agile Software Development Brian Link
Copyright 2011 Agile Foundation Training, Corporation Agile Foundation Training Presented by: Certified Scrum Professional Ken Ward
Chapter 5 Software Process Models. Problems with “Traditional” Processes 1.Focused on and oriented towards “large projects” and lengthy development time.
Sofia Bulgaria Summer School IST eXPERT: Best Practice on e-Project Development 30 June - 2 July 2003 eXtreme programming.
Figures – Chapter 3. Figure 3.1 The principles of agile methods PrincipleDescription Customer involvementCustomers should be closely involved throughout.
One XP Experience: Introducing Agile (XP) Software Development into a Culture that is Willing but not Ready Joe Bergin * Fred Grossman * David Leip **
An Automated Approach for Acceptance Web Test Case Modeling and Executing XP, 蔡侑儒 Felipe M. Besson, Delano M. Beder, and Marcos L. Chaim.
[CS-225: Software Engineering] Course Guide Fatima Khan Prince Sultan University, College for Women.
Creating Interactive Course Assignment Pages The OSU Libraries ICAP Project Coalition for Networked Information Fall 2007 Task Force Meeting Kim Griggs,
Computer Science and Software Engineering© 2014 Project Lead The Way, Inc. Software Design Process.
Goal-Setting Health Miss Kilker.
CS CS 5150 Software Engineering Lecture 2 Software Processes 1.
CS3100 Software Project Management Agile Approaches.
Extreme Programming (XP) XP is an agile methodology: –aims to be responsive to change Theme running through XP is the importance of communication –amongst.
When you are Agile you get Lean How Agile reduces waste in software develpment.
Test Driven Development Daniel Brown dxb17u. Introduction Originates from Extreme Programming (XP) Proposed by Kent Beck in Test Driven Development.
1 Presentation Title Test-driven development (TDD) Overview David Wu.
Lecture 3 – Agile Approach
Extreme programming (XP) Variant of agile Takes commonsense practices to extreme levels © 2012 by Václav Rajlich1.
Agile Methods Presentation By: Jason Abbett. Definition A process to rapidly develop software Many kinds of agile methods but few are practiced.
Extreme Programming. Extreme Programming (XP) Formulated in 1999 by Kent Beck, Ward Cunningham and Ron Jeffries Agile software development methodology.
Intelligent Testing, Improvement and AssuranceSlide 1 Agile Techniques: Which ones really work? Paul Gerrard
Chapter 10 Information Systems Development. Learning Objectives Upon successful completion of this chapter, you will be able to: Explain the overall process.
Intelligence and Information Systems 1 3/17/2004 © 2004 Raytheon Company USC/CSE Executive Workshop on Agile Experiences March 17, 2004 A Raytheon Agile.
It’s Agile …. like! A Corkman’s introduction to Agile software delivery.
Engineering Practices Necessary for Scrum andrew fuqua enterprise agile coach LeadingAgile, LLC
Agile Development Chapter 10 - part 2. Agile Philosophy  A guiding philosophy and set of guidelines for : developing information systems in an unknown,
Extreme Programming מתודולוגיה לפיתוח פרויקטי תוכנה.
Steve Lundquist, PMP, M.Sc..  As a PMP certified program manager, there are numerous tools, processes, methodologies, and tricks that are available to.
Software Quality Assurance Chip Ene, February 14, 2015.
Agile = regular iterations, releases time-boxed incremental regular heartbeat streamlined collaboration co-located team on-site customer face-face communication.
Software Development. The Software Life Cycle Encompasses all activities from initial analysis until obsolescence Analysis of problem or request Analysis.
Presented By : Prima Business Solutions. Agile Software Development Process.
Agile Gintarė Bernotaitytė © 2013.
Project Management Software development models & methodologies
Chapter 5 Agile Development Moonzoo Kim KAIST
Agile Training for Students
Introduction to Agile Software Development
Software Development methodologies
ISCOM 472 Help Bcome Exceptional / iscom472.com
Information Technology Project Management – Fifth Edition
Scaled Agile Requirements: What, When & How
Waterfall and Agile Quality Techniques
ISCOM 472 Enthusiastic Study/snaptutorial.com
Johanna Rothman Create Technical Excellence Chapter 9
Lecture 2 Revision of Models of a Software Process
Agile Process: Overview
Chapt 2 Iterative Evolutionary Agile.
Test Driven Development
Agile Frameworks - Scaling Agile for the Large Enterprise
Introducing ISTQB Agile Foundation Extending the ISTQB Program’s Support Further Presented by Rex Black, CTAL Copyright © 2014 ASTQB 1.
Chapter 5: New and Emerging Process Methodologies
International Institute of Business Analysis
Presentation transcript:

Systems Development Methodologies 3rd semester Autum 2014

Agenda for week 1 Curriculum Be the worst Quality – An agile point of view. Systems development Quality o Product o Process

‘Be the worst’ Be the worst of the people you are surrounded by or “surrond yourself with really greast people” Be a student and have an open mind Connect with experts Immerse yourself “ agile is about learning. For every skill you master, there’s a new one to start learning”:

Quality – An agile point of view What is quality Waste in Software – bugs. – Usability issues – Unused features. Agile approach to improve Quality: - Short Release Cykles - Test-Driven Development (TDD) - Acceptance test driven development (ATDD) - Customer involvement (XP)

curriculum System architecture Experiments Quality in product and process Project management Modern methodologies (agile) Internal exam after 4 th semester based on a project Make the experimentproject in the middel of this semester

Quality: Usability Ten usability heuristics Its about recognizing usability principles (the “heuristics”). We are taking about 10 principles. o Read the article o assignment

Quality: Usability Heuristic evaluation o Read the article o assignment

quality Se Sommerville chapter 24 on my website

Process Improvement Se sommerville chapter 26 on my website

Quality: an agile point of view Quality is a shared underlying theme guiding each and every practice and value used by an agile team The process of increasing quality is an exercise in ‘eliminating waste’ (borrowed from lean manufacturing which talks about all the things preventing a team from reaching its goal)

Quality: an agile point of view Waste in software: o Bugs o Usability issues o Unused features

Quality: an agile point of view Agile approach for improving quality: o Short release cycles o Test-driven development o Acceptance test-driven development o On-site customers ‘the only way to go fast is working in high quality’