Monday, May 2, 2011

Web Evaluation Process

Web Evaluation Process:
Formative Evaluation & Summative Evaluation
 
*Formative Evaluation: A method of judging the worth of a program/product while the program activities/products are forming or happening. Formative evaluation focuses on the process (Bhola, 1990) .
*Summative Evaluation: A method of judging the worth of a program/product at the end of the program activities/products. The focus is on the outcome (Bhola 1990).
Usability Testing for web:
Usability is a quality attribute that assesses how easy user interfaces are to use. The word "usability" also refers to methods for improving ease-of-use during the design process .
 
            *Why usability testing is important?
                 -Usability is a necessary condition for survival.
                 -If a website is difficult to use, people leave.
                 -If the homepage fails to clearly state what a company offers and what users can do on the site,  people leave.
                 -If users get lost on a website, they leave.
                 -If a website's information is hard to read or doesn't answer users' key questions, they leave.



Web Evaluation

  • -Classic methods of evaluation:
               *the use of experts

               *let people test

               *use the results of others and

               *have a look of the use in real life.

  • -Experts can be the teacher himself or an external person.
          What do experts check?

                  *the content of a software.

                  *have a look at the quality of finding fast an information.

                   *make an assessment (just explain his impression).


                   *draw a comparison between different versions.


  • -Tests by persons is often used in formative evaluation to test software before selling it (observation).
  • -Look and listen to a person using software directly, via a mirror, a camera or a microphone.
  • -Analyze their behavior and their talking.
  • -Thinking aloud - means that the user talks about his way of using the software and the feelings and thoughts he has.
  • -Find out what the user has learned.
  • -Tests by persons is often used in formative evaluation to test software before selling it (observation). -Look and listen to a person using software directly, via a mirror, a camera or a microphone.
  • -Analyze their behavior and their talking.
  • -Thinking aloud - means that the user talks about his way of using the software and the feelings and thoughts he has.
  • -Find out what the user has learned

Tuesday, April 5, 2011

Interaction Design

The basic elements in Interaction Design:
  1. Organization
  2. Navigation
  3. Interactivity
*How the information will be organized on the pages ?
  1. Category – organization through similarity and relatedness (categories, tags, taxonomies). Organize your content by categories when there are clusters of similarity in you information or when people will naturally seek that information based on perceived similarities.
  2. Time – organization in a chronological sequence (step-by-step instructions, blog posts, news). Organize content by time when presenting or comparing events over a specific duration of time or when time based sequence is important to the information.
  3. Location – organization through geographical or spatial reference (maps, travel guides). Organize content by location when orientation or wayfinding are important or when your information relates to a geographical place
  4. Alphabet – organization in an alphabetical sequence (dictionary, glossary, index). Organize content by alphabet when the information is referential, when nonlinear access is required, or when no other means of organization is acceptable.
  5. Continuum – organization by magnitude (baseball statistics, search results, ratings). Organize content by continuum when comparing things across a common measure; highest to lowest, best to worst, first to last.
*How people will find their way around your web site ?

Monday, April 4, 2011

Teaching and Learning Methods and Strategies

  • Collaborative Learning
  • Cooperative Learning
  • Discovery-Based Learning 
  • Engaged Learningr
  • Problem-Based Learning
  • Whole Language Approach
  • Examples of Learner-Centered Programs
  • Develop better study strategies and habits

Learning Theories

  • Behaviorism
  • Cognitivism
  • Constructivism
  • Design-Based
  • Humanism 
  • Problem-Based Learning (PBL) 
  • Discovery Learning (Bruner) 
  • Social Development Theory (Vygtosky)

Information Design

Information Design is geared toward information solutions in general—as opposed to Web solutions in particular. That broader understanding of the dynamic inter-relationship of the myriad contexts, strategies and tactics pertaining to the creation of successful information is invaluable. It is also particularly relevant in providing excellent direction for Web development. Information Design is critical to better Web development in the following four ways:

1. Information Design clarifies goals and objectives
Clients often know what they want but rarely understand what they need. Requests for functionality ranging from live chat to online stores to sophisticated content management functionality may not help the client achieve their business goals. Web design professionals are obligated to focus on the business goals of their clients and make recommendations that are in the client's best interests.
Information Design grounds that consultation and planning process. By approaching the Web project as an information solution, among the galaxy of information solutions and organizational realities that face clients, developers are equipped to design a Web site or application that best contributes to their business success.

