idef3_kbsi_report (1013870), страница 44
Текст из файла (страница 44)
There are three types of IDEF3 kits: objectkits, scenario kits, and description kits.A compilation from the completed scenario and objectkits for a given project containing all the scenarios in theIDEF3 description and their associated documentation.An approved description kit would represent one of thefinal deliverables in a development effort.Kits that address one or more objects and all or part oftheir associated documentation. The items which mayappear in an object kit include Object Schematics,elaborations, etc.
packaged for review and comment.Kits that address one scenario and all or part of itsassociated documentation. The items which may appearin a scenario kit include Process Schematics, associatedUOB decompositions, UOB and link elaborations, etc.packaged for review and comment.An extension to the kit cover sheet used when more spaceis needed to list the contents of a kit.A structured document that identifies the materialassembled as an IDEF3 kit, the review requirements, andan index to the contents of the kit.A review and approval process used to validate IDEF3process descriptions.A syntactic element of the IDEF3 Schematic Languageused to connect other IDEF3 syntactic elements.
Linksdenote significant relationships among UOBs, ObjectStates, and Objects. Examples of the types of relationsthat can be highlighted by IDEF3 links include temporal,logical, causal, natural, and conventional.A specialization of precedence links that adds furtherconstraints over and above the activation semantics ofsimple precedence. See Link, Precedence.219Link, DashedLink, First-orderLink, PrecedenceLink, RelationLink, Second-orderLink, Strong transitionLink, TransitionMethodModelNeeds statementA syntactic element of the IDEF3 Schematic Language,used in Process Schematics to highlight the existence of a(possibly constraining) relationship between two UOBs.Dashed links carry no predefined semantics.
For thisreason, they are often referred to as s or User-Definedlinks.Relations that hold between first-order objects.A syntactic element of the IDEF3 Schematic Languageused to express temporal precedence relations betweeninstances of one UOB and those of another.A syntactic element of the IDEF3 Schematic Languageused in Object Schematics to express additional relationsthat hold between objects, between objects and objectstates, between object states, and so forth.Relations that hold between first-order objects andsecond-order objects, properties, or relations; andrelations that hold between second-order objects,properties, and relations.A specialization of transition links that conveys theadditional information that the object involved in theoriginating state of a transition is the same object as thatin the final state of the transition.A syntactic element of the IDEF3 Schematic Languageused to express the relation transitions-to between somesource state(s) and some other destination state(s) in anIDEF3 Object Schematic.An organized, single-purpose discipline or practice foraccomplishing some set of tasks.
The IDEF methods arespecifically designed to accelerate the learning processand help novice practitioners emulate the performance ofhighly experienced individuals engaged in a particularanalysis or design activity. IDEF methods guide usersthrough a disciplined approach, consistent with goodpractice experience, to achieve consistently high levels ofperformance (quality and productivity)An idealized system of objects, properties, and relationsthat has been designed to imitate, in certain relevantrespects, the character of a given real-world system.Models are idealized systems which are assumed to be“close enough” to provide reliable predictors for thepredefined areas of interest within a domain.A statement that records the source of the request (personor project) and paraphrases the objectives of the project.220Note boxObjectObject, First-orderObject, Second-orderObject StateOccurrenceProcessPropertyPurposeA syntactic element of the IDEF3 Schematic Languagethat may be used to emphasize the participation ofparticular objects or relations associated with the IDEF3element to which it is attached, to tie in specific examplesof referenced data or objects (e.g., screen layouts), tohighlight special constraint sets associated with a givenelaboration, and so forth.An individual or class of individuals that participate in aprocess.
See individual.See individual.Classes of individuals and first-order relations are secondorder objects. See individual and First-order link.An individual or class of individuals that exhibit aspecific property or condition (generally indicated by anadjective rather than a common noun). For example, aweapon system development program undergoes anumber of different phases that may be viewed as statetransitions inaugurated by milestone decisions.An instance of a UOB within a scenario activation.“Occurrence” is also used to indicate the use of an IDEF3pool item (i.e., Scenario, UOB, Object, Object State) insome portion of an IDEF3 Process Description. Forexample, the same UOB pool item may be used more thanonce in the same Process Schematic.A real-world event or state of affairs involving one ormore individuals over some (possibly instantaneous)interval of time.
Typically, a process involves some sortof change in the properties of one or more of theindividuals in the process. Sometimes referred to asprocess instance.An abstract, general feature or characteristic that ismultiply instantiable; that is, it can be shared by distinctindividuals.The object or end to be attained by engaging in IDEF3description development activity. That purpose may besimply to document a process—in which case thedevelopment of schematics and elaborations is an endunto itself. In most cases, however, IDEF3 descriptiondevelopment is undertaken to assist with some discoveryor decision-making activities.221Purpose statementReferentRelationRelation, TemporalRole, AnalystRole, CommentorRole, LibrarianRole, Project leaderRole, ReaderRole, ReviewerRole, Team memberA written declaration specifying the 1) main objective(s)of the effort, 2) needs that the description must satisfy,and 3) questions or findings that the client wantsanswered.
The purpose statement can be separated intotwo parts, 1) defining a Needs Statement and 2) definingthe information goals in terms of how the processdescription will be used. The purpose statement isdocumented on an IDEF3 Description Summary form.A syntactic element of the IDEF3 Schematic Languageused to refer to a UOB scenario or Transition SchematicAn abstract, general association, or connection that holdsbetween two or more objects. Like properties, relationsare multiply instantiable (i.e., it can be shared by distinctobjects.
The objects among which a relation holds in aninstance are known as its arguments.A relation between temporal points or intervals such asbefore, during, overlaps and so forth.IDEF3 expert who is the primary developer of the IDEF3description.IDEF3 project team member responsible for reviewingdraft IDEF3 descriptions and making written critiques.A person assigned the responsibility of maintaining filesof documents, making copies, distributing IDEF3 kits,and keeping records.An administrative role that carries the responsibilities foroverseeing and guiding an IDEF3 descriptiondevelopment effort.
In particular, the project leader isultimately responsible for the outcome of the descriptiondevelopment effort, team organization and leadership, andschedule and budget management.IDEF3 project team member responsible for reviewingdraft IDEF3 descriptions but who is not responsible forproviding written comments.IDEF3 project team member knowledgeable of theapplication domain and/or the IDEF3 method andresponsible for reviewing and/or commenting on draftdescriptions and documents. Team members and domainexperts can be reviewers. See also reader andcommentor.A person involved with the IDEF5 ontology descriptionproject.222SchematicSchematic, ProcessSchematic, ObjectSchematic, TransitionSchematic, EnhancedTransitionScenarioSource materialSystemUnit of Behavior (UOB)UOB BoxUOB, ChildUOB, ParentValidationValidation, SyntacticA connected diagram constructed from the lexicon of theIDEF3 schematic language, in accordance with thesyntactic guidelines of the language.
A visualization,produced using the IDEF3 schematic language, that aidsin the construction of process descriptions.An IDEF3 schematic supporting the capture and displayof a process-centered view of a scenario.An IDEF3 schematic supporting the capture and displayof an object-centered view of one or more scenario(s) ofinterest.A type of Object Schematic characterizing the statetransitions traversed by participating objects in aninstance of the scenario (or process kind).A Transition Schematic that includes context-settinginformation about the objects and relations that arerelevant to the scenario but which do not exhibit the statechange behavior of direct interest.In the context of its decomposition, any UOB is ascenario.A textbook, a research article, an enterprise-specificdocument such as a policy manual or a procedure manual,a set of an interview notes, or direct observation notes thathas relevant information to the process descriptiondevelopment project.A collection of physical and/or conceptual objects thatwork together to achieve common objective.A term used in IDEF3 to describe types of “happenings.”Concepts such as function, process, scenario, activity,operation, decision, action, event, procedure, and so fortheach represent “happenings” involving somecircumscribed behavior.
The term UOB is used toencapsulate concepts such as these.A syntactic element of the IDEF3 Schematic Languageused to represent a real-world process.A UOB in a decomposition.A UOB, acting in the role of a scenario, that establishesthe context for a process description.The process of checking and ensuring that the IDEF3process description constructed is both syntactically andsemantically correct. A primary means of validatingIDEF3 process descriptions is through the review andapproval of kits.The process of checking and ensuring that the IDEF3schematic constructed conforms to the grammatical rulesof the IDEF3 language.223Validation, SemanticViewpointThe process of checking and ensuring that the statementsmade in the IDEF3 description accurately capture theassertions of the domain expert.The perspective taken while examining or describing asystem or process. Role-specific and objectiveviewpoints are captured using IDEF3’s UOBdecomposition mechanism.224.
![](https://s.studizba.com/z.php?f=/templates/si/i/noavatar.png&w=100&h=100&t=1"){kind=avatar}
