The B uff. The Buffs Agenda 1. Recent iteration and Progress 2. Plan for next iteration 3. Prototype demonstration.

Slides:



Advertisements
Similar presentations
September 2008Mike Woodard Rational Unified Process Key Concepts Mike Woodard.
Advertisements

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--
Ninth Lecture Hour 8:30 – 9:20 pm, Thursday, September 13
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.
CS 325: Software Engineering January 15, 2015 Software Process & Methodology Prototyping Process Model Evolutionary Process Model Spiral Process Model.
Using UML, Patterns, and Java Object-Oriented Software Engineering Royce’s Methodology Chapter 16, Royce’ Methodology.
Rational Unified Process
Chapter Extension 19 Alternative Development Techniques © 2008 Pearson Prentice Hall, Experiencing MIS, David Kroenke.
NJIT From Inception to Elaboration Chapter 8 Applying UML and Patterns Craig Larman.
OO Development Process. UML and Process UML standardizes notation, not process –Increase likelihood of widespread acceptance There is significant variability.
Object-oriented Analysis and Design
Iterative development and The Unified process
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.
Page 1 R Risk-Driven and Iterative Development. Page 2 R Copyright © 1997 by Rational Software Corporation What the Iterative Life Cycle Is Not It is.
Resume Extraction with Business Process Management (BPM) tools
© 2005 Prentice Hall14-1 Stumpf and Teague Object-Oriented Systems Analysis and Design with UML.
Principles of Object Technology Module 1: Principles of Modeling.
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.
RUP Fundamentals - Instructor Notes
IT Systems Analysis & Design
-Nikhil Bhatia 28 th October What is RUP? Central Elements of RUP Project Lifecycle Phases Six Engineering Disciplines Three Supporting Disciplines.
Unified Process versus Extreme Programming. Outline Compare and contrast UP and XP  Processes / Disciplines  Management  Artefacts Risk management.
©Ian Sommerville 2000, Mejia-Alvarez 2009 Slide 1 Software Processes l Coherent sets of activities for specifying, designing, implementing and testing.
Role-Based Guide to the RUP Architect. 2 Mission of an Architect A software architect leads and coordinates technical activities and artifacts throughout.
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.
The B uff. The Buffs Agenda 1. Recent iteration and job done 2. What we are doing now.
Object-oriented Analysis and Design Stages in a Software Project Requirements Writing Analysis Design Implementation System Integration and Testing Maintenance.
By Matt Baker Eric Sprauve Stephen Cauterucio. The Problem Advisors create a sign-up sheet to be posted on the door of their office. These sign-up sheets.
Distributed Software Development QR Marks The Spot Beta Prototype Vadym Khatsanovskyy, Nicolas Jacquemoud.
Fifth Lecture Hour 9:30 – 10:20 am, September 9, 2001 Framework for a Software Management Process – Life Cycle Phases (Part II, Chapter 5 of Royce’ book)
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,
University of Toronto at Scarborough © Kersti Wain-Bantin CSCC40 other methodologies 1 Method/Process = step-by-step description of the steps involved.
PRJ566 Project Planning & Management Software Architecture.
The principles of an object oriented software development process Week 04 1.
Overview of RUP Lunch and Learn. Overview of RUP © 2008 Cardinal Solutions Group 2 Welcome  Introductions  What is your experience with RUP  What is.
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 (RUP)
Rational Unified Process Fundamentals Best Practices of Software Engineering Rational Unified Process Fundamentals Best Practices of Software Engineering.
Intelligence and Information Systems 1 3/17/2004 © 2004 Raytheon Company USC/CSE Executive Workshop on Agile Experiences March 17, 2004 A Raytheon Agile.
Meghe Group of Institutions Department for Technology Enhanced Learning 1.
Software Development Life Cycle (SDLC)
The B uff. The Buffs Outline 1. Summary of last presentation 2. Current iteration and Progress 3. Plan for next iteration.
RUP RATIONAL UNIFIED PROCESS Behnam Akbari 06 Oct
RATIONAL UNIFIED PROCESS PROCESS FRAMEWORK OVERVIEW.
Review of Definitions Software life cycle: –Set of activities and their relationships to each other to support the development of a software system Software.
Software Development. The Software Life Cycle Encompasses all activities from initial analysis until obsolescence Analysis of problem or request Analysis.
Software Development Framework
Iterative development and The Unified process
TK2023 Object-Oriented Software Engineering
Software Development.
Process 4 Hours.
Methodologies and Algorithms
CSC 355 – Newer Approaches to System Development Life Cycles & Processes, Spring 2017 March 2017 Dr. Dale Parson.
V-Shaped SDLC Model Lecture-6.
UNIFIED PROCESS.
UML: Unified modeling language
IT Systems Analysis & Design
COMP 350: Object Oriented Analysis and Design Lecture 2
Object Oriented Analysis and Design
Rational Unified Process (RUP)
Chapter 2 – Software Processes
Software engineering -1
The Unified/Rational Unified Process (UP/RUP) Defined
Presentation transcript:

