Abstract
This chapter discusses the ways of improving communication in system analysis and design to clarify and solve problems through modeling. Unified Modeling Language (UML) is a notation that is employed towards the goal of defining and understanding a problem so that a solution can be identified. The Object Management Group (OMG) claim that “the UML is a language for specifying, visualizing, constructing, and documenting the artifacts of software systems, as well as for business modeling and other nonsoftware systems.”. The practical issues faced by people in adopting UML are presented. A case study that involves elements of business and systems modeling is presented. The key characteristics of this case study include identification of appropriate problem scope and clarification of business requirements. The cross-references between UML diagrams across the system development lifecycle are analyzed. The timing and synchronization information and importance of modeling interactions and their implications are described.
Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
