soft1

softMicro

Unified Process Phases

Inception, Elaboration, Construction, Transition

Unified Process: Inception

Identify the scope, decide how to build, agree on budget (feasibility) (1-2 Weeks)

Unified Process: Elaboration

Prove we have the right architecture (4-6 Weeks)

Unified Process: Construction

Build the software using incremental process, prioritize requirements (Arbitrary Length)

Unified Process: Transition

Validate the system and move to production

scrum

A way to implement agile programming. Break into small parts, everything is sprints.

Software Engineering

The application of a systematic, disciplined, quantifiable approach to the development, operation, and maintenance of software

Type of Software Development Processes

Scrum, Burndown, and Waterfall

Concept

Who knows

Analysis

Emphasis on finding and describing objects or concepts in the problem domain

Design

Emphasis on defining software objects and how they collaborate to fulfill requirements

UML

Unified Modelling Language /specifying, visualizing, constructing, and documenting the artifacts of software systems (can be used for non software things)

Unified Process

A systems development life cycle based on object-oriented techniques; follows a series of repeated steps

Time-boxed iterations

A time-limited period where the team focus on a single goal and produce an increment of the software

What are the two categories of requirements?

Functional and non-functional

Use Case

Text story capturing the interaction between actors and the system. It captures one or more requirements, which we analyze.

JDK

Java Development Environment - Including JRE, and the compilers and tools

First Method Called when Running Class

Main()

ByteCode

program code that has been compiled from source code into low-level code designed for a software interpreter. It may be executed by a virtual machine (such as a JVM) or further compiled into machine code (JIT)

Iteration in Gantt Diagrams

Long Lines that enclose individual tasks

Sprint

A set period of time, normally two to four weeks, during which specific work must be completed and made ready for review when using Scrum methods

increment

development in small time (added functionality)

Virtual method

Any non-private, non-final, and non-static method

What are the two interaction diagrams?

Sequence diagram

Communication diagram

In Sequence, what is captured in the box on the top?

An instance of a class typically has a colon or is underlined to denote that it is an instance.

synchronous messages

used when the sender waits for the receiver to process the message and return before carrying on with another message(WITH A SOLID ARROW)

asynchronous message

