|
When evaluating tools, start with standard tool selection criteria:
- vendor stability
- merger and acquisition considerations.
- functionality and features
- suites versus stand-alone tools
- best-of-breed considerations
- customer service
- implementation assistance
- training
- availability of consultants
- pricing
- maintenance costs and other costs
- ROI
You’ll need to consider the information you collect in the context of your organization’s culture and environment:
- accountability and controls
- processes and workflow
- policies and standards that apply to these tools
- architectural considerations
- timeline considerations
You’ll also want to determine whether you need to collect requirements or approvals from business stakeholders. This may be necessary if the tools
- are part of processes or procedures subject to formal change control
- fall subject to approval by your IT Portfolio Management group
- fall subject to compliance or legal requirements
- are considered part of key control sets
- are included in approved business processes or workflows that are subject to approval by your internal or external auditors
- they could influence your ability to fulfill Service Level Agreements (SLAs) or other contractual requirements.
|
|
In many organizations, the Project Management Office (PMO) and/or the Application Portfolio Management group expect to be involved in the selection of software applications. They may very well have their own set of requirements. Following are some keywords often found in PMO-based requirements.
- Assumptions
- Availability Management
- Back-out Plan
- Balanced Scorecard
- Baseline
- Benchmarking
- Business Case
- Business Continuity Management (BCM)
- Business Driver
- Business Impact Analysis
- Business Process Management
- Business Process Modeling
- Business Rule
- Change Control
- Change Management
- Configuration Baseline
- Configuration Management
- Constraints
- Contingency Plan
- Cost Benefit Analysis
- Critical Success Factor (CSF)
- Deliverable
- Deming Cycle
- Deployment
- Development Environment
- Entry Criteria
- Exit Criteria
- Functional Requirements
- IT Help Desk
- IT Infrastructure
- Iterative Process
- Just in Time Development or Deployment
- Key Performance Indicator (KPI)
- Lessons Learned
- Lifecycle
- Metric
- Milestone
- Non-Functional Requirements
- Outsourcing
- Pareto Principle
- Performance Testing
- Plan-Do-Check-Act
- Planned Downtime
- Policies and Standard
- Portfolio Management
- Processes and Procedures
- Regression Testing
- Release Management
- Request for Change (RFC)
- Requirements Management
- Requirements Traceability
- Retirement Schedule
- Return on Investment (ROI)
- RFI, RFQ, RFP
- Risk Analysis
- Risk Assessment
- Risk Identification
- Risk Mitigation
- Rollout
- ROM estimate
- Scalability
- Scope
- Scope Change
- SDLC
- Service Catalogue
- Service Delivery
- Service Desk Ticket
- Service Level Agreement (SLA)
- SME involvement
- Software as a Service (SaaS)
- Software Asset Management
- Software Development Life Cycle (SDLC)
- Specifications
- Testing
- Total Cost of Ownership (TCO)
- Traceability
- Unified Modeling Language (UML)
- Unit Testing
- Use Cases
- User Acceptance Testing (UAT)
- Versioning
- Work Breakdown Structure
- Workflows
|
|
- Access Management
- Aggregation
- Alert
- Authorization
- Batch Processing
- Corporate Information Factory (CIF)
- Customer Data Integration (CDI)
- Data Analysis
- Data Integration
- Data Monitoring
- Data Privacy
- Data Synchronization
- Data Visualization
- Decision Support System (DSS)
- Drill Across
- Drill Anywhere
- Drill Down
- Drill Up
- eSecurity
- Executive Information System (EIS)
- Faceted Taxonomy
- Granularity
- Heterogeneous Database Integration
- Hierarchies
- Historical Databases
- Ontology
- Operational Data Store
- Predictive Analytics
- Privacy
- Private Data
- Records Management
- Reporting
- Repository
- Roll Up
- Segmentation
- Segregation of duties
- Sensitive Data
- Service-Oriented Architecture (SOA)
- Slice and Dice
- Split/Merge
- Subject Oriented Database
- Summarization Table
- Taxonomy
Standardization Considerations
Often tools must comply with internal or external regulations, policies, or rules. Following are some keywords often found in regulatory or standardization requirements.
- ANSI
- Capability Maturity Model (CMM
- COBIT
- COSO
- IEEE
- ISO/IEC 20000, BS 7799
- ITIL
- (NIST
- Six Sigma Standards
- UML Processes
- World Wide Web Consortium (W3C) Standards
- XBRL (eXtensible Business Reporting Language)
|
