Determine and Confirm Client Business Requirements

This document provides a comprehensive guide on how to determine and confirm client business requirements. It includes information gathering techniques, objectives development, system requirements identification, and documentation review.

ICTICT401
Determine and Confirm Client
Business Requirements

Table of Contents
INTRODUCTION...........................................................................................................................1
ASSESSMENT 1 PROJECT...........................................................................................................1
1. Clearly establish the business problem to be investigated including system boundaries,
scope and the development methodology to be used..................................................................1
2. Include the use of one or more information gathering techniques and record all responses.. 2
3. Develop objectives and identify the expected outcomes to be achieved................................2
4. Identify the system requirements of the new system and establish problem specifications.. .2
5. Review the documentation to ensure it meets client business needs and make the required
changes........................................................................................................................................3
ASSESSMENT 2 Written Questions ..............................................................................................4
1. List four different information gathering techniques..............................................................4
2. What is the difference between an open question and a closed question?..............................4
3. What is the purpose of determining and confirming client business needs?..........................4
4. What is a Software Requirements Specification (SRS)?........................................................4
5. What is the difference between a functional and a non-functional requirement?...................5
6. What is a functional requirement? Provide an example..........................................................5
7. A waterfall model is a type of __________ development methodology?..............................6
8. Describe 4 different methods of collecting information.........................................................6
9. Describe the meaning of the following terms:-.......................................................................6
CONCLUSION................................................................................................................................7
REFERENCES................................................................................................................................8

INTRODUCTION
It is important to determine the business needs and requirements of clients at regular
intervals of time and verify the appropriateness of the data collected. This is important in order to
make sure that the business requirements and demands of clients can be timely fulfilled as per
their expectations. The report is divided into two sections. The first section is project which is
based upon a case and addressing the queries related to the same. The second section of the
report consists of some written questions related to research and information technology.
ASSESSMENT 1 PROJECT
1. Clearly establish the business problem to be investigated including system boundaries, scope
and the development methodology to be used.
Epic Video runs a complete manual system and its employees are usually young and
casual who are not very particular about the habit of record keeping. The business problem that
emerges as a consequence of this is that the organisation is losing track of the stock which
impacts upon the organisational ability to carry out basic functions, thereby leading it to lose
money. Also, the company is encountering the issue of moderately higher staff turnover and the
manual system makes it tougher to search in the catalogue to select specific movie for customers
and even if one is found, the entity is not able to acknowledged if it is available in the store.
System Boundaries: The main constraints of the physical system were the increasing
staff turnover ratio, the losing money, the lost track of stock by the company and many more.
The new system that will be launched in this regard will be effective enough in order to address
these issues and automate all of these processes.
Scope: The scope of the business problem that has been already identified above is
acknowledged to be wide. This can be said on the basis of the premise that the issue is affecting
an array of domains pertinent to the business organisation. Thus, the emergence of need for
addressing the respective issue became apparent and the manual system needed to be replaced
with an automated system in a rapid course of time. m
Development Methodology: Waterfall method is the development methodology which
will be put to use for the purpose of developing the automated system for stock tracking as well
as record keeping. This will streamline the overall process and provide assistance to the
organisation in avoiding any kind of discrepancy prevailing within the bounds of the company.
1

2. Include the use of one or more information gathering techniques and record all responses.
The main intent of a computer system is to provide assistance to an organisation in
performing its tasks in an effective and efficient manner. Whenever an IS has to be implemented,
it is crucial to collect information about the requirements of users. Information System is
complex and the user requirements often get difficult to comprehend. For the collection of data,
the usage of one or more techniques for data gathering can be done:-
 Questionnaire: A questionnaire can be defined as a research instrument which is put to
use in a bid to collect data via respondents by asking from them, series of questions.
 Focus Groups: It can be defined as a small group discussion whereby participants give
responses to a series of enquiries mainly centred around a specific topic.
 Observation: This can be defined as a method of collecting data whereby information is
gathered by analysing and looking upon things and activities in a detailed manner.
 Interview: It can be defined as a structured conversation whereby one participant makes
