HND Computing for SAD
Technology
56 pag.
Document shared on www.docsity.com
Downloaded by: hakeem-haniffa (hakeem.haniffa46@gmail.com)
Higher Nationals
Internal verification of assessment decisions – BTEC (RQF)
INTERNAL VERIFICATION – ASSESSMENT DECISIONS
Programme title
Assessor
Internal
Verifier
Unit 34: System Analysis & Design
Unit(s)
Online Auction Website for the fineArts.com
Assignment title
Student’s name
List which assessment
criteria the Assessor has
awarded.
Pass
Merit
Distinction
INTERNAL VERIFIER CHECKLIST
Do the assessment criteria awarded match
those shown in the assignment brief?
Is the Pass/Merit/Distinction grade awarded
justified by the assessor’s comments on the
student work?
Has the work been assessed
accurately?
Is the feedback to the student:
Give details:
• Constructive?
• Linked to relevant assessment
criteria?
• Identifying opportunities for
improved performance?
• Agreeing actions?
Does the assessment decision need
amending?
Y/N
Y/N
Y/N
Y/N
Y/N
Y/N
Y/N
Y/N
Assessor signature
Date
Internal Verifier signature
Date
Programme Leader signature (if
required)
Date
Confirm action completed
Remedial action taken
Give details:
Assessor signature
Date
Internal
Date
Document shared on www.docsity.com
Downloaded by: hakeem-haniffa (hakeem.haniffa46@gmail.com)
Verifier
signature
Programme Leader
signature (if
required)
Date
Document shared on www.docsity.com
Downloaded by: hakeem-haniffa (hakeem.haniffa46@gmail.com)
Higher Nationals - Summative Assignment Feedback Form
Student Name/ID
Unit 34: System Analysis & Design
Unit Title
1
Assignment Number
Assessor
Submission Date
Date
Received 1st
submission
Re-submission Date
Date Received 2nd
submission
Assessor Feedback:
LO1 Evaluate the strengths and weaknesses of the traditional and agile systems analysis
methodologies
Pass, Merit & Distinction
Descripts
P1
M1
D1
LO2 Produce a feasibility study for a system for a business-related problem
Pass, Merit & Distinction
Descripts
P2
M2
LO3 Analyse their system using a suitable methodology.
Pass, Merit & Distinction
Descripts
P3
M3
D2
LO4 Design the system to meet user and system requirements.
Pass, Merit & Distinction
Descripts
Grade:
P4
Assessor Signature:
M4
Date:
Resubmission Feedback:
Grade:
Assessor Signature:
Date:
Internal Verifier’s Comments:
Signature & Date:
*
Please note that grade decisions are provisional. They are only confirmed once internal and external moderation has taken place and
grades decisions have been agreed at the assessment board.
Document shared on www.docsity.com
Downloaded by: hakeem-haniffa (hakeem.haniffa46@gmail.com)
Pearson Higher Nationals in
Computing
Unit 34: Systems Analysis & Design
Assignment 01
Document shared on www.docsity.com
Downloaded by: hakeem-haniffa (hakeem.haniffa46@gmail.com)
General Guidelines
1. A cover page or title page should be attached to your assignment. Use page 1 of this
assignment brief as your cover page and make sure all details are accurately filled.
2. The entire assignment brief should be attached as the first section of your assignment.
3. The assignment should be prepared using a word processing software.
4. The assignment should be printed single sided in an A4 sized paper.
5. Allow 1” margin on top, bottom and right sides of the paper and 1.25” on the left side (for
binding).
Word Processing Rules
1. The font size should be 12 point, and should be in the style of Time New Roman.
2. Set line spacing to 1.5. Justify all paragraphs.
3. Ensure that all headings are consistent in terms of size and font style.
4. 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.
5. Use the spell check and grammar check function of the word processing application to
review the use of language on your assignment.
Document shared on www.docsity.com
Downloaded by: hakeem-haniffa (hakeem.haniffa46@gmail.com)
Important Points:
1. Carefully check carefully the hand in date and the instructions given with the assignment.
Late submissions will not be accepted.
2. Ensure that sufficient time is spent to complete the assignment by the due date.
3. Do not wait till the last minute to print or bind the assignment. Such excuses will not be
accepted for late submissions.
4. You must be responsible for efficient management of your time.
5. If you are unable to hand in your assignment on time and have valid reasons such as illness,
you may apply (in writing) for an extension.
6. Failure to achieve at least a PASS grade will result in a REFERRAL grade.
7. Non-submission of work without valid reasons will lead to an automatic REFERRAL. You will
then be asked to complete an alternative assignment.
8. If you use other people’s work or ideas in your assignment, it must be properly referenced,
using the HARVARD referencing system, in your text or any bibliography. Otherwise, you’ll
be found guilty of committing plagiarism.
9. If you are caught plagiarising, your grade will be reduced to a REFERRAL or at worst, you
could be excluded from the course.
Document shared on www.docsity.com
Downloaded by: hakeem-haniffa (hakeem.haniffa46@gmail.com)
Student Declaration
I hereby, declare that I know what plagiarism entails, namely to use another’s work and to present
it as my own without attributing the sources in the correct form. I further understand what it
means to copy another’s work.
1. I know that plagiarism is a punishable offence because it constitutes theft.
2. I understand the plagiarism and copying policy of Edexcel UK.
3. I know what the consequences will be if I plagiarise or copy another’s work in any of the
assignments for this program.
4. I declare therefore that all work presented by me for every aspect of my program, will be my
own, and where I have made use of another’s work, I will attribute the source in the correct
way.
5. I acknowledge that the attachment of this document signed or not, constitutes a binding
agreement between myself and Edexcel UK.
6. I understand that my assignment will not be considered as submitted if this document is not
attached to the assignment.
Student’s Signature:
(Provide E-mail ID)
Date:
(Provide Submission Date)
Document shared on www.docsity.com
Downloaded by: hakeem-haniffa (hakeem.haniffa46@gmail.com)
Higher National Diploma in Computing
Assignment Brief
Student Name /ID Number
Unit Number and Title
Unit 4: Systems Analysis & Design
Academic Year
2018/19
Unit Tutor
Online Auction site for the fineArts.com
Assignment Title
Issue Date
Submission Date
IV Name & Date
Submission format
The submission is in the form of an individual written report. This should be written in a
concise, formal business style using single 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. The recommended
word limit is 2,000–2,500 words, although you will not be penalised for exceeding the
total word limit.
Unit Learning Outcomes:
LO1 Evaluate the strengths and weaknesses of the traditional and agile
systems analysis methodologies.
LO2 Produce a feasibility study for a system for a business-related problem.
LO3 Analyse their system using a suitable methodology.
LO4 Design the system to meet user and system requirements.
Assignment Brief and Guidance:
Document shared on www.docsity.com
Downloaded by: hakeem-haniffa (hakeem.haniffa46@gmail.com)
*Please note that assignment guidance is for reference only and should be
more specific in detail to meet customized needs.
Assignment brief
Case study
fineArts.com needs a Online auction system for selling fine art items on the
Internet. The application provides a server side access to catalogue and record
the items on auction. The customer can locally subscribe and participate to
the auction from the web using a web browser.
The main system features are:
 Items on auction are characterized by a code, an image, a description, and
a category (i.e. painting, print, silverware, etc.). Each item has an auction
starting date and time, and an end date and time (auction interval).
 Items on auction are characterized by a status which specifies the starting
price, the current price, the minimum bid increment, the time remaining
before the end of the auction.
 The item features and its status are displayed in a specific item web page.
Items on auction can be added, deleted and modified using an application
local to the server.
 A Web site allows users to look at items on auction, navigating among
