Latest Entries »

Web design is a broad term covering many different skills and disciplines that are used in the production and maintenance of websites. The different areas of web design include; web graphic design, interface design, authoring; including standardised code and proprietary software, user experience design, and search engine optimization. Often many individuals will work in teams covering different aspects of the design process, although some designers will cover them all. The term web design is normally used to describe the design process relating to the front-end (client side) design of a website including writing mark up, but this is a grey area as this is also covered by web development. Web designers are expected to have an awareness of usability and if their role involves creating mark up then they are also expected to be up to date with web accessibility guidelines.

LDT CONSULTING, INC.

LDT Consulting, Inc. offers 20+ years of IT expertise in various industries and vertical markets helping clients meet user requirements while providing quality end-solutions as both an employee and an independent consultant. Lezlie Tanasiuk has provided professional services to government and municipalities and fortune 500 companies.

A blog (a portmanteau of the term web log) is a discussion or information site published on the World Wide Web consisting of discrete entries (“posts”) typically displayed in reverse chronological order so the most recent post appears first. Until 2009 blogs were usually the work of a single individual, occasionally of a small group, and often were themed on a single subject. More recently “multi-author blogs” (MABs) have developed, with posts written by large numbers of authors and professionally edited. MABs from newspapers, other media outlets, universities, think tanks, interest groups and similar institutions account for an increasing proportion of blog traffic. The rise of Twitter and other “microblogging” systems helps integrate MABs and single-author blogs into societal newstreams. Blog can also be used as a verb, meaning to maintain or add content to a blog.

LDT CONSULTING, INC.

LDT Consulting, Inc. offers 20+ years of IT expertise in various industries and vertical markets helping clients meet user requirements while providing quality end-solutions as both an employee and an independent consultant. Lezlie Tanasiuk has provided professional services to government and municipalities and fortune 500 companies.

Telus Communications – Partner Service Management:
In requirements engineering, requirements elicitation is the practice of collecting the requirements of a system from users, customers and other stakeholders.  The practice is also sometimes referred to as requirements gathering.

The term elicitation is used in books and research to raise the fact that good requirements can not just be collected from the customer, as would be indicated by the name requirements gathering. Requirements elicitation is non-trivial because you can never be sure you get all requirements from the user and customer by just asking them what the system should do. Requirements elicitation practices include interviews, questionnaires, user observation, workshops, brain storming, use cases, role playing and prototyping.

TELUS Partner Service Management is all about forming creative partnerships with other Canadian, American and global service providers. The Business Analyst of the Partner Service Management team has three key areas of focus:

  • Delivering on Corporate, Mandated, Service Development & Strategic Initiatives
  • Designing & executing on tactical plans that improve processes; customer experience
  • Supporting our Sales, Marketing, and CARE Operations & Strategies
    Use case defines a goal-oriented set of interactions between external users and the system under consideration or development. Use cases have become a widespread practice for capturing functional requirements in software design, especially in the object-oriented community where they originated, but their applicability is much wider.

    A Use Case Scenario is a description that illustrates, step by step, how a user is intending to use a system, essentially capturing the system behavior from the user’s point of view. A use case scenario can include stories, examples, and drawings. Use cases are extremely useful for describing the problem domain in unambiguous terms and for communicating with the potential users of a system.

Sales Order Solution Project

The Sales Order Solution project will deliver the sales order, registration/renewal data, logic, and service components for a Service Oriented Architecture (SOA) required for the ATLAS deployment in Europe, in a manner that ensures the effective delivery of these capabilities for web services and the contact center that meet business, functional and non-functional requirements and the unique aspects of Amway’s sales related processes without depending on Oracle EBS for the execution of transactions.

Identified business processes in scope for the Sales Order Solution but limited to order capture and prepared Use Case Diagrams (Context Models) and developed business and system Use Cases for the Enterprise Services department and the Functional Specification deliverable. Processes included:

  1. Distributor Registration
  2. Distributor Resignation
  3. Distributor Blocks and Privileges
  4. Create Sales Order
  5. Item Substitution and Back Order
  6. Process Sales Order
  7. Billing
  8. Distributor Bonus
  9. Awards and Line of Sponsorship

In requirements engineering, requirements elicitation is the practice of collecting the requirements of a system from users, customers and other stakeholders.  The practice is also sometimes referred to as requirements gathering.

