Engineering before the Scientific Revolution Medieval engineers were specifying engineering requirements based on opinions Requirements were imprecise, incomplete, and unstable Most bridges fell down Ancient Bridge

Medieval engineers were specifying engineering requirements based on opinions

Requirements were imprecise, incomplete, and unstable

Most bridges fell down

Engineering after the Industrial Revolution Specify requirements based on physics and mathematics Requirements are precise, concise and stable Consensus and standards of building bridges exist Bridges do not fall down if standards are followed. Modern Bridge

Specify requirements based on physics and mathematics

Requirements are precise, concise and stable

Consensus and standards of building bridges exist

Bridges do not fall down if standards are followed.

Software Engineering Today Software engineers specify requirements based on personal opinions. Requirements are imprecise, inconsistent, and unstable, resulting poor design and rework. Most software projects failed or challenged

Software engineers specify requirements based on personal opinions.

Requirements are imprecise, inconsistent, and unstable, resulting poor design and rework.

Most software projects failed or challenged

Today’s Software are like Medieval Bridges Both have requirements based on personal opinions Both have no consensus on methods Both fail most of the time is like

Both have requirements based on personal opinions

Both have no consensus on methods

Both fail most of the time

Software Industry Revolution Specify requirements based on scientific principles Requirements are precise and stable, resulting in better, cheaper and faster software. . is like

Specify requirements based on scientific principles

Requirements are precise and stable, resulting in better, cheaper and faster software. .

Enterprise Software Redefined Customers Partners Other systems Transactional Environment Contextual Environment Actors Software Components Organizational Units Enterprise Software System Regulation Weather

The New Requirements Model Customer Model Business Model User Model Constrains Constrains Realizes Realizes

Three Steps to Create the Requirements Model Develop Customer Model 1 Develop Business Model 2 Develop User Model 3

Benefits of the New Model Do the right thing in the beginning for greater business and IT alignment Precise, concise, and stable requirements for better, cheaper and faster software Scientific work instead of guesswork No scope creep for complete requirements definition Customer Model Business Model User Model

Next Step Read our website for more information at www.ucsoft.biz Schedule a two-hour representation on your site to get all questions answered Begin to apply the new model to three of your projects with success Institutionalize the methodology throughout of your company

Read our website for more information at www.ucsoft.biz

Schedule a two-hour representation on your site to get all questions answered

Begin to apply the new model to three of your projects with success

Institutionalize the methodology throughout of your company