Hello san007-ga,
I’ve collected a long list of links to help you with reviewing the
traditional systems development strategies. This is usually called
Systems Development Life Cycle (SDLC) development. It’s seen as a
standardized step-by-step process. The number of steps and their
labels can vary slightly but the topics covered always include
conceptualization, planning, development, implementation and
maintenance. Through the years there have been many complaints about
the cumbersomeness of the process and newer methods have been
developed to improve it.
Many of the links I’ve collected come from college courses or seminars
and include excellent PowerPoint presentations that will help you
review the material quickly and should help you with putting together
your assignment. (I’m assuming that you’re working on an assignment
because of your urgent deadline.)
I went for volume on collecting links and I didn’t organize them. I’ve
included an excerpt from each site or a short description to help you
prioritize your explorations.
Good luck on completing your project on time.
czh
http://www.cems.uwe.ac.uk/~tdrewry/modeling.htm
System Development, Methodologies and Modeling
The Traditional Life Cycle
Methodologies
Modeling
Modeling Techniques
Data Flow Diagramming (DFDs)
Logical Data Structures (LDSs)
Entity Life Histories (ELHs)
See also:
System Development Lifecycles
Data Flow Diagrams (DFDs)
Procedure Definitions - low level DFDs
http://www2.bus.orst.edu/faculty/coakley/BA471_web/Lectures/W03_16_SDLC.ppt
Systems Development Life Cycle
PowerPoint Slides from Lecture
**** Long PowerPoint presentation with lots of examples and
illustrations. Covers historical perspective and recent developments.
http://www.imm.ecel.uwa.edu.au/unit450422/2002/2002%20Lecture%20Index.htm
Information Systems Planning and Development Strategies 422
***** Each heading in the outline has an associated set of Power Point
slides.
IS328 Web Course for Systems Analysis, Design and Implementation
Different approaches to systems development: Overview
System development was traditionally accomplished with two different
approaches: the process oriented approach and the data-oriented
approach. Recently with the emergence of object-oriented programming
languages, object-oriented analysis and design is becoming more and
more popular. With the advantages associated with managing
self-contained objects, it is likely that more systems will be
developed with the object-oriented approach in mind.
http://www.ben.light.btinternet.co.uk/papers/BIT99ERPAsSysDev.pdf
"A Departure from Traditional Systems Development Methodologies:
Enterprise Resource Planning (ERP) Systems and the Use of Process
Modelling Tools Manchester",
See page 4 -- A move away from traditional systems development
methodologies
According to the literature, there are three overlapping eras of
systems development. The first era is considered a technical systems
development approach typified by Yourdon and Constantine (Yourdon &
Constantine, 1978). The second era is characterized by Mumford
(Mumford, 1996) and Checkland (Checkland, 1981) and is essentially a
people/organization approach. The third era is characterized by Hammer
and Ward and Griffiths (Ward & Griffiths, 1996) and is essentially a
BPR/strategy approach. Both the second and third eras are considered
to be business focused systems development approaches but there are no
clear methods of implementation for either of these approaches.
Evidence from IT projects such as SNCF (Mitev, 1998), Baxter (Short&
Venkatramen, (1992) and Chrysler (Mukhopadhyay et al., 1995), and
conceptual thinking (McEachern and O'Keefe 1998; Morton 1991),
indicate that all of these approaches need to be considered during
systems implementation. The ERP approach purports to offer this
capability.
http://portal.acm.org/citation.cfm?id=333334.333372&coll=portal&dl=ACM
ABSTRACT
The development process of web-based systems has received little
attention in the academic literature. It is not clear whether the
traditional roles, methods and techniques currently used in
traditional systems analysis and design are still relevant in the
development of web-based systems. This research represents a case
study of a health care organization which developed two web-based
systems projects with different purposes, different development
processes and different roles for IS personnel. Within this single
organizational system the development of these two systems is explored
and rationale for the differing roles of the IS personnel are
suggested. Although both systems discussed are web-based systems, the
role of the IS personnel, the impact on the IS department
responsibilities and the participation of users are different.
http://isds.bus.lsu.edu/cvoc/learn/bpr/cprojects/spring1998/erp/index.html
Project Overview
The focus of the ERP Implementation Methodologies and Strategies
project was the study of the traditional Systems Life Cycle
methodology and Enterprise Resource Planning (ERP) methodologies and
their application in systems development and reengineering.
http://isds.bus.lsu.edu/cvoc/learn/bpr/cprojects/spring1998/erp/page1.html
Systems Life Cycle
The traditional Systems Life Cycle is the oldest method for building
information systems. This methodology assumes that an information
system has a life cycle similar to that of any living organism, with a
BEGINNING > MIDDLE > END.
The Systems Life Cycle methodology has six stages. It partitions the
system development process into distinct stages and develops an
information system sequentially, stage by stage. The six stages and a
detail definition of each are as follows:
http://www.dulcian.com/BRIM%20Documents/BRIM%20Systems%20Development%20Life%20Cycle.htm
BRIM™ Systems Development Life Cycle
BRIMÔ provides a technological foundation that should fundamentally
change the way in which you build systems. There is nothing to prevent
you from using the traditional Software Development Life Cycle (SDLC);
however, building systems in this way will not take full advantage of
what BRIMÔ has to offer in terms of rapid designing, building and
testing capabilities.
http://www.geocities.com/tokyo/6868/980823/isr-s-schf.html
IS DEVELOPMENT AND OPERATIONS
***** Outline of all steps in the process
http://www.cis.gsu.edu/~dstraub/JMBA/MBA8473/2001/sdlc4ups.pdf
Systems Development Life-cycle and Prototyping
***** 50+ Power Point slide presentation
http://cba.fiu.edu/dsis/noguera/ch04_SP034.ppt
Modern Systems Analysis and Design Joey F. George Jeffrey A. ...
http://www.usdoj.gov/jmd/irm/lifecycle/table.htm
The Department of Justice Systems Development Life Cycle Guidance
Document
http://www.usdoj.gov/jmd/irm/lifecycle/intro.htm
Executive Summary -- The Systems Development Life Cycle
Systems Development Life Cycle (SDLC) emphasizes decision processes
that influence system cost and usefulness. These decisions must be
based on full consideration of business processes, functional
requirements, and economic and technical feasibility in order to
produce an effective system. The primary objectives of any SDLC are to
deliver quality systems that: 1) meet or exceed customer expectations
when promised and within cost estimates, 2) work effectively and
efficiently within the current and planned information technology
infrastructure, and 3) are inexpensive to maintain and cost-effective
to enhance. This SDLC establishes a logical order of events for
conducting system development that is controlled, measured,
documented, and ultimately improved.
http://armonia.di.uoa.gr/curriculum/lecture%206.ppt
Systems Development Methods
***** 18-page Power Point presentation
http://www.dbm.state.md.us/mdplan/apdx-a.htm
Appendix A --
Structured Systems Development Life-Cycle Methodology
***** Click on each heading to get fuller explanation
The five basic phases of Systems Development Life-Cycle methodologies
include:
A. Conceptual Design Phase -- During the conceptual design phase,
agency management identifies the need for a system, and develops a
high level project plan.
B. Planning Phase -- During the planning phase, system developers and
users determine functional, quality, and architecture requirements of
the system identified in the conceptual design phase, design the
system to meet those requirements, and plan for development and
implementation.
C. Development Phase -- During the development phase, system
developers code and test the system designed in the planning phase,
and prepare for training and implementation.
D. Implementation Phase -- During the implementation phase, users
learn and test the system to ensure it meets their requirements. If
the users accept the system, systems developers install and convert to
the new system.
E. Post Implementation/System Support Phase -- During the post
implementation/system support phase, management, users, and systems
developers continuously monitor the implemented system to ensure it
measures up to the expectations and requirements developed in previous
phases, and to enhance the system as needed to increase the system's
useful life.
http://www.johnsaunders.com/umuc641/641les04.htm
Lesson 4 - Traditional Life Cycle Development and Alternate Approaches
The Traditional Life Cycle
Whatever methodology you selected, you would likely find four common
threads - analysis, design, "programming", and implementation.
Programming here may be loosely interpreted to include packaged
software and even outsourcing, which will be addressed shortly.
*****Includes examples and bibliography
http://highered.mcgraw-hill.com/sites/0072458720/student_view0/chapter7/glossary.html
DEVELOPING IT SYSTEMS
http://www.informationweek.com/shared/printArticle?article=infoweek/800/metho2.htm&pub=iwk
Methodologies Vary According To The Project
ifferent methodologies address traditional systems development,
object-oriented development, and Web development. A methodology in
general is a set of steps designed to guide the development process
from the beginning of a project to production turnover and
maintenance.
http://www.credata.com/research/jad.html
Development Methodology -
Joint Application Development (JAD)
Joint Application Development, or JAD, is a process originally
developed for designing a computer-based system. It brings together
business area people (users) and IT (Information Technology)
professionals in a highly focused workshop. The advantages of JAD
include a dramatic shortening of the time it takes to complete a
project. It also improves the quality of the final product by focusing
on the up-front portion of the development lifecycle, thus reducing
the likelihood of errors that are expensive to correct later on.
http://www.churchillsys.com/WP1-EXSY.html
WHITE PAPER #1
Expert Systems Technology
6. How does the Expert Systems life cycle differ from the traditional
systems development life cycle?
As discussed in the previous question, the requirements and behavior
of an Expert System are extremely difficult to state in advance during
formal analysis and design stages. Instead, the knowledge captured by
the Expert System increases in depth and scope over time through the
knowledge engineering process. Rapid prototyping enables the Expert
System to develop incrementally in the same manner that knowledge is
obtained incrementally. Each prototype facilitates additional
analysis, design and verification. Because of the overlap between
these activities, the knowledge engineer is involved in virtually all
phases of the Expert Systems life cycle, not just analysis.
http://generalupdate.rau.ac.za/infosci/conf/Wednesday/Jakovljevic.htm
TECHNOLOGICAL STAGES IN THE SYSTEM DEVELOPMENT LIFE CYCLE: AN
APPLICATION TO WEB PAGE DESIGN
Abstract
The purpose of this paper is to explore the application of the
methodology of instructional program development based on
technological stages in information system design. The growth of use
of mind tools has put thinking skills in the focus of teaching
practice but there is still a need for the innovation of more
effective instructional strategies. This has re-emphasised the
importance of developing an instructional program with the innovative
structure of technological stages. Some of criteria used to set up
the program emerged from research literature on complex thinking, mind
tools, learning theories and instructional strategies.
This paper argues that it is now time to place more emphasis on
in-depth research on the technological stages and their implications
for information system design. In much the same way that Technology
Education needs information systems, it is also imperative that
information systems include the study of technological problem-solving
and its stages. A convergence of disciplines is necessary, if the
field of information systems is to be examined in its widest
dimensions.
http://intranetjournal.com/articles/200201/lc_01_23_02a.html
Intranet Talk
The System Life Cycle and Intranets
As most experts would see it, the systems life cycle falls into the
following phases:
1. Initiation or Inception
2. Analysis and Requirements Definition
3. Design
4. Construction
5. Installation or Deployment
6. Maintenance
http://www.acm.org/sigchi/chi96/proceedings/doctoral/Sulaiman/ss_txt.htm
Usability and The Software Production Life Cycle
ABSTRACT
For many types of systems it is as important that the usability is as
good as the functionality. There have been various attempts during the
last fifteen years or more to encourage developers to focus on
usability during the life cycle. These have had only limited success
in that they have affected certain companies without fundamentally
changing the overall software development process. The aim of this
study is to improve software quality by finding ways to integrate
usability with software quality measurements throughout the life cycle
and especially at early stages of development.
http://www.spacewx.com/Research_to_Ops.html
A Tailored System Development Lifecycle
Overview
The “Capability Maturity Model”* is the standard for defining an
organizations software process maturity, including how an organization
defines the software engineering process and systems development life
cycle (SDLC)
Traditional definitions of the SDLC - largely based on business models
- need to be modified to specifically address scientific models and
operations in space-weather
The Research-to-Operations System Development Lifecycle described here
is specifically for Space-Weather applications, and is primarily based
on the experience of recent implementations of two solar-terrestrial
models at the NOAA Space Environment Center, and one satellite drag
model at the Air Force Space Command
In these and other cases, experience has shown there has been a
dramatic under-estimation of the value of best engineering practices,
requirements scope, and total costs of the transitioning process by
the research community
***** Includes illustrations
http://www.starlab.vub.ac.be/staff/robert/Information%20Systems/Hoffer%202nd%20ed/chapter04.pdf
Modern Systems Analysis and Design
***** 32-page PowerPoint presentation
http://www.isaca.org/standard/guide30.htm
Review of System Development Life Cycle (SDLC)
http://edtech.it.bton.ac.uk/esystems/modules/fd141/thedesignprocess/lifecyclesmainresource.htm
FD141 Remote Access Databases
Week 2: Introduction to the design process
More recent system development Approaches
The perception of systems development has suffered greatly under the
reputation that projects are always completed late and over budget and
do not always do what the user want. Although this is not always the
case, where these problems occur, underlying reasons are often poor
analysis of the original scope of the problem, lack of user
involvement and the desire to accomplish too much in unrealistic time.
Because of these continual problems, new techniques that do not follow
the traditional systems development life cycle but follow their own
sequence of phases and tasks. Two of the more notable approaches are
Rapid Application Development
Spiral approach
http://web.uccs.edu/ahickey/INFS330/Ch03a.ppt
Approaches to Systems Development
***** 30-page PowerPoint presentation
http://acct.tamu.edu/smith/books/aisbook/aisch11.ppt
Systems Development Overview
**** 20+ page PowerPoint presentation. Includes historical
perspective, trends and examples
http://sws.pcc.edu/student/CIS244_gjenewei_12449/matthewfarrenkopf92/projects/sdlc.html
THE SYSTEMS DEVELOPMENT LIFE CYCLE
Its History and Its Purpose
SEARCH STRATEGY
traditional "systems development life cycle"
traditional "systems development” strategies |
,
0 Comments
)