Unit 2 Flashcards

1
Q

There are two general approaches to the SDLC

A

Predictive Approach to the SDLC

Adaptive Approach to the SDLC

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Predictive Approach to the SDLC

A

Waterfall model
Assumes the project can be planned in advance and that the information system can be developed according to the plan
Requirements are well understood and/or low technical risk

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Adaptive Approach to the SDLC

A

Iterative model
Assumes the project must be more flexible and adapt to changing needs as the project progresses
Requirements and needs are uncertain and/or high technical risk

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Traditional Predictive SDLC

A

Earlier approach based on engineering

Typically have sequential Phases
Phases are related groups of development activities, such as planning, analysis, design, implementation, and deployment

Waterfall model
SDLC that assumes phases can be completed sequentially with no overlap or iterationOnce one phase is completed, you fall over the waterfall to the next phase, no going backDeliverable Driven

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Phase I: Project Initiation

A

During project initiation, the system’s business value to the organization is identified (How will it lower costs or increase revenues?).

This phase is the fundamental process of understanding why an information system should be built

Feasibility Analysis is performed at this stage
Technical Feasibility
Economic Feasibility
Organizational Feasibility

Key Deliverable: Problem Statement or Systems Proposal

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Phase II: Project Planning

A

The Planning phase will also determine how the project team will go about building the information system.

The Planning phase is composed of the following steps.
Developing a Timeline
Developing a Budget
Developing Success Criteria
Developing Process Standards

Key Deliverable: Project Plan

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Phase III: Analysis

A

The analysis phase answers the questions of who will use the system, what the system will do, and where and when it will be used.

During this phase the project team investigates any current system(s), identifies improvement opportunities, and develops a concept for the new system

Key Deliverable: Functional Specification Document

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Phase IV: Design

A

In this phases it is decided how the system will operate, in terms of the hardware, software, and network infrastructure; the user interface, forms, and reports that will be used; and the specific programs, databases, and files that will be needed.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Phase IV: Design Cont (Steps and Deliverable?)

A

Design steps

  1. Design Strategy: This clarifies whether the system will be developed by the company or outside the company.
  2. Architecture Design: This describes the hardware, software, and network infrastructure that will be used.
  3. Database and File Specifications: These documents define what and where the data will be stored.
  4. Program Design: Defines what programs need to be written and what they will do.

Key Deliverable: Technical Design or Specification Document

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Phase V: Implementation

A

During this phase, the system is either developed or purchased (in the case of packaged software).

This phase is usually the longest and most expensive part of the process.

The phase has the following steps.
System Construction: The system is built and tested to make sure it performs as designed
Key Deliverable: The Concrete System

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Phase V: Deployment

A

During this phase, the system is deployed .
The performance is evaluated and fine tuned
Key Deliverable: Stable System

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Adaptive Approaches

A

Incremental development

Completes portions of the system in small increments and integrated as the project progresses
Sometimes considered “growing” a system
Walking Skeleton
The complete system structure is built first, but with bare-bones functionality
Examples include Prototyping, Rapid Application Development, Agile Development etc.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Agile Development

A

A guiding philosophy and set of guidelines for developing information systems in an unknown, rapidly changing environment
Chaordic
A term for adaptive projects –chaotic yet ordered

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Agile Development (Continued)

A

Agile Values in “Manifesto for Agile Software Development”
Value responding to change over following a plan
Value individuals and interactions over processes and tools
Value working software over comprehensive documentation
Value customer collaboration over contract negotiation

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

SCRUM

A

Combination of principles of Rugby and Agile
Intense effort involving the entire team for a defined period of time
Product backlog
Prioritized list of user requirements
Product owner
The client stakeholder who controls backlogScrum master
Scrum project manager

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Scrum Sprint

A

Scrum sprint

A time-controlled mini-project to implement part of the system

17
Q

Scrum Practices

A

Scope of each sprint is frozen (but can be reduced if necessary)
Time period is kept constant
Daily Scrum meeting
What have you done since the last daily Scrum (during the last 24 hours)?
What will you do by the next daily Scrum?
What kept you or is keeping you from completing your work?

18
Q

Methodologies

A

Methodologies
Provides guidelines for every facet of system development: What to do when, why and how
Specifies an SDLC with activities and tasks
Specifies project planning and project management models and reporting
Specifies analysis and design models to create
Specifies implementation and testing techniques
Specifies deployment and support techniques

19
Q

Methodologies

A

A Methodology includes a collection of techniques that are used to complete activities and tasks, including modeling, for every aspect of the project

20
Q

Models

A

Model
An abstraction of an important aspect of the real world.
Makes it possible to understand a complex concept by focusing only on a relevant part
Each model shows a different aspect of the concept
Crucial for communicating project information
In IS, some models are of system components that will be developed
Other models are used to manage the development process

21
Q

Some models of system components

A
Use Case diagram
Domain model class diagram
Design class diagram
Sequence diagram
Package diagram
Screen design template
Dialog design storyboard
Entity-relationship diagram 
Database schema
22
Q

Some models used to manage the development process

A
Gantt Chart
Organization hierarchy chart
Financial analysis models- NPV, payback period
System development life-cycle model
Stakeholders list 
Iteration plan
23
Q

Tools

A

Tools
Software applications that assists developers in creating models or other components required for a project
Integrated Development Environment (IDE)
set of tools that work together to provide a comprehensive development environment
Visual ModelingTools
Tools to create graphical models

24
Q

Some typical tools

A
Project management application
Drawing/graphics application
Word processor/text editor
Visual modeling tool
IDE
Database management application 
Reverse-engineering tool
Code generator tool
25
Q

Techniques

A

Technique

A collection of guidelines that help an analyst complete an activity or task

26
Q

Learning techniques is the key to having expertise in a field

A
Strategic planning techniques
Project management techniques
User-interviewing techniques
Dat-modeling techniques
Relational database design techniques
Structured programming techniques
Software-testing techniques
Process modeling techniques
Domain modeling techniques
User case modeling techniques
Object-oriented programming techniques
Architectural design techniques
User-interface design techniques