MIS 325 PSCJ. CASE STUDY Using UML diagrams model business processes for a medium-sized enterprise whose main business is the development and support.

Slides:



Advertisements
Similar presentations
CPSC 203. Use Case Diagram  A description of a system’s behavior as it responds to a request that originates from outside of that system. Specifies the.
Advertisements

S Y S T E M S E N G I N E E R I N G.
UML & Together 2006 tutorial Hong Qing Yu 10/2006.
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall 3.1.
Sixth Hour Lecture 10:30 – 11:20 am, September 9 Framework for a Software Management Process – Artifacts of the Process (Part II, Chapter 6 of Royce’ book)
Training of master Trainers Workshop 10 – 15 November 2012 e-Services Design and Delivery Module IIX Emilio Bugli Innocenti.
1 California State University, Fullerton Chapter 13 Developing and Managing Information Systems.
MSIS 110: Introduction to Computers; Instructor: S. Mathiyalakan1 Systems Design, Implementation, Maintenance, and Review Chapter 13.
McGraw-Hill Technology Education © 2006 by the McGraw-Hill Companies, Inc. All rights reserved CHAPTER YOUR FUTURE AND INFORMATION TECHNOLOGY.
1 IS 4420 Database Fundamentals Chapter 2: Database Development Process Leon Chen.
The Problems with Software Engineering Where do we go wrong? The UML lecture notes are based in part on those developed originally by Mats PE Heimdahl.
Lead Black Slide. © 2001 Business & Information Systems 2/e2 Chapter 13 Developing and Managing Information Systems.
An introduction to enterprise systems a birds-eye view of the course.
Software Process Activities. Process activities Real software processes are inter-leaved sequences of technical, collaborative and managerial activities.
Context Diagrams There are three symbols used in these diagrams: Context Diagrams are used in the Analysis and Design phases as an analysis and design.
Marc Conrad University of Bedfordshire 1 Project Management – PMBOK® Project Initiation Dr Marc Conrad Office: D104 – Park Square
Continuation From Chapter From Chapter 1
The Database Development Process
© 2006 ITT Educational Services Inc. SE350 System Analysis for Software Engineers: Unit 6 Slide 1 Chapter 5 Initiating and Planning Systems Development.
1 REQUIREMENT ENGINEERING Chapter 7. 2 REQUIREMENT ENGINEERING Definition Establishing what the customer requires from a software system. OR It helps.
ArchiMate Authors : eSchoolink Group - ITNLU. Contents 1. What’s ArchiMate ? 2. Why ArchiMate ? 3. Main Benefits of ArchiMate 4. Layers of ArchiMate 5.
Principles of Information Systems, Sixth Edition Systems Design, Implementation, Maintenance, and Review Chapter 13.
Programming in Java Unit 3. Learning outcome:  LO2:Be able to design Java solutions  LO3:Be able to implement Java solutions Assessment criteria: 
Cultural Heritage in REGional NETworks REGNET. October 2001Project presentation REGNET 2 Work Package 1 Title: ‘Analysis of the State of the Art and Development.
Improving Integration of Learning and Management Systems Paul Shoesmith Director of Technical Strategy Becta.
 Build a Bridge?  Make a Robot?  Work on a Computer?  Drive a Train?  Repair Car Engines?
