Research

Navigate by...

Refine Your Results

Refine by Lifecycle

Legend

Audio
Video
Membership Required

Requirements & Analysis

1 2 Next Last
Learn Trends and Develop Strategy
 
1 to 10 of 15
Note
 

Custom vs. COTS: Tailor Requirements Gathering for a Tighter Fit

Many IT teams approach requirements gathering for software purchasing the same way they approach custom development requirements. It is important, however, to note the differences between these scenarios from the perspective of requirements gathering. Understand the differences to make sure the right approach is taken to solve enterprise software problems.

Note
 

Don't Overcook or Undercook Requirements for Purchased Software

When gathering requirements for software procurement decisions, enterprises need enough information to narrow the field of candidates. Too much detail, however, can rule out potentially viable candidates. Narrow the field without developing requirements tunnel vision by focusing on core requirements.

Note
 

Requirements Gathering: What Every IT Manager Needs to Know

Requirements gathering is a critical part of custom software development and the procurement of commercial applications. Poor requirements gathering can lead to costly rework, expensive workarounds, and/or poor purchasing decisions. Learn the fundamentals of the requirements gathering process to build or purchase an application that fits business needs.

Note
 

SOX and ITIL Dominate Trends in IT Compliance

Compliance remains a key concern for many IT managers. Frameworks like ITIL and COBIT are very popular, but the NIST 800 guidelines and ISO 17799/27002 may be more beneficial. Regardless of the approach, IT leadership is sacrificed when violations occur.

Note
 

A Solution Specification Simplifies Software Selection

The process of selecting an enterprise software solution is complicated. Requirements are messy and RFP preparation is complicated and political. The effective use of a solution specification eases the process.

Brief
 

More Resources Targeted to the Business Analyst Role

Demand for Business Analysts has been steadily climbing. With formal certification of the role now available, there is increasing interest in providing resources to those in the role. Wyyzzk Inc. has been providing training and expertise in software engineering for over ten years. They now also maintain a Web site of articles for Business Analysts.

Brief
 

Requirements Models: The What, When, and Why

Gathering requirements is a first step in any project. Using those requirements to drive the design and development of an automated system often calls for the use of requirements models. Understand what defines these models and when to use them.

Brief
 

Use Cases: The Primer

Enterprise applications must meet the needs and requirements of their user population. Use Cases are a proven and effective technique for organizing and documenting the functional requirements of an automated system.

Brief
 

Time-boxed Projects: Manage Requirements Ruthlessly

IT leaders must manage requirements of time-boxed projects. Ruthlessly prioritize project requirements to achieve desirable results within the boundaries of development cost and time parameters.

Brief
 

The Pitfalls of IT Change Management

IT managers must not rush to get a tool to automate IT change management. Instead, they must make sure they have strong senior management support and a solid and practical process.

Make Technology Decisions
 
1 to 1 of 1
Brief
 

Oracle Positioned to Help Drive BI 3.0

The acquisition of Hyperion positions Oracle to lead the Business Intelligence (BI) 3.0 charge for large and medium implementations. This can render pure-play BI tool vendors obsolete for customers who run Oracle's business applications.

Improve IT Operations
 
1 to 5 of 5
Premium Resource
 

Application Management: Request Analysis

The framework for applications maintenance and change practices has been established. In this bundle, you will be setting up a process for gathering, assessing, and accepting/denying change requests from users within the organization.

Brief
 

Small Enterprises: Good Process Comes Before Requirements Tool

Small Enterprises should not spend money on requirements management tools as a first step in improving project success. Considerably reduce project cost, time overruns and outright failure rates by following a good requirements management process.

Note
 

Quality Assurance Checklist for Feasibility Studies

Creating a feasibility study is a daunting task for newcomers and for companies that lack experience in developing feasibility studies. Use this checklist as part of a quality assurance process to ensure the feasibility study document meets existing documentation quality standards.

Note
 

Feasibility Study Template

A feasibility study is an invaluable tool that helps companies assess the level of risk the company faces when selecting certain IT projects. Creating a feasibility study is a daunting task for newcomers, and angst-ridden for companies that lack documentation standards. Use this template to reduce documentation preparation woes, and create a standard for the company.

Brief
 

Flawed Requirements Trigger 70% of Project Failures

Up to 50% of project rework is attributable to problems with requirements. Of projects that fail, 70% fail due to poor requirements. Quickly identify requirements risk factors and implement an effective requirements management process to avoid becoming another project failure statistic.

1 2 Next Last