1 creation versus evolution. 2 creation versus evolution the theory of intelligent design holds that...

1

Creation

versus

Evolution

2

Creation versus Evolution

The Theory of Intelligent Design holds that certain aspects of the Universe are best explained by an intelligent cause rather than an undirected process.

3

Workflow versus Spinning Wheels

Intelligent TeamTrack Design holds that certain aspects of a Solution are best implemented by intelligent planning rather than an undirected development.

4

Creation versus Evolution

Intelligent Design is the science of design detection, or rather, how to recognize patterns arranged by an intelligent cause for a purpose.

5

Intelligent TeamTrack Design

Intelligent Design is the science of design detection, or rather, how to recognize patterns arranged by an intelligent cause for a purpose. Ditto for

Intelligent “TeamTrack” Design

6


Intelligent Cause

Goal: To automate processes for NASA’s many hiring organizations that will provide a new hire with all of the things needed in order for that person to become a productive member of the business community as soon as possible.

Case example: Create a New Hire Check-In System

7


Intelligent Cause

Sub Goal 1: Provide those who are responsible for a part of the check in process with all of the information they need in order to manage and fulfill their duties, and provide this information in a timely manner.

Sub Goal 2: Provide those who are responsible for overseeing the check in process with easy access to the information they need to track its progress.

Case example: Create a New Hire Check-In System

8


NASA employs Civil Servants and Contractors and each new person must be uniquely identified and described.

The process for checking in a Contractor is slightly different from the process for a Civil Servant.

There are certain standard things that each person must have, such as a badge and a workspace, and many optional things that can be assigned to a person.

These things must be requested, able to be approved, and made available, assigned, or given access to.

Case example: Create a New Hire Check In System

Business Rules

9


The new Check In system must automatically create standard requests and provide for entering optional requests.

A formal Request Approval process is required. Request Providers and Approvers must be notified. One or more ways to track the progress of all requests

related to a given person or provider must be available. Automatic Interfaces with external systems are

required. A way to Cancel the check in and all requests is needed.


Business Rules

10


“I can explain things for you, but I can’t

understand them for you.”

11


Things to consider before starting a Workflow

Understand exactly what the Ultimate Goal is and what indicates its completion.

Ex: Goal - “Provide a New Hire with everything they need.” Ex: Completion - “All New Hire Requests have been

satisfied.”

Understand the Sub-Goals Ex: “Manage and Track individual requests and approvals.”

Identify the Reporting Needs Ex: “All Requests for a Given Person”; “Overdue Requests”

Identify the User Roles Ex: “Hiring Organization, Requester, IT Department,

Facilities..”

12


Understand the movement of information between individuals and / or systems.

Understand who needs to supply what information, and when.

Understand who needs to see what information, and when.

Understand whether or not tasks can be performed in parallel or must be performed in a sequence.

Understand what DOESN’T need to be seen at a particular point in the process.

Keep the user from being overwhelmed with unnecessary information.


13


Understand the permissions and restrictions for viewing and updating data fields, and transitioning records.

Ex: “Only the Security group (and the Hiring Organization) can see data related to a clearance investigation.”

(Helps to determine whether or not to use multiple primary tables, or both primaries and auxiliaries, and whether or not to use multiple projects, and it also helps for determining default field placements in data sections.)

Understand the notification requirements. Who needs to know what, and when do they need to

know it, and how should they be notified.


14


Develop a set of Use Cases. A Single activity constitutes a single Use Case

Ex: “User creates a Person Record, or User approves a Request”

Describe the data that needs to be captured. “The person’s name, identifiers, organization,

location..” Describe the expected results

“The system stores the record and presents the option to create a check in record or create a stand alone request record.”

Use Cases become the basis for the system design and implementation as well as for the test plans.


15


Components of a Typical TeamTrack Design One or more Primary Tables

Zero or more Auxiliary Tables A Set of User Roles (i.e. User Groups)

Each having specific data views and permissions

One or more Workflows One or more Projects TeamScripts Notifications Reports

16


Aspects of a TeamTrack Implementation

Table and Field Relationships Inter-Table Field Dependencies Item (or Record) Type Designations Assigning Transitions to certain User Groups Viewing and Transitioning based on Ownership Multiple Projects to control data views and

permissions and to provide for reporting needs Enabled and Disabled States and Transitions

Folders for Managing the Workload Subtasks and Posting Records and Triggers

17


Primary Entities and Objects

Persons Hiring Organization (Requesters) Request Providers Check In Records Request Records


18


Supporting Entities and Objects

Person Types Physical Locations Contracting Agencies Request Provider Departments Specific things to be requested


19


Collect the data elements and build the data model


20



Building Relationships and Dependencies

21




22




23




24




25




26




27




28




29



Persons Workflow – With SubtaskingBuilding Relationships and Dependencies

30




Requests Workflow

31




32




33



Check In Workflow

Multiple Projects

34



Check In Workflow

Multiple Projects

35



Check In Workflow

Multiple Projects

36



Sub TaskTransitions

37



AutomaticallyCreateRequestRecords

38



Allow for thecreation ofStand AloneRequests

39



Automatically Creating Request Records

40



Sub TaskRecordsfrom theCheck InWorkflow

41



Sub TaskRecordsfrom thePersonsWorkflow

42


Using Item Types to control process flow

Case example: Create a New Hire Check In SystemRequests Workflow

43




44




45


Case example:

TheCheck-InWorkflowwithParallelProcesses

46




47




48




49


Example: Multiple Projects

PostingRecords toa secondWorkflow

50

Creation

versus

Evolution?

51


In reality, Intelligent TeamTrack Design is a

combination of Creation and Evolution, with both being guided by an intelligent

understanding of the capabilities and limitations of the the TeamTrack product.

1 creation versus evolution. 2 creation versus evolution the theory of intelligent design holds that...

Documents