Process and Requirements Modeling Services

eTrack are experts at facilitating and documenting system requirements and business processes using role based use case/scenario modelling techniques.

Process Modeling is gathering, documentation and reviewing business processes within a company.    The larger and more complex the company the more important it is to do this step as part of selecting a project management application since often different areas of a company do things differently and requirements are uncertain.

This service may be separate from any eTrack deployment and the resulting document can be used:

  • To get agreement on what are the companies best practices;
  • To get agreement on what are the companies project management requirements;
  • As input to a RFI to compare vendor products;
  • To clarify priorities for the requirements of a first roll out;
  • To configure the project management system seleted;
  • As input to user and quality manuals.
  • To guide Change Management.

The techniques eTrack use are very fast.  Within 2 to 5 days, one consultant can run workshops and document a large part of your companies processes so that the resulting documentation can be used immediately.  No longer do you need a team of consultants to come in for weeks!

Please contact eTrack for examples of process models and to discuss further.

Requirements Modeling for Success

eTrack Product Pty Ltd provides a best practice, practical Software Requirements Modeling methodology and training course based on scenario/use case modelling around UML (the Unified Modelling Language).    The methodology was developed by Capability Improvement Pty Ltd and is used by eTrack staff to do all their requirements modeling.It can be used with or without eTrack and consists of a full process manual, crib-sheets, checklists and templates needed to get you going immediately.    The course takes a practical view and the trainers have had extensive hands on experience with different methodologies including OPEN, Rational Unified Process, Prince 2, Process MeNtOR, SDA, IBM and self-developed methodologies dating back to 1992.

The Requirements Modeling pack comes with the full Process Manual, templates, checklists and examples.    It covers…

  1. How to develop a Requirements Initiation Report and its importance.
  2. How to run Use Case Modeling workshops.
  3. How to Document Use Cases.
  4. How to model for success.
  5. How to review a requirements model.
  6. How to capture technical and support requirements.
  7. How to design Business Object Models using UML.
  8. How to project manage requirement Modeling
  9. How to design user interfaces.
  10. How to use the requirements to evaluate products.

For further information and reference sites please contact us at eTrack.

eTrack Support for Tracking Requirement

eTrack supports Requirement Tracking.

a) Use case scenarios can be written into the Notes tab of eTrack and related to each other with many to many relationships.
b) ‘Non Functional’ requirements can be defined in templates so a complete checklist of all things to consider can be created for each project.c) Your process and methodology guidelines and templates can be made visible at a users finger tips or a direct link made to an Intranet methodology. This can be continually improved by encouraging users to raise suggestions in eTrack that flow through approval steps using the workflow capabilities.
d) Change Requests can be raised using eTrack’s Issue Tracking and Help Desk capabilities that can be related to the requirements or use cases.
e) Test Cases can be created that relate to the requirements or refer to use cases as the test procedures. Different groups of Test Cases can be combined to form Test Runs, say for regression testing at various stages of the release cycle (eg: full, 3 days before release, 2 hours before release). Instances of the Test Runs can be created with assigned people and results recorded.

In addition the use cases and requirements can be directly assigned to people, budgeted and scheduled. There is no need to create separate tasks and link the use cases to the tasks for scheduling since the requirements are just another type of work item with their own views.

This is a very brief overview of Requirements Tracking.  Please contact eTrack for more information and a demonstration.