Describe some techniques for gathering requirements to develop SQL queries. Prov
ID: 3878013 • Letter: D
Question
Describe some techniques for gathering requirements to develop SQL queries. Provide an example using a business case.
Also, discuss some merits and demerits of the techniques you identify.
"In today's world, there is so much data and information that we can no longer keep track of or understand our data." How would you respond to this statement? Consider interview questions and use SQL to understand the problem the user is facing.
Describe the different levels of normalization and provide at least two examples of each level. Describe what positive and negative impacts each level has on a database.
"I need to find the following information, but the system does not provide the data I need." Develop a response to this statement focusing on how you could help the user find the information he or she is looking for. Review your classmates' posts and see if their comments would change your approach.
Explanation / Answer
Part 1:- Describe some techniques for gathering requirements to develop SQL queries:-
A. One-on-one interviews:- The most common technique for gathering requirements is to sit down with the clients and ask them what they need. The discussion should be planned out ahead of time based on the type of requirements you're looking for. Eg say a client's business is Online Insurance Policy, we can ask the client as to how he wants this to be implemted, hows the business gonna interact with Customers, How customers Details will be stored, How to find out a policy details, etc and later on analysis break them down to Tables for SQL.
Merit - Since 1 individual is concerned, the requirements will be very clear as the source of info is 1
Demerit - Not the complete requirements can be gathered from a single source of information. ie. 1 person in this case.
B. Group interviews :- Group interviews are similar to the one-on-one interview, except that more than one person is being interviewed — usually two to four. These interviews work well when everyone is at the same level or has the same role. Eg:- In a group we get to know more about the business requirements as in case of "Online Insurance Policy", one member tell us about different policies and benefits, other member tells us about claims and approvals process, third member tells us about report generation strategies, fourth about backup and installations guide, etc.
Merit = Broader Description of various requirements can be gathered together from the group.
Demerit = Time Taking process as you need to hear each and every person for their requirement and understand them.
C. Facilitated sessions - In a facilitated session, you bring a larger group (five or more) together for a common purpose. In this case, you are trying to gather a set of common requirements from the group in a faster manner than if you were to interview each of them separately. Eg- Conduct a session with your clients and ask them to express their business requirements which can be jotted down and later converted to SQL Queries.
Merit = Faster gathering of requirements from clients as they are present in sessions.
Demerit = Need to schedule such sessions after taking appointments from clients which might get delayed because of their busy schedules.
D. Questionnaires:- Questionnaires are much more informal, and they are good tools to gather requirements from stakeholders in remote locations or those who will have only minor input into the overall requirements. Eg- Ask more questions to the clients when some information is not clear or undecided about the implementation in case of "Online Insurance Policy", to clear doubts and gather solid proof before things are finalized.
Merits = Good and proper understanding of the requirements via cross - questioning.
Demerits = Time consuming as lots of questions needs to be asked for getting the related answeres.
E. Joint application development (JAD) - JAD sessions are similar to general facilitated sessions. However, the group typically stays in the session until the session objectives are completed. For a requirements JAD session, the participants stay in session until a complete set of requirements is documented and agreed to. Eg- Until the client confirms the requirements for the business, post that those are documented and signed by the same, which later becomes the base of development of the project.
Merit = Faster gathering of requirements from clients as they are present in sessions, until requirements are finalized and documented.
Demerit = Need to schedule such sessions after taking appointments from clients which might get delayed because of their busy schedules.
Part 2:- In today's world, there is so much data and information that we can no longer keep track of or understand our data." How would you respond to this statement?
In today's ever fast growing technological world data and information are the key relying sources for the growth of any business. For any business to flourish world-wide we need to be keen on data access and storage via which we can determine the rate of growth of the business. As the business keeps growing, so does the data and related information, that today its very difficult to handle them if not stored in a proper fashion or the data stored is difficult to understand eg:- text files or comma separated files or data stored in un-readable format. In order to make efficient use of our data, we must ensure Data Stoage, Data Retrieval and Data Security, the prime components of the business data we are storing and accessing daily without any data getting corrupted.
eg:- Data Storage - CREATE TABLE so that data is stored in a well mannered and structured way.
eg:- Data Retrieval - SELECT clause can retrieve the data we want to see.
Part 3:- Describe the different levels of normalization and provide at least two examples of each level.
First Normal Form (1NF): Each field in a table must contain different information.
Positive Impact :- Each and every column is atomic in nature and no multivalued attribute is present.
Negative Impact:- All details are clubbed together in a single row and deletion of 1 row deletes other important details as wll.
Eg:- STUDENT Database
Second Normal Form (2NF): All attributes that are not dependent upon the primary key in a database table must be eliminated.
Positive Impact:- Clean structure of a particular entity with all relevant columns mapped to the same entity.
Negative Impact:- Since entities are now separated, more entity/tables are formed, which could be difficult to manage.
Third Normal Form (3NF): No duplicate information is permitted. So, for example, if two tables both require a
common field, this common field information should be separated into a different table.
Positive Impact:- No-Duplicate records are allowed to be stored.
Negative Impact:- Since this Normal Form contains Primary-Foreign Key relationships we first need to child the child records in order to delete the Master records else it will report violation errors of Key Constraints.
Please let me know in case of any clarifications required. Thanks!
STUD_ID FIRST_NAME LAST_NAME DOB GENDER EMAIL_ID COURSE_ID COURSE_NAME COURSE_DESC GRADE 123456 JOHN KUHL 08-AUG-1990 MALE xyz@dot.com CS-1234 Advanced Electronics This is acourse for 2nd Semester 10.0 654321 ABC XYZ 02-FEB-1980 FEMALE abc@dot.com CS-543 Automata Thoery This is acourse for 5th Semester 9.00Related Questions
drjack9650@gmail.com
Navigate
Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.