background preloader

Unified Modeling Language

Unified Modeling Language
The Unified Modeling Language (UML) is a general-purpose modeling language in the field of software engineering, which is designed to provide a standard way to visualize the design of a system.[1] It was created and developed by Grady Booch, Ivar Jacobson and James Rumbaugh at Rational Software during 1994–95 with further development led by them through 1996.[1] In 1997 it was adopted as a standard by the Object Management Group (OMG), and has been managed by this organization ever since. In 2000 the Unified Modeling Language was also accepted by the International Organization for Standardization (ISO) as an approved ISO standard. Since then it has been periodically revised to cover the latest revision of UML.[2] Overview[edit] A collage of UML diagrams The Unified Modeling Language (UML) offers a way to visualize a system's architectural blueprints in a diagram (see image), including elements such as:[3] History[edit] History of object-oriented methods and notation Before UML 1.x[edit] [edit]

Related:  Arquitectura Conducida por Modelos: Principios y Prácticas

Round-trip engineering Round-trip engineering (RTE) is a functionality of software development tools that synchronizes two or more related software artifacts, such as, source code, models, configuration files, and other documents. The need for round-trip engineering arises when the same information is present in multiple artifacts and therefore an inconsistency may occur if not all artifacts are consistently updated to reflect a given change. For example, some piece of information was added to/changed in only one artifact and, as a result, it became missing in/inconsistent with the other artifacts. Round-trip engineering is closely related to traditional software engineering disciplines: forward engineering (creating software from specifications), reverse engineering (creating specifications from existing software), and reengineering (understanding existing software and modifying it). Round-trip engineering is often wrongly defined as simply supporting both forward and reverse engineering.

UML 2 Activity Diagramming Guidelines Guidelines: 1. General Guidelines Figure 1. Modeling a business process with a UML Activity Diagram. Place The Start Point In The Top-Left Corner. Associative model of data The associative model of data is an alternative data model for database systems. Other data models, such as the relational model and the object data model, are record-based. These models involve encompassing attributes about a thing, such as a car, in a record structure. Such attributes might be registration, colour, make, model, etc.

PMO The Project Management Body of Knowledge (PMBOK) established by the Project Management Institute (PMI) for training certified Project Management Professionals (PMP) discusses the structure of a projectized organization, a common management structure in organizations in which a major component of the value of the business is based upon the success of individual projects into which investments of resources are made based on their potential value.  The projectized organization structured around programs and portfolios is shown in the figure below. Projectized Organization The PMO at each level also assumes responsibility for the resources that are not allocated, and is also responsible for hiring, developing and evaluating resources within their hierarchy.  The PMO then takes on the responsibility for overhead costs associated with personnel development and costs of personnel time that are not billed to a project. Optimized Project Management Office Structure – I 1.

10 code snippets to interact with Twitter 1 – Autofollow script (PHP) This code allow you to automatically follow user who have tweeted about a specific term. For example, if you want to follow all users who tweeted about php, simply give it as a value to the $term variable on line 7. Source : 2 – Get the number of follower in full text (PHP)

Framework-specific modeling language A framework-specific modeling language [1] (FSML) is a kind of domain-specific modeling language which is designed for an object-oriented application framework. FSMLs define framework-provided abstractions as FSML concepts and decompose the abstractions into features. The features represent implementation steps or choices. A FSML concept can be configured by selecting features and providing values for features. Such a concept configuration represents how the concept should be implemented in the code. Class and sequence diagrams work together to allow precise modeling UML is used as a representation of the Java programming language. Using sample class and sequence diagrams, you can see how UML conveys unambiguous code-mapping information to developers. Class diagrams, when used in conjunction with sequence diagrams, provide an extremely effective communication mechanism. You can use a class diagram to illustrate the relationships between the classes, and the sequence diagram lets you show the messages sent among the instances of these classes and the order in which they are sent. When an object sends a message to another object, it implies that the two classes have a relationship that must be shown on a class diagram.

Entity-relationship model An entity–relationship diagram using Chen's notation In software engineering, an entity–relationship model (ER model) is a data model for describing the data or information aspects of a business domain or its process requirements, in an abstract way that lends itself to ultimately being implemented in a database such as a relational database. The main components of ER models are entities (things) and the relationships that can exist among them, and databases. Scope (project management) In project management, the term scope has two distinct uses- Project Scope and Product Scope. Scope involves getting information required to start a project, and the features the product would have that would meet its stakeholders requirements. Project Scope

Lambda calculus The lowercase lambda, the 11th letter of the Greek alphabet, is used to symbolize the lambda calculus. Because of the importance of the notion of variable binding and substitution, there is not just one system of lambda calculus, and in particular there are typed and untyped variants. Historically, the most important system was the untyped lambda calculus, in which function application has no restrictions (so the notion of the domain of a function is not built into the system). In the Church–Turing Thesis, the untyped lambda calculus is claimed to be capable of computing all effectively calculable functions. The typed lambda calculus is a variety that restricts function application, so that functions can only be applied if they are capable of accepting the given input's "type" of data. Lambda calculus in history of mathematics[edit]

Conceptual model (computer science) This is often used for defining different processes in a particular Company or Institute. Fowler, Martin: Analysis Patterns, Reusable object models, Addison-Wesley Longman, 1997. ISBN 0-201-89542-0.Stewart Robinson, Roger Brooks, Kathy Kotiadis, and Durk-Jouke Van Der Zee (Eds.): Conceptual Modeling for Discrete-Event Simulation, 2010. ISBN 978-1-4398-1037-8David W. Embley, Bernhard Thalheim(Eds.): Handbook of Conceptual Modeling, 2011. UML basics: An introduction to the Unified Modeling Language Way back in the late twentieth century — 1997 to be exact — the Object Management Group (OMG) released the Unified Modeling Language (UML). One of the purposes of UML was to provide the development community with a stable and common design language that could be used to develop and build computer applications. UML brought forth a unified standard modeling notation that IT professionals had been wanting for years.

Related:  DatabasesUMLUML