1. A Conceptual Overview Presentation: 60 minutes Q&A: 30 minutes

2. Why this Presentation? – To update on progress – To obtain feedback – Facilitate the next phase of development

3. What This Presentation Covers Outlines issues with the current development process How EpioDesigner proposes to tackle these issues The EpioDesigner set of tools Testing our methodology: the PR application Refining the development process Open Q&A session

4. The Problem – ‘ Language barrier’ Difficult to capture requirements and manage expectations Assumptions and information gaps Information loss Hard to capture and track all information Inefficient and inaccurate prototyping More information loss Repetition and lack of reuse Lengthy implementation time

5. The Solution – Common information pool Structured information capture Information is centralised and integrated More efficiency, consistency and reuse Provides a mechanism to speak the same language

6. So What Is Epiodesigner? It’s a set of tools… –Manages the solution lifecycle via a common information pool Co-ordinates multidisciplinary teams Captures requirements and system design Facilitates prototyping process Produces template applications …and a process –Structures and co-ordinates the current software lifecycle –Not restricted to building web applications

7. Requirements Analysis Requirements Analysis System Design Proto- typing User Testing Implementation Testing Deployment The current solution process ROLES SOLUTION PROCESS Requirements Analysis Requirements Analysis System Design Proto- typing User Testing Implementation Testing Deployment PROBLEMS Inefficient analysis and design methodology Insufficient time spent prototyping Long implementation time Insufficient testing Deployment difficulties ClientUsersBusiness AnalysisDesignDevelopment

8. Requirements Analysis Requirements Analysis System Design Proto- typing User Testing Implementation Testing Deployment The EpioDesigner solution ROLES SOLUTION PROCESS Requirements Analysis Requirements Analysis SOLUTION TOOLS SOLUTION METADATA ClientUsersBusiness AnalysisDesignDevelopment ProjectAnalysis & DesignPrototypingDevelopmentTestingSupport

9. Requirements Analysis Requirements Analysis System Design Proto- typing User Testing Implementation Testing Deployment The EpioDesigner solution ROLES SOLUTION PROCESS Requirements Analysis Requirements Analysis SOLUTION TOOLS SOLUTION METADATA ClientUsersBusiness AnalysisDesignDevelopment System Design ProjectAnalysis & DesignPrototypingDevelopmentTestingSupport

10. Requirements Analysis Requirements Analysis System Design Proto- typing User Testing Implementation Testing Deployment The EpioDesigner solution ROLES SOLUTION PROCESS Requirements Analysis Requirements Analysis SOLUTION TOOLS SOLUTION METADATA ClientUsersBusiness AnalysisDesignDevelopment System Design Proto- typing User Testing ProjectAnalysis & DesignPrototypingDevelopmentTestingSupport

11. Requirements Analysis Requirements Analysis System Design Proto- typing User Testing Implementation Testing Deployment The EpioDesigner solution ROLES SOLUTION PROCESS Requirements Analysis Requirements Analysis SOLUTION TOOLS SOLUTION METADATA ClientUsersBusiness AnalysisDesignDevelopment System Design Proto- typing User Testing Implementation PrototypingProjectAnalysis & DesignDevelopmentTestingSupport

12. Requirements Analysis Requirements Analysis System Design Proto- typing User Testing Implementation Testing Deployment The EpioDesigner solution ROLES SOLUTION PROCESS Requirements Analysis Requirements Analysis SOLUTION TOOLS SOLUTION METADATA ClientUsersBusiness AnalysisDesignDevelopment System Design Proto- typing User Testing Implementation PrototypingProjectAnalysis & DesignSupport Testing DevelopmentTesting

13. Requirements Analysis Requirements Analysis System Design Proto- typing User Testing Implementation Testing Deployment The EpioDesigner solution ROLES SOLUTION PROCESS Requirements Analysis Requirements Analysis SOLUTION TOOLS SOLUTION METADATA ClientUsersBusiness AnalysisDesignDevelopment System Design Proto- typing User Testing Implementation PrototypingProjectAnalysis & Design Testing DevelopmentSupportTesting

14. Requirements Analysis Requirements Analysis System Design Proto- typing User Testing Implementation Testing Deployment The EpioDesigner solution ROLES SOLUTION PROCESS Requirements Analysis Requirements Analysis SOLUTION TOOLS SOLUTION METADATA ClientUsersBusiness AnalysisDesignDevelopment System Design Proto- typing User Testing Implementation Testing Deployment PrototypingProjectAnalysis & DesignSupportDevelopmentTesting

15. The Metadata Layer Entities Patterns Styler Data Modeling Specifications documents Project Reports Framework-type applications Epiowave applications Prototypes

16. Business Analysis implications Integration of relevant CAM components Structured scripts and questionnaires to get the accurate information from the client including… –Role Control Diagrams –Process Diagrams Increased client satisfaction Less guesswork and less meetings

17. The Epiodesigner set of tools Project Manager Role Manager Entity Manager Navigation Manager Workspace Manager Pattern Manager Styler Usability Tester

18. Entity Manager An Entity: –is unique to other objects in the system –is managed by an application –contains more than one piece of information –has properties and actions An Entity is not: –a role in the system –a collection of properties that are captured elsewhere in other entities []

19. Entity Manager Associated entity and pattern General or specific Display options Validation Associated entities Display options Pattern behaviours Interface controls Validation Data Model Siblings Parent to child RolesRelationships PropertiesActions []

