Personal tools
You are here: Home Knowledge Model REPOSITORY of Terms A Assumption


by Asli Zengin last modified Apr 26, 2012 11:38
— filed under:


Domain: Cross-cutting issues
Engineering and Design
Adaptation and Monitoring
Quality Definition, Negotiation and Assurance
(domain independent)

Business Process Management

Service Composition and Coordination

Service Infrastructure

(domain independent)
The assumptions are used to capture those properties of the SBA environment that make the SBA working according to its requirements. There is a  clear separation between the requirements for the SBA and the assumptions under which it is supposed to operate. Assumptions may be used to capture functional and non-functional properties of the SBAs; they may refer to different aspects and elements of different layers of the functional stack. [Gehlert et al, 2010]

The act of laying claim to or taking possession of something; arrogance, pretension; An assuming that something is true [Webster 2012].






  • [Gehlert et al, 2010] A. Gehlert, A. Bucchiarone, R. Kazhamiakin, A. Metzger, M. Pistore, and K. Pohl. Exploiting assumption-based verification for the adaptation of service-based applications. In Proceedings of the 25th Annual ACM Symposium on Applied Computing, Track on Service Oriented Architectures and Programming, Sierre, Switzerland, March 2010.
  • [Webster, 2012], Last viewed in March 2012.

Document Actions
  • Send this
  • Print this
  • Bookmarks

Generic (domain independent)

Posted by stefania lombardi at Mar 14, 2012 12:07
Difference between constraints and assumption.
Constraints are factors that limit the team's options, such as limits on resources, budget, schedule, and scope (e.g., management saying the project must be completed with only five resources). Assumptions are things that are assumed to be true but that may not be true (e.g., it is assumed that we will not need engineering department approval before we start the activity). Constraints and assumptions, which are recorded in the project scope statement, are inputs to many project management processes.
Constraints and assumptions are identified and then managed. The sponsor, the team, and other stakeholders can identify constraints and assumptions and review them for validity throughout the life of the project. If the constraints change or the assumptions are proven wrong, the project management plan may need to change. Assumptions analysis is part of the risk management process (cit: RITA MULCAHY's "PMp® Exam Prep -
Rapid learning to Pass PMI®'s PMP Exam onYour FIRST Try!", a Guide for Project Managers).

The Plone® CMS — Open Source Content Management System is © 2000-2017 by the Plone Foundation et al.