1. Chapter 1 The Systems Development Environment
Modern Systems Analysis and Design Sixth Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich
Chapter 1
The Systems Development Environment

2. Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall
Learning Objectives
Introduction
Define the usage of information systems analysis and design.
Describe the information Systems Development Life Cycle (SDLC).
Explain Rapid Application Development (RAD), prototyping, Computer Aided Software Engineering (CASE), and Service-Oriented Architecture (SOA).
Describe agile methodologies and eXtreme programming.
Explain Object Oriented Analysis and Design and the Rational Unified Process (RUP).
Chapter 1
Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall

3. Data, Information, and Knowledge
Introduction
Data, Information, and Knowledge
Data: raw facts
Information: collection of facts organized in such a way that they have value beyond(وراء) the facts themselves.
Knowledge: awareness(الوعي والمعرفة) and understanding of a set of information and ways that information can be made useful to support a specific task or reach a decision

4. Figure : The Process of Transforming Data into Information
Data, Information, and Knowledge (continued)
Figure : The Process of Transforming Data into Information

5. System Concepts System Components of a system
A set of elements or components that interact to accomplish goals
Components of a system
Input
Processing
Output
Feedback

6. Input, Processing, Output, Feedback
Input: activity of gathering and capturing raw data
Processing: converting or transforming data into useful outputs
Output: production of useful information, usually in the form of documents and reports
Feedback: output that is used to make changes to input or processing activities

8. System Concepts (continued)
Components of a System

9. What Is An Information System?
The Components of an Information System

10. Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall
An Information System
A set of interrelated components that collect, manipulate, and disseminate(نشر) data and information, and provide feedback to meet an objective.
System users, business managers, and information systems professionals must work together to build a successful information system.
Example: A payroll system, for example, collects information on employees and their work, processes and stores that information, and then produces paychecks and payroll reports for the organization.
4/16/2017Chapter 1
Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall

11. Computer-based information system (CBIS)
Computer-based Information System (CBIS): An information system that uses computer technology to perform some or all of its intended(مقصودة) tasks.
Examples: Airline reservation systems;

12. Systems analysis and design
Systems analysis and design – the process of planning, analysis, designing, building, and maintaining information systems
4/16/2017Chapter 1
Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall

13. Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall
Information Systems Analysis and Design
Complex organizational process
Used to develop and maintain computer-based information systems
Used by a team of business and systems professionals
Chapter 1
Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall

14. Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall
Introduction (Cont.)
FIGURE 1-1 An organizational approach to systems analysis and
design is driven by methodologies(Phases), techniques(Method), and tools (ex. UML)
Chapter 1
Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall

15. A Modern Approach to Systems Analysis and Design
1950s: focus on efficient(كفاءة) automation of existing processes
1960s: advent of 3GL, faster and more reliable(وثوقية واعتمادية) computers
1970s: system development becomes more like an engineering discipline(انضباط)
Chapter 1
Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall

