Systems Development Life Cycle Overview
60 Questions
0 Views

Choose a study mode

Play Quiz
Study Flashcards
Spaced Repetition
Chat to lesson

Podcast

Play an AI-generated podcast conversation about this lesson

Questions and Answers

Automating a current system always leads to improved efficiency.

False

The traditional systems development life cycle includes a feasibility study as one of its phases.

True

Prototyping is guaranteed to speed up the systems development process.

False

End-user development is effective for large-scale development projects.

<p>False</p> Signup and view all the answers

The phases of the ERP systems design process are identical to those in traditional systems development.

<p>False</p> Signup and view all the answers

Creating a logical database design is recommended after the details are refined in the systems development process.

<p>False</p> Signup and view all the answers

Detailed analysis of systems uses process models and data models to identify problem areas.

<p>True</p> Signup and view all the answers

Maintenance is the final phase of the ERP systems design process.

<p>True</p> Signup and view all the answers

Economies of scale are particularly advantageous in the development of software packages.

<p>True</p> Signup and view all the answers

Tangible benefits are not considered during the needs assessment phase.

<p>False</p> Signup and view all the answers

Re-engineering business processes always leads to a smoother transition than customization.

<p>False</p> Signup and view all the answers

Using a 'vanilla' implementation approach is generally associated with on-time and on-budget deployments.

<p>True</p> Signup and view all the answers

Maintaining legacy systems while adding ERP modules typically ensures that organizations reap the full benefits of the ERP system.

<p>False</p> Signup and view all the answers

Customization of software may lead to increased time and costs compared to standard implementations.

<p>True</p> Signup and view all the answers

Interactive prototyping requires limited user involvement during the design phase.

<p>False</p> Signup and view all the answers

External vendors providing Application Service Provider (ASP) services ensure the organization has complete control over operations.

<p>False</p> Signup and view all the answers

The checklist of activities and factors is essential during the re-engineering process to ensure compliance with new business requirements.

<p>True</p> Signup and view all the answers

Best practices methodology is used to identify processes that do not align with the system while allowing customization of unsupported processes.

<p>True</p> Signup and view all the answers

The primary goal of the design phase is to identify business processes to be eliminated from the organization.

<p>False</p> Signup and view all the answers

Re-engineering business processes means adjusting software to fit existing workflows without making significant changes.

<p>False</p> Signup and view all the answers

Which phase of the traditional systems development life cycle involves creating a logical database design?

<p>Detailed design</p> Signup and view all the answers

What is a key disadvantage of automating a current information system?

<p>Inheriting old problems and flaws</p> Signup and view all the answers

Which approach to systems development involves significant feedback from end-users?

<p>Prototyping</p> Signup and view all the answers

What is a primary benefit of using software packages in system development?

<p>Economies of scale in development and maintenance</p> Signup and view all the answers

Which phase in the ERP systems design process specifically focuses on tangible and intangible benefits?

<p>Planning</p> Signup and view all the answers

End-user development is least effective in which of the following contexts?

<p>Large-scale development projects</p> Signup and view all the answers

Which activity is not part of the traditional systems development life cycle?

<p>Pilot testing</p> Signup and view all the answers

In the context of ERP systems, what is one major challenge associated with the detailed design phase?

<p>Difficulty in requirement identification</p> Signup and view all the answers

What does re-engineering a current system primarily aim to achieve?

<p>Address existing problems in the workflow</p> Signup and view all the answers

What is one drawback of using the prototyping development approach?

<p>Not necessarily resulting in faster development</p> Signup and view all the answers

What is a key disadvantage of re-engineering business processes rather than customizing software?

<p>It often results in significant changes to workflows and procedures.</p> Signup and view all the answers

Which approach to ERP implementation is characterized by minimal customization and reliance on vendor-provided methodologies?

<p>Vanilla implementation</p> Signup and view all the answers

What is a common consequence of maintaining legacy systems while adding ERP modules?

<p>A lack of full benefits from the ERP system.</p> Signup and view all the answers

What role does user involvement play in the detailed design phase of an ERP system?

<p>Extensive user involvement is crucial for accurate prototyping.</p> Signup and view all the answers

Which of the following statements accurately describes the outcome of a customized ERP implementation?

<p>It tends to increase the total time and costs incurred.</p> Signup and view all the answers

What is a distinguishing characteristic of outsourcing ERP functioning to external vendors?

<p>Reliability and stability of the vendor are crucial for success.</p> Signup and view all the answers

In the context of ERP design, what does the 'best practices' methodology primarily facilitate?

<p>Selection of applicable processes and models for the system.</p> Signup and view all the answers

What is the primary risk associated with the 'vanilla' implementation strategy?

<p>Inability to meet unique organizational needs.</p> Signup and view all the answers

Which factor is less likely to be a consequence of customizing a software solution?

