Business Requirements Analysis

This document discusses the concept of business requirements analysis and proposes a technology system for JenJin Translations. It explores the methods of collecting and eliciting requirements through interviews and prototyping.

Business Requirements Analysis Assignment 4
Proposed approach to requirements elicitation
Your student ID:
Introduction
Translation and interpretation are considered as two vital part of the communication techniques as
it enhances the way of communication by sharing the ideas, knowledge and information between people
regardless of their original language. Jenjin Translations is one Victoria based translation and
interpretation service provider, which intended to provide efficient translation service for several
languages such as Greek, Russian, Italian, Hindi, Korean and Mandarin. However, the growing customer
demand sometime create difficulties in scheduling jobs for the staffs. This report will focus on a
technological solution in order to trigger the noticeable issue along with the end user and their
characteristics. Apart from that, the report will also emphasize on the collection and elicitations of the
requirement followed by their method of application. Moreover, the suitable requirement elicitation
method for Jenjin Translation is going to be described here.
Proposed Technology system for JenJin Translations
Prior to proposing a suitable technology for the organization it is necessary to acknowledge the
issue occurring in the discussed organization. The discussed translation an interpretation service provider
Jenjin translation has gained immense popularity due to its advance and timely service provided to the
customers. However, it sometime create issue for the organization to handle the increasing customer
demand by the staffs. Hence, the staffs of the translation and interpretation organization look forward to an
innovative technological solution in order to enhance the customer service.
Computer Assisted Translation (CAT) technology
In order to address all the occurring issues installation of a Computer Assisted Translation (CAT)
tool will be one best solution. Though it is not one automated translation tool, yet it can definitely
advantageous to the organization as it can reduce the real human translation time resulting in provide more
accurate service in less time. Moreover, it is obvious that the linguistic and design errors present in the
source text might not be trigger by human translation, but having a CAT tool will definitely ensure
improve quality along with maintain consistency of the translation.
The working procedure of a typical CAT tool such as memoQ begins with breaking the entire line
of source text into small translatable segments. After that the translated segments are saved into the
translation database along with the source text. Furthermore, the search facilities in the chosen software
tool facilities the human translator to access the saved translated segments or fragments in any time for
reusing those either in the same or else in one different document. The vital concern of the chosen tool is
to ensure the writing style and the terminology of the source material to be translated accurately. The
features that one efficient CAT software includes are as follows;
 The autosuggest feature exist in the CAT software tool provides recurring of the words as well as
eliminate the need of retyping the same words repeatedly.
 There exist a quality assurance feature in order to ensure the accurate transmission of omissions as
well as the numerical inconsistencies.
 A side-by-side alignment allow the translator to compare the source segment with the target text in
a side-by-side manner as well as help to maintain the existing workflow by hindering the translator
from getting confusion and lost among two similar documents.
Apart from the above the CAT tools also have several features that provides the flexibility to work

