Abstract: To accurately assess the impact that requirements have on businesses, IAG surveyed over 100 companies. What they found was that less than one-third were properly equipped to define their software requirements, and that suboptimal requirements consumed around 41.5 percent of the IT development budget. Find out what it takes to ensure your organization doesn’t fall on the wrong side of this business requirements equation.

Abstract: The conventional unit of measurement for software size is the point. Unfortunately, the point-based measurement system fails to account for many of the complexities of software development. This paper proposes software size units (SSUs) as an alternative to points, defines their component elements, and explains how to use SSUs for more accurate software estimations and easier productivity assessments.

Abstract: Requirements management (RM) is about bringing products to market faster, improving team efficiency, and catching requirements defects earlier. But you need to dig deeper into the return on investment (ROI). What’s the tangible cost savings an RM solution can deliver to your company? What’s the difference if you just use spreadsheets to manage requirements? Get answers to these and other questions with this ROI analysis.

Abstract: According to an IAG survey, 70 percent of companies lack the fundamental competencies within business requirements discovery to consistently bring in projects on time and on budget. Why do so many fall short in properly diagnosing their requirements failures? Discover how placing a greater focus on the combined aspects of business requirements—people, process, and tools—can provide better project outcomes.

Abstract: The concept of getting business requirements right sounds straightforward. However, flawed requirements trigger 70 percent of project failures. The larger the number of stakeholder groups involved, and the more complex the processes, the more likely a project will fail. Success in large projects is not just about completeness, but also about getting complete requirements information early in the development process.

Abstract: A failed software implementation can cost companies millions in wasted time and money. To ensure your software selection project isn’t a sorry statistic, use the right metrics to gauge your success. Time, budget, and functionality aren’t enough—focus your efforts on requirements analysis and definition. Take measures to ensure your software meets your needs, and discover how to do accurate requirements analysis.

Abstract: The first step in choosing an effectiveness service provider (ESP) that best meets your company's needs is to develop a requirements definition. When used as a request for proposal, the requirements definition can be a powerful evaluation and negotiation tool.

Abstract: The specialized material resource planning module for cut-to-size/shape industries must be able to recognize when current demand cannot be satisfied by the in stock inventory due to dimensional issues, and include that unsatisfied demand in its reorder messages.

Abstract: As with any manufacturing operation, process manufacturing has special system requirements such as formulas, unit of measure conversions, and packaging recipes. However, within the realm of process manufacturing, specific industries have needs that are more critical than others. This article explores these critical needs for the food and beverage, chemical, and a hybrid industry (textiles), so that you can focus on these requirements when evaluating enterprise-wide software.

Abstract: As with any manufacturing operation, process manufacturing has special system requirements such as formulas, unit of measure conversions, and packaging recipes. However, within the realm of process manufacturing, specific industries have needs that are more critical than others. This article explores these critical needs for the food and beverage, chemical, and a hybrid industry -- textiles, so that you can focus on these requirements when evaluating enterprise-wide software.

Abstract: With opportunities in the large enterprise marketplace shrinking due to increased penetration, small and medium-size enterprises (SMEs) are starting to receive more attention and scrutiny. This article explores the special needs of the SMEs and asks, from a software standpoint, what companies can to do survive in this unique marketplace and what vendors can do to service them. Read on for the answers.

Abstract: A Process PLM system must accommodate rapid, global deployment of the system. This need drives specific requirements to minimize both the start-up and the long-term cost of ownership of the system. This article, third in a series details those requirements.

Abstract: How do you go about defining the requirements of large package systems, particularly those with the all-encompassing scope of ERP, EAM, and CRM software, and still satisfy the needs to the project team, the user community, and executive management? It’s a balancing act rivaling the circus performer trying to keep all of the plates spinning at once. While it is difficult to say one aspect of a project plan is more important than another, accurately and completely defining the needs to be fulfilled by the software is critical to the overall success of the implementation and the longevity of software. This article outlines a logical process for defining the requirements and keeping the plates spinning.

Abstract: Companies that are not already offering the capabilities of meeting the exacting, stringent requirements of federal agencies will likely not be able to tap the recent surge in the federal and defense markets. Conversely, those vendors and their users--government contractors--who can deliver comprehensive solutions that satisfy the requirements of federal agencies are in the driver's seat to capture that market segment.

Abstract: Whatever you’re building, your company’s success relies on your development team’s success. The path to building great software is through requirements management. Companies that embrace this concept experience fewer errors and frustration, faster planning and development cycles—and they’re able to deliver higher quality products. Learn about seven essential tips for success with requirements management.

Abstract: Are you on the front lines of product development and project management, and tired of seeing the same project failure statistics? Are you ready to do something to change your approach to requirements management? Then read about the three most common myths (plus a bonus myth) associated with requirements management, and how you can dispel them once and for all—for more successful products and project outcomes.

Abstract: Organizations need to strike a balance between global and local reporting requirements. This is particularly challenging, as a lack of flexibility in data structures adversely impacts both business development and local reporting. Organizations must thus focus on harmonizing the global model and data structures, and assist local entities in designing for local requirements—thereby providing one data source for reporting.

Abstract: In this paper we have taken ten key areas of influence in the evolution of business practices, we look at the changes that have taken place in those areas, and then look at the way ERP systems have to support those areas. In many cases, the requirements today are very different from the requirements ten years ago. Every company's requirements will be different, but the following ten areas seek to highlight the areas of business change which have implications for the ERP system choice, from which a specific and detailed requirements checklist can be drawn up. At the end of the paper, there is a functional checklist that can referred to each of the sections.