In Visual Studio, you can draw a use case diagram to summarize who uses your application or system, and what they can do with it. To create a UML use case diagram, on the Architecture menu, click New UML or Layer Diagram.For a video demonstration, see Organizing Features into Use Cases.To see which versions of Visual Studio support this feature, see Version support for architecture and modeling tools.With the help of a use case diagram, you can discuss and communicate:The scenarios in which your system or application interacts with people, organizations, or external systems.The goals that it helps those actors achieve.The scope of your system.A use case diagram does not show the detail of the use cases: it only summarizes some of the relationships between use cases, actors, and systems. In particular, the diagram does not show the order in which steps are performed to achieve the goals of each use case. You can describe those details in other diagrams and documents, which you can link to each use case. For more information, see Describing Use Cases in Detail in this topic.The descriptions you provide for use cases will use several terms related to the domain in which the system works, such as Sale, Menu, Customer, and so on. It is important to define these terms and their relationships clearly, and you can do that with the help of a UML Class Diagram. For more information, see UML Class Diagrams: Guidelines.Use cases deal only in the functional requirements for a system. Other requirements such as business rules, quality of service requirements, and implementation constraints must be represented separately. Architecture and internal details must also be described separately. For more information about how to define user requirements, see Model user requirements.The examples used in this topic relate to a Web site on which customers can order meals from local restaurants.Elements in a use case diagramAn actor (1) is a class of person, organization, device, or external software component that interacts with your system. Example actors are Customer, Restaurant, Temperature Sensor, Credit Card Authorizer.A use case (2) represents the actions that are performed by one or more actors in the pursuit of a particular goal. Example use cases are Order Meal, Update Menu, Process Payment.On a use case diagram, use cases are associated (3) with the actors that perform them.Your system (4) is whatever you are developing. It might be a small software component, whose actors are just other software components; or it might be a complete application; or it might be a large distributed suite of applications deployed over many computers and devices. Example subsystems are Meal Ordering Website, Meal Delivery Business, Website Version 2.A use case diagram can show which use cases are supported by your system or its subsystems.
The network layer is responsible for logical connection setup, data forwarding, routing & delivery. This therefore means that the network (third) layer of the OSI model is responsible for allowing one computer to share information with other computers.
Phantom inspection is the process of finding various defects in the documents according to the . Basically, it is a group of meeting that usually provide the synergy effects and the maximum defects can easily be detected. This entire process is known as phantom inspector.
It is also made some assumptions regarding the inspection that is made by one and more than one individual.
This process are usually done by inspecting the each operation output with the given output requirements.
Software development life cycle (SDLC) can be defined as a strategic process or methodology that defines the key steps or stages for creating and implementing high quality software applications.
An incremental model refers to the process in which the requirements or criteria of the software development is divided into many standalone modules until the program is completed.
Hence, an incremental method typically involves developing a system through repeated cycles and smaller portions at a time, enhancing and evolving the system over time.
In SDLC, a waterfall model can be defined as a process which involves sequentially breaking the software development into linear phases. Thus, the development phase takes a downward flow like a waterfall and as such each phase must be completed before starting another without any overlap in the process.
Also, a spiral model can be defined as an evolutionary SDLC that is risk-driven in nature and typically comprises of both an iterative and a waterfall model. Spiral model of SDLC consist of these phases; planning, risk analysis, engineering and evaluation.
Spanning Tree Protocol is used to allow path redundancy in the network without creating cycles/circles also called loops.
When two parts of the switched network are connected via two or more Layer 2 switches this result in a loop.
This affects the performance of the network as the result of broadcast packets flooding.
STP puts one port of the switch to forwarding mode and the rest of the ports within the same part of the network to the blocking mode to avoid broadcast packet flooding. STP puts all the ports that are allowing redundant paths to blocking mode and the one port that is left after this is placed in forward mode.
Spanning Tree Algorithm is used by STP to determine the optimal path of switch to the network.
Bridge Protocol Data Units are used to share the information about the optimal path determined by the spanning tree algorithm with other switches.
This information helps STP to eliminate the redundant paths.
So this is how STP allows only one active path to the destination while blocking all other paths to avoid switching loop.
