Natural Language is used to write requirement specification for a proposed system. However, when requirements are written in natural language, several problems might occur. Question State and explain these problems in your own words and what recommendations could you propose to minimize misunderstandings when writing user requirements using natural language?

Natural Language is used to write requirement specification for a proposed system. However, when requirements are written in natural language, several problems might occur. Question State and explain these problems in your own words and what recommendations could you propose to minimize misunderstandings when writing user requirements using natural language?

Fundamentals of Information Systems

9th Edition

ISBN:9781337097536

Author:Ralph Stair, George Reynolds

Publisher:Ralph Stair, George Reynolds

Chapter8: System Acquisition And Development

Section: Chapter Questions

Problem 7SAT: The overall emphasis of the ___________ phase is on gathering data on the existing system,...

See similar textbooks

Similar questions

The overall emphasis of the ___________ phase is on gathering data on the existing system, determining the requirements of the new system, considering alternatives within identified Constraints, and investigating the feasibility of alternative solutions. a. investigation. b. analysis. c. design. d. construction.
If a system’s end- user stakeholders are not involved during its development or updation requirement engineering process then what type of functional requirements related problems are expected? Name and explain any two of them.
Q-2 If a system’s end-user stakeholders are not involved during its development or updating requirement engineering process then what type of functional requirements-related problems are expected? Name and explain any two of them.
may you please explain how an engineer who is producing a system requirements specification may possibly keep track of the dependencies that exist between functional and non-functional needs?
Functional requirements (FR) as those that define what a system is supposed to do, while non functional requirements (NFRs) define constraints which affect how the system should do it. Provide TWO (2) requirement specification examples to differentiate the FR and NFR.
Design a generic post-implementation evaluation form. The form should consist of at least eight (8) questions that you could use to evaluate any information system. Be sure to include questions that evaluate the training received and any problems associated with the program.
Consider how an engineer who is tasked with writing a system requirements specification may keep track of the interdependencies between functional and non-functional needs. Please read this with care.
Q.No.4. Consider the following requirements and identify (Functional and Non Functional) requirements from them. 1. The hospital management system should allow medical staff and doctors to use all system features after four hours of training 2. Patients should be able to search the appointment lists for all clinics 3. The system shall generate for each day a list of patients who are expected to attend appointments that day 4. The system must be implemented in C++ programming language. 5. The hospital management system should be easily modified to accommodate enhancements and repairs. 6. Copies of patient record should be maintained on two separate servers that are not kept in same building 7. X – Ray machines should have all recent windows updates and should operate within small safety tolerances8. The system shall provide access to a legacy course catalogue database with no more than a 10 seconds latency 9. The system should be easy to use by all medical staff and should be organized…
This week's discussion topic focuses on functional requirements. These need to be clearly written so the people who are developing the system or evaluating a system for use, can discern whether or not the functional requirements are met. The functional requirements statement: Is a complete sentence, with a subject (system) and predicate (intended result, action or condition) Identifies only one requirement; does not include the words "and," "also," "with," and "or." States what tasks the system will support or perform Includes a measure or metric that can be used to determine whether the functional requirement is met (time or quantity), where appropriate Is stated in positive terms and uses "must" (not "may" or "should"); e.g., "the system must xxxx" not "the system must not xxx" Avoids the use of terms that cannot be defined and measured, such as "approximately," "robust," "user friendly," etc. Must be testable; that is, there must be some way to test the system to determine whether…
What are non-functional requirements, and why are they important in software development? Provide examples of non-functional requirements.
Provide an illustration of the relationship between requirements engineering and design, and explain why the two fields are complementary to one another in the software engineering industry. Please provide an example to further illustrate the connection between requirements engineering and design.
Think about how an engineer who is entrusted with drafting a system requirements specification might possibly keep track of the interdependencies that exist between functional and non-functional demands. Take your time and carefully read the following.