IC card Management System

Slides:



Advertisements
Similar presentations
K. Ingram1November 2000 Object Orientated Analysis and Design - Contents When to use OO? What is OO? Unified Modelling Language OO Methodologies: –Object.
Advertisements

Architecture. Outline Example Decomposition Style Activity 1.
Practice data flow diagramming as a tool for structured system programming (process modelling) DATA FLOW DIAGRAMs.
7M701 1 Information Systems Modelling and Design with.
More Meaningful Use of CDA: the CDA-FHIR Bridge Robert Worden
Irwin/McGraw-Hill Copyright © 2004 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS6th Edition.
PROCESS MODELING Transform Description. A model is a representation of reality. Just as a picture is worth a thousand words, most models are pictorial.
Visual Basic: An Object Oriented Approach
Requirements Analysis 2 What objects collaborate to achieve the goal of a use case?
Work Package 4.1: End-user Components Months 6-25 D4.1.1Design of the End-user components (Month 13) D4.1.2Prototype of the End-user components (Month.
Group Discussion Hong Man 07/21/ UMD DIF with GNU Radio From Will Plishker’s presentation. 2 GRC The DIF Package (TDP) Platforms GPUs Multi- processors.
Application Engineering & Development Created by : Aeshang Parikh
Template Instructions: Mapping an Existing Workflow
Object-Oriented Design. From Analysis to Design Analysis Artifacts –Essential use cases What are the problem domain processes? –Conceptual Model What.
© 2007 by Prentice Hall (Hoffer, Prescott & McFadden) 1 The Relational Model (Advanced)
System Design Chapter 8. Objectives  Understand the verification and validation of the analysis models.  Understand the transition from analysis to.
PROCESS MODELING Chapter 8 - Process Modeling
Activity Diagram.
What is SMEcollaborate Primarily developed for Small and Medium Companies who wish to collaborate together. It is a:- A resource center for collaborating.
Prepared by: Sanaz Helmi Hoda Akbari Zahra Ahmadi Sharif University of Tech. Summer 2006 An Introduction to.
Reviewing Recent ICSE Proceedings For:.  Defining and Continuous Checking of Structural Program Dependencies  Automatic Inference of Structural Changes.
1 ooa2 Object-Oriented Software A model of the real world.
Lab 04.
Introduction Complex and large SW. SW crises Expensive HW. Custom SW. Batch execution Structured programming Product SW.
CS3773 Software Engineering Lecture 04 UML Class Diagram.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 14 Slide 1 Object-oriented Design.
1 CMPT 275 Software Engineering Requirements Analysis Phase Requirements Analysis activity Janice Regan,
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Slide 1 Use Case Diagrams.
Chapter 7 The Object-Oriented Approach to Requirements.
A Student Guide to Object- Oriented Development Chapter 10 Designing objects and classes.
CIS 112 Exam Review. Exam Content 100 questions valued at 1 point each 100 questions valued at 1 point each 100 points total 100 points total 10 each.
DESIGN PART 2: OBJECT-LEVEL SEQUENCE DIAGRAMS WITH AN EXAMPLE OF COMPOSITION BTS430 Systems Analysis and Design using UML.
Introduction Conclusion Process Evaluation Task Teacher Page.
Week 10 1 Sequence Diagrams. Outline a)Add scenarios to the system to describe how Use Cases are realized as interactions among societies of objects b)Describe.
Computer Science 340 Software Design & Testing Software Architecture.
Chapter 5 System Modeling. What is System modeling? System modeling is the process of developing abstract models of a system, with each model presenting.
click to start Example: A LINEAR TRANSFORMATION.
UML Activity Diagrams.
CERES-2012 Deliverables Architecture and system overview 21 November 2011 Updated: 12 February
Fall 2007 Week 9: UML Overview MSIS 670: Object-Oriented Software Engineering.
Scheduler CSE 403 Project SDS Presentation. What is our project? We are building a web application to manage user’s time online User comes to our webpage.
Collaboration diagrams. Deployment diagrams. Lesson 4.
Metadata Driven Aspect Specification Ricardo Ferreira, Ricardo Raminhos Uninova, Portugal Ana Moreira Universidade Nova de Lisboa, Portugal 7th International.
Development of CAD concept model of package transformer substation (PTS) Aleksandra Seledkova Perm National Research Polytechnic University.
Ondřej Přibyl L4: SAD Methodologies page 1 Lecture 4: System Analysis and Design Methodologies Telematics systems and their design Doc.Ing. Ondřej Přibyl,
Information Systems in Organizations 2.1 Analyzing organizations as systems and processes & Modeling Processes with Swimlane Diagrams.
Application of Design Patterns to Geometric Decompositions V. Balaji, Thomas L. Clune, Robert W. Numrich and Brice T. Womack.
Use Case Diagram Example
FHIRForms – Viewing and Editing FHIR Data
Chapter 0: Introduction
CEN3722 Human Computer Interaction Interface Metaphors and Conceptual Models Dr. Ron Eaglin.
Chapter 1: Introduction to Systems Analysis and Design
Functional organization of the yeast proteome by systematic analysis of protein complexes Presented by Nathalie Kirshman and Xinyi Ma.
Hire Toyota Innova in Delhi for Outstation Tour
CH#3 Software Designing (Object Oriented Design)
IC card Management System
UML Activity Diagrams.
CSE 403 Project SDS Presentation
PROPOSAL WRITING TECH COM 1.
مبررات إدخال الحاسوب في رياض الأطفال
IC card Management System
Systems Analysis and Design With UML 2
PROPOSAL WRITING TECH COM 1.
Software Design Lecture : 15.
21twelveinteractive.com/ twitter.com/21twelveI/ facebook.com/21twelveinteractive/ linkedin.com/company/21twelve-interactive/ pinterest.com/21twelveinteractive/
Andrew Christensen, SDWG Chair
Chapter 1: Introduction to Systems Analysis and Design
I have… I have… Who has 3:40? Who has 12:20? I have… I have…
Chapter 2: Building a System
Building a “System” Moving from writing a program to building a system. What’s the difference?! Complexity, size, complexity, size complexity Breadth.
Presentation transcript:

