question archive 1)Technical Design Diagram 2)Logical Data Flow 3)Updated IT Technical Specification Template to reflect any requested changes and entries to the "Diagram Attachments & Links" section

1)Technical Design Diagram 2)Logical Data Flow 3)Updated IT Technical Specification Template to reflect any requested changes and entries to the "Diagram Attachments & Links" section

Subject:ManagementPrice:2.84 Bought6

1)Technical Design Diagram

2)Logical Data Flow

3)Updated IT Technical Specification Template to reflect any requested changes and entries to the "Diagram Attachments & Links" section. In this section, list the file names for the Technical Design Diagram and the Logical Data Flow (they will be in separate documents) along with a description of what they are. Separate the list by line, as seen in the example below:

 

The Technical Design Diagram shows the new and existing technical resources, separated by color The Logical Data Flow highlights the inputs and outputs of the proposed system

Both diagrams should be in UML design with as much detail.

For the technical design diagram, it would be a good idea to come up with a method (such as color) to identify which components are existing and which components need to be added as a part of the project. The Technical Design Diagram should show everything that will connect into the CRM as well as everything that will receive outputs from the CRM.

The Logical Data Flow should follow a similar pattern as the Technical Design Diagram but will focus on the types of data. Again, it would make sense to show which data lines exist already and which will be newly made.

The TDD is a diagram of the systems involved, and the LDF is a diagram of the data involved.

pur-new-sol

Purchase A New Answer

Custom new solution created by our subject matter experts

GET A QUOTE

Answer Preview

UML is an abbreviation that for Unified Modelling Language. This language is composed of diagrams that are used by both software engineers and system developers in creating the creation of visual representation of the artifacts of a certain software. Additionally, it helps in documentation, specifying and in the construction of certain artifacts of a certain software system. The UML has been proven to contain the best practices that are used in the construction of enormous and complex systems. The UML has been useful in business modelling , software modeling and even in other non-software related system.

IN summerly UML is used in to help people understand the strengths, flaws and even errors in a certain software system. 

UML was initially used in software engineering for general purpose engineering, however it has found its use in  business processes, and in monitoring of workflow. Flow charts have been replaced by UML due to wide range of features that have helped improve readability and its efficiency.

UML also shows the various characteristics of a program. It is however does not show the all the details used in the execution of a program

There are various strategies of how UML is implemented. One of the strategy is :

Forward design- This is a designing a sketch  using UML that is done before coding an application. The benefits of forward design is that it helps in capturing errors in the work flow 

Backward Design - This strategy is applied after coding. In this case the UML diagrams are drawn after coding has been done. The diagrams are drawn as a form of documentation.