Flex Tagcloud Search Results

Tagcloud ACA

Flex Tagcloud Search Detail

 

Agile Requirements Modeling (ARM)


Contents

Agile Requirements Modeling is a practice-based methodology for effective modeling and documentation of requirements. Simply put, Agile Modeling (AM) is a collection of values, principles, and practices for modeling that can be applied on a software development project in an effective and light-weight manner.

Every project team should always evaluate the modeling ceremony required for the project. The requirements modeling effort should be 'just enough'. Meaning 'just enough' temporary and permanent requirements modeling products to allow the development team to develop quality software.  The course will provide guidelines to determine the 'just enough'...

The course covers the following modeling disciplines:

  • Business process modeling
  • Domain modeling
  • User requirements modeling

Business process modeling is a crucial, but often overlooked, activity in new systems development. The goal of the course is to provide you with a practical and effective set of techniques and methods for identifying, mapping and improving business processes and practices within your enterprise and across enterprise boundaries with customers, suppliers and business partners.

The course explains the business modeling technique UML 2.0 Activity diagrams, which is also adopted by the students during the practical exercises. The concepts of a different technique, BPMN 1.0 (Business process modeling notation) are discussed as well.

A domain model is a visual representation of conceptual classes and real-world objects in the domain of interest. UML 2.0 Class diagrams will be adopted as a technique to model the domain of interest. Developing correct domain models in an iterative manner is not that simple. This course will provide students with a better understanding and guidelines for domain modeling.  Further attention is given to basics of domain modeling and to the importance of good conceptual class and attributes definitions.

User requirements modeling is a common activity in systems development.  That part of the course will focus on:

  • Actors and their goals
  • Use case diagrams
  • Use case scenarios
  • Other useful techniques (State charts, context diagrams, ...)

More and more people write use cases to describe requirements for software systems. The proverb "owning a hammer does not make one an architect" is especially true for requirements analysts because everybody writes use cases in a different manner.  There are many misconceptions how use cases should be adopted correctly.  This course will focus on writing clear and concise use case scenarios and will help you avoid the common pitfalls.


Course Approach

During the course the best practice principles of unified process (tackle high-value and high-risk items first, progress in an iterative and incremental way, …) and the agile methods (avoid over-documentation, people over tools, …) will be adopted.

The course consists of both theory and practice. You will use a real world business case to practice business process modeling and requirements gathering skills. A coach will be present at all time to help out individual students during theory and practice.

Since students have different backgrounds, the course is individually organized. Each student will study the theory part at his/her own pace. After a theory part was ‘grasped’ by a student, a coach will verify that it was fully comprehended. If this was not the case, the student will be sent back and restudy the theory part. Theory parts are followed by practice. A specific project case will be the basis of the exercise. Step-by-step the student will elaborate the requirements model of this project case.

The coach will provide the student with an exercise to validate that not only the student actually understood the theory, but can also apply the theory into practice!  The student will make this exercise individually on his/her own pace.

The Benefits and concerns of the solution for the exercise are discussed together with the coach. If the solution that was provided by the student is not acceptable, then the student will recommence the exercise.

This approach (‘your work can be improved, so redo your work ‘) might seem harsh, but it will provide the highest probability that the student will actually be able to model requirements successfully in her future projects.


Requirements

  • Basic knowledge of business processes and requirements gathering
  • Basic knowledge of software development process


Target Audience

  • Business managers
  • Business analysts
  • Requirements analysts (functional analysts)
  • Project leaders
  • Developers
  • Every person involved in business processes and functional requirements for systems development


Period(s)

There are no public training classes scheduled.
Please contact us for possible private classes.