University of Engineering & Technology

(KSK Campus)

Submitted Date: 06-10-2021

Software Engineering
( Lab 3 )
Name: Hafiz Zain Ul Abideen
Registration No: 2019cs659
Name: Hafiz M.SAIM
Registration No: 2019cs644

Section: A

1
 FIVERR-Freelance Website

Requirements Elicitat
Requirements elicitation is the practice
of researching and discovering the requirements of a system from users,
customers, and other stakeholders. The practice is also sometimes referred
to as "requirement gathering".

1- Prepare for Elicitation

a) Purpose
We want to make a website to start browsing for jobs in multiple
categories. When working on a project, freelancer can send offers and set their
prices. Once they finish, they can easily raise an invoice from their dashboard.
The Client accept the offer according to his choice.

b) Description
Freelance website is an online outsourcing platform that puts
clients and businesses in contact with a global network of freelancers. Any
member can post a project, whether a short- or long-term job, and choose from
skilled freelancers who offer bid proposals with rate quotes and time estimates
for completing the work.
Freelance websites are places where you can earn money for
yourself, rather than for a particular company. It enables freelancers to search
for a wide range of jobs. If you are a beginner, then freelancing websites are
an easier way to earn money online.

c) Inputs
1. Needs:
We provide the platform where client can easy the send his
work for completion in his deadline time. Also we provide freelancer to
get money from Project accordance to his skill.

2
 2. Stakeholder (Engagement Approach):
i. Survey Stakeholders.
ii. Prioritize Stakeholders by Interest and Influence.
iii. Map Stakeholders to Measure Stakeholder Engagement.
iv. Communicate Company Activity Regularly.
v. Log Meetings to Maintain Project Knowledge.

d) Outputs
We earn money from both freelancer and client side by providing
them platform and grow our business.We become a middle man between
Client and Developer. Client easily give project in a minute. Freelancer also
earn money and get experience. Freelancer easily show and improve his skill.

2- Conduct Elicitation
a) Purpose
Purpose is to draw, explore and identify information relevant to the
change.
b) Description
The Conduct Elicitation task may be ruled by an Elicitation
Activity Plan that includes the planned elicitation activities, its techniques and
logistics. The Conduct Elicitation comprehends in just two main elements: guide
elicitation activity and capture elicitation outcomes.
c) Inputs(Elicitation Activity Plan)
An elicitation activity plan is the
main input for conducting elicitation. It provides details on elicitation
activities and techniques, sources of information, and logistics and scope of
the activity. The unconfirmed elicitation results are the expected output,
containing information captured in the activity-specific format.
Conducting elicitation has two key elements:

 Guiding Elicitation Activity

 Capturing Elicitation Outcomes
Guidelines and tools that are used as the BAs conduct elicitation are business
analysis approach, existing business analysis information, stakeholder

3
engagement approach, and supporting materials. The most widely used
techniques for conducting elicitation are:

 Benchmarking and Market

 Analysis
 Brainstorming
 Business Rules Analysis
 Collaborative Games
 Concept Modelling
 Data Mining
 Data modeling
 Document Analysis
 Focus Groups
 Interface Analysis
 Interviews
 Mind Mapping
 Observation
 Process Analysis
 Process Modelling
 Prototyping
 Survey or Questionnaire
 Workshops
The key stakeholders in this phase of the business analysis process are customer,
domain subject matter expert, end-user, implementation subject matter expert,
sponsor, and any other stakeholders with relevant knowledge.

d) Outputs(Elicitation Results(Unconfirmed))

4
 Requirements [Stated]: Described from the perspective of the stakeholder.
Stated requirements describe the stakeholder’s need from the stakeholder’s
perspective.
Stakeholder Concerns: Includes issues identified by the stakeholder, risks,
assumptions, constraints, and other relevant information.

3- Confirm Elicitation Results