enquiries and the other person gives the solutions.
3. Develop objectives and identify the expected outcomes to be achieved.
The objectives that have been laid down are as follows:-
“To automate the whole process of record keeping by the end of next 1 month”
“To reduce the staff turnover ration by next 3 months”
“To regularly track stock with the help of automated system”
4. Identify the system requirements of the new system and establish problem specifications.
The investigation that has been carried out so far is acknowledged to be preliminary
investigation or study. The aim hereby is identified to be collecting information which is enough
to be able to make the decision related to continuing or not with a detailed analysis in a critical
manner. In this stage, the system requirements of the new system will be recognised which will
provide due assistance in streamlining the project related to launch of a new system for carrying
out all of the stock tracking and record keeping procedures. In this relation, the system
requirements can be identified with the help of problem specification. The problem
specifications of the system lay down the following:-
• The objectives of the information system – what the client wants to achieve at the end of the
project such as reducing overtime by implementing the new system.
• The scope of the project – the actual work or tasks required to achieve the objective.
2

• Any constraints that will influence the solution – can be monetary, logistical or technical
constraints.
• The functional requirements of the system – what the system change is actually going to do.
It has been identified that the system requirements are mainly technical, functional, and
financial. These requirements need to be duly addressed in a bid to make sure that the new
system developed for carrying out all the procedures of the store in the desired manner, is
effective enough.
5. Review the documentation to ensure it meets client business needs and make the required
changes
Whenever a new information system or new technology has to be implemented within the
bounds of any organisation, it is important to review the documentation that has been done. It
helps in making sure that the requirements and needs of the clients are duly met. This helps in
identifying the changes that need to be made within the system. As a result of identification of
the need of changes, alterations can be then made for the purpose of making sure that the new
system developed is effective enough to cater to the needs of clients.
3

ASSESSMENT 2 Written Questions
1. List four different information gathering techniques.
 Questionnaire, survey & checklist
 Face to Face / Telephonic interview
 Focus Groups
 Observations
2. What is the difference between an open question and a closed question?
Open Question: These are the questions which enable an individual to provide free way
answers.
Closed Question: These are the questions which restrain the form of answers that can be
given by respondents in terms of “Yes or No” or “A or B or C or D”, likert scale and so on.
3. What is the purpose of determining and confirming client business needs?
It is important to identify as well as confirm the business needs of the clients. The
purpose of doing this is to properly recognise the needs and demands held by the clients, which
provide the entity with information regarding the aspects upon which it needs to work for the
maximisation of benefits along with satisfaction driven by the clients. In case the failure to
properly determine the business needs of the clients take place, it will imply the shift of clients to
another company that may recognise and meet their needs in a better and faster manner as per
their requirements as well as expectations. As a result of this, the determination and confirmation
of clients' business needs allow an organisation to retain the clients for a longer time period in
future context of time. This implies entailment of higher revenues and profits on the part of the
organisation from the clientele.
4. What is a Software Requirements Specification (SRS)?
A Software Requirements Specification (SRS) can be comprehensively said to be the
documentation which defines what will be done by the software along with how will it expected
to carry out its performance. In addition to this, it further lays down the functionality that the
offerings of the company need to offer in a bid to makes sure that all the needs and demands of
the stakeholder groups are effectively met as per their interests. Besides this, Software
Requirements Specification (SRS) describes the way in which the software will interact while
being incorporated within the hardware or while being connected to any other software. Now, it
4

is well known that a basic SRS encompasses a purpose, an overall description and certain
requirement.
5. What is the difference between a functional and a non-functional requirement?
Functional Requirements Non Functional Requirements
This describes a system or their components. It describes the quality attribute for any
software system.
This defines the working of the software
system.
This puts restrictions upon the way in which
the software system meets the functional
requirement.
These are made specific by the user. These are made specific by technical persons
such as software developer, technical leader,
architect and so on.
This is considered to be mandatory. This is regarded to be non mandatory.
This is captured in the form of use case. This is captured in terms of a quality attribute.
This is described at a component level. This is applicable to the system as a whole.
It provides assistance in verification of
functionality of the software.
It renders aid in verification of the
performance delivered by the software.
Functional testing such as integrator, system,
end to end, API testing, and so on are carried
out.
Non functional testing takes place in terms of
stress, usability, security testing, performance,
and many more.
It is relatively easier to describe. It is relatively more difficult to describe.
6. What is a functional requirement? Provide an example.
Functional Requirements: These are considered to be the requirements which are
demanded by the end users in the form of basic facilities which the system is expected to
provide. All of such functionalities are required to be essentially integrated within the system as
part of the overall contract. These are demonstrated in terms of input to be fed into the system,
the operations which are performed and the expectations in terms of output. These are
5

