Author name: Abhay Krishnan

A software requirements specification (SRS) is a document generated when a complete description of all features of the software to be built is required prior to the start of the project. It should be noted that a formal SRS is not usually written. In fact, there are numerous cases where the time and effort invested […]

Requirements The description of the features and functionalities of the target system is called requirements. The expectations of users from the software product are communicated through requirements. IEEE defines a requirement as follows: A condition or capability needed by a user to solve a problem or achieve an objective. A condition or capability that must

Agile Process An agile process is highly driven by the customer requirements and considering the customer as a part of the development team thereby adapting to changes after delivering software increments. The emphasis is on construction rather than the intermediate work products recognizing that plans are short-lived and changes are always happening. Principles of Agile

Component-Based Development(CBD) The component Based Development Model has the characteristics of a spiral model, hence is evolutionary and iterative in nature. In this model, applications are built from pre-packaged software components that are available from different vendors. Components are modular products with well-defined functions that can be incorporated into the project of selection. The modelling

Prescriptive process models Prescriptive process models prescribe a set of framework and other activities, quality assurance points, and software process-related elements. They define a workflow among these elements that shows their inter-relationship. The process models described here are, Waterfall Model. Incremental Process Model. Evolutionary Process Model. The Waterfall Model The Waterfall model is also known

SDLC(Software Development Life Cycle) comprises a series of activities that are used to design, develop and test high-quality software products, conforming to time and cost constraints. Planning and Requirement analysis Requirements are gathered and analysed, a feasibility study is conducted. Planning for quality assurance requirements are laid out and possible risk factors are determined. Defining

Software processes are assessed to ensure their ability to control the cost, time and quality of software. Assessment is done to improve the software process followed by an organization. Software Process Improvement (SPI) Cycle includes: Process measurement Process analysis Process change Different approaches towards process assessment include CMM (Capability Maturity Model) and CMMI (Capability Maturity

Software Process The software process comprises activities performed to create a software product. It deals with the technical and management aspects of software development. Software process includes : Tasks – focus on a small, specific objective. Action – set of tasks that produce a major work product. Activities – group of related tasks and actions

Software Engineering Practice Essence of practice General steps in carrying out software engineering are, Understand the problem through communication. Plan a solution by modelling and designing. Carry out the plan (coding). Examine result for correctness (testing). Principles of best practice Software should provide value to users. Keep the software design simple. The vision of the

What is Software? Software can be described as a collection of instruction that is executed to get desired functionalities. It is different from a program in the sense that software includes programs, documentation and operating procedures. Characteristics of software compared to hardware Software is developed, not manufactured. Does not wear out. Has reusable components. Flexible.