Group Y Presenters: (indicate roles)

Slides:



Advertisements
Similar presentations
E-ARMOR: An Online Tool to Evaluate Polypharmacy in Elderly Persons
Advertisements

Cura EMR Data Collection Solution Presenters: Meghan McNeil (Project Manager) Michael Cybulski (Customer Liaison) Robert Victoria (Project Facilitator)
Drawing System Sequence Diagrams
Lecture 12: Chapter 22 Topics: UML (Contd.) –Relationship Structural Behavioral –Diagram Structural Behavioral.
CLAReT PERSONAS AND SCENARIOS. When? Personas were used in the CLAReT workshops as a role play activity. Participants were required to assume a persona.
Project Name Group Name: Customer: Name of Customer Project Manager: Student Name1 Project Facilitator: Student Name1 Customer Liaison/Domain Expert:Student.
USE Case Model.
® IBM Software Group © 2006 IBM Corporation Rational Software France Object-Oriented Analysis and Design with UML2 and Rational Software Modeler 06. Requirements.
1 Scenario template. 2 PART 1: INTRODUCTION ➔ Your organisation ➔ Starting point of your project ➔ The target group ➔ What do you want to achieve? SERVICE.
Requirements Artifacts Precursor to A & D. Objectives: Requirements Overview  Understand the basic Requirements concepts and how they affect Analysis.
Requirements Documentation CSCI 5801: Software Engineering.
Following the submission of your CV and letter of application, the head of Human Resources has invited you to proceed to the second stage of the recruitment.
Requirements Capture. Four Steps of requirements capture List candidate requirements Understand system context Capture functional requirements Capture.
UML-1 8. Capturing Requirements and Use Case Model.
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.
Project X Group Y Presenters: (indicate roles). Part I: Project Overview System provides functionality X Motivation for project –Address problem with…
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Slide 1 Use Case Packets.
CIS 4910 Information Systems Development Project Project Documentation.
IMedLife Presenters: Armand (Web Manager) Ling (Facilitator) Rose (Project Manager) Wahhab (Domain Expert)
CSCI 383 Object-Oriented Programming & Design Lecture 7 Martin van Bommel.
Copyright © 2014 Pearson Canada Inc. 5-1 Copyright © 2014 Pearson Canada Inc. Application Extension 5a Database Design Part 2: Using Information Technology.
Chapter 5 – System Modeling
Pepper modifying Sommerville's Book slides
Application Extension 5a
What is a CONOPS anyway? Avoiding Brook’s “law”: “All major mistakes are made on the first day of the project”!
Working out the Details
Methodology Conceptual Databases Design
Chapter 5 – System Modeling
Architecture Concept Documents
Methodology Conceptual Database Design
BTS430 Systems Analysis and Design using UML
Use Case Model.
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.
Column Sequences An Investigation.
Creating Use Cases.
Introduction to Triggers
Structure and Planning
Chapter Two Cross-Cultural Business
EKT 421 SOFTWARE ENGINEERING
2018 SHOW-IT CATEGORY .
BSA 411 Competitive Success/snaptutorial.com
BSA 411 Education for Service/snaptutorial.com
BSA 411 Teaching Effectively-- snaptutorial.com
Team members: Project Manager: Facilitator: Customer Liason:
denote Project Managers explicitly
Group Y Presenters: (indicate roles)
Requirements – Scenarios and Use Cases
Unified Modeling Language
Chapter 9 Use Cases.
Object Oriented Analysis and Design
Team Members: Member1, … Spring 2013
Concept maps.
Systems Analysis and Design in a Changing World, 6th Edition
DESIGNING YOUR SYSTEM.
Summer Reading Test Study Guide
OOA&D II Bo Wang, Kan Qi Adapted from Alexey Tregubov’s Slides.
Requirements Engineering Processes
Essential Question: Changes in Supply SECTION 2
Understanding Standards
Full Title of Research Proposal
Methodology Conceptual Databases Design
Chapter 5 Understanding Requirements.
Investigation Title by.
Tourist attractions in Wales
Chapter 22 Object-Oriented Systems Analysis and Design and UML
Chapter 26 Estimation for Software Projects.
TYPE TOPIC HERE Type general description here Type number Type number
Interface Design and Usability
Week 10 Systems Development
Presentation transcript:

Group Y Presenters: (indicate roles) Project X Group Y Presenters: (indicate roles)

Part I: Project Overview System provides functionality X Motivation for project Address problem with Facilitates what…

Overview of Features Feature 1 Feature 2 Feature 3

Domain Research Investigated area X Needed to apply domain knowledge on topic Y Project Constraints Constraint 1 Constraint 2 Constraint 3

Risk Analysis Identify risk factors affecting project … How did you mitigate risks?

Part II: Model-based View of System Give us use case diagram Explain key use cases Walk us through class diagram Give us a few representative scenarios in terms of sequence diagrams Walk us through the state diagram of a few key objects

Description of Use Case Diagram Give and describe use case diagram Briefly describe key use cases Take one use case and give details

Description of Class Model General layout of class model Why model is constructed this way

Behavior Model: Sequence Diagrams Give 1 normal scenario in terms of sequence diagram Give a scenario describing exceptional situation in terms of sequence diagram

Behavior Model: State Diagrams Give state diagram for at least two key (interacting) classes. Explain interaction

Part III: Demo of Prototype High-Level features of User Interface Feature 1 Feature 2 Etc.

Scenario(s) Prose description of scenario illustrating prototype functionality Give sequence diagram(s) for scenarios

Sequence Diagram for Scenario Additional scenarios with additional sequence diagrams