Information Systems Analysts and Consultants   (NOC: 2171)

1. 

Reading Text

• Read messages about ongoing work from co-workers, colleagues and clients. (2) , (daily)
• Read about new products in marketing materials such as brochures, pamphlets and product information sheets. for example, they may learn about ad hoc query and reporting analysis tools that can publish information from data warehouses. (2) , (weekly)
• Read comments, suggestions and responses to frequently asked questions posted on internet 'listservs' and forums. for example, they may read about new ways to test database platforms. (2)
• Read about new technologies and their applications in professional journals, industry magazines and periodicals. for example, they may read articles that discuss the arrival of radically restructured database architectures. (3) , (monthly)
• Read about database applications, application platforms, computer languages and hardware in reference and technical manuals. they require a strong understanding of information system technology to understand and apply technical information in these lengthy and complex manuals. (4)
• Read about information systems development projects and requirements in documents such as requests for proposals, business plans and reports. they read these documents for detailed information on a broad range of topics such as technical specifications, project deliverables, timelines and financial constraints. (4)

2. 

Document Use

• Scan tables to locate technical specifications and data such as passwords, dates, names and product identifiers. (1) , (daily)
• Record project activities such as dates, times and actions taken in log books. for example, they may record the length time that systems are down in log books. (1) , (daily)
• Review defect escalation forms written by co-workers and clients to identify the types and severity of database application problems. (2)
• Review gantt charts to determine project schedules, resources being allocated and upcoming activities. (2) , (weekly)
• Review and interpret integrity relationship diagrams to determine key database elements such as entities, attributes, relationships and indexes. (3) , (weekly)
• Interpret lengthy passages of computer language code to determine how an application's functionality such as logical branching or object orientation is achieved. (4) , (daily)
• Interpret process flow charts to understand what data is captured and how it travels between various applications and hardware components. (4)
• Create process flow charts to document how data flows between applications and databases.
• Create gantt charts to identify project activities and timelines.
• May create network topography charts to indicate what hardware components are to be used to store, transfer, display and print data.

3. 

Writing

• Record items discussed with clients using short notes and log entries. for example, they may note that clients understand that toolsets such as oracle designer are used to model, create and test their database applications. (1) , (daily)
• Write memos and e-mail to clients, co-workers and vendors to provide them with work updates and to request information. (2) , (daily)
• Write concise statements in defect escalation reports to describe the severity and frequency of application problems. (2)
• May write policies and procedures to document database application development processes. policies may be lengthy and are written using clear and concise language to avoid misinterpretation on the part of readers. (3)
• Write database implementation plans to document the requirements, approaches and potential problem areas prior to commencing projects. they enter information under headings such as technical specifications, project objectives, planned activities and deliverables. (4)
• May write reports describing database audit reviews. they include detailed information about the purpose of the audit, research approaches, constraints and findings. (4)
• May write lengthy proposals that include technical specifications, benefits, methodologies and costing. they must clearly and concisely present highly technical information in a manner that laypeople can understand and apply. (4)

4. 

Numeracy

• Pay for supplies using cash or credit cards. (money math), (1)
• Check calculations on supplier invoices and approve payments. they confirm quantities, prices and amounts, check tax calculations and verify totals before paying invoices. (money math), (2)
• May prepare invoices and collect payments for consulting services. they charge for the number of billable hours worked or for milestones reached, and calculate goods and services tax amounts. (money math), (2) , (monthly)
• Schedule work and determine the amount of time it will take to complete projects. they organize task lists, plan around vacations and holidays and balance workloads to determine the time it will take to complete projects. (scheduling, budgeting & accounting math), (3)
• Compare application load times to norms to determine if computers and operating systems are running efficiently. (data analysis math), (1)
• Estimate the number of users who will access applications using an analysis of items such as number of points of access and size of user populations. (numerical estimation), (2)
• Estimate the amount of time it will take to transfer data from legacy systems to new applications. they consider the type and amount of data and the attributes of both the old and new systems. (numerical estimation), (2)
• May estimate the resources needed to install new database platforms such as linux. they consider the costs associated with similar projects, expected installation times, the availability of skilled labour and other variables. (numerical estimation), (3)

5. 

Oral Communication

• Discuss task lists, schedules and work loads with co-workers and colleagues. (2) , (weekly)
• Meet clients to discuss topics such as project activities, technical specifications, current business practices, growth plans, regulatory and reporting requirements and security risks. they use clear and succinct language to reduce the chance of misunderstandings. (3) , (monthly)
• May negotiate project fee schedules, timelines and deliverables. they outline their preferred terms and conditions and negotiate concessions as required. (3)
• May meet clients to secure new contracts. they discuss their skill sets, project experiences and the benefits that clients will realize. (3)
• May make presentations to clients. for example, they may present the results of data security audits by providing background information, research findings and the resulting recommendations using language appropriate to the audience's technical backgrounds. (4)

