Object Oriented Analysis and Design with UML
Many Business Managers have adopted UML notation to describe business processes as a first step towards process maturity. Outsourcing partners will often use UML to capture the aspects of workflow as an initial step towards agreeing functional requirements for a new system or to investigate opportunities for process automation. This course is split 50/50 between presentations and practical exercises.
Book your team training at your premises
- More info
- Date and time to suit you
- VenueWe will train your team
at your offices
- CostContact us for price
- Fill in the form and we'll be in touch
within 15 minutes (Mon-Fri 9-5)
Book your place
Unified Modelling Language (UML) is a standardized general-purpose modelling language that includes a set of graphic notation techniques to create visual models which describe a system's architectural blueprints - but UML is not a process in itself. Course attendees will build UML diagrams as they follow the Unified Process through different stages in system development, from inception all the way to delivery. Each stage will focus upon a particular activity in the Unified Process, leading to the production and refinement of UML diagrams capturing outcomes of that activity.
Anyone involved in the Software Development lifecycle - Business Analysts, Systems Architects, Designers, Programmers, Testers, Change and Release Managers, Project Managers, Technical Managers.
Individuals involved in ITIL Service Design, looking at a means of accurately capturing business requirements prior to transformation into service acceptance criteria and service level requirements. Process managers looking to create process documentation for workflow analysis.
- Capture functional and non-functional business requirements for a new system
- Follow the Unified Process to transform requirements into a working system
- Describe, design and develop the new system using different UML diagrams
- Understand object-orientated concepts to describe objects in a business model
Following an established standardised methodology brings a greater understanding, improved clarity and has reduced variance, risk and costs overall. Allowing UML diagrams to emerge during process progression means documentation is created more naturally and validated against business requirements easier. Using standard UML notation for system documentation quickens understanding when implementing change, meaning more maintainable systems that facilitate easy and quick modifications, reducing risk and unexpected side-effects.
A picture tells a thousands words. Everyone has, at some point, used a diagram to convey their thoughts knowing that images improve clarity of understanding and articulate key facts faster. Wouldn't it be a nice idea if there were a standard set of recognisable diagrams everyone could use? That's partly the idea behind UML. But that's not all. Many programmers and developers that are loathe to create documentation alongside code find that UML presents the documentation for them, leaving them to create functional code.
Programming, coding, system building - they're all works of art. No reason why documentation can't be also!
What is the UML?
Contents of the UML
UML and Processes
The Process used in the Course
Classes & Instances
Use Cases and Process
What is a Use Case?
Use Case Diagrams
Use Case Description
Use Case & Actor Relationships
Validating Use Case
Capturing Non Functional Requirements - FURPS +
Exploring a Process
What are Analysis Classes?
Relating Sequence Diagrams to Analysis Classes
Combined Fragments in UML 2
Depicting a Class
Benefits of Using Components
Visibility and Packages
States, Transitions & Events
Initial & Final Pseudo-States
A basic understanding of system development concepts is an advantage, but no prior knowledge is required.