OpenUP

The Open Unified Process (OpenUP) is a part of the Eclipse Process Framework (EPF), an open source process framework developed within the Eclipse Foundation. Its goals are to make it easy to adopt the core of the Rational Unified Process (RUP) / Unified Process.

The OpenUP began with a donation to open source of process content known as the Basic Unified Process (BUP) by IBM. It was transitioned to the Eclipse Foundation in late 2005 and renamed OpenUP/Basic in early 2006. It is now known simply as OpenUP.

Overview

OpenUP preserves the essential characteristics of Rational Unified Process / Unified Process, which include iterative development, use cases and scenarios driving development, risk management, and architecture-centric approach. Most optional parts of RUP have been excluded, and many elements have been merged. The result is a much simpler process that is still true to RUP principles.

OpenUP targets small and colocated teams interested in agile and iterative development. Small projects constitute teams of 3 to 6 people and involve 3 to 6 months of development effort.

Project Lifecycle

Known uses
gollark: - They may be working on them, but they initially claimed that they weren't necessary and they don't exist now. Also, I don't trust them to not do them wrong.- Ooookay then- Well, generics, for one: they *kind of exist* in that you can have generic maps, channels, slices, and arrays, but not anything else. Also this (https://fasterthanli.me/blog/2020/i-want-off-mr-golangs-wild-ride/), which is mostly about the file handling not being good since it tries to map on concepts which don't fit. Also channels having weird special syntax. Also `for` and `range` and `new` and `make` basically just being magic stuff which do whatever the compiler writers wanted with no consistency- see above- Because there's no generic number/comparable thing type. You would need to use `interface{}` or write a new function (with identical code) for every type you wanted to compare- You can change a signature somewhere and won't be alerted, but something else will break because the interface is no longer implemented- They are byte sequences. https://blog.golang.org/strings.- It's not. You need to put `if err != nil { return err }` everywhere.
gollark: Oh, and the error handling is terrible and it's kind of the type system's fault.
gollark: If I remember right Go strings are just byte sequences with no guarantee of being valid UTF-8, but all the functions working on them just assume they are.
gollark: Oh, and the strings are terrible.
gollark: Also, channels are not a particularly good primitive for synchronization.

See also

References
    This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.