Integrating Hardware (Waterfall) and Software (Agile) Development
•
1 like•2,225 views
Integrating hardware development processes (using the Waterfall method / V-model) and Agile software development. This presentation explains the basics of the V-model and how it has evolved into an iterative model, but also tells you about managing hardware and software lifecycle processes in a single release. Then, a live demonstration shows you how to integrate these lifecycles (xLM) in practice.
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (15)
Similar to Integrating Hardware (Waterfall) and Software (Agile) Development
Similar to Integrating Hardware (Waterfall) and Software (Agile) Development (20)
More from Intland Software GmbH
More from Intland Software GmbH (20)
Recently uploaded
Recently uploaded (20)
Integrating Hardware (Waterfall) and Software (Agile) Development
- 1. Integrating Hardware (Waterfall) and Software (Agile) Development Eva Johnson and Sandor Szabo 6 May, 2015
- 2. 2 Agenda 1. Introduction of Intland Software 2. Waterfall in a nutshell 3. Agile in a nutshell 4. Lifecycle xLM with Hardware and Software 5. Release products with hardware and software components 6. Live demo of codeBeamer ALM
- 3. 3 Integrating Hardware (Waterfall) and Software (Agile) Development Webinar info o Live demonstration will be followed by a Q&A session o Webinar recording will be available at www.intland.com/webinars/ o Please register to our upcoming webinars o SAFe – Scaled Agile Framework in practice
- 4. 4 o Founded in 1998 o Headquarters in Stuttgart, Germany o Office in Silicon Valley, USA o Our ALM solution includes: • Requirements Management • Software Development Management • QA & Test Management • Demand Management • IT Operations (DevOps) Intland Software Introduction
- 6. 6 Integrating Hardware (Waterfall) and Software (Agile) Development Waterfall in a nutshell • Waterfall is a popular development model for software engineering. • It is in use since the 1960’s for large scale projects. • Long delivery cycle, separate testing phase and requirements with no change. • Waterfall model describes a development method that is linear and sequential. • Once a phase of development is completed, the development moves to the next phase. Requirements Design Implementation Verification Maintenance
- 7. 7 Hardware (Waterfall) and Software (Agile) Development Evolution of Waterfall Waterfall with overlapping phases The traditional Waterfall / V-model Waterfall / V-model with Agile implementation
- 8. 8 Hardware (Waterfall) and Software (Agile) Development Pros vs. cons Traditional Waterfall Waterfall with Agile software implementation Waterfall Model with overlapping phases Pros Simple and easy to understand and use Agile benefit in developing software Fully leverage of Agile benefits Each phase has specific deliverables Change do not require changes in other discipline Issues can be discovered earlier in the software development Each phase is processed and completed one at a time Minimization of re-work and a better final product Cons Very difficult to make changes Benefits limited to software Changing requirements across the teams Working software is produced at the end of the life cycle Difficult to make changes (except software) Careful to avoid iterating back to an earlier phase High amounts of risk and uncertainty Avoid repeating too many iterations
- 9. 9 • What is Agile? “Agile is a time boxed, iterative approach to software delivery that builds software incrementally from the start of the project, instead of trying to deliver it all at once near the end.” (agilenuteshell.com) Integrating Hardware (Waterfall) and Software (Agile) Development Agile in a nutshell – The Agile Manifesto Individuals and interactions over Processes and tools Customer collaboration over Contract negotiation Working software over Comprehensive documentation Responding to change over Following a plan “That is, while there is value in the items on the right, we value the items on the left more” (Agile Manifesto)
- 10. 10 Integrating Hardware (Waterfall) and Software (Agile) Development Benefits of Agile
- 11. 11 Hardware (Waterfall) and Software (Agile) Development Managing Hardware and Software together Product Embedded software Embedded software Embedded software Connectivity Connectivity Internet Of Things Smart product Smart, connected product Product system IoT, Industry 4 1960
- 12. 12 Integrating Hardware (Waterfall) and Software (Agile) Development Lifecycle xLM with Hardware and Software
- 13. 13 Hardware (Waterfall) and Software (Agile) Development Release products with hardware and software components Software Development Team: - Developer - Tester - Scrum Master Team 1 Team 2 Team 3 Product Release Team 4 Hardware Development Team: - Requirements Engineer - System Engineer - Architect - Programmer - Tester Team Level Program Level Product Manager Product Owner DevOps Release Manager
- 14. 14 Watch our live demo now!
- 15. Thank you for your attention! Any questions? sales@intland.com We are looking forward to hearing from you!
Editor's Notes
- But, before we jump off to our presentation, let me just quickly tell you about the structure of this webinar. After the live demonstration, where we will show you how we support agile and waterfall development for hardware and software, we will start a Q&A session. A recording of today’s webinar will be available on our website soon after the webinar. And once you’re visiting our webpage, make sure you’ll browse through our upcoming webinars as wel (Last time we talked about SAFe)
- The Waterfall methodology is a popular development model for software engineering and is in use since the 1960’s for large scale projects. Waterfall has a ong delivery cycle and a separate testing phase and requirements with no change. Also, Waterfall model describes a development method that has a linear and sequential design process. The traditional waterfall methodology treats analysis of the requirements, design, implementation, verification and maintenance. In the Requirements phase all the requirements are collected. The Design phase is differentiated into the subphases Logical Design and Physical Design. In the Logical Design phase, the system analyst uses the information which has been collected in the requirements phase to design the system and transofms them into the physical design dependent on the specification of hardware and software technologies. In the implementation phase, the source code is written. Once a phase of development is completed, the development moves to the next phase. The next phase verification ist he phase where the project meets customer expectations. During the Maintenance phase, the customer is using the application which has been developed.
- This slide shall give you an overview on what is agile and what are the principals behind agile development. Per definition from the agilenuteshell.com, agile is a time boxed, iterative approach to software delivery that builds software incrementally from the start of the project, instead of trying to deliver it all at once near the end. But the agile approach can and is being applied more and more to the development of products. It works by breaking projects down into little bits of user functionality called user stories, prioritizing them, and then continuously delivering them in short two week cycles called iterations. User stories are features which the clients might one day like to see in their software. Therefore the agile manifesto was created by a group of experienced people who just wanted to create better methods to create software. These are the following four fundamental main concepts in the agile manifesto: Individuals and interactions over processes and tools Customer collaboration over contract negotiation Working software over comprehensive documentation Responding to change over following a plan Basically the items on the right are waterfall. One of the myths of the Agile movement is that documentation is not required or useful. It is true that one of the core values within the Agile Manifesto is "Working Software over Comprehensive Documentation." However, note the word "over" in this statement. The Manifesto is not saying no to any kind of documentation; it's saying there is a preference for working software over documentation. The goal is to remove barriers and defects from the system and leave things that add value. If your organization is creating lengthy documents to produce any kind of products and you're still struggling to release them on time and also within your budget, then ask of what it will take to drive value to the client. Also, the agile manifesto focuses on self-organizing and self-correcting teams to drive quality and efficiency in the system. So this manifesto, who was created by that group of people, is already part of their organisation and they say that the value in the items on the left handside are much more than on the left side. Basically there are also values in the items on the right handside, but in order to reach much more value, there is more need to put effort into the key concepts to achieve these values. Instead of treating the fixed stages like in the waterfall, Agilists believe that the phases are continuous activities. So, by doing them continuously, the quality improves because testing starts from day one, ensuring that bugs are found earlier in the process. In addition to that, Changes can be made after the initial planning phase, and as the client makes changes in the requirement the program can be re-written easily. There is a much closer relationship between the customer and the developer. Also the visibility is enhanced and The product itself is released much faster. Risk is reduced because you are able to get feedback early, and you can meet customer’s expectations
- In the past (1960), products used to have just a hardware component only,e.g. build a car Products are getting smarter Nowadays, products also have software components As we are in the age of IoT, many companies has to face the challenge how to combine both HW and SW components into their product
- Integrating and managing these interconnected, overlapping innovation lifecycles is a challenge faced by a growing number of companies. We have identified three dimensions of the integration that organizations developing IoT-enabled products will have to deal with: Integration of Suppliers – In order to be able to manage the immense complexity introduced by IoT, companies will have to strengthen their ties with suppliers, not only involving them at certain stages of the lifecycle, but instead collaborating with them throughout the development and maintenance of products. Integration of Lifecycles – As mentioned above, interrelated and overlapping lifecycles necessitate a new management approach… Integration of Tools and Technologies – … and to support the new approach and enable the management of the overarching lifecycle, previously disparate tools and technologies will have to be holistically integrated. With all three dimensions of integration, managing the various sub-lifecycles (xLM) of the overarching product development process can be greatly supported by a platform that helps combine these individual approaches, tools and lifecycles. Due to its high integrability and ability to manage high levels of complexity, codeBeamer is a solution that is successfully used by many companies globally to manage such complicated processes. The term ‘xLM’ is used to refer to the single, overarching lifecycle integrating product, innovation, development and service lifecycles. As ALM for Software development with different lifecycle As PLM for hardware development with another lifecycle ALM (Application Lifecycle Management) and PLM (Product Lifecycle Management) are converging XLM: Now you see interconnected lifecycles of innovation and development. On the top left you see demand management. It helps you to decide about projects that is best for your company. Based on the demand you can define your requirements and your system architecture. As you could see, you are going to develop the different layers parallel but separately. At the end, you need to integrate them, run some testing. If everything looks all right, you will have your releases.
- Slide gives an overview how we implemented the demo project for today‘s webinar Many self-organized Teams can work with different methodologies such as Agile or Waterfall as each of them has advantages and disadvantages E.g. 2 Agile Teams for software and 2 waterfall team for hardware development The continuous delivery is called Agile Release Train in the Program Level The Program level aligns the teams to form an Agile Release Train With our release mechanism, we can combine and interconnect many development teams from the team level and they can work together on the release Different roles: Release Manager is responsible for the product release who assists with managing and planning releases for the agile Release Train, DevOps enables more frequent deployment, shorter time to market, reduce number of bugs and increase the product quality Software Development Team consists of Developers and Testers, and each development Team has a Scrum Master. Product Owner, who is also member of the team, can support many agile teams and he is responsible for defining and prioritizing the team backlog and also streamline the execution of the prioritzed programs Waterfall team consists of Requirements Engineer, System Engineer, Architect, Programmer, System Tester and Trainer