Business Requirements Analysis Assignment 4
with different verities of documents such as a Power point Presentation, avoiding the need to convert the
provided text into different file format.
End users proposed system and their characteristics
The end users for the systems would be the clients of the organization who are to get their work
done by the system and the Translators, interpreters and other staffs of the organization. The staffs would
be interacting with the systems to view the jobs available on the system and perform them. They would be
accepting the jobs suitable for them and complete the jobs on time. The clients would be able to make the
payment to the systems obtain their work and invoice in time with the help of this system.
Employees
The end users in the system would be performing the role of an employee and their actions can be
categorised into two different sets of users, the interpreters and the translators. The interpreters would be
performing the tasks of interpretation. The main functionalities to be performed by the interpreters and the
translators are logging into the system and viewing the jobs available for them. They are to select a
particular job and perform the job according to the requirements. After they have selected a job that they
intend to perform they would be able to set the status of the work. This system would be helpful for them
in operating efficiently and carrying out the tasks in their system efficiently.
Clients
The clients in the system would be the individuals that would be submitting the work to be done
and the related files to be uploaded in the system. The clients would be again bifurcated into two sets of
users, one of them being the individual clients and the other being the organizational representatives. The
clients would obtain the results from the translations and make the payment after receiving their desired
solution. The system would be available for the clients 24x7 as they would be able to obtain results from
the system at any time that they desire. The system would be sending an invoice to the clients in the
response to the payments made by them.
Two approaches to collect and elicit their requirements
The concept of requirement elicitation is the vital segment for the accomplishment of any kind of
software projects. Furthermore, the concept can be well understood by the activity of collecting or
researching all the requirements from the users, stakeholders or else the customers who are involved in
practicing any kind of software. Though there exist a number of requirement elicitation method; yet it is
albeit that any single technique will always prove as effective; that is it can be explained that one single
technique of requirement elicitation may not always suitable for all the software testing projects. However,
in order to achieve more appropriate information as well as review of the existing software, the
organization can look forward to any of the available elicitation techniques based on the nature of the
ongoing project, political climate, preference, strength and the organizational market reputation. The most
discussed requirement elicitation techniques are as follows;
Interviews
Face to face interview is one of the best practice of collecting the appropriate and relevant data
regarding the research. Interviews provide the flexibility to the surveyor to collect a huge amount of
information rapidly. Moreover, the procedure of interviewing the best process of defining the variation to
customers as there exist a chance to convey the possible positive solutions if there exist any kind of
negative remarks.
Prototyping
In order to add comparatively more attention to the research, the latest form of collecting
requirement elicitation is prototyping, which allows to collect the basic requirements for building one
initial sort for clarification, broadly known as prototype. Furthermore, prototyping can be described as one
of the valuable and efficient device suitable for the business analyst for deciding whether the created
solution actually match the user’s demand of requirement or not. This technique also facilitates the
stakeholder to provide necessary suggestions or required changes prior to the implementation of the
business plan.

Business Requirements Analysis Assignment 4
Methods of application of requirement elicitations
The appropriate methods for collecting the above discussed requirement elicitation are as follows;
Methods of applying Interview
In case of collecting the required information in an interview, the interviewer needs to stay calm as well as
active, and additionally, the interviewer also needs to possess clear idea about the structured as well as
unstructured format of interview. The structured interview has a pre-set plan and according to that plan the
interviewer asked several questions to the users. Moreover, in such cases, sometime open questions are
also require to be developed. However, in some cases, if necessary, the interviewer needs to maintain
confidentiality and hide the identity of the customers.
Methods of applying Prototyping
In order to apply the prototyping approach to collect the user requirement elicitations for the purposed
system broadly follow six steps.
Creating one prototype: A prototype can be consider as one of the initial model of the product, normally
possessing limited functionality in order to build a test design concept. However, there exist a number of
ways and numerous tools including the online application as well as offline software of creating an
effective prototype. Tools like InVision, Adobe Experience design, Axure RP, UXpin, and Marvel can
consider as vital tools in order to create an appropriate prototype. However, above them all, marvel is the
most prominent tool, which is a great web and mobile application, possessing incredibly simple way of
creating and sharing the prototype. Apart from creating and sharing the prototype, this particular tool
provides the facility of a handy sketch plugin for more appropriate application.
Coming up with an effective test plan: Regardless of the type of requirement elicitation method, it is vital
to lay out one suitable plan in order to carry out the test. Hence, prior to carrying out this method, the
person associated with the requirement collection method need to create a clear vision on what exactly the
feature and functionality of the test, the measurement method that is calculating the success and failure of
the process, and a suitable set of questions. Apart from that, one spread sheet also need to be created prior
to the beginning of the session, containing the name of the users, features of the service to be tested, along
with a column for suggestion of improvement.
Recruit the target user: It might turned out to be easy and simple if the researcher intended to conduct the
research process with the existing users. Conducting the research process by taking the opinion of the sales
team and the stakeholders associated to the organization. Apart from that, using social media network such
as Facebook might turned as effective in some cases. However, it is necessary for the researcher find most
unbiased participates or users for collecting most prominent opinion.
Finding of suitable location: Finding one suitable testing location is as important as finding the unbiased
participates A well-focused participate will definitely provide most appropriate suggestions. However,
conducting remote testing via Hangout or Skype might turned out to be distractive, resulting in failure of
the research. Nevertheless, finding compatible requirement elicitation location with least distraction will
add more value to the particular process.
Moderating the test: The quality of the requirement elicitation methods is heavily biased towards the
ability of running the interview. Furthermore, in order to carrying out an effective research, the researchers
have to be unbiased as well as make it ensure that the participants will experience a well-behaved session.
Moreover, it is the responsible of the researcher to record the session with an appropriate screen recording
software while conducting a real time remote sessions. QuickTime, Screenflick are the most used screen
recording softwares used by the researchers.
Documentation of the result: Summarizing and distilling the findings in a spreadsheet or making a proper
documentation is necessary in prototyping. Furthermore, this particular process will be helpful in
identifying the issues and the associated areas of improvement will be simpler. A typical documentation
process includes a spreadsheet with the research notes, an audio or screen recording, along with the
webcam recording if necessary.

