Telelogic UML Suite // Note: The English is limited, many places are a bit obscured, please understand.
// I saw the special less information about Telelogic, so I took some things I organized to share :)
Background: Telelogic provides a toolset that covers demand management, change management to visualization and testing the entire software development cycle. Founded in 1983, the company is headquartered in Sweden, China Headquarters in Beijing, 10,000 employees. Recently, the three major products in the Chinese market: Demand Management Tools DOORS, Change Management Tools Synergy, and Visual Software Toolset TAU. These include high-level modeling tools UML Suite, Design and Implementation Tools SDL Suite, Test Tools TTCN Suite and Logiscope, resulting in all key issues in software and system development cycles. The Telelogic TAU is a software tool for analysis, design, running, and testing real-time systems, especially applicable to helping real-time system users to solve problems. It reflects the needs of real-time system markets on the design language, and can quickly solve the unique problem in the field of concurrency, signaling transmission. Compared to similar products, the greatest feature of Telelogic TAU is in real-time language SDL and MSC formation, which helps users use simulations in the initial design, confirm and verify design, and ensure that every detail of the system is running correctly. The Telelogic Tau complete customized code generator can compile specifications into executable code, and minimize the number of errors, users to use more time for real engineering work. In addition, Telelogic TAU also provides automatic test sets of generating functions, ensuring consistency with system specifications. The TTCN test language it supports is determined by a number of World Standards Organization and to define test scripts. By using Telelogic Tau, users can analyze user needs, design software and construction test sets in different advanced languages. When the system development is completed, the test set can be output to external devices to test the final product.
Summary: The Telelogic TAU is an object-oriented toolset that covers the development of the software development. It is based on a series of internationally recognized standardization, standardized languages and notes methods such as UML, SDL, TTCN. It covers all phases of event-driven, demand analysis, design and testing of real-time software applications.
Development steps: UML Suite provides a project level, including four default software development phases analysis Analysis system design systemDesign object design ObjectDesign executive Implementation
The goal of the analysis phase is to specify the needs of the application, which will ensure that end users and developers have agreed and mutually understand the functionality of the application. The following chart is very important in the development phase. Use Case Diagram, Sequence Diagram, and Collaboration Diagram Describes the scenario of this application must engage in Scenarios. Class Diagram describes the needs of this class and is described by several charts mentioned above.
The goal of the system design system design phase is to describe the structure of the application, split the application into the package package. The ideal application structure maximizes the interaction between different classes in the middle of the package. Minimization is the interaction between different packages (coupling). In the system design phase, the class chart Class Diagram from the analysis phase describes communication between different classes, which can help you define the boundary of the package, that is, you can determine different packages according to class diagrams. Package, Package is usually defined as a structural system.
The object design phase of the object design object is to explain and improve the class diagram Class Diagram of each package until they can be detailed enough to execute. Most behaviors in this stage relies on your execution environment. If you use UML Suite to generate code, in this stage, you should pay special attention to the details generated by the code generation. You can also create a directory for code existing in the class so you can reverse them. The execution phase target generation and refine application code, UML Suite provides a code generator for a variety of languages. The class diagram in the object design is the source generated by the code. With this information, UML Suite generates code to execution classes, including relationships, properties, and operations between them. Note that your model does not fully illustrate your app, you must modify these generated code to complete this application. To ensure that this model can still be feasible in the middle of the development cycle, the code generator retains your last regeneration code editing.
The steps below the workflow outline the basic workflow of the UML Suite project. 1 Create a project. 2 Create a setup version. 3 Create an analysis phase version in this setting version. 4 Create one or more package versions in this analysis phase version. 5 Create and transplant the chart in each package version, the version of the development package is the target of the current phase. 6 Alternatively, create a document version for each package version, generate a formal project document. 7 Mobile package version to the next stage: Create a new phase of the version in your setup version, then import the package version to the new phase version. 8 Repeat 5 to 7 steps until you have moved all packages in all phases.
In the analysis phase, you build models for the project, do not need to consider technical issues, including what operating system, database, and what kind of programming language is used. End users must be able to understand the model of the analysis because they must be recognized. The analysis should not include the conclusion of the execution. This analysis model declares those constraints that must be set to be made. In the middle of this stage, the problem of worrying about the implementation will stop you from understanding your customers' needs.
In the system design phase, your design of your application, determine the subsystem, and allocate subsystems into a clear hardware. Your goal is to create a hierarchical structure for this system, resolve these classes that need to be used in the establishment of functionality and organizations, so that the definitions and grouping relationships stored in the package. --Translation issue. Reads as follows: In the System Design phase, you design the application architecture, identify subsystems, and allocate the subsystems to specific hardware Your objective is to create a high-level structure of the system, figuring out the classes required to build the functionality and. Organizing The Related and Stored Groups. In the system design phase, your focus lies in those elements you need to solve, these you need to care about graphical user interface, database management system, and hardware and software settings. .
Object design and execution phases need to work according to the target language used by the UML Suite Code Builder. If you don't have to use UML to generate code, you don't have to use these two phases.
The generation of documents. At the end of each phase, the project team often needs to make a formal project document, you can use Docit or DOCEXPRESS to generate these documents from your model.
Project Management Tools, including configuration management Configuration Management, version control Version Control, and Access Control Access Control, allow you to adjust the software development project in your entire organization. Version and setting rules Before you start to perform specific steps, you should understand the rules of the version and settings: Each version of the object can be in three states, in work, freeze or back up. The version in the work can be modified, so an object only has a state in the work at a time. A project can accommodate multiple settings, no matter what, a setting can only include a detail phase, package, or file version. Any version of the object is not frozen when it is heavy in one setting.
Object versions, UML Suite allows you to create multiple versions of an object. Each version has three states, in work, freezing or backup. The work version is stored in the middle of the library, which can be modified, in order to prevent a conflict of an object, UML Suite ensures that only one configuration content is only one configuration. The freezing version is stored in the library, but it cannot be modified. When you create a new object version, the last version is automatically frozen. The backup version is also frozen, stored outside the library, if needed, can be returned to the library.
The setting allows multiple developers to work on the same application without hindering others. Each setting defines a precise developer's object version that is used, in order to prevent conflicts when an object change, the object of UML Suite works only in one setting.