2. Information Design provides a broader context
Even for modest static sites, good Web design is relatively involved and complicated. In any effort to successfully navigate the development process, it is simple to lose sight of the relationship between the project itself and the broader context, including:
  • The original business goals that led to the site being created or modified
  • The client’s unique position now, the position they want to be in later, the other tactics that they have or are planning to initiate, and how all of those factors juxtapose with the Web tactic itself
  • Those same factors in the client’s competition
  • The unique position of the client’s current and potential customers, as well as employees, communities and key stakeholders, and how those groups juxtapose with the Web tactic itself
These are largely strategic concerns that need to be factored in at the beginning of a Web development project, then monitored and considered throughout the project lifecycle. However, those considerations are not the sole domain of the project leaders or strategists. Information Design requires that all team members have an acute awareness of the broader contextual concerns that resulted in this tactic being selected in the first place, and that awareness must be balanced and addressed in the final deliverable. Awareness and acknowledgement of these considerations—even by the most tactical and production-oriented of the team members—provides immeasurable added value and the highest likelihood that the final deliverable will be as effective as possible.

3. Information Design balances the various specialties that participate in Web development
Inevitably, most Web designers or Web development companies have their own particular specialties. Whether in the structure and content, the interface design, the application development—or any sub-specialty therein—it is apparent from the final product that there is a bias toward the comfort level or organizational strengths of the producers.
Information Design as a discipline insists that the focus remain on making the information—with information in this case being the final Web site—as effective as possible. Applying this to the design itself can manifest in a few different ways and is best if all occur together:
  • By assigning someone not on the core production team as the Information Designer or Director (or really any title you prefer) to ensure the final deliverable is appropriately balanced
  • By providing all team members with a short list of essential elements that would contribute to successful Information Design for this unique project, in order to guide their thinking and production
  • By insisting on collaboration and cross-pollination of team members from different disciplines, to give them a better sense of the why, how and what each other is doing
By proactively balancing the different components and specialties, you will best be able to achieve the goals and objectives of the project, with the final product thus proving as effective as possible.

4. Information Design focuses on the dynamic nature of strong Web development
The most effective Web development is that which stakes out the strongest position between a myriad of considerations, including:
  • The articulated goals of the project
  • The client’s internal situation
  • The client’s market situation
  • The target audiences
  • The project budget
  • The available technologies
  • The composition and capability of the development team
During the development process, it is easy to lose sight of one or many of these key components, and the project suffers for being too close to some of the considerations and too far from others.
As such, a strong process naturally incorporates a healthy and regular mechanism for balancing the different considerations. Information Design requires that the core considerations that guide the project be far forward throughout the project lifecycle, ideally incorporating research and actual testing where appropriate. This will ensure that the final deliverable achieves the proper balance to maximize effectiveness and business success.

The web Development Team

The strategic importance and project budget for your web efforts will largely determine the size and skill depth of your web site development team. Even for a smaller project, however, you’ll need to cover the core team disciplines. In most small to medium projects one person may handle multiple tasks or someone with specialized expertise (graphic design, for instance) is hired for specific assignments. Many managers who are assigned the responsibility of creating a web site don’t have the luxury of picking specialist team members. Inventory the skills and aptitudes in the team you assemble, and consider careful outsourcing to supply any expertise your team lacks.
The core skill sets needed in a web site development team are:
  • Strategy and planning
  • Project management
  • Information architecture and user interface design
  • Graphic design for the web
  • Web technology
  • Site production
In larger web projects each role may be filled by a separate person, although in more specialized skill areas those contributors are not likely to be full-time team members for the duration of the project.

Web team roles and responsibilities

Core web team roles and extended secondary team roles in larger web projects are:
  • Project stakeholder or sponsor
  • Web project manager
    • Account executive
    • Quality assurance tester
  • Usability lead
  • Information architect
  • Art director
    • Web graphic designer
    • Interactive designer (Flash, JavaScript, Ajax)
    • Media specialist (photography, illustration, audiovisual, Adobe Flash)
  • Web technology lead
  • Site production lead
    • html page coder
  • Site editor
    • Site copywriter
    • Content domain expert (content coordination, research)

Web Project Management

what Is Project Management?
The Project Management Institute's definition of PM is: "... the application of knowledge, skills, tools, and techniques to project activities to meet project requirements."(PMBOK Guide, 3rd Edition, Project Management Institute Inc., Pennsylvania, 2004.)
A less abstract version of this definition is that PM is what you need to make a project happen on time, within budget, with required scope, and quality.
My personal definition is that PM is the simplest way to look like a superhero without requiring the involvement of any radioactive spiders or questionable parentage.

