Project X Group Y Presenters: (indicate roles). Part I: Project Overview System provides functionality X Motivation for project –Address problem with…

Slides:



Advertisements
Similar presentations
What is an Extended Response?
Advertisements

FROM INCEPTION TO ELABORATION Use Cases, Domain Models & SSDs Oh My!
<<Date>><<SDLC Phase>>
Software Modeling SWE5441 Lecture 3 Eng. Mohammed Timraz
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
Systems Analysis and Design in a Changing World, Fourth Edition
TSS Architecture Definition Context. TSS Scoping Study Context Detailed Requirements Specification (products, functionality) High Level Architecture Description.
Project Name Group Name: Customer: Name of Customer Project Manager: Student Name1 Project Facilitator: Student Name1 Customer Liaison/Domain Expert:Student.
Chapter 7: The Object-Oriented Approach to Requirements
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.
Architectural Design.
1 Office of Instructional Technology-Queens iTeach The Office of Instructional Technology provides innovative solutions to transform teaching, learning,
Model Performance Indicators.
Software Engineering Muhammad Fahad Khan
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 18 Slide 1 Software Reuse.
Chapter 5 – System Modeling
ISO Tor Stålhane IDI / NTNU. What is ISO ISO 9001 was developed for the production industry but has a rather general structure ISO describes.
® 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.
UML & Prototyping. What is a prototype? A prototype is a small-scale model. It can be (among other things): a series of screen sketches a storyboard,
Programming Project (Last updated: August 31 st /2010) Updates: - All details of project given - Deadline: Part I: September 29 TH 2010 (in class) Part.
From Use Cases to Test Cases 1. A Tester’s Perspective  Without use cases testers will approach the system to be tested as a “black box”. “What, exactly,
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.
EdTPA Teacher Performance Assessment. Planning Task Selecting lesson objectives Planning 3-5 days of instruction (lessons, assessments, materials) Alignment.
Methodology - Conceptual Database Design. 2 Design Methodology u Structured approach that uses procedures, techniques, tools, and documentation aids to.
SE: CHAPTER 7 Writing The Program
Behavioral Modeling Chapter 8.
Methodology - Conceptual Database Design
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.
Assessing the influence on processes when evolving the software architecture By Larsson S, Wall A, Wallin P Parul Patel.
Requirements Capture. Four Steps of requirements capture List candidate requirements Understand system context Capture functional requirements Capture.
Notes of Rational Related cyt. 2 Outline 3 Capturing business requirements using use cases Practical principles  Find the right boundaries for your.
SOA Landscape Recommendations By >. Who we are  Team Members  Company History  Current & Past Client Projects  Note: have fun here. Make up your history.
UML-1 8. Capturing Requirements and Use Case Model.
7 Systems Analysis and Design in a Changing World, Fifth Edition.
1 Chapter 4 Analyzing End-to-End Business Processes.
1 What is OO Design? OO Design is a process of invention, where developers create the abstractions necessary to meet the system’s requirements OO Design.
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.
PICTURE your design. Purpose : Functions & Content Functions the facilities that make the content of the ICT useful for relevant users and other ICT’s.
ECE450 - Software Engineering II1 ECE450 – Software Engineering II Today: Introduction to Software Architecture.
Human Computer Interaction
Facilitate Group Learning
Systems Analysis and Design in a Changing World, Fourth Edition
Techniques for presenting content
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 4 Slide 1 Software Processes.
21/1/ Analysis - Model of real-world situation - What ? System Design - Overall architecture (sub-systems) Object Design - Refinement of Design.
4+1 View Model of Software Architecture
IMedLife Presenters: Armand (Web Manager) Ling (Facilitator) Rose (Project Manager) Wahhab (Domain Expert)
VA Internal Use Only 1 Product Architecture Recommendation Briefing Template.
Jill Flanigan, MLS, MS, RHIT Bristol Community College HCI 244 Health Information Systems and Technology.
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”!
Chapter 5 – System Modeling
Group Y Presenters: (indicate roles)
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.
CASE STUDY BY: JESSICA PATRON.
Team members: Project Manager: Facilitator: Customer Liason:
denote Project Managers explicitly
Group Y Presenters: (indicate roles)
Requirements – Scenarios and Use Cases
Object Oriented Analysis and Design
Team Members: Member1, … Spring 2013
Systems Analysis and Design in a Changing World, 6th Edition
ATS Architecture Design Solution Intent
Full Title of Research Proposal
<Your Team # > Your Team Name Here
Presentation transcript:

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 Feature 4 Feature 5

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

Special Constraint Analysis (e.g., Security) Identify security factors affecting project … How did you mitigate security risks? Add more slides if you needed to handle any other constraints

Part II: Model-based View of System Explain the main functions through (choose): –Give us use case diagram Explain key use cases –Walk us through scenarios –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 Scenarios Give and describe an illustration Briefly describe key scenarios Take one scenario and give details

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 Diagram 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 patterns used Identify the cross-cutting concern(s) –How did you use aspect-oriented programming?

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

Description of Architectural Design Show us the original (without components) and final (using components) designs Show the “new” integrated deign –Explain the choice of design selected –Explain key differences in new design Tell us about the major challenges with reusing components

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

Lessons Learned Describe the lessons learned from the process Describe key design decisions that made it easier/faster to build Describe a few things that you would do differently in retrospect Explain the project extensions/open areas for future work

Part III: Demo Live demo Video demo (e.g., Camtasia video illustrating how to use your system) Etc. Should include demonstration of key features

Live Demo 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.

Q & A Provide some time for questions and answers