Presentation is loading. Please wait.

Presentation is loading. Please wait.

1 Creation versus Evolution. 2 Creation versus Evolution The Theory of Intelligent Design holds that certain aspects of the Universe are best explained.

Similar presentations


Presentation on theme: "1 Creation versus Evolution. 2 Creation versus Evolution The Theory of Intelligent Design holds that certain aspects of the Universe are best explained."— Presentation transcript:

1 1 Creation versus Evolution

2 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 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 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 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 6 Intelligent TeamTrack Design 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 7 Intelligent TeamTrack Design 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 8 Intelligent TeamTrack Design 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 9 Intelligent TeamTrack Design 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. Case example : Create a New Hire Check In System Business Rules

10 10 Intelligent TeamTrack Design “I can explain things for you, but I can’t understand them for you.”

11 11 Intelligent TeamTrack Design 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 12 Intelligent TeamTrack Design 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. Things to consider before starting a Workflow

13 13 Intelligent TeamTrack Design 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. Things to consider before starting a Workflow

14 14 Intelligent TeamTrack Design 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. Things to consider before starting a Workflow

15 15 Intelligent TeamTrack Design 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 16 Intelligent TeamTrack Design 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 17 Intelligent TeamTrack Design Primary Entities and Objects Persons Hiring Organization (Requesters) Request Providers Check In Records Request Records Case example : Create a New Hire Check In System

18 18 Intelligent TeamTrack Design Supporting Entities and Objects Person Types Physical Locations Contracting Agencies Request Provider Departments Specific things to be requested Case example : Create a New Hire Check In System

19 19 Intelligent TeamTrack Design Collect the data elements and build the data model Case example : Create a New Hire Check In System

20 20 Intelligent TeamTrack Design Case example : Create a New Hire Check In System Building Relationships and Dependencies

21 21 Intelligent TeamTrack Design Building Relationships and Dependencies Case example : Create a New Hire Check In System

22 22 Intelligent TeamTrack Design Building Relationships and Dependencies Case example : Create a New Hire Check In System

23 23 Intelligent TeamTrack Design Case example : Create a New Hire Check In System Building Relationships and Dependencies

24 24 Intelligent TeamTrack Design Case example : Create a New Hire Check In System Building Relationships and Dependencies

25 25 Intelligent TeamTrack Design Case example : Create a New Hire Check In System Building Relationships and Dependencies

26 26 Intelligent TeamTrack Design Case example : Create a New Hire Check In System Building Relationships and Dependencies

27 27 Intelligent TeamTrack Design Case example : Create a New Hire Check In System Building Relationships and Dependencies

28 28 Intelligent TeamTrack Design Case example : Create a New Hire Check In System Building Relationships and Dependencies

29 29 Intelligent TeamTrack Design Case example : Create a New Hire Check In System Persons Workflow – With Subtasking Building Relationships and Dependencies

30 30 Intelligent TeamTrack Design Building Relationships and Dependencies Case example : Create a New Hire Check In System Requests Workflow

31 31 Intelligent TeamTrack Design Case example : Create a New Hire Check In System Building Relationships and Dependencies

32 32 Intelligent TeamTrack Design Case example : Create a New Hire Check In System Building Relationships and Dependencies

33 33 Intelligent TeamTrack Design Case example : Create a New Hire Check In System Check In Workflow Multiple Projects

34 34 Intelligent TeamTrack Design Case example : Create a New Hire Check In System Check In Workflow Multiple Projects

35 35 Intelligent TeamTrack Design Case example : Create a New Hire Check In System Check In Workflow Multiple Projects

36 36 Intelligent TeamTrack Design Case example : Create a New Hire Check In System Sub Task Transitions

37 37 Intelligent TeamTrack Design Case example : Create a New Hire Check In System Automatically Create Request Records

38 38 Intelligent TeamTrack Design Case example : Create a New Hire Check In System Allow for the creation of Stand Alone Requests

39 39 Intelligent TeamTrack Design Case example : Create a New Hire Check In System Automatically Creating Request Records

40 40 Intelligent TeamTrack Design Case example : Create a New Hire Check In System Sub Task Records from the Check In Workflow

41 41 Intelligent TeamTrack Design Case example : Create a New Hire Check In System Sub Task Records from the Persons Workflow

42 42 Intelligent TeamTrack Design Using Item Types to control process flow Case example : Create a New Hire Check In System Requests Workflow

43 43 Intelligent TeamTrack Design Case example : Create a New Hire Check In System Requests Workflow Using Item Types to control process flow

44 44 Intelligent TeamTrack Design Case example : Create a New Hire Check In System Requests Workflow Using Item Types to control process flow

45 45 Intelligent TeamTrack Design Case example : The Check-In Workflow with Parallel Processes

46 46 Intelligent TeamTrack Design The Check-In Workflow with Parallel Processes Case example : Create a New Hire Check In System

47 47 Intelligent TeamTrack Design The Check-In Workflow with Parallel Processes Case example : Create a New Hire Check In System

48 48 Intelligent TeamTrack Design The Check-In Workflow with Parallel Processes Case example : Create a New Hire Check In System

49 49 Intelligent TeamTrack Design Example : Multiple Projects Posting Records to a second Workflow

50 50 Creation versus Evolution ?

51 51 Intelligent TeamTrack Design 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.


Download ppt "1 Creation versus Evolution. 2 Creation versus Evolution The Theory of Intelligent Design holds that certain aspects of the Universe are best explained."

Similar presentations


Ads by Google