There are also lots of things that PM isn't, the most notable being a replacement for personal productivity. Whether you use a simple todo.txt file, a hipster PDA, or a full GTD (that stands for Getting Things Done) system to keep yourself organized, you're still going to need to use PM tactics. PM is all about making the project happen -- how you complete the work that you need to do for the project is up to you. Mixing up personal productivity and PM is one of the main reasons for those groaning reactions I mentioned earlier: if you make your PM tools double up as your to-do list, then you're obviously going to end up with a lot more detail than anyone else in the project (including the client!) needs to see. It's a very common mistake seen with smaller projects, where realistically the project manager is also doing a lot of the project work, if not all. It can be a lot easier to keep the distinction in large-scale projects with dedicated project managers, but even there you see evidence of the mistake, with project plans starting to look more like personal brainstorms rather than a path to a future that involves getting home in time to see your kids.
Now that we've talked a little about what PM is and isn't, let's move on to looking at the project lifecycle.
The Generic Project Lifecycle
The generic project lifecycle is fairly simple -- first you begin the project (Initiation), then you go on to actually do the project (Planning, Executing, and Controlling, which form a loop, since expecting things to go right first time is rather unrealistic) and finally you finish by making everyone happy and, with any luck, receiving payment (Closure). This process is illustrated in Figure 1.
The project lifecycle


Since typically most time and effort is spent in the Executing (completing tasks) and Controlling (keeping everything on track) phases, many people think these are the most important. It is true that these should be where you spend most of your time -- after all, nothing would be completed if you didn't! -- but they are not the most important.
The most important project phases are Initiation, Planning, and Closure.

Basic Concept of Website

What is the web?

In a nutshell, the web is a whole bunch of interconnected computers talking to one another. The computers (on the web) are typically connected by phone lines, digital satellite signals, cables, and other types of data-transfer mechanisms. A ‘data-transfer mechanism’ is a nerd’s way of saying: a way to move information from point A to point B to point C and so on.
The computers that make up the web can be connected all the time (24/7), or they can be connected only periodically. The computers that are connected all the time are typically called a ‘server’. Servers are computers just like the one you’re using now to read this article, with one major difference, they have a special software installed called ‘server’ software.

What is the function of server software / programs?

 

Server software is created to ‘serve’ web pages and web sites. Basically, the server computer has a bunch of web sites loaded on it and it just waits for people (via web browsers) to request or ask for a particular page. When the browser requests a page the server sends it out.

How does the web surfer find a web site? 

 

The short answer is: by typing in the URL, or in other words, the web site address. So for example, if you wanted to find the web site www.killersites.com, you would type in the address into your web browser’s address bar or maybe use your ‘favorites’ or ‘bookmarks’ link to Killersites.
There are other ways to find web sites (like search engines,) but behind the scenes web sites are all being found by going to the web site’s official address. That brings us our last nerd detail: how does a website get an official address so that the rest of the web can find it?

Tuesday, January 11, 2011

~ADDIE MODEL~

"ADDIE" is the acronym for the Analysis, Design, Development, Implementation and Evaluation Instructional Systems Design Process, which is currently accepted as an industry standard for instructional design and performance technology. ADDIE ensures a consistent and systematic process for design and development of highly efficient and effective systems without sacrificing creativity.
The ADDIE model consists of the following phases:
  • Analysis: The process for defining desired outcomes.
  • Design: The process of determining how desired outcomes are to be accomplished — based on supporting system(s) needed, required resources, timetable, and budget.
  • Development: The process of establishing requisite system(s) and acquiring needed resources to attain desired outcomes.
  • Implementation: The process of implementing design and development plans within the real-world environment.
  • Evaluation: The process of measuring the effectiveness and efficiency of the implemented system and using collected data as opportunities for improvement in closing gaps between actual and desired outcomes.

The ADDIE model of instructional design is a basic model that can be applied to any kind of learning solution.
We implement the ADDIE model in our assignment because of its emphasis on analysis. Before engineering a learning solution, we analyze the problem thoroughly to ensure that the solution impacts performance in a positive way.

Monday, January 10, 2011

Rise of the mobile internet

*Rapid improvements in connectivity & screens
*Mobile to be dominant platform for connecting to net worldwide
*Japan: mostly surf web through phones
*Voice calls powered by internet & SMS/Texts -> IM
*Cell phones electronic wallets & banks = main method of payment
*Citizens vote for first time in elections via mobile phones?