Ace Your OMG UAF MU Certification: 8 Concepts You Must Master

Updated on 23 September 2026. What’s new: the exam's 31% Domain Metamodel section is examined across ten UAF viewpoints, and OMG's exam sheet uses 'viewpoint' in place of 'domain'

The OMG Certified UAF Model User exam is a 90-question paper on the Unified Architecture Framework, and four-fifths of its marks sit in only three places: the Domain Metamodel, the view specifications built on top of it, and the UAF Grid that organises both. Candidates who revise it as a defence-framework vocabulary test lose marks they never see coming. This guide walks the eight concepts that actually decide the result.

Everything below is checked against the exam information sheet OMG published for the Model User level and the figures ProcessExam holds for the exam, with the certification status read on omg.org in September 2026. Where OMG names a specification version, that version is named here too, because the Model User paper is written against particular editions of the UAF documents rather than against UAF in general.

What does the OMG UAF Model User exam actually test?

UAF is the Object Management Group's framework for describing an enterprise as a model rather than as a shelf of documents. It grew out of the work to unify the defence architecture frameworks, and OMG states that it was developed to meet requirements coming from UML, SysML and the military frameworks DoDAF, MoDAF and NAF. The Model User exam is the entry point to the certification programme for it, and OMG describes it as a test of whether you understand UAF's purpose, scope and fundamental concepts, with the emphasis on the UAF Grid and on why its views exist.

The verb in that description matters. Model User is a reading credential, not a building one. You are asked to look at a view, work out which viewpoint it belongs to, say what stakeholder concern it answers and judge whether its contents make sense. You are not asked to author the model. That is what the Model Builder exams exist for, and OMG makes the Model User paper a prerequisite for all of them, so this exam is the gate everyone on the UAF track passes through first.

Here is what you are booking, with the figures ProcessExam records for the exam and the delivery rules from OMG's Model User exam information sheet.

Exam detail	OMG Certified UAF Model User
Exam code	OMG-UAF-MU100
Exam fee	USD $350, plus local taxes where they apply
Number of questions	90
Passing score	56 correct answers of 90 (62%)
Duration	90 minutes for residents of English-speaking countries; 120 minutes for all others
Question format	Multiple choice, single and multiple correct answers, with text and images
Prerequisites	None
Exam language	English
Delivery	Pearson VUE, in a test centre or proctored online
Validity	Three years, counted from the day you sit it
Standards examined	UAF Modeling Language v1.2, UAF Domain Metamodel v1.2, UAF Appendix A: Traceability, SysML v1.6

Two of those rows quietly set the difficulty. Ninety questions in ninety minutes gives you a minute apiece, and several of them put a diagram on screen that has to be read before the options mean anything. And 56 correct answers is not a comfortable margin: you can afford 34 wrong answers across the whole paper, which sounds generous until you notice that the largest topic alone can supply nearly thirty questions.

Which three UAF areas decide four-fifths of your score?

OMG publishes a percentage against every section of the Model User syllabus, and the shape of that list is the single most useful planning tool you have. Three sections together account for 80% of the paper. The graphic below shows the whole split; the sections themselves are described underneath.

Concept 1 - the UAF Domain Metamodel and its ten viewpoints (31%)

The Domain Metamodel, always written DMM, is the part of UAF that defines what exists and what may be connected to what. It is the grammar of the framework: every element you can place in a UAF model, and every legal relationship between elements, is declared there. Nearly a third of the exam comes from it, which makes it the section you cannot bargain with.

OMG's syllabus lists ten viewpoints under this heading, and it adds a note that is worth reading twice: in the exam, the word viewpoint is used where older UAF and defence-framework material said domain. The ten are Strategic, Operational, Services, Personnel, Resources, Actual Resources, Security, Projects, Standards and Parameters. Learn them as a set and you will recognise most of the section on sight, because every DMM question is anchored in one of them.

The content behind each one is worth sketching in a sentence you write yourself. Strategic covers capabilities and the phases in which an enterprise acquires them. Operational covers the logical performers and activities that meet those capabilities, independent of who or what carries them out. Services covers the service interfaces between them. Resources covers the systems, software and physical assets that realise the operational picture, and Actual Resources covers the real, named instances deployed in a particular configuration. Personnel covers posts, roles, competences and organisations. Security covers assets, risks, measures and enclaves. Projects covers the programmes and milestones that deliver the change. Standards covers the technical and operational standards the architecture is bound to. Parameters covers the measurements and properties attached to anything else.

