ACM 213 Information Analysis

1
ACM 213 Information Analysis System Design

• Assist. Prof. Fazli Yildirim
• fazli.yildirim_at_okan.edu.tr
• www.fazliyildirim.com
• BookSystems Analysis and Design with
• UML Version 2.0 -An Object-Oriented Approach
• Second Edition - Alan Dennis - Barbara Haley
  Wixom - David Tegarden

2
ACM 213 Information Analysis System Design

• What is Software Engineering?
• Software Engineering is the systematic approach
  to the development, operation and maintenance of
  software.
• Software Engineering is concerned with
  development and maintenance of software products.
• The primary goal of software engineering is to
  provide the quality of software with low cost.
• Software Engineering involves project planning,
  project management, systematic analysis, design,
  validations and maintenance activities.

3
Contents

• 1. Introduction to Systems - Introduces the
  concept of systems and explains what an
  information system is.
• Various types of information systems and their
  relevance to the functioning of any organization.
  
• 2. Software (System) Development Life Cycle
  Models - Explains various activities involved in
  the development of software systems. It presents
  the different approaches towards software
  development. In this chapter, Waterfall Model,
  Prototype Model, Dynamic System Development
  Model, and Object Oriented models are discussed.
• 3. Preliminary Analysis - covers various
  activities that are performed during the
  preliminary analysis of the system development.
  It shows how the feasibility study for the system
  to be developed is done.
• 4. Fact Finding and Decision Making Techniques -
  shows the various techniques used for fact
  finding during the analysis of the system. In
  this, interviews, questionnaires, on site
  observation, and record reviews are presented.
  Also, discusses the decision-making and
  documentation techniques. For this Decision
  Tables, Decision Tress, Structured English and
  Data Dictionary is presented.

4
Contents

• 5. Functional Modeling I - presents the various
  concepts of system design. Design elements like
  input-output to the system, processes involved in
  the system and the database elements of the
  system are discussed. It also discusses Data Flow
  Diagrams that are used to represent the
  functionality of the system.
• 6. Functional Modeling II - introduces the
  modular programming concept to the software
  development. It explains the structure charts
  that represent the modular structure of various
  modules of the software being developed. Concepts
  like Cohesion and Coupling that further enhance
  the users understanding of modular designing are
  also presented.
• 7. Data Modeling Techniques - presents the
  concepts involve in the data modeling phase of
  system development where the storage of data and
  the storage form is discussed. Here Entity
  Relationship model along with Entity Relationship
  Diagrams is used to illustrate the data modeling
  concepts. are discussed.
• 8. Relational Data Modeling and Object Oriented
  Data Modeling Techniques - Here two other data
  models, Relational and Object Oriented Models are
  discussed. Comparison of the two models is also
  presented.
• 9. Testing and Quality Assurance - covers the
  various testing techniques and strategies
  employed during the development of the system.
  Also various quality assurance activities for
  software development are presented.

5
System?

• The term system originates from the Greek term
  systema, which means to place together.
• System An integrated set of interoperable
  elements, each with explicitly specified and
  bounded capabilities, working synergistically to
  perform value-added processing to enable a User
  to satisfy mission-oriented operational needs in
  a prescribed operating environment with a
  specified outcome and probability of success.
• By an integrated set, we mean that a system, by
  definition, is composed of hierarchical levels of
  physical elements, entities, or components.
• By interoperable elements, we mean that
  elements within the systems structure must be
  compatible with each other in form, fit, and
  function, for example. System elements include
  equipment (e.g., hardware and system, system,
  facilities, operating constraints, support),
  maintenance, supplies, spares, training,
  resources, procedural data, external systems, and
  anything else that supports mission
  accomplishment

6
System?

• By each element having explicitly specified and
  bounded capabilities,. Elements should be
  analyzed, designed, developed, tested, verified,
  and validatedeither on a stand-alone basis or as
  part of the integrated system.
• By working in synergistically, we mean that the
  purpose of integrating the set of elements is to
  leverage the capabilities of individual element
  capabilities to accomplish a higher level
  capability that cannot be achieved as stand-alone
  elements.
• By value-added processing, we mean that factors
  such
• operational cost, utility, suitability,
  availability, and efficiency demand that each
  system operation and task add value to its inputs
  availability, and produce outputs that contribute
  to achievement of the overall system mission
  outcome and performance objectives.
• By enable a user to predictably satisfy
  mission-oriented operational needs, we mean that
  every system has a purpose (i.e., a reason for
  existence) and a value to the user(s). Its value
  may be a return on investment (ROI) relative to
  satisfying operational needs or to satisfy system
  missions and objectives.

7
System?

• By in a prescribed operating environment, we
  mean that for economic, outcome, and survival
  reasons, every system must have a prescribedthat
  is, boundedoperating environment.
• By with a specified outcome, we mean that
  system stakeholders (Users, shareholders, owners,
  etc.) expect systems to produce results. The
  observed behavior, products, byproducts, or
  services, for example, must be outcome-oriented,
  quantifiable, measurable, and verifiable.
• By and probability of success, we mean that
  accomplishment of a specific outcome involves a
  degree of uncertainty or risk. Thus, the degree
  of success is determined by various performance
  factors such as reliability, dependability,
  availability, maintainability, sustainability,
  lethality, and survivability.

8
(No Transcript)
9
System Components and Characteristics

• Resources
• Procedures
• Data/Information
• Intermediate Data
• Processes
• Objective
• Standards
• Environment
• Feed Back
• Boundaries and Interfaces

10
System Components and Characteristics
Transaction Processing System Substitutes computer-based processing for manual procedures.Deals with well-structured processes. Includes record keeping applications.
Management information system Provides input to be used in the managerial decision process. Deals with supporting well structured decision situations. Typical information requirements can be anticipated.
Decision support system Provides information to managers who must make judgements about particular situations. Supports decision-makers in situations that are not well structured.