 |
|||||||||||||||||||||||||||||||||||||||||
| Services : Training : Agile Modeling | |||||||||||||||||||||||||||||||||||||||||
|
Agile Modeling |
|||||||||||||||||||||||||||||||||||||||||
| An
agile team should be cross-functional and have the ability to understand and
transform a set of needs into working software. Thus, a problem may arise
whenever the 'definition of done' includes evidences of additional
supporting artifacts or i'f/when the team lacks some essential capabilities
for productively working with winning artifacts on analysis, design or other
software engineering disciplines. This training course aims at filling the gap between "fullfilling an obligation versus modeling towards the solution" so that all those activities get to be performed accordingly to an Agile Mindset. |
|||||||||||||||||||||||||||||||||||||||||
| Overview |
|
||||||||||||||||||||||||||||||||||||||||
|
Participants of this training course will benefit from 2 valuable perspectives: 1. Agile Modeling principles, values and practices as originally conceived by Scott Ambler and 2. a broad, holistic view about over 20 different modeling & supporting artifacts that may add value, if reasonably applied during software development lifecycle
|
|||||||||||||||||||||||||||||||||||||||||
| Objectives & Learning Outcomes | Duration | ||||||||||||||||||||||||||||||||||||||||
As a result of
taking this course, the participants will understand and be able to:
|
3 days (24 hours) | ||||||||||||||||||||||||||||||||||||||||
| Audience | |||||||||||||||||||||||||||||||||||||||||
|
Product Owners, Team members as well as any professional that is (or will be) working as Business analyst, Systems analyst, Project manager, Software architect, Software designer, Developer, Test analyst amongst other roles |
|||||||||||||||||||||||||||||||||||||||||
| Course Outline | Prerequisites | ||||||||||||||||||||||||||||||||||||||||
|
Note: The supporting tools Sparx Enterprise Architect, Atlassian Confluence and Gliffy are introduced but not deeply explored during exercises and examples. If you are looking for a course just focused on Sparx Enterprise Architect Fundamentals, please click here. |
None | ||||||||||||||||||||||||||||||||||||||||
| Available Via... | |||||||||||||||||||||||||||||||||||||||||
| Introduction | Agile Modeling Practices - diving deeper |
 |
Onsite training | ||||||||||||||||||||||||||||||||||||||
|
|
 |
Online Training (live, instructor-led) | ||||||||||||||||||||||||||||||||||||||
|
|
|
||||||||||||||||||||||||||||||||||||||||
|
Agile Modeling |
|
||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||
|
Agile Modeling - Tools & Notations |
||||||||||||||||||||||||||||||||||||||||
|
|
Tips & Insights | |||||||||||||||||||||||||||||||||||||||
|
This training course covers more than 20 diagrams
and other supporting artifacts that add an extreme value if
properly used. |
||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||
| Important: innumerous modeling and supporting artifacts are introduced during the training course through examples and demonstration, including Prototypes, Use Case Diagrams, Flowchart, DFD, Data Models (conceptual, logical and physical), Class Diagrams, Sequence diagrams, Component Diagrams, Business Rules documents, Requirements Specification, User Stories, Glossary, Services Specification, Test Cases and Deployment diagrams, amongst others, however this training course doesn't cover all of the specifics for each diagram nor notation. | |||||||||||||||||||||||||||||||||||||||||
 |
|||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||