Use Case Modeling Chapter 7 Part of Requirements Modeling Designing Concurrent, Distributed, and Real-Time Applications with UML Hassan Gomaa (2001)
Requirements Engineering for Web Applications. SR: System Vision Document Written by key stakeholders Written by key stakeholders An executive summary.
STAKEHOLDER MANAGEMENT
System Context and Domain Analysis Abbas Rasoolzadegan.
Rational Unified Process Fundamentals Module 3: Disciplines I.
Requirements Engineering for Web Applications. SR: System Vision Document Written by key stakeholders Written by key stakeholders An executive summary.
CONTENT 1.Software Process 2.Object Technology 3.UML 4.UML For Java.
Security Classification ES4C9 Supply Chain Management ~ Improving and Developing Zoe Maxwell.
Principles of Information Systems, Sixth Edition 1 Systems Design, Implementation, Maintenance, and Review Chapter 13.
Requirements Management with Use Cases Module 3: Analyze the Problem Requirements Management with Use Cases Module 3: Analyze the Problem.
Phase 3 The Software Requirements Specification. After review of the customer’s System Spec. After educated analysis Preliminary design A technical, software.
1 Technical & Business Writing (ENG-715) Muhammad Bilal Bashir UIIT, Rawalpindi.
Eurostat 1 3.An overview of the SDMX implementation process Edward Cook Eurostat Unit B5: “Central data and metadata services” SDMX Basics course,
ANALISA & PERANCANGAN SISTEM Disusun Oleh : Dr. Lily Wulandari Program Pasca Sarjana Magister Sistem Informasi Universitas Gunadarma.
CS223: Software Engineering Lecture 16: The Agile Methodology.
Stakeholder Summit Fire Prevention Initiatives. Objectives Review success of “Getting to Know Fire” presentation Review content of “Getting to Know Fire”
18. Discussion Questions - Introduction to Supply Chain Management (SCM) - May 20, 2013 POSTECH Strategic Management of Information and Technology Laboratory.
1 Version /05/2004 © 2004 Robert Oshana Requirements Engineering Analyzing the Problem.
Cloud Computing for Business Cloud Computing Services Cloud Computing Services.
1 Use Cases Object-Oriented Modeling and Design with UML (Second Edition) Blaha & Rumbaugh Sections 7.1, 8.1.
BSA 385 Week 3 Individual Assignment Frequent Shopper Program Part 2 Check this A+ tutorial guideline at
Software Process Activities.
Introduction to MODEM Building a Semantic Foundation for EA: Reengineering the MODAF™ Meta-Model Based on the IDEAS Foundation Model Lt Col Mikael Hagenbo,
Area ERP1 Business Application Manager
Object-Oriented Techniques
Call How to Install Webroot Antivirus?
UML PPt by: Hong Qing Yu.

technical-service/ technical-service/
Chapter 3 Managing the Information Systems Project
Norton Technical Support Norton
Retail Enterprise Orgnaizational Chart
ريكاوري (بازگشت به حالت اوليه)
Dividing Decimals.
Chapter 3 Managing the Information Systems Project
Software Design Lecture : 15.
Fractions.
Enterprise Resource Planning (ERP) System
Advanced Leadership Course Monday, AM, Part 2 Project Initiation
Selected Topics in Project Management Project Initiation
Chapter 3 Managing the Information Systems Project
UML & Together 2006 tutorial
Microsoft Virtual Academy
Divide 9 × by 3 ×
Presentation transcript:

MIS 325 PSCJ

CASE STUDY Using UML diagrams model business processes for a medium-sized enterprise whose main business is the development and support of new products and services. The business processes are divided into the following four groups: Technical: describes all processes associated with development and engineering activities within the organization Enterprise: describes all the processes that apply across the whole organization Project: describes all processes associated with management and support within the organization Agreement: describes all processes that relate to the customer-supplier relationships

Process structure view

Breakdown of the Project process group

Process content view for Enterprise process group

Process content view for Enterprise with emphasis on Personnel

Process content view for the Technical process group with an emphasis on Training processes

Process content view for the Technical process group with an emphasis on Product Development

Process content view for the Technical process group with an emphasis on Maintenance processes

Process content view for the Project process group with an emphasis on Management processes

Process content view for the Project process group with an emphasis on Support processes

Process content view for the Agreement process group

Stakeholder view with an emphasis on Customer

Stakeholder view with an emphasis on External

Stakeholder view with an emphasis on Supplier

Requirements view for invoice-related processes

Instance view for invoice-related processes

Information view for the Course set-up process artefacts