System:

A system is an orderly grouping of interdependent components linked together according to a plan to achieve a specific objective. The study of system concepts has three basic implications:

1. A system must be designed to achieve a predetermined objective.
2. Interrelationships and interdependence must exist among the components.
3. The objectives of the organization as a whole have a higher priority than the objectives of its subsystems.

Characteristics of a system:

1. Organization:

   It implies structure and order. It is the arrangement of components that helps to achieve objectives.

2. Interaction:

   It refers to the manner in which each component functions with other components of the system.

3. Interdependence:

   It means that parts of the organization or computer system depend on one another. They are coordinated and linked together according to a plan. One subsystem depends on the output of another subsystem for proper functioning.

4. Integration: It refers to the holism of systems. It is concerned with how a system is tied together.

5. Central Objective:

   A system should have a central objective. Objectives may be real or stated. Although a stated objective may be the real objective, it is not uncommon for an organization to state one objective and operate to achieve another. The important point is that users must know the central objective of a computer application early in the analysis for a successful design and conversion.

Difference Between structured systems and object oriented systems:

1. Methodology:

   Structured: SDLC

   Object Oriented: Iterative/Incremental

2. Focus:

   Structured: Process

   Object Oriented: Object

3. Risk:

   Structured: High

   Object Oriented: Low

4. Reuse:

   Structured: Low

   Object Oriented: High

5. Maturity:

   Structured: Mature and Widespread

   Object Oriented: Emeraging

6. Suitable For

   Structured: Well-defind projects with stable user requirement

   Object Oriented: risky large projects with changing user requirement

7. Analysis:

   Structured: Structuring Requirements: - DFD's - Structure English - Decision Table/Tree - ER Analysis Object Oriented: Requirement Engineering 1. Use Case Model - Use Case Diagram - Flow Diagram - Activity Diagram 2.Object Model - Find Classes and Class Relationship
   - State Diagram, Sequence Diagram - Collaboration Diagram

8. Design:

   Structured: DB design (DB normalization) GUI Design (forms & reports)

   Object Oriented: Physical DB design

   Design elements:

   • Design system Architecture
   • Design classes: Checking The Model, Combine Classes,

   Splitting Classes, Eliminate Classes

   • Design components
   • GUI design