Documents » software methodology.
Abstract: It’s a sad but well-known fact that many
software implementation projects run out of time and money. Certain crucial activities tend to have striking effects on the cost of an implementation. But it’s possible to stick to plans and budgets, provided that you do the right things and avoid the traps. Discover which parts of a
software implementation are worth spending extra money on in order to minimize risk and cost.
PubDate: 5/11/2010 2:39:00 PM
Abstract: The Microsoft Dynamics NAV Rapid Implementation Methodology (RIM) automates standard processes, speeds up implementation time, and drives the sharing of best practice knowledge and solutions between partners. But in order to understand how RIM can be used in an implementation project to get implementations up and running smoothly and quickly, it is important to understand the different components of RIM.
Abstract: A dashboard is a vital tool for monitoring the daily health of your organization. From a single interface, decision makers have access to key performance indicators (KPI)—actionable information that can be used to effectively guide and track business performance. Successful implementation of a dashboard is complex and requires a step-by-step process using a methodology that considers all aspects of the project life cycle.
Abstract: The Delphi technique—drawing wise counsel from senior and experienced software developers—can help you prepare estimates for software development projects. With this method of software estimation, project specifications are given to a few experts, depending on their availability. Learn about the essential steps involved in this software estimation methodology for more accurate estimates of software development effort.
Abstract: While many software professionals know one or more software sizing techniques—most have a reasonable understanding of function point analysis (FPA) or use case point techniques—they’re often stymied when it comes to making a real-life estimate. Learn a methodology that can help you make realistic estimates, including best- and worst-case scenarios that you can use to make pricing and delivery commitments to clients.
Abstract: We all know the payoffs that can result from the “agile” methodology: highly effective self-managed teams, increased flexibility, real-time change management, tight quality control … and the list goes on. But what happens when you need to expand your agility to include an outsourcing partner 5,000 miles away? Learn what happened to Elastic Path, a Canadian company competing in the fast-paced market of e-commerce software.
Abstract: A group of serial entrepreneurs was look¬ing to jump-start business operations at a series of high technology startups by implementing advanced manufacturing software early in the business cycle. In implementing Expandable ERP at each of their startup companies, the entrepreneurs were able to minimize their risk by developing a repeatable methodology for establishing sound manufacturing operations.
Abstract: In order to achieve success, all business software projects have to surmount requirements risk, technical risk, and planning risk. Many software developers have thus adopted an iterative delivery methodology, finishing first the essential features, and then those additional features which deliver the most value. Some fundamental insights will provide a better understanding of how to set up iterative delivery projects.
Abstract: You may already know what disk defragmentation software does and what the benefits are. Take a closer look at the benefits in performance, cost, time-to-complete, wattage consumed for each test, and overall kilowatt hours (KWHs) consumed with Diskeeper defragmentation software. All tests, including methodology, format, and protocols, were performed with a focus of determining power and cost savings. Learn more.
Abstract: The challenge of supply chain management (SCM) is to identify and implement strategies that minimize costs while maximizing flexibility. Computer simulation can be a valuable tool along your supply chain to help diagnose problems and evaluate possible solutions, and mitigate risks. Discover the methodology for building supply chain models, and the critical criteria for selecting simulation software that fits your needs.
Abstract: Day-to-day IT requirements are often managed at the expense of strategic goals. But if you can consistently control change in your IT environment, you’ll be that much closer to resource efficiency and risk mitigation. Learn about a four-phase change management methodology that, when used with enterprise software, can help you detect, track, and analyze change—for continuous improvements and more budget for new projects.
Abstract: The later in the system development life cycle (SDLC) major errors are discovered, the more expensive it is to fix them. In fact, errors in released software are up to 80 times more expensive to fix than defects in the specification stage. That’s why you should adopt a methodology that brings the early stages of the SDLC up to a high level of maturity, in a way that’s consistent, proven, and optimized for success.
Abstract: Component event management promises an answer. Component event management is a methodology to systematically detect and resolve component events in the most timely and efficient manner possible. This paper will introduce the philosophy of component event management and introduce a new category of software that is being developed to help implement this concept and improve business performance.
Abstract: Arysta LifeScience, one of the largest privately held crop protection and life sciences companies in the world, needed a business intelligence (BI) and business performance management (BPM) solution that would give users access to information from multiple systems, across multiple business areas. Learn how TEC’s software evaluation and selection methodology helped Arysta select the winning solution in only three months.
Abstract: Sales at F.J. Westcott began to grow, placing a greater demand on its legacy enterprise resource planning (ERP) system’s inventory capabilities. Unrelieved inventory and other challenges led Westcott to seek a new ERP system—and a software evaluation and comparison methodology within the company’s budget. See how Technology Evaluation Centers’ Software Selection Services provided the resources for a confident decision.
Abstract: Following several acquisitions, Colombia-based ceramics manufacturer Corona found itself with multiple enterprise resource planning (ERP) systems to manage. To find a single ERP solution that was suitable for all of its facilities, and would integrate with its existing business software, Corona turned to Technology Evaluation Centers (TEC). Learn how TEC’s selection methodology helped Corona choose the right ERP software.
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.
Abstract: After testing procedures have been created and the type of test data has been determined, link or string testing, and system testing must be executed to ensure the job stream is correct and to locate errors before production. Backup and restart testing must be also be conducted to ensure that the restart points within the system are accurately defined. Finally, to demonstrate the benefits and functionality of the system, management and user approval should be received.
Abstract: Program testing and debugging is one of the most critical aspects of implementing a computer system. Without programs which properly work, the system will never process information and produce the output for which it was designed. Testing procedures should be established and testing roles should be demarcated between the programmer and the analyst. Once this is done, test data that can test the limits of the program should then be created.