MIS 180 Chapter Notes - Chapter 9: Systems Development Life Cycle, Legacy System, Application Software
Chapter 9
Systems Development and Project Management:
Corporate Responsibility
The Systems Development Life Cycle (SDLC)
The overall process for developing information systems, from planning
and analysis through implementation and maintenance
•
Legacy system
An old-system that is fast approaching or beyond the end of its
useful life within an organization
○
•
Conversion
The process of transferring information from a legacy system to a
new-system
○
•
Off-the-shelf application software
Supports general business processes and does not require any
specific software customization to meet the organization's needs
○
•
Phases of SDLC
Phase 1: Planning
Establishes a high-level plan of the intended project and determines
project goals
○
First and most critical phase of any systems development effort
○
Change agent
A person or event that is the catalyst for implementing major
changes for a system to meet business changes
§
○
Brainstorming
A technique for generating ideas by encouraging participants
to offer as many ideas as possible in a short period without
any analysis until all the ideas have been exhausted
§
○
Project
A temporary activity a company undertakes to create a unique
product, service, or result
§
○
Project manager
An individual who is an expert in project planning and
management, defines and develops the project plan, and
tracks the plan to ensure the project is completed on time and
on budget
§
○
Project plan
A formal, approved document that manages and controls the
entire project
§
○
•
Phase 2: Analysis
The firm analyzes its end-user business requirements and refines
project goals into defined functions and operations of the intended
system
○
Business requirements
The specific business requests the system must meet to be
successful, so the analysis phase is critical because business
requirements drive the entire systems development effort
§
○
Requirements management
The process of managing changes to the business
requirements throughout the project
§
○
Requirements definition document
Prioritizes all of the business requirements by order of
importance to the company
§
○
Sign-off
The users' actual signatures indicating they approve all of the
business requirements
§
○
Data flow diagram (DFD)
Illustrates the movement of information between external
entities and the processes and data stores within the system
§
○
Computer-aided software engineering (CASE)
Tools are software suites that automate systems analysis,
design, and development
§
○
•
Phase 3: Design
Establishes descriptions of the desired features and operations of
the system, including screen layouts, business rules, process
diagrams, pseudo code, and other documentation
○
Graphical user interface (GUI)
The interface to an information system
§
GUI screen design is the ability to model the information
system screens for an entire system by using icons, buttons,
menus, and submenus
§
○
•
Phase 4: Development
Takes all the detailed design documents from the design phase and
transforms them into the actual system
○
The project transitions from preliminary designs to actual physical
implementation
○
Software engineering
A disciplined approach for constructing information systems
through the use of common methods, techniques, or tools
§
○
Control objects for information and related technology (COBIT)
A set of best practices that helps an organization to maximize
the benefits of an information system, while at the same time
establishing appropriate controls to ensure minimum errors
§
○
Scripting language
A programming method that provides for interactive modules
to a website
§
○
Object-orientated languages
Group data and corresponding processes into objects
§
○
Fourth-generation languages (4GL)
Programming languages that look similar to human languages
§
○
•
Phase 5: Testing
Brings all the project pieces together into a special testing
environment to eliminate errors and bugs and verify that they
system meets all the business requirements defined in the analysis
phase
○
Bugs
Defects in the code of an information system
§
○
Test conditions
Detail the steps the system must perform along with the
expected result of each step
§
○
•
Phase 6: Implementation
The organization places the system into production so users can
begin to perform actual business operations with it
○
User documentation
Created that highlights how to use the system and how to
troubleshoot issues or problems
§
○
Online training
Runs over the Internet or on a CD or DVD, and employees
complete the training on their own time at their own pace
§
○
Workshop training
Held in a classroom environment and led by an instructor
§
○
Help desk
A group of people who respond to users' questions
§
○
•
Phase 7: Maintenance
The organization performs changes, corrections, additions, and
upgrades to ensure the system continues to meet business goals
○
Corrective maintenance
Makes system changes to repair design flaws, coding errors,
or implementation issues
§
○
Preventive maintenance
Makes system changes to reduce the chance of future system
failure
§
○
•
Software Development Methodologies
Methodology
A set of policies, procedures, standards, processes, practices, tools,
techniques, and tasks that people apply to technical and
management challenges
○
•
Waterfall methodology
A sequence of phases in which the output of each phase becomes
the input for the next
○
•
Prototyping
A modern design approach where the designers and system users
use an iterative approach to building the system
○
•
Discovery prototyping
Builds a small-scale representation or working model of the system
to ensure it meets the user and business requirements
○
•
Agile software development methodologies
Iterative development
Consists of a series of tiny projects
§
○
Agile methodology
Aims for customer satisfaction through early and continuous
delivery of useful software components developed by an
iterative process using the bare minimum requirements
§
○
•
Rapid application development (RAD) methodology
Emphasizes extensive user involvement in the rapid and
evolutionary construction of working prototypes of a system, to
accelerate the systems development process
○
•
Extreme programming methodology
Breaks a project into four phases, and developers cannot continue
to the next phase until the previous phase is complete
○
•
Rational unified process (RUP) methodology
Owned by IBM, provides a framework for breaking down the
development of software into four "gates"
○
•
Scrum methodology
Uses small teams to produce small pieces of software using a series
of "sprints," or 30-day intervals, to achieve an appointed goal
○
•
Developing a Service-Oriented Architecture
Service-oriented architecture (SOA)
A business-driven enterprise architecture that supports integrating
a business as linked, repeatable activities, tasks, or services
○
Ensures that MIS systems can adapt quickly, easily, and
economically to support rapidly changing business needs
○
Promotes a scalable and flexible enterprise architecture that can
implement new or reuse existing MIS components, creating
connections among disparate applications and systems
○
•
SOA Concepts
Service
A business task
○
•
Interoperability
The capability of two or more computer systems to share data and
resources, even though they are made by different manufacturers
○
Web service
An open-standards way of supporting interoperability
§
○
Extensible markup language (XML)
A markup language for documents, containing structured
information
§
○
•
Loose coupling
The capability of services or dissembled just as easily into their
functional components
○
•
Using Project Management to Deliver Successful Projects
Tangible benefits
Easy to quantify and typically measured to determine the success or
failure of a project
○
•
Intangible benefits
Difficult to quantify or measure
○
•
Feasibility
The measure of the tangible and intangible benefits of an
information system
○
Types of feasibility studies
Economic
Measures the cost-effectiveness of a project□
§
Operational
Measures how well a solution meets the identified
system requirements to solve the problems and take
advantage of opportunities
□
§
Schedule
Measures the project time frame to ensure it can be
completed on time
□
§
Technical
Measures the practicality of a technical solution and the
availability of technical resources and expertise
□
§
Political
Measures how well the solution will be accepted in a
given organization
□
§
Legal
Measures how well a solution can be implemented
within existing legal and contractual obligations
□
§
○
•
Primary Project Planning Diagrams
Kill switch
A trigger that enables a project manager to close the project before
completion
○
•
PERT (Program Evaluation and Review Technique) chart
A graphical network model that depicts a project's tasks and the
relationships between them
○
•
Dependency
A logical relationship that exists between the project tasks, or
between a project task and a milestone
○
•
Critical path
Estimates the shortest path through the project ensuring all critical
tasks are completed from start to finish
○
•
Gantt chart
A simple bar chart that lists project tasks vertically against the
project's time frame, listed horizontally
○
•
Outsourcing Projects
In-sourcing (in-house development)
Uses the professional expertise within an organization to develop
and maintain its information technology systems
○
Has been instrumental in creating a viable supply of IT professionals
and in creating a better quality workforce combining both technical
and business skills
○
•
Outsourcing
An arrangement by which one organization provides a service or
services for another organization that chooses not to perform them
in-house
○
Onshore
Engaging another company within the same country for
services
§
○
Nearshore
Contracting an outsourcing arrangement with a company in a
nearby country
§
Often this country will share a border with the native country
§
○
Offshore
Using organizations from developing countries to write code
and develop systems
§
The country is geographically far away
§
○
•
Chapter 9 Notes
Tuesday, May 1, 2018
9:58 AM
Chapter 9
Systems Development and Project Management:
Corporate Responsibility
The Systems Development Life Cycle (SDLC)
The overall process for developing information systems, from planning
and analysis through implementation and maintenance
•
Legacy system
An old-system that is fast approaching or beyond the end of its
useful life within an organization
○
•
Conversion
The process of transferring information from a legacy system to a
new-system
○
•
Off-the-shelf application software
Supports general business processes and does not require any
specific software customization to meet the organization's needs
○
•
Phases of SDLC
Phase 1: Planning
Establishes a high-level plan of the intended project and determines
project goals
○
First and most critical phase of any systems development effort
○
Change agent
A person or event that is the catalyst for implementing major
changes for a system to meet business changes
§
○
Brainstorming
A technique for generating ideas by encouraging participants
to offer as many ideas as possible in a short period without
any analysis until all the ideas have been exhausted
§
○
Project
A temporary activity a company undertakes to create a unique
product, service, or result
§
○
Project manager
An individual who is an expert in project planning and
management, defines and develops the project plan, and
tracks the plan to ensure the project is completed on time and
on budget
§
○
Project plan
A formal, approved document that manages and controls the
entire project
§
○
•
Phase 2: Analysis
The firm analyzes its end-user business requirements and refines
project goals into defined functions and operations of the intended
system
○
Business requirements
The specific business requests the system must meet to be
successful, so the analysis phase is critical because business
requirements drive the entire systems development effort
§
○
Requirements management
The process of managing changes to the business
requirements throughout the project
§
○
Requirements definition document
Prioritizes all of the business requirements by order of
importance to the company
§
○
Sign-off
The users' actual signatures indicating they approve all of the
business requirements
§
○
Data flow diagram (DFD)
Illustrates the movement of information between external
entities and the processes and data stores within the system
§
○
Computer-aided software engineering (CASE)
Tools are software suites that automate systems analysis,
design, and development
§
○
•
Phase 3: Design
Establishes descriptions of the desired features and operations of
the system, including screen layouts, business rules, process
diagrams, pseudo code, and other documentation
○
Graphical user interface (GUI)
The interface to an information system
§
GUI screen design is the ability to model the information
system screens for an entire system by using icons, buttons,
menus, and submenus
§
○
•
Phase 4: Development
Takes all the detailed design documents from the design phase and
transforms them into the actual system
○
The project transitions from preliminary designs to actual physical
implementation
○
Software engineering
A disciplined approach for constructing information systems
through the use of common methods, techniques, or tools
§
○
Control objects for information and related technology (COBIT)
A set of best practices that helps an organization to maximize
the benefits of an information system, while at the same time
establishing appropriate controls to ensure minimum errors
§
○
Scripting language
A programming method that provides for interactive modules
to a website
§
○
Object-orientated languages
Group data and corresponding processes into objects
§
○
Fourth-generation languages (4GL)
Programming languages that look similar to human languages
§
○
•
Phase 5: Testing
Brings all the project pieces together into a special testing
environment to eliminate errors and bugs and verify that they
system meets all the business requirements defined in the analysis
phase
○
Bugs
Defects in the code of an information system
§
○
Test conditions
Detail the steps the system must perform along with the
expected result of each step
§
○
•
Phase 6: Implementation
The organization places the system into production so users can
begin to perform actual business operations with it
○
User documentation
Created that highlights how to use the system and how to
troubleshoot issues or problems
§
○
Online training
Runs over the Internet or on a CD or DVD, and employees
complete the training on their own time at their own pace
§
○
Workshop training
Held in a classroom environment and led by an instructor
§
○
Help desk
A group of people who respond to users' questions
§
○
•
Phase 7: Maintenance
The organization performs changes, corrections, additions, and
upgrades to ensure the system continues to meet business goals
○
Corrective maintenance
Makes system changes to repair design flaws, coding errors,
or implementation issues
§
○
Preventive maintenance
Makes system changes to reduce the chance of future system
failure
§
○
•
Software Development Methodologies
Methodology
A set of policies, procedures, standards, processes, practices, tools,
techniques, and tasks that people apply to technical and
management challenges
○
•
Waterfall methodology
A sequence of phases in which the output of each phase becomes
the input for the next
○
•
Prototyping
A modern design approach where the designers and system users
use an iterative approach to building the system
○
•
Discovery prototyping
Builds a small-scale representation or working model of the system
to ensure it meets the user and business requirements
○
•
Agile software development methodologies
Iterative development
Consists of a series of tiny projects
§
○
Agile methodology
Aims for customer satisfaction through early and continuous
delivery of useful software components developed by an
iterative process using the bare minimum requirements
§
○
•
Rapid application development (RAD) methodology
Emphasizes extensive user involvement in the rapid and
evolutionary construction of working prototypes of a system, to
accelerate the systems development process
○
•
Extreme programming methodology
Breaks a project into four phases, and developers cannot continue
to the next phase until the previous phase is complete
○
•
Rational unified process (RUP) methodology
Owned by IBM, provides a framework for breaking down the
development of software into four "gates"
○
•
Scrum methodology
Uses small teams to produce small pieces of software using a series
of "sprints," or 30-day intervals, to achieve an appointed goal
○
•
Developing a Service-Oriented Architecture
Service-oriented architecture (SOA)
A business-driven enterprise architecture that supports integrating
a business as linked, repeatable activities, tasks, or services
○
Ensures that MIS systems can adapt quickly, easily, and
economically to support rapidly changing business needs
○
Promotes a scalable and flexible enterprise architecture that can
implement new or reuse existing MIS components, creating
connections among disparate applications and systems
○
•
SOA Concepts
Service
A business task
○
•
Interoperability
The capability of two or more computer systems to share data and
resources, even though they are made by different manufacturers
○
Web service
An open-standards way of supporting interoperability
§
○
Extensible markup language (XML)
A markup language for documents, containing structured
information
§
○
•
Loose coupling
The capability of services or dissembled just as easily into their
functional components
○
•
Using Project Management to Deliver Successful Projects
Tangible benefits
Easy to quantify and typically measured to determine the success or
failure of a project
○
•
Intangible benefits
Difficult to quantify or measure
○
•
Feasibility
The measure of the tangible and intangible benefits of an
information system
○
Types of feasibility studies
Economic
Measures the cost-effectiveness of a project□
§
Operational
Measures how well a solution meets the identified
system requirements to solve the problems and take
advantage of opportunities
□
§
Schedule
Measures the project time frame to ensure it can be
completed on time
□
§
Technical
Measures the practicality of a technical solution and the
availability of technical resources and expertise
□
§
Political
Measures how well the solution will be accepted in a
given organization
□
§
Legal
Measures how well a solution can be implemented
within existing legal and contractual obligations
□
§
○
•
Primary Project Planning Diagrams
Kill switch
A trigger that enables a project manager to close the project before
completion
○
•
PERT (Program Evaluation and Review Technique) chart
A graphical network model that depicts a project's tasks and the
relationships between them
○
•
Dependency
A logical relationship that exists between the project tasks, or
between a project task and a milestone
○
•
Critical path
Estimates the shortest path through the project ensuring all critical
tasks are completed from start to finish
○
•
Gantt chart
A simple bar chart that lists project tasks vertically against the
project's time frame, listed horizontally
○
•
Outsourcing Projects
In-sourcing (in-house development)
Uses the professional expertise within an organization to develop
and maintain its information technology systems
○
Has been instrumental in creating a viable supply of IT professionals
and in creating a better quality workforce combining both technical
and business skills
○
•
Outsourcing
An arrangement by which one organization provides a service or
services for another organization that chooses not to perform them
in-house
○
Onshore
Engaging another company within the same country for
services
§
○
Nearshore
Contracting an outsourcing arrangement with a company in a
nearby country
§
Often this country will share a border with the native country
§
○
Offshore
Using organizations from developing countries to write code
and develop systems
§
The country is geographically far away
§
○
•
Chapter 9 Notes
Tuesday, May 1, 2018 9:58 AM
Chapter 9
Systems Development and Project Management:
Corporate Responsibility
The Systems Development Life Cycle (SDLC)
The overall process for developing information systems, from planning
and analysis through implementation and maintenance
•
Legacy system
An old-system that is fast approaching or beyond the end of its
useful life within an organization
○
•
Conversion
The process of transferring information from a legacy system to a
new-system
○
•
Off-the-shelf application software
Supports general business processes and does not require any
specific software customization to meet the organization's needs
○
•
Phases of SDLC
Phase 1: Planning
Establishes a high-level plan of the intended project and determines
project goals
○
First and most critical phase of any systems development effort
○
Change agent
A person or event that is the catalyst for implementing major
changes for a system to meet business changes
§
○
Brainstorming
A technique for generating ideas by encouraging participants
to offer as many ideas as possible in a short period without
any analysis until all the ideas have been exhausted
§
○
Project
A temporary activity a company undertakes to create a unique
product, service, or result
§
○
Project manager
An individual who is an expert in project planning and
management, defines and develops the project plan, and
tracks the plan to ensure the project is completed on time and
on budget
§
○
Project plan
A formal, approved document that manages and controls the
entire project
§
○
•
Phase 2: Analysis
The firm analyzes its end-user business requirements and refines
project goals into defined functions and operations of the intended
system
○
Business requirements
The specific business requests the system must meet to be
successful, so the analysis phase is critical because business
requirements drive the entire systems development effort
§
○
Requirements management
The process of managing changes to the business
requirements throughout the project
§
○
Requirements definition document
Prioritizes all of the business requirements by order of
importance to the company
§
○
Sign-off
The users' actual signatures indicating they approve all of the
business requirements
§
○
Data flow diagram (DFD)
Illustrates the movement of information between external
entities and the processes and data stores within the system
§
○
Computer-aided software engineering (CASE)
Tools are software suites that automate systems analysis,
design, and development
§
○
•
Phase 3: Design
Establishes descriptions of the desired features and operations of
the system, including screen layouts, business rules, process
diagrams, pseudo code, and other documentation
○
Graphical user interface (GUI)
The interface to an information system
§
GUI screen design is the ability to model the information
system screens for an entire system by using icons, buttons,
menus, and submenus
§
○
•
Phase 4: Development
Takes all the detailed design documents from the design phase and
transforms them into the actual system
○
The project transitions from preliminary designs to actual physical
implementation
○
Software engineering
A disciplined approach for constructing information systems
through the use of common methods, techniques, or tools
§
○
Control objects for information and related technology (COBIT)
A set of best practices that helps an organization to maximize
the benefits of an information system, while at the same time
establishing appropriate controls to ensure minimum errors
§
○
Scripting language
A programming method that provides for interactive modules
to a website
§
○
Object-orientated languages
Group data and corresponding processes into objects
§
○
Fourth-generation languages (4GL)
Programming languages that look similar to human languages
§
○
•
Phase 5: Testing
Brings all the project pieces together into a special testing
environment to eliminate errors and bugs and verify that they
system meets all the business requirements defined in the analysis
phase
○
Bugs
Defects in the code of an information system
§
○
Test conditions
Detail the steps the system must perform along with the
expected result of each step
§
○
•
Phase 6: Implementation
The organization places the system into production so users can
begin to perform actual business operations with it
○
User documentation
Created that highlights how to use the system and how to
troubleshoot issues or problems
§
○
Online training
Runs over the Internet or on a CD or DVD, and employees
complete the training on their own time at their own pace
§
○
Workshop training
Held in a classroom environment and led by an instructor
§
○
Help desk
A group of people who respond to users' questions
§
○
•
Phase 7: Maintenance
The organization performs changes, corrections, additions, and
upgrades to ensure the system continues to meet business goals
○
Corrective maintenance
Makes system changes to repair design flaws, coding errors,
or implementation issues
§
○
Preventive maintenance
Makes system changes to reduce the chance of future system
failure
§
○
•
Software Development Methodologies
Methodology
A set of policies, procedures, standards, processes, practices, tools,
techniques, and tasks that people apply to technical and
management challenges
○
•
Waterfall methodology
A sequence of phases in which the output of each phase becomes
the input for the next
○
•
Prototyping
A modern design approach where the designers and system users
use an iterative approach to building the system
○
•
Discovery prototyping
Builds a small-scale representation or working model of the system
to ensure it meets the user and business requirements
○
•
Agile software development methodologies
Iterative development
Consists of a series of tiny projects
§
○
Agile methodology
Aims for customer satisfaction through early and continuous
delivery of useful software components developed by an
iterative process using the bare minimum requirements
§
○
•
Rapid application development (RAD) methodology
Emphasizes extensive user involvement in the rapid and
evolutionary construction of working prototypes of a system, to
accelerate the systems development process
○
•
Extreme programming methodology
Breaks a project into four phases, and developers cannot continue
to the next phase until the previous phase is complete
○
•
Rational unified process (RUP) methodology
Owned by IBM, provides a framework for breaking down the
development of software into four "gates"
○
•
Scrum methodology
Uses small teams to produce small pieces of software using a series
of "sprints," or 30-day intervals, to achieve an appointed goal
○
•
Developing a Service-Oriented Architecture
Service-oriented architecture (SOA)
A business-driven enterprise architecture that supports integrating
a business as linked, repeatable activities, tasks, or services
○
Ensures that MIS systems can adapt quickly, easily, and
economically to support rapidly changing business needs
○
Promotes a scalable and flexible enterprise architecture that can
implement new or reuse existing MIS components, creating
connections among disparate applications and systems
○
•
SOA Concepts
Service
A business task
○
•
Interoperability
The capability of two or more computer systems to share data and
resources, even though they are made by different manufacturers
○
Web service
An open-standards way of supporting interoperability
§
○
Extensible markup language (XML)
A markup language for documents, containing structured
information
§
○
•
Loose coupling
The capability of services or dissembled just as easily into their
functional components
○
•
Using Project Management to Deliver Successful Projects
Tangible benefits
Easy to quantify and typically measured to determine the success or
failure of a project
○
•
Intangible benefits
Difficult to quantify or measure
○
•
Feasibility
The measure of the tangible and intangible benefits of an
information system
○
Types of feasibility studies
Economic
Measures the cost-effectiveness of a project□
§
Operational
Measures how well a solution meets the identified
system requirements to solve the problems and take
advantage of opportunities
□
§
Schedule
Measures the project time frame to ensure it can be
completed on time
□
§
Technical
Measures the practicality of a technical solution and the
availability of technical resources and expertise
□
§
Political
Measures how well the solution will be accepted in a
given organization
□
§
Legal
Measures how well a solution can be implemented
within existing legal and contractual obligations
□
§
○
•
Primary Project Planning Diagrams
Kill switch
A trigger that enables a project manager to close the project before
completion
○
•
PERT (Program Evaluation and Review Technique) chart
A graphical network model that depicts a project's tasks and the
relationships between them
○
•
Dependency
A logical relationship that exists between the project tasks, or
between a project task and a milestone
○
•
Critical path
Estimates the shortest path through the project ensuring all critical
tasks are completed from start to finish
○
•
Gantt chart
A simple bar chart that lists project tasks vertically against the
project's time frame, listed horizontally
○
•
Outsourcing Projects
In-sourcing (in-house development)
Uses the professional expertise within an organization to develop
and maintain its information technology systems
○
Has been instrumental in creating a viable supply of IT professionals
and in creating a better quality workforce combining both technical
and business skills
○
•
Outsourcing
An arrangement by which one organization provides a service or
services for another organization that chooses not to perform them
in-house
○
Onshore
Engaging another company within the same country for
services
§
○
Nearshore
Contracting an outsourcing arrangement with a company in a
nearby country
§
Often this country will share a border with the native country
§
○
Offshore
Using organizations from developing countries to write code
and develop systems
§
The country is geographically far away
§
○
•
Chapter 9 Notes
Tuesday, May 1, 2018 9:58 AM
Document Summary
The overall process for developing information systems, from planning and analysis through implementation and maintenance. An old-system that is fast approaching or beyond the end of its useful life within an organization. The process of transferring information from a legacy system to a new-system. Supports general business processes and does not require any specific software customization to meet the organization"s needs. Establishes a high-level plan of the intended project and determines project goals. First and most critical phase of any systems development effort. A person or event that is the catalyst for implementing major changes for a system to meet business changes. A temporary activity a company undertakes to create a unique product, service, or result. An individual who is an expert in project planning and management, defines and develops the project plan, and tracks the plan to ensure the project is completed on time and on budget. A formal, approved document that manages and controls the entire project.
