Software Processes and Life Cycle Models

User‐centered approaches in software development processes: Qualitative research into the practice of Hungarian companies

“…Diagrams (e.g., flow charts and data-flow diagrams) and other tools (e.g., data dictionaries) assigned to the different life cycle phases were also a common characteristic of the different structured development techniques. 26 Formal development methods were widely discussed in research in the 1980s. The main idea behind these formal methods is to specify the requirements of a system in B Abstract Machine Notation specification language with clearly defined semantics by building a mathematically rigorous model of it (e.g., using predicate logic, symbols denoting sets, sequences, and functions abstract data types) and then proving, in the mathematical sense, that the implementation satisfies the specification.…”

“…In practice, there are plenty of SDLC models available for various companies to choose from which describe the combination and temporal relationship of the various processes to specify software requirements and transform them into a deliverable software product. 25,26 The basic model used in the earliest days of software development involved only coding and fixing activities. Thus, the priority in the development processes was writing the code first and thinking about the requirements, design, testing, and maintenance later.…”

“…Consequently, it allows concurrent activities and helps reduce risk by getting quick feedback from the stakeholders on the work performed. 26 Thus, the evolutionary development models ensure rapid initial operational capability and provide a realistic operational basis to the users determining subsequent product improvements for the planning stage of the next cycle. 38 Of course, by applying this model, the process was difficult to follow, making it challenging to measure the progress at management level.…”

“…The process of software development has taken different routes at different times in the past. In practice, there are plenty of SDLC models available for various companies to choose from which describe the combination and temporal relationship of the various processes to specify software requirements and transform them into a deliverable software product 25,26 …”

“…In the evolutionary development model, the key is to create an operational software product, making expanding increments in every stage, with the directions of evolution being determined by operational experience. Consequently, it allows concurrent activities and helps reduce risk by getting quick feedback from the stakeholders on the work performed 26 . Thus, the evolutionary development models ensure rapid initial operational capability and provide a realistic operational basis to the users determining subsequent product improvements for the planning stage of the next cycle 38 .…”