a) Purpose
Check information gathered during elicitation session for accuracy
and consistency against other information
b) Description
4 techniques to confirm elicitation results.
1-Document Analysis. Documenting the analysis can help to be used as a
parameter of comparison between what you have understood in the elicitation
and with any other existing documents and source can say.
2-Interviews.
3-Reviews.
4-Workshops.
c) Inputs(Elicitation Results(Unconfirmed))
The confirm
elicitation results activity is used to check the accuracy of the information
which has been gathered in the elicitation activities. The information is
checked against the source of that information to ensure that it is accurate.
This would prevent ambiguity, omissions, conflicts and may prevent errors.
d) Outputs(Elicitation Results(Confirmed))
Now we make the
result on the bases of the data gathering and data is made from survey social
experiments and reflects the captured information and confirms that is relevant
and useful as input for further work.

4- Communicate Business Analysis info

a) Purpose

5
 Ensure stakeholders have a shared understanding of business
analysis information

b) Description

1. Determine Objectives: Define what reason to prepare the

Business analysis information. Example:
• communicate about requirements and designs to stakeholders,
• estimate quality and planning,
• evaluate alternatives,
• require formal reviews and approvals,
• define inputs to solution design,
• maintain contractual and regulatory obligations and
• support reuse.

2. Select the Format of Communication: A package may be

developed to communicate information clearly and in a usable
format for continuing change activities. The package format may
comprise:
• Formal Documentation: based templates used by the
organization, and provides a solid, simple to use and long-term
record of the information.
• Informal Documentation: used during a change but are not part
of a formal organizational process.
• Presentations: involves a high-level overview appropriate for
understanding goals and to support decision making.

6
 3. Select Communication Platform: An appropriate platform
needs to be chosen to communicate the Business Analysis
information. In general, communication platforms can be:
• Group collaboration: communicate the package to a group of
important stakeholders at the same time.
• Individual collaboration: communicate the package to an
individual stakeholder at a time.
• Non-verbal methods (e.g. Email): to communicate the package
when is not requires verbal explanation to support it.

Is considered that the Business Analysis Information is finally

communicated when the target stakeholders have an understanding of its
content and implications, and also the stakeholders are engaged,
understanding the information and agreeing with the Business Analysis
Information. For this is the Business Analyst responsibility to develop a
Business Analysis information package, with clear goals through an
adequate format in an appropriate platform.

c) Inputs
Stakeholder Engagement Approach:
Provides stakeholder groups,
roles and general needs regarding communication of BA information
Business Analysis info
Any BA information at any level. This
information becomes an input when there's the need of communicating
this to the stakeholders.
d) Outputs(Business Analysis information Communicated)

1. Communicate the Right Way. 

7
 2. Understand the Different Learning Styles. 
3. Be Clear on the Objectives of Your Communication. 
4. Follow Up. 
5. Keep it Simple & Correct. 
6. Engage but Listen. 
7. Provide the Right Level of Detail. 

5- Manage Stakeholder Collaboration

a) Purpose
Encourage stakeholders to work towards a goal of developing
freelance website.
b) Description
1. Determine all key stakeholders

Nothing can tank a project like last-minute

instructions delivered by a late-coming stakeholder. The original vision is bound to
change as a project moves through development, and someone who hasn’t been
involved in the process won’t know why certain decisions—or compromises— were
made.

Involve from the beginning anyone who will need to sign off on the project. If they
can’t be available to provide needed input, assign a stand-in.

On the other hand, limit the number of overall stakeholders to only those who are
essential. You know what they say about too many cooks in the kitchen.

8
2. Establish clear roles

Will your development team be involved in creative brainstorming? Will your primary
stakeholders review the bug lists? Ensuring that each team member is limited to
their role in the process will keep things moving along more smoothly.

3. Identify the basic elements

People always want to jump right to the look and feel of the finished product. (That’s
the fun part, after all.) But first, you need to establish a project framework to set
clear boundaries and goals. Take into consideration things like:

 Purpose and objectives—What’s the overall goal for creating this project
in the first place?

 Timeline—Time limitations will greatly affect the creative process. A

brilliant idea without adequate time to execute it won’t do you any good.
Have a basic timeline in mind before initiating the creative process.

 Resource constraints—Like time, resource limitations will influence

what ideas you can work with. Know what these are before you get
started.

