Introduction to OPEN Sidney Nogueira 12/11/2003.

Slides:



Advertisements
Similar presentations
K. Ingram1November 2000 Object Orientated Analysis and Design - Contents When to use OO? What is OO? Unified Modelling Language OO Methodologies: –Object.
Advertisements

Object-Oriented Software Development CS 3331 Fall 2009.
CS487 Software Engineering Omar Aldawud
Objectives Explain the purpose and various phases of the traditional systems development life cycle (SDLC) Explain when to use an adaptive approach to.
Overview Traditional systems development life cycle (SDLC)
Systems Analysis and Design in a Changing World, 6th Edition
CHAPTER 1 SOFTWARE DEVELOPMENT. 2 Goals of software development Aspects of software quality Development life cycle models Basic concepts of algorithm.
Introduction to UML: Structural &Use Case Modeling
INFO415 Approaches to System Development: Part 1
Approaches to Systems Development
RUP/UP Software Development Method Hoang Huu Hanh, Hue University hanh-at-hueuni.edu.vn.
Software Modeling SWE5441 Lecture 3 Eng. Mohammed Timraz
Practical Business Modeling in the Unified Process Tom Morgan Software Architect, Fidelity National Information Services
Using UML, Patterns, and Java Object-Oriented Software Engineering Royce’s Methodology Chapter 16, Royce’ Methodology.
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.
OO Development Process. UML and Process UML standardizes notation, not process –Increase likelihood of widespread acceptance There is significant variability.
1/31 CS 426 Senior Projects Chapter 1: What is UML? Chapter 2: What is UP? [Arlow and Neustadt, 2005] January 22, 2009.
© Copyright Eliyahu Brutman Programming Techniques Course.
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.
Introduction to Software Design Chapter 1. Chapter 1: Introduction to Software Design2 Chapter Objectives To become familiar with the software challenge.
Lesson 1 Week01.
OOSD Using Java Lecture 1 Introduction. 8/19/04introduction2 Introduction  IST 350 – Tools & CSC 485 – OOD?  Software Development vs. Programming 
CIS 321—IS Analysis & Design
Chapter 2: Approaches to System Development
What is UML? What is UP? [Arlow and Neustadt, 2005] January 23, 2014
1 Introduction Chapter 1. 2 Key Ideas Many failed systems were abandoned because analysts tried to build wonderful systems without understanding the organization.
Thirteenth Lecture Hour 8:30 – 9:20 am, Sunday, September 16 Software Management Disciplines Process Automation (from Part III, Chapter 12 of Royce’ book)
Chapter 1: Introduction to Systems Analysis and Design
©Ian Sommerville 2000, Mejia-Alvarez 2009 Slide 1 Software Processes l Coherent sets of activities for specifying, designing, implementing and testing.
JVB-STC'97- 1 #*#* Successful Adoption and Use of Object Oriented Technologies STC ‘97 April 30, 1997 Jim Van Buren.
Software Development Processes
Object-oriented Analysis and Design Stages in a Software Project Requirements Writing Analysis Design Implementation System Integration and Testing Maintenance.
Content The system development life cycle
Approaches to Systems Development
1/23 Prescriptive Process Models. 2/23 Prescriptive Models Prescriptive process models advocate an orderly approach to software engineering Prescriptive.
Rational Unified Process Fundamentals Module 5: Implementing RUP.
1 COMP 350: Object Oriented Analysis and Design Lecture 1Introduction References: Craig Larman Chapter 1.
1 Software Development Software Engineering is the study of the techniques and theory that support the development of high-quality software The focus is.
Design Analysis builds a logical model that delivers the functionality. Design fully specifies how this functionality will be delivered. Design looks from.
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,
Object-Oriented Analysis and Design. Lesson 1: Introduction to Software Engineering.
CEN5011, Fall CEN5011 Software Engineering Dr. Yi Deng ECS359, (305)
2 2009/10 Object Oriented Technology 1 Topic 2: Introduction to Object-Oriented Approach Reference: u Ch.16 Current Trends in System Development (Satzinger:
Rational Unified Process Fundamentals Module 3: Disciplines I.
1 Software Engineering: A Practitioner’s Approach, 7/e Chapter 2 Process: A Generic View Software Engineering: A Practitioner’s Approach, 7/e Chapter 2.
Slide 1 Systems Analysis and Design With UML 2.0 An Object-Oriented Approach, Second Edition Chapter 2: Introduction to Object-Oriented Systems Analysis.
1 Unified Modeling Language, Version 2.0 Chapter 2.
Ivar Jacobson, Grady Booch, and James Rumbaugh The Unified Software Development Process Addison Wesley, : James Rumbaugh's OOMD 1992: Ivar Jacobson's.
COMP2110 Software Design in 2003 ● a(nother) framework for Software Engineering ● the Software Engineering ideas and concepts in comp2110 ● Organisation.
Rational Unified Process Fundamentals Best Practices of Software Engineering Rational Unified Process Fundamentals Best Practices of Software Engineering.
Object-Oriented Systems. Goals Object-Oriented Methodologies – The Rumbaugh et al. OMT – The Booch methodology – Jacobson's methodologies.
Systems Analysis and Design in a Changing World, 6th Edition
Basic Characteristics of Object-Oriented Systems
UA. Unified Approach ( UA ) It combines best practices, methods process, guidelines & methodology (Rumbaugh, Booch and Jacobson) along with UML notations.
RATIONAL UNIFIED PROCESS PROCESS FRAMEWORK OVERVIEW.
Page 1 An Overview of The COTS-Aware Requirements Engineering and Software Architecting Project (CARE/SA) The University of Texas at Dallas Department.
Pragmatics 4 Hours.
Lecture 3 Prescriptive Process Models
Chapter 1: Introduction to Systems Analysis and Design
What is UML? What is UP? [Arlow and Neustadt, 2005] October 5, 2017
Systems Analysis and Design With UML 2
Rational Worldwide Software Symposium
Introduction to UML.
Object-Oriented Systems Development Life Cycle (CH-3)
Rational Worldwide Software Symposium
Chapter 1: Introduction to Systems Analysis and Design
Rational Worldwide Software Symposium
Chapter 1: Introduction to Systems Analysis and Design
Presentation transcript:

Introduction to OPEN Sidney Nogueira 12/11/2003

Cin - UFPE Topics OPEN OPEN Framework Framework Usage OPEN vs RUP Final Concerns References

Cin - UFPE OPEN “Because no single software development method will work for all kinds of projects, we should not try to standardize on a single development process or method, no matter how tailorable. Instead, we should concentrate on a development process framework that can be extended, instantiated, and tailored to meet the needs of specific projects.” Don Firesmith

Cin - UFPE OPEN Object-oriented Process, Environment and Notation (End of 1994) Public domain, full lifecycle, process-focussed, methodological approach Merge of MOSES, SOMA, Firesmith, etc OPEN Consortium : not-for-profit 35 methodologists, academics, CASE tool vendors and developers Defines a process framework – OPF - organizationally-specific process (instances from XP to RUP)

Cin - UFPE OPEN Encapsulates : business, quality, human issues, modeling, reuse, software development lifecycle support OO paradigm Tailored to suit : individual domains or projects taking into account, personal skills, organizational culture, requirements Approachs: use case driven, contract driven, responsibility driven, document driven, etc – “You Choose” used on small projects and large, mission critical projects

Cin - UFPE OPEN Process Framework OPF - OPEN Process Framework OPF comes with a repository containing: Cohesive class library - reusable interrelated process components (e.g., milestone). Selected instances of these classes (e.g., Requirements Frozen Milestone, Architecture Frozen Milestone, Construction Complete Milestone).

Cin - UFPE OPEN Process Framework OPF components in OML …

Cin - UFPE

OPEN Process Framework Main Elements: 5 metaclass groups : Work Units, Work Products, Producers, Stages and Languages 3 major metalevel classes (Work Units) : Activities, Tasks and Techniques

Cin - UFPE OPEN Process Framework Stage Work Products Work Units Producers Guidelines Languages performeproduce Macro organization Create Evaluate Iterate maintain documented Activites Tasks Technics OML UML, etc helps to OPF Documentaion Anything that produces e.g., documents, diagrams, applications, classes

Cin - UFPE Work Units Components 1) Activity collection of tasks (workflows) that produce a related set of work products. Defined in terms of project constraints If waterfall process these Activities might be equated to Phases. Include : Project initiation, Requirements engineering, Analysis and model refinement, Project planning, Build User review and Consolidation, Evaluation, Implementation or Deployment.

