01-29-2011, 04:46 PM
"Requirement gathering is the most critical phase in software development, Justify or contradict with solid reasons in five (5) to seven (7) lines"
|
CS504 - Software Engineering - I GDB solution fall 2010 on 29/jan/2011
|
|
01-29-2011, 04:46 PM
"Requirement gathering is the most critical phase in software development, Justify or contradict with solid reasons in five (5) to seven (7) lines"
02-04-2011, 03:46 AM
"Requirement Gathering is the most critical phase in Software Development, Justify or Contradict with solid reasons in five (5) to seven (7) lines".
GDB CS504 Idea Solution:- Requirements analysis in systems engineering and software engineering, encompasses those tasks that go into determining the needs or conditions to meet for a new or altered product, taking account of the possibly conflicting requirements of the various stakeholders, such as beneficiaries or users. Requirements analysis is critical to the success of a development project. Requirements must be documented, actionable, measurable, testable, related to identified business needs or opportunities, and defined to a level of detail sufficient for system design. Requirements can be architectural, structural, behavioral, functional, and non-functional. Requirement gathering is the most crucial aspect as many times communication gaps arise in this phase and this leads to validation errors and bugs in the software program. 1.1.1Requirement Gathering Requirement gathering is usually the first part of any software product. This stage starts When you are thinking about developing software. In this phase, you meet customers or prospec-tive customers, analyzing market requirements and features that are in demand. You also find out if there is a real need in the market for the software product you are trying to develop. In this stage, marketing and sales people or people who have direct contact with the cus- tomers do most of the work. These people talk to these customers and try to understand what They need. A comprehensive understanding of the customers’ needs and writing down features of The proposed software products are the keys to success in this phase. This phase is actually a base For the whole development effort. If the base is not laid correctly, the product will not find a Place in the market. If you develop a very good software product which is not required in the Market, it does not matter how well you build it. You can find many stories about software products that failed in the market because the customers did not require them.
02-04-2011, 05:00 AM
Thanks seems to be good answer
|
|
« Next Oldest | Next Newest »
|