Transcript: Other relations : Inculde and Extend relationships Relationship between classifiers Represented by solid lines Arrowheads indicate invocations Behavior Classifier Specifies a Role An Interaction with the subject Behavior Classifier Sequence of actions performed by one or more subjects Collaboration with one or more actions Provides a result Definition By Galiano Folco, Jeannette Antoine, Demogue Anthony, Gasparini Leandro, Da Silva Mathieu Unified Modeling Language (UML): General-purpose, developmental, modeling language. It specifies: Requirements Functionality Environment PROJECT BASED LEARNING Use Case Diagram Actors System boundary / Subject Multiplicity Associations Inculde and extend relationship Specialization of class diagrams Two functions Behavior Diagram : User interaction with system Structure Diagram : User and use cases relationship Diagram elements Associations "Use case diagrams, are used to define and analyze a set of actions that one or many systems should perform in collaboration with external users." (uml-diagrams.org) Generalization sub classes inherit proprieties and behaviors sub classes can override behaviors Use Cases Actors Can be a : Human User System Hardware
Transcript: Subject 1 Subject 1 use overview to show relations is important is important too Conclusion Subject 2 zoom in, and add details to these Frames is important Understand a Topic is important Subject 3 is important Subject 1 is here
Transcript: Media CDC Safe Zones Pilot/ Driver Army Traveling Time Population Airports/ Water Shortest Route President Hospital Location
Transcript: include extend system boundary association Genecalization companents: actors use case use case diagrams A use-case digram is asek of use case Ause-case is model of the interaction between describing aset of user scenarios capturing user requirements Use case Diagrams use case diagrams
Transcript: Understand a Topic Subject 1 Subject 1 Subject 1 use overview to show relations is important is important too Conclusion Subject 2 zoom in, and add details to these Frames is important is important Subject 3 is important is here
Transcript: Algorithm Team Paul Arik Main problems: Company Knowledge is not managed well enough We tackle many new problems that require research without knowldege of the effort to solve Many projects/products delivered at the same time Dan Judith Algorithm team Scientific operation I'm responsible for delivering CytoMETby July 31 We may not deliver on time! and that's not the first time we miss the due date Hi there! :) Don't have too much time to write down my problems, as I'm supporting 3 work streams, and developing CytoReason's FiT (mouse-2-human) technology "I have problems with the data"! Need the algo team support I'm too busy working with Dan from SW team on CytoMET. BTW- "I wonder if Judith asked another project team for help on that matter" I wish Arik could help me on this ... (I know he can't) SW development Next step: Q&A Process with the algo team dedicated for the project team members Consider this issue for future deals (add more time) Try to solve the problems internally before reaching out to the algorithm team Pass some of the risk to the project team - they will accept half-baked methods BD need to estimate the flexibility of a project (start/end/date) of a project Solutions: Damage control decisions Knowledge management & training (Shadowing vs CR school + training check-list) At the end of every project/phase - need to provide a summary, taking etc Save time at the end of every project to wrap-up In-sourcing (external expert to save us time)
Transcript: A Inventory Management System C B Visibility in the supply chain is a problem Most companies have visibility up to their Tier-1 suppliers only Piercing beyond the veil of Tier-1 suppliers is a challenge Upstream Inventory Visibility Inventory Planning Visibility Barrier N-Tier Development Cycle Execution 1 Working with the target audience to understand their pain points in day-to-day life which is until now they didn't had visibility to their upstream inventory to better plan and avoid excess/low stock situations Understanding the key players involved in their supply chain which includes suppliers, DC's and their own stores Based on the total no. of integrations involved phase wise on-boarding has been prepared Planning & Analysis 2 As part of pilot phase, identified few suppliers and limited number of distribution centers, stores to on-board Data Integrations have been carried out to bring the data from all relevant parties and fed to the product Aggregation of numbers is done in the integration layer before feeding the absolute inventory numbers to the product Design & Implementation 3 After the implementation, users have been trained & provided with documentation to understand the product and how product can be used in their day-to-day life operations During Hyper-care, any issues reported or data discrepancies are being monitored to address Post Go-Live Support Corporate planners would have now visibility of Inventory to the lowest level possible in their supply chain Taking into account the shipments & order data to integrate & provide the in-transit inventory The Nuts and Bolts How It Works Data Flow Re-order Level - would let you know if there is a critical supplier from who multiple Tier-1 suppliers are buying from - would be able to identify if the suppliers of a particular component are located in specific geographic location like coast etc. - allows you to see if your end-to-end supply chain responds quickly in case of disruptions or changes in demand New Insights from this tool - Analyze your Tier-1 delivery performance correlation to its supply base structure Product Overview Take Away Alerts are generated if the inventory falls below safety stock Users can create incidents to communicate with suppliers or internally between teams Alerts & Incidents Thank You Q & A
Transcript: USE CASE Body : a) User action b) System Response Footer : a) Alternate Flow b) Exceptional Flow. USE CASE - Use case covers all the boundary value analysis of a system, ie end to end business scenarios. - It consist of all the system response of each user action. - Its consists of three attributes. a) Header b) Body c) Footer. - A use case is a methodology used in system analysis to identify, clarify, and organize system requirements. - The use case is made up of a set of possible sequences of interactions between systems and users in a particular environment and related to a particular goal. - Use Case doc is part UML diagram, which explains the requirement at the simplified format. Header : 1) Use Case ID 2) Use Case Name 3) Author Name 4) Authorized Date 5) Pre condition 6) Post condition 5) Reviewed By 6) Reviewed On 7) Actor
Description: Show the big picture, zoom in on details, and explain clearly how it all relates with this Prezi executive brief or Prezi nonprofit template. The lively image and bold colors make it easy to create compelling, engaging executive brief or nonprofit presentations.
Description: Rise way above the stacks and stacks of two-dimensional paper resumes on the hiring manager’s desk with a Prezi resume template. Simply personalize this Prezi presentation template to create your very own “Prezume” and impress them with your dynamism, originality, and cool.
Description: If you work in education, make your next report visually interesting and easy to navigate. The line-drawn illustrations in this edu report presentation template encourage curiosity and discovery.
Description: Impactful presentations need stunning visuals and a meaningful metaphor to show high-level concepts and the smaller details. This customizable presentation template uses a classic world map visual to help you navigate complex information while staying grounded in your presentation’s core message.
Now you can make any subject more engaging and memorable