Requirements analysis

Why?

Most of the time “creative” people do a mistake, whose design work was ordinary at best and who showed an unashamed disregard for the professional as in standards. They were Designers with mark of top A, They knew it all. Technically you can't have the function until you have finalized the requirements of the client; you can only have the idea or fancy of the function. For example designing software for a company, which would be the world's most high tech functioning software. Well, you would have to visualize how to achieve it b observing the requirements of you client before you could experience the function, which leads me to the statement... without client requirements fulfill your design won’t be 100% success.

How? & what is Analyzing means?

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. It is an early stage in the more general activity of requirements engineering which encompasses all activities concerned with eliciting, analyzing, documenting, validating and managing software or system requirements.

According to the statement above its simple definition of a requirement’s analysis regarding to software engineering same way and same method goes to every design in word by word. In interface designing, there are five types of chucks such as:

· 1. Functional requirements

· 2. Data requirements

· 3. Environmental requirements

· 4. User characteristics

· 5. Usability goals and user experience goals

These are foundation level of requirement there are more requirement’s studies in higher level ex:- feasibility studies, function analytic ETC….

Advantages of requirement’s

§ Provides a checklist of requirements.

§ Provide a contract between the project sponsor(s) and developers.

§ For a large system can provide a high level description.

§ Provider successful project

§ Easy to understand

§ Satisfaction of client

§ Good connection

Disadvantages of requirement’s

§ Such lists can run to hundreds of pages. It is virtually impossible to read such documents as a whole and have a coherent understanding of the system.

§ Such requirements lists abstract all the requirements and so there is little context

§ These lists create a false sense of mutual understanding between the stakeholders and developers.

§ These contract style lists give the stakeholders a false sense of security that the developers must achieve certain things. However, due to the nature of these lists, they inevitably miss out crucial requirements which are identified later in the process. Developers can use these discovered requirements to renegotiate the terms and conditions in their favor.

§ These requirements lists are no help in system design, since they do not lend themselves to application.

Conferring to our every judgment we can say that an analyzing is stretches a lot of trouble than asset but every weakness to only for the creator not for client. If you process the analyzing you will get the consummation of client, this is the main goal of the requirements. In a design only customer gratification is the heart of completeness.