Team Members: Member1, … Spring 2013

Slides:



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

Overview of Project APCA1 Software Engineering CSE435 Michigan State University Fall 2014 Team members: Project Manager: Eric Drews Facilitator: Daniel.
Cura EMR Data Collection Solution Presenters: Meghan McNeil (Project Manager) Michael Cybulski (Customer Liaison) Robert Victoria (Project Facilitator)
Overview of MultipleInput Power Steering Software Engineering CSE 435 Michigan State University Fall 2014 Team members: Project Manager: Gregory Andrew.
Drawing System Sequence Diagrams
Team READ THIS SLIDE CAREFULLY Alpha Demonstrations will be given by each team at our all-hands meeting on the dates listed at All-Hands Meeting Agendas.All-Hands.
Technical Specification / Schedule Department of Computer Science and Engineering Michigan State University Spring 2007 Team : CSE 498, Collaborative Design.
1 Spring 2007 CSCI 660 CSCI-660 Project Title Project team members’ names.
6. & 7. Teams: Technical Specification / Schedule Project Title Team Member 1 Team Member 2 Team Member 3 Team Member 4 Department of Computer Science.
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.
Overview of Team Ford: Active Park Assist Software Engineering - CSE435 Michigan State University Fall 2014 Team members: Project Manager: Joe Reeder Facilitator:
R R R CSE870: Advanced Software Engineering: Cheng (Sp 2001)CSE870: Advanced Software Engineering: Cheng (Sp 2001)1 Mini Project An Overview.
Team Members Rachid Alaoui Medarhri (Senior Student). Tarek Bougroug (Senior Student). Supervised By : Dr. Driss Kettani.
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.
Team GReEN members: Project Manager: Garret Smith Facilitator: Eric Austin Customer Liaison: Nikhil Andrews Artifacts Manager: Rebecca Collins Overview.
Requirements Specification for Lab3 COP4331 and EEL4884 OO Processes for Software Development © Dr. David A. Workman School of Computer Science University.
Systems Analysis and Design in a Changing World, Fourth Edition
Project X Group Y Presenters: (indicate roles). Part I: Project Overview System provides functionality X Motivation for project –Address problem with…
Hypertext transfer family of protocols (HTTP, HTTPS, SOAP) CSE 870 Miniproject on Frameworks Advanced Software Engineering Contact: Dr. B. Cheng, chengb.
Human Computer Interaction
Computer Science Topical Paper Presentation #NN Presenter Name Pattern Name P a t t e r n X Y Z – P a g e 1 Original Paper Title by Paper Author.
Architecture View Models A model is a complete, simplified description of a system from a particular perspective or viewpoint. There is no single view.
Computer/Human Interaction Spring 2013 Northeastern University1 Name of Interface Tagline if you have one (80 chars max, including spaces) Team member.
IMedLife Presenters: Armand (Web Manager) Ling (Facilitator) Rose (Project Manager) Wahhab (Domain Expert)
Overview of Project ADS Software Engineering CSE435 Michigan State University Fall 2013 Team members: Project Manager: Alec Dutch Facilitator: Duncan Young.
Dillon: CSE470: ANALYSIS1 Requirements l Specify functionality »model objects and resources »model behavior l Specify data interfaces »type, quantity,
VA Internal Use Only 1 Product Architecture Recommendation Briefing Template.
Overview of Project CACC1 Software Engineering CSE435 Michigan State University Fall 2013 Team members: Project Manager: Kathy Cummings Facilitator: Phil.
Advanced Software Engineering Dr. Cheng
Pepper modifying Sommerville's Book slides
Chapter 33 Estimation for Software Projects
What is a CONOPS anyway? Avoiding Brook’s “law”: “All major mistakes are made on the first day of the project”!
IS301 – Software Engineering V:
Chapter 5 System modeling
Use Cases and Scenarios
Creating an Effective Syllabus
Chapter 5 – System Modeling
Group Y Presenters: (indicate roles)
Architecture Concept Documents
presentation is a powerful tool
BTS430 Systems Analysis and Design using UML
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.
EKT 421 SOFTWARE ENGINEERING
CSE 5912 Student Presentations
Software Engineering: A Practitioner’s Approach, 6/e Chapter 23 Estimation for Software Projects copyright © 1996, 2001, 2005 R.S. Pressman & Associates,
BSA 411 Competitive Success/snaptutorial.com
BSA 411 Education for Service/snaptutorial.com
Team members: Project Manager: Facilitator: Customer Liason:
denote Project Managers explicitly
Disaster Recovery Model and Resource Tracking
Group Y Presenters: (indicate roles)
A description of the presentation
Kayra Hopkins Loretta Macklem
Overview of Project Active Parking Assist 1
Project Title (Team Name) UTSA CS X Spring 2018 Leader Name
Software Design Lecture : 15.
ATS Architecture Design Solution Intent
SAMANVITHA RAMAYANAM 18TH FEBRUARY 2010 CPE 691
Team # Member1, Member2 Assistant
Chapter 33 Estimation for Software Projects
Software Engineering: A Practitioner’s Approach, 6/e Chapter 23 Estimation for Software Projects copyright © 1996, 2001, 2005 R.S. Pressman & Associates,
Quality Improvement Initiative Title Presenter Name(s)
CSE 498, Collaborative Design
Guide to Catalyst Showcase Template
A description of the presentation
Chapter 26 Estimation for Software Projects.
Guide to Catalyst Showcase Template
Units 3 & 4 Business management transition
Presentation transcript:

Team Members: Member1, … Spring 2013 Title of Project Team Members: Member1, … Spring 2013 CSE870 Advanced Software Engineering Michigan State University Instructor: Dr. B. Cheng For further information: chengb at cse dot msu dot edu

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

Security Analysis Identify security factors affecting project … How did you mitigate security 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

Comparison of Two Designs Show us the two original 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 integration

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 AOP Projects: 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

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.

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.

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