IT SOLUTIONS
Your full service technology partner! 
-Collapse +Expand
Analyst
Search Analyst Group:

Advanced
-Collapse +Expand Analyst Store
PRESTWOODSTORE

Prestwood eMagazine

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

   ► KBAnalyst Knowledge Base  All Groups   Print This   

Analyst Flashcards Library

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

Contribute a Flashcard

8 Analysis & UML FlashCards

Group: Analysis & UML


Topic: Analysis & UML

Q&A: Business Analyst: Entities and Attributes
Question: Should the analyst be responsible for collecting domain entities and attributes?

Answer:

If the analyst is qualified sure, but if they're not, don't push it. Many times a resource was made the analyst not because they are a great analyst but because they have great people skills, know the domain well, and can document process well. Under that scenario, I prefer a programmer analyst work with the business analyst to identify entities and attributes. If the analyst is not good at documenting process, find a new analyst.

In PSDP, we overcome this problem by creating the database and GUI prototype during the requirements phase. By forcing the creation of the database while discovering what the client wants, you force the identifying of entitities and attributes.

In UML, sometimes analysts create class diagrams to create the database. The Data Model is a much better choice.

Posted By Mike Prestwood, Post #100969, KB Topic: Analysis & UML
Definition

Software Artifact

Definition: 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.
Posted By Mike Prestwood, Post #100939, KB Topic: Analysis & UML



Topic: Data Flow Diagrams (DFD)

Definition

Data Flow Diagram (DFD)

Definition:

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.

DFDs are also known as Data Flow Graphs, Bubble Charts, Petri Networks, Yourdon/DeMarco notation, and Gane/Sarson notation.

Posted By Mike Prestwood, Post #100888, KB Topic: Data Flow Diagrams (DFD)



Topic: Unified Modeling Language (UML)

Definition

Actor (UML)

Definition: 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).
Posted By Mike Prestwood, Post #100942, KB Topic: Unified Modeling Language (UML)
Definition

Association

Definition: 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.
Posted By Mike Prestwood, Post #101262, KB Topic: Unified Modeling Language (UML)
Definition

Dependency

Definition: 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.
Posted By Mike Prestwood, Post #101260, KB Topic: Unified Modeling Language (UML)
Definition

Generalization

Definition: 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.
Posted By Mike Prestwood, Post #101259, KB Topic: Unified Modeling Language (UML)
Definition

UML Artifacts

Definition:

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."

Posted By Mike Prestwood, Post #100977, KB Topic: Unified Modeling Language (UML)
-
  Load Time=less than 1 second.
 
Print This
-
 
Have a question? Need our services? Contact us now.
--Mike Prestwood

Call: 916-726-5675

email: info@prestwood.com


-
 
Connect With Us...
PrestwoodBoards
Join Us!
Facebook
Like our page!!!
Twitter
Follow us!
LinkedIn
Join Group
YouTube
View channel.
Go ahead!   Use Us! Call: 916-726-5675 


©1995-2014 Prestwood IT Solutions.   [Security & Privacy]   Made in the U.S.A..   No H1-B.   No offshoring.