HND 8-Systems Analysis Design Assignment - G. Kasun Peiris
HND 8-Systems Analysis Design Assignment - G. Kasun Peiris
HND 8-Systems Analysis Design Assignment - G. Kasun Peiris
Assignment Brief
Student Name G. Kasun Madushanka Peiris
Unit Number and Title Unit 34: Systems Analysis & Design
General Guidelines
1. The font size (Body text) should be 12 point, and should be in the style of Time New Roman.
2. Set line spacing to 1.5.
3. Justify all paragraphs.
4. Ensure that all headings are consistent in terms of size and font style.
5. Use footer function on the word processor to insert your name, unit, assignment no, and page
number on each page. This is useful if individual sheets get detached from the submission.
6. Use the spell check and grammar check function of the word processing application to review the use
of language on your assignment.
Important Points:
LO1 Evaluate the strengths and weaknesses of the traditional and agile systems analysis
methodologies
The submission is in the form of an individual written report. This should be written in a concise,
formal business style using 1.5 spacing and font size 12. You are required to make use of headings,
paragraphs and subsections as appropriate, and all work must be supported with research and
referenced using the Harvard referencing system. Please also provide a bibliography using the
Harvard referencing system.
Deploy Technology (DT) is a leading IT company in Sri Lanka. You are selected to work
as a Business Analyst at DT company. One of their clients who currently use traditional
analysis & design methodologies and intending to go for agile methodologies, have
requested the firm to conduct a study on Evaluating the strengths and weaknesses of
both approaches and produce and present a written report to them. Your manager has
selected you for this assignment.
You are required to carry out the following task (along with its sub tasks) in terms of
completing this assignment.
Task 1
1.1 Discuss the traditional and agile methodology including their features, their
usefulness and limitation of each approach. (LO1,P1)
1.2 Compare and contrast the strengths and weaknesses of these traditional and agile
systems analysis methodologies that you identified. (LO1,M1)
1.3 Critically evaluate (give your own opinion on) the strengths and weaknesses of the
traditional and agile systems analysis methodologies
1.4 Discuss typical transition problems faced by organizations that move from the
traditional to the agile approach. (LO1,D1)
You as the Business Analyst of DT technology have to decide a new system as the
solution of changing traditional in to agile methodology.
Carryout the following tasks based on the business problem that you selected and
document your work.
Task 2
2.1 Explain the background to your business problem and propose a potential solution
for it. (LO2,P2)
Note: You may come up with more than one alternative solution if required and
applicable.
2.2 Discuss the importance, purpose and structure of feasibility study during the initial
stages when developing the new system. (LO2,P2)
2.3 Justify the importance and relevance of the feasibility criteria you assessed above,
in terms of the business problem. (LO2,M2)
2.4 Discuss the impact of the different financial, economic and technical feasibility
criteria on the system develop to the DT IT Company. (LO2,D2)
Task 3
3.1 Perform Systems Analysis for your proposed solution (system) using a suitable
methodology. (LO3,P3)
Use suitable fact finding techniques to investigate to identify user and system
requirements.
3.2 Explain how effective your analysis was in terms of the methodology that you used.
(LO3,M3)
3.3 Explain what criteria you used to select the methodology and justify your choice in
terms of your business problem. (LO3,D2)
4.2 Assess the effectiveness of your design, paying attention to the methodology you
used and how the design meets user and system requirements. (LO4,D2)
:End of Tasks
Programme:
Unit:
Plagiarism
Plagiarism is a particular form of cheating. Plagiarism must be avoided at all costs and students who break
the rules, however innocently, may be penalized. It is your responsibility to ensure that you understand
correct referencing practices. As a university level student, you are expected to use appropriate
references throughout and keep carefully detailed notes of all your sources of materials for material you
have used in your work, including any material downloaded from the Internet. Please consult the relevant
unit lecturer or your course tutor if you need any further advice.
Student Declaration
Student declaration
I certify that the assignment submission is entirely my own work and I fully understand the consequences
of plagiarism. I understand that making a false declaration is a form of malpractice.
Assignment Feedback
Action Plan
Summative feedback
I get this opportunity to wish my sincere gratitude to Ms. Prabashi Manjani helps me to complete this
assignment successfully. She gives good opportunity to improve my skills and knowledge of system
analysis and design. As a lecturer, she has given terrific advice and explained well about the content of
the “System analysis & Design” subject. Thank you so much for your support and dedication.
And thanks, my all friends and my parents help to find some resources and information’s about this
assignment and do complete and successfully this assignment. If they do not have with me, I cannot
complete this task so thank you for your support.
I would like to grant this completed assignment to everyone who supported it.
29.06.2021
Date
t
ACKNOWLEDGMENT.............................................................................................................................10
TABLE OF CONTENT...............................................................................................................................11
TABLE OF FIGURES.................................................................................................................................12
TASK 01..................................................................................................................................................13
1.1 Discuss the traditional and agile methodology including their features, their usefulness, and
the limitation of each approach........................................................................................................13
1.2 Compare and contrast the strengths and weaknesses of these traditional and agile systems
analysis methodologies that you identified......................................................................................15
1.3 Critically evaluate (give your own opinion on) the strengths and weaknesses of the traditional
and agile systems analysis methodologies.......................................................................................18
1.4 Discuss typical transition problems faced by organizations that move from the traditional to
the agile approach.............................................................................................................................20
TASK 02..................................................................................................................................................22
2.1 Explain the background to your business problem and propose a potential solution for it......22
2.2 Discuss the importance, purpose, and structure of feasibility study during the initial stages
when developing the new system....................................................................................................24
2.3 Justify the importance and relevance of the feasibility criteria you assessed above, in terms of
the business problem........................................................................................................................25
2.4 Discuss the impact of the different financial, economic and technical feasibility criteria on the
system developed to the DT IT Company.........................................................................................26
TASK 03..................................................................................................................................................28
3.1 Perform Systems Analysis for your proposed solution (system) using a suitable methodology.
...........................................................................................................................................................28
3.2 Explain how effective your analysis was in terms of the methodology that you used..............30
3.3 Explain what criteria you used to select the methodology and justify your choice in terms of
your business problem......................................................................................................................32
TASK 04..................................................................................................................................................33
4.1 Design (No need to implement) the system of DT IT company to meet user and system
requirements that you identified in the previous task.....................................................................33
4.2 Assess the effectiveness of your design, paying attention to the methodology you used and
how the design meets user and system requirements.....................................................................37
TABLE OF FIGURES
Figure 1: What is Methodology.............................................................................................................16
Figure 2: Traditional Vs Agile Methodology..........................................................................................17
Figure 3: Personal Opinion....................................................................................................................19
Figure 4: Feasibility Study.....................................................................................................................27
Figure 5: Facts-Finding Techniques (Survey Form)...............................................................................31
Figure 6: Use-Case Diagram..................................................................................................................34
Figure 7: Activity Diagram.....................................................................................................................35
Figure 8: Data Flow Diagram.................................................................................................................36
Deploy Technology (DT) is one of the leading IT companies in Sri Lanka. I was recruited as a business
analyst in that company. After join to that company my 1 st work is to write a proposal report about the
features, usefulness, strength, and weakness between traditional methodology and agile methodology
because reason is one of our clients was requested to us focus on the traditional methodology versus
agile methodology and provide to them. That all clients are currently experiencing this traditional
methodology for their projects. In this case, clients want to go for agile methodology. That is why our
clients want to get a comparison between these two methodologies. These methodologies are having on
the SDLC (Software Development Life Cycle) and there have major methodologies. Those are
waterfall, agile, spiral, and prototype. All leading companies are using those methodologies
specifically. It means by those companies are using one or two methodologies among these
methodologies for their projects. These methodologies are helping to conduct project process stable and
efficient.
When talking about the project management section methodologies are one of the major things have on
that. SDLC (Software Development Life Cycle) is the common phase of these methodologies. Simply,
those methodologies have in that SDLC. Waterfall, agile, spiral, and prototype are the major
methodologies have in that SDLC. The traditional methodology is a simple sequential cycle which use
to conduct the project. Simply, this traditional methodology is introduced as well as the waterfall
methodology. Usually, the traditional methodology is going with controllable process and simple. The
traditional methodology has majored few phases. Those phases are initiation, planning, execution,
monitoring, and closure. Most companies in past used this methodology for their projects because the
reason is this is the major and traditional methodology have in the project management process.
Mainly, this methodology is working as a waterfall method therefore this method always focuses on the
plan and outcome without any scope and not highly focus on the customer expectations. It all depends
Agile methodology is the most popular methodology among IT companies and project-based
companies. Nowadays most companies use this methodology for their project success. Typically, this
agile method gives priority to customer needs and expectations because of the reason the customer is
the most valuable metric as per this methodology. Usually, the customer is highly interacting with this
agile methodology. When talking about this method customers can anytime do changes to their project
because the reason is team is always providing demo version after the sprint (sprint is a round of
implementation and round of creating program) to the customer. After that customer can check out that
demo version and if have any changes can inform the team. Next time team will do that needful and
provide another demo version of the system. this will help to study about the system to the customer
very well. This the major feature of this methodology and this is the reason why all companies are
using this method. This agile methodology is works based on the iteration delivery model. Mainly, the
team can control the process of the project without manager involvement and it will help to provide
good output to the customer. This agile methodology is giving priority to creating software, not for the
documents of the projects and continuously test the system, and improving the system to fulfill all
customer needs and expectations. Scrum and Kanban frameworks are mostly used for this agile
methodology. Simply, this methodology helps to conduct very efficiently and archive project goals
quickly. These are the key features of the agile methodology.
when talking about the traditional methodology and agile methodology we can easily find out the
strengths and weaknesses have on that both technologies. Both these technologies are currently using
many companies because that all companies choose that methodology as per the customer requirements
and project type. Every methodology has strengths and weaknesses therefore these methodologies also
have strengths and weaknesses such as have on other methodologies. So, in that case, companies are
doing some comparison between these methodologies and after identifying the strength and weaknesses
after that choose one methodology for conduct their project based on that. It will help to get perfect
output from that project. As a business analysis of the deploy technology, I was identified the major
strength and weaknesses of both methodologies. These details will help customers emphasize and
choose the most suitable methodology for their projects.
According to the given scenario, we can do a comparison of strengths and weaknesses between
traditional and agile methodology. When talking about the strengths of traditional methodology I was
able to identify some special strengths of the traditional method. This methodology is mostly used to
make a cost-effective project. Simple, it is mean by when the company goes to a large scale of projects
company has to spend a lot of time to succeed that project and during the process of that project, will
happens any kinds of bugs and take some time to solve those bugs. On that company have to bear some
cost to that project. When using the traditional method to conduct small projects the company can
complete the project quickly with few developers and using lightweight technology to the project. This
is kind of cost-effective for the company and the customer. Another major strength is very easy to
handle and control the project do under this traditional methodology. Typically, according to this
method project manager is the handler, and it is very sequential. This methodology helps to conduct the
project very well and finish within scheduled time and other all criteria. In this method arrange and
well-defined objectives what have in the project. This method helps to preplan the whole requirement
before starting cording and it helps to reduce all errors and risks. On other hand can prepare a clean
According to this research when research the agile methodology I was able to found some major
strengths the weaknesses of that methodology. This is the most usable methodology in the world to
conduct and do projects. Nowadays most companies use this methodology to succeed in their projects.
When talking about the strength of this method major strength is the high involvement of the customer
in the project. In the present people's thoughts and expectations are changing very quickly. So, in that
case, customer can easily present their opinion and expectation to the team and the team will mainly
focus on the customer requirements. It will help to conduct the project efficiently and increase customer
satisfaction.
Typically, these are weaknesses and strengths both of methodologies. Simply, this is a comparison
between traditional methodology and agile methodology. According to my research agile methodology
is the best one for conducting projects because the reason is all are using this method and there has high
customer interaction to the project, therefore, we can give perfect outcome by fulfilling all expectations
of the customer without any kind of difficulties.
According to my personal opinion when discussing the strengths and weaknesses of these two
methodologies I can find out few things regarding this section. Mainly, when comparing these two
methodologies we have to consider about few major things before choosing a methodology for the
project. Both methodologies have strengths and weaknesses it is a very common phase for both
methodologies. This method is depending on the projects and customer requirements. Nowadays most
companies are using agile methodology to conduct their projects but in the past traditional method is
very famous and efficient at that time. Over time this methodology was deceased because the major
reason is less customer interaction. As per this traditional methodology have less customer interaction
and only focus on the plan. So, in that case, the company and customer were faced with an unsatisfying
outcome of the project. Usually, during the project process customer expectations might be changing
and the customer is providing those changes to the team. At that time if projects processing based on
the traditional method team is not accepting that customer changing because the reason is that method
is using a linear structure. Simply, the customer cannot change anything of the project after starting the
project.
In the traditional method, major strengths are clear documents and well-defined objectives. Typically,
in this methodology project manager is the head and everything control by the manager. So, customers
can clear understanding who is the project handler and directly can get updates about the project meet
project manager. When considering the documentation part, it is very clear and the customer can easily
understand the mechanism behind the project. This document mentioned all processes of phases and
stages wise well. These are the major strengths have in this traditional methodology. When talking
about the agile methodology it is very famous in the world because the reason is that method highly
interactive with the customer. Whatever project customer requirements are the most major and
important thing of that project because the project also we are conducting and handling for the
customer. So, we have a responsibility to do the project according to the customer's expectations. In
agile method is fully customized. Simply, it is means by the customer can change and add anything to
the project during the project process. This is the major reason to famous among IT companies for this
agile methodology. Mainly, all companies want to give good quality service with high satisfaction
project outcome to the customer. That will help to increase the brand and reputation of the company.
Mainly, very difficult to measure the progress of the project and take time to finish the project cannot
provide an estimated date about finishing because directly customer has interacted with the developer.
Simply, customers cannot get any idea of the budget of the project. That is not fixed. The cost will
depend on rounds of iterations and resources. The overall design not providing any kind of correct
architecture of system UI and UX both, so that case customer has to face problems works more with
that product. These are the major weaknesses have in this agile methodology. According to my opinion,
this is suit for large-scale projects but this also depends on the project and customer requirements. I
thought the agile method is suit for complex projects and the traditional method is suit for small or
medium-scale projects. Both are good but the thing is the traditional method is no longer usable now
trending is an agile methodology that might be changing in the future because the reason is this field is
updated with new technology every second. My expectation is agile methodology is good for conduct
projects very successful and efficient. It can fulfill all expectations of the customer.
According to the scenario, customers are requested to discuss and emphasize the traditional
methodology and agile methodology. In that case, as a newly recruited business analysis of the Deploy
technology company assigned to write a report about these methodologies. Simply, I was present the
strength and weaknesses of these methodologies through this report. It will help to choose customers
which type of methodology is most suit for their projects. Usually, our all customers and team have a
lot of experience with the traditional methodology. Previously most clients are a preference to go
traditional methodology but now it was changed and clients are requesting to us emphasize the agile
methodology and which one is the suit for them. So that case our company wase decide to provide the
answer for this all questions as a written report includes with all details about these methodologies. I
was previously mentioned above the weakness and strengths of traditional and agile methodology.
In this section, I am presenting the details about which kind of problem we have to face when we
transition from traditional to agile methodology. Typically, these details valid for customers and the
company because our team also have not enough experience with the agile methodology. This is not
easy work to transition agile methodology quickly for that team members must have well experience
about the agile methodology or hire new experienced employees to the company to conduct this agile
methodology. As per my research, I was able to find a few major problems when we have to face the
transition from traditional to agile methodology. Those major problems are,
When we considering and plan to shift to the agile method you must have an emphasis on the company
expectations. Simply, it means by we have to find out why the company is the shift to agile
methodology and which kind of things the company expects from that agile methodology because agile
is always consider the vision and developing tools not for the paper works. If cannot solve problems
which have inside of your project to agile methodology, it will be a reason to frustrating and exhaust.
Simply, when the organization is finding new and experienced works get to the company and company
marketing team is always gives high promises such as “quickly finish the project” to the customer. It
will not suit agile methodology to that company because the reason is agile methodology is getting
considerable time to close the project.
When talking about the changing of the company environment and methods employees are fearful to
adapt to that because the reason all employees have certain habits around their working environment
and work base. This is a very common thing and it will help to increase their productivity and work
speed. For example, we can get a manager who conducts daily one-hour meetings to improve their
mindset and skills regards to the project with a motivational speech. I tell to that manager do not to do
this daily and use daily standups or Kanban board for the present overview, that will be a not good
suggestion for that manager and he cannot rapidly move on to that. In this case, the most important
thing is providing a practice session for the team members and given a good clear idea and vision about
the agile methodology. It will help to understand that and reduce the fear and anxieties that have on
new changes.
When fast move on to the agile method company is trying to given good practice and training agile
methodology to their employees. That is one of the many things have in the agile method. Most of the
time that will be scrum, lean, and Kanban, or any other methods are a part of agile. For example, if you
know the law of tennis, therefore, you cannot be a good player in a tennis game such as this
methodology also works based on that if you know the all theory of agile methodology you cannot be
professional in that. Wants to be a professional in this agile methodology you must practice and more
focus on the method’s height, width, and length. It will help to handle the agile method like a pro.
Another problem is faced by the company when following and implementing an agile methodology for
the first time is appreciate the success of implement the agile method. Usually, the company is
following and chooses content paper to measure the spread of the agile method in the company.
Simply, they check out how many teams are using the agile method and how many projects are running
based on this agile method and appreciate that count of spread. If we can check how was agile useful to
fulfill their company goals, that is better than appreciate. Such as how is the growth of business and
how projects are done.
When emphasis to the problems which is face when a transition from traditional to agile methodology
has a lot of problems and I was mentioned about that in above. In that case, according to scenario 2, I
was able to find out several problems during transition. When talking about the problems, the major
problem is we have to face during that transition is the less knowledgeable and experienced team
members about the agile methodology. It is very hard to conduct and convert to the agile method.
Typically, on that situation company management try to give training session or provide courses about
the agile methodology and employees must join for that session. It may not be as productive as the
organization hoped. So, that the best way to give understanding about the agile company must give
practical sessions and practice about the agile method. Simply, it is mean by study while working. For
example, the traditional method is given major to documentation part but agile is give priority for the
development software. In that case, team members have accustomed to the documentation and it’s
difficult to convert to the work with development tools. On the other hand, the team member has no
idea about how to build a conversation with the customer because the reason is traditional method has
less customer interaction and agile has critically that. Usually, it is person-oriented. These kinds of
things we cannot study theatrically, we must do these things as practical learning. As a business
analysis of DT technology, I have a responsibility to encourage team members for this transition and
help them to improve their knowledge of agile methodology.
The feasibility study is an analysis method considering account, legal, technical, and schedule relevant
to the project and gets an idea about the probability of success of that project. Mainly, this feasibility
study uses project managers before invest money and time in the project because the reason is it is
helpful to get an idea about the project success rate and status. Simply, this is kind of a prediction about
the future status of the project before undertaking the project and using relevant factors to determine the
pros and cons which have in the project. It will help to restrict unnecessary risky projects come into the
company. When talking about the feasibility study, it is divided into 4 parts. Those 4 parts are technical
feasibility, financial feasibility, market feasibility, and organizational feasibility. These 4 parts help to
do this test every part very subtly which have in the project.
The feasibility study is a test to check the practicality of the project. Mainly, we ask this test: does this
project become a success? Do we have enough resources, tools, and people for this project? Usually,
we can use this test to check our project estimate status before we start the project. It will help to
choose a good project and tempting to consider all parts of the project subtly. These feasibility studies
are very important to conduct a successful project. In that case, the business can identify the major
problems were come from the project and identifying the funding and increase level of business. This
feasibility study's major aim is the convincing the importance of feasibility to the customer, inverters,
and banks. Directly, it will be affected to the raising business. This is why very important to the project
is we can get the correct image of that project. In that case, all team member is focused about every part
very subtly and it will help to reduce some major problems have in the project. On the other hand, we
can find out new opportunities during this process. As a business analysis, I can identify the major
valuable reason to undertake the project. According to this system, I can identify the weakness easily
before the execute this project and system. it will help us to easily stop the project before starting and
waste our valuable time. Feasibility is a must for do every project before starts and it show off the real
status of the planned project. These are the importance of the feasibility study and these are the reason
why very important to do the feasibility study for the project before starting or execute.
In previously I was mentioned above what is the importance of the feasibility study, in this section
going to discuss and explain how feasibility study is important to the relevant system. when talking
about the feasibility study as a business analysis I can find out the future status of the relevant project
using this feasibility study. Simply, this test will help to identify the major reason for undertaking this
project and can estimate (prediction) the budget and resources of this project. It will help to get an idea
about the project before we start the project. Typically, this system is a simple mobile application for
study agile methodology. As a business analysis, I am introducing this website for the team members
for developing their knowledge about agile therefore this system should be always a very user-friendly
and simple application to the team members with great UI. The reason is it will support attractive team
members to this app and invest their valuable time for the valuable thing. So, in that case, the quality is
very important and I use feasibility study to save and improve the system quality.
According to the system, this feasibility study is very helpful to get the full idea of the project vision
and every objective is well identified. Mainly, I can get a well understanding of every stage of project
planning, design, development, and execution. When during this feasibility study process as a business
analysis I was able to find some issues have to in the future. For example, if design this UI to advance it
may not be very user-friendly to the team members. Financially I was able to find unnecessary costs
have in the project before executing the project. I was found direct and indirect costs have in the project
and all benefits of the project. It will help to identify and make ideas about the relevant project before
the start and save time and cost. Technically this feasibility test was helped to choose the best
technology which most suitable for the system without any difficulty such as programming languages,
UI design, Database, Functions and Features, and other kinds of things related to the technical part.
Simply it was helped to conduct and produce a perfect outcome for the team members. On the other
hand, this feasibility study was helped to find out all other things relevant to the project such as team
member's feedback about the system and how many users are going to use this system therefore, as a
business analysis I can fulfill all my expectations and user’s expectations. Simply, this feasibility test
provides perfect prediction about the project and upcoming issues of the project. This feasibility study
is very important and must do before executing the project and it will help to reduce unnecessary things
have in the project without any problem.
When discussing the differences of the financial, economic, and technical parts which have on the
feasibility study, those sections strategies are different from each section. So, in that case, we can do
correctly feasibility without these sections because feasibility is the combination of that stages.
Typically, it is helpful to check every part of the project subtly. Every company does this feasibility test
before the start or execute the project because this test will display the future status of the project and
we can get an idea about those details is this project conduct or leave? This method helps to save time
and money for the whole team and company. Indirectly this method works as a filter for filtering what
project is good for conduct and undertake. It will indirectly affect the reputation and brand name of the
company. As a business analysis, I have a responsibility to protect the reputation and the brand name of
the company that case I will use this feasibility study for every project what comes to the team and
company.
According to this feasibility study check the project using 4 iterations (sections). Those sections are
Financial, Technical, operational, and organizational. We check this system on these 4 sections.
Mainly, in financial feasibility, we are checking our system for how long economically feasible.
Simply, it is means checking about the expenses of the system such as staff, budget, technical expenses
likewise. Typically, this expense is divided into 2 parts. The 1st part is definite expenses and 2nd one is
indefinite expenses. When concern definite expenses, it is checked and calculating expenses of software
and hardware of the system and other all direct expenses which happen on the project such as staff cost,
maintains, etc. on the other hand, indefinite expenses checkout the indirect expenses which happen in
the project such as cost of conducting tests and finally display the benefits of the project.
When talking about the technical feasibility, it will check out how compatible and interact new
technology to the system such as checking new programming languages, databases, frameworks, etc...
simply it will display which kind of technology most suitable for the system. it will help to produce a
good outcome and stable conductivity to the project and system
Survey
The survey is an online question form (feedback) conducts online and anyone can give the information
online for this survey. In this source we can get information’s from a large number of participations &
can get the idea of all information’s from numeric values and graph system. We can use google form as
a survey to gathering data from people.
Observation
Observation is watching & focus on someone and after getting an idea about his behavior, talking sense
and special skills like that information covert to numeric data. For example, if the interviewer interview
some guys and focus him which words are the participations most used and that information convert to
numeric data how many words, he used likewise.
An Interview can get the whole idea about the quality of gathering information. Then interviews can
conduct structured, semi-structured & unstructured. Interviews help to gather data directly from the
relevant persons. Usually, it is used from the past to the present because this technique is very common
and famous and many times this interview happening between team and users or team and customers. It
is depending on the project.
Group discussions
In this case, we can get idea information’s from some medium type of group discussions. Example:
some related community group discussion. Usually, this group conversation is built between each
member. Simply it is means by the team members are sharing their opinions among team members.
Prototype
Another fact-finding technique is prototyping, which collects the system's requirement facts.
Prototyping is the process of sampling a small working model that is more closely tied to the pre-design
of an information system. When examining realty, prototypes can be produced at an earlier stage of the
system development life cycle. Breakthrough prototyping refers to the process of prototype facts to
describe the end user's requirements.
According to my project survey form technique is a fact-finding technique. This technique is very easy
and most suitable for the current pandemic situation to gathering requirements or finding facts. So, in
that case, I am chosen this technique. Simply, it will help to gather information from the large scale of
society and members (users) or customers but my system is going to some average scale of members
therefore I will conduct this technique to gathering information. This survey form technique is most
suited to my project because team member opinion is very important for this system.
when the emphasis on the fact-finding techniques there have few efficient techniques to use for data
gathering among those techniques, I was selected the survey method to conduct my project requirement
gathering section. It was helped to conduct requirement gathering part though the online at this
pandemic situation. Usually, I am using Google forms to conduct this section. This Google form helps
to get the whole idea percentage vise members opinions. I am providing some major questions as a
google form to the team member via WhatsApp or Email after that member is the respond to the form
and finally, I can see the whole response as a one form get the idea about the system and functions of
the system. it is more efficient and easier to respond to the members. Simply, this technique is very
user-friendly and at no cost (totally free). This technique’s accuracy level is high than other techniques
because human involvement is low and error probability also low. nowadays all people are using at that
situation this is the best way to gathering requirement from the members because all are using internet
and mobile phones that will help to respond easily to the survey form. This technique is highly affected
to the project success. Typically, the requirement gathering section gets early stage of the SDLC
because the reason is that is the major thing of the project therefore as business analysis, I have
responded to choose the best fact-finding technique for the data gathering. That will help to get the
perfect outcome from the project with a satisfying product. There have few strengths,
Fast Service: On average, the time required to complete an online survey project is two-thirds that of
traditional research methods. You don't have to wait for paper surveys to be returned because the
information is obtained automatically response time is virtually quick. According to online marketing
experts, more than half of the answers are obtained within the first three days of the campaign.
Easy to use participant and Researcher: The majority of individuals who have access to the Internet
prefer to do surveys online rather than over the phone. With an online survey, participants may take the
survey at a time that is convenient for them, and the time required to complete the survey is
significantly less. Questions that are irrelevant to a specific participant can be skipped automatically
utilizing the Skip logic feature of the Survey. For researchers, the major advantage of online surveys is
that they enhance productivity by saving time. When a more thorough analysis is required, data is
instantaneously available and may be readily imported into specialized statistical tools or spreadsheets.
Flexibility: Depending on the answer to a previous question, the order of the questions in an online
survey can be altered or questions might be skipped entirely. As a result, a survey may be customized to
each participant as the survey progresses. To summarize, online surveys are an excellent choice for
individuals and organizations seeking to conduct their research because they are less time-consuming,
less expensive, provide results faster, and allow you to transfer and use the data in a variety of
applications to answer important questions.
Honest: Market researchers have discovered that participants prefer to conduct online surveys rather
than printed questionnaires or phone interviews and that they often offer longer and more thorough
responses. People are more likely to reply honestly when surveys are designed and sent in a relevant
and focused manner.
According to the project I am using agile methodology and Google survey form as a fact-finding
technique. Mainly, I will develop this system for practice agile methodology to a team member because
the reason is we mostly used traditional methodology to conduct projects but we are decided to shift to
the agile methodology. In that case, our team is not ready for that and the reason is less experience with
the agile methodology. This system is mainly focused to improve team member’s knowledge therefore
this will be very user-friendly and great UI with illustration anime. It will help to attract to the system
and without boring experience. So, in that case, I will get some feedback and their opinion about the
system such as which kind of features implement in the system. it is very helpful to conduct a stable
project and satisfying outcome from the project. The fact-finding technique is the first stage of the agile
methodology. When talking about the survey forms, it was very effective to get valuable feedback from
the team members in this situation without any problem. This technique is more effective than the other
fact-finding techniques. Simply this fact-finding technique is working through the internet so that case
anyone can give a response to the form anywhere. This survey form is used will some stages of the
project not only for the planning section.
During the process of the project, we are releasing the Beta version to the team member as testing and
that situation also we are using survey form to get ideas and feedbacks about that prototype. After that,
we are redeveloping the system and provide the system with the suggested implementations. Typically,
this survey form is full of free and that form provides Google, SurveyMonkey websites. We can
provide questions as a questionnaire and check box methods. Simply it means by a user can provide the
answers to the questions as an essay and MCQ type. This survey form UI also perfect and we can
customize that relevant to the system. the major reason is why I am using this fact-finding technique to
gather data from the team is fast and time-saving. We can do a large scale of research also using this
survey form without any kind of difficulties and this survey form display the responses as a graph and
graphical views (Pie chart). On the other hand, we can share this form via WhatsApp, Facebook. Email
and all other kinds of messaging apps and social media platforms. The survey form is the most suitable
fact-finding technique for any kind of project nowadays. It is very effective to the project for collecting
data from the relevant person or society because the reason is that feedbacks are very important for the
project outcome and conducting. The agile method also a person-oriented methodology. in that case,
user feedbacks are very important for the project.
Data flow diagrams, often known as DFDs, are used to visually describe the movement of data in a
corporate information system. DFD covers the procedures that occur in a system to move data from the
input to file storage and to generate reports. There are two types of data flow diagrams: logical and
physical. The logical data flow diagram depicts the movement of data through a system to execute
certain business functions. The physical data flow graphic depicts how the logical data flow is
implemented. DFD visually represents the functions or processes that capture, alter, store, and
distribute data between a system and its environment, as well as between system components. Because
of the visual representation, it serves as a useful communication tool between the user and the system
designer. The DFD structure allows you to start with a broad overview and work your way up to a
hierarchy of specific graphics. DFD is frequently used for the following reasons:
According to this project, I designed the data flow diagram suit to the system scenario. Simply, it
represents how data will flow in the system as a graphical diagram. We can get an idea about the whole
mechanism of the project. I was able to design three diagrams with this data flow diagram. Those
diagrams are use-case diagrams and activity diagrams. these are representing case, mechanism, and
flow likewise. All diagrams are more similar to the data flow diagram. typically, these diagrams are
designing in the planning stage of agile methodology and the major thing is we can easily identify the
requirements and the drive implementation correctly.
When talking about the system, it is mainly developing for E-Academic solution for the company.
Simply, it is fulfilling all training sessions of employees through the online (system). it will help to
conduct their training session and manage their time. In past, this session was conducted as a physical
session but due to the pandemic situation and all are working from their home therefore as a business
analysis of the DT technology company, I am decided to build an online system for the training
sessions. Simply, employees can manage and study their academics from home without any kind of
problem. I am building this application based on agile methodology and previously mentioned above in
details of the system. before I build this system in the planning session create a diagram to represent the
mechanism of the system. it will help to get a rough idea of the system. usually, I have used a use-case
diagram, activity diagram, and data flow diagram. When talking about the agile methodology that is
fully person-oriented.
Typically, we planning and design the structure of the system to conduct and make corrections with the
customers. For example, some customers are come to the company and tell their requirements to the
project manager to build a system someplace. In that case, the manager mainly concerns about the
customer’s requirements and creates a system structure diagram and shows to the customer and
explains what the manager understands about the customer’s requirements. Simply that is a kind of
proof that represents the mechanism behind the system and the manager’s understanding of the
requirements. That is why very important to diagram before building the system. Customers can get a
simple idea about the system see this mechanism of whatever large or complicated diagram.
There have some major kinds of the diagram we use in project management. Use-case diagram. Data
flow diagram and activity diagram. Mainly, those 3 diagrams are representing the whole mechanism of
the project. We can conduct the project without methodology and diagrams. It is very essential to
project success. The methodology is managed whole project mechanism and the diagram represent the
structure of that critical mechanism of the project therefore these 2 major things are a must for the
project. Methodology handles the whole project from planning to testing section physically and
diagrams show off the project process of the project. These methodology and diagrams are very
effective and essential to conduct a stable project. Simply, the diagram is representing the plan of the
project and the methodology is representing the whole project process (execution). So, in that case,
these are essential to the project.