BADM 353 Midterm 2

अब Quizwiz के साथ अपने होमवर्क और परीक्षाओं को एस करें!

Business Need & Custom, Packaged, Outsourcing

Unique, Common, Not Core

State Machine: State

Value of attributes and relationships with other objects

Object wrappers

Wrap legacy system with API so that it talks to newer systems

The Use Case View is BLANK in the 4+1 view because

mandatory all elements of the architecture come from the requirements

Attributes

Characteristics of a class

State Machine: Guard

Condition that allows or blocks a transition

Information Architecture

Creates a structure for a website

Design Strategies

Custom, Packaged Software, Outsource

The physical view is also called the

Deployment view

Views of the system

Describe the system from the viewpoint of different stakeholders

Deployment View

Describes how system parts are organized into components and modules

Visual Metaphor

Design elements that highlight a theme Ex: images, color, font, icons

Use Case View

System functionality, external environment, principal users

Participants are arranged BLANK such that BLANK

horizontally there is no overlap

The development view is also called the

implementation view

A black hole is one that has transitions BLANK but none BLANK

into it, out of it

Sequence Diagram Steps

1 Identify context (use case) 2 Identify participants (use case actors and class diagram objects) 3 Set lifeline 4 Add messages 5 Add execution occurrence

What is a state?

A condition of being at a certain time

Logical View

Abstract descriptions of your systems parts and interactions

What UML diagram makes up the process view

Activity Diagram

Responsive Web Design

Allows desktop sites to change size depending on viewing device

State Machine: Event

Cause of change in state

State Machine: Transition

Change from a source state to a target state

Process View

Dynamic and explains how the system processes communicate

Behavioral Modeling

Dynamic and internal system behavior, state machines and sequence diagrams

Behavioral Model

Dynamically describes the internal behavior of the system

State Machine: Trigger

Event that begins a state change in an object

Functional Modeling

External and dynamic, use case diagrams

3 types of outsourcing contracts

Flexible, Fixed price, value-added

Analysis & Design

Functional and non-functional requirements

Web Design Trends

Hamburger menu, long scroll, card layout, hero image

What is the goal of IA?

Help users find info and complete tasks

Hamburger menu

Hide site navigation on small screens, only shows on click

Design Focus

How to build the system, physical architecture (hardware, software, networks)

Design Tips

Images with people, redundancy, visual metaphor

Messages

Info sent to objects to tell them to execute a behavior

Objects

Instance of a class

Icon

Link abstract info to concrete concept, labeling is important

4+1 Software Architecture View

Logical, Process, Physical, Development, Use Case

Interaction Diagrams

Model runtime interactions between system parts and logical view

What does IA focus on?

Organizing, structuring, labeling

What does the deployment view contain

Package and component

How do you show object destruction?

Place an X at the end of an object's lifeline

Pros & Cons of Outsourcing

Pros: few in-house resources, cheap Cons: understand problem, vendor experience, culture

Pros & Cons of Custom Development

Pros: specialization, flexibility, build skills Cons: burden on skills, risky

Pros & Cons of Packaged Software

Pros: vendor expertise, fast, reusable components Cons: cusomization, integration

State Machine

Represents the different states a single object passes through over time

Sequence Diagrams

Show how objects collaborate to provide functionality of the use case

Elements of State Machine

State Event Transition

Structural Modeling

Static, Class diagrams

Development View

System from a programmer view that relates to software management - manage layers

Physical View

System from system engineer's view by mapping software and hardware - brings design to life

Operations

The behaviors of a class

What do Sequence Diagrams Describe?

The order in which interactions happen, time is important

When a message is passed to a participant what happens?

The receiving participant becomes active and does something

State is BLANK when entered through a transition and becomes BLANK when exited through a transition

active inactive

With Use Cases and Class Diagrams alone you BLANK model how your system is going to do its job

cant, need interaction or sequence diagram

Return Message is an BLANK piece of notation

optional, only when a condition is met Ex: [aPatient Exists] LookupBills().

Time on a sequence diagram is all about BLANK not BLANK

ordering, duration

A miracle state is one that has transitions BLANK but none BLANK

out of it, into it

If you prefer to see the order of the interactions as clearly as possible then BLANK is the best choice.

sequence diagram

What does the activation bar indicate?

the sending participant is busy while it sends the message and the receiving participant is busy after the message has been received

Card Sorting

user centric design method for navigation

How are operation call messages shown?

using solid lines connecting two objects with an arrow


संबंधित स्टडी सेट्स

CPU Chapter 18: Musculoskeletal System

View Set

Area and Perimeter 4th Math BDES

View Set

Chapitre 1 : Les principes fondamentaux de la fiscalité française

View Set

Financial Management Topic 5 (Time Value of Money)

View Set