Senin, 24 Oktober 2011
Where Process Meets Method
08.07 |
Diposting oleh
Unknown
When process and method are discussed, they tend to be used interchangeably. However, while they are two sides to the same coin, they are different. Process (lat. processus–movement) is a naturally occurring or designed sequence of operations or events over time which produce desired outcomes. Process contains a series of actions, events, mechanisms, or steps, which contain methods. Method is a way of doing something, especially a systematic way through an orderly arrangement of specific techniques. Each method has a process.
From a pragmatic standpoint, design methods is concerned with the “how” and defining “when” things happen, and in what desired order. Design Methods is challenging to implement since there are not enough agreed-upon tools, techniques and language for consistent knowledge transfer. While there are many conceptual models and frameworks, there needs to be more granularity of tools and techniques.There are also many variables that affect outcomes since logic and intuition interplay with one another. Two people can therefore use the same method and arrive at different outcomes.
Label:
Where Process Meets Method
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