You can now attend IRM Training courses remotely from the comfort of your home or office.

The courses will still be:

• Practical
• Hands-on
• Interactive
• Run in small groups
• Run live by highly-skilled instructors with 15 to 25+ years’ experience.

Compared to the in-person training, there will be:

• Smaller instructor-to-participant ratio
• More frequent (albeit shorter) breaks

IRM’s Remote LIVE Training VS other online courses

Platform

Courses are delivered via Zoom which supports most modern computers and mobile devices (Windows, Mac, Android and iOS are supported).

To learn more about how to use Zoom, watch the short video tutorials.

Group Exercises

Most exercises are worked on in groups of 2-4 people where each group is allocated their own breakout room to discuss and share screens with their group.

Similar to in-person training, you can still ask your trainer questions while you are in the breakout room and the trainer will visit all the breakout rooms to offer guidance, or in some cases, additional challenges.

Questions?

If you have any questions please Contact Us.

The post Practical Training Delivered Remotely (Live) appeared first on IRM Training.

A typical business function might contain several unique events each of which we want to end up as a component of a larger software application.

So how do we go from a table containing textual information to a specification which a developer can use?

The first step is to turn each business event into a model – either a use case fragment, a DFD fragment or any modelling language you might be working with.

The following event table describes three typical interactions a customer would have with their bank:

Each of these events can be drawn as a separate use case:

These individual use cases (use case fragments) are only half the picture however. Today developers don’t write individual software programs for each event, particularly when multiple events will have numerous common components e.g. database enquiry, ID validation, etc.

What we do want is to be able to combine use case fragments into a single use case. We do this by identifying and sharing common actors (in this example the customer):

While we still need to write individual descriptions for each use case, we’ve given the developer a concise package of functional requirements, offering them the best opportunity to write efficient and effective code.

For an example of writing formal use cases see the paper How to use Use Cases.

The post Use Case Fragments appeared first on IRM Training.