Software Engineering Lecture #6

Slides:



Advertisements
Similar presentations
Project Analysis Course ( ) Final Project Report Overview.
Advertisements

Karolina Muszyńska Based on:
1 Use Cases 2 CSSE 371 Software Requirements and Specification Mark Ardis, Rose-Hulman Institute September 20, 2004.
Use Case Diagram © copyright 2001 SNU OOPSLA Lab..
Use Case modelling 3 How to go from a diagram to a further definition.
Use Case modelling How to go from a diagram to a further definition.
Use Cases & Requirements Analysis By: Mostafa Elbarbary.
© 2005 Prentice Hall4-1 Stumpf and Teague Object-Oriented Systems Analysis and Design with UML.
Functional Requirements – Use Cases Sriram Mohan/Steve Chenoweth (Chapters 14, 21 – Requirements Text) 1.
Software engineering Olli Alm Lecture 2: requirements, modelling & representation.
Use Case Diagram.
Unified Modeling Language
Use case diagrams A use case diagram is UML’s notation for showing the relationships among a set of use cases and actors A use case diagram can help the.
Use Case What is it?. Basic Definition Of who can do what within a system? TemplateDiagramModelDescription.
1 Requirements Modeling using UML 2.0 Use Cases. 2 Requirements Engineering Software Lifecycle Activities System Engineering Requirements Analysis Software.
Software Development Stephenson College. Classic Life Cycle.
1 Object-Oriented Modeling Using UML (2) CS 3331 Fall 2009.
Use Case Modeling. Watch the video on use cases Review at minute 2:41-3:37.
UML The Unified Modeling Language A Practical Introduction Al-Ayham Saleh Aleppo University
Chapter 7 IS630. Project Design  Technical Design & Specification Network and System Architecture & Design Software System Architecture & Design  Database.
UML Diagrams: Sequence Diagrams The Requirements Model, and The Dynamic Analysis Model Instructor: Dr. Hany H. Ammar Dept. of Computer Science and Electrical.
Use Cases 7/09. lnot part of the system lrepresents roles a user can play lrepresents a human, a machine or another system lactively exchanges information.
1 UML Basic Training. UML Basic training2 Agenda  Definitions: requirements, design  Basics of Unified Modeling Language 1.4  SysML.
 A software application is like a city  Modeling = Architecture  OOP = Civil Engineering  UML Classes = Blueprints of Buildings  UML is a common.
Faculty of Computer & Information
UML-1 8. Capturing Requirements and Use Case Model.
1 Use Case Modeling Reference: RUP Doc. Use Case Example 2.
Faculty of Applied Engineering and Urban Planning Software Engineering Department Software Engineering Lab Use Cases Faculty of Information system Technology.
Touseef Tahir Lecturer CS COMSATS Institute of Information Technology, Lahore USE CASES BY.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Slide 1 Use Case Diagrams.
Functional Requirements – Use Cases (Chapters 14, 21) Sriram Mohan 1.
Use Case Diagram The purpose is to communicate the system’s functionality and behaviour to the customer or end user. Mainly used for capturing user requirements.
CS 772: Global Knowledge Networks V. “Juggy” Jagannathan CSEE, West Virginia University.
1 Version /05/2004 © 2004 Robert Oshana Requirements Engineering Use cases.
Software Engineering Software Engineering - Mr. Ahmad Al-Ghoul.
Unified Modeling Language User Guide Section 4 - Basic Behavioral Modeling Chapter 16 - Use Cases Chapter 17 - Use Case Diagrams.
Requirements and Use Cases
Prof. Hany H. Ammar, CSEE, WVU, and
Inserting Hyperlinks  Purpose : Enables viewers to click the link and move directly to a slide  Directions : Make one link on slide one to move to each.
CSCI 383 Object-Oriented Programming & Design Lecture 7 Martin van Bommel.
Page 1  Copyright © 1997 by Rational Software Corporation Putting the UML to Work The ESU University wants to computerize their registration system –
George Wang, Ph.D. COMP 380/L Lesson 2. Use Case Use cases are a way to capture system functionalities (i.e., functional requirements) Based on use case.
Internal Logical Files (ILF) An internal logical file (ILF) is a user identifiable group of logically related data or control information maintained within.
CompSci 280 S Introduction to Software Development
Software Engineering Lecture #41
Use case diagrams A use case diagram is UML’s notation for showing the relationships among a set of use cases and actors A use case diagram can help the.
Creating Use Cases.
Requirements: Use Case Models and Narratives
Software Engineering Lecture #39
SAD ::: Spring 2018 Sabbir Muhammad Saleh
Object Oriented Analysis and Design
UML Diagrams: Sequence Diagrams Dynamic Analysis Model
Software Engineering Lecture #5.
Software Engineering System Modeling Chapter 5 (Part 1) Dr.Doaa Sami
Software Engineering Lecture #25
Software Engineering Lecture # 17
Software Engineering Lecture #26
Software Design Lecture : 15.
Use Case Model Use case diagram – Part 2.
Using Use Case Diagrams
Software Engineering Lecture # 01
Software Engineering Lecture #35
Extreme Programming.
Software Engineering Lecture #3
Software Engineering System Modeling Chapter 5 (Part 1) Dr.Doaa Sami
Software Engineering Lecture #40
Software Engineering Lecture #16
Software Engineering Lecture #29
Software Engineering Lecture #28
(Software) reuse, is the use of (Software) knowledge, to build new (something) software.
Presentation transcript:

Software Engineering Lecture #6 Fakhar Lodhi

Reuse and Extension An Example Notes of the animations (highlight all the points) 1. Cellular Network 2. User 3. Place Phone call 4. Receive phone call 5. Use scheduler 5. Place conference call 6. Receive additional call 7. extend -- written at the top 8. extend -- written at the bottom

Extended User An Example Notes of the animations Show all the slide and then scroll to the customer and individual customer and corporate customer ----- Zoom to these objects. (highlight text and arrow color) 1. Customer 2. Individual customer – with its arrow going towards the customer 2. Corporate Customer -- with its arrow going towards the customer

Components Of A Use Case Priority Actor Summary Precondition Post- Condition Extend Normal Course of Events Alternative Path Exception Assumption

Use Case Example Delete Information Information in the doc file as slide No 5.doc

Activity Diagram Animation sequence is on the slide. Use arrow for animation If it does not fit on one slide then u can use the scrolling feature. Take care show at least three levels at a time (not less in any case and then use the highlight feature.)

Reuse Extension and Inclusion

Recap

Describing a Use Case

An Example of a Detailed Use Case

Summary of Today’s Lecture

Activity Diagram

Use Case Example Delete Information

Use Case Example Delete Information

Use Case Example Delete Information

Use Case Example Delete Information

Activity Diagram

Activity Diagram

Activity Diagram

Limitation of Use Cases