• Create BookmarkCreate Bookmark
  • Create Note or TagCreate Note or Tag
  • PrintPrint
Share this Page URL
Help

Chapter 20. Diagramming Software Systems > Modeling Software Systems Using UML

Modeling Software Systems Using UML

UML specifies, constructs, visualizes, and documents a software system. Many teams are adopting UML for its life cycle approach to modeling software development and ability to represent everything from analyzing requirements and use cases to system implementation. Like blueprints, UML diagrams help teams visualize a system’s architecture at each step in the development process, which typically includes the following phases:

  • Analyze use cases To describe the interactions between external actors and your system, you can create a use case diagram that depicts system requirements and the terminology used in the domain area.

  • Analyze the domain To provide a conceptual understanding of the objects and relationships in the real world that your system represents, you can create conceptual (also called object) static structure diagrams and sequence diagrams. To understand the life cycle of an object, you can create activity and statechart diagrams as well.

  • Define design requirements To develop a programming solution that meets the use case and domain requirements, you can create collaboration diagrams to determine how objects will communicate and class static structure diagrams to define the classes that you will implement in the software.

  • Plan the implementation To describe the physical and component structure of the development environment, you can create component diagrams and deployment diagrams.


PREVIEW

                                                                          

Not a subscriber?

Start A Free Trial


  
  • Creative Edge
  • Create BookmarkCreate Bookmark
  • Create Note or TagCreate Note or Tag
  • PrintPrint