CPSC 372 John D. McGregor Module 3 Session 5 Assignment and References.

Slides:



Advertisements
Similar presentations
CPSC 203. Use Case Diagram  A description of a system’s behavior as it responds to a request that originates from outside of that system. Specifies the.
Advertisements

ARCH-05 Application Prophecy UML 101 Peter Varhol Principal Product Manager.
UML Static diagrams. Static View: UML Component Diagram Component diagrams show the organization and dependencies among software components. Component:
Software Testing and Quality Assurance
Chapter 7 Requirement Modeling : Flow, Behaviour, Patterns And WebApps.
CPSC 871 John D. McGregor MSumS2 Summary – technical issues in software engineering.
CPSC 871 John D. McGregor Module 4 Session 3 Architecture Evaluation.
PRESENTATION 2 Sri Raguraman CIS 895 Kansas State University.
CPSC 871 John D. McGregor Module 1 Session 2 Requirements Elicitation/analysis.
Chapter 4 User Experience Model. User experience model (Ux) Visual specification of the user interface Visual specification of the user interface Both.
CPSC 872 John D. McGregor Session 16 Design operators.
CS361 Winter 2013 Final Exam Review Software Engineering I Oregon State University.
SYSE 802 John D. McGregor Module 3, Session 3 Assignment.
Pemrograman Web MVC Programming and Design Pattern in PHP 5.
CpSc 875 John D. McGregor AADL. Point of sale system.
ICONIX P ROCESS FOR S OFTWARE D EVELOPMENT Hoang Huu Hanh, Hue University hanh-at-hueuni.edu.vn 1.
CpSc 875 John D. McGregor Class 21 Ocarina/Navigation.
Behavioral Modeling Chapter 8.
Unit 1 INTRODUCTION TO MODELING AND CLASS MODEL Ref : L7-UML.PDF.
CPSC 871 John D. McGregor Module 2 Session 4 CMMI & assignment.
CLASS DIAGRAM. What is a class diagram? Imagine you were given a task of drawing a family tree. The steps you would take would be: What is a class diagram?
Documenting Software Architectures 1.Uses and Audiences for Architecture Documentation Architecture documentation serves as a means of education Architecture.
CS 4850: Senior Project Fall 2014 Object-Oriented Design.
CPSC 871 John D. McGregor Module 7 Session 1 More UML.
CPSC 372 John D. McGregor Module 3 Session 1 Architecture.
CPSC 203. Use Case Diagram  A description of a system’s behavior as it responds to a request that originates from outside of that system. Specifies the.
Modelling Class T07 Conceptual Modelling – Behaviour References: –Conceptual Modeling of Information Systems (Chapters 11, 12, 13 and 14)
John D. McGregor Class 4 – Initial decomposition
CPSC 871 John D. McGregor Module 3 Session 1 Architecture.
CPSC 372 John D. McGregor Module 2 Session 5 Android App.
CpSc 875 John D. McGregor C11 - Documentation. 2 sources Clements et al. – book that describes an approach called Views and Beyond IEEE 1471 adopted standard.
Copyright ©2004 Cezary Z Janikow 1 OOAD Overview n OO language – Necessary for OO systems? – Sufficient for OO systems? Owning a hummer doesn’t make you.
PRESENTATION 2 Sri Raguraman CIS 895 Kansas State University.
Lab 5 CPIT 250 System Analysis and Design.
SYSE 802 John D. McGregor Module 1 Session 2 Requirements Modeling in SysML.
CSE 219 Computer Science III UML. UML Diagrams UML - Unified Modeling Language UML diagrams are used to design object-oriented software systems –represent.
CPSC 875 John D. McGregor Design Concept. Functional decomposition.
CPSC 873 John D. McGregor Session 15 Test suites and tools.
CPSC 372 John D. McGregor More EPF Module 2 Session 4.
John D. McGregor Architecture Evaluation
CPSC 871 John D. McGregor Module 8 Session 3 Assignment.
PowerPoint Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 5th Edition Copyright © 2015 John Wiley & Sons, Inc. All rights.
Objective: Learn to describe the relationships and extend the terms in arithmetic sequence.
Model-View-Controller A Design Pattern SE-2030 Dr. Rob Hasker 1 Based on slides written by Dr. Mark L. Hornick Used with permission.
CPSC 873 John D. McGregor S20 More measurement. Utility is a term used by economists to describe the measurement of "useful-ness" that a consumer obtains.
Introduction to UML and Rational Rose UML - Unified Modeling Language Rational Rose 98 - a GUI tool to systematically develop software through the following.
CPSC 872 John D. McGregor Session 18 Evaluating Specification.
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.
Class Diagrams, MVC and Design Patterns CS153P Session 4.
1 Chapter 13: Class Diagram Chapter 19 in Applying UML and Patterns Book.
CS 350 – Software Design UML – The Unified Modeling Language – Chapter 2 The Unified Modeling Language is a visual language used to create models of programs.
John D. McGregor Eclipse Process Framework Module 2 Session 4
John D. McGregor Session 5 Domain Analysis, cont’d
Use case Diagram.
Smart Tendering System
Software Architecture & Design Pattern
WEB 407 Competitive Success/snaptutorial.com
WEB 407 Education for Service-- snaptutorial.com.
Order Database – ER Diagram
Agenda – week 6 6:00 – 6:10 Questions, announcements, intro
Software Design Lecture : 15.
John D. McGregor Module 0 Session 2 Infrastructure and problem
Arithmetic Sequence Objective:
Csc354 fall 2016 assignment 3 design spec
John D. McGregor Module 6 Session 1 More Design
John D. McGregor Module 1 Session 3 Assignment
John D. McGregor M11S4 Value of designs and assignment
Sample Test Questions Please identify the use cases of the system that cover all the behaviors described in the system specification. Please identify.
Agenda – week 5 6:00 – 6:05 Questions, announcements 6:05 – 6:20
John D. McGregor Session 11 Adv Design Patterns
Presentation transcript:

CPSC 372 John D. McGregor Module 3 Session 5 Assignment and References

Assignment Address the problems found in the evaluation of your use case model. List the quality attributes that are important to your app. List them in priority order and justify that order. Apply the Model/View/Controller pattern to your app: mvc/ Describe the contents of each element of the pattern in terms of the entities and actions needed for your app. Use UML class and sequence diagrams to describe the elements and their relationships. Use sequence diagrams to show example interactions among the objects in the executing system based on the class members. Then look at some of the very detailed Android design patterns such as: Begin a mockup of your app’s intro screen and the controls to be used. Submit a drawing created using Paint or some other drawing program. Save it in.png format.

Blogs with Android architecture examples oid-architecture-part-1-intro/ oid-architecture-part-1-intro/ architecture-message-based-mvc/ architecture-message-based-mvc/ id-application-architecture/ id-application-architecture/ -application-architecture-part-i-background/ -application-architecture-part-i-background/