Software Engineering Lecture #5.

Slides:



Advertisements
Similar presentations
FROM INCEPTION TO ELABORATION Use Cases, Domain Models & SSDs Oh My!
Advertisements

Use Case Diagrams.
Withdrawal Transaction Use Case Primary Actor: Customer Pre-conditions: The customer must have a valid ATM card and PIN. Post-conditions: The customer.
Use Case & Use Case Diagram
Using Track Changes in Microsoft Word Navigating Directions Click on the arrows or the home button located in the bottom right-hand corner of each.
Karolina Muszyńska Based on:
Use Case Diagram © copyright 2001 SNU OOPSLA Lab..
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.
SE 555 Software Requirements & Specification 1 Misuse Cases.
Requirements
Software engineering Olli Alm Lecture 2: requirements, modelling & representation.
Introduction to UNIX Acknowledgement:Thanks to Dr Andrew Horner for the original version of this set of slides. All trademarks are the properties of their.
Use Case Diagram.
Automatic Software Testing Tool for Computer Networks ARD Presentation Adi Shachar Yaniv Cohen Dudi Patimer
Use Case What is it?. Basic Definition Of who can do what within a system? TemplateDiagramModelDescription.
Project Analysis Course ( ) Week 2 Activities.
Software Engineering – University of Tampere, CS DepartmentJyrki Nummenmaa USE CASES In this lecture: Use cases - What are use.
® IBM Software Group © 2006 IBM Corporation Rational Software France Object-Oriented Analysis and Design with UML2 and Rational Software Modeler 06. Requirements.
Software Development Stephenson College. Classic Life Cycle.
1 Objectives  Describe design constraints.  Identify methods of specifying functional requirements.  Describe techniques for writing and structuring.
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.
Intro: Use Case and Use Case Diagram Documentation.
UML The Unified Modeling Language A Practical Introduction Al-Ayham Saleh Aleppo University
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.
Requirements Documentation CSCI 5801: Software Engineering.
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
Parent Portal The txConnect parent portal allows parent’s to monitor their student’s progress in school.
1 Object-Oriented Modeling Using UML CS 3331 Section 2.4 Modeling Requirements with Use Cases.
UML-1 8. Capturing Requirements and Use Case Model.
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.
Get Access to your Online Course Tools Course: Instructor: Office: Hours:
CS 772: Global Knowledge Networks V. “Juggy” Jagannathan CSEE, West Virginia University.
1 Version /05/2004 © 2004 Robert Oshana Requirements Engineering Use cases.
Unified Modeling Language User Guide Section 4 - Basic Behavioral Modeling Chapter 16 - Use Cases Chapter 17 - Use Case Diagrams.
Requirements and Use Cases
UML (Unified Modeling Language)
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.
LESSON 2 Microsoft PowerPoint THE GOAL OF THIS LESSON IS FOR STUDENTS TO SUCCESSFULLY CREATE A THEMED PRESENTATION AS WELL AS MAKE MODIFICATION.
TREND 963 Basic Operation Course Helpful hints for running your Trend 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.
Chapter 4 – System Modeling Lecture 1 1Chapter 5 System modeling.
LOGO Supervisor: Mr.Huỳnh Anh Dũng Students: Nguyễn Công Tuyến Nguyễn Cảnh Phương Phạm Thị Hằng Bùi Thị Huệ Trần Đức Bình Nguyễn.
Microsoft PowerPoint 2010 Lesson 2 Created by Felicia Hudson, Riverside High School--Durham Public Schools.
Chapter 5 – System Modeling
Using Use Case Diagrams
Chapter 5 System modeling
CMPE 280 Web UI Design and Development August 29 Class Meeting
Requirements: Use Case Models and Narratives
مقدمه اي بر مهندسي نيازمنديها
Microsoft PowerPoint 2010 Lesson 2
SAD ::: Spring 2018 Sabbir Muhammad Saleh
UML Diagrams: Sequence Diagrams Dynamic Analysis Model
Software Engineering System Modeling Chapter 5 (Part 1) Dr.Doaa Sami
Software Design Lecture : 15.
Use Case Model Use case diagram – Part 2.
Using Use Case Diagrams
Use Case Modeling.
Presentation title here
Multiple Slide Timeline (1)
The Title of the Paper Author 1, Company Affiliation
(Software) reuse, is the use of (Software) knowledge, to build new (something) software.
Software Engineering Lecture #6
Android Access Control
Presentation transcript:

Software Engineering Lecture #5

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

Use Case Example Delete Information

Use Case Example Delete Information

Use Case Example Delete Information

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.)

Activity Diagram

Activity Diagram

Activity Diagram

Limitation of Use Cases Usability: Color blind people should not have any difficulty in using the system – color coding should take care of common forms of color blindness. Reliability: The system needs to support 7 x 24 operation Performance: Authorization should be completed within 1 minute 90% of the time. Average authorization confirmation time should not exceed 30 seconds. Portability: The system should run on Windows 98 and above as well as Sun Solaris 7.0 and above. Access: System should be accessible over the internet – hidden requirement – security.