16. A Modern Approach to Systems Analysis and Design (Cont.)
1980s: major breakthrough with 4GL, CASE tools, object oriented methods
1990s: focus on system integration, GUI (Graphical User Interface (applications, client/server platforms, Internet
The new century: Web application development, wireless PDAs (personal data assistant) , component-based applications
Chapter 1
Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall

17. A Modern Approach to Systems Analysis and Design (Cont.)
Application Software
Computer software designed to support organizational functions or processes
Systems Analyst
Organizational role most responsible for analysis and design of information systems
Chapter 1
Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall

18. Developing Information Systems
System Development Methodology is a standard process followed in an organization to conduct all the steps necessary to analyze, design, implement, and maintain information systems.
Chapter 1
Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall

19. System Development Life Cycle
Traditional methodology used to develop, maintain, and replace information systems.
Planning
Analysis
Design
Implementation
Maintenance

20. SDLC ’s Phases
PLANNING
MAINTENANCE
ANALYSIS
IMPLEMENTATION
DESIGN

21. Systems Development Life Cycle(SDLC)(Cont.)
Planning –
an organization’s total information system needs are identified, analyzed, prioritized, and arranged.
Phase of planning:
User request
Feasibility study
Project Plan
Project Proposal
Chapter 1
Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall

22. Systems Development Life Cycle (SDLC)(Cont.)
Analysis
The first is requirements determination which the system analyst work with users to determine what the users want from the proposed system.
Next the system analyst study the requirements and structure them according to their interrelationships.
Then system analyst generate alternative initial design to match the requirements.
Analysis – system requirements are studied and structured.

23. Systems Development Life Cycle(SDLC) (Cont.)
System Design
The description of the recommended alternative solutions is converted into logical and then physical system specification.
You must design all aspects of the system from input and output screens to reports, database, and computer processes.

24. Systems Development Life Cycle (SDLC) (Cont.)
Logical design – all functional features of the system chosen for development in analysis are described independently of any computer platform
Functional, detailed specifications of all system elements (data, processes, input, outputs)
4/16/2017Chapter 1
Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall

25. Systems Development Life Cycle (SDLC) (Cont.)
Physical design – the logical specifications of the system from logical design are transformed into the technology-specific details from which all programming and system construction can be accomplished(إنجاز)
Technical, detailed specifications of all system elements (programs, files, network, system software).
Chapter 1
Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall

26. Systems Development Life Cycle (SDLC) (Cont.)
Implementation
Detailed model or detailed written specifications are turned to programmer as the first part of implementation phase.
Implementation includes coding, testing, and installation.
Coding: programmers write the programs that make up the system.
Testing: programmers and analysts test individual programs and the entire system in order to find and correct the errors.
Installation: the new system becomes a part of the daily activities of the organization. .

27. Systems Development Life Cycle (SDLC) (Cont.)
Maintenance
An information system is systematically repaired and improved.
When a system is operate in organization, users sometimes find problems with how it works and often think of better ways to perform its functions.
Programmers make the changes that users ask for and modify the system to reflect changing business condition.
So the final phase of SDLC improve information system.

28. Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall
Chapter 1
Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall

29. The Heart of the Systems Development Process
FIGURE 1-7
The analysis–design–code–test loop
Current practice combines analysis, design, and implementation into a single iterative and parallel process of activities.
Chapter 1
Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall

30. Traditional Waterfall SDLC
One phase begins when another completes, with little backtracking and looping.
FIGURE 1-9
A traditional waterfall SDLC
Chapter 1
Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall

31. Problems with Waterfall Approach
System requirements “locked in” after being determined (can't change)
Limited user involvement (only in requirements phase)
Most errors discovered in last phases, so to correct these errors it will take many (time, money, efforts). Also the system it me be damage and not give the require output.
Chapter 1
Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall

32. Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall
spiral model
4/16/2017Chapter 1
Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall

33. Different Approaches to Improving Development
CASE Tools
Rapid Application Development (RAD)
Joint Application Design(JAD)
Agile Methodologies
eXtreme Programming
Chapter 1
Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall

34. Computer-Aided Software Engineering (CASE) Tools
Diagramming tools enable graphical representation.
Computer displays and report generators help prototype how systems “look and feel”.
Analysis tools automatically check for consistency in diagrams, forms, and reports.
Chapter 1
Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall

35. Computer-Aided Software Engineering (CASE) Tools (Cont.)
A central repository provides integrated storage of diagrams, reports, and project management specifications.
Code generators enable automatic generation of programs and database code directly from design documents, diagrams, forms, and reports.
Chapter 1
Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall

36. Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall
CASE Tools (Cont.)
FIGURE 1-10
A class diagram from IBM’s Rational Rose
(Source: IBM)
Chapter 1
Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall

37. Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall
CASE Tools (Cont.)
Chapter 1
Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall

38. Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall
Prototyping
Building a scaled-down working version of the
system
Advantages:
Users are involved in design
Captures requirements in concrete form
4/16/2017Chapter 1
Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall

39. Rapid Application Development (RAD)
Rapid Application Development (RAD) refers to a type of software development methodology that uses minimal planning in favor of rapid prototyping.
Methodology to radically decrease design and implementation time
Involves: extensive user involvement, prototyping, JAD sessions, integrated CASE tools, and code generators
Chapter 1
Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall

40. Rapid Application Development (RAD) (Cont.)
FIGURE 1-11
RAD life cycle
Chapter 1
Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall

41. Joint Application Design (JAD)
Structured process involving users, analysts, and managers.
Several-day intensive workgroup sessions.
Purpose: to specify or review system requirements.
4/16/2017Chapter 1
Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall

42. Service-Oriented Architecture (SOA)
An approach to systems development based on building complete systems through assembling software components, each of which model generic business functions
Chapter 1
Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall

43. Service-Oriented Architecture (SOA) (Cont.)
FIGURE 1-12
Illustration of a service, a credit check,
used by applications and other services
Chapter 1
Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall

44. Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall
Agile Methodologies
Three key principles
Adaptive(التكيف) rather than predictive(التنبؤية)
Emphasize people rather than roles
Self-adaptive processes
Chapter 1
Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall

45. When to use Agile Methodologies
If your project involves:
Unpredictable or dynamic requirements
Responsible and motivated(دوافع) developers
Customers who understand the process and will get involved
Chapter 1
Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall

46. Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall
eXtreme Programming
Short, incremental development cycles
Automated tests
Two-person programming teams
(Test-driven development and Pair programming)
Chapter 1
Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall

47. eXtreme Programming (Cont.)
Coding and testing operate together
Advantages:
Communication between developers
High level of productivity
High-quality code
Chapter 1
Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall

48. Object-Oriented Analysis and Design (OOAD)
Based on objects rather than data or processes
Object: a structure encapsulating attributes and behaviors of a real-world entity
Chapter 1
Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall

49. Object-Oriented Analysis and Design (OOAD) (Cont.)
Object class: a logical grouping of objects sharing the same attributes and behaviors
Inheritance: hierarchical arrangement of classes enable subclasses to inherit properties of superclasses
Chapter 1
Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall

50. Object-Oriented Analysis and Design (OOAD) (Cont.)
4/16/2017Chapter 1
Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall

51. Rational Unified Process (RUP)
An object-oriented systems development methodology
RUP establishes four phase of development: inception, elaboration, construction, and transition.
Each phase is organized into a number of separate iterations.
Chapter 1
Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall

52. Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall
التوقيتات النمطية للمشروع. كم يجب أن يستغرق كل طور من الأطوار الأربعة؟ يتباين ذلك من مشروع لآخر، و لكن كمؤشّر عام 10% للاستهلال، 30% للتفصيل، 50% للبناء و 10% للانتقال.
التوقيتات المحتملة لكل طور. هذا المثال يوضح طول كل طور لمشروع يستغرق سنتين.
4/16/2017Chapter 1
Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall

53. Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall
FIGURE 1-13
Phases of OOSAD-based development
Chapter 1
Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall

54. Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall
Summary
In this chapter you learned how to:
Define information systems analysis and design.
Describe the information Systems Development Life Cycle (SDLC).
Explain Rapid Application Development (RAD), prototyping, Computer Aided Software Engineering (CASE), and Service-Oriented Architecture (SOA).
Describe agile methodologies and eXtreme programming.
Explain Object Oriented Analysis and Design and the Rational Unified Process (RUP).
Chapter 1
Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall