NetBeans IDE - Integrated tools for UML developers
Follow, research and publish the best content
Get Started for FREE
Sign up with Facebook Sign up with X
I don't have a Facebook or a X account
Already have an account: Login
Devops for Growth
111.5K views |
+0 today
For Product Owners/Product Managers and Scrum Teams: Growth Hacking, Devops, Agile, Lean for IT, Lean Startup, customer centric, software quality...
Curated by
Mickael Ruau
 Your new post is loading...
Your new post is loading...
Scoop.it!
Umple is a modeling tool and programming language family to enable what we call Model-Oriented Programming. It adds abstractions such as Associations, Attributes and State Machines derived from UML to object-oriented programming languages such as Java, C++, PHP and Ruby. Umple can also be used to create UML class and state diagrams textually.
Mickael Ruau's insight:
Umple is an open source project, so details will evolve. However, it is ready to be used for real systems. In fact the Umple compiler itself is written in Umple. Any Java, C++ or PHP project could use Umple. We have found the resulting code to be more readable and have many fewer lines. This is because Umple means you can avoid having to code a lot of 'boilerplate' code that would be needed to implement associations and attributes, a system based on Umple should also be less bug-prone. Umple has also been found to help students learn UML faster in the classroom. Umple works online, as an Eclipse plugin, and as a stand-alone command-line Jar. For further information and downloads, see the left margin. 
Scoop.it!
UML 2.5 Diagrams Overview categorized hierarchically, short description.
Scoop.it!
Software cost estimation with use case points is primarily driven by use case analysis. You take into account environmental and technical factors, but they are
Scoop.it!
A reverse engineering, metamodel driven tool that scans PHP files and directories, and delivers an UML/XMI representation of the classes / packages found. The XMI code that it generates can be imported into any UML modeling tool. It is available on PEAR.
Scoop.it!
The technical factors are the first thing you assess when doing a use case point analysis. Technical factors describe the expectations of the users for the delivered software. Generally, it is an assessment of non-functional requirements. There are 13 technical factors that you have to analyze.
Scoop.it!
Use Cases represents functional requirements and functional requirements need to be tested. The purpose of the functional test is: A) Determine that the delivered solution works as required B) Determine that the delivered solution works as specified
Mickael Ruau's insight:
In this post I will outline how to create a full functional test case foundation on basis of your use cases. Normally you would need to also update the functional test cases to address the design specification. In addition, besides functional testing various other test types exist. However, in this post I will focus only on the functional testing based on use cases. All the examples will be based on the use case example "Create User" Download Use Case Example - Create User
Scoop.it!
From
melashri
Use Case Points (UCP) is an estimation method that provides the ability to estimate an application’s size and effort from its use cases. UCP analyzes the use case actors, scenarios and various technical and environmental factors and abstracts them into an equation.
Mickael Ruau's insight:
The equation is composed of four variables:
UCP = TCP * ECF * UUCP * PF
Scoop.it!
Mike Cohn describes an agile process to measure application size with use case points
Arturo Moquillaza's curator insight,
July 1, 2015 7:21 PM
Este es un listado de artículos publicados por esta web, sobre temas de ingeniería de software.
Scoop.it!
 Méthode d'analyse et de conception d'applications orientées objetPour les articles homonymes, voir MACAO. La méthode d'analyse et de conception d'applications orientées objet (dite MACAO) est fondée sur une démarche participative par prototypage incrémental (processus itératif) permettant aux utilisateurs d'intervenir très tôt dans le processus de développement du logiciel.