Cin - UFPE Work Units Components 2) Task - a single assigned job performed by one or more producers. 3) Technique - way of performing a task (i.e. common - abstraction, design - data mapping, management - pareto analysis, risk management - risk mitigation, quality - inpection, req. eng. - requirements tracing, test - regression testing, training - classroom training)

Cin - UFPE Work Units Components

Cin - UFPE Work Units - Example Role : OO Modeler Task : Identify Classes Techniques : Reify domain concepts Reify nouns as classes (i.e., perform lexical analysis) Reify externals as interfacer classes Reify transactions

Cin - UFPE Framework usage Process engineer must : Instantiate class library process components. Choosing best components. Tailoring fine detail inside chosen components. Extends existing class library of predefined components.

Cin - UFPE Framework Usage Not yet implemented

Cin - UFPE Framework usage Process Construction Guidelines help process engineers instantiate the development process framework How to: Select work products Select producers Select work units Allocate task and techniques Group tasks into workflows and activities

Cin - UFPE Framework Usage Tailoring Guidelines: fine-tuning by tailoring instantiated process components as development lessons learned Extension Guidelines: new process components will need to be added as the field advances

Cin - UFPE OPEN vs RUP RUP can be adapted, but has embed concepts Iterativo, incremental, use-case driven OPEN: mais flexível OPENRUP ActivitieWorkflow (flow) TaskActivitie TechniquesGuideline, Mentors StagePhase ProducerWorker

Cin - UFPE Final Concerns Public domain framework Flexible to join experiences Empashis on process modelage Reduced number of resources Lack of CASE tools support Not too much documentation and experiences

Cin - UFPE References Firesmith’s OPEN Process Framework Website, The OPEN Website, The OMG Software Process Engeneering Architecture, ech/2d1a_omg.html