The chapters in this part explain how to model your information systems in PowerDesigner®.
Getting Started with Object-Oriented Modeling
An object-oriented model (OOM) helps you analyze an information system through use cases, structural and behavioral analyses, and in terms of deployment, using the Unified Modeling Language (UML). You can model, reverse-engineer, and generate for Java, .NET and other languages.
Use Case Diagrams
A use case diagram is a UML diagram that provides a graphical view of the requirements of your system, and helps you identify how users interact with it.
Structural Diagrams
The diagrams in this chapter allow you to model the static structure of your system. PowerDesigner provides three types of diagrams for modeling your system in this way, each of which offers a different view of your objects and their relationships:
Dynamic Diagrams
The diagrams in this chapter allow you to model the dynamic behavior of your system, how its objects interact at run-time. PowerDesigner provides four types of diagrams for modeling your system in this way:
Implementation Diagrams
The diagrams in this chapter allow you to model the physical environment of your system, and how its components will be deployed. PowerDesigner provides two types of diagrams for modeling your system in this way:
Web Services
A Web service is a service offered via the web. The principle on which a Web service works is the following: a business application sends a request to a service at a given URL address. The request can use the SOAP protocol over HTTP. The service receives the request, processes it, and returns a response. An example that is most commonly used for a Web service is a stock quote service in which the request asks for the price of a specific stock and the response gives the stock price.
Created January 30, 2012.To comment on this topic, go to:
DocCommentXchange.