L9_Information Systems Development

KHOA CÔNG NGHỆ THÔNG TIN
Course: INTRODUCTION TO
MANAGEMENT INFORMATION SYSTEMS
Lecture 9: Information Systems

Development
Department of Information System
2023 -2024
Learning Objectives
Upon successful completion of this lecture, you will be able to:

• Understand the relationship between system development and
project.
• Define the information system from three key viewpoints.
• Understand several development life cycle models.
• Understand software development decisions
• Identify the four primary implementation policies
2
Information System and Project
• An information system may require many projects for completion.
• The scope of a project may include more than one information system.
3
Three Viewpoints of a Project
4
Three Viewpoints of a Project
• There are three viewpoints for every project and the most critical factor for project
success is maintaining a balance among these viewpoints:
• The Business viewpoint: is focusing on the business aspect, one that produces a solution to
solve a business problem
• The Resources viewpoint: is focusing on managing resources such as people, budget, tools
etc. The goal is on delivering the project on-time, and within budget.
• The Quality viewpoint: is focusing on the need to deliver solutions with a good architecture,
one that is integrated and cohesive.
• Achieving this balance is essential because:
• Trade-offs among viewpoints are necessary.
• Concerns and conflicts among viewpoints must be resolved quickly.
• Synergy among participants with different viewpoints are important to the success of the
project.
5
Balancing the Three Viewpoints
• Achieving the appropriate balance between these three viewpoints is a key information
system management principle that can ensure a quality business solution.
• Each viewpoint requires a key role in every project and together they coordinate a total
quality solution.
• The three key roles:
• Project Manager (Focus on resource viewpoint)
• Business Manager (Focus on needs viewpoint)
• Technical Manager (Architect) (Focus on technical viewpoint)
• It is possible for one person to fill all three roles, but for larger projects, more than one
person may be needed.
6
Roles & Responsibilities
7
Business Manager
• The Business Manager's role is to review and approve the information system “Task
Package” based on needs and benefits:
• Business Managers must answer:
• Has the task package been validated by the right people?
• Is the task package adding value to the business solution?
8
Project Manager
• The Project Manager's role is to plan and monitor information system development
activities that will ensure the “Task Package” is delivered to users on-time and within
budget.
• Project Managers must answer:
• Have I assigned adequate resources to complete the task package?
• How much effort will it take to complete the task package?
• How am I doing according to the plan?
9
System Architect
• The System Architect's role is to produce information system solutions in terms of
quality “Task Packages.”
• System architects must answer:
• Is the proposed solution complete and usable?
• Is the proposed solution well-designed, properly documented and maintainable?
• Have the tradeoffs between owner, user and developer issues been made to
maximize the usefulness of the application within the constraints?
10
Decision Board
• This board consists of mostly senior managers as they are ultimately accountable for the
success of the information system.
• The board makes major decisions and provides required resources, as well as approves
any changes in direction. This includes the go/no-go decision and makes sure there is a
balance between key viewpoints of the system by reviewing the “status" of the
information system, but is not involved in the daily activities.
• Makes decisions.
• Resolves issues and conflicts.
• Approves tradeoffs.
• Ensures communications among all project participants.
11
Defining the Information System
• For every information systems project, you must ask questions.

• What information does the system need to provide?
• What hardware and software are required?
• Who needs to be trained to use this system?
• The challenge is knowing which questions you will ask then finding the
answers before starting the project.
12
Overview Of Information Systems
13
Business Needs
• The essential feature of an information system is how it improves the ability of an
organization to deliver products and services.
• The business benefits from a system that provides the organization with change
expressed through the system needs.
• Therefore, the business viewpoint requires careful consideration early in a project, as it
enables project managers to begin the cost/benefits evaluation of the change under
consideration, and to verify if its implementation is justified.
14
Solution Implementation
• An Information System is easier to manage when it is a size that can be

handled efficiently. When the scope of an Information System is large, it is
better to break it down into several smaller components for easier
management.
• One approach is to manage each phase as a small project. Another
approach is to divide the project scope into major components that have
separate task packages.
• A project structure must be set up to allow better coordination, planning
and communication among participants to ensure successful
implementation.
19
How Information System Project Starts
20
Information System Phases
1. Problem recognition.
2. Information gathering & analysis.
3. Requirements specification.
4. System architecture & design.
5. System construction & releases.
6. Review and maintenance.
21
Development Life Cycle
• To develop an Information System, organizations must follow a development process or
a step-by-step structure that guides the development called the Development Life cycle.
• There are several life cycle models, each describing approaches to a variety of tasks or
activities:
• The Waterfall Life Cycle
• The Spiral Life Cycle
• The Agile Development Cycle
22
The Waterfall Methodology - 1
Waterfall, which might be more properly called the “traditional”

