Senin, 24 Oktober 2011
Design & Implementation Issues
06.44 | 
Diposting oleh
Unknown
The complexity of groupware development is still an issue. One reason for this is the socio-technical dimension of groupware. Groupware designers do not only have to address technical issues (as in traditional software development) but also consider the social group processes that should be supported with the groupware application. Some examples for issues in groupware development are:
- Persistence is needed in some sessions. Chat and voice communications are routinely non-persistent and evaporate at the end of the session. Virtual room and online file cabinets can persist for years. The designer of the collaborative space needs to consider the information duration needs and implement accordingly.
- Authentication has always been a problem with groupware. When connections are made point-to-point, of when log-in registration is enforced, it's clear who is engaged in the session. However, audio and unmoderated sessions carry the risk of unannounced 'lurkers' who observe but do not announce themselves or contribute.[16][17]
- Until recently, bandwidth issues at fixed location limited full use of the tools. These are exacerbated with mobile devices.
- Multiple input and output streams bring concurrency issues into the groupware applications.
- Motivational issues are important, especially in settings where no pre-defined group process was in place.
- Closely related to the motivation aspect is the question of reciprocity. Ellis and others [18] have shown that the distribution of efforts and benefits has to be carefully balanced in order to ensure that all required group members really participate.
One approach for addressing these issues is the use of design patterns for groupware design.[19] The patterns identify recurring groupware design issues and discuss design choices in a way that all stakeholders can participate in the groupware development process.
Label:
Langganan:
Posting Komentar (Atom)
Statistik
Translate
Blog Archive
-
▼
2011
(1064)
-
▼
Oktober
(834)
-
▼
Okt 24
(256)
- Etymology of the word
- Modeling
- Animation
- Rendering
- form•Z on the small and big screen
- Overview
- History
- Transporter
- Modeler
- Product family
- Drafting Assistant
- Animation tools
- Surfacing
- Cobalt (CAD program)
- There is no one way to practice design methods. Jo...
- Current State of Design Methods
- Significance of Design Management
- Proliferation of Information Technologies
- Significance of Proliferation of Information Techn...
- Significance of Emergence of Design Research and D...
- Professional Design Practice
- Significance of Role of Professional Design Practice
- Design Management
- Alternative View
- Background of Design Methods
- Where Process Meets Method
- Emergence of Design Research and Design Studies
- Design methods
- Globalization and governance controversy
- Internet governance
- Formation and growth of the network
- Governors
- Roles
- Elements
- Principle 4: Ensure separation of project governan...
- Additional and complementary principles of governa...
- Additional principles exist where projects are mul...
- Principle 1: Ensure a single point of accountabili...
- Principle 2: Service delivery ownership determines...
- Principle 3: Ensure separation of stakeholder mana...
- Project governance
- Three pillars of project governance
- Professional certification
- Frameworks
- Problems with IT governance
- Corporate governance of information technology
- Definitions
- Background
- Domination by large organizations
- Administration
- Membership
- Recommendations and Certifications
- History
- Areas of responsibility
- Website management team
- Governance models
- World Wide Web Consortium
- Webmaster
- Website governance
- Effective separation
- Flexible presentation
- Reusability
- Web template
- Template uses
- History
- Web syndication as a commercial model
- Web syndication and e-commerce
- Web syndication
- Motivation
- Representational state transfer (REST)
- Automated design methodologies
- Criticisms
- Big Web services
- Web API
- Remote procedure calls
- Service-oriented architecture
- Web service
- Web document
- Advanced
- Security Considerations
- Client Side + Server Side
- Basic
- Web development as an industry
- Client Side Coding
- Server Side Coding
- Best practices
- Changes and updates
- Web development
- Web design
- Advantages
- Disadvantages
- Web content management system
- Capabilities
- Online processing (called "frying" systems)
- Role of information management
- Four stages
- Five stages
- Governance rather than workflow
- Web content lifecycle
- Career
-
▼
Okt 24
(256)
-
▼
Oktober
(834)
0 komentar:
Posting Komentar