what the system needs to deliver

a report that lists both the functional and non-functional requirements of a system

on-going - no defined scope for a project

Done in iterations

(PMO)

Place to get help as a project manager inside of a company

how it will turn input into output

the process that the system must perform

info. the system must have

performance constraints

behavioral properties

system architecture

considered to be more technical

changes to business processes or organizational structure to take advantage of technology

Improve to make faster, more efficient, or more effective

duration analysis - process time

activity-based costing - cost of each activity in system

benchmarking - formalized, industry practices that can be used as a measurement

radical change in structure/operations

associated with layoffs in the 1990's

structured - same questions asked to many people

unstructured - only asked to a few people; open-ended

researcher bias - questions asked can give inaccurate results

like a focus grp

used often in software engineering apps

asks the user what they want

more difficult than interviews

can present a bias based on how they are asked

80/20 rule - 80% of the data collected will come from 20 questions

easy to data mine and do stats with

research bias

think of heisenberg's uncertainty principle

power of assumption - customer sees front of store, but not back where decisions are made

representation of how a system works

documents current and future processes of a system

description of events

workflow modeling - data flow and swimlane diagrams

description of technology involved

how the technology is involved

logical flow of data through/in a system, or across systems

Begins and ends with process description b/c it is king

begins with high-level summary - called context diagram, or lvl 0; only deals with 1 process

can only include things from your process description

processes - circle

external entity - square

data flows - arrow

storage - 3 sided box

aka level 0 or figure 0 diagram

looks at only 1 process

includes all major sub-processes in the examined process, but level of detail is random

Every level of a DFD must be balanced

structured english - close to programming, so try to avoid

decision trees - graphical representation

decision tables - shows muliple decision rules

business process modeling notation

standard set a symbols used as short-hand notation for documenting business processes in a workflow

similar to bpmn

another set of charts and symbols

used mostly for software engineering

logical model, object collaboration model, dynamic model, physical component model, physical deployment model, use-case model

UML is object-oriented

not the same as database logical model

shows how the classes and objects interact with one another

shows the logical connection

shows what physical components make up the system

sometimes software is included

dfd shows logical flow of data

swimlane shows chronology

swimlane also shows the activities, and the people involved

3 r's - role, responsibility, routes

actors - who is involved

steps - what the actors do

flow isn't shown

branching can be needed if complex - shows the probability of each outcome

a case study of how a system is used, or who uses it

how the system is used by another system or human

what the system does in response to user input

makes sure that there are no mistakes by the user's input

normal = expected

something unexpected happens - called an exception; not broken

length depends on person writing it

should be concise, clear, thorough, and focused

"howevers" are exceptions, and are dealt with later

who is involved?

written after the unique identifier

not like a dfd - use-case is like a narrative, but can have arrows, etc.

trigger - event that starts the process; can be external or temporal (time)

sources and destinations of major inputs and outputs are listed

details are listed about the flow of events and the inputs/outputs involved

represents exception cases

"factored out" of the main event flow

an interaction that is too complex to be described in the use-case

usually will always happen, but is too complex to be grped with other things, hence why it is excluded

decide and document how to build the system

customer and designer agree on what is going to be done

make, buy, or outsource, or all combined in some way

convert logical and data models into physical models

design the architecture for the system

make hardware and software selections

design inputs, outputs, and data storage

create the system specification

technical details required to build the system - come from given requirements

functional - tasks, capabilities, etc.

nonfunctional - performance, security, cultural, political, legal, etc.

decide what your data management strategy is going to be

ECM - enterprise content management - usually most common out of all the methodolgy choices

make it: most expensive

buy it: already made, can be added onto

pay per use access to software, usually on an internet connection

called "rent a software"

allows for flexibility in how many licenses are used at certain times of the year

sells objects that you can put together in your own way to make an app.

is said to be a design option

try to keep each service separate from one another when making an app.

another option for designing, like SOA

used to build web interfaces such as java and XML

ex- google maps doesn't need to be reloaded when the mouse is dragged

fixed-price

value-added - ex. SAP making AFS for Nike

Full-time equivalent

transaction-based

companies want to outsource, but bad in the long-run

b/c of US layoffs and losing the ability to innovate

IT infrastructure library - ITTL

ITTL - best practices for delivering IT services; reduces IT costs and improves service and productivity

service oriented architecture is good for software design

outsourcing is expected to grow in 2011

using it b/c it is cheap

cloud computing is cheaper than outsourcing

automation will be big b/c ppl want clear-cut products

companies will do more offshoring and US layoffs

discusses ASP's

you "rent" the software

pros: can use it when you need it

cons: data is external, and bad for long-term use b/c of monthly payments

More companies are going with open-source

Linux>Windows NT