1. Agenda Introduction Problem Restate Project Progression Use Case Narratives UML Use Case Diagram Data Flow Diagrams Functional Requirements Prototype.

Slides:



Advertisements
Similar presentations
Karolina Muszyńska Based on:
Advertisements

Chapters 7 & 9 System Scope
Title 1 Software Linked Interactive Competitive Environment Preliminary Design November 7 th, 2011.
System Modelling System modelling helps the analyst to understand the functionality of the system and models are used to communicate with customers. Different.
Preliminary Design: Smart Scheduling Client: Dr. Robert Yoder.
1 SWE Introduction to Software Engineering Lecture 16 – System Modeling An Example.
Title 1 Software Linked Interactive Competitive Environment Software Requirements Specification November 2 nd, 2011.
Jan 8, Ron McFadyen1 Waterfall Spiral UP Case study UML Use Cases.
Requirements Specification: Smart Scheduling Client: Dr. Robert Yoder.
FSH Technologies Preliminary Design: F.I.L.E.T. December 9, 2011.
Competitive Algorithm Calculation Testing in a Unified System (C.A.C.T.U.S.) Requirements Specification 11/2/2011 Presented By: ExoNET Solutions 1.
Competitive Algorithm Calculation Testing in a Unified System (C.A.C.T.U.S.) Preliminary Design 12/7/2011 Presented By: ExoNET Solutions 1.
Chapter 7: The Object-Oriented Approach to Requirements
Use Case Diagrams Week 1 – Lab 1.
Monday, October 29 st 2012 Requirements Specification.
Lecture Outline 11 The Development of Information Systems Chapter 8 page 390+
Analysis Modeling (cont’d) CpSc 372: Introduction to Software Engineering Jason O. Hallstrom Authorship Disclaimer. These slides.
Systems Analysis – Analyzing Requirements.  Analyzing requirement stage identifies user information needs and new systems requirements  IS dev team.
Copyright © 2005 Hyundai Team 1 Intelligent Traffic Forecast System Hyundai Team
SOFTWARE ENGINEERING BIT-8 APRIL, 16,2008 Introduction to UML.
10/12/2001Data Structure1 Relationships Between The Data Flow Diagram and The Systems Design Activities Mohammad A. Rob School of Business and Public Administration.
Data-Flow Diagrams Week 10 Lecture 1. Data Flow Diagrams (DFDs) One of most important modelling tools used by system analysts In use since late 1970’s.
C hevrolet A dvance- D esign S eries Paint Visualizer Detailed Design YOUR DREAM, OUR SOLUTION 1.
1 Software Requirements Specification Presentation Client Dr. Darren Lim Friday October 30, 2009 Java.Online.Learning.Tutor.
Hobb-IT Hobby Information Tracker By Illumination Technologies Requirements Specification October 28 rd Illumination Technologies Hobb-IT.
Conceptual Design versus Logical Design. Conceptual Data Design Prepared at beginning of project High level view of how the client sees the data Top down.
OBJECT ORIENTED METHODOLOGIES Week04. Agenda… © Jerry Kotuba SYST39409-Object Oriented Methodologies 2  This week  Quiz 1  Take up ICE-01  Check “Grade.
Lecture 3: Visual Modeling & UML 1. 2 Copyright © 1997 by Rational Software Corporation Computer System Business Process Order Item Ship via “ Modeling.
Requirements Analysis Visual Modeling] Lab 02 Visual Modeling (from Visual Modeling with Rational Rose and UML) A way of thinking about problems using.
Requirements Documentation CSCI 5801: Software Engineering.
Title 1 Software Linked Interactive Competitive Environment Detailed Design March 1 st, 2012.
Friday, December 7 th 2012 Preliminary Design. IntroductionRestatement of ProblemProject ProgressionUser Case NarrativesUse Case DiagramDeployment DiagramWebsite.
R.O.S.E.S. Preliminary Design Presented By: Code Shark Solutions 12/8/10.
Actors and Use Case Diagrams Month Day, Year. Agenda Training Plan Overview Review Detailing Requirements with Requisite Pro Concepts Setting Up XDE Integration.
Learning Objective The students should be able to: a. state the definition of software b. state the usage of software c. list different types of software.
CCRS Comprehensive Conference Registration System Preliminary Design December 7 th,
Sequence diagram in UML Martin Palkovik. Sequence diagram  It is a graphic representation of system operations based on chronology - a time sequence.
Introduction To OOP 1.0 Fundamentals Of Java Programming Language 2.0 Exception Handling 3.0 Classes, Inheritance And Polymorphism © 2011 | PN AZRINA.
Mosaic Creator Lance Finfrock CS 470. Introduction A Mosaic is hundreds or thousands of pictures comprised to make one picture.
(c) Addison Wesley Copyright © 2000 by Addison Wesley Version 1.0
DESIGN PART 2: OBJECT-LEVEL SEQUENCE DIAGRAMS WITH AN EXAMPLE OF COMPOSITION BTS430 Systems Analysis and Design using UML.
Chapter 11 Using SAS ® Web Report Studio. Section 11.1 Overview of SAS Web Report Studio.
UML Examples PRESETED BY: MEHRAN NAJAFI SHIMA AGHTAR.
CS212: Object Oriented Analysis and Design Lecture 32: Use case and Class diagrams.
Use Case Textual Analysis
Lab Course / Praktikum: S ummer Semester 2012 Project Management and Software Development for Medical Applications Computer Aided Medical Procedures (CAMP),
Database for online bookstore Yaxian Yao
IS3320 Developing and Using Management Information Systems Lecture 16: Data-Flow Diagrams 1 (Intro to Context-Level diagrams) Rob Gleasure
1 LAB What is Collaboration diagram? 4 Collaboration diagrams illustrate the interaction between the objects, using static spatial structure. 4.
1 SEQUENCE DIAGRAM EXAMPLE The domain model, showing the navigability of the associations, and the Reserve video (staff scenario) use-case description.
Context Diagram This section includes two parts. Part 1: Description of a Context Diagram Part 2: How To construct a Context Diagram.
Chapter 5 System Modeling (1/2) Yonsei University 2 nd Semester, 2015 Sanghyun Park.
Data Flow Diagrams. A diagram which shows the movement of data in a system.
High Level Design Use Case Textual Analysis SE-2030 Dr. Mark L. Hornick 1.
C hevrolet A dvance- D esign S eries Paint Visualizer Detailed Design YOUR DREAM, OUR SOLUTION 1.
TA: Shreya Rawal.  A use case is a description of a system’s behavior as it responds to a request that originates from outside of that system (Usually.
October 30 th /28/2013 Requirements Specification 2 Client: Dr. Timoth Lederman Guest: Dr. Darren Lim Guest: Dr. Meg Fryling.
Chapter 4 – System Modeling Lecture 1 1Chapter 5 System modeling.
1 Use Cases Object-Oriented Modeling and Design with UML (Second Edition) Blaha & Rumbaugh Sections 7.1, 8.1.
Advanced Higher Computing Science
WHAT IS A Context Diagram?
Object-oriented and Structured System Models
Data Flow Diagrams.
Management Movie Management System Customers Databases Vendors
G063 - Data flow diagrams.
تحلیل سیستم‌ها مدل‌سازی پردازشی.
DATA FLOW DIAGRAM.
G063 - Data flow diagrams.
Software Design Lecture : 15.
واسط كاربري هوشمند Intelligent User Interface
Presentation transcript:

1

Agenda Introduction Problem Restate Project Progression Use Case Narratives UML Use Case Diagram Data Flow Diagrams Functional Requirements Prototype Screens What’s Next? 2

3

Agenda Introduction Problem Restate Project Progression Use Case Narratives UML Use Case Diagram Data Flow Diagrams Functional Requirements Prototype Screens What’s Next? 4

5

Agenda Introduction Problem Restate Project Progression Use Case Narratives UML Use Case Diagram Data Flow Diagrams Functional Requirements Prototype Screens What’s Next? 6

7

Agenda Introduction Problem Restate Project Progression Use Case Narratives UML Use Case Diagram Data Flow Diagrams Functional Requirements Prototype Screens What’s Next? 8

9

10

11

Agenda Introduction Problem Restate Project Progression Use Case Narratives UML Use Case Diagram Data Flow Diagrams Functional Requirements Prototype Screens What’s Next? 12

Actor: An entity that interacts with the system externally. This can be either a human or non-human user. Use Case: A component within the system that actors may interact with. System Boundary: A boundary between internal and external components. A Actor A interacts with all of the systems Use Cases AB A A B A B B Actor A interacts with Use Case B Actor B interacts with all Use Cases that Actor A is able to interact with. Use Case A includes Use Case B Use Case B is a more specific type of Use Case A 13

14

Agenda Introduction Problem Restate Project Progression Use Case Narratives UML Use Case Diagram Data Flow Diagrams Functional Requirements Prototype Screens What’s Next? 15

16 GMC TruckCustomizer CADS GMC TruckRestorer CADS MySQL Database

17

User 1.1 View Library Request 1.2 Get Library View Library Request View Library Request Truck Library Truck Library Truck Library 18

CADS MySQL Database User 2.3 Enter Truck Information 2.1 Display Truck 2.2 Get Truck Information Truck Information Truck Information Truck Image Truck Image Truck Image 19

User 3.2 Select Color and Section 3.3 Display New Truck Color/Section Request Color/Section Request New Truck CADS MySQL Database 3.1 Get Factory Colors Request Colors Request Colors Factory Colors Factory Colors 20

User 4.1. Select View 4.2 Change View Request View New View New View Image 21

CADS MySQL Database User 5.1 View Library View Library Request 5.2 Get Library View Library Request View Library Request Truck Library Truck Library Truck Library 22

Agenda Introduction Problem Restate Project Progression Use Case Narratives UML Use Case Diagram Data Flow Diagrams Functional Requirements Prototype Screens What’s Next? 23

The two types of users are restorers and customizers. Restorer Will be able to choose from the original factory colors of the selected truck that will be stored in a database created by YDOS. Customizer Will be able to choose any color that the user wants using a color wheel. 24

Agenda Introduction Problem Restate Project Progression Use Case Narratives UML Use Case Diagram Data Flow Diagrams Functional Requirements Prototype Screens What’s Next? 25

26

Agenda Introduction Problem Restate Project Progression Use Case Narratives UML Use Case Diagram Data Flow Diagrams Functional Requirements Prototype Screens What’s Next? 27

28

29