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

Slides:



Advertisements
Similar presentations
Testing Relational Database
Advertisements

HR SERVICE REQUEST SYSTEM Department Demonstrations February 2012.
PantherSoft Financials Smart Internal Billing. Agenda  Benefits  Security and User Roles  Definitions  Workflow  Defining/Modifying Items  Creating.
SYSTEM ANALYSIS & DESIGN (DCT 2013)
Systems Analysis and Design 9th Edition
Administration & Workflow
Better Maintenance of the Schedule of Classes Through Customization and Security.
© 2002 by Prentice Hall 1 David M. Kroenke Database Processing Eighth Edition Chapter 10 Database Application Design.
Manager Desktop & Supervisor ID UL Meeting December 15, 2006.
Hands-On Microsoft Windows Server 2003 Administration Chapter 3 Administering Active Directory.
EmpowHR EmpowHR Security Overview. 2 Application Security Administration Permission List Roles User Profiles Row level security Distributed Security Administration.
Employee Central Presentation
---Confidential 1 Order Management Training. ---Confidential 2 Introduction Three cycles in Oracle Applications Plan to make. Order to cash Procure to.
FI$Cal Change Discussion Guide Primavera Guide March 2015.
Lecture 7 Access Control
Process Modeling SYSTEMS ANALYSIS AND DESIGN, 6 TH EDITION DENNIS, WIXOM, AND ROTH © 2015 JOHN WILEY & SONS. ALL RIGHTS RESERVED. 1 Roberta M. Roth.
Chapter 3 Object-Oriented Analysis of Library Management System(LMS)
Databases & Data Warehouses Chapter 3 Database Processing.
1 System for Administration, Training, and Educational Resources for NASA Managing Access.
Software Configuration Management (SCM)
Sage CRM Developers Course
VERSION 7 What’s to Come?. Workflow – Lifecycle Definition  Ability to define custom Lifecycles NEW BEING WORKED IN REVIEW WAITING FOR APPROVAL APPROVED.
SMART Agency Tipsheet Staff List This document focuses on setting up and maintaining program staff. Total Pages: 14 Staff Profile Staff Address Staff Assignment.
NAMS Account Activation Training. 2 What is NAMS? The NASA Account Management System is NASA’s centralized process for requesting and maintaining accounts.
WMS systems manage and coordinate several independent subtasks. The coordination problems get even more serious when the subtasks are performed on separate.
Introduction to the Nevada SharePoint Site
Changing Perspective From Structured to Object-oriented.
RECALL THE MAIN COMPONENTS OF KIM Functional User Interfaces We just looked at these Reference Implementation We will talk about these later Service Interface.
©2004 Deloitte Drop Shipment and Back to Back Order Processes in Oracle 11i July 19, 2004.
Copyright © 2007, Oracle. All rights reserved. Managing Concurrent Requests.
Database Management. ICT5 Database Administration (DBA) The DBA’s tasks will include the following: 1. The design of the database. After the initial design,
Event Management & ITIL V3
© 2008 IBM Corporation ® IBM Cognos Business Viewpoint Miguel Garcia - Solutions Architect.
SiS Technical Training Development Track Day 9. Agenda  Understand Workflow Technology  Practice of Workflow (Instructor Led)
1 Schema Registries Steven Hughes, Lou Reich, Dan Crichton NASA 21 October 2015.
Database Design and Management CPTG /23/2015Chapter 12 of 38 Functions of a Database Store data Store data School: student records, class schedules,
CiviContacts. Agenda CiviCase What is CiviCase? What does it do? How to create a case?
Requirements Capture. Four Steps of requirements capture List candidate requirements Understand system context Capture functional requirements Capture.
Writing Requirements the Use-Case Way Sreeram Kishore Chavali.
7 Systems Analysis and Design in a Changing World, Fifth Edition.
Use Case Diagram The purpose is to communicate the system’s functionality and behaviour to the customer or end user. Mainly used for capturing user requirements.
MCSE Guide to Microsoft Exchange Server 2003 Administration Chapter Five Managing Addresses.
Lecture 13.  Failure mode: when team understands requirements but is unable to meet them.  To ensure that you are building the right system Continually.
22 August, 2007Information System Design IT60105, Autumn 2007 Information System Design IT60105 Lecture 8 Use Case Diagrams.
Systems Analysis and Design 8th Edition
Winter 2007SEG2101 Chapter 31 Chapter 3 Requirements Specifications.
Chapter 12: Service Requests. Streamlined citizen service processes: “3-1-1” Streamlined citizen service processes: “3-1-1” Service citizen requests Service.
Protection & Security Greg Bilodeau CS 5204 October 13, 2009.
Copyright © 2007, Oracle. All rights reserved. Using Document Management and Collaboration Appendix B.
Analysis Classes. What Is an Analysis Class?  A class that represents initial data and behavior requirements, and whose software and hardware-oriented.
SharePoint Workflow Prepared By: Eng. Rasha Farouk.
Copyright © 2007, Oracle. All rights reserved. Managing Items and Item Catalogs.
Overview of Basic 3D Experience (Enovia V6) Concepts
ACO 101: Use cases What do the users do?. When building a system You begin with the Use Case Analysis – When looking at the system as a whole, Use Case.
Introduction: Databases and Database Systems Lecture # 1 June 19,2012 National University of Computer and Emerging Sciences.
oracle apps order management training
Moshe Shechter | Alma Product Manager
SharePoint 101 – An Overview of SharePoint 2010, 2013 and Office 365
Software Project Configuration Management
Accounting Information Systems: A Business Process Approach
RFID enabled Solutions
Fundamentals of Information Systems, Sixth Edition
GMS.NET Security Overview.
Start at 17th March 2012 end at 31th March 2012
Resource Sharing Locate
Lesson 25: Task Management
Access Lesson 2 Creating a Database
CLIENT RELATIONSHIP MANAGEMENT KEEPING TRACK OF REQUESTS THE EASY WAY
DATABASES WHAT IS A DATABASE?
Contract Management Software 100% Cloud-Based ContraxAware provides you with a deep set of easy to use contract management features.
Presentation transcript:

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 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 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 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 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 Intelligent TeamTrack Design “I can explain things for you, but I can’t understand them for you.”

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 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 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 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 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 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 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 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 Intelligent TeamTrack Design Collect the data elements and build the data model Case example : Create a New Hire Check In System

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

50 Creation versus Evolution ?

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.