them using various searching/sorting capabilities, for example, by
category, and through other kinds of search (keyword, cost, auction end
date, etc).
 The Web site allows users to ask for and receive a user ID and password
after subscribing for the auction by providing personal data.
 Bids can be placed only during the auction interval by registered users, and
can only be one or more bid increment higher than the current bid. After
the client has subscribed for the auction he/she can access to a personal
page which takes track of all the items he/she is concurring to buy.
 After the auction end time, no more bids can be accepted, and the item is
assigned to the user with highest bid.
Document shared on www.docsity.com
Downloaded by: hakeem-haniffa (hakeem.haniffa46@gmail.com)
Activity 01
Activity 1.1
a. Identify
and
explain
traditional
and
Agile
system
analysis
methodologies used in the industry.
b. Explain the strengths and weaknesses of the traditional and agile
systems analysis methodologies explained in part (a).
Activity 1.2
a. Explain similarities and differences of strengths and weaknesses
identified in task 1.1.
Activity 1.3
a. Give your opinion as to what extents agree with the similarities and
differences identified in task 1.2. Justify with evidences.
b. Describe transition problems faced by organizations when they move
from traditional approach to agile approach. Justify your answer.
Activity 2
Activity 2.1
a. Discuss the importance and purpose of conducting the feasibility study
on system investigation by considering the given scenario.
b. Produce the feasibility report with suitable recommendations. It
should cover different feasibility criteria including Technical, Economic,
Cultural, Legal, Operational and Schedule.
Activity 2.2
a. Explain the impact of Technical, Economic, Cultural, Legal, Operational
and Schedule criteria for the given scenario. Provide evidences taken
from the scenario.
Document shared on www.docsity.com
Downloaded by: hakeem-haniffa (hakeem.haniffa46@gmail.com)
Activity 3
Activity 3.1
a. Provide suitable tool(s) to collect user and system requirements.
b. Identify user and system requirements/ constraints for the system.
c. Create user stories for identified for user requirements.
d. Identify and explain the most suitable methodology for the analysis of
the system. Answer should cover features, advantages and
disadvantages of the selected methodology.
Activity 3.2
a. Explain how the selected methodology in task 3.1 c) can be used to
improve the effectiveness of the analysis stage.
Activity 3.3
a. Explain reasons to select the methodology in task 3.1 c) for the given
scenario.
Document shared on www.docsity.com
Downloaded by: hakeem-haniffa (hakeem.haniffa46@gmail.com)
Document shared on www.docsity.com
Downloaded by: hakeem-haniffa (hakeem.haniffa46@gmail.com)
Activity 01
a)
1.1
1.1.1 Traditional system analysis methodologies used in the industry.
Traditional software development methodologies are based on pre-organized
phases/stages of the software development lifecycle. Here the flow of
development is unidirectional, from requirements to design and then to
development, then to testing and maintenance. In classical approaches like the
Waterfall model, each phase has specific deliverables and detailed
documentation that have undergone a thorough review process.
Traditional approaches are suited when requirements are well understood – for
example, in industries like construction, where everyone clearly understands the
final product. On the other hand, in rapidly changing industries like IT,
traditional development procedures might fail to achieve project goals. Below
are the major disadvantages of traditional SDLC methods.


Problem statement / business need has to be defined well in
advance. The solution also needs to be determined in advance and
cannot be changed or modified.
The entire set of requirements have to be given in the initial phase
without any chance of changing or modifying them after the project
development has started.
For example, the user might have given initial requirements to analyze their
products in terms of sales. After the project has begun, if the user wants to
change the requirement and analyze the data on the region-wise movement of
products, the user can either wait till the completion of initial requirements or
start another project.




The user cannot conduct intermediate evaluations to make sure
whether the product development is aligned so that the end product
meets the business requirement.
The user gets a system based on the developer’s understanding and
this might not always meet the customer’s needs.
Documentation assumes high priority and becomes expensive and
time consuming to create.
There are less chances to create/implement re-usable components.
Document shared on www.docsity.com
Downloaded by: hakeem-haniffa (hakeem.haniffa46@gmail.com)
These disadvantages hinder project delivery in terms of cost, effort, time and
end up having a major impact on customer relationships.


Testing can begin only after the development process is finished.
Once the application is in the testing stage, it is not possible to go
back and edit anything which could have an adverse impact on
delivery dates and project costs.
Occasionally, projects get scrapped which leads to the impression
of inefficiency and results in wasted effort and expenditure.
Traditional development methodologies are suitable only when the requirements
are precise i.e., when the customer knows exactly what they want and can
confidently say that there won’t be any major changes in scope throughout the
project development. It is not suitable for large projects such as maintenance
projects where requirements are moderate and there is a great scope for
continuous modification.
1.1.2 Agile system analysis methodologies used in the industry.
Unlike the traditional approaches of SDLC, Agile approaches are precise and
customer friendly. Users/Customers have the opportunity to make modifications
throughout project development phases. The advantages of Agile over
traditional development methodologies include:






Though the problem statement/business need and solution are
defined in advance, they can be modified at any time.
Requirements/User Stories can be provided periodically implying
better chances for mutual understanding among developer and user.
The solution can be determined by segregating the project into
different modules and can be delivered periodically.
The user gets an opportunity to evaluate solution modules to
determine whether the business need is being met thus ensuring
quality outcomes.
It is possible to create re-usable components.
There is less priority on documentation which results in less time
consumption and expenditure.
Agile proposes an incremental and iterative approach to development. Consider
Agile Scrum Methodology to get good understanding of how Agile processes
work. Scrum Master plays an important role in Agile Scrum Methodology. A
Scrum Master interacts daily with the development team as well as the product
owner to make sure that the product development is in sync with the customer’s
Document shared on www.docsity.com
Downloaded by: hakeem-haniffa (hakeem.haniffa46@gmail.com)
expectations. The following diagram illustrates the lifecycle process in Agile
methodologies.
During project inception, the customer splits the initial set of requirements into
User Stories. The Scrum Master or Product owner organizes these User Stories
and segregates them into different Sprints. In general, Sprint contains 3-4 User
Stories to be delivered in 4 to 5 weeks, these are approximate figures, and they
will be decided based the complexity of user stories. Once the Sprint planning is
done, the selected User Stories are once again split into Tasks so that the
developer can have a clear roadmap to deliver quality output. At the end of each
Sprint, the customer gets a chance to review and predict the outcome and can
propose changes if any.
The main difference between traditional and agile approaches is the sequence of
project phases – requirements gathering, planning, design, development, testing
and UAT. In traditional development methodologies, the sequence of the phases
in which the project is developed is linear whereas in Agile, it is iterative.
Below picture illustrate this difference.
Document shared on www.docsity.com
Downloaded by: hakeem-haniffa (hakeem.haniffa46@gmail.com)
The main project variables like cost, time, quality etc., can be compared as
shown in the following picture.
Things like project scope and requirements change during the project which
make IT projects different from construction or engineering projects. Agile
methodology like Scrum is preferable in projects involving large teams where
we can expect frequent changes in requirements. As development phases like
requirement gathering, design, development and testing can start in parallel, the
entire team can be engaged in respective areas which increases productivity and
speeds up the development process.
Document shared on www.docsity.com
Downloaded by: hakeem-haniffa (hakeem.haniffa46@gmail.com)
Key points while making the transition from Traditional to Agile
methodologies:






