PivotPoint Technology Corporation

Description

Model-Based Solutions ™ for tough problems. Why Model-Based? – Guide for the Skeptical and Clueless Are you considering the cost/benefit trade-offs of Model-Based Engineering (a.k.a. Model Driven Development and Model-Driven Engineering), but are confused about the “alphabet soup ” of acronyms (UML, BPMN, SysML, DoDAF/MODAF/UPDM, TOGAF, OpenUP) and the “Muddle Driven Marketecture ” tool vendor hype surrounding them? You should evaluate Model-Based Engineering technologies if ... Your organization should perform a cost/benefit analysis of Model-Based Engineering technologies if it has one or more of the following problems: Your system architecture is out of control. Does your system maintenance budge dwarf your R&D budget? Can you reliably and predictably expand your system or products? -Your technology processes are ad hoc, chaotic, or unpredictable. What percentage of your technology projects are completed on time and under budget? -Your business processes are ad hoc, chaotic, or unpredictable. Can you reliably estimate (+/- 10% margin-of-error) the cost/benefits of changing "as is" business processes to result in more competitive "to be" business processes? -Your most valuable corporate asset, your corporate Intellectual Property (IP), is at risk. What would your organization do if your lead business analyst or chief architect/chief engineer unexpectedly resigns, retires, or becomes incapacitated? -Your poor product/system quality is adversely impacting your bottom line. Do you have an established baseline for measuring error reduction rates and cost savings? If you don't, you likely have a chaotic system development process. (See the Your technology processes are ad hoc ... section above.) If your organization is large and you do not have one or more of the problems cited above, you are to be congratulated for being an exception to the general case. However, if your organization consists of humans and you have one or more of the problems cited above, you should exercise healthy skepticism when evaluating Model-Based Engineering technologies. If you are clueless about Model-Based Engineering then ... If you are clueless about what Model-Based Engineering (MBE) technologies are, and how they can help your organization, then the first thing you need to do is to become clued. To be more specific, you first need to learn how to differentiate between MBE and non-MBE approaches. If you fail to do this, you may fall prey to the Muddle-Driven Marketecture hype propagated by modeling tool vendors who promise business nirvana ("better, faster, cheaper") systems if you buy their "silver bullet" modeling tools with their "magic bullet" modeling languages (UML, SysML, BPMN, MumbleML) and architecture frameworks (DoDAF, MODAF, NAF, DNDAF, UPDM, TOGAF, MumbleAF). If you are naive or dumb enough to fall for this marketecture, then you likely deserve to squander your technology budget and blow your project schedule without significant ROI (Return On Investment).

Fact sheet

Products & services

Similar companies nearby