Professional Documents
Culture Documents
Systems
Group Members
M. Amir Mushtaq
Ex-MBA-Fall-12-058
Ayesha Asif
MBA-Spring-13-02
Mehroz Arshad
EMBA-Fall-12-008
M. Zeeshan Munir
EMBA-Fall-12-019
Khurram Minhas
EMBA-Fall -09-022
M. Imran
EMBA-Fall -09-036
2
M. Amir Mushtaq
Contents
Concept of a systems development life cycle (SDLC).
Compare and contrast prototyping, rapid application development
(RAD), joint application design (JAD), and traditional SDLC
approaches to systems development.
Advantages and disadvantages of object-oriented (OO)
development.
Contents (cont.)
Evaluate alternatives to in-house systems development.
Major strategies, methods, and tools for building e-commerce
applications.
Advantages and disadvantages of CASE tools.
Alternative approaches to software process quality improvement.
An Eight-Stage SDLC
Stages 1 & 2
Stage 1: Project Initiation
Stage 2: Systems Analysis & Feasibility Studies
Systems Analysis - the investigation of the existing situation.
Feasibility Studies - the major areas of feasibility investigation are;
Technology
Economics
Organizational factors
Legal, ethical, and other constraints
Stages 3 & 4
Stage 3: Logical Analysis and Design
Systems analysts determine 2 major aspects of the system:
(1) what it needs to do
(2) how it will accomplish these functions.
Stages 5 & 6
Stage 5: Implementation
Approaches to conversion from a previous system include:
Parallel conversion
Direct cutover
Pilot conversion
Phased (or modular) conversion
Stage 6: Operation
After a successful conversion, the system will operate for an
indefinite period of time.
10
Stages 7 & 8
Stage 7: Post-audit Evaluation
An organization should evaluate all its larger system projects
after their completion.
These post-audits introduce an additional element of
discipline into the development process.
Stage 8: Maintenance
Every system needs two kinds of maintenance:
Fixing bugs
Updating systems to accommodate changes in the
environment
11
Ayesha Asif
12
Implementing SDLCs
IS groups considering the implementation of a formal SDLC
methodology should look for the following characteristics:
Minimal overhead
Flexibility and responsiveness
Concurrent tasks
Focused analysis
13
Prototyping
Joint application design
Rapid application
development
Object-oriented
development
14
Prototyping
Instead of spending a lot of time producing very detailed
specifications, the developers find out only what the users want.
Developers quickly create a prototype.
This contains portions of the system of most interest to the users,
or is a small-scale working model of the entire system.
Construction Phase
Cutover Phase
17
18
Mehroze Arshad
19
Object-Oriented Development
An object-oriented (OO) system begins not with the task to be
performed, but with the aspects of the real world that must be modeled
to perform that task.
Object technology enables the development of purchasable, sharable,
and reusable information assets (objects) existing in a worldwide
network of interorganizational information systems.
The techniques and notations that are incorporated into a standard
object-oriented language are called unified modeling language or UML.
The object-oriented approach is ideal for developing Web applications.
20
Component-based Development
Components are self-contained packages of functionality that have
clearly defined, open interfaces with high-level application services.
E.g., interface icons (small), online ordering (a business component)
22
Increasingly powerful
desktop hardware
Declining hardware costs
Increasingly diverse
software capabilities
Backlog of IS projects
Development speed
Business orientation
Small applications
Control
Apparent cost savings
23
Outsourcing
Firms that provide outsourcing
cite numerous benefits:
Staffing
Lack of business expertise
Contract problems
Internal cost reduction
opportunities
24
Khurram Minhas
25
On-time
On-budget
Full functionality
User acceptance
Favorable costs-to-benefits ratio
Low maintenance
Scalability
Integration with other systems
Minimal negative cross-impacts
Reusability
27
Managerial Considerations
The traditional SDLC approach often works well for large projects with
well-defined requirements, where there is not a lot of time pressure.
Prototyping requires effective management to make sure that the
iterations of prototyping do not continue indefinitely.
RAD may be less appropriate than conventional programming
languages for larger projects, or those with a lot of real-time
processing.
JAD is easy for senior management to understand, yet it is difficult and
expensive to get all people in the same place at the same time.
28
30
31
Zeshan Munir
32
35
Benefit
Potential Risk
Business
Technical
Economic
37
Support services
Scope of service
Integration
38
M. Imran
39
Java applets.
40
CASE Tools
Computer-aided software engineering (CASE) tools are
marketed as individual items or in a set (toolkit) that automates
various aspects of the development process.
CASE can be used in two different ways:
To automate certain SDLC activities on a piecemeal basis.
To provide an integrated (I-CASE) package for IS groups.
41
Software Quality
The ISO allows organizations to use any SDLC that includes the following:
Contract review
Purchasers requirements
specification
Acceptance
Development planning
Quality planning
Maintenance
42
Project Planning
Project planning provides an
overall framework with which
the systems development life
cycle can be planned,
scheduled, and controlled.
Milestones, or checkpoints,
are established to allow a
periodic review of progress.
43
Predefined structure
Stability of technology
Size
User proficiency
Developer proficiency
44
Managerial Issues
Importance. Functional managers
must participate in the development
process and should understand all
the phases.
45
Behavior problems.
Perpetual development.
46
THANKYOU
47