History of ITFVHA Organizational meeting: 1996, Orlando First meeting: 1997, San Diego, sponsored by NAHSC Second meeting: 1998, Delft, Netherlands, sponsored by Rijkswaterstaat Third meeting: 1999, Toronto, sponsored by ITS America Fourth meeting: 2000, Tsukuba City, sponsored by MOC/AHSRA Fifth meeting: 2001, Sydney, sponsored by ITS Australia / AAA Sixth meeting: 2002, Chicago, sponsored by TRB and ITS America Seventh meeting: 2003, Paris, sponsored by LIVIC Eighth meeting: 2004, Nagoya, sponsored by MLIT / AHSRA Ninth meeting: 2005, San Francisco, sponsored by ITS America / USDOT Tenth meeting: 2006, London, sponsored by UK Highways Agency Eleventh meeting: 2007, Versailles, sponsored by INRIA Twelfth meeting: 2008, New York City, sponsored by Parsons-Brinkerhoff Thirteenth meeting: 2009, Stockholm, sponsored by H3B Media Fourteenth meeting: 2010, Busan, sponsored by Korean Transport Institute Fifteenth meeting: 2011, Orlando, sponsored by Bishop Consulting
Wednesday, OCTOBER 3 8:30-9:00 9:00-9:30 9:3010:00 10:0010:30 10:3011:00 11:0011:30 11:3012:00 12:001:00 1:00-1:30 1:30-2:00 2:00-2:30 2:30-3:00 3:00-3:30 3:30-4:00 4:00-5:00 Thursday, OCTOBER 4 Welcome Reception Continental Breakfast in Art Gallery Team Meeting-Boardroom Meeting with Dir. Technology [RG] (4122) Gary K Meeting with BOT chair, vice chair [RT, RG] ( ) Meeting with Dean of Library [LW] (5329) Bob Francis Meeting with President, Norma, Pam Goad [RT] (Lee’s O) Library Faculty [LW] (Library Conference Room 4106) Meeting with Foundation Dir. [RG] (1005) Ritva Manchester Library classified staff [LW] (Library Conf. Rm 4106) Articulation & Transfer Task Force (5386) 2 Directors: Financial Aid, Enrollment Services [RG] (5227) C Melton and T. Haase Virtual College (Library Conf. Rm 4106) Meeting with VPAS [RG ] (1019A)—1 hour Daryl Campbell Meeting with VPAS [RG] (1019A) Advising Task Force [ ] (Gillian’s Office 2309) Meeting w/Dir. Auxiliary Services [RG] Bookstore Mary Kelemen ? Team Lunch & debrief time- (Boardroom) Industry Advisory Committee members (9208) Vice Presidents [RT] (Central) ACT [JA] (9208) ACT [RG] 9208? Mcnaughton…? Open Faculty Meeting [RT, LW,RG, ] (1104) Open Student Session [RT, LW] (9208) Workforce Education [KH] (5113) Meeting with Comptroller [RG] (1205) Stuart Trippel Team Meetings (Boardroom) Open Staff Session [RT, LW, RG, ] (9208) Service Learning (Center for Equity, Engagement, Service, 9302) Tour/meeting with Bob Roehl, Dir of Facilities [RG] (5105) Bob R Drama and Music Faculty [KH ] Theatre Lobby Curriculum Committee [JA, LW ] 1402 Team Meetings (Boardroom)
Traceability Forward Traceability (Domain requirement to Work Product) FR_001 All the important participants and active participants could be optionally S1, present in the meeting. More than a certain threshold (say 60%) of the S7 important participant’s preferences on the date and location need to be satisfied. A meeting shall be held when the total number of active and important participants is more than threshold value (say 50%) in which more than 70% of important participants participate. FR_002 “A distributed manner” means, the meeting that involves participants in S4 different geographical locations of the world will be monitored by the meting initiator in terms of how many people are participating and their time/location preferences. FR_003 The system shall plan meetings under the constraints expressed by S7 participants The system shall allow rep-planning of the meeting by permitting participants: S6 active, important and regular to provide and modify the exclusion set, preference set but before a meeting deadline. The system shall allow only the important participants to state preferences about the meeting location and allow the active participants to request special equipments on the meeting location but before a meeting deadline. FR_004 FR_005 Re-plan a meeting to support external constraints like two meeting held at S7 same time or at same location, that meeting take place which is of higher priority Date March 25, 2010
Contd. Contd.. [FR_004] -Re-plan a meeting to support the changing user constraints, that include modification to the exclusion set, preference set and/or preferred location before a meeting date/location is proposed; Issues – Incomplete. Does not indicate if all users or only certain set of users can modify the exclusion set, preference set in addition to location/time before a meeting/date location is proposed. Option1: The system shall allow re-planning of the meeting by providing privilege to all active, important and regular, to make modification to exclusion set, preference set and/or preferred location before a meeting date/location is proposed but before the deadline specified by the meeting initiator. Option2: The system shall allow re-planning of the meeting by permitting participants: active, important and regular to provide and modify the exclusion set, preference set but before a meeting deadline. The system shall allow only the important participants to state preferences about the meeting location and allow the active participants to request special equipments on the meeting location. Decision and rationale Option 2 is chosen as the system shall allow meetings to be re-planned based on user constraint changes of important and active participants only in terms of location and equipment providing an ordered execution and monitoring of the system. Option1 could increase the rounds of negotiations to schedule a meeting. Date March 2, 2010
Contd. Contd.. [FR_004] -Re-plan a meeting to support the changing user constraints, that include modification to the exclusion set, preference set and/or preferred location before a meeting date/location is proposed; Issues – Incomplete. Does not indicate if all users or only certain set of users can modify the exclusion set, preference set in addition to location/time before a meeting/date location is proposed. Option1: The system shall allow re-planning of the meeting by providing privilege to all active, important and regular, to make modification to exclusion set, preference set and/or preferred location before a meeting date/location is proposed but before the deadline specified by the meeting initiator. Option2: The system shall allow re-planning of the meeting by permitting participants: active, important and regular to provide and modify the exclusion set, preference set but before a meeting deadline. The system shall allow only the important participants to state preferences about the meeting location and allow the active participants to request special equipments on the meeting location. Decision and rationale Option 2 is chosen as the system shall allow meetings to be re-planned based on user constraint changes of important and active participants only in terms of location and equipment providing an ordered execution and monitoring of the system. Option1 could increase the rounds of negotiations to schedule a meeting. Date March 25, 2010
Traceability (Contd.) Forward Traceability (Domain requirement to Work Product) FR_014 An initiator should select the ‘room/location’ from the list of available locations. S4 The system should indicate the availability or unavailability of the room, in case of unavailability initiator has to choose other meeting room. FR_015 The initiator should select the ‘equipments’ needed for the meeting from the S4 equipments list; also active participants should have the option of selecting the equipments when the confirm their attendance to meeting FR_016 The system should send the reminder one day before the final meeting date FR_017 The initiator shall have a privilege to make any participant to active, important or S4 regular participant. If the meeting is cancelled by meeting scheduler then it should send the other S7 acceptable schedules to initiator depending on preference set entered. FR_018 S4 FR_019 If the acceptable schedules cannot be found to reschedule the meeting an email S7 shall be sent to initiator to reschedule the meeting with new date range. FR_020 As soon as the all important participants reject the meeting invitation the system S5 shall send an email to initiator regarding rescheduling a meeting. FR_021 The participants should be able to change their response at any time before the S5,S6 deadline FR_022 As soon as meeting is confirmed, the confirmation should be sent to participants S5 via email Date March 25, 2010
Contd. Contd.. [NFR_003]- “Re-planning of a meeting should be done as dynamically and with as much flexibility as possible;” Issue– Incomplete and ambiguous. The words “dynamically” and “flexibility” cannot be quantified or measured as no clear definition is provided for them. It does not indicate who can/or has the authority to re-plan the meeting. Option 1 –The system shall allow the meeting initiator to re-plan the meeting. The word “dynamically” indicates that the system shall find a suitable meeting time and date based on the information available including preferred and exclusion sets, locations and resource requests. The word “flexibility” refers to provision available to the important and active participants to change their feedback whenever necessary but before the meeting deadline. Option 2 – The system shall re-plan the meeting in-case of a conflict. The word “dynamically” indicates that the system shall find a suitable meeting time and date based on the information available including preferred and exclusion sets, locations and resource requests. The word “flexibility” refers to allowing the important and active participants to change the date range and providing their exclusion and preferred sets from the new range before the meeting deadline. Decision and rationale – Option 1 is more flexible as it offers control for the meeting initiator to decide on the date and time providing a simple and feasible solution. Date March 2, 2010
Contd. Contd.. [NFR_003]- “Re-planning of a meeting should be done as dynamically and with as much flexibility as possible;” Issue– Incomplete and ambiguous. The words “dynamically” and “flexibility” cannot be quantified or measured as no clear definition is provided for them. It does not indicate who can/or has the authority to re-plan the meeting. Option 1 –The system shall allow the meeting initiator to re-plan the meeting. The word “dynamically” indicates that the system shall find a suitable meeting time and date based on the information available including preferred and exclusion sets, locations and resource requests. The word “flexibility” refers to provision available to the important and active participants to change their feedback whenever necessary but before the meeting deadline. Option 2 – The system shall re-plan the meeting in-case of a conflict. The word “dynamically” indicates that the system shall find a suitable meeting time and date based on the information available including preferred and exclusion sets, locations and resource requests. The word “flexibility” refers to allowing the important and active participants to change the date range and providing their exclusion and preferred sets from the new range before the meeting deadline. Decision and rationale – Option 1 is more flexible as it offers control for the meeting initiator to decide on the date and time providing a simple and feasible solution. Date March 25, 2010
Minute Taker’s Responsibilities Before Meeting: • Collects agenda items from Facilitator • Prepares TIPS Meeting Minutes agenda form, including content from Data Analyst, as appropriate Minute Taker • Is prepared to project TIPS Meeting Minute form via LCD during meeting After Meeting: • Cleans up TIPS Meeting Minutes from meeting • Disseminates Meeting Minutes to team within 36 hours During Meeting: • Records decisions/no tes on TIPS Meeting Minutes form • Asks for clarification of tasks/decisi ons, as necessary • Is active participant in meeting
Implementing A Skip List struct node; The typedef node *nodePtr; The skip skip list list nodes nodes have have typedef nodePtr* nextArray; “data” “data” and and “next” “next” struct node components, components, just just like like regular regular { elementType item; // Node’s data linked int nbrOfNexts; // Number of next pointers linked list list nodes, nodes, but but skip skip list list nextArray next; // Dynamic array of next pointers nodes nodes have have a a dynamic dynamic array array }; of of next next pointers, pointers, rather rather than than // Member Function: insert // just pointer. just a a single single next pointer. // This next function creates a new node containing the parameterized value as its // CS 240 // item. It uses the randomized algorithm to decide how many next pointers the // // node will have and then links the new node into its proper place within the // // list. A boolean is returned based on whether the node creation was successful. // bool SkipList::insert(elementType value) { nodePtr currPtr; nodePtr insertPtr = getNode(value); if (insertPtr == NULL) return false; // How many next pointers? Between 1 and MAX_NEXTS, but logarithmically weighted // so 1 occurs half the time, 2 occurs a quarter of the time, and so on. insertPtr->nbrOfNexts = MAX_NEXTS + 1 (int)ceil(log10(generateRandomNumber(2, (int)pow(2,MAX_NEXTS)))/log10(2)); insertPtr->next = new nodePtr[insertPtr->nbrOfNexts]; currPtr = head; for (int i = insertPtr->nbrOfNexts - 1; i >= 0; i--) { while ((currPtr->next[i] != NULL) && (currPtr->next[i]->item <= value)) currPtr = currPtr->next[i]; insertPtr->next[i] = currPtr->next[i]; currPtr->next[i] = insertPtr; } return true; } 18
Traceability (Contd.) Forward Traceability (Domain requirement to Work Product) FR_006 FR_007 The system shall support conflict resolution according S7 to given 4 resolution policies; The system shall manage all the interactions among S7 participants required during the organization of the meeting FR_008 FR_009 The system shall support the negotiation and conflict S7 resolution processes; The system shall keep participants informed about S5 schedules and their changes FR_010 The meeting scheduler system must in general handle S7 several meeting requests in parallel. FR_011 The meeting scheduler system should cancel or reschedule the meeting S7 with lower priority to resolve the conflict with a meeting with higher priority level when they overlap in time or space. If two equally important meeting overlaps then we choose first come first served. FR_012 The user who can login into the system/ or a new user who is successfully S2 able to register can initiate a meeting FR_013 The meeting scheduler system shall allow the initiator to set ‘priority level’ S4 of the meeting in order to avoid conflict in scheduling two or more meetings. Date March 25, 2010
Lexical Analyzer Implementation: SHOW front.c (pp. 176-181) - Following is the output of the lexical analyzer of front.c when used on (sum + 47) / total Next Next Next Next Next Next Next Next token token token token token token token token is: is: is: is: is: is: is: is: 25 11 21 10 26 24 11 -1 Next Next Next Next Next Next Next Next lexeme lexeme lexeme lexeme lexeme lexeme lexeme lexeme is is is is is is is is ( sum + 47 ) / total EOF 1-15
Recursive-Descent Parsing (cont.) - Trace of the lexical and syntax analyzers on (sum + 47) / total Next token is: Enter Enter Enter Next token is: Enter Enter Enter Next token is: Exit Exit Next token is: Enter Enter Next token is: Exit Exit Exit Next token is: Exit 25 Next lexeme is ( Next token is: 11 Next lexeme is total Enter Next token is: -1 Next lexeme is EOF Exit 11 Next lexeme is sum Exit Exit 21 Next lexeme is + 10 Next lexeme is 47 26 Next lexeme is ) 24 Next lexeme is / 1-31
Lexical Analyzer Implementation: SHOW front.c (pp. 172-177) - Following is the output of the lexical analyzer of front.c when used on (sum + 47) / total Next Next Next Next Next Next Next Next token token token token token token token token is: is: is: is: is: is: is: is: 25 11 21 10 26 24 11 -1 Next Next Next Next Next Next Next Next lexeme lexeme lexeme lexeme lexeme lexeme lexeme lexeme is is is is is is is is ( sum + 47 ) / total EOF 1-14
Recursive-Descent Parsing (continued) - Trace of the lexical and syntax analyzers on (sum Next token is: Enter Enter Enter Next token is: Enter Enter Enter Next token is: Exit Exit Next token is: Enter Enter Next token is: Exit Exit Exit Next token is: Exit + 47) / total 25 Next lexeme is ( Next token is: 11 Next lexeme is total Enter Next token is: -1 Next lexeme is EOF Exit 11 Next lexeme is sum Exit Exit 21 Next lexeme is + 10 Next lexeme is 47 26 Next lexeme is ) 24 Next lexeme is / 1-28
Existing Strategies & Performance Our core business is our trading and investing customer franchise. Building on the strengths of this franchise, our growth strategy is focused on four areas: retail brokerage, corporate services and market making, wealth management, and banking. • Our retail brokerage business is our foundation. We believe a focus on these key factors will position us for future growth in this business: growing our sales force with a focus on long-term investing, optimizing our marketing spend, continuing to develop innovative products and services and minimizing account attrition. • Our corporate services and market making businesses enhance our strategy by allowing us to realize additional economic benefit from our retail brokerage business. Our corporate services business is a leading provider of software and services for managing equity compensation plans and is an important source of new retail brokerage accounts. Our market making business allows us to increase the economic benefit on the order flow from the retail brokerage business as well as generate additional revenues through external order flow. • We also plan to expand our wealth management offerings. Our vision is to provide wealth management services that are enabled by innovative technology and supported by guidance from professionals when needed. • Our retail brokerage business generates a significant amount of customer cash and we plan to continue to utilize our bank to optimize the value of these customer deposits.
Adding Meeting Times to a Section 8. 9. 10. 11. 12. Click the Next Block icon on the toolbar to move the cursor to the first information block of the form. Under the Options Menu, select Scheduled Meeting Times. Select the drop-down arrow for the Meeting Time. Double-click on the meeting time you want to use. This will bring the meeting time back into the form. (Note: If you extend the meeting time, leave the Start Time as it is and extend the End Time. The Start Time has to follow the Scheduling Guidelines.) Click the Save icon on the toolbar. When you are finished, click the Exit icon on the toolbar.
Binomial-Heap-Union: Merging Heaps Binomial-Heap-Union(H1, H2) 1. 2. H Make-Binomial-Heap() head[H] Binomial-Heap-Merge(H1, H2) 3. free the objects H1 and H2 but not the lists they point to 4. 5. 6. 7. 8. 9. 10. if head[H] = NIL then return H prev-x NIL x head[H] next-x sibling[x] while next-x ≠ NIL do if (degree[x] ≠ degree[next-x]) or (sibling[next-x] ≠ NIL and degree[sibling[next-x]] = degree[x]) then prev-x x x next-x else if key[x] <= key[next-x] then sibling[x] sibling[next-x] Binomial-Link(next-x, x) else if prev-x = NIL then head[H] next-x else sibling[prev-x] next-x Binomial-Link(x, next-x) x next-x next-x sibling[x] return H 11. 12. 13. 14. 15. 16. 17. 18. 19. 20. 21. 22. Stage 1 Stage 2 Stage 3 Case 1 & 2 Case 3 Stage 4 Case 4
FALL/SPRING HOURS OF OPERATION Brandon Academic Success Center Monday – Thursday: 9:00 AM – 7:00 PM * hours for reading lab and other subjects vary Dale Mabry Learning Commons Monday – Thursday: 8:00 AM – 8:00 PM Friday – Saturday: 8:00 AM – 2 PM Plant City Academic Success Center Monday – Thursday: 9:00 AM – 7:00 PM Friday – Saturday: 9:00 AM – 1:00 PM South Shore Student Learning Center Monday – Thursday: 8 AM – 8 PM Friday 8 AM – 4:30 PM Ybor City Academic Monday – Thursday: 9 AM – 7:00 PM Success Center Friday 9:00 AM – 2:00 PM Hours may vary. For the latest schedules, please visit our website at hccfl.edu/asc.