Tcl/TK (Tool Command Language) is a scripting language based on strings, interpreted at run time. These features allow it to be portable on different operating systems.
Its syntax has only twelve rules, but it has all the elements needed to create programs in almost any domain quickly. It allows the development of graphical applications running on Windows, Linux, MacOSX and many other platforms.
Running a TCL script
There are three different ways to run a script written in TCL:
1. Running the command in a Wish console (interactive mode);
2. Run a script in a console file, using the source command:
source <filename.tcl>
3. Invoking a TCL script from an icon.
Unified Modeling Language (UML) is a standard language for describing software models and specifications. The language was created by the Object Management Group (OMG) consortium, which has also produced the message exchange standard among CORBA systems.
The UML was basically developed to represent the complexity of object-oriented programs, the foundation of which is the structuring of programs by classes, and their instances (also called objects). However, due to its efficiency and clarity in representing abstract elements, UML is used beyond the IT domain.
This is why there are UML applications for project management for Business Process Design, etc.
The first version of UML, UML 1.0, appeared in 1990 as a reaction to the numerous modeling languages offered on the market. UML has Grady Booch, Ivar Jacobson and James Rumbaugh as its founders, so-called “the three Amigos.”
They developed the language based on already existing modeling languages, but incomplete as a range of functionalities.
These include OOSE, RDD, OMT, OBA, OODA, SOMA, MOSES, and OPEN/OML.
UML offers a wide range of diagrams for modeling different situations within a software development project:
1. Activity diagram
As the name suggests, this type of UML diagram is used to represent the performance of an activity running the program.
2. Component diagram
There are diagrams that are used in the design of a system architecture, when different components of the software system (also called subsystems) interact with each other through interfaces.
3. Class diagram
It is used for the visual representation of classes and inter dependencies, taxonomy and multiplicity relations between them. Class diagrams are also used for the actual representation of class courts, therefore objects, and of the concrete links between them.
4.Package diagram
It is used to represent the inter dependencies and relationships between packages forming a program. Packages in this sense represent containers that contain classes and are a feature of some programming languages such as Java or C Sharp.
5. Sequence diagram
It is used especially during the development of subsystems and helps to identify the relationships between objects during a certain operation. For example, the relationship between the client object John and the object commands the number 1234 during the operation of completing an order.
6. Diagram use cases
Due to its simplicity, it is used in particular in the discussions between the software developer and clients or users. Use case diagrams represent the interaction between the elements outside a system (also called actors) and the system. In the case of these diagrams, the action performed by the system at the actor’s interaction is presented, but the way the system performs that action does not have to be represented in such a diagram, the BlackBox concept.
7. Deployment diagram
It is used in the design of the system architecture, having the purpose of representing the physical distribution of the different elements of the system. For example, the distribution of a system that is composed of a server, routers, and other external components, including software.