cis339week07inclass

cis339week07inclass - OOADDevelopment Methodologies...

Info iconThis preview shows pages 1–9. Sign up to view the full content.

View Full Document Right Arrow Icon
Slide 1 OOAD Development  Methodologies Unified Process The Unified Process is a software analysis and design process  methods, Booch, OOSE (Use-Case), and OMT with ideas  drawn from many other methods and input from many other  parties. It is a component-based, use case driven, architecture  centered, iterative and incremental developmental process  that uses the Unified Modeling Language (UML) to represent  models of the software system to be developed. The Unified  Process describes the different activities in developing a  software system and the different models developed and  evolved during the lifecycle of a system.
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Slide 2 The Unified Process
Background image of page 2
Slide 3 OOAD Development  Methodologies Rational Unified Process (RUP) The RUP is a specific and highly  detailed instance of the Unified  Process. It is a much more involved and  sophisticated process used for  developing very large and complex  systems. www.rational.com/products/rup
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Slide 4 eXtreme Programming (XP) A lightweight methodology for small-to- medium sized teams developing  software in the face of vague or rapidly  changing requirements. (Source:  Jay Packlick   jay.packlick@sabre.com)
Background image of page 4
Slide 5 What is XP? “Extreme Programming is a discipline of software development  based on values of simplicity, communication, feedback, and  courage. It works by bringing the whole team together in the  presence of simple practices, with enough feedback to enable the  team to see where they are and to tune the practices to their unique  situation.”       - Ron Jefferies XP ( extreme Programming ) is a term coined by Kent Beck ( XP  explained - 1999 ) to describe a set of 12 best practices distilled from  the C3 Chrysler payroll project written in SmallTalk - included Ron  Jefferies, Kent Beck  
Background image of page 5

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Slide 6 What is XP? A collection of 12 software engineering “best practices” that  deliver software systems  Quickly With High Quality And with high business value A set of values and principles that drive and unify the  practices An agile / iterative ‘methodology’ that bridges the gap  between CMM concerns and the low level business of writing  high quality code quickly. (CMM – Capability Maturity Model:  http://www.sei.cmu.edu/cmm/cmm.html)  
Background image of page 6
Slide 7 XP - Agile Software Development XP emphasizes High Quality Working Software Customer satisfaction   Minimum investment for maximum, early yield Short  iterations Collaboration, communications, and feedback   Repeatable processes  Simplicity Low cost of change  
Background image of page 7

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Slide 8 XP - Values and principles Communication " Problems with projects can 
Background image of page 8
Image of page 9
This is the end of the preview. Sign up to access the rest of the document.

Page1 / 44

cis339week07inclass - OOADDevelopment Methodologies...

This preview shows document pages 1 - 9. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online