Filters (0) (reset filters)
Sort by: Date published | Number of comments | Appreciation | Title Ascending | Title Descending | Most popular
Results per page : Page 1 of 13 (61 Result(s))
  • < Prev
  • ...
  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • ...
  • Next >
  • "DevOps can indeed be a positive influence on ITIL, enabling improvements in various processes across the service lifecycle. A more collaborative DevOps approach adds value in service strategy, by ensuring that operations and development functions are included during the development of overall IT business strategy. A DevOps approach also adds value during service design, by ensuring that design coordination includes active participation from both operations and development—resulting in the potential for designing improved functionality and performance, as well as operational support. During service transition, a DevOps approach facilitates the effectiveness and efficiency of both change management, and the process of release and deployment management. By encouraging greater collaboration between development, operations, and indeed all IT functions, a DevOps approach can facilitate knowledge management as well. During service operation a DevOps approach can help ensure closer collaboration between the service desk and backline support and development teams—resulting in more effective incident and problem management. It also emphasizes the need for applying automation to change management as well as release and deployment management "models—thereby facilitating the frequency of deployments, more consistent delivery of new and changed releases, and improved quality. Continual service improvement (CSI) also benefits from a greater level communication and collaboration between development and operations teams, resulting in a higher level of teamwork, synergy, and creativity. The result is a greater likelihood of identifying improvement opportunities across the lifecycle, many of which will be turned into formal CSI improvement proposals - some of which will be approved and chartered for implementation. The result: higher performance, lower costs, and improved service quality."

  • Oracle Partner Network Competency center
    Guided learning paths
    Oracle University Knowledge Center (iLearning)
    My Oracle Support
    Solution Beacon
    Pearson Vue
    Oracle Certview

  • Deployment instructions for the CMS Lite application

  • Technical and Functional design model

  • Table of contents:
    • The Ins and Outs of Fundamental SharePoint Information Architecture Design
    • Make or Break Your Content Management Strategy with Inheritance
    • Supporting Articles
    • What is Information Architecture and Why is it Important?
    • SharePoint 2010 Information Architecture
    • Strategic Information Architecture Plans for SharePoint 2010
    • Taking Control of Governance
    • Want SharePoint Success? Try Dual Architecture.
    • Why Create a Taxonomy for SharePoint ECM Implementation
    • Five Myths about Taxonomy and SharePoint
    • 6 Practical Tips for Designing a Taxonomy
    • Setting the Terms in SharePoint 2010. Do Search and Tag Clouds Replace the Need for a Taxonomy?
    • SharePoint 2010 Marries Formal and Informal Taxonomies
    • SharePoint Governance After-the-fact
    • SharePoint Community Wiki
    • AIIM Training Module SharePoint Practitioner Course 10 - Architecture and ECM
    • Classification...What is it? And How Can it Control the Content Chaos?
    • Next Generation Archives: Changing the Game for Better Management and Control
    • Capture, Governance, and SharePoint: oh the places you could go!
    • 8 Things You Wanted To Know About SharePoint

  • Development workshop simulating the preparation of delivery acceptance testing with task aids and architectural documents defining the unit described in the file. Acceptance testing is put in context and compared to other tests performed by the development team.
    The event concludes with a case study in which the facilitator assists participants during the process.

  • The Preliminary Analysis ("PA") phase focuses on feasibility. It guides the team to clarify the business capability that is desired, establish how that capability will contribute toward business value, and then seek answers to all the questions that affect feasibility. It requires a multi-disciplinary team to integrate business perspectives, architectural concerns and organizational change management issues.
    This learning event enables the learner to use Macroscope material to configure an optimum approach to feasibility in their own situations.

  • Session 10: Testing in the Lab

    In this session of our conversation, Bridging The Gap Between Developers and Testers Using Visual Studio 2010, Etienne and Vincent deploy the web service to the lab environment and then run tests against it to ensure that everything is working.

  • Session 8: Let's Get Back on Track

    In this session of our conversation, Bridging The Gap Between Developers and Testers Using Visual Studio 2010, Vincent updates the code to fix the production bug. Once fixed, he shows us how he associates the changes with the bug and commits the changes. Etienne then creates and runs a test case to prove that the bug has been resolved. Vincent highlights an important point - the new feature that he added is not in the build that Etienne is testing. Why? Etienne is testing the build from the code in the branch that was created for the production release (Vincent's feature was not part of the production release). Etienne then merges the release branch with main branch to bring the bug fix in with the new features developed after the production release.

  • Session 7: Stop, We Have A Problem!

    In this session of our conversation, Bridging The Gap Between Developers and Testers Using Visual Studio 2010, Etienne and Vincent work through a situation that we are all very familiar with - a bug in production code! But how do we deal with defects in code after modifications have been made in support of new features? Branch the code. Etienne and Vincent explore the concept of branching and then show us how to branch code in a project.

  • Session 6: Bridging the Gap

    In this session of our conversation, Bridging The Gap Between Developers and Testers Using Visual Studio 2010, Etienne and Vincent show how the developer uses the information gathered by the tester within Visual
    Studio to resolve a bug. Vincent explores the test results and shows us the output of the recording taken when Etienne, as a tester, was running his test. Remember the IntelliTrace test setting that was enabled? Vincent looks at the results of that IntelliTrace and debugs the code to find the exact line of code that caused the application to crash. Once he makes the required updates to the code, he checks in the code and associates the code check-in with the bug filed by Etienne in the previous session. Last but not least, he updates the bug status, which lets Etienne know that he has a new bug to test.

    Etienne looks up the recommended tests for the particular bug and reruns the test to ensure that the bug is, in fact, fixed. The first time he runs through the test manually. The second time, he uses Test Runner's action
    playback capabilities to have Test Runner run through the test case, enter all the data, and capture the results, all on its own.

  • Session 5: Tester at Work

    In this session of our conversation, Bridging The Gap Between Developers and Testers Using Visual Studio 2010, Etienne and Vincent explore the many different facets of manual testing. First, they introduce us to the different types of tests that can be run with Test Manager and walkthrough creating a test case that runs against the application. Once the test case is designed, Etienne and Vincent show us how to run the test case, record the actions for each step as the test case is being executed, and then explore the results of the test and the information Test Runner captures. All of that information is then used to create a new bug that is then filed for the developers. Etienne also highlights different settings that can be enabled or disabled for each test, including video recording and IntelliTrace.

  • Session 4: Adding a Tester to the Team

    In this session of our conversation, Bridging The Gap Between Developers and Testers Using Visual Studio 2010, Etienne and Vincent talk about the differences between white-box and black-box testing of applications. They switch hats and put on their "tester" hats, introducing us to a new addition to Visual Studio - Test Manager. Etienne demonstrates how to create a new test plan and add test cases to it. But how do you add a test case? Don't worry, Etienne and Vincent cover that in the next session of our conversation.

  • Session 3: Where's our backlog?

    In this session of our conversation, Bridging The Gap Between Developers and Testers Using Visual Studio 2010, Etienne and Vincent show us the basics of a Scrum-based backlog and how to connect and migrate a backlog to Team Foundation Server from Excel. They also introduce us to DemoApp and the bug that's in the code. The bug will be worked on in later sessions of the conversation. During the Q&A session, Etienne also talks about and defines terms used in different methodologies, integration between Team Foundation Server and Project, and Team Foundation Server's API.

  • Session 13: Look Boss, No Hands!

    In this session of our conversation, Bridging The Gap Between Developers and Testers Using Visual Studio 2010, Etienne and Vincent look at automated functional testing by using assertions and the Coded UI Test Builder. Vincent records the actions he wants to tests, sets the conditions he wants to assert, the Coded UI Test Builders generates the test method, and then Vincent adds the test to the coded UI tests that he runs against the application.

  • Session 12: Validating UI Automation

    In this session of our conversation, Bridging The Gap Between Developers and Testers Using Visual Studio 2010, Etienne and Vincent look at automated functional testing by using assertions and the Coded UI Test Builder. Vincent records the actions he wants to tests, sets the conditions he wants to assert, the Coded UI Test Builders generates the test method, and then Vincent adds the test to the coded UI tests that he runs against the application.

  • Session 11: UI Automation

    In this session of our conversation, Bridging The Gap Between Developers and Testers Using Visual Studio 2010, Etienne and Vincent use a previously manually recorded test to created an automated coded UI test. Etienne also demonstrates a trick on how to setup environment variables with scripts to ensure that the test runs against the version of the application that matches the environment in which you're testing without the you having to go in and change the code.

  • Session 3: Where's our backlog?

    In this session of our conversation, Bridging The Gap Between Developers and Testers Using Visual Studio 2010, Etienne and Vincent show us the basics of a Scrum-based backlog and how to connect and migrate a backlog to Team Foundation Server from Excel. They also introduce us to DemoApp and the bug that's in the code. The bug will be worked on in later sessions of the conversation. During the Q&A session, Etienne also talks about and defines terms used in different methodologies, integration between Team Foundation Server and Project, and Team Foundation Server's API.

  • Session 1: Migrating VSS to TFS

    In this session of our conversation, Bridging The Gap Between Developers and Testers Using Visual Studio 2010, Etienne and Vincent give us a brief introduction to Team Foundation Server, it's tools, and how it integrates with the tools in your environment that you're already familiar with such as Visual Studio, Office, and SharePoint. They'll also show us how migration from an existing Visual SourceSafe repository to Team Foundation Server can be automated so that you don't have to migrate everything by hand.

  • Session 2: Automating the Build

    In this session of our conversation, Bridging The Gap Between Developers and Testers Using Visual Studio 2010, Etienne and Vincent talk to us about what is a build, types of builds you can configure in Team Foundation Server, and the advantages of each. They also walkthrough configuring a build, explaining each of the steps required in enabling automated unit tests, sharing of source and symbol files, and retention of builds. Once the build is done, they show us how to read the progress report and understand the information it displays.

  • Fujitsu can draw on its innovative and comprehensive hardware, software and services portfolio to develop personalized solutions for every customer. This is precisely where our strength lies: Fujitsu does not provide off-the-rack IT environments; instead we always find new and ambitious solutions, and together with our customers, develop tailored strategies.

  • This content was submitted by Subramani Sivarathnam.

    This will be an overview of MDM, as well as lesson learned / case study.

    The following items will be covered:

    • What is Master Data Management (MDM)?
    • Hubs in the market
    • Customer Data Hub
    • Product Data Hub
    • Hub and Spoke system architecture and its types
    • Integration strategy and methods
    • Data Mapping, Governance
    • Data flow and Security
    • Project cycle
    • Best practice

  • Session 9: Multi-Environment Testing

    In this session of our conversation, Bridging The Gap Between Developers and Testers Using Visual Studio 2010, Etienne and Vincent introduce us to Lab Management, a new feature of Visual Studio that lets you manage a collection of virtual machines, templates, and virtual environments where you can develop, test, or run your application. Etienne demonstrates how to create a new lab environment and start it in order to test applications.

  • This content was submitted by Ivar Alexander.

    Thought Leadership Presentation:
    This session will cover the latest Automated Process Discovery (APD) technology available from Fujitsu.

    This latest release includes process discovery technology, and adds new management aspects by providing ongoing monitoring and governance of the processes in place.

    The presentation will cover a high level view of the capabilities and architecture of the solution.

  • This content was submitted by Ibrahima Touré.

    The animated SplashScreen is an interface used in WPF as a screen while users are waiting for the download of an application.

    In this video, Ibrahima explains how to develop an animated SplashScreen.

  • This content was submitted by Ibrahima Touré.

    The simple SplashScreen is an image displayed in WPF as a screen for a user waiting for an application to download.

    In this video, Ibrahima explains how to develop a simple SplashScreen.

  • This content was submitted by Ibrahima Touré.

    The animated SplashScreen is an interface used in WPF as a screen while users are waiting for the download of an application.

    In this video, Ibrahima introduces the second part of the lesson on how to develop an animated SplashScreen.

  • This content was submitted by Ibrahima Touré.

    The Scrollviewer control in WPF is a control for unwinding or displaying the protruding part of an item placed in a container encapsulating it.

    In this video, Ibrahima introduces the basic concepts to help properly understand this control.

  • This content was submitted by Ibrahima Touré.

    The Expander control in WPF is a HeaderedContentControl type of control. In action, it plays the role of a container of retractable or expandible elements, based on a certain guideline.

    In this video, Ibrahima introduces the basic concepts to help properly understand this control.

  • This content was submitted by Ibrahima Touré.

    The Popup control in WPF is a control occurring without a real starting Template. Coupled with other controls, the popup control has an aspect of container occurring in execution mode.

    In this video, Ibrahima introduces the basic concepts to help properly understand this control.

  • This content was submitted by Ibrahima Touré.

    The Tooltip control in WPF is a ContentControl type of control. It is quite similar to the popup control without having the latter's persistence capability.

    In this video, Ibrahima introduces the basic concepts to help properly understand this control.

  • This content was submitted by Ibrahima Touré.

    The TabItem control in WPF is an ItemsControl type of control. It can only be used when associated with another control, which is the TabControl.

    In this video, Ibrahima introduces the basic concepts to help properly understand this control.

  • This content was submitted by Ibrahima Touré.

    The GroupBox control in WPF is a HeaderedContentControl type of control. It is very simple and provides a visual indication of the grouping of elements in a window.

    In this video, Ibrahima introduces the basic concepts to help properly understand this control.

  • This content was submitted by Ibrahima Touré.

    The RadioButton control in WPF is a ContentControl type of control. It derives from the ButtonBase class, which makes it a type of button, despite its appearance.

    In this video, Ibrahima introduces the basic concepts to help properly understand this control.

  • This content was submitted by Ibrahima Touré.

    The CheckBox control in WPF is a ContentControl type of control. It derives the ButtonBase class, which makes it a type of button, despite its appearance.

    In this video, Ibrahima introduces the basic concepts to help properly understand these controls.

  • This content was submitted by Ibrahima Touré.

    The Label control in WPF is one of the simplest controls. It is a ContentControl type of control.

    In this video, Ibrahima introduces the basic concepts to help properly understand those controls.

  • This content was submitted by Ibrahima Touré.

    The RepeatButton and ToggleButton controls in WPF are ContentControl types of controls. They are a specific feature of the Control Button.

    In this video, Ibrahima introduces the basic concepts to help properly understand these controls.

  • This content was submitted by Ibrahima Touré.

    The Control Button in WPF is a ContentControl type of control.

    In this video, Ibrahima introduces the basic concepts to help properly understand this control.

  • This content was submitted by Ibrahima Touré.

    In WPF, a control is not just any element that can be placed in window but rather an element that has certain specific factures.

    In this video, Ibrahima introduces an overview of controls.

  • This content was submitted by Ibrahima Touré.

    WPF introduced a new type of event called Routed Event, used in situations involving the execution of event managers based on the ascending or descending hierarchy of interface elements. The concept of routed event may at first glance seem repellent, until it is understood.

    In this video, Ibrahima introduces basic concepts of those types of events.

  • This content was submitted by Ibrahima Touré.

    An AttachedEvent is a type of Routed Event, used in situations involving the execution of event managers following the ascending or descending hierarchy of interface elements.

    In this video, Ibrahima gives an example the development of an Attached Event.

  • This content was submitted by Ibrahima Touré.

    WPF introduced a new type of event called Routed Event, used in situations involving the execution of event managers based on the ascending or descending hierarchy of interface elements. The concept of routed event may at first glance seem repellent, until it is understood.

    In this video, Ibrahima gives an example of the development of Routed Events.

  • This content was submitted by Chris Hammond-Thrasher.

    Alternate title: Why I Have Tape Covering My Webcam.

    For years security professionals have been telling us not to follow links or open attachments from untrusted sources, not to click "Ignore" on your browser's security pop-ups, and not to insert untrusted thumb drives into your USB ports. Do you want to see what can happen with your own eyes? This prensentation will show you how to download, install, configure, and use the basic features of Dave Kennedy's open source hacker tool, the Social Engineering Toolkit.

  • This content was submitted by Ibrahima Touré.

    Developing an ergonomic interface compliant with interfacing standards in terms of margin placement and the positioning or embedding of interface container controls requires a certain technique. In this video, Ibrahima gives an example of the development of an embedded interface via the use of the Grid control container in design mode under Microsoft Expression blend 4.

  • This content was submitted by Ibrahima Touré.

    The StackPanel control container is an interface control used to stack the different controls placed in it based on a specific guideline. In this video, Ibrahima gives an example of the development of a StackPanel.

  • This content was submitted by Ibrahima Touré.

    The WrapPanel control container in WPF is an interface control for docking the various controls placed in it based on a certain position. In this video, Ibrahima gives an example of the development of a WrapPanel.

  • This content was submitted by Ibrahima Touré.

    The DockPanel control container in WPF is an interface control for docking the various controls placed in it based on a certain position. In this video, Ibrahima gives an example of the development of a DockPanel.

  • Developing an ergonomic interface compliant with interfacing standards in terms of margin placement and positioning of the embedding of interface container controls requires a certain technique. In this video, Ibrahima gives an example of the development of an embedded interface via the use of the StackPanel and DockPanel.

  • This content was submitted by Ibrahima Touré.

    The Control Container Grid is an interface control allowing for various controls placed in its cells based on a certain value assigned to the lines and columns of said control. In this video, Ibrahima gives an example of the different characteristics of this control.

  • This content was submitted by Ibrahima Touré.

    Developing an ergonomic interface compliant with interfacing standards in terms of margin placement and the positioning or embedding of interface container controls requires a certain technique. In this video, Ibrahima gives an example of the development of an embedded interface via the use of the Grid control container in design mode under Microsoft Expression blend 4.

  • This content was submitted by Ibrahima Touré.

    WPF introduced a new type of property called Dependency Property, used in various situations for the application of styles, link automation, animations and other items. The concept of dependency property may at first seem repellent, until it is understood. In this video, Ibrahima introduces the basic concepts for understanding this property.

  • This content was submitted by Ibrahima Touré.

    Attached Properties are types of dependency properties used in different situations to apply styles, automate links, produce animations and other items. They are often used when linking two heterogeneous elements.
    In this video, Ibrahima gives an example for understanding AttachedProperties.

  • As changes are continuously increasing, managers give in to the weight of overwhelming emotions. Panicked and unable to overcome their own fear, they struggle to manage those of their employees.
    How can that rapidly learn to manage their emotions and offer the best of themselves?

  • This document presents the new techniques provided by JRE 7 to easily deploy a modern Web application using Java technology

  • This document provides an overview of the target modules for Java EE 7 and the Oracle approach to integrate the principle of PaaS (Platform as a Service) into the Web containers.

  • This document describes a Java EE6 programming workshop

  • This document introduces techniques for deploying Java EE 6 applications with the GlassFish application server