Business Requirements Analysis Assignment 4
Potential benefits and issues related to the considered approaches
Benefits and issues related to the interviewing approach
The main benefit that is obtained with the interview process as it helps in investigating the issues
deeply. This helps in gathering information that turns to be beneficial for the organization and allows the
interviewers collect detailed answers. The responses of every interviewee get recorded based and this
helps in evaluating the results. While conducting the responses it is ensured that the data collected is
authenticate and this also helps in making effective results regarding an issue. It helps in conducting one to
one interview and also ensures that the result that is gathered is authenticated. This will protect the
integrity of the results created.
The major issue that tends to arise with the interview process is that it turns to be one of the most
time consuming process. Setting up an interview becomes a difficult aspect and analysing these results
also becomes difficult. Thus interview process turns to be one of the most costly processes. Apart from
this one more problem that is being faced with the interview process is that it becomes difficult to
understand the perspective of different interviewers. This has the potential to impact the results that are
obtained from interviewees.
Recommendation for overcoming the issues
The following activities may help the interviewer to trigger the issues that might occure during an
interview;
 Making a set of clear research questions
 Developing efficient checklist for each questions that are supposed to be asked in an interview
 Ensuring the clarity of the interview via a clear expression of the interview purpose.
 The researcher need to start with one general or else a neutral question to the users in order to
facilitate a free and clear flow of information.
Benefits and issues related to prototyping
The vital benefit that comes into mind while conducting the prototyping is that, the particular
process reduce the time and cost of the research. Moreover, it enhances the quality of specifications and
requirements provided to the users. Apart from that, with this process of collection of the requirement
elicitation, the researcher can determine what exactly the user want with the help of faster as well as less
expensive software. With this process, the customers can provide immediate feedback, as the process
highly requires customer involvement as well as facilitate them to interact with the working model of the
project.
However, there exist some limitation to the particular process of requirement elicitation, which
need to be weighed before taking the decision of its implementation. In any worst case situation, an
inefficient prototyping can create high customer confusion, which may lead to the failure of the research.
Moreover, a limited prototype analysis might cause hindrance in effectively analysing the entire project.
Apart from that, the potential for integrating a number of additional improvement might stretch the time
and make the research process long.
Recommendations for overcoming the issues
Though, after several revisions, there might exist the possibility of error; yet, there exist some
strategies to minimize the chances of errors and issues occurring during the time of research elicitation
process via prototyping. Allocating one efficient team in order to handle the real time errors can enhance
the process of conducting the research. Apart from that, maintaining a proper documentation such as
maintaining the spreadsheet, gathering the appropriate audio and video of the session can nullify the issues
in the process. Moreover, for making the collection process more effective, it is necessary for the

Business Requirements Analysis Assignment 4
researcher to stay unbiased and maintain confidentiality of the users if necessary.
Suggested approach for collecting and eliciting users’ requirement
It is suggested that the elicitation approach required to be adopted for the gathering of the
information required for the development of the system is the method interview. The interviews would be
aimed towards the staffs and the clients of the organization. In addition to this, the method is suggested
here for this approach as this would be helpful for the organization as they have a large sample data to
collect and analyse for the gathering the requirements regarding the development of the system for the
JenJin translations organization. This approach would be making sure that the data is collected efficiently
and the analysed data received would be appropriate.
Conclusion
For conclusion it can be said that the development of the report has been done in accordance to the
JenJin case study. The report consists of the development discussions of the information system for the
Jenjin translation of the organization. The report consists of an introduction to the organization and the
requirements for the organization. The organization needs to develop an information system and the
details of the development have been included in this report. The requirement gathering process which
would be providing the details of the methods and functions to be included in the system that is developed
for the organization. The discussions have concluded that the interview process is to be selected and the
issues and benefits of it has been described here. In addition to this, the illustrations have been included in
the report, which would be helpful for the readers to make an idea about the system that is to be developed
for the organization.

