COPS Model by sNDd0a3

VIEWS: 4 PAGES: 12

									                   COPS Model
      (Cooperative On-line Problem-tracking System)


                      HELLSTREET POLICE




Acknowledgement & Disclaimer to Peritus Software Services
Dispatcher
             Desk Sergeant
             • collects client requests
             • knows how to locate
               clients and "officers"
             • keeps problem
               documentation              User/Clients
Process Problem Opportunities
P1 – Info Gathering &                Work
     People Assignment           Accomplished
P2 – Initial Work Period
P3 – Period of
     Diminishing Return
P4 – Housekeeping
                                      P1        P2        P3            P4       Time
         Problems                           Opportunities
P1     Insufficient Info                   Gather information before starting;
       Wrong assignments                   Make correct assignments
P2     Wandering in solution               Do up-front planning; Use teaming to
       space; Human error                  reduce human error; Stick to a strategy;
                                           and Broaden solution space
P3     Psychological inhibitions of        Know when to get help;
       relying on buddy network            Develop a solution network
P4     Don't like to document              Document as you go
                      White Board   Captain
                                    • community
                                      relations
  Dispatcher                        • resource
• oversees task                       provider
  assignments
• helps in squad
  car selection                     Squad
• ability to juggle
  several balls in                  Members
  air at one time
TAC#   Description   Squad Car    Status Start-date End-date Interv
.
3236   TCP/IP-interf. Jim/Jay     act.    May 1     May 3
3238   TCP/IP-recov. Mary/Fay/Guy test    May 1     May 4
3524   GUI-map        Guy/John     req    May 2     May 5    min.
4230   C-Opt-expr.     John/Jan    rev    May 3     May 5    com.

                                          White Board (enlarged)
                                 Squad
                                 Car1

Dispatcher                                              Squad
                                                        Car3
       Squad
       Car2
              Driver
               Has major responsibility for solving the
               problem. Pings possible solution(s) to
               rider. Tends to be a Product Specialist.

Ping   Pong

              Rider
               Reviews possible solution(s) and
               pongs any concerns back to driver.
               Tends to be a Maintenance Specialist
                                             Dispatcher
Rules                Discussant Driver
• < 20 minutes                       Rider
• recorder & timer
  are appointed
• five distinct steps
  are followed
• action plan is
  recorded & agreed to Recorder                Timer
• time taken is recorded
Rules
• < 2 hours
• recorder appointed
• squad team identifies      Captain                Dispatcher
  problems based on
  "Book of Annotations"
• action plan is recorded              Driver
  and agreed to                             Rider
• time taken is recorded


Outcome:
 Squad team may ask
 for another round or       Recorder                  Timer
 call in SWAT Team
                                           Users
                    Expert
Formed to attack the hard problems.

Approach
• Specialists called in to use
  formal approach
• Key elements of the defect
  are extracted
• Hypothesis is formulated
• Affected subsystem and variables
  are isolated and specified in UNITY
• Hypothesis is formalized in UNITY
• UNION Theorem is applied

        p co q in F  G  p co q in F  p co q in G

• Defect is isolated corrected and tested
                   - Architecture -
                Management                 Book of
                  Reporting                Annotations




                                         Config Control
                                         & Annotation
Environmental                            Archiving
Interfaces

                                      Book of
                     Process
                 Optimization         Case Histories
             - Basic Components -
• Project Management
                              • Document Processing
• Spreadsheet & White Board     - Book of Annotations
• Database                      - Book of Case Histories
• Diagnostic Tools            • Configuration Management
• E-mail                      • Code Handling Tools
• Personal Productivity       • Interfaces to Existing
  Tools                          Databases
                  • Select Talented People
                  • Mix Product & Maintenance
                    Specialists
                  • Train to Work in Teams
                  • Motivate and Reward
                  • Continually Develop and
                    Improve Team

6 to 12 members     Expect 50% to 60%
                    Productivity
                    Improvement

								
To top