1 / 14

Object-Oriented Analysis

Object-Oriented Analysis. Domain Analysis. class taxononmies. techncial literature. DOMAIN. SOURCES OF. reuse standards. DOMAIN. ANALYSIS. existing applications. DOMAIN. functional models. ANALYSIS. MODEL. KNOWLEDGE. customer surveys. domain languages. expert advice.

elke
Télécharger la présentation

Object-Oriented Analysis

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Object-Oriented Analysis

  2. Domain Analysis class taxononmies techncial literature DOMAIN SOURCES OF reuse standards DOMAIN ANALYSIS existing applications DOMAIN functional models ANALYSIS MODEL KNOWLEDGE customer surveys domain languages expert advice current/future requirements

  3. OOA- A Generic View • Mendefinisikan use case • Menentukan kandidat class • Menentukan hubungan antar class • Mendefinisikan hirarki class • Identifikasi atribut setiap class • Menentukan operasi bagi atribut • Ulangi proses pertama hingga ke 6

  4. Use Cases • Skenario yg menggambarkan urutan kejadian yg dilakukan oleh sistem • Actor merepresntasikan peranan orang atau peralatan yg menggunakan fungsi-fungsi dari sistem • Users dapat memainkan sejumlah peran yg berbeda dalam sebuah skenario

  5. Developing a Use Case • Apa tugas atau fungsi utama dari aktor • Informasi apa yg akan diperoleh, dihasilkan atau diubah oleh actor • Bagaimana actor memberitahukan kepada sistem berkaitan dengan perubahan dari lingkungan luar ? • Informasi apa yg akan diperoleh actor dari sistem

  6. common attributes common operations essential requirements Selecting Classes—Criteria retained information needed services

  7. Unified Modeling Language (UML) User model view. This view represents the system (product) from the user’s (called “actors” in UML) perspective. Structural model view. Data and functionality is viewed from inside the system. That is, static structure (classes, objects, and relationships) is modeled. Behavioral model view. This part of the analysis model represents the dynamic or behavioral aspects of the system. Implementation model view. The structural and behavioral aspects of the system are represented as they are to be built. Environment model view. The structural and behavioral aspects of the environment in which the system is to be implemented are represented.

  8. UML: Use-Case Diagram

  9. UML: Class Diagrams Generalization-specialization Composite aggregates

  10. UML: Package Reference

  11. Relationships between Objects

  12. Object-Behavior Model 1. Evaluate all use-cases to fully understand the sequence of interaction within the system. 2. Identify events that drive the interaction sequence and understand how these events relate to specific objects. 3. Create an event trace [RUM91] for each use-case. 4. Build a state transition diagram for the system 5. Review the object-behavior model to verify accuracy and consistency

  13. UML: State Transition

  14. UML: Event Trace

More Related