enhances support for UML 2.1 standard
for modeling tool
New modeling tool
capabilities support software project teams for both software and hardware
- September 8, 2009 Visible Systems announces a new edition of
its award winning modeling tool Visible Analyst. Completing a new
development initiative, new modeling capabilities have been added to support
state of the art UML 2.1 modeling standards. The purpose of the Unified Modeling
Language (UML) is to provide comprehensive notation for communicating the
requirements, architecture, implementation, and deployment phases of a system.
Visible Analyst 2009 is an easy to learn and use modeling tool for systems
analysis and design, database design, and UML modeling of team-based
systems. The last release of Visible Analyst added support for OMG's
Business Processes Modeling Notation (BPM) geared toward business analysts and
Two key diagram types are included in the new release are Component diagrams
and the Deployment diagrams. Component diagrams focus on the software
components of a system and Deployment diagrams support the hardware components
of a system.
The main purpose of the Component diagram is to visually show the structural
relationships between the components in a system. A component is an
autonomous, encapsulated element within a system that provides for one or more
interfaces. Typically components are larger design elements that will be
implemented using replaceable modules.
Deployment diagrams model the physical architecture of a system showing the
relationships between the software and hardware components in a system, as well
as the physical distribution of the processing. Deployment diagrams
depict the static view of the run-time configuration of processing nodes and
the components that run on those nodes. The deployment diagrams show the
hardware for your system, the software that is installed on that hardware, and
the middleware used to connect the disparate machines to one another.
Deployment diagrams are related to component diagrams because they are used to
deploy the components from Component diagrams. Deployment diagrams are
important because they control the performance, scalability, maintainability,
and portability of a system and are used during the implementation phase of
Deployment diagrams are differentiated from component diagrams in that they
show where "components and artifacts" are used in relation to a
deployed system. The deployment diagram includes the notational elements
used in component diagrams with a couple of additional concepts including a
node. A Node represents physical machine or virtual machine node.
The communities who will benefit most from the new component and deployment
diagrams include: enterprise architects, system administrators, developers,
system engineers, and other key stakeholders on a project development team.
Architects: Component diagrams offer a very intuitive format for
architects to model their solutions. The component diagram allows the
architect a visual tool that ensures that a system's necessary functionality is
properly implemented by its components. This verification process ensures
that the implemented system will be acceptable its users.
Developers: A component diagram can be very useful to developers because
it gives them a high level view of the system that they will build. This
blueprint helps developers to formalize their roadmap for implementation
decisions such as tasks, assignments and skills enhancements.
System Administrators: Component diagrams are useful to system
administrators because they can see at an early stage the logical software
components that will run their systems. Component diagrams will provide
early information about components and relationships that will help them to
Stakeholder Communication: Component diagrams are intuitive and are
generally used by the implementation staff, as well as other stakeholders by
giving them a basic understanding of the system being built.
Systems Engineers: Systems engineers will use deployment diagrams to
visualize the hardware topology of their systems.
System Production Staffs: System Production Staffs: Production staffs
will heavily use deployment diagrams to model the physical run time of their
HARDWARE REQUIREMENTS: All editions of Visible Analyst are available as
32-bit Windows applications for Windows NT 4.0, 2000, 2003, XP, Vista or Windows 7.
A Pentium class processor is required with a minimum of 128MB RAM, 20MB of free
disk space for the installation and 100 MB of free space for the projects, and
a compatible pointing device.
Visible Analyst 2009 is currently available.
ABOUT VISIBLE SYSTEMS: Headquartered in Framingham, MA, Visible Systems offers
end-to-end, model-based solutions for developing and managing large-scale
software, hardware and database applications. Key products include: Visible
Analyst, a powerful systems analysis and design and tool that supports UML,
XML, and round-trip structured software engineering in one integrated
multi-user tool set; Visible Developer, a model-based application design and
code generation tool; and Razor an integrated software configuration management
©2009 Visible Systems Corporation. All rights reserved. Visible Developer, Visible Analyst and Razor are registered trademarks of Visible Systems Corporation. All other trademarks are the property of their respective owners.