Search icon CANCEL
Subscription
0
Cart icon
Cart
Close icon
You have no products in your basket yet
Save more on your purchases!
Savings automatically calculated. No voucher code required
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletters
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Security-Driven Software Development

You're reading from  Security-Driven Software Development

Product type Book
Published in Mar 2024
Publisher Packt
ISBN-13 9781835462836
Pages 262 pages
Edition 1st Edition
Languages
Author (1):
Aspen Olmsted Aspen Olmsted
Profile icon Aspen Olmsted
Toc

Table of Contents (20) Chapters close

Preface 1. Part 1: Modeling a Secure Application
2. Chapter 1: Security Principles 3. Chapter 2: Designing a Secure Functional Model 4. Chapter 3: Designing a Secure Object Model 5. Chapter 4: Designing a Secure Dynamic Model 6. Chapter 5: Designing a Secure System Model 7. Chapter 6: Threat Modeling 8. Part 2: Mitigating Risks in Implementation
9. Chapter 7: Authentication and Authorization 10. Chapter 8: Input Validation and Sanitization 11. Chapter 9: Standard Web Application Vulnerabilities 12. Chapter 10: Database Security 13. Part 3: Security Validation
14. Chapter 11: Unit Testing 15. Chapter 12: Regression Testing 16. Chapter 13: Integration, System, and Acceptance Testing 17. Chapter 14: Software Penetration Testing 18. Index 19. Other Books You May Enjoy

Object behavior

Designing object behavior is a critical aspect of object-oriented software development. Object behavior refers to how objects of a class interact with one another and the system as a whole. In our object identification in the previous chapter, we listed some operations, but we want to dig in and discover how our objects interact. Here are some considerations for designing object behavior:

  • Identify objects and classes:
    • You can begin by identifying the objects and classes in your system. These represent the entities and concepts that your software will model. We focused on this in Chapter 3. One example from our event ticketing system is the Person object, which represents the patrons’ purchasing tickets. We also have previously identified Orders, Tickets, and Payment classes. Figure 4.17 later in this chapter shows an updated version of the UML class diagram from Chapter 3.
  • Define object responsibilities:
    • Determine what each object’s responsibilities...
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 €14.99/month. Cancel anytime}