Linear Sequential Development - Classic life cycle - Waterfall model - Introduction of Software Engineering

Q.  Which model is also called as the classic life cycle or the Waterfall model?
- Published on 22 Jul 15

a. Iterative Development
b. Linear Sequential Development
c. RAD Model.
d. Incremental Development

ANSWER: Linear Sequential Development
 

    Discussion

  • viresh   -Posted on 21 Jul 16
    Bsc nursing
  • Nirja Shah   -Posted on 12 Oct 15
    - The simplest process model is the water fall model which states that the force is organized in a linear order.

    - So it is also known as the linear sequential model or classic life style model.

    - The linear sequential model is the oldest and one of the most widely used paradigm for software engineering.

    - It suggests a systematic, sequential approach to software development that begins at the system level and progresses through analysis, design, coding, testing and maintenance.

    - Modeled after the conventional engineering cycle, the linear sequential model encompasses the following activities.

    System / Information Engineering
    - As software is always a part of larger system (or business), work begins here by establishing requirements for all system elements and then allocating some subset of these requirements to software.
    - This view is essential when software must interface with other elements such as hardware, people, and databases. This provides Top-Level design and analysis.

    Software requirements analysis
    - This process is intensified and focused specifically on software.
    - Analysis is important for the software engineer to understand the information domain for the software, required functions, behavior, performance, and interfacing.
    - Requirements for both the system and the software are documented and reviewed with the customer.

    Design
    - This is a multi-step process that focuses on data structure, software architecture, procedural detail and interface characterization.
    - It translates requirements into a representation of the software that can be assessed for quality before code generation begins.
    - The documents must be prepared and stored as a part of software configuration.

    Code generation
    - This step translates the design into a machine readable form.
    - If design is performed in a detailed manner, code generation can be accomplished mechanistically.

    Testing
    - Once code has been generated, program testing begins.
    - This process focuses on the logical internals of the software, assuring that all statements have been tested, and on the functional externals – that is, conducting test to uncover errors and ensure that defined input will produce actual results that agree with required results.

    Maintenance
    - Software will undergo change after it is delivered to the customer.
    - Change will occur because, errors have been encountered or to accommodate changes in its external environment (e.g. change in device) or customer requires functional or peripheral enhancement.

Post your comment / Share knowledge


Enter the code shown above:

(Note: If you cannot read the numbers in the above image, reload the page to generate a new one.)