婦聯三代表蓄勢待發

640

婦聯於一四年首辦"青年女性國際事務培訓計劃",讓澳門女性更加掌握國際動脈,提升社交能力和個人競爭力。計劃舉辦至今兩年,為讓結業學員提供真正實踐機會,婦總今年特意從培訓計劃中選出兩位優秀學員,在婦聯青協會員大會副主席吳紫薇的組織下,一同代表婦聯以非政府組織(NGO)身份,出席聯合國"婦地會"。

做好溝通橋樑角色

是次為婦聯首次派出隊伍參與聯合國婦地會和非政府組織的周邊會議,屬全新嘗試,也是新挑戰,更是該會對外交流發展的一個新突破,因此三人已積極備戰,做好資料搜集。

7 things you should know about... PLE

7 things you should know about...
Personal Learning Environments

Scenario


For the fall semester, David signed up for a digital photography course, and during the first class, he was assigned
to a critique group with four other students. The professor explained that students would be creating personal learning environments—exploring free applications and networking sites, sharing what they learn with each other, and submitting work for feedback from those in the critique group. Each week students were to photograph something in a public venue and upload the photos to a website where the group could view them, critique and discuss the images, and blog about what they learned. 

David enjoyed looking through the blogs of his fellow students and subscribed to the RSS feeds of his favorites so he would know when each was updated. David found the feedback from his in-class critique group so useful in improving his photography that he created an open group in Flickr for his growing collection, inviting the wider photo community to comment on his work. During a zoo trip, he photographed a llama that looked oddly taken aback. Everyone smiled at the comic expression, but the image was a chance shot with hasty framing, so his in-class group suggested cropping
and minor clean-up work. Then he asked his group on Flickr to suggest titles, from which he chose his favorite, “Whoa, Dude.” He later sold the photograph to a newspaper editor who had seen it on Flickr. It ran with an article about an upcoming music festival at the zoo.


The final course assignment was a joint photojournalism exercise for the class. Students were to cover the local Trout Day Parade along the riverfront, where floats and costumes took an aquatic theme and the river offered a consistent backdrop. Images would accompany a brief article or interview to be posted on student blog sites. One student compiled the articles and ran the text through Wordle, posting the resulting word collage.


Two other students used the collage as a background and pasted all the class photos on top. When the completed group project was published online, several images received outside recognition. Students gathered
those comments for Wordle, too, using the result as a sidebar for a page of final reflections on the course.


The following semester, when David submitted some of his work for a fine arts student fellowship, he felt confident
about his submission, having integrated input from his group at Flickr, which now included several of his former classmates.

 

Source PDF

2015 Instructional Design Trends Compass: Calling IDs to Action

Attention, fellow instructional designers! Our industry is all about learning and change, but our target audiences are not the only ones who should be learning. This in-depth article will help you stay at the forefront of 2015 instructional design trends. And it’s not just a list of the trends, but a “compass” with calls to action to help you implement them.

How to Put Instructional Design Trends to Action

Like most years, 2014 ended with articles about the latest trends in instructional design, e-learning, and training and development. Often these articles describe technology trends by highlighting the “cool” factor to which we should be paying attention. These pieces are important—we need to remain in touch with trends and issues in our field. But perhaps what’s even more important is that we determine how to implement these trends (or decide whether we should). Cool technology is one thing, but what does it mean for instructional design practices?

With support from my colleagues Clare Dygert (senior instructional designer at SweetRush) and Catherine Davis (SweetRush’s instructional design practice lead), I present to you the 2015 Instructional Design Trends Compass. This article will help you identify some of the hot topics and trends and help you navigate the landscape by pointing you in the direction of resources to assist you with putting them into practice. As we like to say in instructional design: it’s great that you know something, but what can you do with this knowledge?

 

Source

Next Gen Web Architecture for the Cloud Era

Briefly Introduce Web App Architecture History and the traditional Web Templating Engines as well as the frameworks.

The trend of today Web App Architecture and template are shifing to SOFEA (Service Oriented Front End Architecture), which is based on the traditional SOA and benifit from Cloud Computing technology.

 

SOFEA Principles

1. Application Download, Data Interchange, and Presentation Flow must be decoupled ‒ No part of the client should be evoked, generated or templated from the server-side.

2. Presentation Flow is a client-side concern only

3. All communication with the application server should be using services (REST, SOAP, etc)

4. The MVC design pattern belongs in the client, not the server

 

SOFEA Lifecycle, Benefits and Implementation Archetype are also including in the powerpoint presentation.

 

Download

3 Types Of Web Application Architecture

Such terms as ''web app'', ''front-end architecture'', ''Web 2.0'', and ''HTML5 apps'' have recently become trendy. Unfortunately these terms are often used in a misleading context which doesn't consider the full specificity of implementation and usage of web app architectures. Today we'll try to find out more about the types of web application architecture in the light of the latest web trends and key issues that matter to software owners.

We'll outline 3 main types of web architecture and discuss their advantages and drawbacks for three points of view: software owner, software contractor (developer) and end user. There can be other types but they basically come down to these three as their subtypes.

First we'll define a web application: it's a client-server application - there is a browser (the client) and a web server. The logic of a web application is distributed among the server and the client, there's a channel for information exchange, and the data is stored mainly on the server. Further details depend on the architecture: different ones distribute the logic in different ways. It can be placed on the server as well as on the client side.

Source