Methodology: Software Engineering and Requirements Gathering

Good Essays
CHAPTER II
METHOD OF THE STUDY (SOFTWARE ENGINEERING PARADIGM)
2.1 Fourth Generation Techniques (4GT)

Figure 2.1 4GT The developers used the fourth generation technique (4GT) as the system development methodology to be applied in this study. 4GT encompasses a broad array of software tools that have one thing in common, each enabled that the software developers to specify some characteristics of software at high level. There is a little debate that the higher the level at which software can be specified to a machine, the faster the program can be built [PRES1997]. The four (4) phases of Fourth Generation Technique (4GT) were relevant to the system to provide a circulation processing of each phase. The developers used the 4GT in developing the system because of it was easy and convenient. They need not to go through the entire phase whenever error is committed. They could go back to any stage. Likewise, this methodology is most applicable to transaction processing system (TPS). It includes the 4 phases such as Requirements Gathering, Design Strategy, Implementation using fourth generation technique (4GL) and Testing.

1. Requirements Gathering Requirement gathering is a process of collecting the user needs to solve a problem or issues and achieve an objective. It is basically a software capability needed by the user to solve a problem or achieve an objective. This is really an important phase/ milestone in a project life cycle. If the requirement gathering is not done properly/ completely, all the hierarchy phases given below stay incomplete, no matter how best the design, until and unless requirements are complete. So we should carefully plan and carry out the requirements gathering with a systematic approach. The developers did some observations regarding the transaction in the company, which eventually led to the discovery of problems of the said institution. In return, these gave the developers the idea to formulate the

You May Also Find These Documents Helpful

  • Better Essays

    American University of Beirut Department of Electrical and Computer Engineering EECE 430: Software Engineering Fall 2013-2014 Section 1 User’s Requirements Document: Home Insurance Group 5 Nour Absi Halabi Petra Chidiac Amal Hneine Mohamed Itani Suzanne Saleh 1|Page Table of Contents A. Introduction...............................................................................................1 1. Purpose ......................................................................…

    • 943 Words
    • 4 Pages
    Better Essays
  • Satisfactory Essays

    Requirements Gathering

    • 447 Words
    • 2 Pages

    Requirements Gathering 101 By Duncan Haughey, PMP Requirements gathering is an essential part of any project and project management. Understanding fully what a project will deliver is critical to its success. This may sound like common sense, but surprisingly it's an area that is often given far too little attention. Many projects start with the barest headline list of requirements, only to find later the customers' needs have not been properly understood. One-way to avoid this problem is…

    • 447 Words
    • 2 Pages
    Satisfactory Essays
  • Satisfactory Essays

    Software Engineering

    • 9756 Words
    • 40 Pages

    K. J. Somaiya Institute of Engineering And Information Technology Sion, Mumbai - 400022 Department: Information Technology Academic year: 2011-12 Lab Manual Class –T.E Sem - VI Subject: Software Engineering Version: 2 K.J.Somaiya Institute Of Engineering And Information Technology Department Of Information Technology Class – T.E Sem - VI Subject: Software Engineering List of Experiments: 1) Detailed Statement…

    • 9756 Words
    • 40 Pages
    Satisfactory Essays
  • Powerful Essays

    software engineering

    • 3131 Words
    • 13 Pages

    History of software engineering From Wikipedia, the free encyclopedia Jump to: navigation, search This article needs additional citations for verification. Please help improve this article by adding citations to reliable sources. Unsourced material may be challenged and removed. (September 2011) History of computing Hardware • Hardware before 1960 • Hardware 1960s to present • Hardware in Soviet Bloc countries Software • Software • Unix • Open-source software Computer science…

    • 3131 Words
    • 13 Pages
    Powerful Essays
  • Powerful Essays

    Software Engineering

    • 2585 Words
    • 16 Pages

    ....................................... 1 Requirements gathering: .............................................................................................. 3 Quick Design: ................................................................................................................ 3 Build Prototype: ............................................................................................................ 3 Evaluate and Refine Requirements:...........................................…

    • 2585 Words
    • 16 Pages
    Powerful Essays
  • Powerful Essays

    Software Engineering

    • 3974 Words
    • 16 Pages

    SOFTWARE ENGINEERING PROJECT – I INTRODUCTION: The goal of this paper is to analyze about three major software projects namely • The London Ambulance System • The Virtual Case File • The Automatic Baggage System By analyzing these software projects and the software engineering principles followed, the key factors responsible for the software projects failure can be understood. Each of these projects has failed miserable…

    • 3974 Words
    • 16 Pages
    Powerful Essays
  • Better Essays

    Software Requirement Engineering through Use case Mrs Mirza Zainab, Lecturer in IT Dept, M.H.S.S. COE, Byculla, India Mirza_zainab@yahoo.com ABSTRACT By now, it is well known that shortcomings in requirements definition and management lead to excessive rework on software projects and products that fail to achieve full customer satisfaction. In systems engineering and software engineering, requirements analysis encompasses all of the tasks that go into the investigation, scoping and definition…

    • 1961 Words
    • 8 Pages
    Better Essays
  • Powerful Essays

    Software Engineering

    • 25020 Words
    • 101 Pages

    INTRODUCTION TO SOFTWARE ENGINEERING ■ What is Software? • Computer Software is the product that software professional design and built. It includes • Programs • Content • Documents ■ What is software engineering? • Your thoughts here • Related to the process: a systematic procedure used for the analysis, design, implementation, test and maintenance of software. • Related to the product: the software should be…

    • 25020 Words
    • 101 Pages
    Powerful Essays
  • Powerful Essays

    Requirements Engineering

    • 2102 Words
    • 9 Pages

    Software Engineering Requirements Engineering Dr.-Ing. Sven Apel Forschergruppe Softwareproduktlinien Universität Passau Based on Material of Oscar Nierstrasz Sven Apel Software Engineering Roadmap      Requirements-engineering process Use cases Functional and non-functional requirements Requirements checking and reviews Roles in requirements engineering Winter Term 2010/11 Slide 2 Sven Apel Software Engineering Sources    Software Engineering…

    • 2102 Words
    • 9 Pages
    Powerful Essays
  • Good Essays

    software engineering (and System Engineering), a functional requirement defines a function of a system or its component. A function is described as a set of inputs, the behavior, and outputs (see also software). Functional requirements may be calculations, technical details, data manipulation and processing and other specific functionality that define what a system is supposed to accomplish. Behavioral requirements describing all the cases where the system uses the functional requirements are captured…

    • 487 Words
    • 2 Pages
    Good Essays