Identify the factors which made the transition necessary
Everyone, including the user, should be clear about the reasons
which lead to the transition
Identify whether it is a small project or big project
Note the current stage of the project to be transitioned, whether
development has started or is yet to start
Make sure the team has a good understanding of the new approach
and have adapted to their respective roles as per the new approach
Arrange necessary training for the team
Therefore, Agile development methodologies are more suitable to withstand the
rapidly changing business needs of IT projects
b)
1.1.3 Strengths and weaknesses of the agile systems analysis methodologies
explained in part (a)
Unless you have been lost in the Andes for the past 14 years or so, you must
have heard about Agile methodology in software development. Agile methods
are diverse, but they all rely upon the basic principles put forward by the
prominent software developers in 2001.
They are the following:




Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
Agile methods are based upon rapid development cycles which end with
incremental delivery of software pieces and constant interaction with the
customer. Each new cycle of software development relies upon the results of the
previous cycle, with the consideration of customer’s feedback and requests as to
functionality and a common vision of the project. Due to the constant
cooperation with the customer and continuous delivery of the software pieces,
the development project becomes very flexible and responsive to change.
Agile methods are considered as a panacea by many software project
developers. However, like any other development methodology, the Agile
methodology has its strengths and weaknesses. It works well with some types of
Document shared on www.docsity.com
Downloaded by: hakeem-haniffa (hakeem.haniffa46@gmail.com)
projects and fails with others. Here we will try to outline the main advantages
and disadvantages of Agile methods for you to decide if they are suitable for
your own project.
Agile model strengths




High flexibility of the project. Short cycles and constant iterations allow
you to adapt your project frequently and tailor it to the customer’s needs
at any moment. You don’t have to waste your time and resources on
delivering a full project which will be rejected by the customer. This
makes the development process extremely flexible.
High customer satisfaction over the development process. Since Agile
projects are closely coordinated with the customer, he/she has a strong
impact on the development project. Software pieces are delivered
constantly, in short cycles and customer’s feedback is always taken into
consideration.
Constant interaction among the stakeholders. With your teams
constantly interacting with each other and with the customer, you avoid
producing tons of technical documentation, processes, and tools. Each
member feels like an important part of the team participating in the
decision-making process. This stimulates creativity and initiative and
leads to better results.
Continuous quality assurance, attention to details. Quality of the
product should be ensured by the testing team from the early stages
of Agile development. Since the development is conducted in short
cycles, testing is run non-stop, allowing you to produce a good final
product.
Document shared on www.docsity.com
Downloaded by: hakeem-haniffa (hakeem.haniffa46@gmail.com)
Agile model weaknesses