<p>Simpler integration with future software versions.</p> Signup and view all the answers

What is a critical factor to consider when deciding whether to re-engineer or customize business processes in ERP implementation?

<p>Evaluating the impact on existing workflows and procedures.</p> Signup and view all the answers

The first phase of the ERP systems design process is ______.

<p>Planning</p> Signup and view all the answers

A needs assessment is part of the ______ phase.

<p>Planning</p> Signup and view all the answers

Automating a current system may inherit old problems and ______.

<p>flaws</p> Signup and view all the answers

New approaches to systems development include prototyping and ______ development.

<p>end-user</p> Signup and view all the answers

The detailed analysis of systems includes the use of ______ models and data models.

<p>process</p> Signup and view all the answers

One disadvantage of end-user development is that it is not effective for ______-scale development.

<p>large</p> Signup and view all the answers

The maintenance phase involves ongoing support and ______ of the system.

<p>upgrading</p> Signup and view all the answers

The phase involving tangible and intangible benefits is part of the ______ analysis.

<p>Requirements</p> Signup and view all the answers

The major activities in the traditional systems development life cycle include feasibility study and ______ design.

<p>systems</p> Signup and view all the answers

Prototyping may not necessarily lead to ______ in the development process.

<p>speed</p> Signup and view all the answers

The implementation of __________ can lead to changes in workflow and procedures.

<p>re-engineering</p> Signup and view all the answers

A __________ implementation typically follows vendor prescribed methodologies and is considered easier to implement.

<p>vanilla</p> Signup and view all the answers

Outsourcing involves an __________ vendor operating the necessary functions, relying on their stability.

<p>external</p> Signup and view all the answers

During the detailed design phase, a team should select applicable business processes based on __________ methodology.

<p>best practices</p> Signup and view all the answers

Maintaining legacy systems while adding __________ modules can be a cost-effective solution but might limit the benefits.

<p>ERP</p> Signup and view all the answers

Customization of software solutions generally leads to increased __________ and costs compared to standard implementations.

<p>time</p> Signup and view all the answers

One of the risks of __________ is that upgrading can become difficult due to high levels of customization.

<p>customizing</p> Signup and view all the answers

Interactions in __________ prototyping result in extensive user involvement during the design process.

<p>interactive</p> Signup and view all the answers

The choice between re-engineering and __________ often impacts how effectively an organization can implement new processes.

<p>customization</p> Signup and view all the answers

An important factor that needs consideration when deciding on business process modifications is the __________ of the changes involved.

<p>disruption</p> Signup and view all the answers

Study Notes

Traditional Systems Development Life Cycle

  • The traditional systems development life cycle (SDLC) consists of multiple phases for system development, planning, design, detailed design, implementation, and maintenance.
  • The traditional SDLC utilizes tools and techniques to determine problem areas.
  • The SDLC emphasizes analysis of the current system.

Shortcomings of Traditional Systems Development Life Cycle

  • Automating current systems can perpetuate existing problems, flaws, and inefficiencies.
  • The SDLC can be very time-consuming and resource intensive.
  • The SDLC can also be expensive.

New Approaches to Systems Development

  • Prototyping involves building models that can be presented to end-users for feedback.
  • End-user development allows end-users to create information systems.
  • Software packages leverage economies of scale for development and maintenance.

ERP Systems Design Process

  • The ERP systems design process incorporates the traditional SDLC but with adaptations.
  • It involves planning, analysis, design, detailed design, implementation and maintenance.

Planning

  • The planning phase includes assessing needs and justifying the business case for implementation.
  • Tangible and intangible benefits should be considered during planning.
  • Requirements analysis helps determine the business processes to be supported by the ERP system.
  • “Best practices” offered by vendors provide models of supported functions, checklists of activities, and relevant factors.

Design Phase

  • The design phase focuses on aligning business processes to the ERP system.
  • The SDLC typically involves defining new business requirements and implementing software that conforms to them.
  • The design phase considers re-engineering business processes or customizing the system.
  • Re-engineering business processes can disrupt workflow and organizational procedures.
  • Customization can make future upgrades challenging.

Alternative Design Approaches

  • Vanilla implementation provides a straightforward approach that follows vendor guidelines and involves consultant expertise.
  • Vanilla implementations often meet deadlines and budget constraints.
  • Customized implementations require more time, resources, and can be complex to integrate with future updates.
  • Maintaining legacy systems alongside ERP modules can be cost-effective but may limit the full benefits of ERP implementation.
  • Outsourcing can involve external vendors operating the ERP system or ASPs providing time-sharing access.

Detailed Design Phase

  • This phase selects models, processes, and information to be supported.
  • The ERP system's “best practices” methodology guides the selection of appropriate business processes.
  • Processes that are not fully compatible with the system become candidates for re-engineering.
  • Areas not covered by the ERP system are identified for possible customization.
  • This phase relies on interactive prototyping and extensive user involvement.

