Showing posts with label uml. Show all posts
Showing posts with label uml. Show all posts

Monday, 21 January 2013

Which Tool to Manage Requirements Management?

The RequirementsManagement.net web site has published the results of a short survey about the usage of software requirements management tools used to create and manage the definition of requirements (text, user stories, models,…). The result is that there is no clear winner in the poll even if office software is the number one tool used to manage requirements (27% of respondents).20% of the participants answered that they use more than one tool.

Thursday, 27 May 2010

Are Unified Modeling Language (UML) Models Still Used?

The Agile approach prefers face to face communication between developers and user. User stories could be specified in simpler artifacts like index cards rather than put larger requirements documents. Does this impact the usage of UML models?

A recent Methods & Tools survey tried to evaluate the usage of UML tools in organizations.

http://www.methodsandtools.com/dynpoll/oldpoll.php?UMLPoll2

Monday, 17 August 2009

More than 1000 Videos and Tutorials on SoftDevTube.com

There are now more than 1000 software development related videos and tutorials categorized on SoftDevTube.com. SoftDevTube is a repository of videos, interviews and tutorials focused on all software development activities: UML, Agile Methodologies (eXtreme Programming, Scrum, TDD, FDD,..), Software Testing, Software Configuration Management, Database Modeling, Coding (Java, .NET, ruby, python, C/C++, Cobol,… ) Rich Interface Application (Ajax, Flex, Silverlight), Software Project Planning and Management, Test Automation, Software Analysis and Design, Quality Assurance, Software Process Assessment and Improvement, Software Development Tools, Risk Management.

Thursday, 16 August 2007

If You Can't Beat Them, Join Them !

August 13th, Borland's subsidiary CodeGear announced JGear™, a set of specialised plug-ins for the Eclipse open-source development platform. JGear augments Eclipse in three areas - Java application performance, visual development and team collaboration. According to CodeGear, the top pain points for Java developers using Eclipse stem from the difficulties of application performance tuning , Java code archaeology, coding and configuring Java servers and frameworks, team collaboration

The new JGear product line includes - JGear™ Performance for Eclipse, JGear™ LiveSource® for Eclipse, and JGear™ Team for Eclipse (both Client and Server editions). JGear Performance contains a variety of performance and tuning features such as memory and CPU profiling and debugging; automatic detection of potential memory leaks; and real-time monitoring of programs' use of virtual machine memory. JGear LiveSource includes a graphical EJB workbench and Web services designer; Unified Modeling Language visualisation of code artefacts and design for analysing an application's design and implementation; CodeGear's LiveSource technology that simultaneously replicates changes to models in the code and vice versa to aid alignment between software architects and developers; and creation of Enterprise JavaBeans and model relationships. JGear Team offers a complete agile team collaboration and development system based on open-source components. JGear Team is both a turnkey server solution and an Eclipse developer client solution JGear Team Server is a team development server stack based on best of breed open-source components such as Subversion, Bugzilla, Continuum, and XPlanner. JGear Team Server includes ProjectAssist™ - the JGear Team administrator client for simple single-click server installation and configuration, team project creation, user administration and setup.

This is a normal evolution for CodeGear as the future is difficult in the software development IDE sector if you want to remain the supplier of an isolated solution. Competition with open source and free products like Eclipse or NetBeans is difficult to sustain. A better strategy is to offer additional services that could be missing in the core open source solution and that developers are ready to pay some dollars to obtain. Acting like this in the Eclipse ecosystems, CodeGear recognises that its survival may depend on its ability to transform itself from software producer to plug-in developer.

http://www.codegear.com/
http://www.eclipse.org/

Friday, 5 January 2007

Who Profits from Free Software?

Telelogic has just announced the release of Telelogic Modeler a free Unified Modeling Language (UML) design environment. This entry-level product will allow user with extended needs to migrate to other Telelogic's products in the same area. Telelogic Modeler is available for download at http://www.telelogic.com/modeling/modeler.

Facing the competition of free open source products, major editors like Microsoft or Oracle have followed the same strategy than Telelogic. They have created free versions of their software development tools. These products are "simplified" versions of the paying product, often minus specific features that are useful for large/complex projects or systems. They hope that people using the free version will one day have unsatisfied needs and that they will migrate to paying versions from the same editor. Time will tell if this strategy is right, but I think that it is facing major issues:
  • The majority of people looking for a free software could not be the one that are more enthusiastic to get it from a commercial editor.
  • Upgrading to a commercial version is not the only solution to get more performance. Open source tools are improving and there are companies interested to increase the power of the open source tools they support. Red Hat is doing this with JBoss in the Web server market. Another example is EnterpriseDB that is building an Oracle-compatible product based on PostgreSQL. In both cases companies are selling services and not software.
  • According to the Pareto principle, 80% of the people should be satisfied with 20% of the features of the original product. Thus migration to a product offering more features could be limited, furthermore if this imply paying for it ;o)