UPEDU

The UPEDU or Unified Process for Education is a software development process specialized for education, developed by Pierre-N. Robillard (École Polytechnique de Montréal), Philippe Kruchten (Rational Software) and Patrick d'Astous (École Polytechnique de Montréal).[1]

UPEDU is a customization of the IBM Rational Unified Process (or RUP) and therefore inherits the most prominent properties of RUP, such as:

* It is iterative and an implementation of the spiral model
* The process is divided in time into four phases; the inception, elaboration, construction and transition phases, each of which consists of one or more milestones. For each phase, the set of artifacts (work products) and the work flow are defined by the process.
* The activities are categorized into disciplines, to clarify the required expertise and categorize the activities.

To help implementing the UPEDU in educational purposes, the authors have put a website online[2] that provides most of the information that students need to use the process in their project.

## Disciplines

The disciplines in UPEDU in comparison to RUP are more aimed towards getting familiar with the unifying process and teaching the effect of using and adapting the process. Therefore, the RUP model has been simplified on some points, and the Nusiness modeling discipline, the Deployment discipline and the Environment discipline have been left out of the process.

## Known uses

* The Dutch University of Groningen and the Swedish Linnaeus University offer students a collaborative course called ISEP (International Software Engineering Project) in which UPEDU is heavily used.
* The École Polytechnique de Montréal, alma mater of Robillard, features a course focused on software project management using UPEDU as a teaching tool.

## References

1. ↑ Robillard, Pierre N.; Kruchten, Philippe; d'Astous, Patrick (16 September 2004). Software Engineering Processes with the UPEDU. Boston: Addison Wesley. ISBN 0201754541.
2. ↑ "UPEDU website". http://www.upedu.org/.

* v
* t
* e

Software engineering

Fields|

* Computer programming
* Requirements engineering
* Software deployment
* Software design
* Software maintenance
* Software testing
* Systems analysis
* Formal methods

Concepts|

* Data modeling
* Enterprise architecture
* Functional specification
* Modeling language
* Orthogonality
* Programming paradigm
* Software
* Software archaeology
* Software architecture
* Software configuration management
* Software development methodology
* Software development process
* Software quality
* Software quality assurance
* Software verification and validation
* Structured analysis

Orientations|

* Agile
* Aspect-oriented
* Object orientation
* Ontology
* Service orientation
* SDLC

Models|

| Developmental|

* Agile
* EUP
* Executable UML
* Incremental model
* Iterative model
* Prototype model
* RAD
* UP
* Scrum
* Spiral model
* V-Model
* Waterfall model
* XP

|

Other|

* SPICE
* CMMI
* Data model
* ER model
* Function model
* Information model
* Metamodeling
* Object model
* Systems model
* View model

Languages|

* IDEF
* UML
* USL
* SysML

Software
engineers

* Victor Basili
* Kent Beck
* Grady Booch
* Fred Brooks
* Barry Boehm
* Peter Chen
* Danese Cooper
* Ward Cunningham
* Tom DeMarco
* Edsger W. Dijkstra
* Delores M. Etter
* Martin Fowler
* Adele Goldstine
* Margaret Hamilton
* C. A. R. Hoare
* Lois Haibt
* Mary Jean Harrold
* Grace Hopper
* Watts Humphrey
* Michael A. Jackson
* Ivar Jacobson
* Alan Kay
* Nancy Leveson
* Stephen J. Mellor
* Bertrand Meyer
* David Parnas
* Trygve Reenskaug
* Winston W. Royce
* James Rumbaugh
* Mary Shaw
* Peri Tarr
* Elaine Weyuker
* Niklaus Wirth
* Edward Yourdon

Related fields|

* Computer science
* Computer engineering
* Project management
* Risk management
* Systems engineering

* Category
* Commons

0.00

(0 votes)

Original source: https://en.wikipedia.org/wiki/UPEDU. Read more

|

Retrieved from "https://handwiki.org/wiki/index.php?title=Philosophy:UPEDU&oldid=4019618"
*[v]: View this template
*[t]: Discuss this template
*[e]: Edit this template