The B uff

The Buffs

Agenda 1. Recent iteration and Progress 2. Plan for next iteration 3. Prototype demonstration

I1 I2 E1 C1 C2 Current situation Inception Elaboration Construction Mar 29 – Apr 10 Apr

Progress on the Elaboration iteration 1  Held a structured confirmation interview with Ms. Izel  Yes/No question  Refined the requirements and related documents  Determine the exact development and management tool  PHP Framework: Code igniter  Google code for version controlling, issue tracking, task allocation, and knowledge distribution using built-in wiki  Project schedule monitoring through Gantt chart  Rational Rose for generating UML diagrams  Define the overall architecture based on the most significant use cases and an assessment of risk  The selected PHP framework kind of base lining the architecture for us which is nice  Persistence pattern using Data Mapper.  Model view controller pattern

Progress on the Elaboration iteration 1(cont.)  Risk Management  Risk and the corresponding mitigation/contingency strategy is identified  Documented in the Risk List and Risk Management Plan  Perform object oriented design and analysis on critical use cases (~70%)  Static and dynamic diagram  Documented in the SAD doc and Use case realization doc  Prototypes  Digital prototype for group understanding  Working (not thrown away) prototype for getting rapid customer feedback  ~15% use cases  Iteration plan for next iteration

Problem encountered in this iteration  We have no user involvement in this iteration at all  More frequent short meeting  Cost and benefit is mostly intangible and difficult to measure.  Eg. Customer satisfaction  Must find a way  Documentation becomes a big overhead  we lack experiences in customizing the RUP framework, anyhow, we are getting better  Frankly saying, some documents are never opened again once it’s finished?  We do not work exactly according the Gantt chart  We need to keep up with the schedule  Some risk is not properly mitigated and occurs. Eg. Schedule slip  Minor conflicts on SVN lost updates

Meeting the Lifecycle Architecture milestone? 1. Since most of the baseline architecture for web application is quite determined by the framework solution, we have a easier life.  Main use cases are tested.  Selection and verification? 2. Risk is identified and mitigation strategy is determined 3. Requirement is quite stable 4. Bye Bye Elaboration phase!

Construction iteration 1 Gantt Chart

Plan for Construction iteration 1(April 12)  Refine documentation accordingly  Refine analysis and design diagrams  Describing the remaining use cases and fill in design  Implement the rest of the use cases  Some extreme programming practices may be applied eg. Continuous integration  Integration test and functional test  Hopefully, we plan to release the beta version by next iteration  Get customer feedback  Prepare the beta deployment  Contact the IT-serv

Solution Flow Login Create Update/ Preview/ Delete Publish PWL Existed ? No Yes Archive PWL Database Search task, issue, letter View Import Word