Tutorials
Tutorials
Monday, October 12, 2015
Track B: 8:00 a.m. – 11:45 a.m.
Managing Technical Debt for Software and Systems Projects Dick Fairley and Mary Jane Willshire Technical debt provides a useful perspective for dealing with problems that arise when work that should have been completed on a software or systems project is deferred until later. This tutorial describes some techniques that can be used to identify, assess, and mitigate technical debt. Topics presented will include the nature of and consequences of technical debt across the continuum of system development life cycles that range from highly predictive (e.g., waterfall) to incremental predictive (e.g., incremental development) to iterative adaptive (e.g. Scrum) to highly adaptive (e.g., eXtreme Programming). The relationship between managing technical debt and risk management will be covered. Learning Objectives: The learning objectives for this half-day tutorial is for participants to understand the concepts of technical debt, which provide a useful perspective for dealing with problems that arise when work that should have been completed on a software or systems project is deferred until later. In addition, participants will learn useful techniques for identifying, assessing, and mitigating technical debt at four points on the lifecycle continuum of software and systems development models. Understanding the various techniques across the life cycle continuum will provide participants with the information needed to adapt the concepts of technical debt to their projects and programs. Dick Fairley (IEEE) Richard E. (Dick) Fairley, PhD is Principal Associate of Software Engineering and Management Associates (S2EA), a consulting and training company. He is also chair of the Software and Systems Engineering Committee of the IEEE Computer Society and a Computer Society delegate to the governing board of BKCASE. In addition, he is the appointed Computer Society appointed liaison to PMI and INCOSE. He is an adjunct faculty member at Colorado Technical University and an Affiliate Faculty Member at Regis University. His research interests include software systems engineering, project management, and process improvement. He is a member of IEEE, the IEEE Computer Society, INCOSE, and PMI. Mary Jane Willshire (S2EA) Mary Jane Willshire, PhD is an Associate Member of Software Engineering and Management Associates (S2EA), a consulting and training company. She is an adjunct professor at Regis and Capella Universities and a former Dean of Computer Science at Colorado Technical University. Her research interests include software engineering, human computer interaction, and process improvement. She is a member of IEEE-CS and ACM. Track B: 1:15 p.m. – 5:00 p.m. Systems Engineering for Software Engineers Dick Fairley and Massood Towhidnejad It is well known that the majority of functionality and behavior of modern systems is provided by software, whether in health care, telecommunications, transportation, aeronautics, manufacturing, military systems, consumer products, and other domains. Understanding systems engineering issues is an important topic for software engineers who engage in projects and programs that involve developing and modifying hardware, software, and manual operations because these systems are becoming ever larger, more complex, and include more diverse kinds of components. This tutorial will cover some key areas that create problems when system engineers, software engineers, and other engineers work together on systems projects and programs. Topics to be covered include consequences of the differences between physical artifacts and software; differences in approaches to problem solving – functional decomposition and quantified metrics versus associative decomposition and qualitative metrics; differences in terminology such as “performance,” “verification,” and “validation;” differences in approaches to component integration – one-time versus stepwise versus continuous; difference in development processes – linear waterfall versus iterative agile; and differences in personality traits –outward people-focus versus inward product-focus. Techniques and strategies will be discussed on how software engineers, systems engineers, and other engineers can better understand their differences and integrate their work activities. Ample time will be allotted for discussions and interchanges of viewpoints. Learning Objectives: The learning objectives for this half-day tutorial is for participants to understand the nature of systems engineering for software-intensive systems, the differences in approaches to problem solving, terminology, metrics and measures, process models, and personality characteristics of software engineers and systems engineers, and to learn how to deal with these differences when participating as a member of a systems engineering team or as a member of a software project that is part of an systems engineering program. Dick Fairley (IEEE) Richard E. (Dick) Fairley, PhD is Principal Associate of Software Engineering and Management Associates (S2EA), a consulting and training company. He is also chair of the Software and Systems Engineering Committee of the IEEE Computer Society and a Computer Society delegate to the governing board of BKCASE. In addition, he is the appointed Computer Society appointed liaison to PMI and INCOSE. He is an adjunct faculty member at Colorado Technical University and an Affiliate Faculty Member at Regis University. His research interests include software systems engineering, project management, and process improvement. He is a member of IEEE, the IEEE Computer Society, INCOSE, and PMI. Massood Towhidnejad (Embry Riddle Aeronautical University) Massood Towhidnejad, PhD is Director of the NextGeneration ERAU Applied Research (NEAR) laboratory, and Professor of Software Engineering in the department of Electrical, Computer, Software, and Systems Engineering at Embry-Riddle Aeronautical University. He is also a vice chair of the Software and Systems Engineering Committee of the IEEE Computer Society and a Computer Society delegate to the governing board of BKCASE. His research interests include software engineering, software quality assurance and testing, autonomous systems, and Air Traffic Management (NextGen). In addition to his university position, he has served as Visiting Research Associate at the Federal Aviation Administration, Faculty Fellow at NASA Goddard Flight Research Center, and Software Quality Assurance Manager at Carrier Corporations. He is a senior member of IEEE. Track C: 8:00 a.m. – 11:45 a.m. Balancing Systems and Software Qualities Tutorial Description Pending Dr. Barry Boehm, USC Dr. Barry Boehm is the TRW Professor in the USC Computer Sciences, Industrial and Systems Engineering, and Astronautics Departments. He is also the Director of Research of the DoD-Stevens-USC Systems Engineering Research Center, and the founding Director of the USC Center for Systems and Software Engineering. He was director of DARPA-ISTO 1989-92, at TRW 1973-89, at Rand Corporation 1959-73, and at General Dynamics 1955-59. His contributions include the COCOMO family of cost models and the Spiral family of process models. He is a Fellow of the primary professional societies in computing (ACM), aerospace (AIAA), electronics (IEEE), and systems engineering (INCOSE), and a member of the U.S. National Academy of Engineering. Track C: 1:15 p.m. – 5:00 p.m. Secure data collection with the open source OpenDOF technology Bryant Eastham and Mark Nelson The OpenDOF Project is an open-source solution to device, gateway, and cloud communications that includes a standardized object model and secure communication. The project was incubated for 10 years inside of Panasonic, and released as an open-source project in March of 2015. In addition to secure bi-directional command and control, the platform includes libraries and SDKs for data collection. These libraries can be easily included in IoT projects, either using existing back-end datastores or cloud solutions such as MongoDB or AWS DynamoDB. There is no payment required to use the libraries. Participants in the tutorial will receive a full set of SDKs (open source, freely available) and will use their laptop to create a data-gathering solution in addition to adding secure command-and-control. The tutorial is built for participants to follow along on their own laptop using a virtual machine image that will be provided. Laptops should have sufficient free resources to run a virtual machine. Participants with access to infrastructure (for example, an AWS account) can deploy their solution to their cloud. Otherwise, participants will leverage local, tutorial-only systems provided. The tutorial will include: Participants will leave with everything they need to use the technology in their own projects and infrastructure. Learning Objectives: Participants would understand the OpenDOF Project solution to secure device to cloud data gathering. Bryant Estham (Panasonic North America) Track D: 8:00 a.m. – 5:00 p.m. Practical Guide to Using SFIA Matthew Burrows Understanding SFIA: Full day tutorial - Face to Face Workshop-based training This tutorial introduces the Skills Framework for the Information Age (SFIA) and provides essential training required to use SFIA in your organization. It is also a prerequisite for anyone wishing to become a SFIA Accredited Consultant. Taking attendees from the history of SFIA through to practical exercises on using SFIA, and handy tips for implementation, this course is ideal for people looking to lead the way with SFIA within their organization. Having attended this tutorial, people should be able to do the following: Matthew Burrows (SFIA) Matthew currently serves on the SFIA Council, is Chair of the itSMF International Ethics Review Board, and contributes to the service management industry and the development of best practice – including as Design Authority for SFIA V6. He is an ISO/IEC 20000 qualified consultant and auditor, and SFIA Accredited Consultant, specializing in implementing pragmatic business service management solutions rather than just theoretical consulting. He has considerable practical and operational experience of Service Management. Matthew’s authoring credits include SFIA (Skills Framework for the Information Age), Service Management, Portfolio and Programme Management methodologies, white papers, books, articles and publications.
Bryant Eastham serves as the Principal Software Architect for Panasonic Corporation of North America. He is responsible for establishing the company’s architectural road map and vision for distributed platforms and the Internet of Things. Bryant sets and shares Panasonic’s architectural vision across R&D projects and products developed in North America. Bryant joined Panasonic in 2005 as a Chief Software Architect of the Panasonic Electric Works Laboratory of America in Salt Lake City, Utah. He began his career in robotics and digital control at the University of Utah where he graduated in 1993 with a B.S. in Computer Science. Since then, his focus has been on software systems for robotic control, sensor networks, real-time graphics and distributed object systems. He has also supported development initiatives in computer networking and system design. Bryant is active in the Open Source community through the Linux Foundation as well as the OpenDOF Project and AllSeen Alliance. His research interests include distributed systems, protocol design and network security.
