Chapter 1 and 3 Systems Development, IS350 Test 2 Over 7-12, 15-17 inclusive., IT ch.16

In a best practice scenario who should own major risk?

A Committee

The Unified Process

A methodology that maps out when and how to use the various UML techniques for OOSA

Activity elimination

Eliminate each activity in a business process in a "force-fit" exercise

What do IT risk incidents do?

Enable profitability

Which of the following activities is NOT part of the corporate context within which IT plans and budgets are created:

Establishing IT governance

Hazards such as disasters, pandemics, geopolitical upheavals, or environmental are examples of:

External Risks

true or false?: The Unified Modeling Language is a collection of terms and diagrams designed to be used in data-oriented software projects.

False- object-oriented software projects

true or false?: Kim repeatedly performs the analysis, design, and implementation phases concurrently in a cycle until the system is completed. She then goes back and from scratch does a thorough design and implementation to complete the project. She is following a prototype methodology.

False- throwaway prototyping

Effective IT budgeting is important because it assists with (choose two):

Fiscal Discipline & Strategy Implementation

Types of Requirements

Functional and Non-functional

Focusing on what is important, expecting changes over time, and viewing risk from multiple levels and perspectives are a part of:

Holistic Risk Management

Unified Process phases

Inception • Feasibility analyses performed • Workflows vary but focus is on business modeling & requirements gathering Elaboration • Heavy focus on analysis & design • Other workflows may be included Construction: Focus on programming (implementation) Transition--Focus on testing & deployment

The source of criminal interference can be:

Internal or external

_________ are multilevel and complex and frequently occur in parallel with each other

It Processes

The information gathering technique that is most effective in combining information from a variety of perspectives, building consensus, and resolving discrepancies is a(n) _____.

Joint application development

Which of the following is not a source of internal risk?

Legal

IT managers plan their spending using two different categories:

Operation costs & Strategic Investments

_______ costs consist of what is costs to "keep the lights on"in IT.

Operations

Systems Development Life Cycle (SDLC) phases

PADI- planning, analysis, design, and implementation.

General Principles of guiding risk decisions are categorized in a Risk Management Framework as

Policies and Standards

What is the purpose of Requirements Determination?

To convert high level business requirements (from the system request) into detailed requirements that can be used as inputs for creating models

IT Plans and budgets need attention more frequently than once a year T/F:

True

Today, IT risk management is a low-key activity focused on delivering projects and keeping applications up and running.

True

Methodology

a formalized approach to implementing the SDLC

Deliverables

specific documents and files that provide understanding about the project

three classes of SD methodologies

structured design, rapid application development, and agile development.

Polymorphism

the same message can have different meanings

What is a Functional requirement?

relates to a process or data (what a systems needs to do/store)

What is a non-functional requirement?

relates to performance or usability

SAD

transforms the existing (as is) system proposed (to be) system

Dynamic binding:

type of object is not determined until run-time

disadvantage of phased development

users begin to work with systems that intentionally incomplete

System analyst

who analyzes the business situation, identi es opportunities for improvements, and designs an information system to implement them.

Problems in requirements determination

• Analyst may not have access to the correct users • Requirements specifications may be inadequate • Some requirements may not be known in the beginning • Verifying and validating requirements can be difficult

Informal benchmarking

• Analyzes similar processes in other successful organizations

Problem analysis

• Ask users to identify problems with the current system • Ask users how they would solve these problems • Good for improving efficiency or ease-of-use

Benefits of OOSAD

• Break a complex system into smaller, more manageable modules • Work on modules individually

Duration analysis

• Determine the time required to complete each step in a business process • Compare this to the total time required for the entire process • Large differences suggest problems that might be solved by: • Integrating some steps together • Performing some steps simultaneously (in parallel)

Root cause analysis

• Focus is on the cause of a problem, not its solution • Create a prioritized list of problems • Try to determine their causes • Once the causes are known, solutions can be developed

Architecture centric

• Functional (external) view: focuses on the user's perspective • Static (structural) view: focuses on attributes, methods, classes & relationships • Dynamic (behavioral) view: focuses on messages between classes and resulting behaviors

Inheritance

• General classes are created (superclasses) • Subclasses can inherit data and methods from a superclass

Design phase Questions to be Answered

• How should we build it?

Techniques for identifying requirements

• Interviews • Joint application development (JAD) • Questionnaires • Observation • Document analysis

Joint Application Development (JAD)

• Joint user-analyst meeting hosted by a facilitator • Meetings can be held electronically( e-JAD) and anonymously

two dimensional process

• Phases are time periods in development • Workflows are the tasks that occur in each phase • Activities in both phases & workflows will overlap

Document Analysis

• Provides information about the "as-is" system • Review technical documents when available • Look for unused form elements

Activity-based costing

• Same as duration analysis but applied to costs

Requirements determination

• The single most critical step of the entire SDLC • Changes can be made easily in this stage

Iterative & incremental

• Undergoes continuous testing & refinement • The analyst understands the system better over time

Outcome analysis

• What does the customer want in the end?

Analysis Phase Questions to be Answered

• Who will use it? • What should the system do for us? • Where & when will it be used?

Planning Phase Questions to be Answered

• Why should we build this system? • What value does it provide? • How long will it take to build?

Which Phase of SDLC is requirements determination?

The Analysis phase

Disadvantages of prototyping

-Fast-pasced system releases make it hard make it hard to conduct careful, methodical analysis -undergoes such significant changes that many initial design decisions become poor ones

Waterfall development

