Hardware and Software Evaluation Procedures for Business Client Solution Implementation
Notes for Preparing the Information Technology Case Proposal
Overall Evaluation Goal: The goal of hardware or software evaluation is to select a hardware or software product that is the best match between the business requirements (needs) with the capabilities (includes specifications) of an information technology hardware or software product.
Each student will conduct two kinds of evaluation during the semester: First Fit (Select the first product that meets the client requirements and complies with the conditions itemized below) and Best Fit (Select the product that is the Best-Fit from a comparison of several products based on the Best-Fit with the client’s requirements and complies with the Best-Fit conditions itemized below) Evaluations.
The First-Fit analysis will be done in the Software Proposal Case (Doctor’s office case proposal on medical practice management software analysis and selection. The Best-Fit analysis will be done on the Hardware analysis and selection in the hardware case proposal. Review the conditions and situations where First-Fit and Best-Fit evaluations are applied in the definitions below including the conditions for Hardware and Software requirements related to Maturity, Stability and Proven Track Record:
First fit should be used when the goal is simply to fulfill a minimum set of needs—when additional “goodness” of a product is unimportant or it is not cost effective to evaluate to determine additional goodness. First fit considers minimum requirements and answers the question “Is it good enough?”
Best fit should be used when there is an appreciable gain in getting more than the minimal amount of some characteristic. For example, in many situations a minimum performance is specified, but better performance adds significant value to a product within the context of the system. Best fit is also the approach to use in situations where no product has all the capabilities being sought in a particular evaluation. Best fit answers the question “How good is it?”
Hardware and Software Maturity, Stability and Proven Track Record: Hardware and software evaluation tasks and processes were based on meeting business needs or requirements rather than selecting products based on “bells and whistles” or immature technology that is too new to have been shown through research, testing, user reliability and vendor stability and support (proven track record) to meet business needs/requirements in a reliable, user friendly, cost effective manner.
IT Hardware & Software Evaluation Steps with IT Case Proposal Sections
IT Case Proposal Sections and Applicable Content Requirements
1. ORGANIZATIONAL PROFILE AND OPERATIONAL ENVIRONMENT
Stakeholder Profile
Information Technology Network Structure
Hardware and Software Installed Base
Identify the organization and describe the organization’s business environment, stakeholders,
business and operational needs. Discuss the role of information technology in addressing and
resolving the organization’s business and stakeholder’s job task, training, skill level and support
needs.
This handout is used in conjunction with the Hardware and Software Evaluation Case Proposal
Template. Refer to this Template to see how this handout is used as a base to develop a hardware
or software evaluation case proposal.
2. PROBLEM AND OPERATIONAL REQUIREMENTS
Problem and Opportunity Identification
Operational Selection Requirements
a. Itemized list of Requirements
b. Requirements Ranked by Priority
Hardware or Software Selection Requirements
a. Conformity Requirements
b. Compatibility Requirements
Describe the organizational problem, opportunity and operational requirements within the context of the organizational problem, purpose, operational requirements. The operational requirements constitute the selection criteria for the proposed hardware or software solution.
This section should define the operational selection requirements, hardware or software selection requirements (conformity, compatibility requirements).
This handout is used in conjunction with the Hardware and Software Evaluation Case Proposal
Template. Refer to this Template to see how this handout is used as a base to develop a hardware or
software evaluation case proposal.
Requirements Ranking: The requirements for the proposed hardware or software solution are itemized into a list of requirements that are ranked in order from the highest priority** or essential business needs or capabilities. These requirements must be written in task oriented language that detail the tasks, operations or results that will be achieved through the implementation of the project.
** Ranking the Requirements by Priority Criteria Process:
Rank the requirements by the priorities of these specific features in terms of what is really required. Are they:
Mission-critical – If essential components are not already included within the proposed solution, is it
unacceptable?
Desirable – If added to existing functionality, will the additional features enhance or improve the affected
business processes?
Nice to have – If available, and there is no significant additional cost, do these features affect the final
selection?
See the following Hardware and software selection criteria that incorporates the requirements for conformity, compatibility with the current system, software, business model:
Hardware Selection Criteria
Hardware must support the current software infrastructure as well as any planned software purchases for the next two year planning period
Hardware must be compatible with existing or planned networks
Hardware must be upgradeable and expandable to meet the needs of the next planning interval
Hardware warranties must be of an appropriate length Software Selection Criteria
Software must be compatible with current and future hardware over the next planning interval
Software maintenance and warranties must be of appropriate length and cost
Software must be standardized throughout the business to improve purchasing power, simplify training, and facilitate support
Software must comply with current standards set by technology leadership Software must support and enhance business goals
3. PROPOSED SOLUTION PROFILE AND APPLICATION
Purpose
Specifications
Deliverables (Components)
Pricing
Training and Support Provided with Pricing
Describe the proposed solution. This section explains how the solution matches the operational, conformity, compatibility and other selection requirements by discussing the solution’s specifications, components, and how the solution will integrate and operate with the current infrastructure and systems.
This section should address the “goodness” of fit between the operational, conformity, compatibility and other requirements and the capabilities and applications of the proposed solution.
Implementation Time Frame & Schedule
Justification
Conformity to Business Strategies and Standards
Technical Impact (Compatibility with Current and Planned Infrastructure Updates or Expansion for Two Years)
Maturity, Scalability and Proven Track Record
Scope and Limitations Parameters
This handout is used in conjunction with the Hardware and Software Evaluation Case Proposal
Template. Refer to this Template to see how this handout is used as a base to develop a hardware
or software evaluation case proposal.
4. EVALUATION OF SOLUTION EFFECIVENESS)
Rationale and Justification
Evaluation Criteria
Evaluation Measures
Describe and discuss the criteria and measures used to judge the effectiveness of the information technology solution.
This section should address the overall effectiveness of the solution and the measures that determine the solution’s level of effectiveness.
This handout is used in conjunction with the Hardware and Software Evaluation Case Proposal
Template. Refer to this Template to see how this handout is used as a base to develop a hardware
or software evaluation case proposal.
5. REFERENCES (Research Sources)
References are listed in complete APA citation style
Research references or sources formatted in APA citation style are included (but not limited to): articles from information technology publications, product comparison articles and reviews, product or vendor web sites, product brochures, information from software database sites (Capterra), etc.