Search icon CANCEL
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
The Complete Edition - Software Engineering for Real-Time Systems

You're reading from   The Complete Edition - Software Engineering for Real-Time Systems A software engineering perspective toward designing real-time systems

Arrow left icon
Product type Paperback
Published in Dec 2019
Publisher
ISBN-13 9781839216589
Length 824 pages
Edition 1st Edition
Languages
Arrow right icon
Author (1):
Arrow left icon
Jim Cooling Jim Cooling
Author Profile Icon Jim Cooling
Jim Cooling
Arrow right icon
View More author details
Toc

Table of Contents (16) Chapters Close

Preface
1. Real-Time Systems – Setting the Scene 2. The Search for Dependable Software FREE CHAPTER 3. First Steps – Requirements Analysis and Specification 4. Software and Program Design Concepts 5. Multitasking Systems – an Introduction 6. Diagramming – an Introduction 7. Practical Diagramming Methods 8. Designing and Constructing Software – Code-Related Issues 9. Software Analysis and Design – Methods and Methodologies 10. Analyzing and Testing Source Code 11. Development Tools 12. Mission-Critical and Safety-Critical Systems 13. Performance Engineering 14. Documentation Glossary of terms

9.7 Agile Software Development

9.7.1 Introduction and Basic Concepts

The core concepts of Agile software development methods can be simply and clearly by reference to Figure 9.66. Here, Figure 9.66(a), we have the classical Waterfall software development process. First, the system requirements are analyzed and, using this information, the software is designed. This is followed by the implementation phase: coding, compilation, and installation of machine code into the target. Finally, the installed software is tested to eliminate bugs, improve performance, and check that it meets its requirements.

Figure 9.66: Agile versus Waterfall software development methods

Well, that seems fine and reasonable. However, its detractors point out that this approach has a number of serious flaws:

  • It is a very rigid technique, lacking the flexibility to incorporate requirement changes during the development process.
  • There isn't any way, during the development...
lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime