Analysis

Following are some questions you can ask as you analyze your system requirements, with possible answers in parentheses:

• What business problem are you trying to solve? (make remote e-mail access available while traveling; grant branch-office access to large client/server applications, such as a human resources database; streamline the order-entry process; improve customer service)
  
  
• What computing platform and applications are you using? (NetWare, Oracle database, PowerBuilder application on Windows 3.1 desktops)
  
  
• How many users will need access? How many are concurrent users? How long will a typical connection last? (100 users total, 25 concurrent connections, 30 minutes)
  
  
• How will you be connecting to the application server? (asynchronous dial-in; remote node, such as Microsoft Remote Access Service [RAS] or third-party remote node software; LAN; WAN, such as leased line, frame relay, ISDN, ATM; Internet)
  
  
• What client hardware and software will you be using? (486DX/2 notebook running Windows, 12 MB of RAM, Shiva PPP dialer supporting IP and IPX)
  
  
• What are the functional requirements for a remote user? (interactively access Microsoft Office client/server applications; ensure 3270 connectivity to mainframe applications; print e-mail, documents, reports to client printer; transfer files between client and servers; include security protocols, such as dial-back, firewalls, third-party security hardware)
  
  
• What are your performance requirements? (10 seconds to look up a record; type-ahead speed limited to 23 characters for a 50-words-per-minute typist)
  
  
• What is the time frame from the initial pilot to full deployment? (30-day pilot, with full deployment in the following 60 days)
  
  
• Have the resources been allocated for this project? (budget approved, project manager and internal resources assigned, professional systems integrator/Citrix authorized reseller engaged)
  
  
• Who are the decision makers? (director of IS department for budget approval and overall responsibility, vice president of finance for sign-off on success criteria and final OK, project manager “owns” the project)