Mickael Ruau's insight:
Afin de limiter les tests de non-régression toujours très lourds et coûteux, MACAO applique à chaque prototype réalisé le principe de non-régression basé sur l'encapsulation et l'héritage qui font tout l'intérêt et la richesse de la programmation orientée objet.
Scoop.it!
"Models that don't execute are like cars without engines".
Mickael Ruau's insight:
A few issues need to be addressed, as highlighted during the discussion session: educational issues (make learners approach executable UML as their basic interface with programming, instead of other lower-level languages); integration with existing code, libraries, distribution, and so on.
Scoop.it!
Survol de la programmation par objet: Les bases, les cartes CRC, l'UML, l'analyse, la conception (design), jusqu'aux méthodologies de développement logiciel avec l'Unified Process (RUP).
Mickael Ruau's insight:
Carte CRC
Avant de nous attaquer à des éléments plus complexes et afin de consolider les bases, nous allons voir un moyen de décrire un objet de façon très simple sans utiliser un langage particulier: Les cartes CRC. Elles ont été inventées pour faciliter l'apprentissage de la programmation objet. Une carte CRC est tout simple un morceau de carton de taille environ 8x13cm ressemblant à ceci. On indique le nom de la classe, ainsi que les responsabilités et si il y a, les collaborations. Une responsabilité est tout comportement dont la classe est responsable. Une responsabilité dénote l'obligation pour un objet d'avoir un certain comportement. Pour effectuer certaines responsabilités, il se peut que la classe ai besoins d'une autre classe. On note dans la colonne des collaborateurs ces autres classes.
Scoop.it!
Programmers could not live without version control systems like Subversion or Git. However, modelers have been forced to live like that until now.
|
Scoop.it!
Born as a fork of BoUML, it is a UML 2 modelling tool capable of round-trip, reverse engineering and code generation. Supports class, state and other diagrams, C++, Java, Python, PHP, IDL code generation. It can also export to XMI.
Scoop.it!
Open Source UML Unified Modeling Language Tools: use cases, class diagram, sequence diagram, object diagram
Scoop.it!
In this article I explore in detail how AM can be used in conjunction with the various instantiations of the Unified Process (UP), including but not limited to the RUP and the EUP. To do so, I discuss
- See more at: http://www.agilemodeling.com/essays/agileModelingRUP.htm#sthash.YdzL4Hwx.dpuf
Scoop.it!
Quels sont les meilleurs outils UML 2 pour les bases de données ?
Mickael Ruau's insight:
Télécharger le document ici (Miroir http).
Scoop.it!
Estimating the amount of work required to deliver software is hard. Estimating the amount of work in the very early stages of a project is even harder.
Scoop.it!
Estimating what effort is needed to develop an IT solution is not an easy act. The pitfalls are multiple and chances are that you end up guessing. In this post I will outline how to estimate projects based on the use cases. In addition I will show you how you...
Mickael Ruau's insight:
Warning
Remember that UCP estimation and PF calculation are not absolute truths. What you get is an estimate based on facts and an estimate that gives you a feeling of what end the “real” estimate should be in.
Scoop.it!
Object-oriented applications frequently rely on Use Cases to describe the business processes of a software application. Since use cases consist of the strategic goals and scenarios that provide value to a business domain, they can also provide insight into an application’s complexity. Deriving a reliable estimate of the size and effort an application needs, is possible by examining the actors and scenarios of a use case. Use Case Points is a projectestimation method that employs a project’s use cases to produce an accurate estimate of a project’s size and effort.
Mickael Ruau's insight:
Use Case Points (UCP) is an estimation method that provides the ability to estimate an application’s size and effort from its use cases. Based on work by Gustav Karner in 1993, UCP analyzes the use case actors, scenarios and various technical and environmental factors and abstracts them into an equation. The equation is composed of four variables:
Scoop.it!
We just completed a series of articles detailing how to use Use Case Points for software cost estimation. In this article we have a free MS Excel Spreadsheet
Scoop.it!
Revue du livre Rédiger des cas d'utilisation efficaces de Alistair Cockburn pour apprendre à rédiger des spécifications efficaces.
Mickael Ruau's insight:
Voilà encore un livre très utile, rédigé avec le soin de faire gagner du temps au lecteur, plutôt que « s’écouter disserter sur le sujet » au risque de noyer le lecteur.
Scoop.it!
UML Generalization, Aggregation, Composition, Interface, Dependency, Multiplicities, Association (Class)
Scoop.it!
Curated list of the best UML cheatsheets available online to use as quick UML reference guide
Mickael Ruau's insight:
If you need a quick reference guide for the UML notation, check one of the following, IMHO, gret UML cheatsheets (in no particular order): http://refcardz.dzone.com/refcardz/getting-started-uml :Newest reference card, covers all major diagrams http://msdn.microsoft.com/en-us/library/dd409437.aspx :Very complete. Includes activity, component, class, sequence and use case diagrams (menu on the left). The only thing that should be improved is that the name of the elements is not shown directly in the digram but explained in tables below http://www.digilife.be/quickreferences/QRC/UML%20Reference%20Card.pdf: Very compact. UML 1.0. Covers class and sequence digrams. http://www.holub.com/goodies/uml/ :Lots of examples to help you understand the semantics of each notation element. UML 2.0. Covers all major diagrams. http://www.scribd.com/doc/399157/UML-20-Cheatsheet :Very well explained. UML 2.0. Covers all major UML diagrams http://loufranco.com/blog/assets/cheatsheet.pdf :To the point, example diagrams annotated with the name of the modeling elements used in the example. Class, use case and sequence diagrams covered http://edn.embarcadero.com/article/31863 : Very complete, even covering component and deployment diagrams (which is not the case for most of the previous ones). It used to include self-tests to quickly check your knowledge of the notation but this part seems to have been removed from the site.UML Diagrams: Detailed overview of all UML diagrams (including the new features of latest UML versions). It’s more a reference guide than a cheatsheet though, since each diagram has its own dedicated page.
|
Looking for a full featured, free UML modeling environment? JDeveloper provides comprehensive modeling capabilities that include