C01 - The Systems Development Environment

A focus on adaptive rather than predictive methodologies.

Agile methodologies are adapted for real-world software development.

An evolutionary model.

The information system is coded, tested, installed, and supported in the organization.

To uncover better ways of developing software by doing it and helping others do it.

Planning.

87%.

The location of activities and the specific sequencing of steps in a project.

Knowledge about agile throughout the organization.

Efficiency of processing.

The Sprint.

An agile software development methodology that focuses on technical excellence and customer satisfaction.

It leads to the start of another cycle.

Scrum teams with associated roles, events, artifacts, and rules.

Requires top management support.

Two weeks to a month.

Microcomputers became key organizational tools.

Off-the-shelf software.

Other practices in eXtreme Programming.

Code, documentation, training procedures, and support capabilities.

Customers monitor the development process.

To focus on the product, what has been accomplished, and what needs to be done.

A focus on people rather than roles.

Several phases that mark the progress of systems analysis and design efforts.

More choice in producing good systems that come in on time and under budget.

Working software.

Because the organization’s needs may change over time, requiring adjustments to the system based on user needs.

Priorities for system and projects, architecture for data and networks, detailed work plan, system scope specification, resource assignment, and system justification.

It incurs great expense to make changes.

It is a spiral process cycling through phases at different levels.

A circular process.

Sutherland and Schwaber in 1995.

Once one phase ends, another begins, following a sequential process.

Current systems, both manual and computerized, that might be replaced or enhanced.

Their role is narrowly defined.

Two-person programming teams.

To develop, maintain, and replace information systems.

The need for a new or enhanced system.

No, it can be an iterative process.

Decisions made by the organization or client.

Approaches to software development that emphasize flexibility, collaboration, and customer feedback.

Resistance to change.

An Agile framework that uses iterative and incremental practices to manage complex projects.

To convert alternate solutions into logical and physical specifications.

To determine what needs to be delivered by the end of the Sprint and how the team will accomplish that work.

The analysis – design – code – test loop.

Description of the current system, identification of problems or opportunities, general recommendations, and justification for alternative systems.

A standard process followed in an organization to analyze, design, implement, and maintain information systems.

Systems Development Life Cycle.

The design process that is independent of any specific hardware or software platform.

Individuals and interactions.

The process of defining and designing information systems to meet business needs.

The stages involved in developing an information system from planning to implementation.

Continuous attention to technical excellence and good design.

Sustainable development.

Simplicity.

Short, incremental development cycles.

New systems become part of the daily activities of the organization.

Yes, at any given phase the project can return to a previous phase when needed.

The transformation of logical specifications into technology-specific details for programming/system construction.

Unpredictable or dynamic requirements.

Functional and technical specifications of system elements, including data, processes, inputs, outputs, and an acquisition plan for new technology.

Self-organizing teams.

New versions or releases of software along with updates to documentation, training, and support.

Building projects around motivated individuals and providing them with the environment and support they need.

Evolved to handle highly critical products but hard to tailor down to non-critical products.

Automating existing processes.

The systematic repair and improvement of an information system.

Machine or assembly language.

Related parts of the same process.

The process goes downhill until complete, resembling a waterfall.

Responding to change.

Enabled development of smaller, faster, less expensive computers.

A description of the alternate solution recommended by the analysis team.

Untested on safety-critical products.

Face-to-face conversation.

A focus on self-adaptive processes.

A baseline project plan.

Increased communications among developers.

It makes it difficult to go back to previous phases.

It can vary greatly from one project to the next.

Instruct computers what to do instead of how to do it.

Identifying, analyzing, prioritizing, and arranging needs.

A 15-minute meeting held to evaluate progress made within the past 24 hours and what needs to be done.

Studying system requirements from user input.

42%.

It became more like engineering, shifting focus from process first to data first.

Developers should be responsible and motivated.

Customers should understand the process and be willing to get involved.

To satisfy the customer through early and continuous delivery of valuable software.

Working software.

Product owner, Development team, Scrum master.

The advent of procedural (third-generation) languages.

No, they are not for every project.

An Agile methodology that focuses on frequent releases in short development cycles to improve software quality.

Well matched to small products and teams.

Automated tests are written by programmers.

Team performance and how it can improve.

They combine them into a single process.

Customer collaboration.

Designed for speed and multiple functional product releases.

It leads to higher levels of productivity.

A constant pace indefinitely.

It results in higher quality code.

Agile welcomes changing requirements, even late in development, as it harnesses change for the customer’s competitive advantage.

Reflects on how to become more effective and adjusts its behavior.

From a couple of weeks to a couple of months, with a preference for the shorter timescale.

Businesspeople and developers.

Simple design and continuous refactoring.

It is focused on meeting deadlines.

Methods evolved to handle large products and teams, but are hard to tailor down to small products.

4 hours.

A listing of only items to be addressed in a particular sprint.

They are fused into a single phase of activity.

Detailed plans and Big Design Up Front can lead to expensive rework.

Needs a critical mass of scarce experts during project definition but can work with fewer later.

Its unique way of capturing and presenting system requirements and design specifications.

System integration.

Visual programming environments like Visual Basic.

Represents the sum of all the Product Backlog items completed during a sprint.

A move to wireless system components.

Requires continuous presence of a critical mass of scarce experts.

3 hours.

A culture where roles are defined by clear practices and procedures.

Relational and object-oriented databases.

Enterprise-wide systems.

Web and Internet applications.

Assembling systems from programs and components purchased off the shelf.

A listing of potential requirements.

A culture where people feel comfortable and empowered by having many degrees of freedom.

Three-tier design.

Database on one server, application on a second server, client logic on user machines.

An agile framework for managing and completing complex projects through iterative progress.

Approaches to software development that emphasize flexibility, collaboration, and customer feedback.

A complex, challenging, and stimulating organizational process used by a team of business and systems professionals to develop and maintain information systems.

To support organizational functions or processes.

The process of examining and creating information systems to meet specific needs.

The organizational role most responsible for the analysis and design of information systems.

Methodologies, techniques, and tools.

A structured process for developing information systems through various phases.