Role Description

[Work on own experiences/completions]



.System Analyst

Abbreviation:
Organisation Unit: .
Task: Supports the system analysis, the use case modelling, the analysis and communication in a project.

  • Analyses, identifies, values and describes the requirement on the system which has be developed. Analyses the usefulness, the completeness and contradictions of the requirements.
  • Identifies and describes system use cases and agreed them with the domain experts, user, developers, etc.
  • Is involved actively in defining concepts for solution possibilities (transistion from analysis to design)
  • Checks whether staff follows the guidelines and standards.
Ideal-Qualification:
  • Knows the UML very well.
  • Has at least 2 months experience with the relevant modeling tool.
  • Has at least 6 months practical experience in object oriented analysis and design, exspecially with use case analysis and description, modeling classes, specification of operations and attributes incl. Invariants, exceptioins, etc.
  • Knows the technical and domain architecture which is relevant for the project.
  • Understands the technical terms of the user, clients and contractor.
  • High communicative abilities and social competence are important and necessary.
  • Has knowledge in presentation.
  • Knows the user concept well.

  • .System Analyst is involved in the following activities:




    responsible: A-15 Requirement specification
    A-26 Specify a dialog
    A-28 Identify reference models
    A-67 Describe the state model
    A-306 coming soon
    A-68 Modelling Interaction Models
    A-74 Identify and specify data base queries
    A-81 Identify and describe exceptions and possible errors
    A-128 Define a preliminary study
    A-137 Define a migration concept
    A-138 Prepare the data- and system migration
    A-157 Describe data base mapping
    A-165 Identify Primitive Data Types
    A-176 Define an outline of the requirement specification
    A-195 Identify Stakeholders
    A-200 Identify system use cases
    A-201 Collection of material
    A-204 Set up a glossary
    A-206 Describe the system interface
    A-215 Develop a sequence or a collaboration diagram
    A-226 Requirement workshop
    A-228 Requirement workshop
    A-229 Detail system use case
    A-230 UML-business-class-model
    A-231 Identify and describe output (artifact)
    A-235 Identify non-functional requirements
    A-236 Identify features
    A-237 Workshop: Define the modelling focus and describe the aims of the company
    A-238 Model the organisation units
    A-239 Define the aim and the purpose of the business process modelling
    A-240 Identify active business partners
    A-241 Workshop: Identify the business use cases of the active business partners
    A-242 Identify supporting business use cases
    A-243 Identify business employees and develop an actor model
    A-244 Define business processes
    A-245 Describe business processes
    A-247 Describe the business use cases essential
    A-248 Modeling business use case sequences
    A-269 Optimize and consolidate the business use case sequences
    A-270 Describe business use cases in detail
    A-271 Identify the organisational assignment and reorganise the dependencies, if necessary
    A-272 Develop a business class model
    A-273 Develop a business use case model
    A-274 Define State Models for State Relevant Business Classes
    A-275 Describe business requirements and rules
    A-276 Derive and identify system use cases
    A-282 Change or add request for requirements
    A-284 Identify Enumerations (tables of key values)
    take actively part in: A-252 Restructurine Workshop
    A-230 UML-business-class-model
    A-231 Identify and describe output (artifact)
    A-232 Develop a design class modell and an evaluated sub system model
    A-235 Identify non-functional requirements
    A-249 Effort Estimation Workshop
    A-229 Detail system use case
    A-250 Risk management workshop (risks and success factors)
    A-260 Develop a domain architecture model
    A-253 Make experience report of the project
    A-257 Update the test concept
    A-256 Define the test concept
    A-258 Run a code review
    A-207 Exploratory interface-prototyping
    A-246 Develop a Sub System Model and a first draft of the business class model, if necessary
    A-305 coming soon

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