1 / 18

INFO2005 Requirements Analysis The OPEN Methodology

INFO2005 Requirements Analysis The OPEN Methodology. Department of Information Systems. Learning Objectives. Introduce the essential concepts of OPEN (a rival to RUP) Overview the COMN notation (used in OPEN as an alternative to UML). Life cycle. Modelling. Techniques. metamodel.

hogan
Download Presentation

INFO2005 Requirements Analysis The OPEN Methodology

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. INFO2005Requirements Analysis The OPEN Methodology Department of Information Systems

  2. Learning Objectives • Introduce the essential concepts of OPEN (a rival to RUP) • Overview the COMN notation (used in OPEN as an alternative to UML)

  3. Life cycle Modelling Techniques metamodel language Methodology OPEN’s Idea of a Methodology How to document what you’ve done What to do How to organise it Actions Representation Process

  4. Initiation Requirements elicitation Analysis + model refinement Project planning Evolutionary development Evaluation Implementation planning The OPEN Lifecycle • Basic form is the “contract-driven” lifecycle

  5. OOA OOD OOP V&V (verification + validation) User review User review Evolutionary development Consolidation The OPEN Development Activity • The development activity in more detail: X 3

  6. Components of OPEN • The Process Specification defines these methodology components:

  7. OPEN Activities

  8. Activity Examples • Project initiation • Requirements engineering • Analysis and model refinement • Project planning and build

  9. Open Tasks • Activity = one or more tasks • Mainly represents the developer’s view • Some management tasks also included • Comprehensive list of tasks

  10. Task Examples

  11. OPEN Techniques • How to carry out one or more tasks • List is again comprehensive (many pages) • Many not original to OPEN, e.g.

  12. Technique Examples • Class internal design • Object life cycle histories • Many techniques use Common Object Modelling Notation (COMN) notation

  13. OPEN Deliverables • Post-condition for an activity • Often a pre-condition for another activity • Examples:

  14. COMN Notation • Common Object Modelling Notation

  15. BOAT Object Class Specialisation CLASS NAME Characteristics YACHT LAUNCH U Containment OBJECT NAME Aggregation Adapt for different characteristics, e.g. responsibilities, attributes, etc. 1 1 - * PASSENGER CARGO 1 - * 1 - 3 (Carries) MAST HULL FLAG Note: in COMN associations are always unidirectional 1 - * COMN Notation How does this differ from UML?

  16. Other OPEN Notation • OPEN uses notation that is close to UML

  17. Summary • Introduced the main concepts of OPEN • Overviewed the COMN notation

  18. Further Reading www.open.org.au Bennett, S. et al, 2002, “Object Oriented Systems Analysis and Design Using UML” McGraw-Hill (Chapter 22) Graham, I., et al, 1997, “The OPEN Process Specification” Addison-Wesley

More Related