Business Requirements Analysis Assignment 4
6 of 12

Business Requirements Analysis Assignment 4
Your model
Use cases diagram and event flow description for one complex use case
The complex use case selected for the description and the diagram, is the job assigned use case.
The fully functional description of the job assignment process for the JenJin Translators has been
described in the table provided below:
Use Case Number UC6
Use Case Name Confirm Job Assignment
Use Case Description The translators and the interpreters would be able to view the
tasks available to them confirm the jobs once they accept them.
Actors The main actors for the system are the translators and the clients.
Pre-Condition Accept jobs
Post-Condition Start jobs
Process Flow User System
1. Login
2. View Jobs
3. Accept Jobs
4. Confirm Job Assignment
1. Authenticate
2. Display jobs
3. Allocate jobs
4. Store Details
Exceptions An exception takes place in case the interpreter or the translator
does not accept the job.
Use cases diagram and sequence diagram for one complex use case
7 of 12

Business Requirements Analysis Assignment 4
The sequence diagram for the use case scenarios described above is provided below:
8 of 12

Business Requirements Analysis Assignment 4
Domain class diagram
The Domain class model for the JenJin Translators organization has been described below:
9 of 12

Business Requirements Analysis Assignment 4
10 of 12

Business Requirements Analysis Assignment 4
Bibliography
Cats, O. and Loutos, G., 2016. Real-time bus arrival information system: an empirical evaluation.
Journal of Intelligent Transportation Systems, 20(2), pp.138-151.
De Vasconcelos, J.B., Gouveia, F.R. and Kimble, C., 2016, July. An organisational memory information
system using ontologies. In Atas da Conferência da Associação Portuguesa de Sistemas de Informação
(Vol. 3, No. 3).
Dumais, S., Cutrell, E., Cadiz, J.J., Jancke, G., Sarin, R. and Robbins, D.C., 2016, January. Stuff I've
seen: a system for personal information retrieval and re-use. In Acm sigir forum (Vol. 49, No. 2, pp. 28-
35). ACM.
Jensen, R.E., Moinpour, C.M., Keegan, T.H., Cress, R.D., Wu, X.C., Paddock, L.E., Stroup, A.M. and
Potosky, A.L., 2016. The Measuring Your Health study: Leveraging community-based cancer registry
recruitment to establish a large, diverse cohort of cancer survivors for analyses of measurement
equivalence and validity of the Patient Reported Outcomes Measurement Information
System®(PROMIS®) short form items. Psychological Test and Assessment Modeling, 58(1), p.99.
Krajewski, W.F., Ceynar, D., Demir, I., Goska, R., Kruger, A., Langel, C., Mantilla, R., Niemeier, J.,
Quintero, F., Seo, B.C. and Small, S.J., 2017. Real-time flood forecasting and information system for the
state of Iowa. Bulletin of the American Meteorological Society, 98(3), pp.539-554.
Laudon, K.C. and Laudon, J.P., 2016. Management information system. Pearson Education India.
Liu, X., Wang, X., Wright, G., Cheng, J., Li, X. and Liu, R., 2017. A state-of-the-art review on the
integration of Building Information Modeling (BIM) and Geographic Information System (GIS). ISPRS
International Journal of Geo-Information, 6(2), p.53.
Tarhini, A., Arachchilage, N.A.G. and Abbasi, M.S., 2015. A critical review of theories and models of
technology adoption and acceptance in information system research. International Journal of
Technology Diffusion (IJTD), 6(4), pp.58-77.
Theorin, A., Bengtsson, K., Provost, J., Lieder, M., Johnsson, C., Lundholm, T. and Lennartson, B.,
2017. An event-driven manufacturing information system architecture for Industry 4.0. International
Journal of Production Research, 55(5), pp.1297-1311.
11 of 12

Business Requirements Analysis Assignment 2 – Part D
12 of 12