Assignment of subsystems • Development teams Processes and processors Address non-functional requirements • Reliability Performance • Scalability

Midterm Flashcards by Mitch Lacy

What is Modeling and Why Model

A model is an abstraction of the system aimed at simplifying the reasoning about that system. Modeling is a way to reduce complexity and deal with a system that is too complex or expensive to reproduce live

How well did you know this?

Not at all

Perfectly

Define System

Organized set of communicating parts

How well did you know this?

Not at all

Perfectly

Define a use case diagram

Focus on the behavior of the system from an outside point of view
Results in the formation of Actors within the system
Use Cases Capture Responsibilities

How well did you know this?

Not at all

Perfectly

Describe a class Diagram

Describe the system in terms of objects/classes/attributes

How well did you know this?

Not at all

Perfectly

Describe a view in terms of modeling

subset of a model that allows you to view a complicated part more easily

How well did you know this?

Not at all

Perfectly

Sequence Diagram

Represent the interaction that take place between those objects

How well did you know this?

Not at all

Perfectly

Actors

External Entities that interact with the system use case is from an actors point of view

How well did you know this?

Not at all

Perfectly

Describe the iterative Process

Each iteration delivers a unit of functionality
Encourages early, frequent testing
Large projects may involve architecture and modeling • Each iteration involves a number of the practices

How well did you know this?

Not at all

Perfectly

Describe Risk Management

One of the primary activities of Software Engineering • Risk is often unavoidable but manageable
Validate concepts and approaches early
Risk areas
Performance
Security
Scalability • Testability • Usability

How well did you know this?

Not at all

Perfectly

Describe a Domain Model

Describes the concepts in the domain

* Captures relationships • No design concepts

How well did you know this?

Not at all

Perfectly

Describe the 4+1 view

Logical View
Developmental View
Physical View
Process View
Scenarios

How well did you know this?

Not at all

Perfectly

Software Development Activities (TAIROS)

Requirements Elicitation • Analysis
System Design
Object Design
Implementation • Testing

How well did you know this?

Not at all

Perfectly

SE Management Activities

Communication
Rationale management
Configuration management • Project management

How well did you know this?

Not at all

Perfectly

CS361

Non-Functional Requirements

Address qualities of the system
Impacts architectural decisions
Architectural decisions impact qualities

How well did you know this?

Not at all

Perfectly

Role of Architecture

Assignment of subsystems • Development teams
Processes and processors
Address non-functional requirements • Reliability
Performance • Scalability

How well did you know this?

Not at all

Perfectly

Layering Architecture

Create abstractions to represent services
Downward dependencies
Multiple clients

How well did you know this?

Not at all

Perfectly

Partitioning Architecture

Peers are created to reduce complexity

• May be dependent on similar lower layers

How well did you know this?

Not at all

Perfectly

Design Results in

Design Goals
Software Architecture
Boundary Use cases

How well did you know this?

Not at all

Perfectly

What is Software Engineering?

Design and development of software products
Production of programs that meet specifications • Demonstrably accurate
Management of the software process
Produced on time & within budget

How well did you know this?

Not at all

Perfectly

Black Box Testing

Study These Flashcards

Focus is on expected behavior of the object
No knowledge of internal behavior
Measure results

White Box Testing

Study These Flashcards

Focus on internal operation
Unit and Integration level testing
Regression tests

Scaffolding for testing

Study These Flashcards

Creates environment for testing

* Ex: JUnit • Reusable

Determine Inputs to Test

Study These Flashcards

Corners and boundaries
Examine requirements and models for limits • Consider domains (and ranges)
Inflexions
Conditional behavior
Equivalence classes
Pick input data that covers all classes • Probe for different modes of failure

Boundary Value Analysis

Study These Flashcards

Edge conditions for both domain and range
Analyze for min / max input and output values • Create combinations
Extreme input count
EX: number of records read
EX: scan buffer • EX: input events

Stress Testing

* Push system beyond limits • Data limits * Performance limits * Frequency

Acceptance Testing

* Test cases run by client * Requirements based * Involve all the Actors in system * Tie to use cases * Should be written with requirements

Regression Testing

Selective re-testing of components likely affected by change • Lower level tests for critical areas • Key mechanisms tested in regressions with smoke test

Black Box Testing

* Focus is on the expected behavior of the object * No knowledge of internal behavior * Scaffolding required * Mock actors * Determine appropriate cases • Test data (parameters) * Measure results

What 6 fields are included in a use case diagram

Name, Participants, Actors, Entity, Entry Conditions, Flow of Events, Exit Conditions, Quality Requirements

Class diagram | Explains a systems in terms of what?

Objects and Classes

What do Actors represent

Actors represent entities that interact with the system

What Questions can you ask to identify Actors

Which groups are supports by the system Which groups Execute the System functions Which group perform secondary functions With what external hardware will the system interact

What is a scenario

functionality available to the actors that will later be formalized into use cases

How do use cases and scenarios relate to each other

A use case specifies all possible scenarios

Describe a nonfunctional requirements

reliability performance supportability legal packaging

What does analysis focus on

using use cases and nonfunctional requirements to produce a model of the system called the analysis model.

What are the 3 parts of the analysis model

dynamic model analysis object model functional model

What diagrams make up the Dynamic Model

Sequence Diagrams

What makes up the analysis object Model

class object diagrams

What makes up the functional Model

use cases/scenarios

Iteration plan

How are we going to distribute features amoung iterations | allows us to order and prioritize our risk

Test plans

What features am I intending to test | what assets and resources do I need

Test cases

specific tests that I am going to cary out that validate that I am testing a certain behavior

Boundary value analysis

What are the maximum and mins inflection points ex. Withdrawal test big values test zero values, exactly the amount in the account Determing test data classes What happens when you want 25 dollars but it only has 20s

How to calculate the cyclomatic number

(Edges - Nodes) +2

Definition of a pattern

A pattern is a solution to a problem in a context I have a generic solution that can be applied in different envrionemts but the actual solution is dependent upon the context

Coverage testing

Monopoly Example Figuring out what values of the parameters are going to help us force failure here What is going to make this thing fail Mistakes -> faults -> failures -> errors

Object Diagram

identify specific obejcts and show how they interact with each other If I have 3 or 4 workers how are they related

Momento Pattern

notion of a momento allows us to caputre the state of an object so we can send it somewhere else Send a string form over the internet reconstitue it and put it back togehter as an object

Midterm Flashcards

(49 cards)