DOCSLIB.ORG

Chapter 5 – Extending the Requirements Models Solutions to End-Of-Chapter Problems

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Chapter 5 – Extending the Requirements Models Solutions to End-Of-Chapter Problems Systems Analysis and Design in a Changing World, sixth edition 5-1 Chapter 5 – Extending the Requirements Models Solutions to End-of-Chapter Problems Review Questions 1. What are the models that describe use cases in more detail? Fully developed use case description, activity diagrams, and system sequence diagrams. 2. What two UML diagrams are used to model domain classes? Problem domain class diagram and state machine diagram. 3. Which part of a use case description can also be modeled by using an activity diagram? The “flow of activities” section. 4. Explain the difference between a use case and a scenario. Give a specific example of a use case with a few possible scenarios. A use case is the entire function or user goal or event. A scenario is one specific version or instance of that use case. From RMO we have Create customer account as a use case. But we might have Create online Customer account and Create instore customer account and even Create phone customer account as different scenarios. 5. List the parts or compartments of a fully developed use case description. Use case name Scenario Triggering event Brief description Actors Related use cases Stakeholders Preconditions Postconditions Flow of activities Exception conditions 6. Compare/contrast precondition and postcondition. A precondition describes the “states” of data and the system that must exist before the use case can begin. For example to add an item to a shopping cart, the item must exist in the database. A postcondition describes the states of data and the system that must exist after the use case completes. For example after Create a customer account use case, a customer account object (record) must exist. Systems Analysis and Design in a Changing World, sixth edition 5-2 7. Compare/contrast postcondition and exception condition. A post condition, as explained about describes states of the data and the system. An exception condition describes some non-normal situation in the processing, i.e. in the flow of activities, that must be handled in some way.. 8. Compare/contrast business process and flow of activities for a use case. Explain how an activity diagram can be used to model both. A business process is larger than a use case. A business process might include various manual business procedures both before and after the “business event” that causes the use case to occur. However, an activity diagram is a powerful model to describe all types of sequences of tasks and activities. The various swimlanes can represent various users or user groups as well as system activities. 9. What is the purpose of an SSD? What symbols are used in an SSD? An SSD (system sequence diagram) is used to describe the messages that flow into and out of a system, i.e. between the system and the use case user. The symbols include: Stick figure for the actor Box with object name for the system object Vertical dashed lines for object lifelines Horizontal arrows for messages Horizontal dashed arrows for return data Comment box for comments 10. What are the steps required to develop an SSD? 1. Identify the input messages (from the activity diagram) 2. Describe the input message using the SSD message syntax 3. Add message conditions such as looping or true/false conditions 4. Add all output message data 11. Write a complete SSD message from the actor to the system, with the actor asking the system to begin the process for updating information about a specific product. updateProductInformation (productID, updateInformation) 12. What is the name of the sequence diagram symbol used to represent the extension of an object throughout the duration of a use case? Lifeline or object lifeline 13. What are the two ways to show a returned value on a sequence diagram? Either with a return value on the left hand side of the equal (:=) sign, or with a return message shown by a dashed line and labeled with the return data. Systems Analysis and Design in a Changing World, sixth edition 5-3 14. What are two ways to show repetition on a sequence diagram? Either with an asterisk on the message label or a loop frame around the message(s). 15. What are the three types of frames used on a sequence diagram? Loop frame – repeat or loop the contents of the frame Opt frame – send or do not send the message based on true/false condition Alt frame – if-else alternative flows based on condition 16. What is the symbol for a true/false condition on a sequence diagram? A true/false condition is shown in brackets [ ] 17. What are the parameters of a message? The parameters represent the input data, i.e. the data that is being passed to the destination object. 18. List the primary steps for developing a SSD. Ooops, duplicate question. See question 10. 19. What is an object state? An object state is the state of being of an object, and is usually measured by a set of values. It is comparable to a status condition. 20. What is a state transition? A state transition is the movement of an object from one state to another state. 21. When considering requirements, states and state transitions are important for understanding which other diagram? States and Transitions are part of the state machine diagram for an object class. Therefore, they help to understand the objects in the class diagram. 22. What UML diagram is used to show the states and transitions for an object? States and Transitions are part of the state machine diagram, which describes the activity of the objects in an object class. 23. List the elements that make up a transition description. Which elements are optional? Systems Analysis and Design in a Changing World, sixth edition 5-4 Transition-name (parameters, ... ) [guard-condition] / action-expression Any of the three elements may be empty, i.e. are optional. 24. What is a composite state? What is it used for? A composite state is a high-level state in that it may have other states and transitions inside of it. It is used to represent concurrent states. For example, a printer may be in the “on” state, which is a composite state, and it may be “idle” which is an internal state within “on.” 25. What is meant by the term path? A path is a sequence of states and transitions. It may be a complete path to describe an entire origin to destination path, or it may be a “snippet” of a path and only contain a few states and transitions. 26. What is the purpose of a guard-condition? A guard-condition determines whether or not a transition can fire. Usually first the trigger fires to notify the transition that it should execute, but before it begins execution, it tests to see if the guard-condition is true. 27. Identify the models explained in this chapter and their relationship to one another. The two main models for requirements are the Use case model,which identifies the use cases or the “processes,” and the Domain model class diagram, which identifies the information or data for the system. The Use case diagram is supported by Use Case Descriptions, Activity diagrams, and System Sequence diagrams. The Domain model class diagram is supported by State machine diagrams. Systems Analysis and Design in a Changing World, sixth edition 5-5 Problems and Exercises 1. After reading the following narrative, do the following: i. Develop an activity diagram for each scenario. ii. Complete a fully developed use case description for each scenario. Contractor Sale activity diagram: Systems Analysis and Design in a Changing World, sixth edition 5-6 Contractor Sale fully developed use case description: Use Case Name: Create a new sale Scenario: Create new sale to a contractor (on account sale) Triggering Event: Contractor wants to purchase items. Brief Description: A contractor wants to purchase items. The clerk rings up the items and then adds them to the contractor’s account. Actors: Sales clerk Stakeholders: Sales clerk Accounting department Sales department Preconditions: Customer account must exist. Inventory items must exist. Postconditions: New sale is created. Sales line items are created and connected to the sale. Customer (contractor) account is updated. Flow of Activities: Actor System 1. Clerk enters contractor ID. 1.1 System validates contractor account. 2. Clerk enters each item. 2.1 System finds item in inventory, finds price, adds to 3. Clerk indicates the end of the sale. total. 3.1 System calculates total and 4. If contractor wants receipt, requests adds to contractor account. receipt. 4.1 System prints receipt. Exception 1.1 If contractor account is out of balance, treat this sale as a cash sale, or Conditions: stop process and send contractor to accounting clerk. 2.1 If system has information missing, sales clerk calls manager and manually enters information. 3.1 If contractor account balance is over the limit, treat as cash sale, cancel, or send contractor to accounting clerk. Systems Analysis and Design in a Changing World, sixth edition 5-7 Sale to public activity diagram: Systems Analysis and Design in a Changing World, sixth edition 5-8 Sale to public fully developed use case description: Use Case Name: Create a new sale Scenario: A new cash sale Triggering Event: Cash customer wants to purchase items. Brief Description: A cash customer wants to purchase items. The clerk enters the item ID, and the system creates a sales ticket. Customer pays with cash, check or credit card. Actors: Sales clerk Stakeholders: Sales clerk Accounting department Sales department Preconditions: Inventory items must exist. Postconditions: New sale is created.
Load more