Concept 2 - view specifications and the stakeholder question each one answers (27%)

If the DMM says what may exist, a view specification says which slice of it to show, to whom, and why. This section is worth more than a quarter of the paper and it is where most of the diagram-reading questions live. OMG lists nine viewpoints here: Architecture Management, Strategic, Operational, Services, Personnel, Resources, Projects, Standards and Parameters.

Notice that Architecture Management appears in this list but not in the DMM list, and that Actual Resources and Security appear in the DMM list but not here. Those asymmetries are examinable. Architecture Management is the housekeeping viewpoint that holds the metadata, the architecture description itself and the traceability back to source material, which is why it belongs with the view specifications rather than with the domain content.

The habit that earns marks in this section is to read every view specification as a question with an owner. Strategic view specifications answer a sponsor asking which capabilities the enterprise needs and when. Operational ones answer a planner asking what has to be done. Resources ones answer an engineer asking what will do it. Personnel ones answer an HR or force-structure lead asking who is needed and with what skills. When a question shows you a view and asks which specification it satisfies, the stakeholder in the stem is usually the clue.

Concept 3 - the UAF Grid (22%)

The Grid is the one-page map of the whole framework, and at 22% it is the third pillar of your preparation. It is a matrix. Its rows are the viewpoints just described; its columns are model kinds, which are ways of looking at the same subject matter rather than diagram types. Taxonomy asks what kinds of thing there are. Structure asks how they are put together. Connectivity asks what talks to what. Processes ask what happens in what order. States ask what conditions a thing can be in. Interaction scenarios ask how an exchange plays out. Information asks what data is involved. Parameters ask what is measured. Constraints ask what rules apply. Roadmaps ask how the picture changes over time.

OMG's syllabus splits this section into the motivation for organising the Grid that way, the viewpoints and aspects it uses, and the individual view specifications it points to. Read those three parts as three different kinds of question. Motivation questions ask why a grid beats a list of diagrams; the answer is completeness and gap analysis, because an empty cell is a question nobody has asked yet. Aspect questions ask you to place a cell. View specification questions ask you to name what sits in it.

A practical drill: draw the Grid from memory on a single sheet, then pick any cell and say out loud what a view in that cell would contain and who would want it. If you can do that for twenty cells, this section stops being a memory exercise.

Which five remaining concepts finish the syllabus?

The last 20% of the paper is spread across three small sections, and inside them sit the remaining five concepts on this list. They are cheap to learn and expensive to skip, because at 62% you do not have enough margin to write off a fifth of the exam.

Concept 4 - general UAF: background, motivation, compliance and specification organisation (9%)

This section is the context that everything else hangs on, and it is almost entirely recall. It covers where UAF came from, why it exists, which frameworks influenced it, how compliance with the specification is defined, and how the UAF documents themselves are organised. The influencing frameworks are the ones named earlier: the framework had to serve UML and SysML modellers at the same time as the DoDAF, MoDAF and NAF communities.

The compliance material catches people out because it is not about your model being correct. It is about what a tool or a specification implementation has to support to claim conformance to UAF. Read that part of the specification once, properly, rather than skimming it; it is a small number of pages and a reliable source of marks.

Concept 5 - view representations in SysML notation (7%)

UAF invents no new diagram types. It is expressed through UML and SysML notation, which is why SysML v1.6 sits in the list of standards the exam covers. This section tests whether you can look at a diagram and say what it is.

On the structural side you need to recognise how UAF applies SysML structure. On the behavioural side, OMG names the diagram kinds explicitly: activity, parametric, sequence, state machine and use case. And in the general SysML material it names the relationships you must tell apart: aggregation, association, containment, composition, dependency and generalisation. That last group is worth a dedicated study session, because the difference between a shared aggregation and a composition is exactly the sort of thing a single-mark question is built on. The section also covers representation types that are not diagrams at all, such as tables and matrices, which UAF uses heavily.

Concept 6 - traceability and cross-cutting relationships (part of 4%)

Traceability is the thread that makes a UAF model worth building: it links a capability to the operational activity that delivers it, to the resource that performs it, to the project that funds it. OMG examines it through cross-cutting relationships, the connections that run between viewpoints rather than inside one. The exam asks you to follow such a chain and say what would be affected if one end of it changed.

Concept 7 - model analysis (part of 4%)

The other half of that small section is what you do with a complete, traced model: query it. Find the operational activities no service supports. Find the resources that realise nothing. Check that every project milestone has a capability behind it. The specification frames this under its core principles, and the Model User exam expects you to understand the idea rather than to run the queries yourself.

