Technology Assignment

Technology Assignment

Part A

Answer # 1

Elicitation and Validation is “the disciplined application of scientific principles and techniques for developing, communicating, and managing requirements”. It is “the systematic process of developing requirements through an iterative process of analyzing a problem, documenting the resulting observations, and checking the accuracy of the understanding gained”.

Requirements Elicitation phase in Requirements Engineering (RE) is found to be very complex and demands more attention when software development is performed on the global scale. The available approaches of requirements elicitation require vigilant application in different scenarios of GSD and may need further improvement when considering challenges of distributed development.

Answer # 2

A requirements specification defines the requirements for the future system at a conceptual level (i.e. class or type level). In contrast, a scenario represents a concrete example of current or future system usage. In many cases, those goals can to a large degree be elicited by observing, documenting and analyzing scenarios about current system usage.

Answer # 3

Use case will be developed by Business Analyst based on the requirement specification. It is a detailed description of the Specification in a simplified version with real-time scenarios. Based on Use case, test cases will be written by the testers.

While Scenarios are writing a test case for a module, you write different tests for that module say, creating a user. There may be several ways to create a user like, creating a user through wizard or through uploading set of users. These are all the things we can call as a scenario.

The more we examine a requirement, the more we learn, and the more things change. To further complicate the issue, changes to one use case can lead to changes in others. Therefore, we want a flexible, highly efficient method for writing use cases that eliminates unnecessary work and rewriting.

You must also capture any requirements that are related to the use case, but are not taken into consideration in the flow of events of the use case. Such requirements are likely to be nonfunctional.

Typically, nonfunctional requirements that refer to a specific use case are captured in the special requirements section of the use case. If there are nonfunctional requirements that apply to more than one use case, capture these in the system-wide requirements specification.

Answer # 4

The key to effective interviewing and hiring is the establishment of functions. By deciding upon the essential functions of the position, you will be able to determine the job's specific requirements.

It is beneficial to stay flexible while conducting interview such as, Formulate questions that indicate whether or not a candidate meets the requirements you have established for the position. Keep three rules in mind (Arthur, 1998):

Ask questions that focus on past employment performance. Avoid questions that address the candidate's personal lifestyles or habits

Ask questions that relate to your listed skill, ability, knowledge or experience requirements

Ask the same questions of all candidates.

Avoid (Arthur, 1998):

Closed questions that require merely a yes or no response

Multiple questions that require several answers

"Loaded" questions that force a choice between two alternatives

Answer # 5

A Requirement is a statement of ...