CH17 – Business Flashcards

Increase revenues

A. Decrease productivity B. Damage to brand reputation C. Incur liabilities D. All of the above*

The overall process for developing information systems from planning and analysis through implementation and maintenance The SDLC is the overall process for developing information systems from planning and analysis through implementation and maintenance.

Systems development life cycle

Plan, analysis, design, develop, test, implement, maintain

Involves analyzing end-user business requirements and refining project goals into defined functions and operations of the intended system

Analysis

Involves describing the desired features and operations of the system

Involves placing the system into production so users can begin to perform actual business operations with the system

Methodology

. Flaws in accurately defining and articulating the business problem B. Managing costs, resources, and time constraints C. Assumes users can specify all business requirements in advance D. All of the above*

Iterative development

Agile methodology

Fast and efficient B. Small and nimble C. Lower cost D. All of the above*

SDLC

. Waterfall methodology

RAD methodology

Extreme programming

1 in 10 The waterfall methodology has a 10 percent success rate, or 1 in 10.

Focus initially on creating a prototype that looks and acts like the desired system B. Actively involve system users in the analysis, design, and development phases C. Accelerate collecting the business requirements through an interactive and iterative construction approach D. All of the above*

RUP

Collaboration Elaboration is the gate in RUP, not collaboration.

Elaboration Elaboration provides a rough order of magnitude.

Construction

RUP

Scrum

Scrum

30 days

Do not allow changing requirements, especially late in development

Test and deliver infrequently

TRUE Traditional business risk models typically ignored software development, largely because most organizations considered the impact from software and software development on the business to be minor.

FALSE Preventing liabilities is a business-related consequence of successful software.

FALSE The development phase involves taking all of the detailed design documents from the design phase and transforming them into the actual system.

TRUE The traditional waterfall methodology is a sequential, activity-based process in which each phase in the SDLC is performed sequentially from planning through implementation and maintenance.

TRUE A prototype is a smaller-scale representation or working model of the users' requirements or a proposed design for an information system.

Planning

Increased

Implementation

Maintenance

Analysis

Waterfall

Prototypes

Agile

Scope

Feature

Maintenance

Project

Planning phase - involves establishing a high-level plan of the intended project and determining project goals. Analysis phase - involves analyzing end-user business requirements and refining project goals into defined functions and operations of the intended system. Design phase - involves describing the desired features and operations of the system including screen layouts, business rules, process diagrams, pseudo code, and other documentation. Development phase - involves taking all of the detailed design documents from the design phase and transforming them into the actual system. Testing phase - involves bringing all the project pieces together into a special testing environment to test for errors, bugs, and interoperability, in order to verify that the system meets all the business requirements defined in the analysis phase. Implementation phase - involves placing the system into production so users can begin to perform actual business operations with the system. Maintenance phase - involves performing changes, corrections, additions, and upgrades to ensure the system continues to meet the business goals.

The benefits associated with successful software development include increase in revenues, repair to brand reputation, prevent liabilities, and increase in productivity.

There are a number of different software development methodologies. The waterfall methodology is a sequential, activity-based process in which each phase in the SDLC is performed sequentially from planning through implementation and maintenance. The rapid application development methodology (RAD) emphasizes extensive user involvement in the rapid and evolutionary construction of working prototypes of a system to accelerate the systems development process. The extreme programming (XP) methodology breaks a project into tiny phases, and developers cannot continue on to the next phase until the first phase is complete. The agile methodology is a form of XP, aims for customer satisfaction through early and continuous delivery of useful software components. Rational Unified Process (RUP) provides a framework for breaking down the development of software into four gates Gate One: Inception, Gate Two: Elaboration, Gate Three: Construction, Gate Four: Transition. Scrum - uses small teams to produce small pieces of deliverable software using sprints, or 30-day intervals, to achieve an appointed goal.

All software development methodologies use the systems development life cycle, however, the way that they use it differs. For example, all projects must have planning and testing phases, however one project might use the waterfall approach and have the planning occur at the beginning of the project and the testing occur at the end. Another project might use the XP method and have small planning and testing phases occurring all the time.

The waterfall methodology is a sequential, activity-based process in which each phase in the SDLC is performed sequentially from planning through implementation and maintenance. The agile methodology is a form of XP, aims for customer satisfaction through early and continuous delivery of useful software components. These are two opposite ends of the spectrum in terms of systems development methodologies. The primary difference between the waterfall and XP methodologies is that XP divides its phases into iterations with user feedback.

Only 28 percent of projects are developed within budget and delivered on time and as promised, says a report from the Standish Group, a Massachusetts-based consultancy. The primary reasons for project failure are: Unclear or missing business requirements, skipping SDLC phases, failure to manage project scope, failure to manage project plan, and changing technology.