Engineering and Innovation, a key focus activity for Corporate Engineering & Technology, is pleased to introduce one-hour Webinars, aimed at helping systems and software engineers and architects achieve flawless execution in the development of complex solutions that are delivered problem free to the customer. http://www.computer.org/lockheed Technology : Software Copyright ©2011, IEEE, Inc. All rights reserved. http://blogs.law.harvard.edu/tech/rss en-us Fri, 4 May 2012 17:20:02 -0700 dsims@computer.org Fri, 4 May 2012 17:17:40 -0700 webmaster@computer.org FeedForAll v2.0 (2.0.3.1) http://www.feedforall.com The Systems & Software Initiative, a key focus activity for Corporate Engineering & Technology, is pleased to introduce the first in a series of ten, one-hour Webinars. The Systems & Software Initiative, a key focus activity for Corporate Engineering & Technology, is pleased to introduce the first in a series of ten, one-hour Webinars, aimed at helping systems and software engineers and architects achieve flawless execution in the development of complex solutions that are delivered problem free to the customer. IEEE Computer Society Debbie Sims dsims@computer.org IEEE, Computer Society, software architecture, software development clean yes http://media.computer.org/sponsored/podcast/lmco/lmco144.jpg http://www.computer.org/lockheed The Systems & Software Initiative, a key focus activity for Corporate Engineering & Technology, is pleasedXto introduce the first in a series of ten, one-hour Webinars. 144 144 The past few years have witnessed high-end processors with increasing numbers of cores and larger dies. With limited instruction-level parallelism (ILP), chip power constraints, and non-ideal technology scaling, processor designers have embraced multiple cores rather than single-core performance scaling to improve chip throughput and to meet Moore's Law. This webinar provides some important insights on whether this approach is sustainable by investigating a scaling trend from a state-of-the-art big-chip design point using analytical models. It also discusses technical challenges and potential opportunities for processor and system design engineers. http://www.computer.org/lockheed Software Development A05DFEF2-EE9A-4BA8-BB42-747626300494 Thu, 26 Apr 2012 09:00:00 -0700 LMCO SSI Webinar Series This webinar investigates a scaling trend from a state-of-the-art big-chip design point using analytical models. The past few years have witnessed high-end processors with increasing numbers of cores and larger dies. With limited instruction-level parallelism (ILP), chip power constraints, and non-ideal technology scaling, processor designers have embraced multiple cores rather than single-core performance scaling to improve chip throughput and to meet Moore's Law. This webinar provides some important insights on whether this approach is sustainable by investigating a scaling trend from a state-of-the-art big-chip design point using analytical models. It also discusses technical challenges and potential opportunities for processor and system design engineers. 0:59:02 Wei Huang software development, scaling, design constrainsts, instruction-level parallelism, ILP, chip power, big chip, multicore no yes Test automation skills are too often directly tied to a resource’s experience with a specific tool. This does little to help managers distinguish between an effective test automator and a person that has simply memorized some popular tool syntax. In addition, this correlation does little to prepare testers for important tasks associated with test automation; it prevents those already proficient at test automation from being able to appropriately market their abilities and it stymies the entire test automation discipline. This presentation helps to eliminate the skills-to-tools correlation by relaying some of the fundamental, transferrable skills necessary for an automation test professional to be effective across tools. Knowledge and proficiency in these skills will help organizations acquire the right resources, while helping automators more effectively improve and market their abilities. http://www.computer.org/lockheed Software Development BDABB462-E66A-4569-829B-8E60499B506E Thu, 5 Apr 2012 09:00:00 -0700 LMCO SSI Webinar Series This presentation helps to eliminate the skills-to-tools correlation by relaying some of the fundamental, transferrable skills necessary for an automation test professional to be effective across tools. Test automation skills are too often directly tied to a resource’s experience with a specific tool. This does little to help managers distinguish between an effective test automator and a person that has simply memorized some popular tool syntax. In addition, this correlation does little to prepare testers for important tasks associated with test automation; it prevents those already proficient at test automation from being able to appropriately market their abilities and it stymies the entire test automation discipline. This presentation helps to eliminate the skills-to-tools correlation by relaying some of the fundamental, transferrable skills necessary for an automation test professional to be effective across tools. Knowledge and proficiency in these skills will help organizations acquire the right resources, while helping automators more effectively improve and market their abilities. 1:00:10 Dion Johnson software development, automation, test automation no yes In a large scale industrial software development environment, software measurement must be meaningful, automatable, nonintrusive, and feasible. For a company to survive and to make progress against its competition, it must have answers to questions such as "What is my customers' perception of the quality of the software in my products?", "How long will it take me to complete a new product or a new release of an existing one?" "What are the major bottlenecks in software production?" "How effective is a new technique or tool when introduced into the software development process?" Sources of data are diffuse, nonuniform, and nonstandard. The data itself are difficult to collect and interpret, and hard to compare across projects and organizations. Nonetheless, other industries perform such measurements as a matter of course, and software development organizations should as well. In this talk David Weiss discusses the challenges of deciding what questions to ask, how to answer them, and what the impact of answering them is. He illustrates with examples drawn from real projects, focusing on change data and how to use it to answer some of the questions posed in the preceding. http://www.computer.org/lockheed Software Development BFD28741-DC38-466D-B49B-BF22E15F9A2F Thu, 22 Mar 2012 09:00:00 -0700 LMCO SSI Webinar Series In this talk David Weiss discusses the challenges of deciding what questions to ask, how to answer them, and what the impact of answering them is. In a large scale industrial software development environment, software measurement must be meaningful, automatable, nonintrusive, and feasible. For a company to survive and to make progress against its competition, it must have answers to questions such as "What is my customers' perception of the quality of the software in my products?", "How long will it take me to complete a new product or a new release of an existing one?" "What are the major bottlenecks in software production?" "How effective is a new technique or tool when introduced into the software development process?" Sources of data are diffuse, nonuniform, and nonstandard. The data itself are difficult to collect and interpret, and hard to compare across projects and organizations. Nonetheless, other industries perform such measurements as a matter of course, and software development organizations should as well. In this talk David Weiss discusses the challenges of deciding what questions to ask, how to answer them, and what the impact of answering them is. He illustrates with examples drawn from real projects, focusing on change data and how to use it to answer some of the questions posed in the preceding. 1:00:28 David M. Weiss software development, quality of service, software measurement no yes As budgetary pressure on government systems continues to increase, the interest in reusing products is emerging. Reuse is the idea of leveraging previously developed products (i.e. hardware, software, designs, outcomes of a process, etc.) into a new application for purposes of improving project attributes such as quality, cost, schedule, or risk. While reuse is well-documented and commonly practiced in the domains of software and product-line development, limited research has been performed on the (deliberate or accidental) reuse of systems engineering products. Unfortunately, there are many misconceptions about the economic benefits of reuse. These include: Misconception #1: reuse is free Misconception #2: the payoff of reuse is immediate Misconception #3: the benefits of reuse are higher for small projects than for large projects To clarify these misconceptions we provide a generalized framework that can help guide more disciplined reuse of systems engineering products; documenting the key considerations, activities, and resources necessary for effective reuse. Building on insight from systems engineering practitioners and previous work on systems engineering cost estimation, the framework is intended to serve as a tool for planning, executing, and managing reuse activities, as well as identifying reuse opportunities. We also provide tips on what engineers can do to create more reusable products for future benefit. Recommended reading: Wang, G., Valerdi, R. and Fortune, J., "Reuse in Systems Engineering," IEEE Systems Journal, 4(3), 376-384, 2010; 10.1109/JSYST.2010.2051748. http://www.computer.org/lockheed Reuse 6B05FC75-9299-42E1-A719-595A866D5A45 Thu, 8 Mar 2012 09:00:00 -0700 LMCO SSI Webinar Series To clarify misconceptions on the economics of reuse, we provide a generalized framework that can help guide more disciplined reuse of systems engineering products; documenting the key considerations, activities, and resources necessary. As budgetary pressure on government systems continues to increase, the interest in reusing products is emerging. Reuse is the idea of leveraging previously developed products (i.e. hardware, software, designs, outcomes of a process, etc.) into a new application for purposes of improving project attributes such as quality, cost, schedule, or risk. While reuse is well-documented and commonly practiced in the domains of software and product-line development, limited research has been performed on the (deliberate or accidental) reuse of systems engineering products. Unfortunately, there are many misconceptions about the economic benefits of reuse. These include: Misconception #1: reuse is free Misconception #2: the payoff of reuse is immediate Misconception #3: the benefits of reuse are higher for small projects than for large projects To clarify these misconceptions we provide a generalized framework that can help guide more disciplined reuse of systems engineering products; documenting the key considerations, activities, and resources necessary for effective reuse. Building on insight from systems engineering practitioners and previous work on systems engineering cost estimation, the framework is intended to serve as a tool for planning, executing, and managing reuse activities, as well as identifying reuse opportunities. We also provide tips on what engineers can do to create more reusable products for future benefit. Recommended reading: Wang, G., Valerdi, R. and Fortune, J., "Reuse in Systems Engineering," IEEE Systems Journal, 4(3), 376-384, 2010; 10.1109/JSYST.2010.2051748. 59:54 Ricardo Valerdi reuse, economics, budget, product improvement no yes Systems are fragile when it comes to security because they have overlooked critical dependencies which frequently fail. One such dependency is that end users will make good security choices. Another is that the supply chain is reliable. To deal with modern cybercriminals, hacktivists and perpetrators of Advanced Persistent Threats that will go after our dependencies, we need to be agile and fault tolerant. This talks takes a look at the science (and art) of security fragility. It will pull striking examples from IT, physics, weather, and business and introduce The Five Laws of Security Fragility. http://www.computer.org/lockheed Security 547C24EF-8C19-43A3-A509-63F8941582B0 Thu, 23 Feb 2012 09:00:00 -0800 LMCO SSI Webinar Series This talks takes a look at the science (and art) of security fragility. It will pull striking examples from IT, physics, weather, and business and introduce The Five Laws of Security Fragility. Systems are fragile when it comes to security because they have overlooked critical dependencies which frequently fail. One such dependency is that end users will make good security choices. Another is that the supply chain is reliable. To deal with modern cybercriminals, hacktivists and perpetrators of Advanced Persistent Threats that will go after our dependencies, we need to be agile and fault tolerant. This talks takes a look at the science (and art) of security fragility. It will pull striking examples from IT, physics, weather, and business and introduce The Five Laws of Security Fragility. 59:07 Herbert "Hugh" Thompson security, fragility, critical dependency, cybercriminal, hacktivist, persistent threats no yes Cognitive scientists tell us that we are hardwired for deception--overly optimistic about outcomes. In fact, we surely wouldn't have survived without this trait. With this built-in bias as a starting point, it's no wonder that software managers and teams almost always develop poor estimates. But that doesn't mean all is lost. We must simply accept that our estimates are optimistic guesses and continually re-evaluate as we go. Linda Rising has been part of many development projects where sincere, honest people wanted to make the best estimates possible and used "scientific" approaches to make it happen--and all for naught. In many projects, because re-estimation was regarded as an admission of failure, the team spent too much time and endless meetings trying to "et it right." Offering examples from ordinary life--especially from the way people eat and drink--Linda demonstrates how hard it is for us to see our poor estimating skills and offers practical advice on living and working with the self-deception that is hardwired in all of us. http://www.computer.org/lockheed Cognitive Science 63694E3C-E8FB-45F3-B769-6E7FD9ACC0B1 Thu, 9 Feb 2012 09:00:00 -0800 LMCO SSI Webinar Series Linda demonstrates how hard it is for us to see our poor estimating skills and offers practical advice on living and working with the self-deception that is hardwired in all of us. Cognitive scientists tell us that we are hardwired for deception--overly optimistic about outcomes. In fact, we surely wouldn't have survived without this trait. With this built-in bias as a starting point, it's no wonder that software managers and teams almost always develop poor estimates. But that doesn't mean all is lost. We must simply accept that our estimates are optimistic guesses and continually re-evaluate as we go. Linda Rising has been part of many development projects where sincere, honest people wanted to make the best estimates possible and used "scientific" approaches to make it happen--and all for naught. In many projects, because re-estimation was regarded as an admission of failure, the team spent too much time and endless meetings trying to "et it right." Offering examples from ordinary life--especially from the way people eat and drink--Linda demonstrates how hard it is for us to see our poor estimating skills and offers practical advice on living and working with the self-deception that is hardwired in all of us. 57:06 Linda Rising deception, cognitive science, estimation, software management no yes Traditionally, the analysis of Ballistic Missile Defense System (BMDS) effectiveness has been limited in fidelity due to the inherent complexity of the subject. Indeed, the BMDS battle management process involves monitoring and controlling the actions of many interacting participants (e.g. radar sensors, communications networks and interceptor missiles) in a process whereby a target moves from launch through sensor detection through intercept kill assessment. Because the actions of each participant may evolve independently, the battle management process functions as a true system-of-systems (SoS). Proper SoS analysis requires architecture level engineering, dealing with component functional allocation and inter-component interaction rather than the internal workings of individual participants. Although prior work has been identified that addresses BMD effectiveness at the SoS level, each method sacrifices analysis fidelity of both process elements and individual participants to enable timely decision making. This study proposes a modeling and simulation (M&S) framework that supports architecture level analysis of the BMDS. The key innovation is the application of neural network surrogate models, which are representations of other high- or medium-fidelity M&S tools, and can be executed rapidly with negligible loss in fidelity. Surrogate models were created of a BMDS analysis tool that included multi-sensor target tracking and fusion codes. Results will show the benefit of integrating M&S to architecture level analysis. Specific examples include sensitivity of operational level metrics to formation of an integration tracking picture, and the enabling architecture level decision making. http://www.computer.org/lockheed Systems-of-Systems 52B38F7B-579A-47DF-9E05-4B3DD03E9058 Thu, 26 Jan 2012 09:00:00 -0800 LMCO SSI Webinar Series This study proposes a modeling and simulation (M&S) framework that supports architecture level analysis of the BMDS. Traditionally, the analysis of Ballistic Missile Defense System (BMDS) effectiveness has been limited in fidelity due to the inherent complexity of the subject. Indeed, the BMDS battle management process involves monitoring and controlling the actions of many interacting participants (e.g. radar sensors, communications networks and interceptor missiles) in a process whereby a target moves from launch through sensor detection through intercept kill assessment. Because the actions of each participant may evolve independently, the battle management process functions as a true system-of-systems (SoS). Proper SoS analysis requires architecture level engineering, dealing with component functional allocation and inter-component interaction rather than the internal workings of individual participants. Although prior work has been identified that addresses BMD effectiveness at the SoS level, each method sacrifices analysis fidelity of both process elements and individual participants to enable timely decision making. This study proposes a modeling and simulation (M&S) framework that supports architecture level analysis of the BMDS. The key innovation is the application of neural network surrogate models, which are representations of other high- or medium-fidelity M&S tools, and can be executed rapidly with negligible loss in fidelity. Surrogate models were created of a BMDS analysis tool that included multi-sensor target tracking and fusion codes. Results will show the benefit of integrating M&S to architecture level analysis. Specific examples include sensitivity of operational level metrics to formation of an integration tracking picture, and the enabling architecture level decision making. 59:45 Tommer Ender systems of systems, SOS, missile defense, software architecture, simulation, Ballistic Missile Defense System, BMDS, architecture level analysis no yes Congratulations. You've earned a job as a software executive. Now what? Do you know what it takes to keep it? More important, do you know what it takes to excel? After more than 10 years of working with top software executives across a full spectrum of software-intensive industries, Steve McConnell has found a method for predicting which technical executives will be successful in their organizations and which will end up looking for different positions. McConnell describes the seven crucial rules that lead software executives first to satisfactory performance and ultimately to superior performance and superior results. http://www.computer.org/lockheed Software Leadership ADBB37DD-BDEF-49E3-A059-EA86FB517C64 Thu, 12 Jan 2012 09:00:00 -0800 LMCO SSI Webinar Series Congratulations. You've earned a job as a software executive. Now what? Congratulations. You've earned a job as a software executive. Now what? Do you know what it takes to keep it? More important, do you know what it takes to excel? After more than 10 years of working with top software executives across a full spectrum of software-intensive industries, Steve McConnell has found a method for predicting which technical executives will be successful in their organizations and which will end up looking for different positions. McConnell describes the seven crucial rules that lead software executives first to satisfactory performance and ultimately to superior performance and superior results. 1:00:37 Steve McConnell software leadership, training, software executives, performance no yes The presentation gives an overview on the technology status, application and market potential of a pure copper nanoparticle-based "solder-free" (nanoCu) interconnect material with a 200-degree C processing temperature, up to 15x higher thermal & electrical conductivity and a large adjacent market with tremendeous revenue opportunities. Besides the 80,000 ton per year commercial 2D electronics packaging market, there is the solar cell market (approaching $1B) to replace the 100x more expensive silver interconnects, the very large flat panel display market (>$10B) , printable/flexible electronics (multi-billion $), 3D integration (emerging), biomedical applications (infection prevention), LED lighting (20% brighter). Due to its small particle size, low cost and low fusion temperature, the nanoCu interconnect material is a true enabling technology. http://www.computer.org/lockheed Interconnect Technology FC88318F-B077-445A-B34E-896B2095876A Thu, 8 Dec 2011 09:00:00 -0800 LMCO SSI Webinar Series The presentation gives an overview on the technology status, application and market potential of a pure copper nanoparticle-based "solder-free" (nanoCu) interconnect material. The presentation gives an overview on the technology status, application and market potential of a pure copper nanoparticle-based "solder-free" (nanoCu) interconnect material with a 200-degree C processing temperature, up to 15x higher thermal & electrical conductivity and a large adjacent market with tremendeous revenue opportunities. Besides the 80,000 ton per year commercial 2D electronics packaging market, there is the solar cell market (approaching $1B) to replace the 100x more expensive silver interconnects, the very large flat panel display market (>$10B) , printable/flexible electronics (multi-billion $), 3D integration (emerging), biomedical applications (infection prevention), LED lighting (20% brighter). Due to its small particle size, low cost and low fusion temperature, the nanoCu interconnect material is a true enabling technology. 50:43 Dragos Maciuca and Alfred A. Zinn solder-free, interconnect technology, RoHS, SAC joint, electronic assembly, reliability no yes Ensuring that systems of systems and large-scale systems behave acceptably under all conditions of use is very difficult. The nature of these systems poses verification and validation (V&V) issues that are not as critical in smaller scale and less complex systems. This talk will discuss these issues and how more traditional V&V approaches may need to be modified to deal with them adequately. http://www.computer.org/lockheed Software Engineering 07C320A2-955F-4702-AFA2-D90EC785B5E2 Thu, 17 Nov 2011 09:00:00 -0800 LMCO SSI Webinar Series This talk will discuss V&V issues and how more traditional approaches may need to be modified to deal with them adequately. Ensuring that systems of systems and large-scale systems behave acceptably under all conditions of use is very difficult. The nature of these systems poses verification and validation (V&V) issues that are not as critical in smaller scale and less complex systems. This talk will discuss these issues and how more traditional V&V approaches may need to be modified to deal with them adequately. 56:47 John Goodenough system of systems, verification and validation, V&V, large-scale systems no yes The technical debt metaphor describes situations were developers accept compromises in one dimension (e.g. maintainability) to meet an urgent demand in another dimension (e.g. delivering a release on time). These compromises incur a "debt" in the software that will demand "interest" through rework and increased maintainability cost. Identifying and managing technical debt helps in understanding which types of debt (i.e. improvement opportunities) are worth paying off and which can be left in a software system until some future date. This webinar describes state-of-the-art methods to assess and quantify existing technical debt that slows down development activities (i.e. has a high interest rate), and methods to make a more educated decision on when it is beneficial to go into debt, and when to repay existing debt (e.g. through refactoring). Techniques in this webinar identify technical debt at the detailed code level (i.e. Code Smell detection and Design Pattern Decay), and higher architecture level (i.e. Design Structure Matrix, and Architecture Violation analysis), as well as methods to estimate interest through examining the defect proneness and change proneness of software components. Join Dr. Carolyn Seaman from UMBC and Dr. Nico Zazworka from the Fraunhofer Center for Experimental Software Engineering, to learn how technical debt management can decrease the risk of unpleasant surprises and increase profitability in your project. http://www.computer.org/lockheed Software Engineering 6E96593D-F8B5-4D1F-93C6-B6B557784540 Thu, 10 Nov 2011 09:00:00 -0800 LMCO SSI Webinar Series This webinar describes state-of-the-art methods to assess and quantify existing technical debt. The technical debt metaphor describes situations were developers accept compromises in one dimension (e.g. maintainability) to meet an urgent demand in another dimension (e.g. delivering a release on time). These compromises incur a "debt" in the software that will demand "interest" through rework and increased maintainability cost. Identifying and managing technical debt helps in understanding which types of debt (i.e. improvement opportunities) are worth paying off and which can be left in a software system until some future date. This webinar describes state-of-the-art methods to assess and quantify existing technical debt that slows down development activities (i.e. has a high interest rate), and methods to make a more educated decision on when it is beneficial to go into debt, and when to repay existing debt (e.g. through refactoring). Techniques in this webinar identify technical debt at the detailed code level (i.e. Code Smell detection and Design Pattern Decay), and higher architecture level (i.e. Design Structure Matrix, and Architecture Violation analysis), as well as methods to estimate interest through examining the defect proneness and change proneness of software components. Join Dr. Carolyn Seaman from UMBC and Dr. Nico Zazworka from the Fraunhofer Center for Experimental Software Engineering, to learn how technical debt management can decrease the risk of unpleasant surprises and increase profitability in your project. 1:01:25 Carolyn Seaman and Nico Zazworka technical debt, maintainability, software development, code smell, pattern decay no yes There is only one step left in millennia-old process of automating humanity. The first and most ancient step networking, a trick that language enabled by allowing data to pass through the physical world and be shared with others. The second great step was writing, which captured networking as external memories that are no longer dependent on the life span of an individual. The third and most recent step was the externalization of action, where structured memory (software) was given the ability not just to preserve knowledge, but to use that knowledge to operate machines. The final step is to automate automation itself--that is, to create machines capable of making decisions that cannot be fully anticipate in advance. The positives and negatives of machine autonomy have been much discussed, but one of their most profound implications is this: Machines scale in ways that humans cannot. That means that truly autonomous robots accomplish feats not possible for humans alone. Amazingly, we are right now in the midst of the period in human history when this fourth step is most likely to occur. Sitting right at the center of this nexus of human history is its most critical and fragile link: Software developers. In this talk I’ll discuss why that is, and why robotics software is so challenging. Without profound increases in the effectiveness of methods used to develop, validate, adapt, port the knowledge represented by robotic software, the world of robotics risks slipping into the Hollow Shell Syndrome, in which robotic platforms continue to become faster and more perceptive, but never really progress beyond being powerful hand puppets. I’ll talk about why economic and cost drivers point to the need for what amounts to some sort of synthesis of machine intelligence with the principles of software engineering, in effect giving autonomous platforms what amounts to a suite of real-time software engineering agents that keep its explorations in check. I’ll end by talking about some of the more interesting cross-disciplinary research ideas that may in time force us to rethink the very way we build computers, let alone how to write software. http://www.computer.org/lockheed Software Engineering 9CB2F1B4-10E3-4655-9FB9-4D36928A72BB Thu, 27 Oct 2011 09:00:00 -0700 LMCO SSI Webinar Series Terry Bollinger discusses why robotics software is so challenging. There is only one step left in millennia-old process of automating humanity. The first and most ancient step networking, a trick that language enabled by allowing data to pass through the physical world and be shared with others. The second great step was writing, which captured networking as external memories that are no longer dependent on the life span of an individual. The third and most recent step was the externalization of action, where structured memory (software) was given the ability not just to preserve knowledge, but to use that knowledge to operate machines. The final step is to automate automation itself--that is, to create machines capable of making decisions that cannot be fully anticipate in advance. The positives and negatives of machine autonomy have been much discussed, but one of their most profound implications is this: Machines scale in ways that humans cannot. That means that truly autonomous robots accomplish feats not possible for humans alone. Amazingly, we are right now in the midst of the period in human history when this fourth step is most likely to occur. Sitting right at the center of this nexus of human history is its most critical and fragile link: Software developers. In this talk I’ll discuss why that is, and why robotics software is so challenging. Without profound increases in the effectiveness of methods used to develop, validate, adapt, port the knowledge represented by robotic software, the world of robotics risks slipping into the Hollow Shell Syndrome, in which robotic platforms continue to become faster and more perceptive, but never really progress beyond being powerful hand puppets. I’ll talk about why economic and cost drivers point to the need for what amounts to some sort of synthesis of machine intelligence with the principles of software engineering, in effect giving autonomous platforms what amounts to a suite of real-time software engineering agents that keep its explorations in check. I’ll end by talking about some of the more interesting cross-disciplinary research ideas that may in time force us to rethink the very way we build computers, let alone how to write software. 1:02:46 Terry Bollinger software engineering, robotics software, software developers, knowledge management, machine autonomoy, robots no yes Imagine woodcutters in a forest. They work hard and cut tree after tree to build a street. It is a huge physical effort and their foreman drives them hard to stay on schedule. He wants to cut a certain amount of trees per day and provides the workers with all they need to achieve this objective. Suddenly the client who ordered the street to be build comes back and shouts: "wrong direction". Despite all the operational efficiency of the foreman and his team, they did not manage to deliver the intended customer experience. Sounds familiar? Indeed, this is what we observe with many software products. Complex features must be developed at a low cost, but once they hit the market they won't sell as expected. Or customers demand many changes during the development process, thus reducing margins dramatically from initial targets. Requirements engineering is the systematic approach to providing direction before and during software development. It provides the means to deliver the right products or solutions at the right time for the right markets. Requirements Engineering (RE) bridges the entire life cycle and thus determines success or failure of a product or solution. This mini tutorial shows how to best use RE and master its challenges. It practically describes how to develop and write good requirements and how to manage them during the project. The presentation underlines the basic concepts and practices of RE with broad industrial experiences. Starting with a brief intro and overview to current techniques and best practices of RE, it highlights advances in RE, such as lean and agile development, product management, quality engineering, and global development. Based on industrial experiences and benchmarks from different industries Dr. Ebert will practically show how to best use RE and thus master business challenges. http://www.computer.org/lockheed Software Engineering 42693F06-C202-4CED-920A-8B10B6C00F1C Thu, 13 Oct 2011 09:00:00 -0700 LMCO SSI Webinar Series This mini tutorial shows how to best use requirements engineering (RE) and master its challenges. It describes how to develop and write good requirements and how to manage them during the project. Imagine woodcutters in a forest. They work hard and cut tree after tree to build a street. It is a huge physical effort and their foreman drives them hard to stay on schedule. He wants to cut a certain amount of trees per day and provides the workers with all they need to achieve this objective. Suddenly the client who ordered the street to be build comes back and shouts: "wrong direction". Despite all the operational efficiency of the foreman and his team, they did not manage to deliver the intended customer experience. Sounds familiar? Indeed, this is what we observe with many software products. Complex features must be developed at a low cost, but once they hit the market they won't sell as expected. Or customers demand many changes during the development process, thus reducing margins dramatically from initial targets. Requirements engineering is the systematic approach to providing direction before and during software development. It provides the means to deliver the right products or solutions at the right time for the right markets. Requirements Engineering (RE) bridges the entire life cycle and thus determines success or failure of a product or solution. This mini tutorial shows how to best use RE and master its challenges. It practically describes how to develop and write good requirements and how to manage them during the project. The presentation underlines the basic concepts and practices of RE with broad industrial experiences. Starting with a brief intro and overview to current techniques and best practices of RE, it highlights advances in RE, such as lean and agile development, product management, quality engineering, and global development. Based on industrial experiences and benchmarks from different industries Dr. Ebert will practically show how to best use RE and thus master business challenges. 57:33 Christof Ebert software engineering, requirements engineering, software development, RE, requirements no yes Virtual reality (VR) has undergone a transition in the past 15 years that has taken it from the realm of expensive toy and into that of functional technology. Revolutionary advances in the underlying VR enabling technologies (i.e., computation speed and power, graphics and image rendering technology, display systems, interface devices, immersive audio, haptics tools, tracking, intelligent agents, and authoring software) have supported development resulting in more powerful, low-cost PC-driven VR systems. Such advances in technological "prowess" and accessibility have provided the hardware platforms needed for the conduct of human research and treatment within more usable, useful and lower cost VR systems. At the same time, there has been a growing awareness of the potential value of VR by scientists and clinicians, in addition to the general public. While much of this recognition may be due to the high visibility of digital games and massive shared internet-based virtual worlds (World of Warcraft, Halo and 2nd Life, etc.), clinical research applications routinely come into the public consciousness via the popular media. Whether this can be considered as "hype" or "help" to a field that has a storied history of alternating periods of public enchantment and disregard, still remains to be seen. Regardless, growing public awareness coupled with solid scientific results delivered from VR clinical and research applications, have brought the field past the point where skeptics can be taken seriously when they characterize VR as a "fad technology". It is not 1994 anymore! When discussion of the potential for VR applications in the human clinical and research domains first emerged in the early-1990s, the technology needed to deliver on the anticipated "visions" was not in place. Consequently, during these early years, VR suffered from a somewhat imbalanced "expectation-to-delivery" ratio, as most users trying systems during that time will attest. The "real" thing never quite measured up to expectations generated by some of the initial media hype, as delivered for example in the films "The Lawnmower Man" and "Disclosure"! Yet the idea of producing simulated virtual environments that allowed for the systematic delivery of ecologically relevant stimulus events and challenges was compelling and made intuitive sense. As well, a long and rich history of encouraging findings from the aviation simulation literature lent support to the concept that testing, training and treatment in highly proceduralized VR simulation environments would be a useful direction for psychology and rehabilitation to explore. Since that time, we have seen the development of VR systems that have demonstrated added-value for addressing a variety of clinical conditions and research objectives including: fear reduction with phobic clients, stress management in cancer patients, acute pain reduction during wound care with burn patients, exposure therapy for Post Traumatic Stress Disorder, body image disturbances in patients with eating disorders, navigation and spatial training in children and adults with motor impairments, functional skill training and motor rehabilitation with patients having central nervous system dysfunction (stroke, TBI, SCI cerebral palsy, multiple sclerosis, etc.) and in the assessment (and in some cases, rehabilitation) of attention, memory, spatial skills and executive cognitive functions in both clinical and unimpaired populations. To do this, scientists have constructed virtual airplanes, skyscrapers, spiders, battlefields, social events populated with virtual humans, fantasy worlds and the mundane (but highly relevant) functional environments of the schoolroom, office, home, street and supermarket. These efforts are no small feat in light of the technological challenges, scientific climate shifts and funding hurdles that many researchers have faced during the early development of this emerging technology. This presentation will provide an overview of the many forms of Virtual Reality that have been applied across a diverse range of clinical disorders and research questions. I will start with an overview of the use of VR for Exposure Therapy for anxiety disorders, addictive behaviors and with OIF/OEF military personnel with PTSD. This will be followed by overviews of research and clinical applications of VR for cognitive assessment/rehabilitation, motor rehabilitation, pain distraction and social interaction. The social interaction overview will conclude with the detailing of an emerging project area that involves the creation of artificially intelligent virtual human "patients" for clinical training and as online healthcare support guides. http://www.computer.org/lockheed Virtual Reality Simulations CF3E4430-D448-4749-AD80-E0D6155EA69D Thu, 22 Sep 2011 09:00:00 -0700 LMCO SSI Webinar Series This presentation will provide an overview of the many forms of Virtual Reality that have been applied across a diverse range of clinical disorders and research questions. Virtual reality (VR) has undergone a transition in the past 15 years that has taken it from the realm of expensive toy and into that of functional technology. Revolutionary advances in the underlying VR enabling technologies (i.e., computation speed and power, graphics and image rendering technology, display systems, interface devices, immersive audio, haptics tools, tracking, intelligent agents, and authoring software) have supported development resulting in more powerful, low-cost PC-driven VR systems. Such advances in technological "prowess" and accessibility have provided the hardware platforms needed for the conduct of human research and treatment within more usable, useful and lower cost VR systems. At the same time, there has been a growing awareness of the potential value of VR by scientists and clinicians, in addition to the general public. While much of this recognition may be due to the high visibility of digital games and massive shared internet-based virtual worlds (World of Warcraft, Halo and 2nd Life, etc.), clinical research applications routinely come into the public consciousness via the popular media. Whether this can be considered as "hype" or "help" to a field that has a storied history of alternating periods of public enchantment and disregard, still remains to be seen. Regardless, growing public awareness coupled with solid scientific results delivered from VR clinical and research applications, have brought the field past the point where skeptics can be taken seriously when they characterize VR as a "fad technology". It is not 1994 anymore! This presentation will provide an overview of the many forms of Virtual Reality that have been applied across a diverse range of clinical disorders and research questions. I will start with an overview of the use of VR for Exposure Therapy for anxiety disorders, addictive behaviors and with OIF/OEF military personnel with PTSD. This will be followed by overviews of research and clinical applications of VR for cognitive assessment/rehabilitation, motor rehabilitation, pain distraction and social interaction. The social interaction overview will conclude with the detailing of an emerging project area that involves the creation of artificially intelligent virtual human "patients" for clinical training and as online healthcare support guides. 1:05:32 Albert "Skip" Rizzo virtual reality, simulations, haptics, intelligent agents, authoring software, immersive audio, image rendering, gaming, clinical medicine, stress management, post traumatic stress disorder, mental illness no yes The rhythm of agile software development is always to work on the next known, small batch of work. So where is the place for software architecture in this style of development? Some think that good software architecture should simply emerge. But it isn’t always prudent to let the software architecture emerge at the speed of the next iteration--especially when there is a lot of technical risk, interdependencies, and conflicting priorities. Good architecture requires ongoing attention and stewardship. This webinar presents several techniques for incorporating architectural activities into complex agile projects and explains how an agile architect’s role differs from traditional software architects. http://www.computer.org/lockheed Agile Architecture 7C772F02-23BD-4438-B3A8-874B1DBFF1F1 Thu, 8 Sep 2011 09:00:00 -0700 LMCO SSI Webinar Series This webinar presents several techniques for incorporating architectural activities into complex agile projects and explains how an agile architect’s role differs from traditional software architects. The rhythm of agile software development is always to work on the next known, small batch of work. So where is the place for software architecture in this style of development? Some think that good software architecture should simply emerge. But it isn’t always prudent to let the software architecture emerge at the speed of the next iteration--especially when there is a lot of technical risk, interdependencies, and conflicting priorities. Good architecture requires ongoing attention and stewardship. This webinar presents several techniques for incorporating architectural activities into complex agile projects and explains how an agile architect’s role differs from traditional software architects. 59:01 Rebecca Wirfs-Brock agile architecture, agile projects, software architecture, agile design, software architect no yes Test automation is an essential part of building secure software. The two most popular analysis testing are fuzzing and static analysis. In this talk I explain why automation is essential, how the two analysis techniques work, what they're good for, and where they struggle. In this Webinar, we'll consider approaches for combining techniques. Some intuitive combinations perform poorly in practice, but there is good evidence that the right hybrid approach enables significantly better security testing. http://www.computer.org/lockheed Software and Security 7BDA8C72-5E4A-4C83-9911-F7AC5A671C17 Thu, 25 Aug 2011 09:00:00 -0700 LMCO SSI Webinar Series In this talk I explain why automation is essential, how the two analysis techniques work, what they're good for, and where they struggle. Test automation is an essential part of building secure software. The two most popular analysis testing are fuzzing and static analysis. In this talk I explain why automation is essential, how the two analysis techniques work, what they're good for, and where they struggle. In this Webinar, we'll consider approaches for combining techniques. Some intuitive combinations perform poorly in practice, but there is good evidence that the right hybrid approach enables significantly better security testing. 57:15 Brian Chess gray box, vulnerability, security, fuzzy analysis, statis analysis, testing no yes Software Product Lines (SPLs) present the first successful approach to intra-organizational reuse in more than four decades of research. Companies that successfully adopted SPLs were rewarded with significant market success and numerous examples exist of companies that managed to grow with an order of magnitude due to early and innovative adoption of SPLs. The first part of the talk focuses on the ingredients of successful SPL adoption, addressing the link to the business strategy, architectural concerns, as well as process and organizational issues. After close to 20 years since the initial formalization of the SPL approach, however, the software development landscape has changed quite dramatically. Global software development, agile development processes and networked, ecosystem-centric organizational approaches have evolved over the last decade in response to a constantly increasing demand for speed of execution and response to the market. The second part discusses the new approaches that companies are adopting to evolve SPL approaches to these new realities. The talk contains numerous industrial examples from the author’s almost two decades of experience with industrial software reuse. http://www.computer.org/lockheed Software 6C7CB755-BBD2-4DF5-99AD-C1BBF19296F0 Thu, 11 Aug 2011 17:46:14 -0700 LMCO SSI Webinar Series This webinar focuses on the ingredients of successful SPL adoption, addressing the link to the business strategy, architectural concerns, as well as process and organizational issues. Software Product Lines (SPLs) present the first successful approach to intra-organizational reuse in more than four decades of research. Companies that successfully adopted SPLs were rewarded with significant market success and numerous examples exist of companies that managed to grow with an order of magnitude due to early and innovative adoption of SPLs. The first part of the talk focuses on the ingredients of successful SPL adoption, addressing the link to the business strategy, architectural concerns, as well as process and organizational issues. After close to 20 years since the initial formalization of the SPL approach, however, the software development landscape has changed quite dramatically. Global software development, agile development processes and networked, ecosystem-centric organizational approaches have evolved over the last decade in response to a constantly increasing demand for speed of execution and response to the market. The second part discusses the new approaches that companies are adopting to evolve SPL approaches to these new realities. The talk contains numerous industrial examples from the author’s almost two decades of experience with industrial software reuse. 1:01:19 Jan Bosch software product lines, SPL, business strategy, software architecture no yes There is an increasing trend towards interconnected systems of systems (SoS) that provide capabilities that are not available in a single system. One emerging approach for engineering software-intensive systems of systems is service-oriented architecture (SOA); however it is likely that future new implementation technologies will appear as SoS requirements change and become more demanding. The purpose of this webinar is to present fundamental service-oriented principles that can be used for engineering SoS regardless of the implementation technologies, aspects of service orientation that need to advance in order to support SoS engineering and some thoughts on what a service-oriented SoS engineering approach would look like. http://www.computer.org/lockheed Software F942F76A-B3D5-48D7-8540-A35D361D1DED Thu, 28 Jul 2011 00:00:00 -0700 LMCO SSI Webinar Series The purpose of this webinar is to present fundamental service-oriented principles that can be used for engineering SoS regardless of the implementation technologies. There is an increasing trend towards interconnected systems of systems (SoS) that provide capabilities that are not available in a single system. One emerging approach for engineering software-intensive systems of systems is service-oriented architecture (SOA); however it is likely that future new implementation technologies will appear as SoS requirements change and become more demanding. The purpose of this webinar is to present fundamental service-oriented principles that can be used for engineering SoS regardless of the implementation technologies, aspects of service orientation that need to advance in order to support SoS engineering and some thoughts on what a service-oriented SoS engineering approach would look like. 57:51 Grace Lewis SOA, service-oriented architecture, system of systems, SoS, software, engineering no yes Every software-intensive system is a legacy system: from the moment a line of code is written, it becomes part of that system's legacy. Systems grow through the gradual accretion of such individual contributions, but the accumulated mass has properties of its own: as Voltaire notes, no snowflake in an avalanche ever feels responsible. Legacy is an issue for long-lived systems (such as many defense systems) but for new ones as well (even Facebook has a legacy challenge). In this talk, we'll examine nine things you can do with old software, and the best practices that contribute to delivering resilient systems. http://www.computer.org/lockheed Software 04DFD7F9-42DB-423B-9A85-93287351E6C1 Thu, 14 Jul 2011 16:52:35 -0700 LMCO SSI Webinar Series In this talk, we'll examine nine things you can do with old software, and the best practices that contribute to delivering resilient systems. Every software-intensive system is a legacy system: from the moment a line of code is written, it becomes part of that system's legacy. Systems grow through the gradual accretion of such individual contributions, but the accumulated mass has properties of its own: as Voltaire notes, no snowflake in an avalanche ever feels responsible. Legacy is an issue for long-lived systems (such as many defense systems) but for new ones as well (even Facebook has a legacy challenge). In this talk, we'll examine nine things you can do with old software, and the best practices that contribute to delivering resilient systems. 59:02 Grady Booch Grady Booch, software, legacy system no yes The ever-increasing availability of Internet connectivity is redefining open-source intelligence analytics. Online social media is not only reflective of population opinions and dynamics, but may also provide public venues to actively influence others and garner support for organized movements. In fact, in some situations like the recent protests in the Middle East and North Africa, top social networking sites have been shown to report events and dissatisfaction with leadership prior to traditional news sources. On the one hand, the rapidity of information spread renders the Internet a valuable real-time source of intelligence on population behaviors and sentiment. On the other hand, this rapidity is precisely the challenge with effectively exploiting this data source. This presentation will discuss how Lockheed Martin’s software suite, called "Web Information Spread Data Operations Module" (WISDOM), is breaking new ground in online social media collection and analytics. WISDOM’s innovative algorithms are integrated with, and indeed govern, existing technologies (e.g., crawling, tagging, agents, visualizations, etc.) to provide near real-time monitoring and analytic exploitation of the Internet as a socio-cultural data source. With its suite of capabilities, WISDOM’s automated collection, processing, and analytic visualizations save the analyst time generally spent on collection so they may devote the majority of their effort toward analysis; and discover trends, sentiment shifts, and key influencers in online communities to alert the analyst to indications of unrest that may lead to instability events. http://www.computer.org/lockheed Social Media 2E6ACB8C-6D58-4CED-9811-4163BBA7B739 Thu, 23 Jun 2011 17:26:57 -0700 LMCO SSI Webinar Series This presentation will discuss how Lockheed Martin’s software suite, called "Web Information Spread Data Operations Module" (WISDOM), is breaking new ground in online social media collection and analytics. The ever-increasing availability of Internet connectivity is redefining open-source intelligence analytics. Online social media is not only reflective of population opinions and dynamics, but may also provide public venues to actively influence others and garner support for organized movements. In fact, in some situations like the recent protests in the Middle East and North Africa, top social networking sites have been shown to report events and dissatisfaction with leadership prior to traditional news sources. On the one hand, the rapidity of information spread renders the Internet a valuable real-time source of intelligence on population behaviors and sentiment. On the other hand, this rapidity is precisely the challenge with effectively exploiting this data source. This presentation will discuss how Lockheed Martin’s software suite, called "Web Information Spread Data Operations Module" (WISDOM), is breaking new ground in online social media collection and analytics. WISDOM’s innovative algorithms are integrated with, and indeed govern, existing technologies (e.g., crawling, tagging, agents, visualizations, etc.) to provide near real-time monitoring and analytic exploitation of the Internet as a socio-cultural data source. With its suite of capabilities, WISDOM’s automated collection, processing, and analytic visualizations save the analyst time generally spent on collection so they may devote the majority of their effort toward analysis; and discover trends, sentiment shifts, and key influencers in online communities to alert the analyst to indications of unrest that may lead to instability events. 57:14 Mike Baylor, Tina Chau WISDOM, Web Information Spread Data Operations Module, social media collection, analytics, crawling, tagging, agents, visualizations no yes This presentation will cover: Affordability increasingly competition-critical Need to avoid overruns Need to balance cost, schedule, performance, functionality Several improvement avenues available Concurrent vs. Sequential Engineering Total Ownership Cost Analysis Product Line Engineering and Management Value-Based Engineering Early Warning Indicators Balancing Agility and Architecting Conclusions http://www.computer.org/lockheed System Testing 68EAEB41-269B-4EF4-982C-AB8041F9968D Thu, 9 Jun 2011 17:22:43 -0700 LMCO SSI Webinar Series This webinar covers increasingly competition-critical affordability and several improvement avenues available. This presentation will cover: Affordability increasingly competition-critical Need to avoid overruns Need to balance cost, schedule, performance, functionality Several improvement avenues available Concurrent vs. Sequential Engineering Total Ownership Cost Analysis Product Line Engineering and Management Value-Based Engineering Early Warning Indicators Balancing Agility and Architecting Conclusions 57:49 Barry Boehm software, affordability, overruns, cost analysis, agility no yes Software and system testing costs industry hundreds of millions of dollars annually. In addition, testing takes multiple months, delaying time to market of key technologies. In this current economic environment, several major defense and commercial firms are embarking on using orthogonal arrays (OA) to reduce the cost of testing and time to market while ensuring that defects are not passed onto the customer. OAs provide a systematic, scientific, and repeatable approach to generating test plans that reduce testing cost by an estimated 40% while providing capability to detect more faults when compared to the typical business-as-usual practice. In addition, OAs provide distinct advantages for results analysis and defect isolation, delivering savings throughout the end-to-end Test and Evaluation (T&E) lifecycle. In this webinar we will (a) describe the fundamentals of using OAs for test planning and illustrate them with a defense systems example, (b) present results of 20 side-by-side IT and software testing pilots conducted in financial services industry, (c) describe a commercial software toolset, rdExpert (TM) Test Suite, which was utilized for OA based testing in the defense example and finance services industry pilots, and (4) provide comparison of OA based testing with other combinatorial test planning methods, viz., pairwise, n-way, and Classical Design of Experiments. http://www.computer.org/lockheed System Testing E76B6CFC-7245-42B8-99B2-8FFECB65F50F Thu, 12 May 2011 14:41:55 -0700 LMCO SSI Webinar Series This webinar describes the fundamentals of using OAs for test planning and illustrate them with a defense systems example using rdExpert Test suite. Software and system testing costs industry hundreds of millions of dollars annually. In addition, testing takes multiple months, delaying time to market of key technologies. In this current economic environment, several major defense and commercial firms are embarking on using orthogonal arrays (OA) to reduce the cost of testing and time to market while ensuring that defects are not passed onto the customer. OAs provide a systematic, scientific, and repeatable approach to generating test plans that reduce testing cost by an estimated 40% while providing capability to detect more faults when compared to the typical business-as-usual practice. In addition, OAs provide distinct advantages for results analysis and defect isolation, delivering savings throughout the end-to-end Test and Evaluation (T&E) lifecycle. In this webinar we will (a) describe the fundamentals of using OAs for test planning and illustrate them with a defense systems example, (b) present results of 20 side-by-side IT and software testing pilots conducted in financial services industry, (c) describe a commercial software toolset, rdExpert (TM) Suite, which was utilized for OA based testing in the defense example and finance services industry pilots, and (4) provide comparison of OA based testing with other combinatorial test planning methods, viz., pairwise, n-way, and Classical Design of Experiments. 59:37 Madhav S. Phadke orthogonal arrays, OA, system testing, rdExpert no yes Technical organizations tend to prefer to make decisions based on technical criteria and to engage greater economic and social issues on their own terms. To do this, they deploy a variety of barriers, including institutions, decision structures, language, and symbols. In general they use these ideas to force these issues into categories that they can control and answer in a technical framework. At times, these barriers can be breached by the public. Outside institutions can force technical organizations to make decisions or even alter the decision making process to work with non-technical categories or processes. Often, this kind of breaching occurs when the public institutions perceive that the technical institution has not behaving in a way that they believe to be responsible. The technical institution may may be taking too long to make a decision or may be making decisions that do not appear to be sound. However, technical institutions can find themselves in circumstances when they are behaving responsibly and yet are caught in forces beyond their control. This webinar develops the basic ideas of technical institutions and technical autonomy. It shows technical institutions maintain their independence and how they can lose that independence. The talk will be illustrated by a number of examples, including the computerization of the automobile in the 1970s. http://www.computer.org/lockheed Image Generation 81ADAAEC-8FF8-46D8-97ED-C5BAFA76F1BD Thu, 28 Apr 2011 10:20:24 -0700 LMCO SSI Webinar Series This webinar develops the basic ideas of technical institutions and technical autonomy. It shows technical institutions maintain their independence and how they can lose that independence. Technical organizations tend to prefer to make decisions based on technical criteria and to engage greater economic and social issues on their own terms. To do this, they deploy a variety of barriers, including institutions, decision structures, language, and symbols. In general they use these ideas to force these issues into categories that they can control and answer in a technical framework. At times, these barriers can be breached by the public. Outside institutions can force technical organizations to make decisions or even alter the decision making process to work with non-technical categories or processes. Often, this kind of breaching occurs when the public institutions perceive that the technical institution has not behaving in a way that they believe to be responsible. The technical institution may may be taking too long to make a decision or may be making decisions that do not appear to be sound. However, technical institutions can find themselves in circumstances when they are behaving responsibly and yet are caught in forces beyond their control. This webinar develops the basic ideas of technical institutions and technical autonomy. It shows technical institutions maintain their independence and how they can lose that independence. The talk will be illustrated by a number of examples, including the computerization of the automobile in the 1970s. 1:02:16 David Alan Grier technical institutions, autonomy, independence no yes The purpose of testing after development is to find defects. One purpose of Test-Driven Development is to prevent defects. TDD is a disciplined (and addictive) approach to developing software that drives out many of the bugs that sneak into the product during development. Production code and test code are developed in a tight feedback loop, with tests written just in time to confirm the behavior of the production code. This webinar will describe the problems that TDD is designed to prevent, and how it accomplishes it. TDD has been applied to many application development problems in virtually every programming language over its ten year history. One of the most challenging environments for TDD is the development of embedded software. This webinar will describe the steps of TDD and provide an example of applying TDD to embedded C that programmers from many disciplines will relate to. http://www.computer.org/lockheed Image Generation DB468056-11DD-43E9-AB50-FB71D5711A46 Thu, 14 Apr 2011 10:18:24 -0700 LMCO SSI Webinar Series This webinar will describe the steps of TDD and provide an example of applying TDD to embedded C that programmers from many disciplines will relate to. The purpose of testing after development is to find defects. One purpose of Test-Driven Development is to prevent defects. TDD is a disciplined (and addictive) approach to developing software that drives out many of the bugs that sneak into the product during development. Production code and test code are developed in a tight feedback loop, with tests written just in time to confirm the behavior of the production code. This webinar will describe the problems that TDD is designed to prevent, and how it accomplishes it. TDD has been applied to many application development problems in virtually every programming language over its ten year history. One of the most challenging environments for TDD is the development of embedded software. This webinar will describe the steps of TDD and provide an example of applying TDD to embedded C that programmers from many disciplines will relate to. 1:02:16 James Grenning test-driven development, TDD, defects, embedded C no yes The ever increasing availability of computational, rendering, and network bandwidth is redefining every aspect of our life from getting 1990s workstation class computational and graphics power, connected to the internet everywhere, mobile, and with an 8 hours battery life called your Cell Phone, tablet, or laptop.These changes are disruptive to the world markets and are redefine our expectations on a quarterly basis. However, there is this niche part of the world, called 60Hz image generation,that instead of making disruptive and quantum leaps with the changes of technology have evolved basically the same software and concepts since the early 1970s SimNet devices. This presentation will discuss how a disruptive image generation technology called "Dynamic Construction" is breaking new ground in the image generation arena by starting with a clean piece of paper and no historical assumptions about formats, rendering, and where work has always been done. The impact of this clean piece of paper design will be discussed and how starting over after 40 years of image generator product evolution has implications in simplifying every aspect of image generation including deployment, updating, data preparation, data formats, and achieving correlation. At the same time transforming how the image generation community define correlation, reuse, and real-time in the future while at the same time developing new product concepts only just dreamed about today. http://www.computer.org/lockheed Image Generation 38D9BAC0-BDD2-4857-A64A-52D8EFA7CF23 Thu, 24 Mar 2011 11:06:25 -0700 LMCO SSI Webinar Series This presentation will discuss how a disruptive image generation technology called "Dynamic Construction" is breaking new ground in the image generation arena. The ever increasing availability of computational, rendering, and network bandwidth is redefining every aspect of our life from getting 1990s workstation class computational and graphics power, connected to the internet everywhere, mobile, and with an 8 hours battery life called your Cell Phone, tablet, or laptop.These changes are disruptive to the world markets and are redefine our expectations on a quarterly basis. However, there is this niche part of the world, called 60Hz image generation,that instead of making disruptive and quantum leaps with the changes of technology have evolved basically the same software and concepts since the early 1970s SimNet devices. This presentation will discuss how a disruptive image generation technology called "Dynamic Construction" is breaking new ground in the image generation arena by starting with a clean piece of paper and no historical assumptions about formats, rendering, and where work has always been done. The impact of this clean piece of paper design will be discussed and how starting over after 40 years of image generator product evolution has implications in simplifying every aspect of image generation including deployment, updating, data preparation, data formats, and achieving correlation. At the same time transforming how the image generation community define correlation, reuse, and real-time in the future while at the same time developing new product concepts only just dreamed about today. 1:02:16 Aaron Hutchinson bandwidth, computational science, rendering, networks, image generation, product evolution, data preparation, correlation no yes A program is easier to develop and maintain if it is structured around the concerns of the business. This structuring is sometimes called architecture. There are two main structures that stand out in software design: the form of the business domain, and the form of the business behaviors offered by the software. The object paradigm is often held up as a design approach that optimizes the match between the business world and programming world, but while it does well to capture the domain structure, it breaks down business behavior into methods that make it difficult to reason about end-to-end behavior of any scenario. Polymorphism adds to the confusion, and makes it almost impossible to understand program behavior from the source code. This talk describes a new paradigm called Data, Context and Interaction--DCI. DCI separates the source code for the system behavior from the source code for its domain structure so that the programmer can reason about both during design and implementation. At run time, these two perspectives are brought back together into objects that match the end user mental model, which fulfills the initial purpose of the object paradigm. DCI leads to programs that better capture the business in the code, and which are easier to reason about than their OO counterparts. DCI gives full first-class standing to program behavior. http://www.computer.org/lockheed DCI Architecture 00173C6C-8AD3-4BA0-887D-E31144F5DEB2 Thu, 10 Mar 2011 14:18:41 -0700 LMCO SSI Webinar Series This talk describes a new paradigm called Data, Context and Interaction--DCI. A program is easier to develop and maintain if it is structured around the concerns of the business. This structuring is sometimes called architecture. There are two main structures that stand out in software design: the form of the business domain, and the form of the business behaviors offered by the software. The object paradigm is often held up as a design approach that optimizes the match between the business world and programming world, but while it does well to capture the domain structure, it breaks down business behavior into methods that make it difficult to reason about end-to-end behavior of any scenario. Polymorphism adds to the confusion, and makes it almost impossible to understand program behavior from the source code. This talk describes a new paradigm called Data, Context and Interaction--DCI. DCI separates the source code for the system behavior from the source code for its domain structure so that the programmer can reason about both during design and implementation. At run time, these two perspectives are brought back together into objects that match the end user mental model, which fulfills the initial purpose of the object paradigm. DCI leads to programs that better capture the business in the code, and which are easier to reason about than their OO counterparts. DCI gives full first-class standing to program behavior. 1:02:16 Jim ("Cope") Coplien DCI, Data, Context and Interaction, system behavior, system architecture, software design no yes This presentation deals with the relationship between literate human beings and literal machines as it pertains to the notion of knowledge. Recent emphasis Knowledge Management brings this interesting paradox to light. The introduction provides a working distinction between human knowledge and machine borne information. An initial analysis of observable trends highlights how networked system federations reinforce growing globalization and non-linear relationships. Given this backdrop, the paper then explores the mandate to move away from static architectural constructs towards a non-deterministic, non-reductionism, multi-disciplinary approach to systems design. Finally, to resolve the apparent paradox between literate, non-deterministic human beings and literal seemingly deterministic machines, the presentation offers the operational concept of "living ontology" to provide a pragmatic means of bridging the gap. http://www.computer.org/lockheed Systems Engineering 9D828B11-1CFB-4B87-97DE-34A3AF3762DF Thu, 24 Feb 2011 10:21:49 -0800 LMCO SSI Webinar Series This presentation deals with the relationship between literate human beings and literal machines as it pertains to the notion of knowledge. This presentation deals with the relationship between literate human beings and literal machines as it pertains to the notion of knowledge. Recent emphasis Knowledge Management brings this interesting paradox to light. The introduction provides a working distinction between human knowledge and machine borne information. An initial analysis of observable trends highlights how networked system federations reinforce growing globalization and non-linear relationships. Given this backdrop, the paper then explores the mandate to move away from static architectural constructs towards a non-deterministic, non-reductionism, multi-disciplinary approach to systems design. Finally, to resolve the apparent paradox between literate, non-deterministic human beings and literal seemingly deterministic machines, the presentation offers the operational concept of “living ontology” to provide a pragmatic means of bridging the gap. 1:02:16 George F. Hurlburt systems engineering, knowledge management, systems design, living ontology no yes Test and evaluation are critically related in every engineering endeavor. Many who frequently perform testing are unaware that how one tests the various combinations will determine how easy or how hard it will be to evaluate the results of testing. This presentation will provide an overview of the best techniques for multi-variate testing. Multi-Variate Testing (MVT) is known by different names. Combinatorial Test (CT) and Design of Experiments (DOE), really a subset of CT, are some of the more commonly used names. We will briefly touch on full and fractional factorial designs, along with response surface designs, to illustrate some of the important properties of a test design. Then we will move into the higher dimension spaces where Latin Hypercube Designs are extremely useful for fractionating or reducing the number of test cases when many variables are being tested. A special combinatorial test design method called High Throughput Testing (HTT) will be demonstrated. This technique is very valuable in software testing because it is impossible to test every path through the software. It will be shown to provide great test coverage with a significantly reduced number of tests, especially in the all pairs test strategy of HTT. HTT is useful in any environment where it is necessary to show that the combinations of many variables, each with perhaps many different levels, work together. This includes developmental and operational testing, systems level testing, functional testing, unit testing, interoperability testing, and regression testing. This webinar will address locating the problem or combination(s) that may be the failure mode for failed test cases and also show how to design follow-on tests to isolate the failure mode(s). All engineers need these concepts and tools in their repertoire of testing techniques, because it will enhance the effectiveness and efficiency of testing. http://www.computer.org/lockheed Test Design Methodology C96D51BF-FBA1-4D35-8385-B2CCF2B3B9BD Thu, 10 Feb 2011 10:19:44 -0800 LMCO SSI Webinar Series This presentation will provide an overview of the best techniques for multi-variate testing. Multi-Variate Testing (MVT) is known by different names. Test and evaluation are critically related in every engineering endeavor. Many who frequently perform testing are unaware that how one tests the various combinations will determine how easy or how hard it will be to evaluate the results of testing. This presentation will provide an overview of the best techniques for multi-variate testing. Multi-Variate Testing (MVT) is known by different names. Combinatorial Test (CT) and Design of Experiments (DOE), really a subset of CT, are some of the more commonly used names. We will briefly touch on full and fractional factorial designs, along with response surface designs, to illustrate some of the important properties of a test design. Then we will move into the higher dimension spaces where Latin Hypercube Designs are extremely useful for fractionating or reducing the number of test cases when many variables are being tested. A special combinatorial test design method called High Throughput Testing (HTT) will be demonstrated. This technique is very valuable in software testing because it is impossible to test every path through the software. It will be shown to provide great test coverage with a significantly reduced number of tests, especially in the all pairs test strategy of HTT. HTT is useful in any environment where it is necessary to show that the combinations of many variables, each with perhaps many different levels, work together. This includes developmental and operational testing, systems level testing, functional testing, unit testing, interoperability testing, and regression testing. This webinar will address locating the problem or combination(s) that may be the failure mode for failed test cases and also show how to design follow-on tests to isolate the failure mode(s). All engineers need these concepts and tools in their repertoire of testing techniques, because it will enhance the effectiveness and efficiency of testing. 1:02:16 Mark J. Kiemele Multi-Variate Testing, MVT, combinatorial test, CT, Design of Experiments, DOE, High Throughput Testing, HTT no yes At the beginning of a project we are always under pressure to answer questions like: how big is this? how long will it take? how much will it cost? how valuable will it be? - all this before we know what "it" is. These questions and how to answer them are the focus of this webinar with Suzanne Robertson, joint originator of the Volere requirements techniques and a principal and founder of The Atlantic Systems Guild. Suzanne will describe a strategy for defining the scope of the requirements work early in the life of a project. This scope provides consistent, countable components as input to making early estimates of size and complexity. The unambiguous definition of scope means that we have a commonly understood starting point from which we can explore and trace the details. When changes happen during the project we can precisely assess how the change affects the scope and adjust estimates accordingly. In other words we can manage the changes because we have consistent measurements for what we are changing from and to. These early countables also provide the basis for assessing customer value and doing early and progressive prioritisation. This increased ability to respond to change and to provide customer value expands the potential for agility. Key items in this presentation: * countable components * early estimates of size and complexity * assessing customer value * progressive prioritisation http://www.computer.org/lockheed Requirements A5C258F5-2859-4849-9CFC-0C6177229BC8 Thu, 27 Jan 2011 10:16:10 -0800 LMCO SSI Webinar Series Suzanne Robertson will describe a strategy for defining the scope of the requirements work early in the life of a project. At the beginning of a project we are always under pressure to answer questions like: how big is this? how long will it take? how much will it cost? how valuable will it be? -- all this before we know what "it" is. These questions and how to answer them are the focus of this webinar with Suzanne Robertson, joint originator of the Volere requirements techniques and a principal and founder of The Atlantic Systems Guild. Suzanne will describe a strategy for defining the scope of the requirements work early in the life of a project. This scope provides consistent, countable components as input to making early estimates of size and complexity. The unambiguous definition of scope means that we have a commonly understood starting point from which we can explore and trace the details. When changes happen during the project we can precisely assess how the change affects the scope and adjust estimates accordingly. In other words we can manage the changes because we have consistent measurements for what we are changing from and to. These early countables also provide the basis for assessing customer value and doing early and progressive prioritisation. This increased ability to respond to change and to provide customer value expands the potential for agility. Key items in this presentation: * countable components * early estimates of size and complexity * assessing customer value * progressive prioritisation 1:02:16 Suzanne Robertson project management, Volere requirements, prioritization no yes Competence in systems thinking is implicitly assumed among the population of engineers and managers-- in fact, most technical people claim to be systems thinkers. But this competence is not as prevalent as these assertions might lead one to assume. Controlled experiments show that systems thinking performance, even among highly educated people, is poor. This presentation provides a set of systems thinking competencies and demonstrates how these are not as common as advertised. We also discuss how these competencies can be measured. http://www.computer.org/lockheed What Every Engineer Should Know About Systems Thinking 7823C7DE-4DF2-4347-AAD9-A01A584A7CEE Thu, 13 Jan 2011 10:13:34 -0800 LMCO SSI Webinar Series This presentation provides a set of systems thinking competencies and demonstrates how these are not as common as advertised. We also discuss how these competencies can be measured. Competence in systems thinking is implicitly assumed among the population of engineers and managers - in fact, most technical people claim to be systems thinkers. But this competence is not as prevalent as these assertions might lead one to assume. Controlled experiments show that systems thinking performance, even among highly educated people, is poor. This presentation provides a set of systems thinking competencies and demonstrates how these are not as common as advertised. We also discuss how these competencies can be measured. The main thesis is that systems thinking is not a natural act because (1) evolution has favored mechanisms tuned to dealing with immediate surface features of problems and (2) the Western education system tends to emphasize reductionist approaches. We discuss the implications of the current state and provide recommendations for closing the gap between the demand and supply of systems thinking through the use of systems thinking flight simulators. Finally, key take-aways are provided for the application of systems thinking across a variety of scenarios. 1:02:16 Dr. Ricardo Valerdi systems thinking, Western education, competencies no yes CAPT Dylan Schmorrow, Acting Director of Human Performance, Training and BioSystems for the Director of Defense Research and Engineering, will present on research and development in the area of human social culture behavior as it applies to national defense. CAPT Schmorrow directs the OSD Human Social Culture Behavior (HSCB) Modeling Program, which sponsors applied research and technology development grounded in the emerging field of computational social science. Operational forces have begun to incorporate social science methodologies into planning, and there are programs that have implemented social science methodologies and advising on a large scale within the military services, primarily the brigade staff. In the webinar CAPT Schmorrow will discuss methods, models, technologies and analysis within the DoD, Interagency, and Allied partner social-cultural domains, sketch a vision for success in the socio-cultural domain, and review upcoming initiatives and programs of interest to the Lockheed and IEEE communities. http://www.computer.org/lockheed Human Behavior Modeling F6BEED83-DA5E-47D9-850E-2B80086E2A08 Thu, 16 Dec 2010 10:00:22 -0800 LMCO SSI Webinar Series CAPT Dylan Schmorrow will present on research and development in the area of human social culture behavior as it applies to national defense. CAPT Dylan Schmorrow, Acting Director of Human Performance, Training and BioSystems for the Director of Defense Research and Engineering, will present on research and development in the area of human social culture behavior as it applies to national defense. CAPT Schmorrow directs the OSD Human Social Culture Behavior (HSCB) Modeling Program, which sponsors applied research and technology development grounded in the emerging field of computational social science. Operational forces have begun to incorporate social science methodologies into planning, and there are programs that have implemented social science methodologies and advising on a large scale within the military services, primarily the brigade staff. In the webinar CAPT Schmorrow will discuss methods, models, technologies and analysis within the DoD, Interagency, and Allied partner social-cultural domains, sketch a vision for success in the socio-cultural domain, and review upcoming initiatives and programs of interest to the Lockheed and IEEE communities. 1:02:16 Dylan Schmorrow, Ph.D., Captain, Medical Service Corps, US Navy social culture, social science, national defense, OSD Human Social Culture Behavior, HSCB no yes Surgery is a tradition-bound field, but societal pressures and disruptive innovations in technology are creating a rapidly changing landscape for surgeons and healthcare systems. In this presentation, Dr. Wright will discuss new innovations that will transform surgery in the near and long term, including integration of information technology into the operating room, surgical robotics, and the latest developments in minimally invasive surgery such as single incision laparoscopy. Dr. Wright will also explore changes in the healthcare environment that are impacting delivery of surgical care, including the recent national emphasis on prevention of medical errors - which contribute to up to 100,000 lives lost every year in this country. The surgeon of the future will need to keep pace with this rapid change. Safe and effective introduction of new technology will require new approaches to continuing education and certification of physicians. Dr. Wright is a leading researcher in surgical education and will discuss how new innovations in surgical simulation will affect training of surgeons and will also lead to a new mandate for surgical warmup and patient-specific rehearsal of difficult procedures. http://www.computer.org/lockheed Future of Surgery 321FC7A1-248A-4126-A9D1-595775F5E9E9 Thu, 9 Dec 2010 09:56:59 -0800 LMCO SSI Webinar Series In this presentation, Dr. Wright will discuss new innovations that will transform surgery in the near and long term, including integration of information technology into the operating room. Surgery is a tradition-bound field, but societal pressures and disruptive innovations in technology are creating a rapidly changing landscape for surgeons and healthcare systems. In this presentation, Dr. Wright will discuss new innovations that will transform surgery in the near and long term, including integration of information technology into the operating room, surgical robotics, and the latest developments in minimally invasive surgery such as single incision laparoscopy. Dr. Wright will also explore changes in the healthcare environment that are impacting delivery of surgical care, including the recent national emphasis on prevention of medical errors - which contribute to up to 100,000 lives lost every year in this country. The surgeon of the future will need to keep pace with this rapid change. Safe and effective introduction of new technology will require new approaches to continuing education and certification of physicians. Dr. Wright is a leading researcher in surgical education and will discuss how new innovations in surgical simulation will affect training of surgeons and will also lead to a new mandate for surgical warmup and patient-specific rehearsal of difficult procedures. 1:02:16 Dr. Andrew S. Wright surgery, innovation, technology, healthcare systems, laparoscopy, surgical robotics no yes The architecture of a software system defines its primary structural and behavioural organization. A well designed and clearly documented architecture is a crucial pre-requisite for the successful implementation of a software system as well as for its subsequent evolution. In this talk, we examine how the new generation of model-based software engineering (MBSE) methods and technologies can be exploited to facilitate the specification and enforcement of software architectures. At the core of MBSE is the use of higher levels of abstraction and greater use of automation compared to more traditional development approaches. http://www.computer.org/lockheed Software Architecture 4E74DB67-A69D-4F3E-8518-F105B0E7D8E9 Thu, 11 Nov 2010 09:51:07 -0800 LMCO SSI Webinar Series In this talk, we examine how the new generation of model-based software engineering (MBSE) methods and technologies can be exploited to facilitate the specification and enforcement of software architectures. The architecture of a software system defines its primary structural and behavioural organization. A well designed and clearly documented architecture is a crucial pre-requisite for the successful implementation of a software system as well as for its subsequent evolution. In this talk, we examine how the new generation of model-based software engineering (MBSE) methods and technologies can be exploited to facilitate the specification and enforcement of software architectures. At the core of MBSE is the use of higher levels of abstraction and greater use of automation compared to more traditional development approaches. The talk briefly introduces to the concept of software architecture and related technical issues and challenges. Next, we examine some of the key features of MBSE, explaining why it is such a promising approach to software development. Finally, we bring the two together and demonstrate how common architectural patterns can be expressed using the industry standard UML 2 modeling language. We also explain how MBSE can be used to eliminate the nefarious and serious problem of "architectural decay". 1:02:16 Bran Selic architecture, software system, structural and behavioural organization, MPSE, architectural decay no yes The average project overruns its planned budget and schedule by 50-80 percent. In practice, little work is done that could truly be called "estimation." Many projects are scheduled using a combination of legitimate business targets and liberal doses of wishful thinking. In this talk, award-winning author Steve McConnell presents 10 of the worst ways estimates go wrong, and presents time-tested rules of thumb for dramatically improving estimation accuracy. http://www.computer.org/lockheed Innovation http://media.computer.org/sponsored/podcast/lmco/lmco-048-p.mp4 Thu, 14 Oct 2010 13:21:05 -0700 LMCO SSI Webinar Series The average project overruns its planned budget and schedule by 50-80 percent. In practice, little work is done that could truly be called "estimation. The average project overruns its planned budget and schedule by 50-80 percent. In practice, little work is done that could truly be called "estimation." Many projects are scheduled using a combination of legitimate business targets and liberal doses of wishful thinking. In this talk, award-winning author Steve McConnell presents 10 of the worst ways estimates go wrong, and presents time-tested rules of thumb for dramatically improving estimation accuracy. 1:02:16 Steve McConnell project, estimation, Steve McConnell, accuracy no yes What happens when science fiction becomes battlefield reality? An amazing revolution is taking place on the battlefield, starting to change not just how wars are fought, but also the politics, economics, laws, and ethics that surround war itself. This upheaval is already afoot -- remote-controlled planes take out terrorists in Afghanistan and Pakistan, while the number of unmanned systems on the ground has gone from zero to 12,000 over the last five years. Singer’s work meets all the various players in this strange new world of war: odd-ball roboticists working in latter-day “skunk works” in the midst of suburbia; science fiction authors quietly advising the military; Air Force pilots flying combat mission from their office cubicles outside Las Vegas; the Iraqi insurgents who are their targets; journalists in the US and Middle East trying to figure out just how to cover robots at war; and human rights activists wrestling with what is right and wrong in a world where our wars are increasingly being handed over to machines. http://www.computer.org/lockheed Innovation http://media.computer.org/sponsored/podcast/lmco/lmco-047-p.mp4 Thu, 23 Sep 2010 09:28:20 -0700 LMCO SSI Webinar Series What happens when science fiction becomes battlefield reality? An amazing revolution is taking place on the battlefield, starting to change not just how wars are fought, but also the politics, economics, laws, and ethics that surround war itself. This upheaval is already afoot -- remote-controlled planes take out terrorists in Afghanistan and Pakistan, while the number of unmanned systems on the ground has gone from zero to 12,000 over the last five years. Singer’s work meets all the various players in this strange new world of war: odd-ball roboticists working in latter-day “skunk works” in the midst of suburbia; science fiction authors quietly advising the military; Air Force pilots flying combat mission from their office cubicles outside Las Vegas; the Iraqi insurgents who are their targets; journalists in the US and Middle East trying to figure out just how to cover robots at war; and human rights activists wrestling with what is right and wrong in a world where our wars are increasingly being handed over to machines. 1:02:16 Dr. Peter Warren Singer training, immersive virtual realities, virtual world no yes Immersive Virtual Worlds are increasingly popular in this current age of tightened purse strings and limited overhead budgets. Training and collaboration are no longer dependent on geography, as immersive virtual realities bring people together from their desktops. Join us for a webinar to learn about overcoming the challenges of expanding virtual world capabilities. This discussion will address technical issues such as the authenticity of graphics, as well as non-technical challenges such as perceptions within the user community. Respected virtual reality expert Ken Kisiel of Lockheed Martin will advise on the elements of success and how to avoid pitfalls as you navigate virtual worlds in the defense community http://www.computer.org/lockheed Innovation http://media.computer.org/sponsored/podcast/lmco/lmco-046-p.mp4 Thu, 16 Sep 2010 09:25:11 -0700 LMCO SSI Webinar Series Immersive Virtual Worlds are increasingly popular in this current age of tightened purse strings and limited overhead budgets. Training and collaboration are no longer dependent on geography, as immersive virtual realities bring people together from their desktops. Join us for a webinar to learn about overcoming the challenges of expanding virtual world capabilities. This discussion will address technical issues such as the authenticity of graphics, as well as non-technical challenges such as perceptions within the user community. Respected virtual reality expert Ken Kisiel of Lockheed Martin will advise on the elements of success and how to avoid pitfalls as you navigate virtual worlds in the defense community 1:02:16 Kenneth W. Kisiel, Richard Boyd training, immersive virtual realities, virtual world no yes The trick to affordable software architecture is to be application independent. A successful architecture (as opposed to a shambles) must appear to have been constructed by a single mind, even though we know that many minds are involved in the construction of an application of any size. An application-independent architecture, however, is independent of the size of the application (hence the name!), which makes it much more affordable, especially for large systems. http://www.computer.org/lockheed Innovation http://media.computer.org/sponsored/podcast/lmco/lmco-045-p.mp4 Thu, 9 Sep 2010 09:17:59 -0700 LMCO SSI Webinar Series The trick to affordable software architecture is to be application independent. A successful architecture (as opposed to a shambles) must appear to have been constructed by a single mind, even though we know that many minds are involved in the construction of an application of any size. An application-independent architecture, however, is independent of the size of the application (hence the name!), which makes it much more affordable, especially for large systems. 1:02:16 Josh Wolfe Forbes, Emerging Technology Report, no yes The Forbes / Wolfe Emerging Technology Report features interviews with CEOs, CTOs, technologists and innovators from top technology companies around the world. Based on his own experiences and the things he has learned while interviewing many of these brilliant individuals, Josh will share his insights on where today’s technology leaders see the world moving and the trends that they believe will shape our future.” http://www.computer.org/lockheed Innovation http://media.computer.org/sponsored/podcast/lmco/lmco-044-p.mp4 Thu, 26 Aug 2010 09:17:59 -0700 LMCO SSI Webinar Series The Forbes / Wolfe Emerging Technology Report features interviews with CEOs, CTOs, technologists and innovators from top technology companies around the world. As Co-Founder and Managing Partner of venture capital firm Lux Capital and the editor of the Forbes / Wolfe Emerging Technology Report, Josh Wolfe interviews many of the leading minds in the world of emerging technologies. In this webinar, Josh will discuss some of the most exciting innovation and technology trends that he sees today, from nanotechnology and nuclear power to solar and cleantech. Beyond just discussing the technologies themselves, Josh will provide perspective on the future of these trends from a business standpoint and how they are affecting Wall Street and the investor community. The Forbes / Wolfe Emerging Technology Report features interviews with CEOs, CTOs, technologists and innovators from top technology companies around the world. Based on his own experiences and the things he has learned while interviewing many of these brilliant individuals, Josh will share his insights on where today’s technology leaders see the world moving and the trends that they believe will shape our future. 1:02:16 Josh Wolfe Forbes, Emerging Technology Report, no yes This talk introduces the a BAO framework tailored to SSD organization improvement. http://www.computer.org/lockheed Innovation http://media.computer.org/sponsored/podcast/lmco/lmco-043-p.mp4 Thu, 12 Aug 2010 09:12:40 -0700 LMCO SSI Webinar Series This talk introduces the a BAO framework tailored to SSD organization improvement. With the current capability of business to collect and analyze process execution data, business analytics and optimization (BAO) is increasing is a means for competitive advantage. BAO is generally applied to organizations that carry out repetitive business processes such manufacturing, supply chain management, financial services, retail operations, etc. The same BAO patterns apply to software and system organizations, but the analytics are different. 1:02:16 Dr. Murray Cantor business analytics and optimization, software and system organizations, BAO framework no yes Dr Kilcullen’s seminar will examine three major concepts. http://www.computer.org/lockheed Innovation http://media.computer.org/sponsored/podcast/lmco/lmco-042-p.mp4 Thu, 22 Jul 2010 12:24:57 -0700 LMCO SSI Webinar Series Dr Kilcullen’s seminar will examine three major concepts. First, he will discuss the large-n perspective on counterinsurgency, drawing on the 386 examples of counterinsurgency since 1815 and the broader, millennia-old practices of countering internal unrest, used by governments and states from the ancient to the modern world. Second, he will look at the intellectual content of the modern, Western, variant of Counterinsurgency, in the specific form that was invented in the United States in 1958 and subsequently applied in conflicts from Vietnam to Iraq and Afghanistan. Third, he will look at the implications of counterinsurgency for the United States, for the U.S. military and other agencies, and for Lockheed Martin. 1:02:16 Dr. David Kilcullen strategic disciplines, Discovery Driven Growth, strict discipline no yes It is imposible to comprehensively test anything but very small fragments of code. However, not testing everything in a program means there's a non-zero probability that there are defects in what was not tested. http://www.computer.org/lockheed Innovation http://media.computer.org/sponsored/podcast/lmco/lmco-041-p.mp4 Thu, 8 Jul 2010 12:23:24 -0700 LMCO SSI Webinar Series It is imposible to comprehensively test anything but very small fragments of code. However, not testing everything in a program means there's a non-zero probability that there are defects in what was not tested. Risk-based testing gives an organization a systematic way of deciding what to test and, more importantly, what not to test. This webinar presents the basics of risk-based testing: * What is risk-based testing? * Why is risk-based testing an important approach? 1:02:16 Steve Tockey strategic disciplines, Discovery Driven Growth, strict discipline no yes Through consumer electronics and personal computing technologies, we have come to expect device and data interoperability and an ecosystem of innovative products that leverage open standards and marketplace competition to promote access to technology and services. http://www.computer.org/lockheed Innovation http://media.computer.org/sponsored/podcast/lmco/lmco-040-p.mp4 Thu, 24 Jun 2010 12:22:06 -0700 LMCO SSI Webinar Series Through consumer electronics and personal computing technologies, we have come to expect device and data interoperability and an ecosystem of innovative products. However, medical devices – essential for the practice of modern medicine – have traditionally been designed to operate independently. With the increasing complexity of the healthcare environment, stand-alone, proprietary devices and systems no longer provide an acceptable solution. Medical devices and systems must easily integrate with other vendors’ equipment, software, and systems in order to improve healthcare quality, reduce healthcare costs, and provide more comprehensive and secure management of health information. The absence of an intranet-like ecosystem for interconnecting medical devices and clinical information systems is a fundamental impediment to realizing the national vision of using comprehensive, accurate, electronic medical records and health IT systems to improve the quality and efficiency of healthcare. Standards-based integration of devices and IT systems in clinical environments will permit mixed-vendor (“heterogeneous”) data transfer, comprehensive secure data acquisition, and safety-enhancing capabilities such as safety interlocks and closed-loop device control. These improvements in workflow will reduce medical errors and healthcare costs to the benefit of patients throughout the continuum of care – from the home, to out-of-hospital transport, and to clinical areas as diverse as the OR, ICU, and general hospital ward. This functionality has been recognized by the Health Information Technology Standards Panel as an important part of the roadmap for common device connectivity requirements, and is the subject of a new ASTM standard on the "Integrated Clinical Environment" (ICE). 1:02:16 Julian M. Goldman, MD strategic disciplines, Discovery Driven Growth, strict discipline no yes Imagine, a soldier preparing to traverse new territory, apprehensive of the unknown terrain or an engineer preparing to study the wind patterns to optimize the location for a new wind farm. http://www.computer.org/lockheed Innovation http://media.computer.org/sponsored/podcast/lmco/lmco-039-p.mp4 Thu, 17 Jun 2010 12:20:13 -0700 LMCO SSI Webinar Series Imagine, a soldier preparing to traverse new territory, apprehensive of the unknown terrain or an engineer preparing to study the wind patterns to optimize the location for a new wind farm. Both situations have something in common… each would benefit from the leading edge technology, Laser Detection And Ranging (Ladar). Ladar is a technology that measures the properties of scattered light, typically in the ultraviolet, visible, and near infrared ranges, to determine information such as range, speed, rotation, and chemical composition. In this webinar, Dr. Sammy Henderson, a highly-respected expert from Lockheed Martin will discuss chemicals and atmospheric applications for Ladar and Dr. Paul McManamon, an esteemed industry leader will focus on applications for target identification and detection. 1:02:16 Dr. Paul McManamon / Dr. Sammy Henderson strategic disciplines, Discovery Driven Growth, strict discipline no yes Developing software for distributed computing applications that effectively utilize concurrency over high-speed, low-speed, and mobile networks is hard; developing high quality and affordable reusable distributed applications is even harder. http://www.computer.org/lockheed Innovation http://media.computer.org/sponsored/podcast/lmco/lmco-038-p.mp4 Thu, 10 Jun 2010 12:18:42 -0700 LMCO SSI Webinar Series Developing software for distributed computing applications that effectively utilize concurrency over high-speed, low-speed, and mobile networks is hard; developing high quality and affordable reusable distributed applications is even harder. Many patterns in the software literature focus on distributed computing. Until recently, however, there has been no holistic view of distributed computing that emphasizes how groups of patterns complete and complement each other. Building complex distributed systems has therefore been a craft that many have tried, but few have mastered. To address this issue, this talk describes a pattern language that links scores of patterns relevant for distributed computing, including: (1) Object interaction, (2) Interface and component partitioning, (3)Application control, (4) Resource management, (5) Concurrency and synchronization. This pattern language has been used successfully by the speaker on production distributed applications and middleware at scores of companies for telecommunication systems, network management for personal communication systems, electronic medical imaging systems, real-time defense and aerospace systems, and computational finance. Much of the material presented in this talk is covered in the book ""Pattern-Oriented Software Architecture: A Pattern Language for Distributed Computing"", Wiley & Sons, 2007 by Frank Buschmann, Kevlin Henney, and Douglas Schmidt. 1:02:16 Dr. Douglas C. Schmidt strategic disciplines, Discovery Driven Growth, strict discipline no yes Discovery Driven Growth encompasses a set of strategic disciplines that are appropriate for today’s highly uncertain and volatile environments. Unlike conventional approaches to growth, which presume far more information than most companies possess, Discovery Driven Growth assumes that information needs to be identified and assumptions need to be converted to fact. http://www.computer.org/lockheed Innovation http://media.computer.org/sponsored/podcast/lmco/lmco-037-p.mp4 Thu, 27 May 2010 12:16:34 -0700 LMCO SSI Webinar Series Discovery Driven Growth encompasses a set of strategic disciplines that are appropriate for today’s highly uncertain and volatile environments. Unlike conventional approaches to growth, which presume far more information than most companies possess, Discovery Driven Growth assumes that information needs to be identified and assumptions need to be converted to fact. The core premise of the method is that when there isn’t enough information to develop a conventional business plan, the thrust of planning must instead be on learning, while at the same time reducing cost and risk. Conventional planning tends to lock an organization in, too early, to a specific operational trajectory. Discovery driven planning comprises five interdependent practices: 1) define success and drive the plan from this definition; 2) benchmark against key external variables; 3) think through operational specifications; 4) document assumptions and 5) re-assess assumptions and goals at key checkpoints. It imposes strict discipline on new projects, but discipline that is appropriate to their uncertain nature. Examples might include an entrepreneurial business, SAP contemplating entry into SaaS, and a chemical company evaluating a new product introduction. 1:02:16 Professor Rita Gunther McGrath strategic disciplines, Discovery Driven Growth, strict discipline no yes The world is becoming more dependent on software delivery efficiency and world economies are becoming more dependent on producing software with improved economic outcomes. What we have learned over decades of advancing systems and software development best practice is that successful software production involves more of an economics mindset than an engineering discipline when it comes to managing software delivery projects. http://www.computer.org/lockheed Software Engineering http://media.computer.org/sponsored/podcast/lmco/lmco-036-p.mp4 Thu, 13 May 2010 12:13:40 -0700 LMCO SSI Webinar Series The world is becoming more dependent on software delivery efficiency and world economies are becoming more dependent on producing software with improved economic outcomes. What we have learned over decades of advancing systems and software development best practice is that successful software production involves more of an economics mindset than an engineering discipline when it comes to managing software delivery projects. Most organizations that depend on software are struggling to transform their life-cycle model from a development focus to a delivery focus. This subtle distinction in wording represents a dramatic change in the principles that are driving the management philosophy and the governance models. A software development orientation focuses on the various activities required in the development process, while a software delivery orientation focuses on the results of that process. Organizations that have successfully made this transition—perhaps 30-40% by our estimate—have recognized that engineering discipline is trumped by economics discipline in most software-intensive endeavors. Day-to-day decisions in software projects have always been, and continue to be, dominated by: value judgments, cost tradeoffs, human factors, macro-economic trends, technology trends, market circumstances, and timing. Software project activities are less concerned with engineering disciplines such as mathematics, material properties, laws of physics, or established and mature engineering models. The primary difference between economics and engineering governance is the amount of uncertainty inherent in the product under development. The honest treatment of uncertainty is the foundation of today’s best practices; we have learned over and over that what makes a software practice better or best is that the practice reduces uncertainty in the target outcome. 1:02:16 Walker Royce software delivery, economics and engineering governance no yes We now live in an era of almost constant change. First, new technologies continue to emerge at an ever-more rapid pace. Second, globalization brings with it new markets, new customers, nontraditional competitors, and new challenges http://www.computer.org/lockheed Technology : Software http://media.computer.org/sponsored/podcast/lmco/lmco-035-p.mp4 Thu, 22 Apr 2010 12:12:01 -0700 LMCO SSI Webinar Series We now live in an era of almost constant change. First, new technologies continue to emerge at an ever-more rapid pace. Second, globalization brings with it new markets, new customers, nontraditional competitors, and new challenges We now live in an era of almost constant change. First, new technologies continue to emerge at an ever-more rapid pace. Second, globalization brings with it new markets, new customers, nontraditional competitors, and new challenges. Third, the Internet has created much greater transparency to any company’s strategy, actions, and performance. As a result of these forces, companies find that their strategies need almost constant redefinition—either because the old assumptions are no longer valid, or because the previous strategy has been imitated and neutralized by competitors, or because technological developments and globalization offer unanticipated opportunities. Rooted in these premises, the strategic challenges for organizations become: How do we identify the market discontinuities (e.g., fundamental shifts in technology, customers, competitors, lifestyle/demographics, globalization, regulations, etc.) that could transform our industry? How do we analyze the opportunities and risks, as a result of our understanding of market discontinuities? How can we create new growth platforms with a view to exploit the market discontinuities? What are our core competencies and how can we leverage them in the growth platforms? How do we allocate resources to support growth? What is your role in shaping the future of your company? What kind of organizational DNA must we have in order to anticipate and respond to changes on a continual basis? How do you execute breakthrough strategies? 1:02:16 Professor Vijay Govindarajan Reduce Costs, Test-driven development, Continuous integration, Continuous deployment no yes It's a dilemma as old as business: if you tell the customer what you think it will cost to build something, he won't buy. If you tell him what he wants to hear, he'll buy but then you can't make any money on the deal. Even if you take the high road, there's someone else out there who's willing to take the low road just to get the business. What do you do? http://www.computer.org/lockheed Technology : Software http://media.computer.org/sponsored/podcast/lmco/lmco-034-p.mp4 Thu, 8 Apr 2010 12:08:13 -0700 LMCO SSI Webinar Series It's a dilemma as old as business: if you tell the customer what you think it will cost to build something, he won't buy. If you tell him what he wants to hear, he'll buy but then you can't make any money on the deal. Even if you take the high road, there's someone else out there who's willing to take the low road just to get the business. What do you do? In private business the solution is building relationships. Once a supplier and customer have earned each others' trust, the conflict disappears. The supplier quotes honestly, the customer trusts that this represents a reasonable return for the supplier. Selling to governments doesn't allow this kind of long-term view, for fear of abuse (trust does exist de facto once a project is running, but the bidding process is still adversarial). One way out of this conundrum is to learn to build for less. One assumes that if this was easy, you would already be doing it. Some fundamental change is going to be required. My experience is with much smaller systems than those you build. However, I wonder if the same principles apply. When I want to work more efficiently, I take the tasks I am doing, chop them up, and rearrange the subtasks. My goal is to maximize feedback by delivering concrete value early and to minimize waste by deferring decisions until as much of the information required to make them is available. For those times when the information is not available, I invest in insurance to make sure I can change the decision later should new, contradictory information come to light. 1:02:16 Kent Beck Reduce Costs, Test-driven development, Continuous integration, Continuous deployment no yes In this talk we lay out the beginnings of a science of innovation tournaments, illustrating how the somewhat random process of identifying and selecting opportunities can be managed more deliberately. http://www.computer.org/lockheed Technology : Software http://media.computer.org/sponsored/podcast/lmco/lmco-033-p.mp4 Thu, 25 Mar 2010 12:04:45 -0700 LMCO SSI Webinar Series In this talk we lay out the beginnings of a science of innovation tournaments, illustrating how the somewhat random process of identifying and selecting opportunities can be managed more deliberately. Extremely valuable innovations are usually based on statistically exceptional opportunities. In most settings, organizations use tournaments to find these exceptional opportunities, by which we mean they generate many candidate opportunities and develop and filter them until only the very best remain. Although the basic idea of a tournament is common in industrial practice, very little science has been brought to bear on the problem of generating more, better opportunities and on more accurately evaluating and selecting the exceptional few. In this talk we lay out the beginnings of a science of innovation tournaments, illustrating how the somewhat random process of identifying and selecting opportunities can be managed more deliberately. 1:02:16 Professor Karl Ulrich innovations, tournaments no yes This lecture will examine various value engineering activities for requirements engineers. This presentation covers concepts from requirements engineering, project management, cost accounting, and system engineering http://www.computer.org/lockheed Technology : Software http://media.computer.org/sponsored/podcast/lmco/lmco-032-p.mp4 Thu, 11 Mar 2010 12:00:38 -0700 LMCO SSI Webinar Series This lecture will examine various value engineering activities for requirements engineers. This presentation covers concepts from requirements engineering, project management, cost accounting, and system engineering Value engineering is typically considered a project management activity. It is essential, however, for requirements engineers to be included in this activity in order to help manage customer expectations concerning the final costs of the delivered system and the feasibility or infeasibility of delivering certain features. Value engineering activities should commence when the systems-level requirements are being organized, and continue throughout the project life cycle. So that as better cost estimates become available, more informed tradeoff decisions can be made with the with the customer. This lecture will examine various value engineering activities for requirements engineers. This presentation covers concepts from requirements engineering, project management, cost accounting, and system engineering. 1:02:16 Dr. Phil Laplante Affordability, requirements engineering, project management no yes One reason why healthcare is so expensive, and quality of care so inconsistent, is that today’s hospitals and physician practices are actually a conflated set of business models. In this session, we’ll explain these problems and recommend solutions. http://www.computer.org/lockheed Technology : Software http://media.computer.org/sponsored/podcast/lmco/lmco-031-p.mp4 Thu, 25 Feb 2010 12:00:03 -0700 LMCO SSI Webinar Series One reason why healthcare is so expensive, and quality of care so inconsistent, is that today’s hospitals and physician practices are actually a conflated set of business models. In this session, we’ll explain these problems and recommend solutions. The process of making products and services more affordable and accessible begins when historically expensive expertise is commoditized. This has happened in every industry we have studied, and healthcare is no different. In healthcare, this process is heavily dependent upon the ability to make a precise diagnosis, which is driven by molecular and imaging diagnostics. These technologies need to be coupled with business model innovation. One reason why healthcare is so expensive, and quality of care so inconsistent, is that today’s hospitals and physician practices are actually a conflated set of business models. In this session, we’ll explain these problems and recommend solutions. 1:02:16 Professor Clayton M. Christensen Affordability, Healthcare, Innovation. no yes This webinar describes the model development methodology and the model parameters that drive systems engineering cost. http://www.computer.org/lockheed Technology : Software http://media.computer.org/sponsored/podcast/lmco/lmco-030-p.mp4 Thu, 11 Feb 2010 12:00:21 -0700 LMCO SSI Webinar Series This webinar describes the model development methodology and the model parameters that drive systems engineering cost. The process of accurately estimating systems engineering cost continues to be a challenge for organizations that develop or acquire complex systems. Building on the synergy between systems engineering and software engineering, we have developed a parametric cost model to address this need: the Constructive Systems Engineering Cost Model (COSYSMO). The objective of COSYSMO is to more accurately estimate the effort associated with performing system engineering tasks. This webinar describes the model development methodology and the model parameters that drive systems engineering cost. A simple implementation of COSYSMO is also provided along with associated lessons learned from its development and validation resulting from the usage experience within the U.S. aerospace industry (BAE Systems, Boeing, General Dynamics, L-3 Communications, Lockheed Martin, Northrop Grumman, Raytheon, and SAIC) and the DoD. 1:02:16 Dr. Ricardo Valerdi Affordability, software costs no yes In this presentation, we will first examine some best practices for delivering quality software-intensive systems, and then we will analyze the factors that contribute to the costs of production and of evolution. http://www.computer.org/lockheed Technology : Software http://media.computer.org/sponsored/podcast/lmco/lmco-029-p.mp4 Thu, 10 Dec 2009 14:08:00 -0700 LMCO SSI Webinar Series In this presentation, we will first examine some best practices for delivering quality software-intensive systems, and then we will analyze the factors that contribute to the costs of production and of evolution. Building quality software-intensive systems that meet the needs of its stakeholders is hard; trying to do that while simultaneously striving to reduce the cost of production as well as the total cost of ownership of that software as it evolves over its lifetime is harder still. In this presentation, we will first examine some best practices for delivering quality software-intensive systems, and then we will analyze the factors that contribute to the costs of production and of evolution. Next, we will study some approaches to building software for affordability, and then we will conclude by presenting emerging approaches to measuring and monitoring software costs. 1:02:16 Grady Booch Affordability, software costs no yes Most software cocktail conversations these days include a contest of how lean or agile people are relative to each other, and treat the two terms as if they are the same. The two concepts may be interchangeable at the cocktail discussion level. http://www.computer.org/lockheed Technology : Software http://media.computer.org/sponsored/podcast/lmco/lmco-028-p.mp4 Thu, 12 Nov 2009 15:09:57 -0800 LMCO SSI Webinar Series Most software cocktail conversations these days include a contest of how lean or agile people are relative to each other, and treat the two terms as if they are the same. The two concepts may be interchangeable at the cocktail discussion level. Most software cocktail conversations these days include a contest of how lean or agile people are relative to each other, and treat the two terms as if they are the same. The two concepts may be interchangeable at the cocktail discussion level. If we go one level deeper to the glossy brochure level we find blatant contradictions between the two: planning versus reacting; thinking versus doing; generalization versus specialization; and "figure it out" versus standards. But if we get beyond this dirty little secret of the Agile community and take a systems thinking approach we find strange loops between these two ideals: loops that suggest that you can reach the greatest heights with both together. The talk will offer concrete guidelines to reconcile the apparent contradictions based on broad experience. 1:02:16 Jim ("Cope") Coplien lean, agile, no yes This talk will provide examples of how this approach is coming together and really being used today. It will also highlight some important recent developments in the support for the development of model-driven architectures, including the standard SoaML profile for UML for services, the specification of execution semantics for models and the availability of open-source model provisioning tools. http://www.computer.org/lockheed Technology : Software http://media.computer.org/sponsored/podcast/lmco/lmco-027-p.mp4 Thu, 29 Oct 2009 15:09:57 -0800 LMCO SSI Webinar Series This talk will provide examples of how this approach is coming together and really being used today. It will also highlight some important recent developments in the support for the development of model-driven architectures. It is becoming increasingly understood that “Service-Oriented Architecture” should mean more than inserting Web services into your IT architecture. The techniques of service orientation are exceptionally useful at the levels of business and system architecture, as well at the technical IT level. Indeed, the concept of a “service” can provide the means for effectively tying together work across these levels, by focusing on the creation of business and IT solutions that identifiably deliver valuable services to end users. In order to do this, one needs a consistent representation, at all levels, to persist a common understanding of the architecture of an enterprise and to drive any new development within that architecture. Using models as the primary artifacts to do this leads to a model-driven service-oriented approach that enables a clear line of sight from the requirements of business services to the design and specification of supporting system services to the technical implementation of the specified Web services. Further, by providing appropriate abstractions at each level, a model-driven approach provides the means to control the complexity that can unfortunately come with simply introducing service-oriented technology at the technical level. Such an approach is truly “enterprise scope” because it takes into consideration the entire organization delivering those services, not just information systems or applications. And it is truly "architecture" because it straddles the business and the technical, looking for creative solutions that are effective for the business client and achievable for the technical developers. This talk will provide examples of how this approach is coming together and really being used today. It will also highlight some important recent developments in the support for the development of model-driven architectures, including the standard SoaML profile for UML for services, the specification of execution semantics for models and the availability of open-source model provisioning tools. 1:02:16 Ed Seidewitz Service oriented architecture, it architecture, end users, Web services, model-driven service-oriented no yes In addition, in this talk will also discuss Cloud Computing in general as well as from the industry perspective. Cloud options will be presented and HP’s strategy in the Cloud space. http://www.computer.org/lockheed Technology : Software http://media.computer.org/sponsored/podcast/lmco/lmco-026-p.mp4 Thu, 15 Oct 2009 15:08:00 -0800 LMCO SSI Webinar Series In addition, in this talk will also discuss Cloud Computing in general as well as from the industry perspective. Cloud options will be presented and HP’s strategy in the Cloud space. There are a number of important and useful testbeds, such as PlanetLab, EmuLab, IBM/Google cluster, and Amazon EC2/S3, that enable researchers to study different aspects of distributed computing. However, no single testbed supports research spanning systems, applications, services, open-source development, and datacenters. Towards this end, we have developed Open Cirrus, a cloud computing testbed for the research community that federates heterogeneous distributed data centers. Open Cirrus offers a cloud stack consisting of physical and virtual machines, and global services, such as sign-on, monitoring, storage, and job submission. By developing the testbed and making it available to the research community, we hope to help spur innovation in cloud computing and catalyze the development of an open source stack for the cloud. 1:02:16 Dr. Dejan Milojicic Cloud computing, testbeds, planetlab, emulab, open cirrus, monitoring, storage, open source no yes Test and evaluation are an important duo in almost any endeavor, and it is certainly no exception in software development. http://www.computer.org/lockheed Technology : Software http://media.computer.org/sponsored/podcast/lmco/lmco-025-p.mp4 Thu, 1 Oct 2009 15:06:04 -0800 LMCO SSI Webinar Series Test and evaluation are an important duo in almost any endeavor, and it is certainly no exception in software development. Test and evaluation are an important duo in almost any endeavor, and it is certainly no exception in software development. Many who frequently perform testing are unaware that how one tests will determine how easy or how hard it will be to evaluate the results of testing. This presentation will provide a brief overview of the best techniques for multi-variate testing. Multi-Variate Testing (MVT) is known by different names, and perhaps Design of Experiments (DOE) is the most commonly used alternative name. We will begin with Full and Fractional Factorial designs to illustrate the important properties of a test design. Then we will move into the higher dimension spaces where Latin Hypercube Designs are the best choices for fractionating or reducing the number of test cases that have to be investigated. A special technique called High Throughput Testing will be demonstrated. These testing techniques can be used at all levels, including system level testing, functional testing, and regression testing. Since testing is essentially a continuous process in software development, it behooves software testers to know the best techniques for testing. 1:02:16 Dr. Mark J. Kiemele Test, multi-variate testing, design of experiments, latin hypercube designs no yes Software Architecture is often either imprecise and hard to grasp or technology specific. http://www.computer.org/lockheed Technology : Software http://media.computer.org/sponsored/podcast/lmco/lmco-024-p.mp4 Thu, 17 Sep 2009 15:04:02 -0800 LMCO SSI Webinar Series Software Architecture is often either imprecise and hard to grasp or technology specific. Software Architecture is often either imprecise and hard to grasp or technology specific. What you really want is a succinct, precise, technology-independent and tool-processable description of an architecture. In this session we illustrate how textual Domain Specific Languages can be used for this. The core idea is to actually develop the architecture language as you understand the architecture, formalizing the growing intuitive understanding into a formal language. This removes ambiguity from the discussion, requires answers to arising questions and results in a more consistent and (re-)usable architecture. The session outlines the concept based on an extensive example, explains some of the conceptual background and briefly looks at language tools that can be used to implement this approach. 1:02:16 Dr. Markus Völter Software Architecture, architecture language, formal language no yes Testing is often characterized as a relatively mindless activity that should be formalized, standardized, routinized, endlessly documented, fully automated, and most preferably, eliminated. http://www.computer.org/lockheed Technology : Software http://media.computer.org/sponsored/podcast/lmco/lmco-023-p.mp4 Thu, 3 Sep 2009 15:02:00 -0800 LMCO SSI Webinar Series Testing is often characterized as a relatively mindless activity that should be formalized, standardized, routinized, endlessly documented, fully automated, and most preferably, eliminated. Testing is often characterized as a relatively mindless activity that should be formalized, standardized, routinized, endlessly documented, fully automated, and most preferably, eliminated. This webinar presents the contrasting view: good testing is challenging. cognitively complex, and customized to suit the circumstances of the individual project. The webinar presents testing as an empirical, technical investigation of a software product or service, conducted to provide quality-related information to stakeholders. A fundamental challenge of testing is that cost/benefit analysis underlies every decision. Two tests are distinct if one can reveal an error that the other would miss. The population of distinct tests of any nontrivial program is infinite. And so any decision to do X is also a decision to not do the things that could have been done if the resources hadn’t been spent on X. The question is not whether an activity is worthwhile. It is whether this activity is so much more worthwhile than the others that it would be a travesty not to do it (or at least, a little bit of it). For example, system-level regression-test automation might allow us to run the same tests thousands of times at low cost, but after the first few repetitions, how much do we learn from the typical regression test? What if instead, we spent the regression-test resources on new tests, addressing new risks (other ways the program could fail)? Quality is not quantity. If our measure is amount (or value) of quality-related information for the stakeholders, what improves efficiency? Do we cover more ground by running in place very quickly, or by moving forward more slowly? Under what conditions do which types of automation improve testing effectiveness or efficiency? Another fundamental challenge of testing is that quality is subjective—as Weinberg put it, “Quality is value to some person.” Meeting a specification might trigger someone’s duty to pay for a program, but if the program doesn’t actually meet their needs, preferences, and expectations, they won’t like it, won’t want to use it, and certainly won’t recommend it. How should we design a testing effort to expose the potential dissatisfiers for each stakeholder? 1:02:16 Dr. Cem Kaner Testing, Software, Quality no yes "Design Patterns", by Erich Gamma, Richard Helm, Ralph Johnson, and John Vlissides, was released in October, 1994. It has continued to sell for 15 years and has had a big impact. http://www.computer.org/lockheed Technology : Software http://media.computer.org/sponsored/podcast/lmco/lmco-022-p.mp4 Thu, 20 Aug 2009 14:59:07 -0800 LMCO SSI Webinar Series "Design Patterns", by Erich Gamma, Richard Helm, Ralph Johnson, and John Vlissides, was released in October, 1994. It has continued to sell for 15 years and has had a big impact.. "Design Patterns", by Erich Gamma, Richard Helm, Ralph Johnson, and John Vlissides, was released in October, 1994. It has continued to sell for 15 years and has had a big impact. Fifteen years after it came out, some of the patterns continue to be important, some less important. New patterns have arisen that have displaced some of the older patterns. There are common ways that the patterns are misused. Ralph Johnson will talk about what he has learned about the patterns since the book was published. 1:02:16 Dr. Ralph Johnson Design Patterns no yes A system of systems consists of two or more systems that work together to provide value-added capabilities that cannot be achieved by any of the individual systems working in isolation of the other systems. http://www.computer.org/lockheed Technology : Software http://media.computer.org/sponsored/podcast/lmco/lmco-021-p.mp4 Thu, 6 Aug 2009 14:57:23 -0800 LMCO SSI Webinar Series Many of today’s large-scale systems are systems of systems. We agree that we want to manage our requirements, but what does this mean? How will we know if we are managing them? What are the advantages we want? And what can we do to realise them? These questions are the focus of this webinar with Suzanne Robertson, joint originator of the Volere requirements techniques and a founder of The Atlantic Systems Guild. Ability to make changes, accurate estimates, task allocation, communication between business and technical people, risk monitoring, reuse of requirements, these are a few of the reasons for spending effort on managing requirements. This webinar shows how a well-defined requirements knowledge structure is at the heart of achieving these advantages. Suzanne will outline a structure, think of it as a filing system, for making traceable connections between all levels of your requirements. You can identify the dependencies between high-level business or domain requirements and measurable atomic requirements and all the levels in between. Systems analysis models/deliverables, design models/components, data definitions, code and testing are all types of requirements knowledge that you can include in your requirements management plan. The resulting requirements knowledge model is a framework that you can use to manage your requirements knowledge regardless of modelling notation, methodology, degree of agility, or tool usage. 1:02:16 Dr. James Bret Michaels Large-scale systems, life-cycle, no yes We agree that we want to manage our requirements, but what does this mean? http://www.computer.org/lockheed Technology : Software http://media.computer.org/sponsored/podcast/lmco/lmco-020-p.mp4 Thu, 23 Jul 2009 14:54:18 -0800 LMCO SSI Webinar Series How will we know if we are managing them?. We agree that we want to manage our requirements, but what does this mean? How will we know if we are managing them? What are the advantages we want? And what can we do to realise them? These questions are the focus of this webinar with Suzanne Robertson, joint originator of the Volere requirements techniques and a founder of The Atlantic Systems Guild. Ability to make changes, accurate estimates, task allocation, communication between business and technical people, risk monitoring, reuse of requirements, these are a few of the reasons for spending effort on managing requirements. This webinar shows how a well-defined requirements knowledge structure is at the heart of achieving these advantages. Suzanne will outline a structure, think of it as a filing system, for making traceable connections between all levels of your requirements. You can identify the dependencies between high-level business or domain requirements and measurable atomic requirements and all the levels in between. Systems analysis models/deliverables, design models/components, data definitions, code and testing are all types of requirements knowledge that you can include in your requirements management plan. The resulting requirements knowledge model is a framework that you can use to manage your requirements knowledge regardless of modelling notation, methodology, degree of agility, or tool usage. 1:02:16 Suzanne Robertson Requirements, measurable atomic requirements, Systems analysis models/deliverables, design models/components, data definitions, code and testing no yes Systems Architecting is a technical activity with technical products, but it is inextricably linked to business or operational strategy. In this talk we will take up the challenge of reconciling architectures at two apparently different levels: Business strategy at the high level and hardware and software are the low level http://www.computer.org/lockheed Technology : Software http://media.computer.org/sponsored/podcast/lmco/lmco-019-p.mp4 Thu, 9 Jul 2009 14:48:59 -0800 LMCO SSI Webinar Series Systems Architecting is a technical activity with technical products, but it is inextricably linked to business or operational strategy. In this talk we will take up the challenge of reconciling architectures at two apparently different levels: Systems Architecting is a technical activity with technical products, but it is inextricably linked to business or operational strategy. In this talk we will take up the challenge of reconciling architectures at two apparently different levels: Business strategy at the high level and hardware and software are the low level. We will see that while these levels are very different in abstraction and concern they share important architectural concepts. We can also find examples that illustrate the issues from pre-WWII to the present day. The first example is old, the development of the DC-3 airplane, but demonstrates the interaction of technical architectural decision making with business strategy. In the 1930's two companies took the same technology down two different paths that were superficially similar, but dramatically different in business strategy. Both were successful in the local sense of meeting their architectural objectives, but only one was successful in revolutionizing the airline business. In the present day the move from vertically organized (or "Stovepiped") software to horizontally layered systems is, in many ways, a similar example with many more players. The technical shift, from vertical to horizontal organization, has enormous consequences in management and programmatics. The reconcilation of those consequences ultimately lies with the business strategy. Technical choices are enabling or disabling of strategic choices, and vice versa. The talk will illustrate with specific case examples. 1:02:16 Dr. Mark Maier Systems architect, technical products, business strategy, hardware, software no yes Software is not only a key asset in IT systems, but plays an increasingly important role in almost all domains such as automation systems, healthcare products, or home appliances. http://www.computer.org/lockheed Technology : Software http://media.computer.org/sponsored/podcast/lmco/lmco-018-p.mp4 Thu, 25 Jun 2009 14:42:07 -0700 LMCO SSI Webinar Series Software is not only a key asset in IT systems, but plays an increasingly important role in almost all domains such as automation systems, healthcare products, or home appliances. Software is not only a key asset in IT systems, but plays an increasingly important role in almost all domains such as automation systems, healthcare products, or home appliances. Consequently, quality problems or failures in software projects have a huge economic impact. If software is so important, then the role of a software architect needs special consideration and care. What are the responsibilities of software architects in the development process? How do they interact with other roles such as requirements engineers, developers or test managers? What are the typical failures and challenges they are facing? Which kind aof experience, skills and knowledge should they have? It is the main objective of the webinar to address these issues. After the webinar, attendees will have a clearer picture about the role of a software architect. 1:02:16 Dr. Michael Stal Software architect, it systems, software, automation systems, healthcare no yes How much design is enough design in software? http://www.computer.org/lockheed Technology : Software http://media.computer.org/sponsored/podcast/lmco/lmco-017-p.mp4 Thu, 11 Jun 2009 14:39:05 -0700 LMCO SSI Webinar Series How much design is enough design in software? How much design is enough design in software? We know that software which lacks a coherent design can be extremely difficult to maintain, extend, scale, and reuse. We also know that software which is over-designed becomes excessively complex, and as a result is just as hard to work with. The concept of emergence in design is based on the critical principles, practices, and disciplines that remove the risks and waste associated with changing a design as needed, and thus removes the motivation for overdesign in the first place. This seminar will introduce these concepts, and provide a brief demonstration of design emergence through system evolution. 1:00:33 Scott Bain Software, over-designed, emergence in design, critical principles, practices and disciplines no yes This webinar describes the construction of executable UML models and translation rules that map models onto multiple platforms and implementations. We also show how this process is inherently agile, and parallel to boot. http://www.computer.org/lockheed Technology : Software http://media.computer.org/sponsored/podcast/lmco/lmco-016-p.mp4 Wed, 28 May 2008 14:36:44 -0700 LMCO SSI Webinar Series This webinar describes the construction of executable UML models and translation rules that map models onto multiple platforms and implementations. We also show how this process is inherently agile, and parallel to boot. "Agile" and "Model-Driven Development" do not often appear in the same sentence. Among several important ideas, agility promotes the notion that testing a running system is better than building descriptions of them. With the addition of actions to UML, models can be executed, and many of the principles of agility can be applied to executable models. This webinar describes the construction of executable UML models and translation rules that map models onto multiple platforms and implementations. We also show how this process is inherently agile, and parallel to boot. 1:00:33 Stephen J. Mellor Agile model-driven development, uml, models, multiple platforms no yes The construction and exploitation of models are integral to any engineering discipline. http://www.computer.org/lockheed Technology : Software http://media.computer.org/sponsored/podcast/lmco/lmco-015-p.mp4 Thu, 14 May 2009 14:33:36 -0700 LMCO SSI Webinar Series The construction and exploitation of models are integral to any engineering discipline Given the complexity of modern real-time and embedded software systems, it is quite natural to use models and modeling in their design. However, while models have been used in software development for a long time (consider, for example, the classical flow-chart notation used to describe algorithmic procedures), it is only recently that their full potential for boosting productivity and quality has been recognized and effectively realized in software engineering. In this talk, we first examine the essential characteristics of model-based software engineering and then focus on its application to real-time and embedded systems, including a review of the relevant latest developments and standards. Next, we examine the state of the art as well as the state of the practice of these methods and technologies in industrial settings. Finally, we discuss the challenges to and opportunities for extending the current capabilities of model-based real-time software and systems development. 59:43 Bran Selec Modern real-time, embedded software sytems, design, software engineering no yes What will that profession require of us, and who among us can truly claim to be professional? http://www.computer.org/lockheed Technology : Software http://media.computer.org/sponsored/podcast/lmco/lmco-014-p.mp4 Thu, 7 May 2009 14:28:28 -0700 LMCO SSI Webinar Series What will that profession require of us, and who among us can truly claim to be professional? We’ve come a long way in the last 20 years. We start our journey in the late 80s and our “discovery” of design principles such as The Open Closed Principle and the Liskov Substitution Principle. In the middle 90s, we discovered that these principle led to repeating patterns of design. We gave those patterns names such as Visitor and Decorator. At the turn of the millennium we found that the benefits gained from the principles and patterns could be amplified by combining them with practices such as Test Driven Development and Continuous Integration. And now, as the decade is coming to a close, we have found that these principles, patterns, and practices have driven us to define a true profession. What will that profession require of us, and who among us can truly claim to be professional? 56:31 Robert Martin Liskov Substitution Principle, Visitor and Decorator, principles, patterns, and practices no yes This talk will discuss how lean principles and agile software development practices can contribute to improved performance while negotiating and developing software under contract. http://www.computer.org/lockheed Technology : Software http://media.computer.org/sponsored/podcast/lmco/lmco-013-p.mp4 Thu, 30 Apr 2009 14:10:08 -0700 LMCO SSI Webinar Series This talk will discuss how lean principles and agile software development practices can contribute to improved performance while negotiating and developing software under contract. Systematic is a Danish company that develops software under contract for military, health care and other mission critical applications. Appraised in November 2005 and found to be CMMI level 5 compliant, Systematic turned to agile software development and lean principles to further improve its performance, with impressive positive results. The company presents just one example of the benefits that you can expect from applying lean principles to software development. This talk will discuss how lean principles and agile software development practices can contribute to improved performance while negotiating and developing software under contract. 1:04:55 Mary Poppendieck software development, agile no yes This presentation will examine the factors that separate vision and execution, and the processes and best practices we've seen that attend to these factors. http://www.computer.org/lockheed Technology : Software http://media.computer.org/sponsored/podcast/lmco/lmco-012-p.mp4 Thu, 2 Apr 2009 14:07:23 -0700 LMCO SSI Webinar Series This presentation will examine the factors that separate Xvision and execution, and the processes and best practices we've seen Xthat attend to these factors. A number of factors separate the vision of system from its manifestation in software and hardware; some of these factors are fundamental (such as the limits of the speed of light) while others are human (such as those imposed by moral or ethical considerations). Most organizations struggle with the factors that are at the cusp of the technical and the social, the limits of design and the limits of organization. This presentation will examine the factors that separate vision and execution, and the processes and best practices we've seen that attend to these factors. We'll emphasize the role of architecture, architectural patterns, the architect, and organizational patterns, and we'll also examine issues of the engineering of software-intensive systems, which involves an intricate dance between the software- and hardware-related design decisions that must be made interdependently. 57:42 Grady Booch Systems Architecture, architecture, architectural patterns, organizational patterns, software-intensive systems no yes Through her insight and experience, Janet will show you how to take a holistic approach to collaboration between teams and adjust the processes to make it happen. http://www.computer.org/lockheed Technology : Software http://media.computer.org/sponsored/podcast/lmco/lmco-011-p.mp4 Thu, 19 Mar 2009 14:04:52 -0700 LMCO SSI Webinar Series Through her insight and experience, Janet will show you how to take a holistic approach to collaboration between teams and adjust the processes to make it happen. Even if agile development has “crossed the chasm” and is becoming a mainstream set of practices, the concentration of literature is about application development. Products that include hardware, firmware and application development teams have special needs that need to be addressed. Janet explains how a shift in thinking helps you make the transition to agile product development. When teams change their mindset from, “How do I create my hardware or software?” to “How can I help the organization deliver a really great product?”, the whole product quality ultimately improves. Through her insight and experience, Janet will show you how to take a holistic approach to collaboration between teams and adjust the processes to make it happen. 58:12 Janet Gregory Agile development, hardware, software no yes This webinar explains how to perform trade-off analysis among requirements, schedule and resource constraints, development risks, projected effects on revenues and profits, market share, and ROI. http://www.computer.org/lockheed Technology : Software http://media.computer.org/sponsored/podcast/lmco/lmco-010-p.mp4 Wed, 4 Mar 2009 14:02:44 -0700 LMCO SSI Webinar Series This webinar explains how to perform trade-off analysis among requirements, schedule and resource constraints, development risks, projected effects on revenues and profits, market share, and ROI. We all know that requirements engineering is one of the first activities to be initiated for a project. Many books have been written on requirements elicitation (learning about needs and problems experienced by customers) and specification (recording the external behavior of the desired system). Yet few authors and even fewer practitioners are willing to tackle the most difficult task of requirements engineering, i.e., requirements triage. Requirements triage is the set of activities to determine which requirements are the right requirements to attempt to satisfy. The reason it is so onerous is that there are never sufficient resources to accomplish all that is desired, and the decision requires knowledge of engineering, marketing, sales, and finance. In traditional software organizations, marketing takes control of feature selection. The latest incarnations of agile development give most of the responsibility for selecting features to development. Neither extreme works in practice. This webinar explains how to perform trade-off analysis among requirements, schedule and resource constraints, development risks, projected effects on revenues and profits, market share, and ROI. The trade-off analysis starts with a list of candidate requirements, takes you through the triage process (which considers all of the above factors), and ends with a list of selected requirements, an optimal allocation of development resources, and a believable product plan. The webinar will also show how seeing simultaneous multiple views of your product is essential to see the ramifications of any change you make during the process. 1:07:03 Dr. Al Davis right requirements, requirements engineering, knowledge of engineering no yes McConnell names the Agile practices that have worked well for Construx's clients, describes the failure modes of Agile practices http://www.computer.org/lockheed Technology : Software http://media.computer.org/sponsored/podcast/lmco/lmco-009-p.mp4 Tue, 19 Feb 2008 14:00:57 -0700 LMCO SSI Webinar Series McConnell names the Agile practices that have worked well for Construx's clients, describes the failure modes of Agile practices Agile development has now been in use for almost a decade. Why use Agile methods? What are the strengths of Agile? What are some common failure modes? What other lessons has the software industry learned about Agile development? In this talk, Steve McConnell draws on Construx's extensive consulting work to dissect Agile development. McConnell names the Agile practices that have worked well for Construx's clients, describes the failure modes of Agile practices that have failed to live up to the hype, and explains how to right-size Agile development for your organization. 1:00:48 Steve McConnell Agile development, dissect Agile development, right-sizing no yes The Responsive Design Project is my attempt to understand, after thirty some years of practice, what I do when I design software http://www.computer.org/lockheed Technology : Software http://media.computer.org/sponsored/podcast/lmco/lmco-008-p.mp4 Thu, 5 Feb 2009 13:58:17 -0700 LMCO SSI Webinar Series In this presentation, we will discuss current schools of TDD practice Xwith the aid of a set of Java and C++ examples. The Responsive Design Project is my attempt to understand, after thirty some years of practice, what I do when I design software. One of the first encouraging results was that when I looked at the kind of changes I made to designs, I found they fit into four strategies: Leap, Parallel, Stepping Stone, and Simplification. In this talk I will introduce these four strategies, describe how they play at many levels from architecture to methods, and set them in the context of the overall project. 1:01:23 Kent Beck Responsive Design Project, Leap, Parallel, Stepping Stone, Simplification no yes In this presentation, we will discuss current schools of TDD practice with the aid of a set of Java and C++ examples. http://www.computer.org/lockheed Technology : Software http://media.computer.org/sponsored/podcast/lmco/lmco-007-p.mp4 Thu, 22 Jan 2009 13:55:06 -0700 LMCO SSI Webinar Series In this presentation, we will discuss current schools of TDD practice Xwith the aid of a set of Java and C++ examples. Test-Driven Development is one of the more controversial software development practices to have gained popularity over the past ten years. TDD is a simple process to describe, but its effects are significant. They force us to reconsider many of our ideas about encapsulation, design and testing. In this presentation, we will discuss current schools of TDD practice with the aid of a set of Java and C++ examples. We will also discuss the technical challenges presented by large existing code bases, and the various ways that TDD is currently impacting requirements gathering, and framework and language design. 58:51 Michael Feathers Object interaction, Interface and component partitioning, Application control, Resource management, Concurrency andXsynchronization. no yes This talk describes a pattern language that links hundreds of patterns relevant for distributed computing. http://www.computer.org/lockheed Technology : Software http://media.computer.org/sponsored/podcast/lmco/lmco-006-p.mp4 Thu, 8 Jan 2009 13:51:59 -0700 LMCO SSI Webinar Series This talk describes a pattern language that linksXhundreds of patterns relevant for distributed computing. Developing software for distributed computing applications that effectively utilize concurrency over high-speed, low-speed, and mobile networks is hard; developing high quality reusable distributed applications is even harder. Many patterns in the software literature focus on distributed computing. Until recently, however, there has been no holistic view of distributed computing that emphasizes how groups of patterns complete and complement each other. Building complex distributed systems has therefore been a craft that many have tried, but few have mastered. To address this issue, this talk describes a pattern language that links hundreds of patterns relevant for distributed computing, including: (1) Object interaction, (2) Interface and component partitioning, (3) Application control, (4) Resource management, (5) Concurrency and synchronization. This pattern language has been used successfully by the speaker on production distributed applications and middleware at scores of companies for telecommunication systems, network management for personal communication systems, electronic medical imaging systems, real-time avionics and aerospace systems, and automated stock trading. The material presented in this talk appears in the book "Pattern-Oriented Software Architecture: A Pattern Language for Distributed Computing", Wiley & Sons, 2007 by Frank Buschmann, Kevlin Henney, and Douglas Schmidt. 59:31 Dr. Douglas C. Schmidt Object interaction, Interface and component partitioning, Application control, Resource management, Concurrency andXsynchronization. no yes This webinar will review the set of concepts and methods applicable to systems architecting across a wide range of applications. http://www.computer.org/lockheed Technology : Software http://media.computer.org/sponsored/podcast/lmco/lmco-005-p.m4v Thu, 18 Dec 2008 13:47:41 -0700 LMCO SSI Webinar Series This webinar will review the set of concepts and methods applicable to systems architecting across a wide range of applications. Systems Architecture and Architecting are central to successful system development, but they are also terms with variable and inconsistent meanings. In some cases systems architecture is a defined business type. In other contexts systems architecting is that part of systems engineering with primary concern for purpose determination, concept formulation, and validation for use. This webinar will review the set of concepts and methods applicable to systems architecting across a wide range of applications. The webinar will focus on concepts, specifically identifying “architectural” or fundamental aspects of systems and development projects, and methods for accomplishing the same. The concepts discussed will include the architecture metaphor and its application to system development, distinguishing between architecture as a concept and architecture description, architecture as invariants in evolving systems, and dimensions of complexity and their impact on architectural approaches. In methods we will contrast project management techniques, formalized heuristics, and document-driven approaches that illuminate fundamental decisions rather than hide them. 1:01:50 Dr. Mark W. Maier Systems Architecture, successful system development no yes This webinar provides an introduction to applying lean principles to software development. It will cover eight principles of Lean Software Development http://www.computer.org/lockheed Technology : Software http://media.computer.org/sponsored/podcast/lmco/lmco-004-p.mp4 Thu, 4 Dec 2008 13:59:12 -0800 LMCO SSI Webinar Series This webinar provides an introduction to applying lean principles to software development. It will cover eight principles of Lean Software Development This webinar provides an introduction to applying lean principles to software development. It will cover eight principles of Lean Software Development 1:04:55 Mary Poppendieck Eliminate Waste, Focus on Learning , Build Quality In, Defer Commitment, Deliver Fast, Respect People, Improve Relentlessly, Optimize the Whole no yes This webinar will describe how organizations and projects adopt standards process descriptions to define their life cycle models and to define their procedures so their practices to achieve the successful outcomes with measurable maturity capability. http://www.computer.org/lockheed Technology : Software http://media.computer.org/sponsored/podcast/lmco/lmco-003-p.mp4 Thu, 20 Nov 2008 16:16:13 -0800 LMCO SSI Webinar Series Standards & Practices for Software and System Engineers / Professionals This webinar will describe how organizations and projects adopt standards process descriptions to define their life cycle models and to define their procedures so their practices to achieve the successful outcomes with measurable maturity capability. 1:00:11 John Walz software-intensive system, review fundamental concepts of modeling and simulation, model, simulate, automate, and test complex no yes In this presentation, we'll examine the state of the practice in software architeture, examining topics such as software architecture representation, patterns, process, and governance. http://www.computer.org/lockheed Technology : Software http://media.computer.org/sponsored/podcast/lmco/lmco-002-p.mp4 Thu, 6 Nov 2008 16:14:28 -0800 LMCO SSI Webinar Series Modeling and Simulation-Driven Development of Complex, Software-Intensive Systems In this presentation, we'll examine the state of the practice in software architecture, examining topics such as software architecture representation, patterns, process, and governance. 1:05:27 Dr. Bernard P. Zeigler software-intensive system, review fundamental concepts of modeling and simulation, model, simulate, automate, and test complex no yes In this presentation, we'll examine the state of the practice in software architecture, examining topics such as software architecture representation, patterns, process, and governance. http://www.computer.org/lockheed Technology : Software http://media.computer.org/sponsored/podcast/lmco/lmco-001-p.mp4 Thu, 16 Oct 2008 07:56:00 -0700 LMCO SSI Webinar Series Best Practices in Software Architecture In this presentation, we'll examine the state of the practice in software architecture, examining topics such as software architecture representation, patterns, process, and governance. 1:08:30 Grady Booch software-intensive system, architecture, legacy systems, patterns, process, governance no yes