Systems, Roles, and Development Methodologies
Systems, Roles, and Development Methodologies
Systems, Roles, and Development Methodologies
Kendall & Kendall Copyright 2014 Pearson Education, Inc. Publishing as Prentice Hall 1-2
InformationA Key Resource
Kendall & Kendall Copyright 2014 Pearson Education, Inc. Publishing as Prentice Hall 1-3
Major Topics
Kendall & Kendall Copyright 2014 Pearson Education, Inc. Publishing as Prentice Hall 1-6
Qualities of the Systems Analyst
Problem solver
Communicator
Strong personal and professional ethics
Self-disciplined and self-motivated
Kendall & Kendall Copyright 2014 Pearson Education, Inc. Publishing as Prentice Hall 1-7
Systems Development Life Cycle
(SDLC)
The systems development life cycle is a
phased approach to solving business
problems
Developed through the use of a specific
cycle of analyst and user activities
Each phase has unique user activities
Kendall & Kendall Copyright 2014 Pearson Education, Inc. Publishing as Prentice Hall 1-8
The Seven Phases of the Systems
Development Life Cycle (Figure 1.1)
Kendall & Kendall Copyright 2014 Pearson Education, Inc. Publishing as Prentice Hall 1-9
Incorporating Human-Computer
Interaction (HCI) Considerations
The demand for analysts who are
capable of incorporating HCI into the
systems development process keeps
increasing, as companies begin to
realize that the quality of systems and
the quality of work life can be improved
by taking a human-centered approach
at the outset of a project
Kendall & Kendall Copyright 2014 Pearson Education, Inc. Publishing as Prentice Hall 1-10
Identifying Problems,
Opportunities, and Objectives
Activity:
Interviewing user management
Summarizing the knowledge obtained
Estimating the scope of the project
Documenting the results
Kendall & Kendall Copyright 2014 Pearson Education, Inc. Publishing as Prentice Hall 1-11
Identifying Problems,
Opportunities, and Objectives
Output:
Feasibility report containing problem
definition and objective summaries from
which management can make a decision
on whether to proceed with the proposed
project
Kendall & Kendall Copyright 2014 Pearson Education, Inc. Publishing as Prentice Hall 1-12
Determining Human Information
Requirements
Activity:
Interviewing
Sampling and investing hard data
Questionnaires
Observe the decision makers behavior and
environment
Prototyping
Learn the who, what, where, when, how,
and why of the current system
Kendall & Kendall Copyright 2014 Pearson Education, Inc. Publishing as Prentice Hall 1-13
Determining Human Information
Requirements
Output:
The analyst understands how users accomplish
their work when interacting with a computer
Begin to know how to make the new system more
useful and usable
Know the business functions
Have complete information on the:
People
Goals
Data
Procedure involved
Kendall & Kendall Copyright 2014 Pearson Education, Inc. Publishing as Prentice Hall 1-14
Analyzing System Needs
Activity:
Create data flow, activity, or sequence
diagrams
Complete the data dictionary
Analyze the structured decisions made
Prepare and present the system proposal
Output:
Recommendation on what, if anything,
should be done
Kendall & Kendall Copyright 2014 Pearson Education, Inc. Publishing as Prentice Hall 1-15
Designing the Recommended
System
Activity:
Design procedures for data entry
Design the human-computer interface
Design system controls
Design database and/or files
Design backup procedures
Output
Model of the actual system
Kendall & Kendall Copyright 2014 Pearson Education, Inc. Publishing as Prentice Hall 1-16
Developing and Documenting
Software
Activity:
System analyst works with programmers to
develop any original software
Works with users to develop effective
documentation
Programmers design, code, and remove
syntactical errors from computer programs
Document software with help files, procedure
manuals, and Web sites with Frequently Asked
Questions
Kendall & Kendall Copyright 2014 Pearson Education, Inc. Publishing as Prentice Hall 1-17
Developing and Documenting
Software
Output:
Computer programs
System documentation
Kendall & Kendall Copyright 2014 Pearson Education, Inc. Publishing as Prentice Hall 1-18
Testing and Maintaining the
System
Activity:
Test the information system
System maintenance
Maintenance documentation
Output:
Problems, if any
Updated programs
Documentation
Kendall & Kendall Copyright 2014 Pearson Education, Inc. Publishing as Prentice Hall 1-19
Implementing and Evaluating the
System
Activity:
Train users
Analyst plans smooth conversion from old
system to new system
Review and evaluate system
Output:
Trained personnel
Installed system
Kendall & Kendall Copyright 2014 Pearson Education, Inc. Publishing as Prentice Hall 1-20
Some Researchers Estimate that the Amount of Time Spent
on Systems Maintenance May Be as Much as 60 Percent of
the Total Time Spent on Systems Projects (Figure 1.2)
Kendall & Kendall Copyright 2014 Pearson Education, Inc. Publishing as Prentice Hall 1-21
The Impact of Maintenance
Kendall & Kendall Copyright 2014 Pearson Education, Inc. Publishing as Prentice Hall 1-22
Resource Consumption over the
System Life (Figure 1.3)
Kendall & Kendall Copyright 2014 Pearson Education, Inc. Publishing as Prentice Hall 1-23
Approaches to Structured Analysis and Design
and to the Systems Development Life Cycle
Kendall & Kendall Copyright 2014 Pearson Education, Inc. Publishing as Prentice Hall 1-24
Case Tools
Kendall & Kendall Copyright 2014 Pearson Education, Inc. Publishing as Prentice Hall 1-25
Reasons for Using Case Tools
Kendall & Kendall Copyright 2014 Pearson Education, Inc. Publishing as Prentice Hall 1-26
Kendall & Kendall Copyright 2014 Pearson Education, Inc. Publishing as Prentice Hall 1-27
The Agile Approach
Based on:
Values
Principles
Core practices
Kendall & Kendall Copyright 2014 Pearson Education, Inc. Publishing as Prentice Hall 1-28
Agile Values
Communication
Simplicity
Feedback
Courage
Kendall & Kendall Copyright 2014 Pearson Education, Inc. Publishing as Prentice Hall 1-29
Four Agile Resources
Kendall & Kendall Copyright 2014 Pearson Education, Inc. Publishing as Prentice Hall 1-30
Five Stages of Agile Development
Exploration
Planning
Iterations to the first release
Productionizing
Maintenance
Kendall & Kendall Copyright 2014 Pearson Education, Inc. Publishing as Prentice Hall 1-31
Agile Project Development
Process (Figure 1.5)
Kendall & Kendall Copyright 2014 Pearson Education, Inc. Publishing as Prentice Hall 1-32
Object-Oriented (O-O) Systems
Analysis and Design
Kendall & Kendall Copyright 2014 Pearson Education, Inc. Publishing as Prentice Hall 1-33
Object-Oriented (O-O) Systems
Analysis and Design
Kendall & Kendall Copyright 2014 Pearson Education, Inc. Publishing as Prentice Hall 1-34
Unified Modeling Language (UML)
Phases
Define the use case model:
Use case diagram
Use case scenarios
Create UML diagrams
Develop class diagrams
Draw statechart diagrams
Modify the UML diagrams
Develop and document the system
Kendall & Kendall Copyright 2014 Pearson Education, Inc. Publishing as Prentice Hall 1-35
Kendall & Kendall Copyright 2014 Pearson Education, Inc. Publishing as Prentice Hall 1-36
Choosing a Method
Choose either:
SDLC
Agile
Object-oriented methodologies
Kendall & Kendall Copyright 2014 Pearson Education, Inc. Publishing as Prentice Hall 1-37
When to Use SDLC
Kendall & Kendall Copyright 2014 Pearson Education, Inc. Publishing as Prentice Hall 1-38
When to Use Agile
Kendall & Kendall Copyright 2014 Pearson Education, Inc. Publishing as Prentice Hall 1-39
When to Use Object-Oriented
Kendall & Kendall Copyright 2014 Pearson Education, Inc. Publishing as Prentice Hall 1-40
Open Source Software
Kendall & Kendall Copyright 2014 Pearson Education, Inc. Publishing as Prentice Hall 1-41
Four Types of Open Source
Communities:
Ad hoc
Standardized
Organized
Commercial
Kendall & Kendall Copyright 2014 Pearson Education, Inc. Publishing as Prentice Hall 1-42
Six Key Dimensions that Differentiate
Open Source Communities
General structure
Environment
Goals
Methods
User community
Licensing
Kendall & Kendall Copyright 2014 Pearson Education, Inc. Publishing as Prentice Hall 1-43
Reasons for Participating in Open
Source Communities
Rapidity with which new software can
be developed and tested
Faster to have a committed group of
experts develop, test, and debug code
This fosters creativity
Have many good minds work with
innovative applications
Kendall & Kendall Copyright 2014 Pearson Education, Inc. Publishing as Prentice Hall 1-44
Reasons for Participating in Open
Source Communities
Potential to reduce development costs
Bolster their self-image
Contribute something worthwhile to the
software development community
Kendall & Kendall Copyright 2014 Pearson Education, Inc. Publishing as Prentice Hall 1-45
Open Source Contribution and
Differentiation
Contributions to the open community
and differentiation from the open
community are for the following
reasons:
Cost
Managing resources
Time it takes to bring a new product to the
market
Kendall & Kendall Copyright 2014 Pearson Education, Inc. Publishing as Prentice Hall 1-46
Reasons for Analyst Participation
in the Open Source Community
Curiosity about software benefits
Achieve collective design
Incorporate open source software design
into:
Proprietary products
Processes
Knowledge
IT artifacts
Kendall & Kendall Copyright 2014 Pearson Education, Inc. Publishing as Prentice Hall 1-47
Collective Design
Kendall & Kendall Copyright 2014 Pearson Education, Inc. Publishing as Prentice Hall 1-48
Summary
Kendall & Kendall Copyright 2014 Pearson Education, Inc. Publishing as Prentice Hall 1-49
Copyright 2014 Pearson Education, Inc.
Publishing as Prentice Hall
Kendall & Kendall Copyright 2014 Pearson Education, Inc. Publishing as Prentice Hall 1-50