Concept 8 - the four documents the exam is written against

This one is not a syllabus percentage, and that is precisely why candidates miss it. OMG states which editions the Model User paper examines: the UAF Modeling Language v1.2, the UAF Domain Metamodel v1.2, Appendix A on traceability, and SysML v1.6. Studying from a different edition of UAF, or from generic DoDAF material, puts you at risk of answering a question about a concept that has since been renamed or restructured. The current UAF specification pages on omg.org are the free, authoritative source, and Appendix A in particular is short enough to read end to end in an evening.

How do you book the MU100, and what happens after you pass?

Booking runs entirely through Pearson VUE. You create or sign into a Pearson VUE account, choose the UAF Model User exam, pay, and pick either a test centre or an online sitting. OMG's guidance is to run the system test on your own machine before you commit to an online slot rather than discovering a webcam or bandwidth problem on the morning.

The longer duration for candidates outside the English-speaking countries is not a box you tick while booking. OMG sends it through by email once your order goes through, so open that message and check the allowance it states before you settle on a slot. Plans change, and a sitting cancelled through Pearson VUE with more than 24 hours to go returns the fee in full; leave it later and the money is gone.

A failed attempt is not a dead loss. OMG prints a 20% retake code on the score report, which is reason enough to open the report properly instead of closing the tab. A pass brings a Credly digital badge within hours, plus a certificate you can print as a PDF or on paper. From that day the credential runs for three years, and you keep it alive by sitting the same exam once more, or a higher UAF exam, before the three years are up.

One more detail that reassures nervous candidates: there are no prerequisites. You do not need a prior OMG certification, a degree or a documented number of years to sit Model User. The barrier is the material, not the paperwork.

What does a UAF Model User question look like on screen?

Because the format includes questions with more than one correct answer, the first thing to learn is to read the stem for how many selections it wants. Beyond that, the questions fall into a few recognisable shapes. Working through a set of UAF Model User sample questions before you build a study plan tells you quickly which shape you are weakest at.

Shape one: place the view

You are shown a diagram of organisational posts with lines showing who reports to whom, and asked which viewpoint and model kind it belongs to. The reasoning runs in two steps. The subject matter is people and posts, so the viewpoint is Personnel. The diagram shows how the parts are arranged rather than what kinds exist or what flows between them, so the model kind is structure.

Shape two: name the relationship

A fragment of a diagram shows two blocks joined by a line with a filled diamond at one end, and four options describe what that means. Here the exam is testing SysML notation inside a UAF context. A filled diamond is composition, which carries an ownership and lifetime dependency, while the hollow one is shared aggregation and does not.

Shape three: follow the thread

A short scenario states that a capability has been dropped from the strategic plan and asks which elements need review. The answer depends on cross-cutting relationships: the operational activities that realised the capability, the services exposed to support them, the resources allocated, and the project milestones that were funding the change.

Shape four: why does this exist

Plainest of all, and drawn from the general UAF section: a question asks what problem the Grid was designed to solve, or why UAF was produced when DoDAF, MoDAF and NAF already existed. These reward one careful read of the specification's opening chapters and nothing else.

How should you split your study time across the UAF syllabus?

Take whatever hours you can realistically give the exam and divide them by the published percentages rather than by what you enjoy. If you can find forty hours, that puts roughly twelve into the DMM viewpoints, eleven into view specifications, nine into the Grid, and the remaining eight across general UAF, view representations, traceability and model analysis. The arithmetic is crude, but it stops the common failure of spending three weeks on the Grid because it is visually satisfying and arriving at the exam unable to tell a Security viewpoint from a Standards one.

Phase one: build the vocabulary

Write the ten DMM viewpoints on one card and the nine view-specification viewpoints on another. Say what each covers in your own words. Do not move on until both lists come out in any order without prompting, because every later phase assumes them.

Phase two: draw the Grid

Reproduce the Grid by hand, then fill cells from memory. Work along a row to see one viewpoint expressed in different model kinds; work down a column to see one model kind applied across viewpoints. Reading the Grid both ways is what turns it from a picture into a tool.

Phase three: read notation

Spend a session on SysML relationships and a session on the five named behavioural diagram kinds. Sketch one of each with UAF content rather than a generic example, so the notation and the framework fuse in your memory instead of sitting in separate drawers.

Phase four: time yourself

The last phase is about pace, not knowledge. Once the two viewpoint lists come out cleanly and the Grid holds up, a timed OMG-UAF-MU100 practice test is the fastest way to find out whether you can hold a minute a question when a diagram is on screen. Note every question you got right slowly, not just the ones you got wrong; those are the ones that will cost you at the end of the paper.