-Key deliverables are typically very long (hundreds of pages) -presented to project sponsor for approval as project moves from phase to phase -extremely difficult to move backward in SDLC

Advantages of Prototyping

-VERY quickly provides a system with which the users can interact -reassures users that project team is working on system (always see progress) -quickly refines real requirements

Parallel development

-attempts to address the problem of long delays between the analysis phase and the delivery of the system -performs a general design for the whole system and then divides the project into a series of distinct subprojects that can be designed and implemented in parallel

Object(instance)

-instantiation of a class -Attributes: information that describes the class -State: describes its values and relationships at a point in time

Use-case driven

-means that use cases are the primary modeling tools de ning the behavior of the system. -Each use-case focuses on one business process

Advantages of phased development

-quickly getting a useful system into the hands of users -able to identify important additional requirements sooner than with structured design situations

disadvantage of parallel development

-subprojects are not completely independent;design decisions made in one subproject can affect another -the end of the project can require significant integration efforts

Throwaway prototyping

-thorough analysis phase -relies on design prototypes during design & analysis - after issues resolved; design prototypes are thrown away

Characteristics of Object- Oriented Systems

1. Classes & objects 2. Methods and messages 3. Encapsulation & information hiding 4. Inheritance 5. Polymorphism & dynamic binding

Disadvantages of waterfall development

1. Design must be completely specified before programming begins 2. long time elapses between the completion of the system proposal in the analysis phase and the delivery of the system

Steps in creating a requirements definition

1. Determine the types of functional and non-functional requirements applicable to the project 2. Use requirements-gathering techniques 3. Analysts work with users to verify, change and prioritize each requirement 4. Continue this process through analysis workflow

Design phase

1. Develop a design strategy 2. Design architecture and interfaces 3. Develop databases and file specifications 4. Develop the program design to specify: • What programs to write • What each program will do

Analysis Phase

1. Develop an analysis strategy • Model the current system • Formulate the new system 2. Gather the requirements • Develop a system proposal • Create a business model to represent: -Business data -Business processes 3. Develop a system proposal

What are some Requirements Analysis Strategies?

1. Problem analysis 2. Root cause analysis 3. Duration analysis 4. Activity-based costing 5. Informal benchmarking 6. Outcome analysis 7. Technology analysis 8. Activity elimination

Planning Phase

1. ProjectInitiation • Develop/receive a system request • Conduct a feasibility analysis 2. ProjectManagement • Develop the work plan • Staff the project • Monitor & control the project

Implementation phase

1. System Construction- system is built and tested to ensure it performs as designed. 2. System Installed - (installation) is the process of the old system being turned off and the new one is turned on; (training) how to use new system 3. Support Plan- review of system

Advantages of waterfall development

1. identifies system requirements long before programming begins 2. minimizes changes to the requirements as project proceeds

What is a requirement?

A statement of what the system must do or a characteristic it must have that will later evolve into a technical description of how the system will be implemented

The conflict between the need for truly integrated initiatives and traditional siloed budgets budgets frequently cause budgeting problems. A proposal would be:

Adaption of enterprise funding models

Technology analysis

Apply new technologies to business processes & identify benefits

Object-oriented systems

Attempts to balance data and process

Fiscal IT Budgets (those prepared for the CFO) are broken down into two major categories:

Capital expenditures & Operating Expenses

The System Proposal

Combines all material created in planning & analysis Included sections: • Executive summary • The system request • The workplan • The feasibility analysis • The requirements definition • Current models of the system (expected to evolve)

The process of allocating the cost of the services IT provides to other's budgets is called:

Cost allocation

Unified Modeling Language

Provides a common vocabulary of OO terms and diagramming techniques

________ should serve as a high-level overview of how risk is to be managed in an enterprise and can also act as a structure for reporting on risk at various levels of detail.

Risk Management Framework

Establishing controls, practices, and tools for addressing each type of risk is also known as:

Risk Mitigation

________ is an ongoing process because levels and types of risk are changing continually.

Risk Monitoring

In order to separate maintenance and support from new project development, IT managers must:

Separate operations from innovation

Which of the following is NOT part of the IT processes (for budgeting)

Strategic IT Budget

Spending on initiatives and technology designed to deliver new business value and achieve the enterprises strategic objective is known as:

Strategic Investments

key person in the SDLC

System analyst

Structured development/design

adopt a formal step-by-step approach to the SDLC that moves logically from one phase to the next. ex. -waterfall development -parallel development

Rapid application development (RAD)

attempt to address both weaknesses of structured design methodologies by adjusting the SDLC phases to get some part of the system devel- oped quickly and into the hands of the users. ex. -phased development -prototyping -throwaway prototyping

Agile Development

based on the agile manifesto and a set of twelve principles. Focus on streamlining the system-development process by eliminating much of the modeling and documentation overhead and the time spent on those tasks. ex. -extreme programming -SCRUM

Method

behavior of a class

Phased development

breaks and overall system into a series of versions that are developed sequentially

advantages of parallel development

can reduce the time to deliver a system

Encapsulation

combination of process & data

Class

general template we use to define and create specific instances, or objects.

Message

information sent to an object to trigger a method

Architecture centric

means that the underlying so ware architecture of the evolving system speci cation drives the speci cation, construction, and documentation of the system

Prototyping

performs the analysis, design, and implementation phases concurrently, all three phase are performed repeatedly in a cycle until the system is completed

In which phase of the SDLC is the project plan developed?

planning

systems development life cycle (SDLC)

process of understanding how an infor- mation system (IS) can support business needs by designing a system, building it, and delivering it to users.