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.
2. Introduction to the Unified Modeling Language
This introduction to the UML covers symbol usage, definitions, and creating diagrams. The UML standardizes what diagrams with what symbols for what situation. The UML is complete with diagrams for analysis, design, and coding. Use use case diagrams to document how users (actors) use a system (a use case). Use class and object diagrams for the design and coding of a system. A class is the prototype for an object. An object has attributes (properties) and the current values of those properties is the current state of the object.
3. 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.
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. 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."
6. 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.
7. 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.
9. 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).
10. 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.
1. Introduction to the Unified Modeling Language
This introduction to the UML covers symbol usage, definitions, and creating diagrams. The UML standardizes what diagrams with what symbols for what situation. The UML is complete with diagrams for analysis, design, and coding. Use use case diagrams to document how users (actors) use a system (a use case). Use class and object diagrams for the design and coding of a system. A class is the prototype for an object. An object has attributes (properties) and the current values of those properties is the current state of the object.
2. 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.
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.
4. 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. 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).
8. 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."
9. 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.
Analyst
Print This
