Skip to content

Eagle0eye/Head-First-Object-Oriented-Analysis-and-Design

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

9 Commits
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Head First Object-Oriented Analysis and Design

Chapter 1 - Well-Designed Apps Rock

Introduction:

This chapter aims to teach you how to think to build a Great Software example: a Rick Application.

Objectives:

Phase 1:

Phase 2:

Phase 3:

Conclusion:

Chapter 2 - Gathering Requirements

Introduction:

Phase 1: Understanding Requirements

  • Understanding what the customer needs very well.
  • Ask the Customer about details if it's exist.
  • How to write Use Cases:
    • Clear Value:
      Every use case must have a clear value to the system. If the use case doesn't help customers achieve their goals, then the use case isn't of much use.
    • Start and Stop:
      Every use case must have a definite starting and stopping point. Something must begin the process, and then there must be a condition that indicates that the process is complete
    • External Initionators:
      Every use case is started off by an external initiator, outside of the system. Sometimes that initiator is a person, but it could be anything outside of the system.
  • Imeplemenadtion:
    • Purpose Screenshot
      Create DogDoor Class
      Create Remote Class
      Run Code

Phase 2:

Phase 3:

Conclusion: