Using Quality Function Deployment in Software Requirements Specification

This review and evolution process is repeated as many times as needed, until the final Formal Spec is produced, or the SRS. Then programming can begin. “The process of writing a requirements specification usually requires frequent communications between the developer and the client, keeping the structure of the specification clear and the statements or expressions used readable is therefore crucial”(Lui et al.).

Another way of successfully gathering information is by building a prototype or model of the system, so that users can test or get an idea of what the finished product will be like. With this they can determine issues, problems, or inconsistency with the system. Another important part of gathering information is organizing it so that it can be understood and put to proper use. I propose categorizing the requirements into functional requirements, operational requirements, technical requirements, and transitional requirements. The functional requirements define how the user thinks the system is functioning overall, the operational requirements define what background processes need to be executed in order for the system to work optimally over a period of time, the technical requirements define what technical issues that must be addressed in order to successfully implement the system, and the transitional requirements define the processes or steps needed to implement the system smoothly and successfully. ("Mind Tools", 2012).

2. During elicitation process the user requirements are agreed upon and are clearly defined and expressed in natural language, unambiguous and easy to understand. The requirements, defines the characteristics or operational objectives of the project. During validation, the document reduces the potential for dispute between customer and contractor allowing changes, misunderstandings and problems to be worked out ahead of time, before design and implementation of the system occurs.

Functional requirements must address the quality characteristic of functionality while the other qualities of the characteristics should be concerned with other kinds of non-functional requirements. Applied Software Project Management states,

The information system’s requirements in the systems planning phase are based on a case summary, potential interview questions, and the systems analyst’s experience in systems planning. One must not only generate requirements based specifically on what users’ state they want or need. Analysts must also generate requirements based on insight into the overall organization and project goals.

The project requirements need to be documented in detailed using SMART approach with proper use case scenarios. The revised

Requirement Analysis: collect the business needs, document the requirements, and help team members to prepare Functional and enhancement Specification Document and Technical detail design document.

Agile Project management is one of the industries dominating methodology for project management in IT. It is an incremental and iterative way to manage the build and design activities for constructing an IT product, services, and project development in manner which is highly interactive and flexible. In this methodology, scope is defined in granularity that is appropriate with time horizon and checked with the agreement on each feature with the customer. In this methodology work steps are divided with feature breakdown structures. In order to track the progress of the project progress charts are used instead of Gantt charts. Cross-functional and test-driven development teams starts working from the very beginning of the project to provide

“Perform Quality Assurance (QA)- The process of auditing the quality requirements and the results from quality control measurements to ensure that appropriate quality standards and operational definitions are used” (Project Management Institute, 2013, p. 227). The task begins with development and continues to

Each model was worked close by the others to guarantee streamlined correlations with be made among themselves, revealing and cross-referencing issues found while making comparable and similar models. Once these models were made, necessities and utilize cases moved toward becoming clearer and could be utilized to manufacture the Software Requirements Specification to later convey to the customer to improve the items prerequisites and stream of control to guarantee we were not missing any expected

It is generally accepted that developing use case scenarios is also useful as a means for eliciting requirements, and ensuring that the goals captured are sufficient to support desired system behaviours. Furthermore, the use case scenarios are useful, and that it is important to use a ‘‘textual description of each use case to facilitate understanding’. therefore the unified methodology should support both techniques (e.g., use cases and use case scenarios) to help the analysts identify the key communications/interactions between

This figure represents the relationship that forms under the extreme programming methods. I believe this exemplifies the planning phase and the team deliverables that go into consideration. The project works on five main operational principles that are based on the core values which are assume simplicity, rapid feedback, incremental change, embrace the change, and quality work.

External customer requirements may be gathered and transformed into specific, actionable process improvements using quality function deployment, a well- structured product development process which dictates what the market requires into a program to create, manufacture, and deliver it. However, teams should collaborate to arrive at a common understanding of the customer needs and determine the appropriate technical requirement of each stage. As soon as customer expectations are met, customer satisfaction will improve, resulting in a take-back of market share and an increase in revenue.

Requirements quality: In order to make sure the good quality of a software product certain characteristics of requirements model like correctness, completeness and consistency play a very crucial role.

In software development, there are various types of methods that developers follow in order to produce valuable software. From the many types of methods that exist today, the industry standard that is mostly followed today is the software development lifecycle (SDLC). The SDLC is a process that software development companies utilize in order to design, develop and test software during production. Within the SDLC, there are different test models that developers can utilize based on their business and development requirements. Currently today, the most common models include the waterfall, iterative, spiral and V-model. Regardless of the model that a developer decides to utilize, all the phases will be the same, which would begin with the first step and that is the requirement gathering and analysis phase.