20. Entity examples These entities are from the PR application, our test-case in-house application SIBLING Contribution Press Release Comment Digital Record Comment Digital Record PARENT TO CHILD

21. Entity Manager -Relationships

22. Entity Manager - Properties

25. Entity Manager - Actions

28. Entity Reuse Default preset properties and actions Categorised entity library for reuse Functionality templates –Groupings of default actions –Extensible and scalable Import and export via standard formats (UML, E-R…) On-sell potential –Client subscription to libraries –Client submission to libraries

29. Navigation Manager Adds to entity information Transforms entity actions into navigation structures Manages navigation hierarchy, appearance and behaviour []

30. WORKSPACE Workspace Manager Link between patterns and navigation Library of workspaces for reuse and consistency NAVIGATION PATTERN [] [][]

31. Pattern Manager A pattern is: –a way of visualising and interacting with data –a predefined managed piece of functionality –applied to none or more entities, which it then controls and visualises Patterns have options that affect their behaviours A pattern can be applied to specified properties of an entity A Pattern is not like a transform, it is metadata required to produce both prototypes and applications

32. Pattern Manager Patterns are mainly based on Epiowave V2 design standards

33. Pattern Manager List –List – Simple –List – Select Single –List – Select Multiple –List – Categorised Confirm –Confirm/Report Details –Details – View –Details – Edit –Details – Enter Others –Reorder –Tree-view There are four groups of patterns:

34. Pattern Manager List pattern types Simple List List – Select Single List – Select Multiple List - Categorised

35. Pattern Manager List pattern types Simple List List – Select Single List – Select Multiple List - Categorised

36. Pattern Manager List pattern types Simple List List – Select Single List – Select Multiple List - Categorised

37. Pattern Manager List pattern types Simple List List – Select Single List – Select Multiple List - Categorised

38. Pattern Manager Details pattern types Details – View Details – Edit Details – Enter

39. Pattern Manager Details pattern types Details – View Details – Edit Details – Enter

40. Pattern Manager Details pattern types Details – View Details – Edit Details – Enter

41. Pattern Manager Confirm pattern type Confirm and Report

42. Pattern Manager Reorder pattern type Reorder

43. Pattern Manager Tree-view pattern type Tree-View

44. Pattern Manager Using pattern options (some examples) Links Properties Numeric Paging Page Counting Simple Search Display Quantity Sort By Add Icon Alphabetical Filtering

45. Pattern Manager Using pattern options (some examples) Links Properties Numeric Paging Page Counting Simple Search Display Quantity Sort By Add Icon Alphabetical Filtering

46. Pattern Manager Using pattern options (some examples) Links Properties Numeric Paging Page Counting Simple Search Display Quantity Sort By Add Icon Alphabetical Filtering

47. Pattern Manager Using pattern options (some examples) Links Properties Numeric Paging Page Counting Simple Search Display Quantity Sort By Add Icon Alphabetical Filtering

48. Pattern Manager Using pattern options (some examples) Links Properties Numeric Paging Page Counting Simple Search Display Quantity Sort By Add Icon Alphabetical Filtering

49. Pattern Manager Using pattern options (some examples) Links Properties Numeric Paging Page Counting Simple Search Display Quantity Sort By Add Icon Alphabetical Filtering

50. Pattern Manager Using pattern options (some examples) Links Properties Numeric Paging Page Counting Simple Search Display Quantity Sort By Add Icon Alphabetical Filtering

51. Pattern Manager Using pattern options (some examples) Links Properties Numeric Paging Page Counting Simple Search Display Quantity Sort By Add Icon Alphabetical Filtering

52. Pattern Manager Using pattern options (some examples) Links Properties Numeric Paging Page Counting Simple Search Display Quantity Sort By Add Icon Alphabetical Filtering

53. Builder Creates and links workspaces, patterns and navigation from the entity metadata []

54. Exporting the prototype Prototypes are disposable Prototypes are exported in different modes, for different disciplines –Client –Developer illustration –User-testing –Role-specific exports Prototype metadata is refined iteratively, then re-exported Build

55. Styler Customise colour skins, icons and corporate branding

56. Usability Tester Prototypes can be exported in user- testing mode Interactive evaluation forms Highlight areas with a high density of functionality for testing

57. A Better Result DesignDevelopment Prototype driven: P SOLUTION METADATA Metadata driven: Design Development P ? ? ?

58. A Better Result DesignDevelopment Prototype driven: P SOLUTION METADATA Metadata driven: Design Development P ? ? ?

59. Further Thoughts ‘Flight-check’ process –Identifies weak or missing metadata –Rates/checks the project against best-practice, and for conflicts and usability issues Clients can check current status of their project

60. Summary EpioDesigner: –is the bridge to better integrate software development teams –centralises all information during the development process –Provides formalised requirements analysis and specification structure –produces more accurate and realistic prototypes –automatically code-generates entire applications

61. Deployment Summary Metadata Entity Manager Pattern Manager Navigation Manager Workspace Manager Styler Usability Tester Export Business Analysis The EpioDesigner process is not linear…

62. Summary Business Analysis Deployment Metadata Entity Manager Pattern Manager Navigation Manager Workspace Manager Styler Usability Tester Export …but circular and iterative…

63. Summary Business Analysis Deployment Metadata …integrates various disciplines…

64. Summary … Leading to More efficiency, consistency and reuse

69. Questions & answers