IC card Management System Card transformation and decomposition

Current implementation

Current implementation Current implementation creates new IC cards. It does not offer the feature of transforming/decomposing an existing IC card.

Current implementation The organic activity name is not used. Each condition becomes a new IC card.

Current implementation

Implementation Proposal We add a new field in the IC card creation that identifies if the card is a composite of smaller activities and if it has a organic component (human interaction). With this can identify which cards can be initially considered to further transformation or decomposition. Maps IC cards that can be organic/inorganic hybrid or posses a complex task

Implementation Proposal Schedule Patient Appointment We add a new field in the IC card creation that identifies if the card is a composite of smaller activities and if it has a organic component (human interaction). With this can identify which cards can be initially considered to further transformation or decomposition.

Implementation Proposal Schedule Patient Appointment x We add a new field in the IC card creation that identifies if the card is a composite of smaller activities and if it has a organic component (human interaction). With this can identify which cards can be initially considered to further transformation or decomposition.

Implementation Proposal Schedule Patient Appointment x Find available time Match Patient time with Physician time We add a new field in the IC card creation that identifies if the card is a composite of smaller activities and if it has a organic component (human interaction). With this can identify which cards can be initially considered to further transformation or decomposition.

Implementation Proposal Schedule Patient Appointment x x Find available time Match Patient time with Physician time x x We add a new field in the IC card creation that identifies if the card is a composite of smaller activities and if it has a organic component (human interaction). With this can identify which cards can be initially considered to further transformation or decomposition.

Parallel with Use Case Diagrams In use case diagram actors can be either humans or another system.