Role Description

[Work on own experiences/completions]

.Domain Expert

Abbreviation: DU
Organisation Unit: .
Task: Expert of the application scope of a project or of a part of it.
  • Is expert for the terms of the area of application (technical terms).
  • Knows the existing system in the sourroundings of the area of application.
  • Knows all important contact person or is able to identy or contact them fast.
  • Has knowledge, whether things of the area of application are stable or not, which one are changing and what quality they have.
  • Has practical experience in object oriented analysis and design, class modeling, activity modeling and interaction modeling.
  • Knows the technical and domain architecture which is relevant for the project.
  • High communicative abilities and social competence are important and necessary.
  • Has knowledge of the user concept.

  • .Domain Expert is involved in the following activities:

    responsible: A-71 Check and update the glossary
    A-142 Train the hotline, the support and the multiplier
    A-174 Define or update Enumeration Contents (key value tables)
    A-233 Develop a use case model with associations between system use cases
    A-289 Check and update the glossary
    A-290 Check and update the glossary
    advisory: A-16 Plan iterations and deliveries
    A-59 Realize and Test batch-programs
    A-58 Identify and specify batch-programs
    A-128 Define a preliminary study
    A-305 coming soon
    A-294 coming soon
    A-95 Identify and specify project external requirements
    take actively part in: A-236 Identify features
    A-243 Identify business employees and develop an actor model
    A-245 Describe business processes
    A-247 Describe the business use cases essential
    A-248 Modeling business use case sequences
    A-7 Identify and Classify System Interfaces
    A-241 Workshop: Identify the business use cases of the active business partners
    A-18 Check the mile stone achievement
    A-237 Workshop: Define the modelling focus and describe the aims of the company
    A-235 Identify non-functional requirements
    A-244 Define business processes
    A-231 Identify and describe output (artifact)
    A-153 Run the User Test
    A-229 Detail system use case
    A-240 Identify active business partners
    A-274 Define State Models for State Relevant Business Classes
    A-228 Requirement workshop
    A-200 Identify system use cases
    A-242 Identify supporting business use cases
    A-239 Define the aim and the purpose of the business process modelling
    A-238 Model the organisation units
    A-306 coming soon
    A-276 Derive and identify system use cases
    A-226 Requirement workshop
    A-272 Develop a business class model
    A-273 Develop a business use case model
    A-271 Identify the organisational assignment and reorganise the dependencies, if necessary
    A-270 Describe business use cases in detail
    A-269 Optimize and consolidate the business use case sequences
    A-28 Identify reference models
    A-275 Describe business requirements and rules

    OEP - Object Engineering Process, v2.0, 06.11.2006 11:08:20, Copyright © 2003 by eG