fundamentally the requirements which are mentioned by the users that they can directly look
upon within the final offering, dissimilar to the non functional requirement. Example: Some of
the examples of functional requirements are listed beneath:-
 Validation of user when he/she logs into the system.
 System close down in the event of any cyber attack.
 A Verification email being sent to the user in an instance whereby he/she registers for the
first time on any of the software systems.
7. A waterfall model is a type of __________ development methodology?
Iterative
Sequential ✔
8. Describe 4 different methods of collecting information
Questionnaire: A questionnaire can be defined as a research instrument which is put to
use in a bid to collect data via respondents by asking from them, series of questions.
Focus Groups: It can be defined as a small group discussion whereby participants give
responses to a series of enquiries mainly centred around a specific topic.
Observation: This can be defined as a method of collecting data whereby information is
gathered by analysing and looking upon things and activities in a detailed manner.
Interview: It can be defined as a structured conversation whereby one participant makes
enquiries and the other person gives the solutions.
9. Describe the meaning of the following terms:-
Quantitative Research:
This can be referred to as the procedure of gathering as well as analysing the data
expressed in terms of numbers. It can be put to use for the purpose of finding average, pattern,
making forecast, testing casual relationship, generalising results onto wider base of population.
Qualitative Research:
This encompasses collection as well as analysis of non numeric data such as audio, text
or video for comprehension of opinion, ideology, views and concepts. This is usually put to use
for the purpose of gathering detailed knowledge of an issue or generate newer ideas for the
study.
Mean:
6

Within a data set, mean is calculated by adding up all the numbers in the set and dividing
the total arrived at with the quantum of values in that particular data set.
Median:
Within a sorted series of numbers, median is acknowledged to be the number which
appears in the exact middle. It holds the capacity of describing the data in a more effective
manner as compared to the average of series.
Secondary Research:
This is a kind of research whereby the information is gathered by way of accessing
already published information or data gathered by other researchers in the past. The main sources
of secondary research are identified to be books, journals, magazines, articles, and so on.
Boolean Operators:
Boolean Operators are simple words (AND, OR, NOT or AND NOT) used as
conjunctions to combine or exclude keywords in a search, resulting in more focused and
productive results. This should save time and effort by eliminating inappropriate hits that must
be scanned before discarding.
CONCLUSION
The above discussion has led to the inference that there is vital importance of gathering
information related to business needs and requirements of clients. This empowers an
organisation to effectively ensure the fulfilment of such demands in stipulated course of time.
This in the long run helps in retention of clients for a longer period of time.
7

REFERENCES
Books and Journals
Wiegers, K. and Beatty, J., 2013. Software requirements. Pearson Education.
Chang, J.Y., Wang, E.T., Jiang, J.J. and Klein, G., 2013. Controlling ERP consultants: Client and
provider practices. Journal of Systems and Software, 86(5), pp.1453-1461.
Daneva, M., Van Der Veen, E., Amrit, C., Ghaisas, S., Sikkel, K., Kumar, R., Ajmeri, N.,
Ramteerthkar, U. and Wieringa, R., 2013. Agile requirements prioritization in large-
scale outsourced system projects: An empirical study. Journal of systems and
software, 86(5), pp.1333-1353.
Mamabolo, M.A., Kerrin, M. and Kele, T., 2017. Entrepreneurship management skills
requirements in an emerging economy: A South African outlook. The Southern African
Journal of Entrepreneurship and Small Business Management, 9(1), pp.1-10.
Kulak, D. and Guiney, E., 2012. Use cases: requirements in context. Addison-Wesley.
Yeoh, W. and Popovič, A., 2016. Extending the understanding of critical success factors for
implementing business intelligence systems. Journal of the Association for Information
Science and Technology, 67(1), pp.134-147.
Venter, C. and Goede, R., 2017. The use of critical systems heuristics to surface and reconcile
users' conflicting visions for a business intelligence system. Systemic Practice and
Action Research, 30(4), pp.407-432.
Ballard, C., Farrell, D.M., Gupta, A., Mazuela, C. and Vohnik, S., 2012. Dimensional Modeling:
In a Business Intelligence Environment. IBM Redbooks.
Ahmed, N., 2014. Deriving security requirements from business process models (Doctoral
dissertation).
Chen, A. and Beatty, J., 2012. Visual models for software requirements. Pearson Education.
Authority, F.C., 2015. Developing our approach to implementing MiFID II conduct of business
and organisational requirements. Londres: Financial Conduct Authority.
8