Activity diagram for Multilevel Marketing Management (MLM) system

Activity diagrams are typically used for business process modeling, for modeling the logic captured by a single use case or usage scenario.


Initial node. The filled in circle is the starting point of the diagram.  An initial node isn’t required although it does make it significantly easier to read the diagram.
Activity final node. The filled circle with a border is the ending point.  An activity diagram can have zero or more activity final nodes
Activity.   The rounded rectangles represent activities that occur. An activity may be physical, such as Inspect Forms, or electronic, such as Display Create Student Screen.
Flow/edge.  The arrows on the diagram.  Although there is a subtle difference between flows and edges I have never seen a practical purpose for the difference although I have no doubt one exists.  I’ll use the term flow.
Fork.  A black bar with one flow going into it and several leaving it.  This denotes the beginning of parallel activity.
Join.  A black bar with several flows entering it and one leaving it.  All flows going into the join must reach it before processing may continue.  This denotes the end of parallel processing.
Condition.  Text such as [Incorrect Form] on a flow, defining a guard which must evaluate to true in order to traverse the node
Decision. A diamond with one flow entering and several leaving.  The flows leaving include conditions although some modelers will not indicate the conditions if it is obvious.
Merge.  A diamond with several flows entering and one leaving.  The implication is that one or more incoming flows must reach this point until processing continues, based on any guards on the outgoing flow.

• Partition. is organized into three partitions, also called swimlanes, indicating who/what is performing the activities (either the Applicant, Registrar, or System).
• Sub-activity indicator.  Indicates that the activity is described by a more finely detailed activity diagram.  
• Flow final.  The circle with the X through it.  This indicates that the process stops at this point

Use case diagram for multilevel marketing management system(MLM)

Use Case Diagram :-
Use case diagram is designed for visualizing and documenting the behavior of a system. The main notations of use case diagram include System (subject), Use Case, Actor, Association (communication link), Dependency and Generalization. Use case diagram is usually used in modeling the context of a system and requirements of system.

Elements of a Use Case Diagram:-

  1)Actors :- An actor portrays any entity (or entities) that performs certain roles in a given system.

                  An actor in a use case diagram interacts with a use case

2)Use case:-A use case in a use case diagram is a visual representation of a distinct business functionality in a  
                  system.
3)System boundary: -A system boundary defines the scope of what a system will be. A system cannot have  
                                infinite functionality.
               Use cases share different kinds of relationships. A relationship between two use cases is basically a dependency between the two use cases. 

Uml diagrams for multilevel marketing management system(MLM)

Context level DFD :-


STEPS TO DRAW A DATA FLOW DIAGRAM:-
Use a Data Flow Diagram (DFD) to show the relationships among the business processes within an organization to:
·   External systems,
·   External organizations,
·    Customers,
·   other business processes.


· Start from the context diagram.  Identify the parent process and the external entities with their net inputs and  
  outputs.
· Place the external entities on the diagram.  Draw the boundary. 
· Identify the data flows needed to generate the net inputs and outputs to the external entities.
· Identify the business processes to perform the work needed to generate the input and output data flows.
· Connect the data flows from the external entities to the processes.
· Identify the data stores.
· Connect the processes and data stores with data flows.
· Apply the Process Model Paradigm to verify that the diagram addresses the processing needs of all external entities.
· Apply the External Control Paradigm to further validate that the flows to the external entities are correct.
· Continue to decompose to the nth level DFD.  Draw all DFDs at one level before moving to the next level of decomposing detail.  You should decompose horizontally first to a sufficient nth level to ensure that the processes are partitioned correctly;  then you can begin to decompose vertically

errorprovider in c sharp

code:-

public void Get_errorprovider()

{

bool bb = true;

if (txt_name.Text==string .Empty )

{

errorProvider1.SetError(txt_name, "please enter Name");

bb = false;

}

}