Development and Management of Sustainable Enterprise Information Portals (2018) / Chapter Skim
Currently Skimming:
Pages 222-230
The Chapter Skim interface presents what we've algorithmically identified as the most significant single chunk of text within every page in the chapter.
Select key terms on the right to highlight them within pages of the chapter.
From page 222... ...
222 Appendix A Full Interview Guide INTERVIEWER NOTE: This guide contains a list of questions. However, it is anticipated that the conduct of each interview will adopt a relaxed, conversational tone. Please paraphrase or adjust the order of questions to enhance rapport and keep the discussion moving forward. Focus on identifying processes, resources and capabilities, technical necessities, components, barriers and issues, and concerns. Introduction Prior to asking questions to the interviewee, we will Identify who is on the phone and their role on the project Identify goal of the project using the paragraph below: State Departments of Transportation produce and use a non‐negligible amount and a large variety of data and information to make decisions. Web portals have become the primary way of providing DOT internal and external users with the information they want in a timely and cost‐effective manner. DOT Enterprise information portals (EIPs) are how DOTs provide and manage several web portals to their users. EIP are challenging to design, maintain and evolve because they encompass many diverse web portals, many diverse datasets and functions. The goal of this project is to identify what are the requirements of a DOT EIP web portal and what architecture should it use to be sustainable, that is to grow with its datasets, adapt to new technologies (Sensors, GIS, etc.)
|
From page 223... ...
223 Today's conversation is scheduled for one hour, and we have some questions to guide us and make sure we finish within the time frame Beg forgiveness for pushing ahead on some questions in the interest of time. We will try to come back to other issues at the end if time allows. 1. Background/Profile Name Contact Information Agency/Division Role/Title Bio Note background, expertise, years with agency, responsibilities Links Relevant links to portal interfaces, organization division, etc.
|
From page 224... ...
224 Focus on current clients and data. More forward‐looking responses will be noted and followed‐ up in the next section. Interviewer note: Focus on current clients and hold discussion of future needs until later. After the interview, the answers should be arranged in a table similar to the one below. End-User Type Example Priority Why? What value is this user to the agency?
|
From page 225... ...
225 How is search being used on your portal/service? How many documents are expected to be indexed?
|
From page 226... ...
226 Business Objectives This section of the interview focuses on extracting the business objectives and business requirements of DOT EIPs. It is important to understand objectives and requirements early so as not to make erroneous assumptions that could affect the accuracy of your future deployments. Example questions: What are the current and future business goals of this portal/service? (For example, do you want to enhance customer service?
|
From page 227... ...
227 Front‐End Systems This section of the interview explores the front‐end systems that will be used for access to DOT EIP. It will help identify how your users will connect to your portal and what kinds of devices they will use. Example questions: How will users access your portal? What environments do your users have?
|
From page 228... ...
228 Interviewer note: If time allows, ask the questions in this additional focus area Back‐End Systems This section of the interview examines the current and future DOT EIP back‐end systems to assess what will be needed to support the current and future needs of the DOT EIPs. Scalability, performance, and data center organization are among the factors to be explored. Example questions: Does your organization have the technical competence and support organization to deploy and maintain the portal system? Are back‐end systems scaled to levels that your portal will need?
|
From page 229... ...
229 What transaction volume do you expect? What transaction volume do you expect during peak use?
|
From page 230... ...
230 What are the obstacles to accomplishing these goals? What is your ideal approach to sharing data with clients?
|
Key Terms
This material may be derived from roughly machine-read images, and so is provided only to facilitate research.
More
information on Chapter Skim is available.