Traditional Systems Development Life Cycle

  • Detailed analysis of a system using structured tools and techniques to determine problem areas
  • Phases include: problem definition, feasibility study, systems analysis, systems design, detailed design, implementation, and maintenance
  • Automating a current system is generally counterproductive
  • Provides an opportunity to re-engineer the current system
  • Logical database design is created before detailed design is refined
  • Time-consuming, resource-intensive and expensive

New Approaches to System Development

  • Prototyping: Models shown to end-users for feedback
  • End-User Development: End-users create information systems using spreadsheets and databases
  • Software Packages: Economies of scale in development, enhancement, and maintenance

ERP Systems Design Process

  • Phases include: Planning, Requirements Analysis, Design, Detailed Design, Implementation, and Maintenance

Planning and Requirements Phase

  • Needs assessment: Determines the requirements of the project
  • Business justification: Justification of the project's impact using quantifiable and unquantifiable benefits
  • Requirements analysis: Identification of the business processes to be supported by the system
  • "Best practices" are offered by ERP vendors
  • Checklist of activities and factors helps to determine the scope and complexity of the project

Design Phase

  • Re-engineering business processes to fit software
  • Re-engineering can disrupt the organization and lead to changes in workflow and procedures
  • Customization can make upgrading versions difficult

Alternative Designs

  • "Vanilla" ERP implementations follow vendor methodology and are typically on time and within budget
  • Customized ERP implementations have increased time and costs and are not easily integrated into new versions
  • Maintain legacy systems and add specific ERP modules to support particular functions: Cost-effective, less disruptive, lacks integration
  • Outsourcing: An external vendor operates the system
  • ASPs provide on time-sharing basis.
  • Relies on the reliability and stability of the vendor.

Detailed Design Phase

  • The team selects the models, processes, and information to be supported
  • The "best practices" methodology provides an initial model selection.
  • Applicable business processes are selected, inapplicable processes are discarded.
  • Processes that don't match the system are used as foundation for re-engineering.
  • Identify any areas not covered as candidates for customization
  • User involvement in interactive prototyping is extensive

Enterprise Resource Planning Systems Development

  • Traditional Systems Development Life Cycle (SDLC)

    • Phases: problem definition, feasibility study, systems analysis, systems design, detailed design, implementation, and maintenance.
    • Involves detailed analysis using tools and techniques like process models and data models.
    • Often involves automating current systems.
  • Issues with Traditional SDLC

    • Inherits old problems and flaws.
    • Can take a long time and require significant resources.
    • Can be expensive.
  • New Approaches to Systems Development

    • Prototyping: Models are shown to end-users for feedback and guidance.
    • End-user development: End users create information systems using spreadsheets and databases.
    • Software packages: Offer economies of scale in development, enhancement, and maintenance.

ERP Systems Development Process

  • Phases: planning, requirements analysis, design, detailed design, implementation, and maintenance.

  • Planning & Requirements Analysis

    • Needs assessment: Identifies the need for the new system.
    • Business justification: Provides tangible and intangible benefits for implementing the new system.
    • Identify business processes to be supported by the new ERP system.
    • Vendors often offer "best practices" models of supported functions.
  • Design Phase

    • Re-engineer business processes to fit the software.
    • Re-engineering versus customization:
      • Re-engineering can disrupt the organization (changes in workflow and procedures).
      • Customization can make upgrading difficult.
  • Alternative ERP Designs

    • "Vanilla" ERP Implementation:
      • Easy to implement (follows vendor methodology).
      • Uses consultants with specialized ERP expertise.
      • Usually on time and on budget.
    • Customized ERP:
      • Time and costs increase.
      • Not easily integrated into new versions.
    • Legacy Systems and ERP Module Integration:
      • Supports specific functions.
      • Cost-effective.
      • The organization may not receive the full benefits of the ERP.
      • Less disruptive.
      • Lacks integration.
    • Outsourcing:
      • External vendor operates the system.
      • ASPs (Application Service Providers) provide time-sharing access.
      • Depends on reliability and stability of the vendor.
  • Detailed Design Phase

    • Selection of models, processes, and information to be supported.
    • "Best practices" methodology provides models to guide selection.
    • Processes that don't match the system are candidates for re-engineering.
    • Any areas not covered by the chosen model are candidates for customization.
    • Relies on interactive prototyping for extensive user involvement.

Studying That Suits You

Use AI to generate personalized quizzes and flashcards to suit your learning preferences.

Quiz Team

Related Documents

Description

This quiz explores the traditional Systems Development Life Cycle (SDLC), its phases, and shortcomings. Additionally, it covers new approaches such as prototyping and end-user development in the context of ERP systems. Test your knowledge on the evolution of system design processes!

More Like This

Use Quizgecko on...
Browser
Browser