ARTiSAN Logo Prodotti     Download     Centro UML     Società     Clienti     Contattaci     Home

Novità     Eventi     Partner     Lavoro     Training     Supporto     Mappa Sito

Fornitore Leader di strumenti software di sviluppo UML tecnologicamente avanzati

[Sito in lingua inglese]
English

Training

Sommario
Corsi
Nord America
Europa
Libri
Home
Mappa sito
Contattaci
Mailing List
Parla di noi a un amico

Using Real-time Studio - Requirements and Design Modeling

Se siete interessati all'effettuazione del seguente corso d'addestramento presso i Vostri uffici in Italia, per favore mandate una email a .

EUROPE REGISTRATION     US REGISTRATION

Course Description

This course provides hands-on, tool specific training for software engineers who already have a solid understanding of UML concepts and techniques. The course covers Real-time Studio (RtS) modeling for system definition and requirements capture, and shows how these models lead onto design modeling for both object design and concurrency design

Course Objectives

  • To provide practical experience in the use of RtS modeling.
  • To outline UML deficiencies for real-time system modeling and describe the ARTiSAN extensions.
  • To illustrate how RtS provides a consistent and related set of models for the analysis and design of real-time systems.

Attendees Will Learn

  • The environment in which RtS operates.
  • To use RtS in order to develop UML based requirements and design models.
  • Where and why RtS extends UML modeling, and how these additional models are created and used.
  • How Real-time Studio’s requirements models provide a complete and consistent definition of the required system.
  • How the requirements models are used to provide a traceable path into design modeling.
  • How to use Real-time Studio’s Document Generator to document the various model types.

Pre-requisites

Delegates should have some experience of object-oriented programming of real-time systems, and should therefore be aware of concepts such as classes and objects, multi-tasking, etc.

The course assumes that delegates are also familiar with the concepts, notation and techniques of UML (use cases, object interaction diagrams, state diagrams, etc.). These having ideally been attained from attendance on a UML techniques course. An inability to meet this pre-requisite will significantly reduce the benefit of the course to the attendee and others on the course. The emphasis is on applying UML concepts and techniques using RtS, rather than explaining them.

Who Should Attend

  • Software engineers who have been previously trained in UML techniques, and who want to know how RtS can be used effectively as a modeling tool.
  • Evaluators of RtS or those needing to convert from other toolsets.
  • People who have previously attended an ARTiSAN UML training course, but have not used RtS for some time and therefore need a short ‘refresher’ on how best to use it.

Duration

2 days

Attendees Receive

  • An annotated copy of all course presentation material.
  • All course exercises and solutions.
  • A certificate of attendance.

Course Format

The course is a mix of lecturer presentations and practical exercises designed to illustrate and reinforce the presentation content. Numbers are strictly limited to ensure that each delegate has sufficient time to discuss particular issues of concern with the lecturer.

Related Courses

This course provides another route, for those engineers who have already been trained in UML techniques, to the practical experience provided in the ‘Developing Real-time Systems Using UML’ course. Delegates not having the required pre-requisites for this course should take ‘Developing Real-time Systems Using UML’.

This course also provides a useful preliminary course to other ‘Using Real-time Studio’ courses.

Course Outline

RtS Essentials

  • RtS overview – repositories and models, Models Neighborhood.
  • The components of RtS
  • Using RtS – the UI, menus and toolbars.

Requirements Architecture

  • Define System Scope.
  • Document the System Usage.
  • Document the System Modes.
  • Specify System Constraints.

Object Architecture

  • Object Interaction – creating use case-based, UML interaction diagrams in RTS.
  • Class Modeling – building a UML class model defining class properties and relationships.
  • State Modeling – creating UML state diagrams consistent with the other Object Architecture models.

Software Architecture

  • Concurrent systems - the need for concurrency and how to develop a design strategy to cope with it.
  • Objects and tasks - the relationship between them.
  • Define Concurrency Model -tasks and inter task communication.

System and Software Architecture

  • Architecture modeling – documenting the hardware environment to ensure a correct HW/SW interface.
  • Objects and Tasks – the relationship between object design and task design.
  • Concurrency Modeling –tasks and inter-task communication.

Additional Features

  • Activity Diagrams
  • Partitioning with Packages.
  • UML Extensibility Mechanisms.
  • The Document Generator.
  • OLE Automation Interface.