Problems with workflow coordination. Agile projects involve several
small teams working on their own software pieces. They should always
coordinate their work with each other, testers and management. Add to
that constant interaction with the customer, and you will get a ton of
communication management to consider before starting the project. Even
though a lot of interaction is considered an advantage of Agile
methodology, it may become a weak point due to many factors.
Difficult planning at early stages. Planning in Agile development is
essential before the process is started. It is important to assess your
resources, build up teams, and communicate an overall vision of the
project to them before it is kicked off.
Professional teams are vital. Agile projects require teams to make
serious decisions constantly. It means that only experienced software
developers, testers, and managers should be working on the project. This
software development methodology provides a very few places for
rookies.
Lack of long-term planning. A lack of final vision of the project may be
disorganizing in some cases. Your project may end up off track if the
customer changes his mind too often during the process. And remember,
by the end of the project you will have to assemble all those software
pieces, which had been changed and adapted a few times over the
development cycle and make them work. Also, there will be weak
documentation, since the interactions with the customer were mostly
verbal.
Document shared on www.docsity.com
Downloaded by: hakeem-haniffa (hakeem.haniffa46@gmail.com)
As you can see, Agile includes enough pluses and minuses. Therefore, it is very
important for project managers and their teams to identify and select the right
and appropriate project management tool for strategic goals and issues.
How to do it? The best way is to search, test, try and compare. It will take time
for you, for example, to study the detailed differences between Hygger and
Jira or to realize the main points in the comparison of Hygger and Trello.
However, it’s worth it.
Agile software development strengths and weaknesses, specified in this article,
should prompt you to make the right decision whether to use them or not and to
choose the appropriate project management tools.
Regardless of all their benefits, Agile methods do not give the answer to any
challenge. And in certain cases, traditional software development methods will
be more useful and productive than Agile.
1.1.3 The strengths and weaknesses of the traditional systems analysis
methodologies.
The Traditional Project Management Methodology is the complete
methodology for ongoing projects in a sequential cycle: initiations, planning,
executing, monitoring, controlling and closing. It works best for the projects
which can be completed in one sequence. It completes the successful delivery of
the project in time and low budget.
Document shared on www.docsity.com
Downloaded by: hakeem-haniffa (hakeem.haniffa46@gmail.com)
Strengths of Traditional System Analysis.
1.
COST EFFECTIVE
Since the projects are easier to complete under Traditional Project Management.
That’s why they likely take less time in completion and in meeting the timeline
successfully. There are very few chances of facing bugs, errors, or complex
problems during the planning, designing, testing and the final execution of the
project.
The companies happily go for the Traditional Methodology for smaller and
sequential projects. They take less time, fewer developers, and fewer resources
to complete.
It is also less costly because the companies don’t need to use heavy technology
and machinery to complete such projects.
2.
SUITABLE FOR REMOTE PROJECTS
Communication and different geographical position becomes a major hurdle for
larger and complex projects. Traditional projects are smaller and easier ones are
highly applicable for remote projects. As such projects can be developed by a
smaller team and don’t require much communication to solve the hurdles.
3.
IT’S SEQUENTIAL
It has sequential patterns which make it easy to follow the traditional
methodology. The sequential projects don’t need much alteration during the
development. If you stick to the developing plan, there are likely the best
chances to finish your task within the time schedule and all other criteria. The
sequence also makes management and development easier.
Traditional model suits best for the smaller projects where requirements are
clear and understandable. Every step in the traditional method has a start and
end point hence it’s flexible to share progress with stakeholders and customers.
The focused preplanning on requirements and design before writing a code
reduces the risk of errors and delay.
The sequential procedure requires proper documentation for every phase which
results in an enhanced understanding of the logic behind the code and
evaluation. This sequence creates proper trails for the stakeholder to have an
insight into a specific phase.
Document shared on www.docsity.com
Downloaded by: hakeem-haniffa (hakeem.haniffa46@gmail.com)
4.
QUICK TIME AROUND
A standard problem facing many firms, no matter where they’re in the business
life cycle, is they get stuck in the trenches of daily operations, at the expense of
conducting business growth activities. It wastes resources, money and time.
Traditional methodology projects don’t require much changing as they follow a
sequence. That’s is why they are delivered on time.
5.
OPTIMIZATION OF CUSTOMER’S SATISFACTION
The Traditional Projects are not too complex to meet the requirements of the
client. Every project management methodology highly prioritizes the happiness
of the clients. The entire development process occurs under the keen view of the
client’s requirements. The client is being aware of each process, confidential
about feedback, prioritized for each demand.
In the event the customer is clear regarding the needs of the software that will
be developed, the traditional model is the very best approach to follow because
it follows a sequential strategy and requirements are made clear in the very first
phase.
6.
RESPONSIBLE FOR THE QUALITY DELIVERABLE
Every Software Development Methodology has the goal to deliver quality
development to create a robust product, efficiently meeting to market’s
demands. It is more foolish than a fancy assumption to achieve 100% results.
The realistic approach and refined precision can be attained through dedicated
competency, collaboration, coordination, and management.
7.
NO TRAINING IS REQUIRED
The Traditional Project Management is a flexible one to go with as it needs no
prior knowledge and training to begin the projects. The traditional methodology
is also a rigid model; the specific deliverable and reviews make it easy to
manage and develop.
8.
SECURED
No project is ever without risks, but it’s the nature and intricacy of the project
that is most likely to learn the effect of the risks on the entire success of the
Document shared on www.docsity.com
Downloaded by: hakeem-haniffa (hakeem.haniffa46@gmail.com)
undertaking. Bigger projects will call for additional heights of consultation to
assess the extra company and technical requirements.
Traditional Project Management ensures privacy and security. It supports a
robust security mechanism during the end to end execution of the program.
9.
FLEXIBLE MANAGEMENT
Controlling a project is rather one of the toughest things in project
administration. There’s a demand for the entire team to have a good
comprehension of their own Development and Management practice.
Management change ought to be well structured so as to achieve goals and
missions.
In the present dynamic business environment, there’s a strong demand for
those organizations to become globally competitive. Because management
failures can make development worse and uncontrollable.
Traditional projects require fewer teams and less complex management to
handle project development.
10. EASY TO CHANGE
The project starts with a simplistic design and afterward is shaped by short
development cycles that permit the general project design to change when the
need comes up.
11. EFFICIENCY
The Best Project Management Strategy and the successful execution of the
project develops a good relationship with the clients for future projects. It also
has a positive impact on the team in gaining experience and specialized to
handle complex and technical activities.
It’s especially suited to projects developed in complex environments where
there’s a need to receive results quickly.
Weakness of Traditional System Analysis
Document shared on www.docsity.com
Downloaded by: hakeem-haniffa (hakeem.haniffa46@gmail.com)
1)
IT IS SLOW
It is going to be a slow development if your client isn’t clear about the
requirements. Since the changes are difficult in the sequential methodology of
traditional project management. The changes can break the sequence and the
next development step will be trodden upon until the previous step isn’t
completed.
2)
NO CUSTOMER FOCAL POINT
There isn’t much space for the customer’s opinion in every development
process. The clients are not involved or being open to the entire development
process until the product is ready. If it is not according to a client’s
requirements, then it’s going to be a time-wasting phenomenon. The stage of
finalizing the product is too late to check the marketing accountability of the
product as well.
Making the customer happy is the topmost priority of today’s world. Because
it’s their happiness which is going to determine your actual Position Application
Development Company in the market.
3)
THE ABSENCE OF THE CENTRAL AUTHORITY
There are individual subcontractors controlling the ropes of development. There
isn’t any singular dynamic teamwork and leadership as a central authority.
4)
TIME MANAGEMENT
The time mismanagement issue can arise in traditional methodology due to a
lack of mutual teamwork, unity, and mutual development.
5)
LACK OF INTUITIVENESS
There isn’t much space for new ideas to employ in Traditional Methodology.
The sequential method doesn’t have room for continuous evolution. You cannot
do much but just to follow the sequence.
6)
LACK OF COORDINATION
The subcontractors are involved as individuals, not as a singular dynamic team.
There is no attempt is made to have unity, mutual teamwork, and commitment
Document shared on www.docsity.com
Downloaded by: hakeem-haniffa (hakeem.haniffa46@gmail.com)
to the development. The lack of coordination delays development and can cause
some serious issues.
7)
LOCAL OPTIMIZATION
All individual subcontractors only care about their own efforts and talent. If
something goes wrong, there isn’t mutual teamwork to defend and tackle the
problem.
No teamwork, no dream work in traditional project management.
8)
NO EASY CHANGE
Once an application is on the testing stage, it is very likely impossible, time
taking and expensive to go back and fix it according to the requirements.
Sometimes you need to start again to implement any changes.
9)
RISK INVOLVING AND CHALLENGING DEVELOPMENT
Sometimes the customers and stakeholders are not sure about their requirements
in the start, and waterfall Software Development cannot begin without gathering
all relevant details and requirements. That is why the traditional approach does
not offer much space for customer’s feedback and the customized final product.
It is also a not viable model for complex, big and object-oriented project
development.
1.2
1.2.1 Similarities and differences of strengths and weaknesses of the traditional
and agile systems analysis methodologies
Traditional systems analysis methodologies
Traditional software development is the software development process used to
design and develop the simple software. It is basically used when the security
and many other factors of the software are not much important. It is used by
freshers in order to develop the software.
It consists of five phases:
Document shared on www.docsity.com
Downloaded by: hakeem-haniffa (hakeem.haniffa46@gmail.com)
1. Requirement’s analysis
2. Design
3. Implementation
4. Coding and Testing
5. Maintenance
Agile systems analysis methodologies
Agile software development is the software development process used to
design complicated software. It is basically used when the software is quite
sensitive and complicated. It is used when security is much important. It is
used by professionals to develop the software
.
It consists of three phases:
1. Project initiation
2. Sprint planning
3. Demos
1.2.2.1 Difference between Traditional and Agile Systems Analysis
Methodologies
Traditional Software Development
Agile Software Development
It is used to develop the simple
software.
It is used to develop the complicated
software.
In this methodology, testing is done
once the development phase is totally
completed.
In this methodology, testing and
development processes are
performed concurrently.
It provides less security.
It provides high security.
It provides less functionality in the
It provides all the functionality
Document shared on www.docsity.com
Downloaded by: hakeem-haniffa (hakeem.haniffa46@gmail.com)
Traditional Software Development
Agile Software Development
software.
needed by the users.
It is basically used by freshers.
It is used by professionals.
Development cost is less using this
methodology.
Development cost is high using this
methodology.
It majorly consists of five phases.
It consists only three phases.
It is less used by software
development firms.
It is normally used by software
development firms.
There is often a lot of talk around how different Agile is from traditional
methodologies, but this isn't always the case. Let's take a look at where some
similarities can be found.
1.2.2.2 Similarities between Traditional and Agile Systems Analysis
Methodologies
1. Expression of Business Need
When it boils down to it both approaches have the same goal for their
requirements — to develop a good quality product or solution that meets the
business needs. To do this you must:



Focus on the business vision and the objective of each increment
Make the business vision and the objective of each increment clearly
visible to all
Figure out what is important for each business need, it might not be
what you (or the business) first think.
2. Need to be clear, concise, and unambiguous
Well written User Stories need to be clear, concise, and complete. Double
check against this checklist:
Document shared on www.docsity.com
Downloaded by: hakeem-haniffa (hakeem.haniffa46@gmail.com)




Is it a single requirement or does it overlap?
Is it easy to read and understand by non-technical people?
Is it unambiguous and not susceptible to different interpretations?
Does it contain definitions or descriptions? If so remove them.
3. Do not constrain design
It is important for all requirements not to suggest or contain a solution. But
they must also not constrain the solution either. This is the same for Agile
requirements too, they should avoid being tied to a particular solution for as
long as possible.
4. Need to be testable
A testable requirement is a requirement that has been broken down to a level
where it is precise, unambiguous, and in an absolute state. For most
requirements, they can be tested by:



Inspection
Analysis
Demonstration
b)
1.3.1 What extents agree with the similarities and differences
1.3.2 Transition problems faced by organizations when they move from
traditional approach to agile approach
1. Training - Agile requires a lot of training to do it successfully
and many standard Agile training courses (CSM, CSPO, etc.)
only cover the “mechanics” of how to do Agile/Scrum. That’s
not sufficient - a high performance Agile team has to go beyond
the “mechanics” and understand Agile/Scrum at a deeper level.
2. Aligning Agile with Your Business - Many companies will try to
force-fit an Agile/Scrum approach to their business. The goal
should not be to just adopt Agile; you should focus on what
Document shared on www.docsity.com
Downloaded by: hakeem-haniffa (hakeem.haniffa46@gmail.com)
problems it will solve and how it will improve the business and
that might be different from one business to the next.
3. Enterprise-level Transformation - An Agile/Scrum approach
won’t work very well unless the organization is well-aligned to
support it and that might require some enterprise-level
transformation.
Activity 2
Activity 2.1
a)
2.1.1 Importance of conducting the feasibility study on system investigation
Feasibility refers to the process that describes, identifies, and evaluates the
proposed system and selects the best system for proper functioning. For
evaluating the feasibility, a feasibility study is conducted that helps in
determining whether the system is possible to develop or not. There are three
types of feasibility study, they are – technical feasibility, economic feasibility,
and behavioral feasibility. Studying all these feasibility helps the user and the
developer to understand on what grounds their system will be made and what all
features they can include in the software. The main purpose to conduct the
feasibility study is to establish the reasons to develop the software that is
accepted by all the users and can be modified easily as per the requirements
(KENTON, 2018). Some of the objectives of the feasibility study are discussed
below:
• To determine whether the newly developed software can be integrated with the
software that exists already.
• To analyze whether that software has the potential to be implemented with the
adoption of the current technology and within the specified schedule and
budget.
• To determine whether the software can fulfill the requirements of the
organization or a user.
Document shared on www.docsity.com
Downloaded by: hakeem-haniffa (hakeem.haniffa46@gmail.com)
Types of Feasibility
• Technical Feasibility: Technical feasibility helps in accessing the current
resources as well as technology that is required for accomplishing the
requirements of the user in the software within the allocated budget and time.
Following tasks are performed in the technical feasibility:
Helps in determining whether the technology used is stable.
Is the technology being demanded available? Or can the features being
requested are possible to embed with the current/ available technology
Analyze the technical capabilities and skills of the team members of software
development.
Operational/ Behavioral Feasibility: Behavioral feasibility is studied in order
to check, whether the human or employees in the business will use it or not.
Operational feasibility relies on human resources and analyzes whether the
software will operate after it is developed properly or not. Following tasks are
performed by the operational feasibility:
Operational feasibility helps in determining whether the solution that is
suggested by the team of the software development is acceptable or not.
Operational feasibility also helps in determining whether the problems that are
anticipated in the user requirements are of high priority.
It checks that the software is user friendly or not.
Its interface should be simple so that everyone should be able to use it.
Helps to analyze whether the organization is satisfied by the alternative
solutions provided by the team members of the software development
Economic Feasibility: Economic Feasibility helps in determining whether the
required software has the potential to generate financial gains for an
organization. This type of study involves the cost incurred on the team of the
software development, cost of study involved in conducting a feasibility study,
estimated cost of software and hardware. Software can be feasible only if it
focuses on the issues that are discussed below:
 The cost associated with the training, development team, software and
hardware.
 Cost required for conducting software investigation such as requirements
analysis and requirements elicitation.
Document shared on www.docsity.com
Downloaded by: hakeem-haniffa (hakeem.haniffa46@gmail.com)


The cost incurred on the development of software for producing longterm gains for an organization.
It is also studied that; can the software be made in the given budget?
Because sometimes the clients want many features to add in their
software but are not willing to pay the required amount. Hence, economic
feasibility is used to study this.
Scheduling feasibility:
It is the most important study that is used for measuring the success of the
project. All the projects will fail, if not completed at specified time. In
scheduling feasibility, an organization can estimate the time required for
completing the project. The time that will be required for the development of
the system, is estimated based on the requirements. Once all these things are
sorted, manpower is allocated their respective task and efforts are made to
complete the task within the deadline.
Benefits of conducting a feasibility study:





Enhances the focus of the project team
Helps in identifying new opportunities
Provides valuable information for decision making
Narrows the alternatives of business
Enhances the rate of success by evaluating several parameters
2.1.2 Purpose of conducting the feasibility study on system investigation
What Is the Purpose of Conducting a Feasibility Study?
If you are a land or property owner, whether that be residential, commercial, or
agricultural and think your land or property has development potential then a
feasibility study can be undertaken at the earliest stage of the project to outline
the land/properties development potential.
What Is a Feasibility Study?
The main purpose of a feasibility study is to assess the financial viability of
developed land and whether it will be a success or failure. The study aims to
highlight problems and risks that a potential plot will face such as gaining
planning, local authority, assessing current development supply & demand and
the suitability of a site, neighbors and so forth.
Document shared on www.docsity.com
Downloaded by: hakeem-haniffa (hakeem.haniffa46@gmail.com)
What Type of Properties/Land Require a Feasibility Study?
Examples of a property with development potential include: –
 Tired/dilapidated/vacant buildings,
 Parcels of land with current use or former use, e.g., builders’ yard,
parking area etc.,
 Existing residential dwelling with substantial gardens,
 Old barns or other agricultural buildings,
 Fields/agricultural lands near city/town/village.

What Are the Benefits of a 0Development Feasibility?
The conclusion of a development feasibility study is to access whether you are
going to benefit from the development process before investing time and money
in the planning process.
A feasibility study is an instrument to:  Understand the opportunity and limitations to a development.
 Financial viability determines how best to financially structure and plan
the development process to maximize value.
 Gross Development Value (GDV) assessment.
 Planning restrictions, requirements, and obligations.
 Type of planning applications such a full or detail consent, outline,
reserved matters, conservation areas, listed, prior notification, tree
preservation orders, material amendments etc.
 S106, affordable housing and CIL contributions assessments.
 Supply and demand assessment for a potential unit mix.
 Recommendations for appropriate further surveys including, ecology,
drainage, arboricultural, contamination, archaeological etc.
 Sensitivity testing on cashflows and concepts where potential costs and
sales values can damage a scheme’s viability.
 Construction costs assessment including fees, utility, sales/marketing,
contingency etc.
b)
2.1.2
Document shared on www.docsity.com
Downloaded by: hakeem-haniffa (hakeem.haniffa46@gmail.com)
Introduction
One of the most important parts of System Development Life Cycle is System
Analysis. After gathering and analyzing the requirements, we must start the
System Analysis. There are lot of different analysis include in the system
analysis phase. Feasibility Analysis can be identified as one of major part under
the system analysis.
There can be number of different alternatives that will be available to
address end users’ potential problems. Therefore, we must make sure that we
are selecting the best option. It is not an easy task to select the best option and if
we could not select the best option, we will end up with wasting lot of
resources.
So, how can we select the best option? To answer that we should do a
feasibility study in the main areas, such as operational, technical, economical
etc… with the identified different alternative options.
So, purpose of this document is to identify the available alternative
solutions to address the problem definition, study about the different feasibility
criteria, carry on feasibility studies from the various feasibility angles for those
identified options, rank the alternative options with respect to different feasibly
scopes and finally to select the best option or solution which will address the
identified problems and end user requirements optimally.
Problem Definition
What is the current state?
We can define current state of an Information system as the present state or
position in which Information system belongs or in which range of level it
provides services to users. So, in a current state of an Information system if the
ultimate end user satisfaction was not meet then there will be a definite gap of
potential end user satisfaction and the current state. So, any new Information
system, which is built to address the potential problem, should make sure that it
would fill the gap, which exists between current state and the desired state.
For our project, we will be building an Information System for indigenous and
western medical system to provide wide scope of health and medical
information from both the western and indigenous medical system point of
views in a flexible and comparative atmosphere.
Document shared on www.docsity.com
Downloaded by: hakeem-haniffa (hakeem.haniffa46@gmail.com)
So, these were the key points of current state which we identified by analyzing
the existing systems.
 Lack of readily available medical information on different medical
systems on a comparative platform.
 Absence of a forum for the discussion of professional issues on health
care industry.
 Not having a proper interface for the medical researchers to conduct their