An asynchronous message is used when the message caller does not wait for the receiver to process the message and return before sending other messages to other objects within the system. (WITH A NOTATION LIKE <

Interaction diagrams

describes how a group of objects collaborate in some behavior (typically a single use case) and shows object interactions regarding messages passed between these objects within use case.

What is the meaning of the triangle arrow?

Synchronous/blocking call

How do we derive a System Sequence Diagram?

Take use case and divide user system interaction based on actions/reactions.

System Operations

Product of a System Sequence Diagram

Operation Contracts Subsections

Name, cross-reference, pre, and postconditions

Can you draw a hierarchy of collections?

Yes

Types of sets

HashSet, TreeSet, EnumSet, LinkedHashSet

Which package contains collections?

java.util.Collections

Java Collections Framework

interfaces, implementations, aggregate operations & algorithms

Collection

An object that groups multiple elements into a single unit.

What is the difference between Use Case and Use Case Diagram?

One produces a text story for requirements, and the other gives a graphical outline of system features.

Map

Maps key and value pairs, cannot contain duplicate keys

Brief Use Case

one-paragraph summary, usually of the main success scenario (early steps of development)

What is the difference between Concept and Class?

A concept is an object of the real world; a class can be a software construct.

What strategies are there to extract domain concepts?

Noun analysis, Category lists

Casual Use Case

informal paragraph format - multiple paragraphs covering various scenarios

Fully Dressed Use Case

Elaborated. All steps and variations are described in detail

* preconditions, successes, guarantees
* done in later stages of dev

Different actor types:

Person, computer system, or organizaion

Associations

Relating two classes

Association role

specific role that it plays in that relationship, what the near one poses to the next one

Association class

■ is used to model an association as a UML class.

■ it has its own name, attributes operations

Association

Relating two classes together

Set

Cannot contain duplicate elements

Domain Concepts

concepts (objects)

associations between concepts

attributes of concepts

rarely polymorphism

extends (use case diagram relation)

inherits behaviors from the other class extended from.

List

An ordered collection, can contain duplicate elements

Use Case diagram

Used to describe a set of actions (use cases) that a system can perform in collaboration with one or more external actors.

Why do I need equals and hashCode?

For object identity, we do not want to compare reference in memory location but the data the object holds.

Actors

Represents a role in the system, makes actions, or receives them. Not necessarily human.

why base soft dev on use-cases?

* discover and record requirements.
* define interactions between actor using a system to define goal

Multiplicities

defines how many instances of a type A can be associated with one instance of a type B

Two types of associations:

* Association
* Relating two classes
* Generalization
* Specialization of a class

Dependencies

Has to exist for the associated class to perform its task

domain model vs design class model

A class diagram differs from a Domain Model by showing software entities rather than real-world concepts.

Essential Use Case vs Concrete Use Case

E - what a software application or system must do to fulfill the goal

C- initiated by an actor

interaction diagram

models that describe how a group of objects collaborate in some behavior, show instances/objects + interaction

System Sequence Diagrams (SSDs) vs Sequence Diagrams (SDs) vs. Architectural Sequence Diagrams

SSD - shows the interaction between actors and the black-box system.

SD - shows the interaction between two objects.

ASD - Depict workflow, Message passing and how elements in general cooperate over time to achieve a result

Design Classes

Having an attribute of the supply type

Sending a message to a supplier

Receiving a parameter of the supplier type

The supplier is a superclass or interface

Unified Process Phases

Inception, Elaboration, Construction, Transition

Unified Process: Inception

Identify the scope, decide how to build, agree on budget (feasibility) (1-2 Weeks)

Unified Process: Elaboration

Prove we have the right architecture (4-6 Weeks)

Unified Process: Construction

Build the software using incremental process, prioritize requirements (Arbitrary Length)

Unified Process: Transition

Validate the system and move to production

scrum

A way to implement agile programming. Break into small parts, everything is sprints.

Software Engineering

The application of a systematic, disciplined, quantifiable approach to the development, operation, and maintenance of software

Type of Software Development Processes

Scrum, Burndown, and Waterfall

Concept

Who knows

Analysis

Emphasis on finding and describing objects or concepts in the problem domain

Design

Emphasis on defining software objects and how they collaborate to fulfill requirements

UML

Unified Modelling Language /specifying, visualizing, constructing, and documenting the artifacts of software systems (can be used for non software things)

Unified Process

A systems development life cycle based on object-oriented techniques; follows a series of repeated steps

Time-boxed iterations

A time-limited period where the team focus on a single goal and produce an increment of the software

What are the two categories of requirements?

Functional and non-functional

Use Case

Text story capturing the interaction between actors and the system. It captures one or more requirements, which we analyze.

JDK

Java Development Environment - Including JRE, and the compilers and tools

First Method Called when Running Class

Main()

ByteCode

program code that has been compiled from source code into low-level code designed for a software interpreter. It may be executed by a virtual machine (such as a JVM) or further compiled into machine code (JIT)

Iteration in Gantt Diagrams

Long Lines that enclose individual tasks

Sprint

A set period of time, normally two to four weeks, during which specific work must be completed and made ready for review when using Scrum methods

increment

development in small time (added functionality)

Virtual method

Any non-private, non-final, and non-static method

What are the two interaction diagrams?

Sequence diagram

Communication diagram

In Sequence, what is captured in the box on the top?

An instance of a class typically has a colon or is underlined to denote that it is an instance.

synchronous messages

used when the sender waits for the receiver to process the message and return before carrying on with another message (WITH A SOLID ARROW)

asynchronous message

An asynchronous message is used when the message caller does not wait for the receiver to process the message and return before sending other messages to other objects within the system. (WITH A NOTATION LIKE <

Interaction diagrams

describes how a group of objects collaborate in some behavior (typically a single use case) and shows object interactions regarding messages passed between these objects within use case.

What is the meaning of the triangle arrow?

Synchronous/blocking call

How do we derive a System Sequence Diagram?

Take use case and divide user system interaction based on actions/reactions.

System Operations

Product of a System Sequence Diagram

Operation Contracts Subsections

Name, cross-reference, pre, and postconditions

Can you draw a hierarchy of collections?

Yes

Types of sets

HashSet, TreeSet, EnumSet, LinkedHashSet

Which package contains collections?

java.util.Collections