ISDS 406 CSUF-Hunt TEST 1

critical success factors

Project Portfolio Management(Selecting, Prioritizing, and Monitoring project results)

RAD(Rapid Application Development)

A collection of methodologies to make up for Waterfall weaknesses.

Uses special techniques and computer tools. {Scope Creep}

Iterative development

Breaks projects into versions that are developed sequentially.[Ids important req.]{users use incomplete system}

System Prototyping

Concurrent analysis, design, and implementation produces a "quick and dirty" version which is used to redesign, etc. until it's ready. {lack of careful, methodical analysis}

Throwaway prototyping

Uses throwaway prototypes to explore alternative designs rather than as an actual new system.

Extreme programing

Small focused teams work with clients to emphasize customer satisfaction.

selecting appropiate development methodology

1. Unclear user req.

2. Unfam. w/ tech.

3. Complexity

4. Relieability

5. Short time schedule

6. Schedule visibility

CH2

{con}[pro] (parenthesis)

waterfall development

Analysts and users proceed sequentially form one phase to the next. [Ids req. long before]{limits changes}{going backward is quite difficult.}

parallel development

General design is created for WHOLE sequence.(Evolved to address waterfall long development. )

system complexity

Req. careful and detailed analysis and design.

Staffing the project

# of people, skills::project, motivation, and minimize team conflict.

Interpersonal Skills

Communication and interpersonal abilities that are used when dealing with users, management, execs, and team members.

Trade-offs

SIZE-TIME-COST

Scope Creep

Additional req. added after project is set and frozen.

CH 3

...

Requirements

Statements of what a system must do or what characteristics it needs to have.

Business Requirements

What the business needs

Functional requirements

What the user needs

Non-functional Requirements

characteristics the system should have

System Requirements

how the system should be built

Requirements elicitation Techniques

Observation, jad, documentation analysis, interviews, and questionnaires.

Interviews

JAD (Joint Application Development)

Information gathering technique that allows the team, users, and management to work together to Id req. for the system.

Questionnaires

A method of collecting information from stakeholders by asking pre-defined questions, typically in a written format, to gather requirements for a system.

Observation

...A data collection method that involves watching users in their natural environment to understand their behaviors and tasks.

Outcome Analysis

Focuses on understanding the fundamental outcomes that provide value to customers.

CH4

...

Use Cases

Represents how a system interacts with its environment by illustrating the activities that are performed by the system's users and responses.

Triggers

An event to which the system must respond

Inputs & Outputs

Should be listed along with its source/destination.

Primary Actor

Primary person, software, or hardware that interacts with the system to achieve a useful goal.

User using the application(customer, manager, sales, exec)

Major Steps

Confirming Use Cases

Ask the user to execute the process, using the written steps in the use case: that is, have the user role-play the use case.

CH5

...

Process model

Graphical representation of how a business should operate.

DFD (Data Flow Diagram)

Graphical representation of data flow through processes and activities performed.

Logical Process Model

Describe processes without suggesting how they are conducted.

Data Flow

...

Decomposition

Breaking down of the DFD into a hierarchy, each level down representing less scope, but more detail.

Context Diagram

1st DFD in every business model; shows the entire system in context with its environment.

LEVEL 0 Diagram

Shows all the processes at the first level of numbering, the data stores, external entities and data flows among them.

LEVEL 1 Diagram

Next level of decomposition.

LEVEL 2 Diagram

Next level of decomposition.

Balancing

Ensuring all the info presented in a DFD at one level is accurately represented in the next-level DFD

Black Hole

A process without output.