research through sudden pop-up questionnaires.
 Lack of interactivity & user friendliness of the existing articles providing
medical services.
 Lack of public awareness of the innovations in both the medical systems.
 Less motivation for the indigenous medical innovations.
 A surface that communicates the current medical needs of the public
needs to be established.
 Difficulty of reaching the medical resources due to unawareness of the
physical location.
What is the desired state?
Desired state of an Information System is the future state where the system will
be able to gain the ultimate user satisfaction and will address to all the potential
problems. It is the state where there will not be any gap between ultimate
customer requirements and the Information System.
Therefore, in our Information system we will hope to address the problems,
which exist in the current system and to provide the solutions mentioned below
through the system.
·
Maps directing the hospitals clinics indigenous medical
centers & other medical recourses locally.
·
Facilitating the researchers to reach the interested crowd to
direct their questionnaires.
·
Out of box medical scope covering a vast area on both
medical systems.
Document shared on www.docsity.com
Downloaded by: hakeem-haniffa (hakeem.haniffa46@gmail.com)
·
Users will be able to participate the improvement of the site
& flex the site according to their needs through their suggestion as
well as their complaints.
·
Facilitating the promotions of special medical functions
organized around the country through the site.
·
Maintaining a quick response question & answer forum.
·
Facilitating the users to direct their suggestions &
complaints regarding the site & use them in subsequent site
development.
·
Prioritizing the offered articles to the viewers based on their
age, sex, & the locality information extracted from the user
accounts.
·
Gathering user needs & suggestions on both the medical
systems & draw the attention of the medical board to assess the
viability of implementing those, which could lead to successful
medical innovations.
·
Providing users with the option of rating an article &
directing those articles that are with least ratings to the medical
board for further modifications.
Through our Information system, what we are trying to achieve is to
merge the gap that exists between the current state & the desired state.
The System
As we identified the main requirement is, to develop a medical information
system, which will provide medical information in both western and indigenous
medical system point of views in a comparative platform. Therefore, at the
requirement-gathering phase we identified the main requirements, which will
address end user’s potential problems. The identified requirements can be
categorized into functional and non-functional requirements.
The functional requirements
The system should be able to provide general details about a particular
diagnosis such as an overview of the diagnosis, the symptoms, causes for
the diagnosis etc…
Document shared on www.docsity.com
Downloaded by: hakeem-haniffa (hakeem.haniffa46@gmail.com)
This is one of the main functionalities of the system. A general user
or a patient should be able to get all the details related to a
particular diagnosis from the system. Users will be able to get
details for the diagnosis, which they are interested on via indexing
method or users can get information for a particular diagnosis from
querying the system database.
The system should be able to provide medical treatments and available
drugs for a particular diagnosis from both the western medical system and
conventional medical system point of view.
The major objective of the system is to provide medical treatments
and available drugs for a particular diagnosis from both the
systems point of view to the patients. Moreover, the information
should be comparative to the user. This should include many
details such as the drug name, available places, cost etc… In
addition, for some diagnosis the system should not suggest the
drugs, because those medical drugs should not be obtained without
a prescription from the doctor.
The system should be able to provide general health details which will be
required by public such as details about healthy lifestyles, details about
various health issues, various health related articles etc…
Implemented information system should provide latest news in
health and health related industry and various newsletters, articles
on health-related topics.
The users of the system should be able to provide health related articles to
the system and they should be able to comment and modify those articles.
Apart from the articles, which are available in the system, users
also will be able to provide health related articles to the system and
they can comment and rate those articles too. From the rating
system, users will motivate to provide articles to the system. The
users will be able to provide modifications to existing articles as
well. Those modifications will update to the system after it
approves by medical specialists of the institution.
The system should be able to provide spaces to publish the health-related
questions of the public, they will be able to get answers for those questions
from medical specialists, and they will be able to carry discussions forward
through the system.
Document shared on www.docsity.com
Downloaded by: hakeem-haniffa (hakeem.haniffa46@gmail.com)
And users should be able to provide their personal experience
regarding medical treatments which they used.
Nonfunctional requirements
For any information system, non-functional requirements will also play a major
role of the success of that information system. These non-functional
requirements will provide the atmosphere and environment to achieve success
of functional requirements. We identified several non-functional requirements,
which will be essential to our Information System.
User Friendliness
User friendliness is one of most important part of our proposed
system. Because in our system many of end users will be public
and patients. So, it is essential to provide maximum user
friendliness because those end users will not be that much
technically expert people. Our goal is to provide an information
system, which will be very comfortable to use and very flexible.
Secure
Security will play another major part of an information system.
Without proper security implementations, we cannot provide the
information system product to the end users. We are hoping to
develop User levels, user logins, user authentications, system
logbooks and many other features to make sure the developed
system is fully secure.
Accuracy
In addition, the developed information system should be very
accurate because at the end of the day, it is a matter of life. For
example, if we could not provide accurate information for a
particular diagnosis, user may end up with trouble that is more
serious. Therefore, we hope to put our maximum focus on this, and
we are expecting to provide 100% accurate system at the end of the
project.
Reliability
The reliability of the system is also a crucial matter. The system
should build up its reliability gradually along with the system
Document shared on www.docsity.com
Downloaded by: hakeem-haniffa (hakeem.haniffa46@gmail.com)
maturity by providing truly accurate solutions & details that
enhances user satisfaction.
Availability
The system should be readily available & freely accessible at any
given moment to all the users
The solutions
There are many ways available to implement an information system and as a
development team we have to make sure that we are choosing the most feasible
solution. We can identify several alternative methods to develop an information
system,
 Internet based Information System.
 Intranet based Information System.
 Stand-alone Information System.
 Customizing available Information system to meet client requirements.
We are developing a Medical Information System, which will provide
up-to date information, latest news, articles, newsletters, with the opportunity to
provide articles, comments, questions, personal experiences, to the system.
More importantly, the end users of the system will be general public. Therefore,
our client requested us to develop a public Internet Web site, which will address
the potential problems.
For that reason, any other viable alternative methods to develop the
system could not be identified other than developing a public internet site. So,
we are mainly focusing on that. Apart from that we also focused on measuring
the feasibility of a stand-alone system as an alternative solution. This standalone system will include all the information from both the western and
conventional medical system point of views and it a will also have various
articles, answers to common questions and other implementable stuffs. But, this
system will not offer the opportunity to provide articles, comments, questions,
personal experiences of users. This stand-alone system can be obtained from our
client and after developing the complete system, they will be able to publish
updated versions like, once 3 months.
In the rest of this report, we will analyze the feasibility of these two
solutions from different feasibility analysis methods.
Document shared on www.docsity.com
Downloaded by: hakeem-haniffa (hakeem.haniffa46@gmail.com)
What is Feasibility study?
Feasibility is the measure of how beneficial / practical an information system
will be to an organization. A feasibility study looks at the viability of an idea
with an emphasis on identifying potential problems and attempts to answer one
main question: Will the idea work and should you proceed with it?
When assessing feasibility of a project following criteria can be identified.
1.
Operational Feasibility
2.
Technical Feasibility
3.
Economic Feasibility
4.
Schedule Feasibility
5.
Legal Feasibility
6.
Cultural Feasibility
Operational Feasibility
·
A measure of how well a solution meets the identified system
requirements to solve the problem.
·
Take advantage of the opportunities identified during the scope definition
and problem analysis phases.
 Will the solution fulfill the users’ requirements? To what
degree?
 How will the solution change the users’ work environment?
 How do users feel about such a solution?
