• Like
  • Save
My Version Of Rocket Science V4
Upcoming SlideShare
Loading in...5
×
 

My Version Of Rocket Science V4

on

  • 516 views

A selection of three of my utilities that have helped me make sense of Projects/Programmes from a testing perspective

A selection of three of my utilities that have helped me make sense of Projects/Programmes from a testing perspective

Statistics

Views

Total Views
516
Views on SlideShare
511
Embed Views
5

Actions

Likes
0
Downloads
0
Comments
0

2 Embeds 5

http://www.linkedin.com 3
https://www.linkedin.com 2

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • The techniques presented here are available in many different guises! Obviously, there are numerous high-powered, corporate-level amalgamation and assimilation tools that do exactly what I’m achieving here (but they are rather expensive) but this is a glimpse into my own practical productivity tools that I use in my testing arena. My tools have evolved from years ago. They started as a simple (IBM) JCL Decompositer. The Decompositer grew from extracting simple JCL Job Decks, and mapping those internal/external file dependencies into two-dimensional tables to this suite of tools. DocIndex – extracts textual info from Word Documents into two-dimensional tables. It parses the Word object model into two tables to form a Table of Contents and text body repository of all paragraphs in a Word document. InternetMiner – does a similar job to DocIndex by extracting HTML data from URLs on the Internet, Intranet or Extranet into two-dimensional tables. It parses the Internet Explorer object model into two tables to form a table of contents and text body repository of all text data on the web page. It also maintains details of all Hyperlinks and scripts executed on each web page. VisioDecompositer – does a similar job to both DocIndex and InternetMiner by extracting (properly formed) Visio diagram information into a two-dimensional table. It parses the Visio object model into one table to form a two-dimensional view of boxes and lines on a page. The common theme outlined here is that decomposition takes place into two-dimensional tables. Common search words or phrases that are meaningful to a project, or programme or an organisation are quickly linked across one (or more) KeyDoc repositories. The natural and logical organisation of Word documents, Visio diagrams and internet/intranet web pages allows sentences and paragraphs of text data to be stored “in context” with one another – this facilitates a far more powerful search facility than can be achieved by conventional means. This presentation shows how

My Version Of Rocket Science V4 My Version Of Rocket Science V4 Presentation Transcript

  • My version of rocket science - 1 N
    • This presentation airs an intelligent way of using textual documentation with diagrammatic information found across all projects and programmes in today organisations.
    • 3 tools– DocIndex , InternetMiner and VisioDecompositer
    • One unique way to access and cross-reference source material and turn it into linked, contextual information that covers an entire project, programme or even organisation. The common theme identified here is that decomposition of data takes place into a common format
    • Extract text from Word documents, text from Internet/intranet web pages and diagrammatic information from Visio diagrams into two-dimensional tables and use intelligent cross-referencing to enhance the view of a project/programme or organisation
  • My version of rocket science - 2 N
    • KeyDocs will define the Project, Programme or Organisation. These documents will (usually) be the key deliverable documents from the SDLC (SUMMIT in the case of M&S). Originally created to enable me to prove (automatically) test coverage at any level in an organisation
    • KeyDocs repository for a Project (say, 80 documents in the case of IS). KeyDocs repository for a Programme (say, 400 documents in the case of Foods). KeyDocs repository for an organisation (say, 1500 documents in the case of M&S)
    • The more documents in the KeyDocs repositories, the better the ability to cross-refer textual and diagrammatic information “across the piste”. It all aids the Big Picture (from a testing perspective) but ultimately enables far greater power to be unleashed. The key principle here is the quality of the defined KeyDocs is paramount ! Suggest you include ONLY signed-off (non-draft) documents from SUMMIT
    • Not convinced? Here are some screen shots to give you a better flavour of what I’ve been blagging on about in these first couple of slides and the underlying notes….
  • DocIndex 1 of 10 N
    • DocIndex (viewer) main menu
  • DocIndex 2 of 10
    • KeyDocs main menu
  • DocIndex 3 of 10
    • Display a selectable list of KeyDocs
  • DocIndex 4 of 10
    • Now display a summarised list of the sections in the selected KeyDoc
  • DocIndex 5 of 10
    • Select one of the sections in the document and the text is displayed
  • DocIndex 6 of 10
    • The power of this tool lies in the fact that ALL relevant project/programme/organisational-level documentation is captured into the tool in a pertinent and common format
  • DocIndex 7 of 10
    • The contents of all of the KeyDocs are stored in two tables: tblSectionHeaders – which is a summarised “table of contents” for a KeyDoc
  • DocIndex 8 of 10
    • and File_Decomposition – which is textual body for all KeyDocs
  • DocIndex 9 of 10 N
    • There is a keyword/key phrase Search facility for the group of KeyDocs, which allows the user to quickly become acquainted with “project specific” terminology
  • DocIndex 10 of 10
    • and the reader can, very quickly, become acquainted with the context in which the specific search terms are used.
  • InternetMiner 1 of 10 N
    • InternetMiner main menu
  • InternetMiner 2 of 10
    • Enter a suitably relevant URL - in this case, found by doing a “biztalk performance test” search string in Google UK
  • InternetMiner 3 of 10
    • And the page(s) are decomposed into InternetMiner , in much the same way as DocIndex
  • InternetMiner 4 of 10
    • The list of decomposed URLs can be viewed (and refreshed either manually or automatically) so that the information contained therein is always up to date
  • InternetMiner 5 of 10
    • And the content from ALL of the decomposed URLs can be viewed at a glance
  • InternetMiner 6 of 10 N
    • And relevant search keywords or key phrases can be entered
  • InternetMiner 7 of 10
    • And the result be displayed (in various forms) - so that the user can see, contextually, where the search term is used
  • InternetMiner 8 of 10
    • Alternative views of the results (and search strings) can be made
  • InternetMiner 9 of 10 N
    • And you can quickly build up a picture of the various (in this case technical Biztalk) phrases
  • InternetMiner 10 of 10 N
    • And how they relate to the overall topic (Biztalk Performance testing)
  • VisioDecompositer 1 of 2 N
    • VisioDecompositer takes a straightforward Visio diagram…..
  • VisioDecompositer 2 of 2 N
    • And converts it into two-dimensional information that can be “mapped” into test cases or test scripts quite easily
  • Going forward N
    • Can I suggest that you identify 20 of your projects’ Key Documents (KeyDocs) – both Word documents and those useful diagrams that EVERY projects’ personnel refers to at some stage in their projects/programmes lifecycle and I’ll show you what these tools can do for you
    • Remember, the more documents in the KeyDocs repositories, the better the ability to cross-refer “across the piste”. The key principle here is the quality of the defined KeyDocs is paramount ! Suggest you include ONLY signed-off (non-draft) documents from the various SUMMIT Quality Gates
    • Please refer to the Notes Page for suggested document types to include in your KeyDocs repository – but feel free to include your own as you see fit
    • I’ll run your material through my (automated) tools and show you what pops out the other end – you’ll be surprised
  • End of presentation