| 1. |
Business Process Management Notations within Business Process Management (4 Pages)
by Hans Mercx
Nov 7, 2006
Abstract : Business process management notation (BPMN) is an initiative to increase standardization within process modeling. What are the principles of BPMN, and what is the value of BPMN to vendors and organizations using business process modeling?
Type: Article
|
| 2. |
Architecture-Centered Information Systems In The Manufacturing Domain - Part III - Steps in the Architecture Process (14 Pages)
by Glen B. Alleman
Sep 11, 2002
Abstract : Architecture bridges the semantic gap between the requirements and software. Application software systems must be architected in order to deal with the current and future needs of the business organization. Managing software projects using architectureﾖcentered methodologies must be an intentional step in the process of deploying information systems ﾖ not an accidental byﾖproduct of the software acquisition and integration process.
Type: Article
|
| 3. |
Project Portfolio Management for New Product Development: Tracking the Project Cycle from Idea to Launch (4 Pages)
by Neil Stolovitsky
Jan 6, 2006
Abstract : Resource allocation and phase-based processes are key features to consider when selecting a project portfolio management solution for new product development (NPD) projects. More importantly, NPD projects demand a best practices framework, like Stage-Gate®, for their success.
Type: Article
|
| 4. |
Business Process Management: How to Orchestrate Your Business (6 Pages)
by Hans Mercx
Jul 9, 2005
Abstract : Business process management (BPM), having evolved over the past fifteen years, has finally reached a level of maturity where vendors are now abolishing functional silos to allow the enterprise-wide flow of business processes. It replaces the old, manual system of coordinating activities in a company and improves functionality and effectiveness through modeling, documentation, certification, collaboration, automation, and compliancy to minimize costly errors.
Type: Article
|
| 5. |
Business Process ManagementHow to Orchestrate Your Business (10 Pages)
by Hans Mercx
Oct 27, 2004
Abstract : Business process management (BPM), having evolved over the past fifteen years, has finally reached a level of maturity where vendors are now abolishing functional silos to allow the enterprise-wide flow of business processes. It replaces the old, manual system of coordinating activities in a company and improves functionality and effectiveness through modeling, documentation, certification, collaboration, automation, and compliancy to minimize costly errors.
Type: Article
|
| 6. |
Business Process Analysis versus Business Process Management (4 Pages)
by Hans Mercx
Oct 9, 2006
Abstract : Business process analysis (BPA) vendors are trying to enter the business process management (BPM) market by marketing themselves as BPM solutions. This article discusses the differences between BPA and BPM vendors, and examines the benefits of each.
Type: Article
|
| 7. |
Business Process Analysis versus Business Process Management (4 Pages)
by Hans Mercx
Feb 24, 2006
Abstract : Business process analysis (BPA) vendors are trying to enter the business process management (BPM) market by marketing themselves as BPM solutions. This article discusses the differences between BPA and BPM vendors, and examines the benefits of each.
Type: Article
|
| 8. |
Requirement Traceability—A Tester's Approach (3 Pages)
by Neha Grover
Apr 30, 2007
Abstract : The value of a requirement traceability matrix is in its ability to track and monitor each requirement to be incorporated into the customer's product throughout the entire process of product development, and to detect defects at the earliest stage possible.
Type: Article
|
| 9. |
Architecture-Centered Information Systems In The Manufacturing Domain - Part I - Introduction to Software Architecture (15 Pages)
by Glen B. Alleman
Sep 4, 2002
Abstract : Architecture bridges the semantic gap between the requirements and software. Application software systems must be architected in order to deal with the current and future needs of the business organization. Managing software projects using architecture-centered methodologies must be an intentional step in the process of deploying information systems ― not an accidental by-product of the software acquisition and integration process.
Type: Article
|
购物车 
