IS0514 Lecture - Week 2 Best Practice Development Methodology.

Slides:



Advertisements
Similar presentations
Unified process(UP) UP is an OO system development methodology offered by Rational(Rational Rose) s/w, now a part of IBM Developed by Booach,Rambaugh,Jacobson--
Advertisements

ARCH-05 Application Prophecy UML 101 Peter Varhol Principal Product Manager.
CS487 Software Engineering Omar Aldawud
Arlow and Neustadt ch.21 What is the unified process? People are more important than any process. Good people with a good process will outperform good.
IS0514Slide 1 IS0514 Lecture Week 4 Use Case Modelling (2)
Development Processes UML just is a modeling technique, yet for using it we need to know: »what do we model in an analysis model? »what do we model in.
Slide 1 Systems Analysis & Design CS183 Spring Semester 2008 Dr. Jonathan Y. Clark Course Website:
03/12/2001 © Bennett, McRobb and Farmer Avoiding the Problems Based on Chapter 3 of Bennett, McRobb and Farmer: Object Oriented Systems Analysis.
1/31 CS 426 Senior Projects Chapter 1: What is UML? Chapter 2: What is UP? [Arlow and Neustadt, 2005] January 22, 2009.
03/12/2001 © Bennett, McRobb and Farmer Development Process Based on Chapter 5 of Bennett, McRobb and Farmer: Object Oriented Systems Analysis and.
COMP 350: Object Oriented Analysis and Design Lecture 2
Objectives Explain the purpose and various phases of the traditional systems development life cycle (SDLC) Explain when to use an adaptive approach to.
1 CS 426 Senior Projects Chapter 1: What is UML? Chapter 2: What is UP? [Arlow and Neustadt, 2002] January 26, 2006.
1 © Bennett, McRobb and Farmer 2002, and De Montfort University 2002 Systems Development Methodologies Based on Chapter 22 of Bennett, McRobb and Farmer:
Chapter 6 View Alignment Techniques and Method Customization (Part I) Object-Oriented Technology From Diagram to Code with Visual Paradigm for UML Curtis.
Principles of Object Technology Module 1: Principles of Modeling.
PowerPoint Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 3rd Edition Copyright © 2009 John Wiley & Sons, Inc. All rights.
CIS 321—IS Analysis & Design
Chapter 2: Approaches to System Development
What is UML? What is UP? [Arlow and Neustadt, 2005] January 23, 2014
UML - Development Process 1 Software Development Process Using UML (2)
Object-Oriented Analysis and Design Iterative Development and the Unified Process.
Introduction to RUP Spring Sharif Univ. of Tech.2 Outlines What is RUP? RUP Phases –Inception –Elaboration –Construction –Transition.
2Object-Oriented Analysis and Design with the Unified Process Objectives  Explain the purpose and various phases of the traditional systems development.
Methods for OO Development USDP and DSDM. 2 Outline Characteristics of OO development USDP UML and DSDM.
Chapter 1: Introduction to Systems Analysis and Design
Software Development Processes
Software development process ธนวัฒน์ แซ่ เอียบ. The development process Process –set of rules which define how a development project. Methodology and.
Iterative development and The Unified process Chapter 2 Applying UML and Patterns -Craig Larman.
Chapter 2 Iterative, Evolutionary, and Agile You should use iterative development only on projects that you want to succeed. - Martin Fowler 1CS
Unified Modeling Language* Keng Siau University of Nebraska-Lincoln *Adapted from “Software Architecture and the UML” by Grady Booch.
1 UML Distilled 3e by Martin Fowler Chapter 1 Introduction to UML.
© Bennett, McRobb and Farmer Avoiding the Problems Based on Chapter 3 of Bennett, McRobb and Farmer: Object Oriented Systems Analysis and Design.
© 2010 Bennett, McRobb and Farmer1 Development Process Based on Chapter 5 Bennett, McRobb and Farmer Object Oriented Systems Analysis and Design Using.
Rational Unified Process Mr Hisham AlKhawar. Iterative versus Waterfall  We need to use a life cycle model in order to approach developing a system easily,
2 Systems Analysis and Design in a Changing World, Fifth Edition.
1 Introduction to UML. 2 What is UML? UML is an acronym for Unified Modeling Language. Unified –Combines the best from existing object- oriented software.
2 2009/10 Object Oriented Technology 1 Topic 2: Introduction to Object-Oriented Approach Reference: u Ch.16 Current Trends in System Development (Satzinger:
Inception Chapter 4 Applying UML and Patterns -Craig Larman.
Slide 1 Systems Analysis and Design With UML 2.0 An Object-Oriented Approach, Second Edition Chapter 2: Introduction to Object-Oriented Systems Analysis.
Slide 1 Systems Analysis and Design With UML 2.0 An Object-Oriented Approach, Second Edition Chapter 2: Introduction to Object-Oriented Systems Analysis.
The principles of an object oriented software development process Week 04 1.
1 Unified Modeling Language, Version 2.0 Chapter 2.
© Bennett, McRobb and Farmer 2005
Ivar Jacobson, Grady Booch, and James Rumbaugh The Unified Software Development Process Addison Wesley, : James Rumbaugh's OOMD 1992: Ivar Jacobson's.
Rational Unified Process Fundamentals Best Practices of Software Engineering Rational Unified Process Fundamentals Best Practices of Software Engineering.
28 June 2000P. Mato, CERN1 Software Checklist Proposal for controlling and documenting all the steps in developing software Program of Work Meeting, June.
Slide 1 Objectives Understand the basic characteristics of object-oriented systems. Be familiar with the Unified Modeling Language (UML),V.2.0.
2 Systems Analysis – ITEC 3155 Systems Analysis Tasks.
Unified Process Software Development Darren Roback/Ravali Kallem CMIS Fall 2009.
Basic Characteristics of Object-Oriented Systems
Software Development. The Software Life Cycle Encompasses all activities from initial analysis until obsolescence Analysis of problem or request Analysis.
Development Process Based on Chapter 5 Bennett, McRobb and Farmer
TK2023 Object-Oriented Software Engineering
Software Development.
The Basics of OOP Design
Chapter 1: Introduction to Systems Analysis and Design
TIM 58 More on Chapter 1: Introduction to Systems Analysis and Design
Business System Development
What is UML? What is UP? [Arlow and Neustadt, 2005] October 5, 2017
Systems Analysis and Design With UML 2
Systems Analysis and Design With UML 2
Unified Process Source & Courtesy: Jing Zou.
UNIFIED PROCESS.
COMP 350: Object Oriented Analysis and Design Lecture 2
Software engineering -1
Chapter 1: Introduction to Systems Analysis and Design
Chapter 1: Introduction to Systems Analysis and Design
CSCI 360: Software Architecture & Design
Presentation transcript:

IS0514 Lecture - Week 2 Best Practice Development Methodology

Slide 2 IS0514 – Semester 2 Week 2 Today's Lecture What is considered as best practice Information System Development What is part of best practice? What processes are required? How should the processes be put together?

Slide 3 IS0514 – Semester 2 Week 2 SDLC and Approaches Software Development Life Cycle (SDLC) Planning Why build the system? Analysis Who, what, when, where will the system be? Design How will the system work? Implementation System delivery Approaches Structured Development Rapid Application Development Agile Development

Slide 4 IS0514 – Semester 2 Week 2 What is best practice? Model Visually Use case driven Architecture centric Iterative and Incremental Grady Booch, Ivar Jacobson and James Rumbaugh (1999) The Unified Modelling Language User Guide

Slide 5 IS0514 – Semester 2 Week 2 Model Visually Picture speaks a thousand words Choice of language Traditional approach ERD / DFD / etc Object Oriented Approach UML <= in this module Choice of approach As sketch As blue print Fowler (2005) UML Distilled

Slide 6 IS0514 – Semester 2 Week 2 Use-Case Driven Use Case is a single interaction between user and system What the client wants the system to do Link to clients Constant reminder of client Unit from which later models are derived Thread that links through development Functional / non-functional / usability requirements?

Slide 7 IS0514 – Semester 2 Week 2 Use Case Driven – why? Build only what the client wants Don’t build technically driven project Everyone focused upon same requirements Developers Clients Users

Slide 8 IS0514 – Semester 2 Week 2 Architecture Centric - History ApproachWhen MainframeUp to late 1980s Thick clientLate 1980s – mid 1990s Web / Thin clientMid 1990s - present Web servicesLast few years

Slide 9 IS0514 – Semester 2 Week 2 Architecture Centric Many ways to solve problems Find best solution to provide value from choices available Architecture significantly affects everything else Very important to DESIGN This year focus is ANALYSIS

Slide 10 IS0514 – Semester 2 Week 2 Iterative Development The lifecycle is cyclic: Analyse a bit Design that bit Code the design Test the code Refine the analysis and repeat

Slide 11 IS0514 – Semester 2 Week 2 Iterative & Incremental Delivery

Slide 12 IS0514 – Semester 2 Week 2 How does this help? Mini-Projects Promotes early risk mitigation People think best short term Plan, design & code a little Encourages participation Allowing for correction sooner Allows software to evolve Exposes problems earlier Management of Risk

Slide 13 IS0514 – Semester 2 Week 2 Activity 1 – are diagrams enough? Do you think diagrams are enough? In groups of 3-4 spend 5 minutes discussing this. At the end of the time please be ready to share your discussions with the rest of the class.

Slide 14 IS0514 – Semester 2 Week 2 Activity 1 - Answer

Slide 15 IS0514 – Semester 2 Week 2 Unified Process Workflows 9 Workflows in 2 types: Engineering Workflows Business Modelling Requirements Analysis and Design Implementation Test Deployment Supporting Workflows Project Management Environment Configuration and change management

Slide 16 IS0514 – Semester 2 Week 2 Iterative Approach for the Full Lifecycle Phases Process Workflows Iterations Supporting Workflows Management Environment Business Modeling Implementation Test Analysis & Design Preliminary Iteration(s) Iter. #1 Iter. #2 Iter. #n Iter. #n+1 Iter. #n+2 Iter. #m Iter. #m+1 Deployment Configuration Mgmt Requirements ElaborationTransitionInceptionConstruction Workflows group activities logically In an iteration, you walk through all workflows

Slide 17 IS0514 – Semester 2 Week 2 Each major workflow describes how to create and maintain a particular model Models and Workflows Design Model Implementation Model Test Model realized by implemented by Requirements Workflow Analysis Design Workflow Implementation Workflow Test Workflow Use-Case Model Business Modeling Business Model verified by Core process workflows Iterative process resulting in a series of models which work with each other

Slide 18 IS0514 – Semester 2 Week 2 USDP Phases Inception Phase Business Case Technical Feasibility – Can We build it? Economic Feasibility – Is it worth building? Organisation Feasibility – If we build it will it be used? Elaboration Phase Enough System Analysis and Design to build system Construction Phase Build and Test Transition Phase Deploy

Slide 19 IS0514 – Semester 2 Week 2 Activity 2 – Do all projects need all the workflows? Do you think all projects need all the workflows? In groups of 3-4 spend 5 minutes discussing this. At the end of the time please be ready to share your discussions with the rest of the class.

Slide 20 IS0514 – Semester 2 Week 2 Activity 2 – Answer

Slide 21 IS0514 – Semester 2 Week 2 Summary How do you develop software? What is part of best practice? What processes are required? How should the processes be put together? Next week: Use Cases

Slide 22 IS0514 – Semester 2 Week 2 This weeks reading ESSENTIAL READING Dennis A, Wixom B, and Tegarden D (2005) System Analysis and Design with UML version 2 second edition, Wiley Pages Further reading Bennett, S., McRobb, S. and Farmer, R. (2002) Object- Oriented Systems Analysis and Design using UML, 2nd Edition, McGraw-Hill Chapter 3