The term elicitation is used in books and research to raise the fact that good requirements can not just be collected from the customer, as would be indicated by the name requirements gathering. Requirements elicitation is non-trivial because you can never be sure you get all requirements from the user and customer by just asking them what the system should do. Requirements elicitation practices include interviews, questionnaires, user observation, workshops, brain storming, use cases, role playing and prototyping.

Common Infrastructure – STMS Kamloops!

Establish the Managed Services Cage in the Q9 Kamloops facility. The cage must be in a state to accept requirements/requests for the installation of servers intended to support HP Advanced Solutions ongoing business.

This project introduces the following common infrastructure and services:

  • Base IT services (Active Directory [AD], Domain Name Services [DNS], Network Time Protocol [NTP], Simple Mail Transfer Protocol [SMTP], Patching solutions [PAU/BSA, YUM, NAS])
  • Set-up provisioning process and base infrastructure services for the *.nix, Windows, and the Database environment
  • Virtualization Infrastructure (bare-bones ESX environment set-up for SAN/BUR project)

Shared File and Print Transformation!

The Shared File Print (SFP) service is the corner stone of office productivity services for users and their applications. It is the most widely used Hosting Service; used by over 35,000 BC Public Servants. The current environment consists of over 250TB of data and over 100 servers used to support the environment.

Advanced Solutions is creating a new version of the SFP architecture. The strategy involves replacing multiple Windows servers with larger Network Attached Storage (NAS) devices, as well as virtualizing print queues.

This architecture will allow for improvements to the Province’s Green direction by removing approximately 100 servers from the Data Centres; saving floor space, as well as power usage, and resulting in cost savings to both the Province and HP Advanced Solutions.

In project management, a project charter, project definition or project statement is a statement of the scope, objectives and participants in a project. It provides a preliminary delineation of roles and responsibilities, outlines the project objectives, identifies the main stakeholders, and defines the authority of the project manager. It serves as a reference of authority for the future of the project. The terms of reference is usually part of the project charter.

Common Infrastructure – STMS Kamloops!

Establish the Managed Services Cage in the Q9 Kamloops facility. The cage must be in a state to accept requirements/requests for the installation of servers intended to support HP Advanced Solutions ongoing business.

This project introduces the following common infrastructure and services:

  • Base IT services (Active Directory [AD], Domain Name Services [DNS], Network Time Protocol [NTP], Simple Mail Transfer Protocol [SMTP], Patching solutions [PAU/BSA, YUM, NAS])
  • Set-up provisioning process and base infrastructure services for the *.nix, Windows, and the Database environment
  • Virtualization Infrastructure (bare-bones ESX environment set-up for SAN/BUR project)

  • Fit/Gap analysis is an important component in the Project Life Cycle.

  • In this phase a study is made to identify whether the present system fits the requirements, and if any such gaps are identified, they are recorded in a prescribed format.

    Trip Planner III Project!

      The primary objective of the Trip Planner III Project was to gather investment gate, business requirements and complete the fit / gap analysis for an estimated $350,000.00 enhancement to the trip planner application located at the City of Edmonton web portal.

    http://etstripplanner.edmonton.ca/PlanYourTrip.aspx

    The Information Technology Branch (ITB), Stage Gate Methodology included the Concept, Investment, Design, Implementation, Post Implementation and Post Project Evaluation gates. The platform was MS .Net Framework and future technologies may include Google Maps utilizing spatial data.

    In project management, a schedule consists of a list of a project’s terminal elements with intended start and finish dates. Terminal elements are the lowest element in a schedule, which is not further subdivided. Those items are often estimated in terms of resource requirements, budget and duration, linked by dependencies and scheduled.

    Cost–benefit analysis (CBA), sometimes called benefit–cost analysis (BCA), is a systematic process for calculating and comparing benefits and costs of a project, decision or government policy (hereafter, “project”). CBA has two purposes:

    1. To determine if it is a sound investment/decision (justification/feasibility),
    2. To provide a basis for comparing projects. It involves comparing the total expected cost of each option against the total expected benefits, to see whether the benefits outweigh the costs, and by how much.

    Work Order Management Scada Solution – Hydro One

    • Conducted Cost-Benefit analysis for Hydro One’s (Toronto, ON) to compare benefits and costs to provide a work order management soltuion (Infowave’s COTS solution).
    Follow

    Get every new post delivered to your Inbox.