Changes between Version 56 and Version 57 of Event/2011/GCI

Timestamp:

11/19/11 14:59:08 (13 years ago)

Author:

Nuwan Waidyanatha

Comment:

--

Event/2011/GCI

@@ -195 +195 @@
 for Common Alerting Protocol (CAP) with capabilities for multi-language alerting and multi-media delivery; use Agasti CAP Broker as a starting point (Nuwan)
 Difficulty : '''MEDIUM''' Proposed by: [http://lirneasia.net/profiles/nuwan-waidyanatha | Nuwan][[BR]] 
-'''Specific    : ''' Build a wireframe with functionality for the [http://www.incident.com/cookbook/index.php/Welcome_to_the_CAP_Cookbook | Common Alerting Protocol] messaging broker. It should follow a publisher subscriber model. Some specifications are in the [http://lirneasia.net/wp-content/uploads/2009/05/Sahana-CAP-Msg-Mod-v0.2.pdf | CAP Software Requirement Specifications] [[BR]]
+'''Specific    : ''' Build a [http://sixrevisions.com/user-interface/website-wireframing/ | wireframe] with functionality for the [http://www.incident.com/cookbook/index.php/Welcome_to_the_CAP_Cookbook | Common Alerting Protocol] messaging broker. It should follow a publisher subscriber model. Some specifications are in the [http://lirneasia.net/wp-content/uploads/2009/05/Sahana-CAP-Msg-Mod-v0.2.pdf | CAP Software Requirement Specifications] [[BR]]
 '''Measurable  : ''' CAP messaging broker is becoming a much sort after tool by many organizations. It is an ITU recommendation. Such tool can be easily adopted by governments and emergency coordination agencies for managing their alerting and situational awareness. [[BR]]
 '''Attainable  : ''' [[BR]]
@@ -207 +207 @@
 '''Reevaluate  : ''' Once the wireframe is built on the concluded requirements that will be put to test through the scenario based testing. [[BR]]
 
-=== Design a GUI (deliverable: "wireframes" = hard) ===
+=== Design a GUI to build and test XSL file ===
 Difficulty : '''MEDIUM''' Proposed by: [http://lirneasia.net/profiles/nuwan-waidyanatha | Nuwan][[BR]] 
-'''Specific    : ''' , for example with http://www.google.com/ime/transliteration/ engine or any other generic plug-in[[BR]]
-'''Measurable  : ''' [[BR]]
-'''Attainable  : ''' [[BR]]
-'''Relevant    : ''' [[BR]]
+'''Specific    : ''' Given that Sahana is getting heavy on XML there should be a tool to develop text, html, etc outputs based one's own XSL transformation file.  The user should be presented with the option to select the XML file; i.e. tags and schema, then include/exclude those tags with inserts of fixed text. The user should be able to preview the output. The built XSL file can then be stored to be used for a particular function. In this case it would be producing CAP message based user specific outputs for email, web, rss, twitter, google, etc. [[BR]]
+'''Measurable  : ''' This would allow super users to develop implementation specific CAP content delivery outputs. [[BR]]
+'''Attainable  : ''' [[BR]]
+Step 1 :: research existing available solutions to get a feel for the type of functionality needed [[BR]]
+Step 2 :: document and discuss the set of requirements with Sahana community [[BR]]
+Step 3 :: develop the wireframe and test it with test scenarios [[BR]]
+Step 4 :: document the set of specifications [[BR]]
+'''Relevant    : ''' The Irrigation department may want the CAP messages to be formed in one way in an email compared with that of the Health department. A rapid XSL development tool will put the burden of building and maintaining those finals in the hands of the users and implementers and not engineers. [[BR]]
 '''Time-bound  : ''' [[BR]]
-'''Evaluate    : ''' [[BR]]
-'''Reevaluate  : ''' [[BR]]
-for building implementation specific XSL documents that generate SMS, Email, IVR, tweet, etc multi-media delivery text outputs (Nuwan)
+'''Evaluate    : ''' design requirements and settling on them. [[BR]]
+'''Reevaluate  : ''' wirefram with the test scenarios [[BR]]