Technical Feasibility
·
A measure of the practicality of a technical solution & the
availability of technical recourses and expertise
·
Addresses these major issues
 Is the proposed technology or solution practical?
 Do we possess the necessary technical expertise?
(Hardware/Personnel)?
Economic Feasibility
Document shared on www.docsity.com
Downloaded by: hakeem-haniffa (hakeem.haniffa46@gmail.com)
·
·
A measure of the cost-effectiveness of a project
Will address three major issues

Is the solution cost-effective?

Whether the solution will pay for itself?

How profitable the solution is?
Schedule Feasibility
·
A measure of how reasonable the project timetable is.
 Can the solution be designed and implemented during the
acceptable time frame?
 How much time is available to build the new system?
 When it can be built? (Mandatory / Desirable deadlines.)
Cultural Feasibility
A measure of how well the solution will be accepted in each organizational
climate
 Deals with how the end users feel about the proposed
system.
 Evaluates whether a system will work in each organizational
climate.
Legal Feasibility
·
A measure of how well a solution can be implemented within existing legal
and contractual obligations.
·
Understands potential legal and contractual ramifications of the system
 copyright law
 code ownership
Document shared on www.docsity.com
Downloaded by: hakeem-haniffa (hakeem.haniffa46@gmail.com)
Internet based Information System (recommended solution)
Internet based system seems to be the most feasible solution & because of
that will be considered as the recommended solution to continue into the
implementation stage.
Operational feasibility
·
Considering the security of this solution this will be the most insecure
system. Since anybody in the world can access the system through the internet.
The security aspect will have to be strictly dealt with. Users will have to log in
to the system using their usernames & passwords. Authentication of the user
will limit the ability of unsecured entrance. However, that does not solve the
entire problem.
·
The system can be updated easily online & the users will always
experience an up-to-date system.
·
No additional troubles to go through complex installation processes. Will
work through the usual web browser.
·
No platform dependency. Any user can access the web site using their
existing web browsers
·
Availability of the system will depend on the availability of the internet
facility.
·
The speed of the internet facility will also be a very important factor
when determining the speed of access of a particular user.
·
The general users need not to have technical expertise to use the site.
·
Traditional patients may be rather comfortable going to their usual doctor
due to customized treatments. So, the resistance to change might affect the
system usage.
Document shared on www.docsity.com
Downloaded by: hakeem-haniffa (hakeem.haniffa46@gmail.com)
·
Modern users on the other hand may prefer the ease of reach.
·
The demanding quality required in the article maintenance, created by the
intense competition from the available sites will have to be addressed.
·
The medical board will have to comprise of experts covering all the
relevant areas in both the medical systems.
·
System administrators in accordance with the functional policies of the
institute will do granting access levels.
Cultural feasibility
·
Physical absence of the patient may confuse the traditional patients. Both
the medical systems demand a lot of physical evidence being examined prior to
the medical prescription.
·
The language barriers will not be material. The user friendliness of the
system & the high level of interactivity will eliminate the need of the language
fluency.
·
The different medical practices in different parts of the country will be
respected evenly when preparing the articles & recommending the solutions.
Economic feasibility
·
The cost of medical servicing will be considerably low compared to the
normal consultation process.
·
But the maintenance costs of the system will demand a certain level of
income from the site.
·
Once the system creates its audience, the system will be in a position to
recover its expenses through publishing various advertisements on the page.
Document shared on www.docsity.com
Downloaded by: hakeem-haniffa (hakeem.haniffa46@gmail.com)
When exploring the economic feasibility of the system a cost benefit
analysis would evaluate the benefits of the system against its costs.
Cost Benefit Analysis
BENEFITS
•
Less cost compared to the normal individual consultation.
•
Higher flexibility with number of alternative solutions.
•
Very high levels of readily available information.
•
Providing information on solutions from both the ends.
•
Rare comparisons among solutions.
•
Very interactive user experience.
•
Providing articles enhancing the public awareness on health
related issues.
•
Ability to direct the doubts to experts
•
Providing a professional platform for health discussions.
•
A forum to share the individual viewpoints & experiences.
•
Innovations
communicated.
in
both
the
medical
systems
will
be
•
Providing maps directing the hospitals clinics indigenous
medical centers & other medical recourses locally.
•
Facilitating the researchers to reach the interested crowd to
direct their questionnaires.
•
Out of box medical scope covering a vast area on both
medical systems
COSTS
Document shared on www.docsity.com
Downloaded by: hakeem-haniffa (hakeem.haniffa46@gmail.com)
DEVELOPMENTCOSTS
·
Hardware Costs No need to purchase new hardware. Existing resources in
premises & the personal hardware of the users will be used.
·
Software costs Free & open-source software will be used in the
development
·
Initial implementation Costs
No initial installation cost. (Free hosting)
OPERATIONAL COSTS (to the client when using the site)
•
Payments to the expert medical board
•
Salaries of the administrative staff
•
Expenses of the physical location
•
Other over heads.
•
PCs and other technical equipment costs
•
Software costs in development.
It is evident that benefits of the system clearly outweigh the costs of the
system.
Since most of the benefits mentioned above are intangible & non-monitory, an
estimate cannot be prepared with a reasonable level of accuracy.
Technical Feasibility
Technical feasibility considers main 3 factors.
Document shared on www.docsity.com
Downloaded by: hakeem-haniffa (hakeem.haniffa46@gmail.com)
Is the proposed solution practical?
Do we currently possess the necessary technology?
Do we have the expertise needed to develop the solution?
Technologies used in the project
For an Internet based system there are lots of available resources today.
·
Web development:
Client-side scripting: HTML
Server-side scripting: PHP, ASP.net, Perl
·
Web servers: Apache, Microsoft IIS, Google web server
·
Database management systems: Oracle, MySQL, Microsoft SQL
server, MS Access
Freely available technologies will be exhausted in the development process. The
technologies we are supposed to use in this system are
·
Web development:
Client-side scripting: HTML, XHTML, VB Script
Server-side scripting: PHP and other related technologies
·
Web servers: Apache
Document shared on www.docsity.com
Downloaded by: hakeem-haniffa (hakeem.haniffa46@gmail.com)
·
Database management systems : MySQL
Ø Is the proposed solution practical?
All the technologies mentioned above which we propose to use in our
project are very matured and open source technologies. Because of their
maturity it is enough to build up a stable web system well known among
technicians.
Ø Do we currently possess the necessary technology?
All the technologies that we proposed to use are free and open source, so
they are easily obtainable and available for almost any software platform.
Therefore the possession of the technology is not a problem.
Ø Do we have the expertise needed to develop the solution?
All the members in the group are familiar with these technologies.
Members share the technical knowledge among each other. So expertise is not a
problem. Members of the group will employ their effort & time to the project
within their maximum capacity.
Document shared on www.docsity.com
Downloaded by: hakeem-haniffa (hakeem.haniffa46@gmail.com)
6.5 Schedule feasibility
Schedule feasibility will look at whether it is possible to build a
successful solution to the given problem, within the time frame given. The
Gantt chart shows the mandatory deadlines that we are expected to achieve. We
have created our project plan considering the given time line.
6.6 Legal Feasibility
Legal feasibility involves in verifying the legal validity of the proposed system.
Ø Copyrights Issues
We are using free and open source technologies and tools in developing
our system. Therefore, there is no violation of any laws. If any articles or
images from any other publication used in the site, we will exclude the liability
by indicating their respective reference sources.
Ø Government Constraints
Since the proposed system is implemented in a government institute, it
may be subject to rules & regulations imposed & even funding constraints.
7.0 Stand-Alone Information System (alternative solution)
Document shared on www.docsity.com
Downloaded by: hakeem-haniffa (hakeem.haniffa46@gmail.com)
Stand-alone system will be the alternative option incase if the recommended
option (internet-based system) goes unviable.
7.1
Operational Feasibility
Ø Will the solution fulfill the user’s Requirements?
·
The system is supposed to provide enormous details to the general
public. But, if the system is going to be a standalone one it is doubt full
whether the system will truly be able to achieve this functionality.
Because the audience that will be benefiting is going to be very low with
a standalone system.
·
If the system is going to be a standalone one it is difficult to provide realtime details through the site. As an example if there is a dangerous virus
spreading through the environment, we cannot acknowledge the users how to
protect themselves through the system. So, keeping the system up to date is
going to be exhaustive.
·
Users will not have the opportunity to provide articles, comments,
questions, personal experiences of users.
·
The user interactions with the system will reduce. Because users cannot
access the system at any time that they want.
·
If the system is a standalone, one the general public will not use it as
much as we expected. So, in this case people won’t be interested to edit articles
even if they are published.
Ø How will the solution change the users’ work environment?
·
If this is a standalone solution or a web based one, In Sri Lanka people are
used to consult a doctor when they are suffering from some kind of a diagnosis.
If we introduce a standalone, system that habit will not change as we expected.
Document shared on www.docsity.com
Downloaded by: hakeem-haniffa (hakeem.haniffa46@gmail.com)
Ø How do the users feel about such a solution?
·
Users of this system especially traditional general public will pay less
attention on this system because they might feel that consulting a doctor is
easier than using a system like this due to their technological unfriendliness.
7.2
Schedule Feasibility
Ø Can the solution be implemented during the acceptable time frame?
·
As we are concerned on a stand-alone solution, it should be more
perfected & completed than a web based solution. Because we cannot update
the system daily. So, a standalone solution will take more time than a web based
solution.
7.3
Economic Feasibility
Under those questions we have to concern on
·
Hardware cost - Hardware requirements we must use for a standalone
system
usually
higher than web based system because the all the features should be
included in to the system when we implement it.
·
Software cost - We can use freely available software to
implement this.
·
Personal cost - Cost of programmers, salaries of other workers,
when considering the stand-alone system may be high because a
programmers are expensive than web designers.
Document shared on www.docsity.com
Downloaded by: hakeem-haniffa (hakeem.haniffa46@gmail.com)
·
Maintain cost - When standalone system maintains cost is high.
We have to introduce new things to the systems as different versions of
the systems.
7.4
Technical Feasibility
Ø Technologies
For the implementation of these systems, we can use free and open source
software. They are easily obtainable and available for almost any platform.
·
C++ , Java
·
MYSQL
·
Apache
Ø Is the propose technology or solution practical?
As a stand-alone system, this has to be updated manually. To update the
system it needs more case tools and expertise. It is extra expensive for Institute
to maintaining the system.
Ø Do we possess the necessary technical expertise?
As a result of updating the system manually Institute needs expertise
team to updating process.
7.5
Cultural Feasibility
·
Users feel good about our system because it is going to make their work
easier.
Document shared on www.docsity.com
Downloaded by: hakeem-haniffa (hakeem.haniffa46@gmail.com)
·
But, the system is run in one place. So general users have to go to the
place where the system is held. Because of that, the system affects the existing
culture of the user.
·
And it is a time waste. It can also be a reason to avoid this system.
·
People do not have a method to compare western and conventional
medicine. The system provides this facility to users.
·
After releasing the system it will give good impression to public about
the institute.
7.6
·
Legal Feasibility
Users will have to obey the rules and regulations of the Institute.
·
All the information is under the authority of the system administrator. So
all the information is secured.
8.0 Feasibility Analysis Matrix
OPERATIONAL
FEASIBILITY
TECHNICAL
FEASIBILITY
WEIGHT
STAND-ALONE
SYSTEM
30%
• Low number
of end users.
• High
security.
• Cannot
provide up-to
date
information.
INTERNET
BASED
SYSTEM
• High number
of end users.
• Security
problems.
• Up-to date
information.
• Easy to use.
SCORE - 80
SCORE - 40
• Easy to
implement.
• No network
• Easy to
implement.
• Internet
30%
Document shared on www.docsity.com
Downloaded by: hakeem-haniffa (hakeem.haniffa46@gmail.com)
ECONOMIC
FEASIBILITY
15%
CULTURAL
FEASIBILITY
10%
connection
needed.
SCORE - 75
• Less
implementation
cost.
• Updating
cost may high.
SOCRE - 50
• Lots of
diagnosis needs
physical
treatment.
• May not use
because not upto date.
SCORE - 45
SHEDULE
FEASIBILITY
7.5%
LEGAL
FEASIBILITY
7.5%
RANKING
100%
• Implemented
with available
time.
SCORE - 80
• Illegally can
duplicate.
• Government
rules and
regulations will
apply.
SCORE - 60
57
Document shared on www.docsity.com
Downloaded by: hakeem-haniffa (hakeem.haniffa46@gmail.com)
connection
needed.
SCORE - 70
• Less
implementation
cost.
• Less
maintenance
cost.
SOCRE - 80
• Lots of
diagnosis needs
physical
treatment.
• Will use
because up-to
date
information.
• Familiar with
internet.
SCORE - 65
• Implemented
with available
time.
SCORE - 80
• Government
rules and
regulations will
apply.
SCORE - 70
75
8.0 Conclusion
According to the above descriptive feasibility analysis report and the feasibility
matrix, the most feasible solution from the candidate solutions seems to be the
internet based system. Therefore, the implementation will be carried forward
with this option. But, in case if this preferred option is unviable, we will have to
continue with the next best alternative solution mentioned. We have analyzed
the feasibility of that option as well. However, that does not seem to be that
much a feasible solution. So, our expectation is to implement the web based
internet site which optimally meets our client expectations. The users will be
able to access the system through internet, which is already available to them.
The system will be available to the users at any time at any place, where they
have access to the internet
Document shared on www.docsity.com
Downloaded by: hakeem-haniffa (hakeem.haniffa46@gmail.com)
Grading Criteria
Achieved
Feedback
LO1 Evaluate the strengths and weaknesses of the
traditional and agile systems analysis methodologies.
P1 Discuss the strengths and weaknesses of the traditional
and agile systems analysis methodologies.
M1 Compare and contrast the strengths and weaknesses of
the traditional and agile systems analysis methodologies.
LO2 Produce a feasibility study for a system for a
business-related problem.
P2 Produce a feasibility study for a system for a
business related problem.
M2 Evaluate the relevance of the feasibility criteria on
Document shared on www.docsity.com
Downloaded by: hakeem-haniffa (hakeem.haniffa46@gmail.com)
the systems investigation for the business related
problem.
LO1 & 2
D1 Critically evaluate the strengths and weaknesses of
the traditional and agile systems analysis methodologies,
including the transition problems faced by organisations
that move from the traditional to the agile approach.
LO3 Analyse their system using a suitable
Methodology
P3 Analyse a system using a suitable methodology for a
business-related problem.
M3 Evaluate the effectiveness of the analysis in the
context of the methodology used.
LO4 Design the system to meet user and system
Requirements
Document shared on www.docsity.com
Downloaded by: hakeem-haniffa (hakeem.haniffa46@gmail.com)
P4 Design a fully functional system to meet user and
system requirements for the business related
problem.
M4 Assess the effectiveness of the system design with
particular reference to the methodology used and how
the design meets user and system requirements.
LO3 & 4
D2 Justify the choice of the analysis methodology used in
the context of the business problem.
Document shared on www.docsity.com
Downloaded by: hakeem-haniffa (hakeem.haniffa46@gmail.com)