Blog

A CASE (Computer Aided Software Engineering) tools mean any tool used to automate some activity associated with software development. Some of these CASE tools assist in phase-related tasks such as specification, structured analysis, design, coding, testing etc.

Risk management aims at reducing the chances of a risk becoming real as well as reducing the impact of risk that becomes real. Three activities in risk management are risk identification, risk assessment, risk mitigation.

COCOMO (Constructive Cost Estimation Model) model was proposed by Boehm (1981). According to Boehm, software cost estimation should be done through three stages: Basic COCOMO, Intermediate COCOMO, and Complete COCOMO.

Software maintenance is the process of modifying a software system or component after delivery to correct faults, improve performances or other attributes, or adapt to a changed environment.

A good software design implies clean decomposition of the problem into modules and the neat arrangement of these modules in a hierarchy. The primary characteristics of neat module decomposition are low coupling and high cohesion. Cohesion is a measure of functional strength of a module.

Software design deals with transforming the client requirements, as described in the SRS document, into a form (set of documents) that is suitable for implementation in a programming language.

At a technical level, software engineering begins with a series of modeling tasks that lead to a complete specification of requirements and a comprehensive design representation for the software to be built. The first technical representation of a system which is the analysis model, actually a set of models. There have been many methods proposed for analysis modeling.

A software requirement specification (SRS) is a comprehensive information/description of a product/system to be developed with its functional and non-functional requirements. The software requirement specification (SRS) is developed based on the agreement between customer and supplier.

The requirements elicitation and specification phase starts when the feasibility study phase is completed and the project is found to be technically and feasible. The goal of the requirements analysis and specification phase is to understand client requirements and to systematically organize these requirements in a specification document.

Evolutionary model is also referred to as the successive versions model and sometimes as the incremental model. In Evolutionary model, the software requirement is first broken down into several modules (or functional units) that can be incrementally constructed and delivered.

The spiral model is a software process model that couples the iterative nature of prototyping with the controlled and systematic aspects of the linear sequential model. Barry Boehm mentioned the Spiral model in this paper (1986).

A prototype model is a toy/demo implementation of the actual product or system. A prototype model usually exhibits limited functional capabilities, low reliability, and inefficient performance as compared to the actual software.

In Iterative waterfall model, the feedback paths are provided from every phase to its preceding phase. In practice, it is not possible to strictly follow the classical waterfall model for software development work. In this context, we can view the iterative waterfall model as making necessary changes to the classical waterfall model so that it becomes applicable to practical software development projects.

The classical Waterfall Model was the first Process Model. It is also known as a linear-sequential life cycle model. It is very simple to understand and use. Classical waterfall model is the earliest, best known and most commonly used methodology.