System Analysis Methods Quiz

AISPrE 2: REVIEWER - MODULE 1

• System Development is a systematic process encompassing phases like planning, analysis, design, deployment, and maintenance.
• System Analysis involves fact-gathering, problem identification, and breaking down systems into their components.
• System Design plans new systems or replaces existing ones, defining components for specific requirements.

What is a System?

• System is derived from Greek word Systema meaning an organized relationship between components achieving a shared purpose.
• A system is an orderly grouping of interconnected components that work collectively according to a plan to accomplish a particular goal.

Properties of a System

• Organization: Structured and ordered arrangement of components to achieve objectives.
• Interaction: How components operate with each other.
• Interdependence: Components relying on each other for functionality.
• Integration: Components’ connection within the system.
• Central Objective: A system's primary (stated or real) goal.

Elements of a System

• Inputs: Information entering the system for processing.
• Outputs: Results of the processing.
• Processor: Part transforming input into output.
• Control: Decision-making subsystem governing activities for processing input and producing output.

AISPrE 2: REVIEWER - MODULE 1

• Feedback: Provides control in dynamic systems; positive encourages performance, negative informs for action.
• Environment: The broader system influencing an organization; external elements influencing it.

Types of Systems

• Physical Systems: Tangible, touchable entities (desks, chairs).
• Abstract Systems: Conceptual or non-physical entities (formulas, models).
• Open Systems: Interact with their surroundings exchanging inputs and outputs.
• Closed Systems: Isolated from environment.

Adaptive and Non-Adaptive Systems

• Adaptive: Adjusts in response to environment, examples are human beings and animals.
• Non-adaptive: Doesn't change based on surroundings, examples are machines.

Permanent vs Temporary Systems

• Permanent: Enduring systems; examples are business policies.
• Temporary: Systems with a defined lifespan; examples are setups for programs like DJs.

Natural and Manufactured Systems

• Natural Systems: Systems created by nature; examples are solar systems.
• Manufactured Systems: Systems created by humans; examples are spaceships, dams, and machinery.

Deterministic vs Probabilistic Systems

• Deterministic Systems: Predictable behavior; outputs determined by inputs.
• Probabilistic: Uncertain behavior; outputs not entirely determined by inputs.

AISPrE 2: REVIEWER - MODULE 2

• System Development Life Cycle (SDLC): A structured approach to developing/modifying systems.

System Analysis

• System Planning: Defining goals and tasks for new system initiatives.
• Analysis: Understanding existing business needs before system development.
• Requirements Anticipation: Predictions about system characteristics based on previous experiences.
• Requirements Investigation: Assessing current system features and documenting.
• Requirements Specifications: Determining required features and capabilities describing new systems specifications and details.
• Information Gathering Techniques: Methods like interviews, questionnaires and observations used for gathering data.

AISPrE 2: REVIEWER - MODULE 3

• Software Development Methodology: A framework guiding system development processes.

Types of Methodologies

• Agile Software Development: Flexible method that allows changes.
• DevOps Methodology: Integration of development and IT operations.
• Waterfall Methodology: A linear, sequential, traditional approach.
• Prototype Methodology: Developing a prototype to demonstrate functionality to clients.
• Feature Driven Development (FDD): An iterative model good for transitioning from phase-based to iterative approach.

Rapid Application Development (RAD):

• An effective methodology focused on faster development and better quality outcomes.

Spiral Model:

• A model emphasizing early risk identification and mitigation.

AISPrE 2: REVIEWER - MODULE 4

• System Planning: Establishing the initial needs for a system before development.
• Requirements: The necessary specifications or components for a system that include the processes, data capture, data output, and overall data management system.
• Requirements Determination: Evaluating and collecting details about the existing system to identify what is required for a new or enhanced one.

AISPrE 2 :REVIEWER - MODULE 5

• Structured Analysis: A method for logically grasping systems and their operations.
• Decision Trees: Diagrams illustrating decision-making paths based on different conditions.
• Decision Tables: Matrixes delineating conditions and resulting actions.
• Structured English: A method for precise, procedural descriptions.
• Pseudocode: Using plain English to express system logic.

AISPrE 2: REVIEWER - MODULE 6

• Feasibility Study: Preliminary investigation into the viability and practicality of a new system.
• Types of Feasibilities: Economic, operational, behavioral and schedule.
• Data Flow Diagrams (DFD): Visual representations of data and their movement.
• Entity-Relationship Model (E-R Model): Technique used in database design for relating various entities of an organization.

AISPrE 2: REVIEWER - MODULE 7

• System Design: A critical phase bridging the problem domain and the functional system for managing expectations.
• Types of System Design: Logical design (data flow diagram) and physical design (actual processes, inputs and outputs detailed).

File Organization

• Serial: Stored sequentially by order.
• Sequential: Ordered by a unique identifier.
• Direct/Relative: Stored through a calculated address.
• Indexed: Sequential and random accessing of records.

File Access Methods

(e.g. Sequential, Random).

Modules Design Strategies

• Top-down strategy: Breaking down a system into modules from top to bottom.
• Bottom-Up Strategy: Developing the system from the basic functional components, upwards to the higher level modules.
• Transform-Centered: Transactions all follow the same path.
• Transaction-Centered: Transactions do not all follow the same path.

System Documentation

• Program Documentation: Details about inputs, outputs and processes.
• System Documentation: Technical details, requirements and specifications.
• Operations Documentation: Operations and distributed outputs.