6. 

Problem Solving

• Encounter clients who lack the technical background needed to understand commonly-used acronyms and information technology jargon. they determine the extent of clients' technical understanding and use more appropriate language. (2)
• Determine that projects will not finish on time due to delays caused by work stoppages, late arriving shipments and technical glitches. they work with suppliers, clients and co-workers to resolve the delays and then establish new timelines. (3)
• Have clients who change specifications after projects have started. they determine the extent of the changes and renegotiate timelines and budgets. (3)
• Discover that database applications are not capable of meeting all the technical specifications requested by clients. they consult with clients to discuss the limitations and determine options such as which of the lower priority functions could be abandoned. (3)

7. 

Decision Making

• Decide what labels to assign to fields and tables. (1)
• Select programming languages to execute commands. for example, they may choose javascript to create password protection scripts which require users to enter passwords before accessing information. (2)
• Choose tests to assess the performance of new software applications and platforms such as oracle 9i, ibm db2, microsoft sql server and sybase adaptive server enterprise. for example, they may use manual or automated tests to ensure that relational databases are performing as expected. (2)
• Decide which applications and database platforms will best meet client needs. they factor in the number of users expected, budgets, scalability requirements and the need for web-based technologies such as java, http, web services and xml. (2)
• May decide to bid on projects. they consider the deliverables, timelines, fee schedules and levels of expertise required. (2)
• Decide how to migrate data from legacy systems to database applications such as db2 and sybase by considering data structures, storage requirements and the functionality of new software programs. (3)
• Decide the priority levels of concurrent projects. they consider how delays will affect each project and how they can use available resources to satisfy at least some of their clients. (3)

8. 

Job Task Planning

9. 

Finding Information

• Locate technical specifications, timelines and budgets by referring to proposals, reports and business plans. (1)
• Seek information about system and software malfunctions from co-workers, colleagues and suppliers. (2)
• Consult technical manuals to locate specific information such as program codes and executable commands. (3)

10. 

Computer Use

• Use communications software. for example they use e-mail programs like outlook and communicator to send and receive e-mail, and attachments such as spreadsheets, reports and diagrams. (2) , (daily)
• Use the internet. for example, they use the internet to access vendor and client websites, contact members of access listservs, forums and remotely access databases. (2)
• Use word processing. for example, they use advanced features such as pagination, footnotes and track changes to create and edit reports and proposals. (3) , (weekly)
• Use graphics software. for example, they use advanced features in diagramming programs such as visio to create schematics that outline how data flows between applications. (3) , (weekly)
• Use spreadsheets. for example, they use spreadsheets such as excel and quatro pro to test data integrity and to create budgets that incorporate formulas and macros. (3)
• Use other computer and software applications. for example, they use advanced features in project management applications such as project to organize task lists, schedule activities, balance workloads and create gantt charts. (3)
• Use databases. they conceptualize, design and create data management systems such as database-centric internet applications, enterprise reporting tools, ad-hoc query and analysis tools, online transaction processing systems and programs which manage the full life-cycle of data and metadata. (5) , (daily)
• Do programming and systems software and design. for example, they use a variety of computer languages such as javascript, vb script, codebase and visual basic. for example, they write software routines to optimize performance between clients and servers or they may reduce network traffic and lock contention by executing queries directly on servers. (5)

11. 

Critical Thinking

• Evaluate the acceptability of software performance. they compare the results of manual and automated tests to technical specifications published by suppliers. they verify specifications such as throughput rates, load times, functionality and connectivity. (2) , (daily)
• Evaluate the ability of legacy databases to meet increased data processing and information sharing demands. they consider system architectures, data processing speeds, defect escalation reports and reporting capabilities. (3)
• May evaluate the adequacy of existing database security measures. they review the security risks presented by current business practices and the protection offered by existing security measures such as the use of passwords, firewalls and virus filters. (3)
• Assess the suitability of database platforms and software applications such as enterprise reporting tools and online transaction processing systems. they consider client needs and resources, and the costs, technical supports and specifications provided by suppliers. (4)

12. 

Use of Memory

• Remember registration dates, passwords and logon codes.
• Remember the functionality of software programs.
• Recall which applications and database platforms work best in on-line environments.
• Recall documentation processes used with previous projects.

13. 

Working with Others

14. 

Continuous Learning

15. 

Other Information

• Information systems analysts and consultants sit for long periods of time at desks and computer workstations. they require fine motor skills for keyboarding. strength requirements are light. they occasionally lift technical manuals and office supplies weighing up to five kilograms.

• Information systems analysts and consultants must be client-focused, communicate well with others and have the ability to work independently.

• Information systems analysts and consultants will require enhanced computer skills to keep pace with advancements in information technologies. continuous learning activities will help ensure that these workers remain competitive in their field.