Latest Posts

Benefits of an SRS | Building the SRS
Benefits of an SRS | Building the SRS

Using an SRS model provides a specification process that is unequivocal and delivers a complete specification document. This assists the project manager in communicating clearly with the project stakeholders to ensure that:

Tags life cycle, srs, software product, project stakeholders, traceability matrix

Questions the SRS Answers for a Project
Questions the SRS Answers for a Project

The most important question that the SRS addresses concerns the problem domain in which the product will exist. As shown in Figure 1, all software products can be viewed from three perspectives: data, process, and behavior.

Tags software products, software system, srs, construx software

Developing the Software Requirements Specification
Developing the Software Requirements Specification

Getting the requirements correct is perhaps the major part of a software development project. Once a software development team begins to collect the project requirements, it is critical that the project have a consistent format for maintaining and presenting them. This section

Tags srs, software development, life cycle,

Requirements and Quality Function Deployment
Requirements and Quality Function Deployment

Quality function deployment (QFD), also generally known as a way to represent the "voice of the customer" is a process for capturing customer requirements and translating them into requirements that can be used by designers, producers, and suppliers. As with many other

Tags qfd, life cycle, elicitation methods, fast, brainstorming, jad, requirements prioritization

Challenges in Eliciting Requirements
Challenges in Eliciting Requirements

The most difficult single part of building a software system is deciding specifically what to build. No other part of the conceptual work is as difficult as establishing the detailed technical requirements, containing all the interfaces to people, to machines, and to other software

Tags software systems, eliciting requirements, software requirements, life cycle models

Guidelines for Writing Quality Requirements
Guidelines for Writing Quality Requirements

Requirements, generally gathered via many different means, will become specifications when they are tightened up and formatted according to the SRS template, or "container". Clarity that can be imbued at this point will be appreciated later. There is not as much precision in the

Tags srs template, software requirements, prototypes

Facilitated Application Specification Techniques (FAST)
Facilitated Application Specification Techniques (FAST)

FAST is similar enough to brainstorming and to JAD that we will provide only cursory coverage here. This is not to belittle the process in any way - FAST is an important part of the software PM's vocabulary because it was developed to be a method particularly for gathering software

Tags fast, brainstorming, jad, software requirements, elicitation methods

Requirements Elicitation Methods
Requirements Elicitation Methods

We will study interviewing, brainstorming, mind mapping, facilitated application specification technique (FAST), Joint Application Design (JAD), and use case scenarios as viable methods for eliciting software requirements. These are some suggested activities and thoughts that are

Tags software requirements, fast, jad, brainstorming, mind mapping

What Is a Software Requirement
What Is a Software Requirement

A software requirement is a capability that somebody needs or wants. It can be a component of an entire new application, a new feature for an existing application (an enhancement), or a request to correct a current shortcoming. IEEE describes a requirement as: (a) a condition or capability needed by a user to solve a problem or achieve an objective; (b) a condition or

Tags software requirement, product features, requirements elicitation

Requirements Management and the SEI CMM
Requirements Management and the SEI CMM

Requirements management is a key process area (KPA) for SEI CMM Level 2, the repeatable level. The purpose is to "establish a common understanding between the customer and the software project of the customer's requirements that will be addressed by the software project."

Tags software product, life cycle, software engineering group, software project, csf

The contents available on this website are copyrighted by TechPlus unless otherwise indicated. All rights are reserved by TechPlus, and content may not be reproduced, published, or transferred in any form or by any means, except with the prior written permission of TechPlus.
Copyright 2015 SPMInfoBlog.
Designed by TechPlus.com.pk