--%>
Assignment Help - homework help

  Level of SRS

Introduction to Level of SRS

The level of SRS is about the need to restrict the specification as much as possible to specify what the system should do rather than how it should do. As we  have seen the  specification should idea be the user view of the system  rather than say anything  about  how  the system is obtain implemented. This relationship between the specification and the implementation is often explained in terms of the versus how. The specification states what a system should do. The implementer decides how to do it. In practice, however the distinction between the two is not often so harp. For instance in some  case, the  decision as to whether to distribute a banking   system  throughout  the bank s branches or to keep it centralized  in the main branch and  use remote terminals at the o the branches can be considered a design matter I. e. A how matter .so one can claim that physical distribution of system is not a requirement, but an implementation issue.

An Example:  In 1995, the Australian defence and. Technology organisation reported the result of a survey of problem with requirements specification in the navy (Gabb and Henderson 1995). One of the problems it highlighted was the uneven level of specification. That is some requirements had been specified at too high a level and other too low. The unevenness was compounded by several situations.

  • Sometimes requirements analysis used different writing styles, particularly in different system areas.
  • The difference in experience among analysts led to different levels of detail in the requirements.
  • In attempting to reuse requirements from previous systems, analysis used different formats and writing styles.
  • Analysts sometimes mixed the requirements with partial solutions, leading to serious problem in designing a cost effective solution.
  • Often requirements were over specified when analysts identified particular types of computers and programming languages assumed a particular solution or mandated inappropriate processes and protocols.
  • Sometimes requirements were under specified especially when describing the operating environment maintenance simulation for training administrative computing and fault toe lance.

Most of those surveyed agreed that there is no universally correct level of specification.  Customers with extensive experience prefer high level specifications and those with less experience like more detail. The survey respondents made several recommendations, including:

  • Each clause should contain only one requirement,
  • Avoid having one requirements refer to another requirements , and

Collect like requirements together.

Latest technology based Software Engineering Online Tutoring Assistance

Tutors, at the www.tutorsglobe.com, take pledge to provide full satisfaction and assurance in Level of SRS homework help via online tutoring. Students are getting 100% satisfaction by online tutors across the globe. Here you can get homework help for Level of SRS, project ideas and tutorials. We provide email based Level of SRS homework help. You can join us to ask queries 24x7 with live, experienced and qualified online tutors specialized in Level of SRS. Through Online Tutoring, you would be able to complete your homework or assignments at your home. Tutors at the TutorsGlobe are committed to provide the best quality online tutoring assistance for Software Engineering homework help and assignment help services. They use their experience, as they have solved thousands of the software engineering assignments, which may help you to solve your complex issues of Level of SRS. TutorsGlobe assure for the best quality compliance to your homework. Compromise with quality is not in our dictionary. If we feel that we are not able to provide the homework help as per the deadline or given instruction by the student, we refund the money of the student without any delay.