Group Y Presenters: (indicate roles)

Slides:



Advertisements
Similar presentations
OOAD – Dr. A. Alghamdi Mastering Object-Oriented Analysis and Design with UML Module 3: Requirements Overview Module 3 - Requirements Overview.
Advertisements

E-ARMOR: An Online Tool to Evaluate Polypharmacy in Elderly Persons
Cura EMR Data Collection Solution Presenters: Meghan McNeil (Project Manager) Michael Cybulski (Customer Liaison) Robert Victoria (Project Facilitator)
Drawing System Sequence Diagrams
Project Name Group Name: Customer: Name of Customer Project Manager: Student Name1 Project Facilitator: Student Name1 Customer Liaison/Domain Expert:Student.
NJIT Drawing System Sequence Diagrams Chapter 10 Applying UML and Patterns Craig Larman Presented by Anuradha Dharani.
USE Case Model.
Design Patterns Discussion of pages: xi-11 Sections: Preface, Forward, Chapter
Business Analysis and Essential Competencies
Demo Guidelines Lesson 9. Modules 9.1Demo Video Guidelines 9.2Begin Filming Pitch Video 9.3Continue working on prototype.
System Specification Specify system goals Develop scenarios Define functionalities Describe interface between the agent system and the environment.
Requirements Specification for Lab3 COP4331 and EEL4884 OO Processes for Software Development © Dr. David A. Workman School of Computer Science University.
Requirements Artifacts Precursor to A & D. Objectives: Requirements Overview  Understand the basic Requirements concepts and how they affect Analysis.
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…
PICTURE your design. Purpose : Functions & Content Functions the facilities that make the content of the ICT useful for relevant users and other ICT’s.
IMedLife Presenters: Armand (Web Manager) Ling (Facilitator) Rose (Project Manager) Wahhab (Domain Expert)
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.
VA Internal Use Only 1 Product Architecture Recommendation Briefing Template.
Active Learning.
Pepper modifying Sommerville's Book slides
Systems Analysis and Design in a Changing World, Fourth Edition
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
Welcome to M301 P2 Software Systems & their Development
Chapter 5 – System Modeling
Group Y Presenters: (indicate roles)
Computational Thinking, Problem-solving and Programming: General Principals IB Computer Science.
Architecture Concept Documents
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.
Use Case Model Use case diagram.
EKT 421 SOFTWARE ENGINEERING
Designing Information Systems Notes
CASE STUDY BY: JESSICA PATRON.
Software Engineering: A Practitioner’s Approach, 6/e Chapter 23 Estimation for Software Projects copyright © 1996, 2001, 2005 R.S. Pressman & Associates,
2018 SHOW-IT CATEGORY .
Are you ready for the Literacy Test?
CIS 510 Education for Service-- snaptutorial.com.
CIS 510 Teaching Effectively-- snaptutorial.com
Team members: Project Manager: Facilitator: Customer Liason:
denote Project Managers explicitly
Requirements – Scenarios and Use Cases
Unit 13: Website Development
Chapter 9 Use Cases.
Object Oriented Analysis and Design
Team Members: Member1, … Spring 2013
Concept maps.
NEW TRAINING PROGRAMME
DESIGNING YOUR SYSTEM.
Summer Reading Test Study Guide
More Requirements Models
Software Design Lecture : 15.
OOA&D II Bo Wang, Kan Qi Adapted from Alexey Tregubov’s Slides.
Software Engineering: A Practitioner’s Approach, 6/e Chapter 23 Estimation for Software Projects copyright © 1996, 2001, 2005 R.S. Pressman & Associates,
Dr. M. L. Holt Application #8 Morgan State University
Quality Improvement Initiative Title Presenter Name(s)
What stresses you out? With your group make a list of things that stress you out. Then try to order then from the most stressful to the least stressful.
Chapter 5 Understanding Requirements.
Tourist attractions in Wales
Dr. M. L. Holt Application #8 Morgan State University
-Who -What -Where -Why -When -How
To investigate the home life of women in depressed areas in the 1930s.
Chapter 26 Estimation for Software Projects.
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 Identify the design patterns used for system (use color or other means to distinguish design patterns). Explain the rationale for the design pattern use

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

Related Work Mention any related work (similar systems) How are they similar? How are they different?

Lessons Learned Describe key design decisions that made it easier to build Describe a few things that you would do differently in retrospect Open areas for future work

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

Video demonstration Play your Camtasia video illustrating how to use your system Should include demonstration of key features

Live Demonstration I Prose description of scenario illustrating prototype functionality Give live planned demonstration

Live Demonstration II Solicit input from audience to walk through a few more scenarios Alternatively let someone from audience try out the system.