Skip to main content

Structured English

 

Structured English in System Analysis and Design

Structured English is a technique used in system analysis and design to describe the logic of a system's processes in a clear and concise way. It combines the readability of natural language with the precision of programming constructs.

Here's a breakdown of its role:

  • Purpose: Clearly document the steps involved in a system's functionalities.
  • Benefits:
    • Improves communication between analysts, designers, and users by using familiar language with a structured approach.
    • Enhances the clarity and maintainability of system design documents.
    • Aids in identifying potential flaws in the logic before coding begins.
  • Structure:
    • Uses a limited set of English verbs like "display," "calculate," "update," etc.
    • Incorporates control flow keywords like "IF," "WHILE," "FOR EACH" for decision-making and loops.
    • Avoids unnecessary adjectives and adverbs for better focus.

Relationship to Structured Analysis and Design (SA/SD):

Structured English is one of the tools used within the SA/SD methodology. SA/SD is a systematic approach for developing software systems. Here's how they work together:

  1. Structured Analysis: Analyzes the existing system (if applicable) and defines the requirements for the new system. This might involve Data Flow Diagrams (DFDs) to map data flow and functionalities.
  2. Structured Design: Uses the analysis results to design the new system's architecture. Structured English comes into play here to describe the logic within each process or function identified in the DFDs.
  3. Coding: The structured English descriptions are then translated into actual programming code.

Overall, Structured English helps bridge the gap between the high-level requirements of a system and the detailed code that implements it.

Comments

Popular posts from this blog

Installation Steps

Download the Installer: Visit the website of the application you want to install and locate the download link for the Windows version. Usually, this will be an executable file (.exe) or a compressed file (.zip) containing the installer. Run the Installer: Once the installer file is downloaded, locate it in your downloads folder or wherever you saved it. Double-click on the installer file to run it. If it's a compressed file, extract its contents first and then run the installer. User Account Control (UAC) Prompt: Windows might display a User Account Control prompt asking for permission to make changes to your device. Click "Yes" to proceed with the installation. Setup Wizard: Most installers launch a setup wizard that guides you through the installation process. Follow the on-screen instructions which may involve accepting the license agreement, choosing the installation directory, and selecting any additional options or components you want to install. Installation Pr...

Spawning Processes of Linux OS

In Linux, spawning a process refers to the act of creating a new program execution instance. This essentially means creating a new child process from an existing parent process. Spawning allows for multitasking and running multiple programs concurrently on your system. Here's a breakdown of the mechanics: The core concept: Parent process:  The existing process that initiates the spawning. Child process:  The newly created process that inherits resources like memory and open files from the parent, but has its own execution path. The tools for spawning: fork() system call:  Creates a copy of the parent process, forming the basis for the child process. exec() system call:  Replaces the current process image with a new program, essentially loading and executing the child program within the child process. The two-step approach: fork():  Creates a near-identical copy of the parent process, including memory and file descriptors. This essentially duplicates the parent p...

Private, Protected and Public Members

  In C++ Object-Oriented Programming (OOP), access specifiers control how members (data and functions) of a class can be accessed from different parts of your program. These are crucial for understanding data encapsulation and promoting secure object-oriented design. Access Specifiers: Public:  Members are accessible from anywhere in your program, including outside the class, its subclasses, and friend functions. Use them cautiously to avoid exposing internal implementation details unnecessarily. Private:  Members are accessible only within the class and its friend functions. This promotes data encapsulation and protects data integrity by restricting direct access from outside. Protected:  Members are accessible within the class, its subclasses, and their friend functions. Useful for inheritance scenarios where subclasses need controlled access to base class members. Benefits of Each: Public:  Provides direct access and ...