What trips up candidates who already know DoDAF or SysML?

Prior experience is an advantage on this exam right up to the point where it quietly becomes a liability. The errors below are the ones that experienced architects make and beginners do not.

Calling a viewpoint a domain

Long-standing UAF and defence-framework material talks about domains. OMG's exam material uses viewpoint in that place. The idea is the same, but if you have drilled the older word you can lose a beat on every question that uses the newer one, and a beat a question is expensive when you have a minute each.

Confusing the view with its specification

A view specification is the template: it declares what a view of that kind must contain and whose concern it addresses. The view is the artefact you produce by following it. Answer options routinely offer both, and the stem tells you which one it wants.

Treating Grid columns as diagram types

Model kinds are perspectives, not notations. Structure, connectivity, processes and states are questions about the subject, and more than one of them can be drawn with the same SysML diagram. Mapping a column straight onto a diagram type produces confident wrong answers.

Assuming SysML knowledge transfers untested

SysML v1.6 is examined, not assumed. If you last worked in UML, check the relationship semantics again; if you have moved to newer systems-modelling work, check that you are answering from the edition the exam names rather than from a later one.

Skipping the 9% because it looks like preamble

General UAF is history, motivation, influencing frameworks, compliance and document organisation. It is also nine marks in every hundred, available to anyone willing to read a short chapter, and it is the cheapest section on the paper.

Preparing only from third-party summaries

Blog posts and course notes compress the framework, and compression loses exactly the distinctions the exam probes. Use them to orient yourself, then verify every list against the specification itself.

Where does the UAF Model User credential take you next?

Model User is designed as a foundation rather than a destination. OMG's position is that it proves you can interpret UAF views and their contents correctly and contribute usefully to an architecture team working at enterprise, mission, system-of-systems or system level. That is the realistic claim to make about it in an interview, and it is a claim that holds up.

The programme continues into the Model Builder exams, and Model User is the prerequisite for all of them, so passing it is the only way onto that path. Since certifications run for three years, the natural rhythm is to move up a level before the clock runs out, which renews your standing and raises it in one sitting.

The credential carries most weight in the places UAF is actually used: defence and aerospace programmes that inherited DoDAF, MoDAF or NAF obligations, large infrastructure and transport projects, and government enterprise-architecture teams. OMG notes that the UAF exam and standards are maintained by experts from organisations including The Aerospace Corporation, Armstrong Process Group, Dassault Systemes, Elparazim, Lockheed Martin and System Strategy, which tells you plainly which industries the framework was built for and where the certification will be recognised.

For an individual, the honest value is narrower than a general architecture certification and deeper. It does not claim you can run an enterprise-architecture practice. It says you can walk into a room where UAF views are on the wall, understand what each one is for, and take part in the conversation from the first meeting. On a programme that models this way, that is the difference between joining a team and being carried by it. If UAF is on your employer's roadmap, the OMG UAF certification programme page is where the current exam list and booking route start.

Frequently Asked Questions

What is the passing score for the OMG UAF Model User exam?

You need 56 correct answers of the 90 asked, which OMG records as 62%. The paper is multiple choice, and some questions accept more than one correct answer, so read each stem for how many selections it expects before you commit to an option.

How much does the OMG-UAF-MU100 exam cost and how do I book it?

The exam fee is USD $350, plus local taxes where they apply. You book and pay through a Pearson VUE account and choose either a test centre or an online sitting. Cancel with more than 24 hours to go and the fee comes back in full; leave it later and it does not.

How long do I get for the UAF Model User exam?

Residents of English-speaking countries get 90 minutes for the 90 questions, and everyone else gets 120 minutes. You do not choose the longer allowance when you book it; OMG emails the confirmation once your order goes through, so check the duration it names.

Do I need any prior certification before sitting UAF Model User?

No. OMG lists no prerequisites for the Model User exam, so it can be your first OMG certification. The dependency runs the other way: a pass at Model User is required before you can sit any of the UAF Model Builder exams further up the programme.

Which UAF version does the Model User exam cover?

The exam is written against the UAF Modeling Language v1.2, the UAF Domain Metamodel v1.2, Appendix A on traceability, and SysML v1.6. Studying from a different edition risks answering on concepts that have been renamed, so check the edition on any material you use.

Select ratingPoorOkayGoodGreatAwesome

Rating: 4.8 / 5 (111 votes)