I.T. Discussion Community!
-Collapse +Expand
Search Analyst Group:

-Collapse +Expand Analyst Store

Prestwood eMagazine

July Edition
Subscribe now! It's Free!
Enter your email:

   ► KBAnalyst Knowledge Base  Print This    Computer Dictionary All Groups  

Analyst Definitions Page

These Definitions are contributed by you (our online community members). They are organized by our knowledge base topics. Specifically, by the Analyst sub-topics.

Contribute a Definition

7 Analysis & UML Definitions

Group: Analysis & UML

Topic: Analysis & UML

#1. Software Artifact - Any nugget discovered and developed and used during software development and maintenance. Examples are requirement items, design items, diagrams, test script, and even code itself. In PSDP, a PSDP Artifact is a specific implementation of the generic software artifact. A PSDP Artifact is used to work with a software feature from inception through testing. It links together a task, requirement item, design item, and test script. You can edit a PSDP artifact as a whole or expand any of the four linked items to include more details.

Topic: Data Flow Diagrams (DFD)

#2. Data Flow Diagram (DFD) - DFDs document a process by documenting the flow of data throughout the process. They depict how data interacts with a system. They can be used to engineer a new process, document an existing process, or re-engineer an existing process. Traditional Data Flow Diagrams use four (4) symbols, a square, an arrow, a circle, and parallel lines.

Topic: Unified Modeling Language (UML)

#3. Actor (UML) - An actor is a person or system that fills a role and interacts with another system. An actor supplies a stimulus to the system. When establishing actors of your system, do not think in terms of a specific person, think in terms of their role. Do not name an actor the name of the person filling the role. If Bob is our Sales Clerk, name your actor Sales Clerk (not Bob).
#4. Association - An Association is a generic relationship between two classes and is represented a line connecting the two classes. This line can be qualified with the type of relationship, and can also feature multiplicity rules such as one-to-one, one-to-many, many-to-many, 0 or 1 to many, etc.
#5. Dependency - A "uses-a" relationship. For example, when a class uses another class as a member variable or a parameter. A "uses-a" relationship forms a dependency on a class. A Dependency relationship is indicated by a dotted line with an arrow.
#6. Generalization - Where you generalize specific classes into general parent classes or take general parent classes and specialize them as needed in child classes. A Generalization relationship is the equivalent of inheritance in object oriented programming (OOP). A Generalization relationship is an "is-a" relationship and is indicated by an arrow with a hollow arrowhead pointing to the parent class. For example, a Honda Accord "is-a" Car.
#7. UML Artifacts - In UML 1.x, many UML users referred to the UML diagrams as UML Artifacts. Starting with UML 2.0, a UML Artifact is defined as a physical unit, such as an application executable, database, file, script, etc. Only artifacts live on physical nodes; classes and components do not have "location."

Follow PrestwoodBoards on: 

©1995-2020 PrestwoodBoards  [Security & Privacy]
Professional IT Services: Coding | Websites | Computer Tech