Assignment 2 :You are required to produce a documentation that

explains the purpose of the feasibility report

and describe how technical solutions can be compared.

Ans:A feasibility report is a testimony that attempts to create some sort of action.
Feasibility reports are created to persuade/help the decision makers to choose between
available options. Remember that your option is not the only one, the decision makers will
probably have many to choose from. A feasibility report also determines whether or not
the investigated task can be done with the amount of resources available OR how many
resources will be necessary in order to complete the task. A feasibility may be useful in a
lot of different situations such as event planning, finances, or even remodeling your
home.

● Feasibility studies are important to business development. They can allow a

business to address where and how it will operate. They can also identify
potential obstacles that may impede its operations and recognize the
amount of funding it will need to get the business up and running.

The purpose of feasibility studies are given as follows: The purpose is to

know the different variables involved with the proposed system. It explores
the business opportunity and alternative paths available.
● Technical feasibility evaluates the technical complexity of the expert system
and often involves determining whether the expert system can be
implemented with state-of-the-art techniques and tools. In the case of expert
systems, an important aspect of technical feasibility is determining the shell
in which the system will be developed. The shell used to develop an expert
system can be an important determinant to its quality and makes it vital to
the system's success. Although the desirable characteristics of an expert
system shell will depend on the task and domain requirements, the shell
must be flexible enough to build expert reasoning into the system
effectively. It must also be easily integrated with existing computer-based
systems. Furthermore, a shell providing a user-friendly interface
encourages end users to use the system more frequently

COMPONENTS:

● There are basically six parts to any effective Feasibility Study:

1. The Project Scope which is used to define the business problem and/or
opportunity to be addressed. The old adage, "The problem well stated is half
solved," is very apropos. The scope should be definitive and to the point;
rambling narrative serves no purpose and can actually confuse project
participants. It is also necessary to define the parts of the business affected
either directly or indirectly, including project participants and end-user
areas affected by the project. The project sponsor should be identified,
particularly if he/she is footing the bill.
I have seen too many projects in the corporate world started without a well
defined project scope. Consequently, projects have wandered in and out of
their boundaries causing them to produce either far too much or far too little
 than what is truly needed.
2. The Current Analysis is used to define and understand the current
method of implementation, such as a system, a product, etc. From this
analysis, it is not uncommon to discover there is actually nothing wrong
with the current system or product other than some misunderstandings
regarding it or perhaps it needs some simple modifications as opposed to a
major overhaul. Also, the strengths and weaknesses of the current
approach are identified (pros and cons). In addition, there may very well be
elements of the current system or product that may be used in its successor
thus saving time and money later on. Without such analysis, this may never
be discovered.
Analysts are cautioned to avoid the temptation to stop and correct any
problems encountered in the current system at this time. Simply document
your findings instead, otherwise you will spend more time unnecessarily in
this stage (aka "Analysis Paralysis").
3. Requirements and how requirements are defined depends on the object
of the project's attention. For example, how requirements are specified for a
product are substantially different than requirements for an edifice, a bridge,
or an information system. Each exhibits totally different properties and, as
such, are defined differently. How you define requirements for software is
also substantially different than how you define them for systems.
4. The Approach represents the recommended solution or course of action
to satisfy the requirements. Here, various alternatives are considered along
with an explanation as to why the preferred solution was selected. In terms
of design related projects, it is here where whole rough designs (e.g.,
"renderings") are developed in order to determine viability. It is also at this
point where the use of existing structures and commercial alternatives are
considered (e.g., "build versus buy" decisions). The overriding
considerations though are:
● Does the recommended approach satisfy the requirements?
● Is it also a practical and viable solution? (Will it "Play in Poughkeepsie?")
● A thorough analysis here is needed in order to perform the next step…
5. Evaluation examines the cost effectiveness of the approach selected. This
begins with an analysis of the estimated total cost of the project. In addition
to the recommended solution, other alternatives are estimated in order to
offer an economic comparison. For development projects, an estimate of
labour and out-of-pocket expenses is assembled along with a project
schedule showing the project path and start-and-end dates.
After the total cost of the project has been calculated, a cost and evaluation
summary is prepared which includes such things as a cost/benefit analysis,
return on investment, etc.
6. Review that all of the preceding elements are then assembled into a
Feasibility Study and a formal review is conducted with all parties involved.
The review serves two purposes: to substantiate the thoroughness and
accuracy of the Feasibility Study, and to make a project decision; either
approve it, reject it, or ask that it be revised before making a final decision. If
approved, it is very important that all parties sign the document which
expresses their acceptance and commitment to it; it may be a seemingly
small gesture, but signatures carry a lot of weight later on as the project
 progresses. If the Feasibility Study is rejected, the reasons for its rejection
should be explained and attached to the document

2.Prepare a brief report discussing the components of the feasibility report.

https://www.entrepreneurindia.co/blog-description/13679/what+are+the+components+of
+a+project+feasibility+report%3F

3.Carry out the feasibility study as per the best of your previous research work against
the solution to be developed for the given problem and assess the impact of different
feasibility criteria on the software investigation.

4.“Investigate the potential future developments which the IoT can

help advance e.g. automate
manufacturing, medicine and healthcare, virtual world, AI, machine
learning etc”.
https://www.mdpi.com/2571-9394/3/1/12/pdf
5.You have to design and implement a security
policy for the bank which will
List out the main components of an organizational disaster recovery
plan, justifying
the reasons for inclusion.
Discuss the roles of stakeholders in the organization to implement
security audit
recommendations.
And an evaluation of the suitability of the tools used in an
organizational policy.

https://www.urgenthomework.com/sample-homework/emc-cloud-solutions-u
nit-5-security
6.Discuss different approaches to improve the software quality and
considering the above context
discusses the two approaches that can be applied at this context to
improve the software quality.
some of the tools to gather better software requirements:

1) gathering requirements is complicated

2) use the toolbox approach

3) AS-IS and TO-BE process model

4) AS-IS process model

5) functional decomposition

To Create technical Documentation we have to follow below steps:

step 1: Do research and create a documentation plan

step 2: Structure and design

Step 3: create the content

step 4: Deliver and test

step 5: create a maintenance and update schedule

Example for planio wikis : In this template ,the user knows exactly what they are reading
gets a short overview of what the document covers and then has a table of contents
outlining each step so they can jump to the most relevant one right away. not only will
keeping things organized like this help you users find information more quickly but it will
let you know if you have all the information you need to keep your content consistent.

the two approaches to improving software quality:

1. Test early andTest often with Automation

To improve software quality it is absolutely paramount to test early and test often .Early
testing will ensure that any defects do not snowball into larger more complicated issues.
The bigger the defect, the more expensive it becomes to iron out any issues.

2.Encourage innovations

it is important that testing structures and quality measures sre in place however there

should always be room for innovation . A great way jto allow for innovation is to automate
testing where possible to minimise time spent on controls.