Requirements Engineering
|
|
- Elfrieda Lyons
- 5 years ago
- Views:
Transcription
1 Chapter 3: Requirements Modeling Requirements Engineering
2 Objectives In this chapter, you will learn about: Functional requirements Modeling requirements Overview of basic modeling paradigms Gus Requirements Engineering 2
3 Functional Requirements Functional Requirements Specification is the second step in Requirements Engineering Functional Requirements define the solution space for the problem Our goal is to use the customer s needs (see lecture notes 2) and create: 1. Graphical representations of the required interactions, behaviors and activities 2. Narrative of the required interactions, behaviors and activities 3. Algorithms to support your views (You may skip this step for your class project. This step is typically handled by SMEs. It falls mainly in the HOW domain. If you are not an SME, then you will need to brainstorm initially with various Subject Matter Experts) The deliverables of the Functional requirements provide a framework for deriving i and structuring t systems requirements Gus Requirements Engineering 3
4 Functional Requirements Modeling 1. Modeling is a method to schematically describe our perceived representations of the customer s s needs, behaviors and interactions for the problem domain What are the advantages of Modeling? Allows you to restate t the requirements in a format different from the original i customer s requests Force the customer to examine your models in order to validate the model s accuracy Helps you to better understand d the customer s requirements Multiple, conflicting outputs to the same input is an indication of inconsistencies in the requirements Allows consideration of multiple interacting aspects and views of the system apriori Allows requirements specifications to be visualized in diagrams ( A picture is worth a thousand words ) Facilitates efficient communications between the different SDLC organizations Gus Requirements Engineering 4
5 Modeling Requirements Modeling Techniques: There are several eral modeling notations to express info about problem s concept, behavior and interactions (properties) New (customized) notations are being introduced to adapt to new type of problem domains The individual modeling notations, however, are based on less than 10 basic paradigms We will examine some of the basic paradigms Gus Requirements Engineering 5
6 Modeling Requirements Data Flow Diagrams Data Flow Diagrams (DFD) Provide graphical representation of a fundamental system structure and interfaces Do not show control flows Elements in a Data Flow Diagram: Data Flows Labeled arrows: to indicate information exchanged between two transformations Flow type: Continuous, on demand asynchronous etc. Data Transformations Bubbles: indicate processes/subsystems to depict internal entities Data Stores Horizontal Parallel lines: indicate Transactions, db External Entities Rectangles: indicates entities that interact with the system DFD must be accompanied by textual descriptions of data Flows, data Transformations and data Stores Data Dictionary defines data Stores and Flows Gus Requirements Engineering 6
7 Modeling Requirements Data Flow Diagrams Credit card holder Check details Transactions s Process transaction Print receipt Account system Printer Example Data Flow Diagram for ATM System Gus Requirements Engineering 7
8 Modeling Requirements Developing a Data Flow Diagram Start with a Context Diagram Show all external systems that interact with proposed system Process transaction Check details ATM System Credit card holder Account system Printer Fundamental Data Flow Diagram for ATM System Gus Requirements Engineering 8
9 Modeling Requirements Developing a Data Flow Diagram Next, progressively expand ( explode ) each bubble Detailed processes (bubbles), data stores and/or data flows Credit card holder (A) A Y C Accounts System (B) o Printer (C) B 1 2 C 3 4 X Z X Z Explode 0 Explode 3 Gus Requirements Engineering 9
10 Developing a Data Flow Diagram Model for Ambulance Command & Control (AC&C) System Caller Handle Callers Current Incidents Handle ambulances Keep records Ambulance Ambulance State Model for Ambulance C&C System Records Gus Requirements Engineering 10
11 Developing a Data Flow Diagram Model for Ambulance Command & Control (AC&C) System Handle Callers Obtain Incident details Communicate with Caller Analyze incident Provide On-line advice Caller Handle ambulances Current Incidents Communicate with Ambulances Allocate ambulance Monitor Ambulance states Monitor incident Keep records Provide statistics Ambulance Ambulance State Detail Model for Ambulance C&C System Records Gus Requirements Engineering 11
12 Developing a Data Flow Diagram Functional structure of Ambulance Command & Control (AC&C) System Handle callers Communicate with caller Obtain incident details Analyze incident Provide on-line advice The obtain incident details function shallallowcenterstaff allow staff to obtain and record incident details from the caller C&C system Handle ambulances Allocate ambulance Communicate with ambulances Monitor ambulances The allocate ambulance function shall allow the controller to allocate an ambulance to an incident Keep records Monitor incidents Provide Statistics Gus Requirements Engineering 12
13 Modeling Requirements Use Cases A Use Case: Describes particular functionality of a system Modeling the interactions (dialog) that a user, external system or other entity (actor) will have with the system being developed Each use case describes possible scenarios of how the actor interacts with the system Use Cases are presented as Drawings of pertinent objects plus Brief textual description of how the function is performed For each scenario the use case identifies: All possible events System s response The collection of all use cases provides a complete description of the different ways of using the system by all possible entities Gus Requirements Engineering 13
14 Modeling Requirements Use Cases Pay fines <<include>> Check fines Patron Find item <<extend>> <<include>> Borrow item Return item <<extend>> Reserve item Recall item Library inventory Librariani Cancel reservation Example: Library Use Cases Can you Identify the actors? How about the use cases? Gus Requirements Engineering 14
15 Modeling Requirements Use Cases Actors: Patron (Human) Librarian (Human but different user) Library inventory (system/shelf) <<include>> Pay fines Check fines Base Case: Pay fines Find item Return item Reserve item Borrow item Patron Find item <<extend>> <<include>> Borrow item Return item Library inventory Subcase: Check fines Common to Base Cases: Pay fines and Borrow item Dashed arrows goes from Base Case to Subcase <<include>> Recall item (extension subcase) Adds functionality to base case Reserve item Dashed arrowed line points to Base case Borrow item (extension subcase) Adds functionality to base case Reserve item Dashed arrowed line points to Base case <<extend>> Librarian <<extend>> Reserve item Recall item Cancel reservation Library Use Cases Gus Requirements Engineering 15
16 Use Cases Shell Gas Station Lets consider a shell gas station that provides Three types of services: Refueling, Parking and Maintenance Bill to the customer for each service Develop the use cases for the system Gus Requirements Engineering 16
17 Use Cases Shell Gas Station Start with the fundamental use case diagram Refueling <<extend>> Customer Billing Services Parking Maintenance High-level view for billing But customer Performs refueling Parking, maintenance? Some customers will use credit card Next, Discover new aspects of the problem by asking questions Gus Requirements Engineering 17
18 Use Cases Shell Gas Station Add credit card payment option Refueling Customer Billing Services Parking High-level view for billing Some will pay with Visa? Credit card system Maintenance Gus Requirements Engineering 18
19 Use Cases Shell Gas Station Add manager; gas station offers Tune up services Refueling Customer Parking Manager But how does manager interacts with the system? Maintenance Tune up <<extend>> Next, Discover new aspects of the problem by asking questions Gus Requirements Engineering 19
20 Use Cases Shell Gas Station Managerial role is different from customer Accounting, inventory, orders parts for the services Printer system Accounting services Inventory Control Manager But how does manager interacts with the system? Fuel ordering system Parts ordering system Gus Requirements Engineering 20
21 Use Cases Shell Gas Station Collection of Use Cases for the various scenarios Printer system Accounting services Customer Billing Services Inventory Control Manager Parking Fuel Services Refueling Fuel ordering system Maintenance Services Parts ordering system Tune up Gus Requirements Engineering 21
22 Functional Requirements Unified Modeling Language (UML) Class Diagrams UML Represents systems in terms of objects and methods Objects (analogous to Entities) Organized in classes that have inheritance Each provides methods that perform actions on the object variables As objects executes they: Send messages to invoke each others method Acknowledge actions Transmit data Class Diagram is an ER that relates classes (entities) in a UML model Gus Requirements Engineering 22
23 UML Class Diagrams Patron * patron id name address fines checkfines( ) increasefines( () payfines( ) recallnotify( ) * Loan due date overdue fine calc due date( ) calc overdue fines( ) renew( ) recall( () Publication * call number title value depreciation loan period reserve loan period reserve fine rate recall period find(title): publication buy() lose() borrow() return() reserve() unreserve() decreasevalue() Class name Class attributes (simple variables) Set of Operations on attributes Book author Example UML Class Model of Library Problem Periodical editor volume number loan period fine rate * Article Gus Requirements Engineering author 23
24 UML Class Diagrams Notations Class-Scope Attribute (Underlined attributes) Attributes associated with the class rather than instances of the class Loan period, fine rate apply to all publications Librarian can modify loan duration for all books, all periodicals but not for individual books or individual periodicals Class-Scope Operations (Underlined operations) Operation performed by abstract class on a new instance or a whole collection of instances Association (Line between two entities) Indicates relationship between the classes entities Patron borrows a Publication Aggregate Association (line with clear diamond end) Class at the diamond end owns (includes instances) of class at the other end of the line Composition Association (line with black diamond) Instances of compound class are physically constructed from classes of component classes Periodicals is composed of Articles Generalization Association (Line with triangle on one end) Publication is a parent class of subclasses: Book and Periodical A subclass inherits all the parents class s attributes, operations and associations It is not necessary to draw a line between Patron and Book, because Book inherits this association from Publication Multiplicities Constraints on number of links between entities Number, range, unlimited numbers (*) Gus Requirements Engineering 24
25 Modeling Requirements Massage Sequence Charts (MSC) MSC provides graphical representations of Sequences of events exchanged between real-world entities Elements in MSC: Participating Entity Depicted as a vertical line Message Depicted as an arrow from the sending entity to receiving entity Actions Invoked operations or changes to variable values Depicted as labeled rectangles Gus Requirements Engineering 25
26 Massage Sequence Chart (MSC) Library Loan Request (Item available) Publication Loan Patron borrow (patron) publication, patron a b checkfines es c no fine d calc due date e Gus Requirements Engineering 26
27 MSC Operational Details a. Library loan request is sent to the Publication entity to be burrowed b. Publication creates a loan entity to manage the loan specific data c. Check if patron has a fine d. Patron does not have fines e. Calculate due date to return burrowed item Gus Requirements Engineering 27
28 Massage Sequence Chart (MSC) Library Loan Request (item checked out ~ reserve) Publication Loan Patron reserve (patron) recall a b return Recall notification (publication) delete Recall notice (publication) c d e f calc due date g Increase fine h Gus Requirements Engineering 28
29 Modeling Requirements Use Case Scenario & Message Sequence Chart Medical Device Nurse PDA Wireless Network Server Outside World ISP, PROVIDER Gus Requirements Engineering 29
30 Patient uses speech command to raise bed Use Case Scenario & MSC Commands PDA Server TV Monitor Device Pti Patient: t Bd Bedop Cmd-API CTL a Bed up b Bed -ID up c Patient Selects Option # Simulate Bed on TV + CTL Menu Display bed + Menu Options d e f g h Simulate Bed level i Display bed position j Wait 1 sec Send ctrl to raise bed k l Gus Requirements Engineering 30
31 Glossary of Terms This section provides a glossary of terms used in this document. It is not meant to be a glossary of all relevant terms used in the product. Acronym CCD GUI JVM MS NE NEI OA&M QA SSN Definition Control Command Definition Graphical User Interface Java Virtual Machine Microsoft Network Element Network Element Interface Operations Administration and Maintenance Quality Assurance Social Security Number Refers to customer (business) & technical jargons Gus Requirements Engineering 31
32 Functional Requirements Example: Case Study Case Study Case Study materials will be presented in class Gus Requirements Engineering 32
Chapter 4. Capturing the Requirements. 4th Edition. Shari L. Pfleeger Joanne M. Atlee
Chapter 4 Capturing the Requirements Shari L. Pfleeger Joanne M. Atlee 4th Edition It is important to have standard notations for modeling, documenting, and communicating decisions Modeling helps us to
More informationCh t 8 Chapter 8. System Models
Ch t 8 Chapter 8. System Models Objectives To explain why the context t of a system should be modelled d as a part of requirements engineering process To describe behavioural modelling, data modelling
More informationChapter 10. Object-Oriented Analysis and Modeling Using the UML. McGraw-Hill/Irwin
Chapter 10 Object-Oriented Analysis and Modeling Using the UML McGraw-Hill/Irwin Copyright 2007 by The McGraw-Hill Companies, Inc. All rights reserved. Objectives 10-2 Define object modeling and explain
More informationClass diagrams. Modeling with UML Chapter 2, part 2. Class Diagrams: details. Class diagram for a simple watch
Class diagrams Modeling with UML Chapter 2, part 2 CS 4354 Summer II 2014 Jill Seaman Used to describe the internal structure of the system. Also used to describe the application domain. They describe
More informationClass diagrams. Modeling with UML Chapter 2, part 2. Class Diagrams: details. Class diagram for a simple watch
Class diagrams Modeling with UML Chapter 2, part 2 CS 4354 Summer II 2015 Jill Seaman Used to describe the internal structure of the system. Also used to describe the application domain. They describe
More informationUML diagrams. Software artifacts include: SRS, SDS, test cases, source code, technical/user manual, software architecture, etc.
UML Modeling UML diagrams UML (Unified Modeling Language) is a general purpose visual modeling language that provides different types of diagrammatic techniques and notations to specify, visualize, analyze,
More informationSystem models Abstract descriptions of systems whose requirements are being analysed. System modelling. Structured methods
System models Abstract descriptions of systems whose requirements are being analysed Ian Sommerville 995/2000 (Modified by Spiros Mancoridis 999) Software Engineering, 6th edition. Chapter 7 Slide System
More informationObjectives Pre-Test Questions Introduction Collaboration Diagrams Flow of Events and Special Requirements...
10 Analysis Modeling M MAJOR A J O R T TOPICSO P I C S Objectives... 144 Pre-Test Questions...144 Introduction... 145 Collaboration Diagrams... 145 Flow of Events and Special Requirements... 151 Class-Responsibility-Collaboration
More informationSE Assignment III. 1. List and explain primitive symbols used for constructing DFDs. Illustrate the use of these symbols with the help of an example.
SE Assignment III 1. List and explain primitive symbols used for constructing DFDs. Illustrate the use of these symbols with the help of an example. There are essentially 5 different types of symbols used
More informationObject Oriented Design. Program Design. Analysis Phase. Part 2. Analysis Design Implementation. Functional Specification
Object Oriented Design Part 2 Analysis Design Implementation Program Design Analysis Phase Functional Specification Completely defines tasks to be solved Free from internal contradictions Readable both
More informationUML. By Somenath Mukhopadhyay.
UML By som@som-itsolutions.com What is the UML? Stands for unified modelling language Is the successor of OOAD methods It unifies the methods of Booch, Rumbaugh and Jacobson Now a standard with Object
More informationIntroducing the UML Eng. Mohammed T. Abo Alroos
Introducing the UML Eng. Mohammed T. Abo Alroos Islamic University of Gaza Introduction to the UML: The UML stands for Unified Modeling Language. It was released in 1997 as a method to diagram software
More informationObject-Oriented Systems Analysis and Design Using UML
10 Object-Oriented Systems Analysis and Design Using UML Systems Analysis and Design, 8e Kendall & Kendall Copyright 2011 Pearson Education, Inc. Publishing as Prentice Hall Learning Objectives Understand
More informationSoftware Life-Cycle Models
Software Life-Cycle Models CMPSC 487 Lecture 03 Topics: UML Class Diagram Rosenburg Chap 2. Domain Modeling A. UML: Unified Modeling Language UML is a general-purpose, developmental, modeling language
More informationPractical UML : A Hands-On Introduction for Developers
Borland.com Borland Developer Network Borland Support Center Borland University Worldwide Sites Login My Account Help Search Practical UML : A Hands-On Introduction for Developers - by Randy Miller Rating:
More informationSlide 1 Welcome to Fundamentals of Health Workflow Process Analysis and Redesign: Process Mapping: Gane-Sarson Notation. This is Lecture d.
WORKFLOW ANALYSIS Audio Transcript Component 10 Unit 3 Lecture D Fundamentals of Health Workflow Process Analysis & Redesign Interpreting and Creating Process Diagrams Process Mapping Gane-Sarson Notation
More informationChapter 2: Entity-Relationship Model
Chapter 2: Entity-Relationship Model! Entity Sets! Relationship Sets! Design Issues! Mapping Constraints! Keys! E-R Diagram! Extended E-R Features! Design of an E-R Database Schema! Reduction of an E-R
More informationSE 1: Software Requirements Specification and Analysis
SE 1: Software Requirements Specification and Analysis Lecture 9: UML Class (Concept), Object, Communication Diagrams Nancy Day, Davor Svetinović http://www.student.cs.uwaterloo.ca/ cs445/winter2006 uw.cs.cs445
More informationObject-oriented design. More UML
Object-oriented design More UML Interfaces An interface is a language construct specific to Java Java does not support multiple inheritance Interfaces provide some of the same functionality A Java class
More informationInteraction Modelling: Use Cases
Interaction Modelling: Use Cases Fabrizio Maria Maggi Institute of Computer Science (these slides are derived from the book Object-oriented modeling and design with UML ) Interaction Modelling: INPUT 1
More informationInteraction Modelling: Sequence Diagrams
Interaction Modelling: Sequence Diagrams Fabrizio Maria Maggi Institute of Computer Science (these slides are derived from the book Object-oriented modeling and design with UML ) Interaction Modelling
More informationLecture Notes. Structured Systems Analysis
Lecture Notes Structured Systems Analysis Lecture 3 Structured Analysis & Data Flow Diagrams Written by Dr. Fred Grossman Copyright 1999 Fred Grossman All Rights Reserved Structured Systems Analysis Structured
More informationData Analysis 1. Chapter 2.1 V3.1. Napier University Dr Gordon Russell
Data Analysis 1 Chapter 2.1 V3.1 Copyright @ Napier University Dr Gordon Russell Entity Relationship Modelling Overview Database Analysis Life Cycle Components of an Entity Relationship Diagram What is
More informationPractical UML - A Hands-On Introduction for Developers
Practical UML - A Hands-On Introduction for Developers By: Randy Miller (http://gp.codegear.com/authors/edit/661.aspx) Abstract: This tutorial provides a quick introduction to the Unified Modeling Language
More informationEntity Relationship Modelling
Entity Relationship Modelling Overview Database Analysis Life Cycle Components of an Entity Relationship Diagram What is a relationship? Entities, attributes, and relationships in a system The degree of
More informationSoftware Engineering Fall 2014
Software Engineering Fall 2014 (CSC 4350/6350) Mon.- Wed. 5:30 pm 7:15 pm ALC : 107 Rao Casturi 10/01/2014 Class Announcements Grading is done for the Deliverable #2 (Requirement Elicitation) Will be posed
More informationQuestion Sheet There are a number of criticisms to UML. List a number of these criticisms.
Question Sheet 1 Name: ID: These questions do not have a formal, definitive answer. They are meant to be food for thoughts. Feel free to seek answers on browsing the Internet, talking to other software
More information7. UML Sequence Diagrams Page 1 of 1
7. UML Sequence Diagrams Page 1 of 1 Sequence Diagram in UML In the last article, we saw Activity diagrams, the notations to be used in Activity diagrams, their significance, and how to build an Activity
More informationDarshan Institute of Engineering & Technology for Diploma Studies
REQUIREMENTS GATHERING AND ANALYSIS The analyst starts requirement gathering activity by collecting all information that could be useful to develop system. In practice it is very difficult to gather all
More informationChapter 6: Entity-Relationship Model
Chapter 6: Entity-Relationship Model Database System Concepts, 5th Ed. See www.db-book.com for conditions on re-use Chapter 6: Entity-Relationship Model Design Process Modeling Constraints E-R Diagram
More informationFollow this and additional works at: Part of the Information Literacy Commons
Wright State University CORE Scholar University Libraries' Staff Publications University Libraries 10-7-2016 Circulation Rules Leigh Ann Duncan Wright State University - Main Campus, leigh.duncan@wright.edu
More information0. Database Systems 1.1 Introduction to DBMS Information is one of the most valuable resources in this information age! How do we effectively and efficiently manage this information? - How does Wal-Mart
More informationRequirements Analysis. SE 555 Software Requirements & Specification
Requirements Analysis Goals of Requirements Analysis Create requirements containing sufficient detail and of high enough quality to allow realistic project planning as well as successful design and implementation.
More informationVP-UML Quick Start. Last update: October 15, Copyright Visual Paradigm International Ltd.
VP-UML Quick Start Last update: October 15, 2012 Copyright 2002-2012 Visual Paradigm International Ltd. Table of Contents Table of Contents... 2 Getting Started... 3 Installing Visual Paradigm for UML
More informationIntro to DB CHAPTER 6
Intro to DB CHAPTER 6 DATABASE DESIGN &THEER E-R MODEL Chapter 6. Entity Relationship Model Design Process Modeling Constraints E-R Diagram Design Issues Weak Entity Sets Extended E-R Features Design of
More informationLesson 06. Requirement Engineering Processes
Lesson 06 Requirement Engineering Processes W.C.Uduwela Department of Mathematics and Computer Science Objectives To describe the principal requirements engineering activities and their relationships To
More informationChapter : Analysis Modeling
Chapter : Analysis Modeling Requirements Analysis Requirements analysis Specifies software s operational characteristics Indicates software's interface with other system elements Establishes constraints
More informationChapter 2: Entity-Relationship Model. Entity Sets. Entity Sets customer and loan. Attributes. Relationship Sets. A database can be modeled as:
Chapter 2: Entity-Relationship Model Entity Sets Entity Sets Relationship Sets Design Issues Mapping Constraints Keys E-R Diagram Extended E-R Features Design of an E-R Database Schema Reduction of an
More information26. Object-Oriented Design. Java. Summer 2008 Instructor: Dr. Masoud Yaghini
26. Object-Oriented Design Java Summer 2008 Instructor: Dr. Masoud Yaghini Object-Oriented Design In the preceding chapters you learned the concepts of object-oriented programming, such as objects, classes,
More informationIan Sommerville 2006 Software Engineering, 8th edition. Chapter 8 Slide 1
System models Slide 1 Objectives To explain why the context of a system should be modelled as part of the RE process To describe behavioural modelling, data modelling and object modelling To introduce
More informationTopics. Overview- The UML Functional Model. Structural Model. Behavioral Models. Use Case Diagram (essential and system)
Topics Overview- The UML Functional Model Use Case Diagram (essential and system) Structural Model Class/object, Component and Deployment Diagram Behavioral Models Activity, State chart, sequence /collaboration
More informationOO System Models Static Views
OO System Models Static Views UML Class & Object Diagrams Software Engineering OO Models Class Diagram Slide 1 Objective Introduces the evolutionary approach for building classes Explain how to identify
More information10 Implinks and Endpoints
Chapter 10 Implinks and Endpoints Implementation links and endpoints are important concepts in the SOMT method (described in the SOMT Methodology Guidelines starting in chapter 69 in the User s Manual).
More informationData and Process Modeling
Data and Process Modeling Chapter 3 Data Models Start with User Views Data Model Diagramming Entity Relationship Diagram (ERD) is most common Original by Peter Chen in 1976 Common ERD Elements: Entities
More informationRequests Charges. Librarian. University affiliated patrons students, faculty, staff. Media Center Staff
Catherine Rutan INFO 530-901 Dr. Valerie Yonker Circulation of Media Materials from University Media Center: Requests Charges Librarian Circulation Desk Attendant Inquires University ID # (Primary Key)
More informationModeling with UML. (1) Use Case Diagram. (2) Class Diagram. (3) Interaction Diagram. (4) State Diagram
Modeling with UML A language or notation intended for analyzing, describing and documenting all aspects of the object-oriented software system. UML uses graphical notations to express the design of software
More informationSoftware Engineering Fall 2015 (CSC 4350/6350) TR. 5:30 pm 7:15 pm. Rao Casturi 09/29/2015
Software Engineering Fall 2015 (CSC 4350/6350) TR. 5:30 pm 7:15 pm Rao Casturi 09/29/2015 http://cs.gsu.edu/~ncasturi1 Class Announcements Grading is done for the Deliverable #2 (Requirement Elicitation)
More informationUnified Modeling Language (UML)
1 / 45 Unified Modeling Language (UML) Miaoqing Huang University of Arkansas 2 / 45 Outline 1 Introduction 2 Use Case Diagram 3 Class Diagram 4 Sequence Diagram 3 / 45 Outline 1 Introduction 2 Use Case
More informationChapter 2, Modeling with UML, Part 2
Using UML, Patterns, and Java Object-Oriented Software Engineering Chapter 2, Modeling with UML, Part 2 Outline of this Class What is UML? A more detailed view on Use case diagrams Class diagrams Sequence
More informationSpecification and Documentation Techniques: Graphical Notations (2)
Specification and Documentation Techniques: Graphical Notations (2) CS/SE 3RA3 Ryszard Janicki Department of Computing and Software, McMaster University, Hamilton, Ontario, Canada Ryszard Janicki Graphical
More informationCS 451 Software Engineering
CS 451 Software Engineering Yuanfang Cai Room 104, University Crossings 215.895.0298 yfcai@cs.drexel.edu 1 Elaboration 2 Elaboration: Building the Analysis Model An analysis model provides a description
More informationLecture c, Process Mapping: Yourdon Notation for Data Flow Diagrams, covers Yourdon notation for data flow diagrams.
WORKFLOW ANALYSIS Audio Transcript Component 10 Unit 3 Lecture C Fundamentals of Health Workflow Process Analysis & Redesign Interpreting and Creating Process Diagrams Process Mapping Yourdon Notation
More informationSoftware Service Engineering
Software Service Engineering Lecture 4: Unified Modeling Language Doctor Guangyu Gao Some contents and notes selected from Fowler, M. UML Distilled, 3rd edition. Addison-Wesley Unified Modeling Language
More informationUML Is Not a Methodology
UML COSC 4354 1 UML Is Not a Methodology UML is an acronym for Unified Modeling Language UML is a language A language is simply a tool for communication and exchanging ideas UML is a notation, not a methodology
More informationMSc programme (induction week) Department of Informatics INTRODUCTION TO UML
MSc programme (induction week) Department of Informatics INTRODUCTION TO UML Some of this material is based on Bernd Bruegge and Allen H. Dutoit (2009) Object-Oriented Software Engineering: Using UML,
More informationSlide 1 Welcome to Fundamentals of Health Workflow Process Analysis and Redesign: Process Mapping: Entity-Relationship Diagrams. This is Lecture e.
WORKFLOW ANALYSIS Audio Transcript Component 10 Unit 3 Lecture E Fundamentals of Health Workflow Process Analysis & Redesign Interpreting and Creating Process Diagrams Process Mapping UML notation for
More informationWorkFlows Learning to Use the Staff Client. Version 3.5
WorkFlows Learning to Use the Staff Client Version 3.5 Contents Basic Terms... 4 SAILS... 4 Symphony... 4 WorkFlows... 4 Enterprise... 4 Getting Started... 5 Logging into WorkFlows... 5 The WorkFlows screen...
More informationUnit 6 - Software Design and Development LESSON 10 DESIGN TOOLS, INPUTS, OUTPUTS, STORYBOARDS
Unit 6 - Software Design and Development LESSON 10 DESIGN TOOLS, INPUTS, OUTPUTS, STORYBOARDS Previously Key features of programming languages Software Development Lifecycle Using tools to demonstrate
More informationSoftware Engineering
Software Engineering Engr. Abdul-Rahman Mahmood MS, PMP, MCP, QMR(ISO9001:2000) armahmood786@yahoo.com alphasecure@gmail.com alphapeeler.sf.net/pubkeys/pkey.htm http://alphapeeler.sourceforge.net pk.linkedin.com/in/armahmood
More informationUML Views of a System
UML Views of a System The architecture of a system is the fundamental organization of the system as a whole. The five UML Views: Use Case View: focuses on scenarios Design View: focuses on the vocabulary
More informationDatabase Systems. Overview - important points. Lecture 5. Some introductory information ERD diagrams Normalization Other stuff 08/03/2015
Lecture 5 Database Systems Instructor: M.Imran Khalil Imrankhalil3@gmail.com Resource:Imrankhalil3.wordpress.com University of Sargodha Canal Campus Lahore Overview - important points Some introductory
More information6.1 RELATIONSHIP CONCEPTS
1 SYLLABUS 6.1 Basic Entity Relationship Concepts: Entities, Relationship, Attributes 6.2 E R Diagram symbols 6.3 Conversion of Entity Relationship Model into Relations 6.4 Problems with Enitty Relationship
More informationPragmaDev. change request. Emmanuel Gaudin. PragmaDev ITU-T SG17 change request Grimstad June 24,
PragmaDev change request Emmanuel Gaudin emmanuel.gaudin@pragmadev.com Languages Table of contents PragmaDev introduction Languages SDL-RT Tool support Market tendancy Change requests Presentation PragmaDev
More informationEntity-Relationship Modelling. Entities Attributes Relationships Mapping Cardinality Keys Reduction of an E-R Diagram to Tables
Entity-Relationship Modelling Entities Attributes Relationships Mapping Cardinality Keys Reduction of an E-R Diagram to Tables 1 Entity Sets A enterprise can be modeled as a collection of: entities, and
More informationModule 5. Function-Oriented Software Design. Version 2 CSE IIT, Kharagpur
Module 5 Function-Oriented Software Design Lesson 12 Structured Design Specific Instructional Objectives At the end of this lesson the student will be able to: Identify the aim of structured design. Explain
More informationChapter 3 System Models
March 16, 2009 Introduction Graphical models aid in requirements and development Introduction Graphical models aid in requirements and development Different perspectives are possible: external: context
More information2.0.3 attributes: A named property of a class that describes the range of values that the class or its instances (i.e., objects) may hold.
T0/06-6 revision 2 Date: May 22, 2006 To: T0 Committee (SCSI) From: George Penokie (IBM/Tivoli) Subject: SAM-4: Converting to UML part Overview The current SCSI architecture follows no particular documentation
More informationArchitecture and the UML
Architecture and the UML Models, Views, and A model is a complete description of a system from a particular perspective Use Case Use Case Sequence Use Case Use Case Use Case State State Class State State
More informationChapter VI: Process Analysis and Modeling
1. Introduction In the structured analysis, the data is modeled by ERD diagram after requirements are collected. When the data feeds on the system, it is transformed to the output. Transforming an input
More informationA Rapid Overview of UML
A Rapid Overview of UML The Unified dmodeling Language (UML) Emerged in the mid 90s as the de facto standard for softwareengineering engineering design Use case diagram depicts user interaction with system
More informationAn Introduction to Business Process Modeling using Data Flow Diagrams
An Introduction to Business Process Modeling using Data Flow Diagrams BSAD 141 Dave Novak BDIS: 2.2 (61-77) Lecture Overview Systems and Business processes Business process models Data Flow Diagrams (DFDs)
More informationWorking with Health IT Systems is available under a Creative Commons Attribution-NonCommercial- ShareAlike 3.0 Unported license.
Working with Health IT Systems is available under a Creative Commons Attribution-NonCommercial- ShareAlike 3.0 Unported license. Johns Hopkins University. Welcome to the Fundamentals of Health Workflow
More informationSoftware Engineering Lab Manual
Kingdom of Saudi Arabia Ministry Education Prince Sattam Bin Abdulaziz University College of Computer Engineering and Sciences Department of Computer Science Software Engineering Lab Manual 1 Background:-
More informationLesson 11. W.C.Udwela Department of Mathematics & Computer Science
Lesson 11 INTRODUCING UML W.C.Udwela Department of Mathematics & Computer Science Why we model? Central part of all the activities We build model to Communicate Visualize and control Better understand
More informationLab Manual. Object Oriented Analysis And Design. TE(Computer) VI semester
Lab Manual Object Oriented Analysis And Design TE(Computer) VI semester Index Sr. No. Title of Programming Assignment Page No. 1 2 3 4 5 6 7 8 9 10 Study of Use Case Diagram Study of Activity Diagram Study
More informationAdvanced Interaction
8 Advanced nteraction Modeling The interaction model has several advanced features that can be helpful. You can skip this chapter on a first reading of the book. 8.1 Use Case Relationships ndependent use
More informationGoal: build an object-oriented model of the realworld system (or imaginary world) Slicing the soup: OOA vs. OOD
Domain analysis Goal: build an object-oriented model of the realworld system (or imaginary world) Slicing the soup: OOA vs. OOD OOA concerned with what, not how OOA activities focus on the domain layer
More informationFundamentals of Health Workflow Process Analysis and Redesign
Fundamentals of Health Workflow Process Analysis and Redesign Unit 10.3d Process Mapping Gane-Sarson Notation Slide 1 Welcome to the Gane-Sarson Notation for Data Flow Diagrams Subunit. This is the third
More informationUML DIAGRAM FOR PLATFORM ASSIGNMENT RAILWAY E-BOOK
01 January, 2018 UML DIAGRAM FOR PLATFORM ASSIGNMENT RAILWAY E-BOOK Document Filetype: PDF 200.01 KB 0 UML DIAGRAM FOR PLATFORM ASSIGNMENT RAILWAY E-BOOK Platform assignment system for the trains in a
More information(C) 2010 Pearson Education, Inc. All rights reserved. Dr. Marenglen Biba
Dr. Marenglen Biba In Chapters 12 13, you design and implement an object-oriented automated teller machine (ATM) software system. Concise, carefully paced, complete design and implementation experience.
More informationMAHARASHTRA STATE BOARD OF TECHNICAL EDUCATION (Autonomous) (ISO/IEC Certified) MODEL ANSWER
Important Instructions to examiners: 1) The answers should be examined by key words and not as word-to-word as given in the model answer scheme. 2) The model answer and the answer written by candidate
More informationUnified Modeling Language (UML)
Appendix H Unified Modeling Language (UML) Preview The Unified Modeling Language (UML) is an object-oriented modeling language sponsored by the Object Management Group (OMG) and published as a standard
More informationObject Oriented Modeling
Overview UML Unified Modeling Language What is Modeling? What is UML? A brief history of UML Understanding the basics of UML UML diagrams UML Modeling tools 2 Modeling Object Oriented Modeling Describing
More informationSOFTWARE DESIGN COSC 4353 / Dr. Raj Singh
SOFTWARE DESIGN COSC 4353 / 6353 Dr. Raj Singh UML - History 2 The Unified Modeling Language (UML) is a general purpose modeling language designed to provide a standard way to visualize the design of a
More informationUML & OO FUNDAMENTALS CSCI 4448/5448: OBJECT-ORIENTED ANALYSIS & DESIGN LECTURE 3 08/30/2011
UML & OO FUNDAMENTALS CSCI 4448/5448: OBJECT-ORIENTED ANALYSIS & DESIGN LECTURE 3 08/30/2011 1 Goals of the Lecture Review the material in Chapter 2 of the Textbook Cover key parts of the UML notation
More informationCourse "Softwaretechnik" Book Chapter 2 Modeling with UML
Course "Softwaretechnik" Book Chapter 2 Modeling with UML Lutz Prechelt, Bernd Bruegge, Allen H. Dutoit Freie Universität Berlin, Institut für Informatik http://www.inf.fu-berlin.de/inst/ag-se/ Modeling,
More informationA - 1. CS 494 Object-Oriented Analysis & Design. UML Class Models. Overview. Class Model Perspectives (cont d) Developing Class Models
CS 494 Object-Oriented Analysis & Design UML Class Models Overview How class models are used? Perspectives Classes: attributes and operations Associations Multiplicity Generalization and Inheritance Aggregation
More informationCSIT5300: Advanced Database Systems
CSIT5300: Advanced Database Systems L01: Entity Relationship (ER) Model Dr. Kenneth LEUNG Department of Computer Science and Engineering The Hong Kong University of Science and Technology Hong Kong SAR,
More informationChapter 6: Entity-Relationship Model. E-R Diagrams
Chapter 6: Entity-Relationship Model A database can be modeled as: a collection of entities, relationship among entities. An entity is an object that exists and is distinguishable from other objects. Example:
More informationMAHARASHTRA STATE BOARD OF TECHNICAL EDUCATION (Autonomous) (ISO/IEC Certified)
Subject Code: 17630 Model Answer Page No: 1 /32 Important Instructions to examiners: 1) The answers should be examined by keywords and not as word-to-word as given in the model answer scheme. 2) The model
More informationCS504-Softwere Engineering -1 Solved Objective Midterm Papers For Preparation of Midterm Exam
CS504-Softwere Engineering -1 Solved Objective Midterm Papers For Preparation of Midterm Exam MIDTERM EXAMINATION 2010 Question No: 1 ( Marks: 1 ) - Please choose one By following modern system engineering
More informationUNIT-4 Behavioral Diagrams
UNIT-4 Behavioral Diagrams P. P. Mahale Behavioral Diagrams Use Case Diagram high-level behaviors of the system, user goals, external entities: actors Sequence Diagram focus on time ordering of messages
More informationLecture 5 STRUCTURED ANALYSIS. PB007 So(ware Engineering I Faculty of Informa:cs, Masaryk University Fall Bühnová, Sochor, Ráček
Lecture 5 STRUCTURED ANALYSIS PB007 So(ware Engineering I Faculty of Informa:cs, Masaryk University Fall 2015 1 Outline ² Yourdon Modern Structured Analysis (YMSA) Context diagram (CD) Data flow diagram
More informationLecture 09. Spring 2018 Borough of Manhattan Community College
Lecture 09 Spring 2018 Borough of Manhattan Community College 1 Entity Relationship Modeling The Entity Relationship (ER) is a nontechnical communication model that describes the nature of the data and
More informationCS350 Lecture 2 Requirements Engineering. Doo-Hwan Bae
CS350 Lecture 2 Requirements Engineering Doo-Hwan Bae bae@se.kaist.ac.kr Contents Overview of Requirements Engineering OO Analysis: Domain modeling, Use-case, sequence, class Structured Analysis: Dataflow
More information3. Advanced E/R Concepts
What you will learn about in this section Subclasses & connection to OO 3. Advanced E/R Concepts Constraints Weak entity sets 75 76 Modeling Subclasses Modeling Subclasses Some objects in a class may be
More informationModeling Databases Using UML
Modeling Databases Using UML Fall 2017, Lecture 4 There is nothing worse than a sharp image of a fuzzy concept. Ansel Adams 1 Software to be used in this Chapter Star UML http://www.mysql.com/products/workbench/
More informationWhat is a Data Model?
What is a Data Model? Overview What is a Data Model? Review of some Basic Concepts in Data Modeling Benefits of Data Modeling Overview What is a Data Model? Review of some Basic Concepts in Data Modeling
More informationCOMP Instructor: Dimitris Papadias WWW page:
COMP 5311 Instructor: Dimitris Papadias WWW page: http://www.cse.ust.hk/~dimitris/5311/5311.html Textbook Database System Concepts, A. Silberschatz, H. Korth, and S. Sudarshan. Reference Database Management
More informationChapter 2, lecture 2 Modeling with UML
Object-Oriented Software Engineering Using UML, Patterns, and Java Chapter 2, lecture 2 Modeling with UML Overview: More detail on modeling with UML Use case diagrams Class diagrams Sequence diagrams Activity
More information