Recommended publications
  • 07 Requirements What About RFP/RFB/Rfis?
    CMPSCI520/620 07 Requirements & UML Intro 07 Requirements SW Requirements Specification • Readings • How do we communicate the Requirements to others? • [cK99] Cris Kobryn, Co-Chair, “Introduction to UML: Structural and Use Case Modeling,” UML Revision Task Force Object Modeling with OMG UML Tutorial • It is common practice to capture them in an SRS Series © 1999-2001 OMG and Contributors: Crossmeta, EDS, IBM, Enea Data, • But an SRS doesn’t need to be a single paper document Hewlett-Packard, IntelliCorp, Kabira Technologies, Klasse Objecten, Rational Software, Telelogic, Unisys http://www.omg.org/technology/uml/uml_tutorial.htm • Purpose • [OSBB99] Gunnar Övergaard, Bran Selic, Conrad Bock and Morgan Björkande, “Behavioral Modeling,” UML Revision Task Force, Object Modeling with OMG UML • Contractual requirements Tutorial Series © 1999-2001 OMG and Contributors: Crossmeta, EDS, IBM, Enea elicitation Data, Hewlett-Packard, IntelliCorp, Kabira Technologies, Klasse Objecten, Rational • Baseline Software, Telelogic, Unisys http://www.omg.org/technology/uml/uml_tutorial.htm • for evaluating subsequent products • [laM01] Maciaszek, L.A. (2001): Requirements Analysis and System Design. • for change control requirements Developing Information Systems with UML, Addison Wesley Copyright © 2000 by analysis Addison Wesley • Audience • [cB04] Bock, Conrad, Advanced Analysis and Design with UML • Users, Purchasers requirements http://www.kabira.com/bock/ specification • [rM02] Miller, Randy, “Practical UML: A hands-on introduction for developers,”
    [Show full text]
  • Blurred Lines Between Role and Reality: a Phenomenological Study of Acting
    Antioch University AURA - Antioch University Repository and Archive Student & Alumni Scholarship, including Dissertations & Theses Dissertations & Theses 2019 Blurred Lines Between Role and Reality: A Phenomenological Study of Acting Gregory Hyppolyte Brown Follow this and additional works at: https://aura.antioch.edu/etds Part of the Psychology Commons BLURRED LINES BETWEEN ROLE AND REALITY: A PHENOMENOLOGICAL STUDY OF ACTING A Dissertation Presented to the Faculty of Antioch University Santa Barbara In partial fulfillment of the requirements for the the degree of DOCTOR OF PSYCHOLOGY In CLINICAL PSYCHOLOGY by GREGORY HIPPOLYTE BROWN August 2019 This dissertation, by Gregory Hippolyte Brown, has been approved by the committee members signed below who recommend that it be accepted by the faculty of Antioch University Santa Barbara in partial fulfillment of requirements for the degree of DOCTOR OF PSYCHOLOGY Dissertation Committee: _________________________ Brett Kia-Keating, Ed.D. Chairperson __________________________ Sharleen O‘ Brien, Ph.D. Second Faculty __________________________ Thalia R. Goldstein, Ph.D. External Expert ii Copyright © 2019 Gregory Hippolyte Brown iii Abstract When an actor plays a character in a film, they try to connect with the emotions and behavioral patterns of the scripted character. There is an absence of literature regarding how a role influences an actor’s life before, during, and after film production. This study examined how acting roles might influence an actor during times on set shooting a movie or television series as well as their personal life after the filming is finished. Additionally the study considered the psychological impact of embodying a role, and whether or not an actor ever has the feeling that the performed character has independent agency over the actor.
    [Show full text]
  • Sysml, the Language of MBSE Paul White
    Welcome to SysML, the Language of MBSE Paul White October 8, 2019 Brief Introduction About Myself • Work Experience • 2015 – Present: KIHOMAC / BAE – Layton, Utah • 2011 – 2015: Astronautics Corporation of America – Milwaukee, Wisconsin • 2001 – 2011: L-3 Communications – Greenville, Texas • 2000 – 2001: Hynix – Eugene, Oregon • 1999 – 2000: Raytheon – Greenville, Texas • Education • 2019: OMG OCSMP Model Builder—Fundamental Certification • 2011: Graduate Certification in Systems Engineering and Architecting – Stevens Institute of Technology • 1999 – 2004: M.S. Computer Science – Texas A&M University at Commerce • 1993 – 1998: B.S. Computer Science – Texas A&M University • INCOSE • Chapters: Wasatch (2015 – Present), Chicagoland (2011 – 2015), North Texas (2007 – 2011) • Conferences: WSRC (2018), GLRCs (2012-2017) • CSEP: (2017 – Present) • 2019 INCOSE Outstanding Service Award • 2019 INCOSE Wasatch -- Most Improved Chapter Award & Gold Circle Award • Utah Engineers Council (UEC) • 2019 & 2018 Engineer of the Year (INCOSE) for Utah Engineers Council (UEC) • Vice Chair • Family • Married 14 years • Three daughters (1, 12, & 10) 2 Introduction 3 Our Topics • Definitions and Expectations • SysML Overview • Basic Features of SysML • Modeling Tools and Techniques • Next Steps 4 What is Model-based Systems Engineering (MBSE)? Model-based systems engineering (MBSE) is “the formalized application of modeling to support system requirements, design, analysis, verification and validation activities beginning in the conceptual design phase and continuing throughout development and later life cycle phases.” -- INCOSE SE Vision 2020 5 What is Model-based Systems Engineering (MBSE)? “Formal systems modeling is standard practice for specifying, analyzing, designing, and verifying systems, and is fully integrated with other engineering models. System models are adapted to the application domain, and include a broad spectrum of models for representing all aspects of systems.
    [Show full text]
  • Modelling Interactions
    University of Toronto Department of Computer Science Lecture 15: Modelling System Interactions Interactions with the new system How will people interact with the system? When/Why will they interact with the system? Use Cases introduction to use cases identifying actors identifying cases Advanced features Sequence Diagrams Temporal ordering of events involved in a use case © 2004-5 Steve Easterbrook. This presentation is available free for non-commercial use with attribution under a creative commons license. 1 University of Toronto Department of Computer Science Moving towards specification What functions will the new system provide? How will people interact with it? Describe functions from a user’s perspective UML Use Cases Used to show: the functions to be provided by the system which actors will use which functions Each Use Case is: a pattern of behavior that the new system is required to exhibit a sequence of related actions performed by an actor and the system via a dialogue. An actor is: anything that needs to interact with the system: a person a role that different people may play another (external) system. © 2004-5 Steve Easterbrook. This presentation is available free for non-commercial use with attribution under a creative commons license. 2 University of Toronto Department of Computer Science Use Case Diagrams Capture the relationships between actors and Use Cases Change a client contact Campaign Staff contact Manager Add a new client Record client payment Accountant © 2004-5 Steve Easterbrook. This presentation is available free for non-commercial use with attribution under a creative commons license. 3 University of Toronto Department of Computer Science Notation for Use Case Diagrams Use case Change client contact Staff contact Actor Communication association System boundary © 2004-5 Steve Easterbrook.
    [Show full text]
  • Plantuml Language Reference Guide (Version 1.2021.2)
    Drawing UML with PlantUML PlantUML Language Reference Guide (Version 1.2021.2) PlantUML is a component that allows to quickly write : • Sequence diagram • Usecase diagram • Class diagram • Object diagram • Activity diagram • Component diagram • Deployment diagram • State diagram • Timing diagram The following non-UML diagrams are also supported: • JSON Data • YAML Data • Network diagram (nwdiag) • Wireframe graphical interface • Archimate diagram • Specification and Description Language (SDL) • Ditaa diagram • Gantt diagram • MindMap diagram • Work Breakdown Structure diagram • Mathematic with AsciiMath or JLaTeXMath notation • Entity Relationship diagram Diagrams are defined using a simple and intuitive language. 1 SEQUENCE DIAGRAM 1 Sequence Diagram 1.1 Basic examples The sequence -> is used to draw a message between two participants. Participants do not have to be explicitly declared. To have a dotted arrow, you use --> It is also possible to use <- and <--. That does not change the drawing, but may improve readability. Note that this is only true for sequence diagrams, rules are different for the other diagrams. @startuml Alice -> Bob: Authentication Request Bob --> Alice: Authentication Response Alice -> Bob: Another authentication Request Alice <-- Bob: Another authentication Response @enduml 1.2 Declaring participant If the keyword participant is used to declare a participant, more control on that participant is possible. The order of declaration will be the (default) order of display. Using these other keywords to declare participants
    [Show full text]
  • Methodological and Analytical Expertise in Socio-Technological
    Paper prepared for the Conference Proceedings of the International System Dynamics Conference in Washington DC USA, July, 2011 How does the Multi-Level Perspective help to enhance a System Dynamics analysis of a specific transition challenge? Silvia Ulli-Beer 1, Stefan Grösser 2 and Alexander Wokaun 1 [email protected] ; [email protected] ; [email protected] 1Paul Scherrer Institut, Dynamics of Innovative Systems, 5232 Villigen PSI, Switzerland 2University of St. Gallen, Institute of Management (IfB), Dufourstrasse 40a, 9000 St. Gallen, Switzerland 2University of Bern, Interdisciplinary Center for General Ecology (IKAÖ), Schanzeneckstr. 1, 3001 Bern, Switzerland Abstract This paper addresses the challenge of identifying adequate theoretical starting points for problem oriented simulation studies of socio-technical transitions towards near fossil free energy services e.g. for housing and transportation. The identification of adequate starting points for simulation studies is becoming increasingly important for the generalization of simulation results as well as for theory refinement. We found that the Multi-Level Perspective (MLP) offers a helpful language for a modelling experiment based in a feedback perspective. This allows the conceptualization of a socio-technical transition challenge departing from an inter-subjective and hence scientific starting point. In addition feedback modelling appears to be a promising mathematical analysis approach that helps to substantiate the MLP. We have seen that the insights of the simulation experiment corroborate basic assumptions of the MLP concerning multi-level alignment processes but also discriminate the decisive determinants and governance mechanisms that explain radical innovation and subsequently the creation of path dependency. 1. Introduction This paper addresses the challenge of identifying adequate theoretical starting points for problem oriented simulation studies of socio-technical transitions towards near fossil free energy services e.g.
    [Show full text]
  • Define Your Project and System Requirements - a Guide for Program Managers and Directors
    Define your project and system requirements - A guide for program managers and directors Disease Surveillance [epidemic determined] Notify Local Health Dept. [no significant activity] Assess Sensitivity of Measurement Georgia Department of Human Resources Division of Public Health Office of Health Information & Policy Define your project and system requirements - A guide for program managers and directors Disease Surveillance [epidemic determined] Notify Local Health Dept. [no significant activity] Assess Sensitivity of Measurement A synopsis of Applying Use Cases, Prepared by Gordon R. Freymann, MPH Office of Health Information & Policy Division of Public Health Georgia Department of Human Resources Publication # DPH02.92 Office of Health Information & Policy Division of Public Health Georgia Department of Human Resources Page 2 of 18 Define your project and system requirements - A guide for program managers and directors Inception Phase .......................................................................................................... 3 Identifying system boundaries...................................................................................... 4 Identifying Actors........................................................................................................ 4 Identifying Use Cases ...................................................................................... ........... 4 Elaboration Phase ....................................................................................................... 6 Primary
    [Show full text]
  • Ten Strategies of a World-Class Cybersecurity Operations Center Conveys MITRE’S Expertise on Accumulated Expertise on Enterprise-Grade Computer Network Defense
    Bleed rule--remove from file Bleed rule--remove from file MITRE’s accumulated Ten Strategies of a World-Class Cybersecurity Operations Center conveys MITRE’s expertise on accumulated expertise on enterprise-grade computer network defense. It covers ten key qualities enterprise- grade of leading Cybersecurity Operations Centers (CSOCs), ranging from their structure and organization, computer MITRE network to processes that best enable effective and efficient operations, to approaches that extract maximum defense Ten Strategies of a World-Class value from CSOC technology investments. This book offers perspective and context for key decision Cybersecurity Operations Center points in structuring a CSOC and shows how to: • Find the right size and structure for the CSOC team Cybersecurity Operations Center a World-Class of Strategies Ten The MITRE Corporation is • Achieve effective placement within a larger organization that a not-for-profit organization enables CSOC operations that operates federally funded • Attract, retain, and grow the right staff and skills research and development • Prepare the CSOC team, technologies, and processes for agile, centers (FFRDCs). FFRDCs threat-based response are unique organizations that • Architect for large-scale data collection and analysis with a assist the U.S. government with limited budget scientific research and analysis, • Prioritize sensor placement and data feed choices across development and acquisition, enteprise systems, enclaves, networks, and perimeters and systems engineering and integration. We’re proud to have If you manage, work in, or are standing up a CSOC, this book is for you. served the public interest for It is also available on MITRE’s website, www.mitre.org. more than 50 years.
    [Show full text]
  • Plantuml Language Reference Guide
    Drawing UML with PlantUML Language Reference Guide (Version 5737) PlantUML is an Open Source project that allows to quickly write: • Sequence diagram, • Usecase diagram, • Class diagram, • Activity diagram, • Component diagram, • State diagram, • Object diagram. Diagrams are defined using a simple and intuitive language. 1 SEQUENCE DIAGRAM 1 Sequence Diagram 1.1 Basic examples Every UML description must start by @startuml and must finish by @enduml. The sequence ”->” is used to draw a message between two participants. Participants do not have to be explicitly declared. To have a dotted arrow, you use ”-->”. It is also possible to use ”<-” and ”<--”. That does not change the drawing, but may improve readability. Example: @startuml Alice -> Bob: Authentication Request Bob --> Alice: Authentication Response Alice -> Bob: Another authentication Request Alice <-- Bob: another authentication Response @enduml To use asynchronous message, you can use ”->>” or ”<<-”. @startuml Alice -> Bob: synchronous call Alice ->> Bob: asynchronous call @enduml PlantUML : Language Reference Guide, December 11, 2010 (Version 5737) 1 of 96 1.2 Declaring participant 1 SEQUENCE DIAGRAM 1.2 Declaring participant It is possible to change participant order using the participant keyword. It is also possible to use the actor keyword to use a stickman instead of a box for the participant. You can rename a participant using the as keyword. You can also change the background color of actor or participant, using html code or color name. Everything that starts with simple quote ' is a comment. @startuml actor Bob #red ' The only difference between actor and participant is the drawing participant Alice participant "I have a really\nlong name" as L #99FF99 Alice->Bob: Authentication Request Bob->Alice: Authentication Response Bob->L: Log transaction @enduml PlantUML : Language Reference Guide, December 11, 2010 (Version 5737) 2 of 96 1.3 Use non-letters in participants 1 SEQUENCE DIAGRAM 1.3 Use non-letters in participants You can use quotes to define participants.
    [Show full text]
  • Tram - Trng - Modeling - UML Startup - All.Pages 2 1991 Booch 91
    UML Start-Up Training UB1 Index History Overview Diagrams Use Case Diagram Sequence Diagram Activity Diagram Class Diagram Composite Structure Diagram UML State Machine Diagram This training course is designed with the intention to teach UML in not Package Diagram longer than a day. Yes UML is a complicated language with a lot of diagrams, model elements, a complex syntax and semantic; and most people claim that it takes a long time to learn that language. But: if we concentrate our efforts to the most important part of the language you will be able to become familiar with it in a day. And: use it frequently, then you’ll get the less important things by use and by reading a good book: the standard (visit the web pages from OMG and you’ll manage to download the standard, it’s free of charge). History The “OO tower” of Babel In the early Nineties there was a vast amount of competing object oriented modeling approaches together with corresponding kinds of diagrams and CASE environments which, sometimes more and sometimes less, differ from each other. Examples: Object-Oriented Analysis (OOA): Coad-Yourdon 1991 Object-Oriented Design (OOD): Booch 1991 Object Modeling Technique (OMT): Rumbaugh 1991 OO Software Engineering (OOSE): Jacobson 1992 Fusion: Coleman 1994 The Idea: Unified Modeling Language The idea of Grady Booch: A number of OO modeling dialects is replaced by a standardized language in order to bury unnecessary ditch (and religious) wars in the OO environment unite advantages of different modeling approaches relieve potential users of being spoilt for choice provide for the preconditions for data exchange between OO tools enable close integration of OO tools reduce dependencies of users of one supplier release tool manufacturers of the support of many approaches.
    [Show full text]
  • Real Time UML
    Fr 5 January 22th-26th, 2007, Munich/Germany Real Time UML Bruce Powel Douglass Organized by: Lindlaustr. 2c, 53842 Troisdorf, Tel.: +49 (0)2241 2341-100, Fax.: +49 (0)2241 2341-199 www.oopconference.com RealReal--TimeTime UMLUML Bruce Powel Douglass, PhD Chief Evangelist Telelogic Systems and Software Modeling Division www.telelogic.com/modeling groups.yahoo.com/group/RT-UML 1 Real-Time UML © Telelogic AB Basics of UML • What is UML? – How do we capture requirements using UML? – How do we describe structure using UML? – How do we model communication using UML? – How do we describe behavior using UML? • The “Real-Time UML” Profile • The Harmony Process 2 Real-Time UML © Telelogic AB What is UML? 3 Real-Time UML © Telelogic AB What is UML? • Unified Modeling Language • Comprehensive full life-cycle 3rd Generation modeling language – Standardized in 1997 by the OMG – Created by a consortium of 12 companies from various domains – Telelogic/I-Logix a key contributor to the UML including the definition of behavioral modeling • Incorporates state of the art Software and Systems A&D concepts • Matches the growing complexity of real-time systems – Large scale systems, Networking, Web enabling, Data management • Extensible and configurable • Unprecedented inter-disciplinary market penetration – Used for both software and systems engineering • UML 2.0 is latest version (2.1 in process…) 4 Real-Time UML © Telelogic AB UML supports Key Technologies for Development Iterative Development Real-Time Frameworks Visual Modeling Automated Requirements-
    [Show full text]
  • Fakulta Informatiky UML Modeling Tools for Blind People Bakalářská
    Masarykova univerzita Fakulta informatiky UML modeling tools for blind people Bakalářská práce Lukáš Tyrychtr 2017 MASARYKOVA UNIVERZITA Fakulta informatiky ZADÁNÍ BAKALÁŘSKÉ PRÁCE Student: Lukáš Tyrychtr Program: Aplikovaná informatika Obor: Aplikovaná informatika Specializace: Bez specializace Garant oboru: prof. RNDr. Jiří Barnat, Ph.D. Vedoucí práce: Mgr. Dalibor Toth Katedra: Katedra počítačových systémů a komunikací Název práce: Nástroje pro UML modelování pro nevidomé Název práce anglicky: UML modeling tools for blind people Zadání: The thesis will focus on software engineering modeling tools for blind people, mainly at com•monly used models -UML and ERD (Plant UML, bachelor thesis of Bc. Mikulášek -Models of Structured Analysis for Blind Persons -2009). Student will evaluate identified tools and he will also try to contact another similar centers which cooperate in this domain (e.g. Karlsruhe Institute of Technology, Tsukuba University of Technology). The thesis will also contain Plant UML tool outputs evaluation in three categories -students of Software engineering at Faculty of Informatics, MU, Brno; lecturers of the same course; person without UML knowledge (e.g. customer) The thesis will contain short summary (2 standardized pages) of results in English (in case it will not be written in English). Literatura: ARLOW, Jim a Ila NEUSTADT. UML a unifikovaný proces vývoje aplikací : průvodce ana­lýzou a návrhem objektově orientovaného softwaru. Brno: Computer Press, 2003. xiii, 387. ISBN 807226947X. FOWLER, Martin a Kendall SCOTT. UML distilled : a brief guide to the standard object mode•ling language. 2nd ed. Boston: Addison-Wesley, 2000. xix, 186 s. ISBN 0-201-65783-X. Zadání bylo schváleno prostřednictvím IS MU. Prohlašuji, že tato práce je mým původním autorským dílem, které jsem vypracoval(a) samostatně.
    [Show full text]