BDT T4

1
OM
IS

Building Software to Support
WE ARE
BUSINESS
an Agile Organization
Business Driver Technology
2
"Golden Triangle" of System Development
SystemResources(People )
SystemRequirements
Time
3
Systems Development Life Cycle (SDLC)
What is a Systems Development Life Cycle?
What are some of the phases in SDLC?
What are advantages and disadvantages of this
approach?
4
Systems Development Life Cycle (SDLC)
Systems Development Life Cycle (SDLC)
the overall process for developing information
systems from planning and analysis through
implementation and maintenance
1. Planning
involves establishing a high level plan of the
intended project and determining project goals
2. Analysis
involves analyzing end-user business requirements
and refining project goals into defined functions
and operations of the intended system
Business Requirements
the detailed set of business requests that the
system mustmeet in order to be successful
5
Systems Development Life Cycle (SDLC)
3. Design
involves describing the desired features and
operations of the system including screen
layouts, business rules, process diagrams, pseudo
code, and other documentation
4. Development
involves taking all of the detailed documents
from the design phase and transforming them into
the actual system
5. Testing
involves bringing all the project pieces together
into a special testing environment to test for
errors, bugs, and interoperability and verify
that the system meets all of the business
requirements defined in the analysis phase
6. Implementation
involves placing the system into production so
users canbegin to perform actual business
operations with the system
6
Systems Development Life Cycle (SDLC)
7. Maintenance
involves performing changes, corrections,
additions, andupgrades to ensure the system
continues to meet business goals
PROCESS
7
Systems Development Life Cycle (SDLC)
Methodology Advantages
1. Milestones and deliverables at the end of each
phase
2. Highly structured and process-oriented approach
3. Methodical approach leads to quality system
4. Approach most appropriate for - large and
high cost projects - high risk projects
involving complicated requirements - projects
involving many stakeholders - projects that must
result in high quality system
Methodology Disadvantages
1. Ties up organizational resources for a long
period of time
2. Business priorities may change before project
is completed
3. Hard to change project requirements during the
process
8
Rapid Application Development (RAD)
What is a Rapid Application Development?
What are some characteristics of RAD?
What are advantages and disadvantages of this
approach?
9
Rapid Application Development (RAD)
Rapid Application Development
emphasizes extensive user involvement in the
rapid and evolutionary construction of working
prototypes of a system to accelerate the systems
development process
APPROACH CHARACTERISTICS
1. Proof on Concept approach is often used when
user is unsure of the requirements for the
systems (prototype) or the organization is
unsure whether is it even possible to build the
system.
2. Team Formed both users and IS support are
placed in a separate RAD room to quickly
develop the system.
3. Heavily Interactive the approach is heavily
interactive where the users quickly developed
system specifications IS builds the system
using the specs and gives it to the user users
provide immediate feedback gt the process
starts over
10
Rapid Application Development (RAD)
Methodology Advantages
1. Strong user support and commitment
2. Quick development of prototype system
3. Loss resource use both people and time
4. Approach most appropriate for - proof of
concept or prototypes - smaller projects with
focused requirements - projects involving few
stakeholders
Methodology Disadvantages
1. Limited documentation due to speed
2. Projects results in only a prototype a
non-working system
3. Repetitive process makes it difficult to
determine when to end the prototype
development process
4. Users may want to use the prototype without
waiting for completion of a fully functional
system
11
Agile Systems Development (ASD)
What is Agile Systems Development?
What are some characteristics of ASD?
What are advantages and disadvantages of this
approach?
12
Agile Systems Development (ASD)
Agile Systems Development
system designed to provide a high level of
customer service by early and continuous delivery
of useful software components
APPROACH CHARACTERISTICS
1. User Leadership project team headed up by
business user responsible for the successful
completion of the project
2. Essential Requirements projects are only
given enough resources to build a system
using ONLY the users essential systems needs
3. Small Project Teams the project team is only
comprised of a small number of key business
stakeholders to reduce the system review and
approval process
4. Continuous Project Triage projects are
continually reviewed by top management to
ensure that are showing value. Projects that
do not show value are killed their funding
is taken away.
13
Agile Systems Development (ASD)
Methodology Advantages
1. Increased velocity of systems development
2. Quicker start to end construction time
3. High user commitment project headed by user
4. Project triage ensures firm resources at not
wasted on projects
5. Approach most appropriate for - medium size
projects with limited of stakeholders - medium
projects with clear project requirements - time
sensitive projects
Methodology Disadvantages
1. Approach does not support complex and large
projects
2. User project leader may be inexperienced
3. Process may kill a project that may eventually
have showed business value
14
Why Do IT Projects Fail?
What are the common reasons whyIT projects Fail?
15
Common Reason Why IT Projects Fail
16
Any Questions?