approach, is a linear approach to software development. In this
methodology, the sequence of events is:
23
The Waterfall Methodology - 2
Advantages Disadvantages
Planning and designing more straightforward. Error can be fixed only during the phase
Suited for smaller projects where requirements It is not desirable for complex project where
are well defined requirement changes frequently
Project is completely dependent on project team Clients valuable feedback cannot be included
with minimum client intervention with ongoing development phase
Any changes in software is made during the Small changes or errors that arise in the
process of the development completed software may cause a lot of problems
Elaborate documentation is done at every phase Documentation occupies a lot of time of
of the software's development cycle developers and testers
24
The Agile Methodology - 1
• Agile is an iterative, team-based approach to development. This

approach emphasizes the rapid delivery of an application in
complete functional components.
• Rather than creating tasks and schedules, all time is “time-
boxed” into phases called “sprints.” Each sprint has a defined
duration (usually in weeks) with a running list of deliverables,
planned at the start of the sprint.
25
• Deliverables are prioritized by business value as determined by

the customer. If all planned work for the sprint cannot be
completed, work is reprioritized, and the information is used
for future sprint planning.
• As work is completed, it can be reviewed and evaluated by the
project team and customer, through daily builds and end-of-
sprint demos. Agile relies on a very high level of customer
involvement throughout the project, but especially during
these reviews.
26
Advantages Disadvantages
Customer-focused approach, resulting in Requires a high degree of customer involvement,
increased customer satisfaction which not all customers are comfortable with or
prefer to give.
Flexible in accepting changes It's more difficult to measure progress than it is
in Waterfall because progress happens across
several cycles
Empowers teams to manage projects Assumes every project team member is
completely dedicated, without which weakens
the principle of self-management.
Ideal for projects with non-fixed funding Need a long-term vision for the product and
actively work on communicating it
Promotes efficient communications Recommends co-location for efficient
communication, which is not always possible.
27
Implementation Methodologies
Several implementation methodologies exist:
• Direct cutover – new system is turned on and old system turned off
• Riskiest but least expensive – no need to support 2 systems
• Pilot implementation – a small group uses the new system
• Small impact on organization is something goes wrong – still have old system
running
• Parallel operation – all transactions are entered in new and old system
• Very expensive to maintain 2 systems
• Least risky that you can identify bugs and go back to old system if needed
• Phased implementation – new functions are implemented as parts of
old system are turned off
• Slowly move from old system to new one
28
System Development Decisions
• Every new development project should decide whether to
create it themselves using in-house personnel or buy one that
has already been developed
Development Decision Advantages Disadvantages
Purchasing • Less expensive • Same software may be
• Available more quickly used by competitors
• Tested already • Fewer/none
• Bugs worked out customizations
Building Yourself • Customized to your • More expensive

businesses’ needs • Not available quickly
• Would not be used by your • Requires testing and bugs
competitors to maintain being worked out
your competitive edge
29
Summary
• Defined the information system from three key viewpoints.

• Defined Information System Project Phases
• Explained the differences between Waterfall and Agile
methodologies.
30
Question – Lecture 9
1. What happens if one of the three viewpoints of an Information System
Project is missing?
2. Why would an organization consider building its own software application
if it is cheaper to buy one?
3. “You are working for a software company. Your manager assigns your team
to develop software for a very special customer. The customer is busy and
difficult to reach due to his global travel. The customer does not have time
to write all the requirements down but is willing to pay top money if your
team can complete the project with all functions working and on time. How
can you solve this problem? [Hint: which approach (life cycle model) will
make it easier for your project team to build the software that the customer
wants?]
31

L9_Information Systems Development

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

L9_Information Systems Development

Uploaded by

Copyright:

Available Formats

KHOA CÔNG NGHỆ THÔNG TIN

Lecture 9: Information Systems

Department of Information System

Upon successful completion of this lecture, you will be able to:

• For every information systems project, you must ask questions.

• An Information System is easier to manage when it is a size that can be

Waterfall, which might be more properly called the “traditional”

• Agile is an iterative, team-based approach to development. This

• Deliverables are prioritized by business value as determined by

Building Yourself • Customized to your • More expensive

• Defined the information system from three key viewpoints.

You might also like