The SvcV-10c “Services Event-Trace Description” provides a time-ordered examination of the interactions between services functional resources. Each event-trace diagram should have an accompanying description that defines the particular scenario or situation. The SvcV-10c is valuable for moving to the next level of detail from the initial solution design, to help define a sequence of service functions and service data interfaces, and to ensure that each participating resource or Service Port role has the necessary information it needs, at the right time, to perform its assigned functionality. 
The intended usage of the SvcV-10c includes: 
- Analysis of resource events impacting operation
- Behavioral analysis
- Identification of non-functional system requirements
The SvcV-10c specifies the sequence in which Resource Flow elements are exchanged in context of a resource or Service Port. Services Event-Trace Descriptions are sometimes called sequence diagrams, event scenarios or timing diagrams. The components of a SvcV-10c include functional resources or service ports, owning performer, as well as the port which is the subject for the lifeline. 
Specific points in time can be identified. The Resource Flow from one resource/port to another can be labeled with events and their timing. The Service Event-Trace Description provides a time-ordered examination of the Resource Flow elements exchanged between participating resources (external and internal) or service ports. Each Event-Trace diagram should have an accompanying description that defines the particular scenario or situation.
The SvcV-10c is typically used in conjunction with the SvcV-10b “Services State Transition Description” to describe the dynamic behavior of resources. The data content of messages that connect Resource Flows in a SvcV-10c model may be related, in modeling terms, with Resource Flows (interactions, in SvcV-1 “Services Context Description”, SvcV-3a “Systems-Services Matrix”, and SvcV-3b “Services-Services Matrix”), Resource Flows (data, in SvcV-4 “Services Functionality Description” and SvcV-6 “Services Resource Flow Matrix”) and entities (in DIV-3 “Physical Data Model”) modeled in other models.
- The DoDAF descriptions in this website are very generic and are mostly taken from the DoDAF Architecture Framework website. Make sure you visit the actual website for the most update information and a more thorough explanation of each viewpoint.
- DoDAF Version 1.0, although outdated, has some good examples on how to construct AV’s, OV’s, and SV’s.
AcqLinks and References:
-  DoDAF Architecture Framework Version 2.02
- DoD Architecture Framework Working Group Version 1.0, Volume 1: Definition and Guideline, 9 Feb 04 (Old Version)
- DoD Architecture Framework Version 1.0, Volume 2: Product Description, 9 Feb 04 (Old Version)
- Website: DoDAF Architecture Framework – DoD Deputy Chief Information Officer
- Website: DoDAF Version 2.02 Journal
- Website: DoDAF Meta Model (DM2)
- Website: DoD Information Enterprise Architecture
- Website: OMB Enterprise Architecture Assessment Framework (EAAF)