Uml

Notas do Editor

• #2: Large enterprise applications - the ones that execute core business applications, and keep a company going - must be more than just a bunch of code modules. They must be structured in a way that enables scalability, security, and robust execution under stressful conditions, and their structure - frequently referred to as their architecture - must be defined clearly enough that maintenance programmers can (quickly!) find and fix a bug that shows up long after the original authors have moved on to other projects. That is, these programs must be designed to work perfectly in many areas, and business functionality is not the only one (although it certainly is the essential core). Of course a well-designed architecture benefits any program, and not just the largest ones as we've singled out here. We mentioned large applications first because structure is a way of dealing with complexity, so the benefits of structure (and of modeling and design, as we'll demonstrate) compound as application size grows large. Another benefit of structure is that it enables code reuse : Design time is the easiest time to structure an application as a collection of self-contained modules or components. Eventually, enterprises build up a library of models of components, each one representing an implementation stored in a library of code modules. When another application needs the same functionality, the designer can quickly import its module from the library. At coding time, the developer can just as quickly import the code module into the application.  
• #6: Não é possível avaliar tudo isso na implementação. O momento ideal é no projeto do software.
• #7: Modeling is the designing of software applications before coding. Modeling is an Essential Part of large software projects, and helpful to medium and even small projects as well. A model plays the analogous role in software development that blueprints and other plans (site maps, elevations, physical models) play in the building of a skyscraper. Using a model, those responsible for a software development project's success can assure themselves that business functionality is complete and correct, end-user needs are met, and program design supports requirements for scalability, robustness, security, extendibility, and other characteristics, before implementation in code renders changes difficult and expensive to make. Surveys show that large software projects have a huge probability of failure - in fact, it's more likely that a large software application will fail to meet all of its requirements on time and on budget than that it will succeed. If you're running one of these projects, you need to do all you can to increase the odds for success, and modeling is the only way to visualize your design and check it against requirements before your crew starts to code.
• #9: Modelos ajuda a pessoas iniciantes a se interarem do projeto mais rapidamente; Melhor errar no modelo; Modelar reduz a necessidade de retrabalho;
• #10: Cada notação gráfica possuía suas vantagens e desvantagens;
• #13: Ver versão; Em aperfeiçoamento questões como programação concorrente, etc.
• #14: The OMG's Unified Modeling Language™ ( UML® ) helps you specify, visualize, and document models of software systems, including their structure and design, in a way that meets all of these requirements. (You can use UML for business modeling and modeling of other non-software systems too.) Using any one of the large number of UML-based tools on the market , you can analyze your future application's requirements and design a solution that meets them, representing the results using UML 2.0's thirteen standard diagram types .  You can model just about any type of application, running on any type and combination of hardware, operating system, programming language, and network, in UML. Its flexibility lets you model distributed applications that use just about any middleware on the market. Built upon  fundamental OO concepts including class and operation , it's a natural fit for object-oriented languages and environments such as C++, Java, and the recent C#, but you can use it to model non-OO applications as well in, for example, Fortran, VB, or COBOL.  UML Profiles (that is, subsets of UML tailored for specific purposes) help you model Transactional, Real-time, and Fault-Tolerant systems in a natural way.  You can do other useful things with UML too: For example, some tools analyze existing source code (or, some claim, object code!) and reverse-engineer it into a set of UML diagrams. Another example: Some tools on the market execute UML models, typically in one of two ways: Some tools execute your model interpretively in a way that lets you confirm that it really does what you want, but without the scalability and speed that you'll need in your deployed application. Other tools (typically designed to work only within a restricted application domain such as telecommunications or finance) generate program language code from UML, producing most of a bug-free, deployable application that runs quickly if the code generator incorporates best-practice scalable patterns for, e.g., transactional database operations or other common program tasks. (OMG members are working on a specification for Executable UML now.) Our final entry in this category: A number of tools on the market generate Test and Verification Suites from UML models. 
• #16: What can you Model with UML? UML 2.0 defines thirteen types of diagrams, divided into three categories: Six diagram types represent static application structure; three represent general types of behavior; and four represent different aspects of interactions: Structure Diagrams include the Class Diagram, Object Diagram, Component Diagram, Composite Structure Diagram, Package Diagram, and Deployment Diagram.  Behavior Diagrams include the Use Case Diagram (used by some methodologies during requirements gathering); Activity Diagram, and State Machine Diagram.  Interaction Diagrams, all derived from the more general Behavior Diagram, include the Sequence Diagram, Communication Diagram, Timing Diagram, and Interaction Overview Diagram.
• #22: Documenta as funcionalidades básicas do sistema, do ponto de vista do usuário; Ajudam a compreender os requisitos; Guiam o desenvolvimento do sistema, e muitas vezes são utilizados para dividir o desenvolvimento de sistemas em tarefas; Muitas vezes os requisitos levantados juntamente com os clientes são mapeados em use cases.
• #24: Além de pessoas, também sistemas externos são representados por atores. Por exemplo, se você estiver desenvolvendo um sistema de automação para uma máquina da produção, que irá trocar informações com o sistema de estoque da indústria, este é representado nos diagramas por um ator.
• #29: Relaciona classes que precisam conhecer uma a outra para realizar o seu trabalho;
• #30: Relaciona classes que precisam conhecer uma a outra para realizar o seu trabalho;
• #31: Relaciona classes que precisam conhecer uma a outra para realizar o seu trabalho;
• #32: Relaciona classes que precisam conhecer uma a outra para realizar o seu trabalho;
• #33: Relaciona classes que precisam conhecer uma a outra para realizar o seu trabalho;
• #34: Relaciona classes que precisam conhecer uma a outra para realizar o seu trabalho;
• #41: Relaciona classes que precisam conhecer uma a outra para realizar o seu trabalho;
• #44: Relaciona classes que precisam conhecer uma a outra para realizar o seu trabalho;
• #48: Certos projetos permitem automatismos sobre os modelos, de maneira a gerar código ou base de dados;
• #50: 2) Select a UML Development Tool: Because most (although not all) UML-based tools implement a particular methodology, in some cases it might not be practical to pick a tool and then try to use it with a methodology that it wasn't built for. (For other tool/methodology combinations, this might not be an issue, or might be easy to work around.) But, some methodologies have been implemented on multiple tools so this is not strictly a one-choice environment.  You may find a tool so well-suited to your application or organization that you're willing to switch methodologies in order to use it. If that's the case, go ahead - our advice to pick a methodology first is general, and may not apply to a specific project. Another possibility: You may find a methodology that you like, which isn't implemented in a tool that fits your project size, or your budget, so you have to switch. If either of these cases happens to you, try to pick an alternative methodology that doesn't differ too much from the one you preferred originally.  As with methodologies, OMG doesn't have an opinion or rating of UML-based modeling tools, but we do have links to a number of lists here . These will help you get started making your choice.