4. Develop your concept

Whether you prefer group brainstorming or simply sharing individual ideas, this is the
truly fun part of creative development. Go wild. Don’t be afraid of your imagination
—and don’t expect your first idea to work. This is where iteration comes in. You have
to start somewhere, so don’t worry if it’s rough at first. Start big and then trim your

9
ideas against the project framework you established earlier to identify an executable
concept.

5. Tackle the content

The content, in whatever format, will be the driver behind the project. Start
by establishing the basics, like audience, topic, form factor, length, and so on.
Next, identify any content activities that need to happen, such as script writing,
character descriptions, and story boards. Then start developing that content as soon
as possible. It will always take longer than expected. It’s a marathon, not a sprint—
contrary to popular belief, creativity doesn’t happen in big dramatic movements. It’s
often quite slow and tedious. Make sure you have the mental bandwidth needed to
stay sharp throughout.

6. Address the visual design

This is the other fun part. But even the visuals need a framework before development
begins. First, you must establish foundational elements such as orientation,
dimensions, color palate, and graphic elements. From here, you can move on to the
look and feel of the finished product.

7. Allow time for development

The development aspect of your project, particularly if you’re working with

multimedia, is the other thing that always takes longer than expected. But this is
where it all comes together. Expect a few iterations to get it right, catch bugs, and
fine-tune.

10
And remember, creative collaboration takes time. Approval cycles, coordinating
schedules, incorporating feedback—all of these are necessary in group projects, and
all are time-consuming. Work this stuff into your project timeline and add some extra
padding to boot.

Above all, the key to a successful collaboration is to always allow for a certain

amount of flexibility. And that means being prepared to compromise. Time and
resources pose limitations, as may the personal whims of high-ranking stakeholders.
So don’t become overly attached to any single element, because you may need to let
something go for the overall sake of the project. But if you follow the advice above,
the process can be *almost* as rewarding as the end result.

c) Inputs
SH Engagement Approach:
It’s a one-way communication from
the organization to the stakeholders with no invitation to reply.
BA Performance Assessments:
It’s a limited two-way engagement:
performance is monitored according to terms of the contract set.
d) Outputs(Stakeholder Engagement)
1. Discover Potential Risks

One of the most important benefits of stakeholder

collaboration is that it helps early detection and resolution of issues. Collaboration
with the stakeholders using the task management software can help identifies
problems that will usually get unnoticed.

Improved stakeholder involvement using the task management software reduces

the risk of project failures. The more engaged the stakeholders are right from the
start, the more improved will be the outcome of the project.

2. Get Valuable Support from Stakeholders

11
Customers have a big stake in the project. They want the project to conform to their
exact requirements. By involving them in the project management using a
collaboration software, you will be able to get invaluable inputs from them. Some of
them will even be ready to provide their specialized information in finance,
procurement, and other fields free of charge. Using the spreadsheet software will
allow you to get the information that will prove helpful in successful project
completion.

3.  Increased Perception of Quality

Stakeholder collaboration can also help in improving the perception of project

quality. Irrespective of the outcome of the project, if the stakeholders feel that their
inputs are valued and implemented they will have a positive perception regarding
the project.

4. Reduced Cost of Project

One of the prime goals of a project manager is to ensure that the project gets
completed using minimum costs. Collaborating with the stakeholders using
a collaboration software can help achieve this goal. There will be fewer chances of
cost overruns when the stakeholder is involved from the start. This will ultimately
result in improved profitability for the company.

5. Speedier Closure of Projects

One main reason for project cost overruns is delays caused due to conforming to
feedbacks of the client received during later stages of the project execution stage.
When the stakeholders are involved from the start, it will increase the odds of a
speeder closure of the projects. This again will result in great cost savings that will
benefit everyone involved with the project.

To sum up, close stakeholder collaboration using work management software is

essential. Greater stakeholder engagement and involvement will help ensure
delivery of quality project outcomes. This, in turn, will make a positive impact on the
company’s financials. By reading the above benefits about stakeholder
collaboration, there is now no reason not to collaborate with the different
stakeholders using a project management software.

12