Finalizing Scope functionslevel of automation

1
Finalizing Scope (functions/level of automation)

• Finalizing scope in terms of functions and level
  of automation for each function overlaps with and
  requires information from
• Defining target deployment environment
• Defining implementation alternatives
• e.g., build vs. buy
• General Approach for including/excluding
  functions
• Functions deemed mandatory are in scope.
• Include as many important functions as budget and
  schedule allow
• Desirable features delay to later release of
  system
• Strategic plan
• Often, genesis of a new system is organizations
  strategic plan
• Functions that align with strategic plan
  typically get included in scope

2
Finalizing Scope (functions/level of automation)

• Need to revisit feasibility analysis. Now have
  much more information to work with.
• Economic feasibility
• What set of functions give us an optimal return
  on investment?
• What set of functions can we afford?
• Schedule and resource feasibility
• What can be implemented in time available?
• What can be implemented given human and other
  resources?
• Technological feasibility
• What can be practically implemented given state
  of technology and organizations knowledge and
  experience?
• Operational, organizational, and cultural
  feasibility
• What can our organization handle/accept?
• How much change is required?

3
Application Deployment Environment

• What is the technical environment in which system
  will be implemented?
• Deployment environment consists primarily of
• Hardware
• Networks
• System software
• Development software
• Development methodology and tools
• Technical requirements define constraints
  regarding deployment environment
• Organizations current environment/standards
  typically drive deployment options

4
Hardware

• Single-computer
• Mainframe-based
• Limited by single machine capacity
• Clustered
• Group of computers to provide processing and data
  storage capacity
• Cluster acts as a single system

5
Distributed Computing

• Distributes system across several computers and
  locations
• Relies on computing networks for connectivity
• LAN
• WAN
• Client-server architecture dominant model for
  distributed computing

6
Internet

• Increasingly popular frameworks for implementing
  and delivering information systems, both to
  internal users via Intranet and external
  customers, suppliers, etc. via Extranet)

7
Internet as Application Platform

• Organized as client-server architecture
• Can use Web browsers as application interfaces
  (view layer)
• Benefits
• Accessibility
• Low-cost communication and software distribution
• Widely implemented standards

8
Issues with Internet Application Delivery

• Breaches of security
• Fluctuating reliability of network throughput
• Slow, throughput speeds to home users
• Volatile, changing standards

9
Development and System Software Environments

• Consists of standards and tools used in an
  organization to develop systems
• Important components
• Language environment and expertise
• Java, C, etc,
• Existing CASE tools and methodologies
• RUP and Rose, Information Engineering
• Required interfaces to other systems
• Operating system environment
• Unix, Linux, OS390, NT
• Database management system environment
• Oracle, DB2, SQL Server

10
Choosing Implementation Alternatives

• System must be designed and programmed
• Variations on obtaining a system
• Facilities management solutions
• Packaged, turnkey, ERP software systems
• Custom software development
• In-house development

11
Implementation Alternatives
ASPs Salesforce. com MySAP.com
ERP SAP PeopleSoft
Off the shelf packages Simply Accounting
We build, consultants build or blended approach
12
Identifying Criteria for Selection

• Comparisons difficult
• Different proposed systems have strengths in
  different areas
• Need a consistent framework for comparison of
  alternatives
• Criteria
• Weights
• Scores
• Three areas to consider
• General requirements
• Technical requirements
• Functional requirements

13
Evaluation Framework
Weight importance of criteria vs other criteria
Alternatives considered
Evaluation Criteria
Total 49
Total 42
Score Weight
Score
14
General Requirements

• General requirements include considerations that
  are important but not directly associated with
  the computer system itself.
• Related to feasibility assessment alternative
  must be feasible to be chosen
• General requirements examples
• Performance record of the provider
• Level of technical support from the provider
• Warranties and support services (from outside
  vendor)
• Availability of experienced staff
• Development cost
• Expected value of benefits
• Length of time (schedule) until deployment
• Requirements for internal expertise
• Organizational impacts (retraining, skill levels)

15
Technical Requirements

• Constraints under which system must operate
• Defined by technical requirements identified
  during information gathering
• Categories
• Performance (response time/throughput, etc)
• Security and Control
• User interface (ease of use, etc.)
• Service (number/location of users to be
  supported)
• Operating environment
• etc.

16
Functional Requirements

• Need to evaluate alternatives based on how well
  they meet functional requirements.
• Use expanded event table

17
Making the Selection

• After rating alternatives, choice can be made
• Scores are tabulated and compared

18
Presenting Results and Making Decisions

• Compile, organize, and present the alternatives
  and critical issues in an easy-to-understand but
  complete manner
• Final choice generally made by executive steering
  committee
• Format of documentation and presentation style
  varies with organization