1 / 22

Notification System

Notification System. Functional Goals. Provide a single list for all university related communications Workflow items Non-workflow items Examples of non-workflow items: Your book is overdue A concert is coming up on campus Graduation checklist to all Seniors.

donald
Download Presentation

Notification System

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Notification System

  2. Functional Goals • Provide a single list for all university related communications • Workflow items • Non-workflow items • Examples of non-workflow items: • Your book is overdue • A concert is coming up on campus • Graduation checklist to all Seniors <---- Kuali Enterprise Workflow <---- Notification System

  3. 1

  4. 2

  5. 3

  6. 4

  7. 5

  8. 6

  9. 7

  10. 8

  11. 9

  12. 10

  13. 11

  14. 14

  15. 16

  16. 17

  17. Functional Requirements • Three types of notifications: • Things I have to do • Electronically • Manually • Things I need to know about • Things I want to know about • Subscribe to notification channels • Concerts on campus • Visiting lecturers in Computer Science <---- Kuali Enterprise Workflow

  18. Functional Requirements • Target groups of people or specific people • Control start and stop dates • Notifications automated by systems - s2s • Manual entry of notifications - generic client • Event notification • Integration with personal calendars • Multiple delivery end-points • Email • Text message to mobile phones

  19. Technical Goals • Adhere to SOA • Standards - WS-NOTIFICATION, OKI OSIDs, iCal, etc • Pluggable components - Spring, etc • Community Source • Collaborative development • Continue building existing relationships; create new ones • Leverage Kuali components • Kuali Enterprise Workflow (KEW) • Kuali Nervous System (KNS) • Kuali Enterprise Service Bus (KESB)

  20. Technical Design PluggableTicklers ChannelAdministration DeliveryPreferences NotificationSystem KNS Client System KNS Kuali Enterprise Service Bus Messaging Kuali EnterpriseWorkflow KNS AsynchronousProcessing Generic WebService Exposure Users andWorkgroups Action ListIntegration Logging

  21. Project Status • Two team members • Aaron Godert and John Fareira (CU) • Looking for 1-2 more teammates • Worked with KEW team last week on how we could leverage KEW • Finalize design within a few weeks • Hold initial retreat for developers mid-September • First release 3/1/2007

  22. Notification and Kuali • Re-use of Kuali work • Help KEW components mature into KESB • Help KNS mature into a standalone toolset • Useful functionality for Kuali suite • Leverage existing relationships for collaborative development • Community source at work • Kuali Enterprise Notification (KEN)???

More Related