Unit 34 - System Analysis

Higher Nationals
Internal verification of assessment decisions – BTEC (RQF)

INTERNAL VERIFICATION – ASSESSMENT DECISIONS
Programme title HND in Computing
Mrs. Gagani
Assessor Internal Verifier
Unit 34: System Analysis & Design
Unit(s)
Automated system for E-Solutions Private Limited
Assignment title
M.S.M HISHMATHDEEN
Student’s name
List which assessment criteria Pass Merit Distinction
the Assessor has awarded.
INTERNAL VERIFIER CHECKLIST
Do the assessment criteria awarded match

those shown in the assignment brief? Y/N
Is the Pass/Merit/Distinction grade awarded

justified by the assessor’s comments on the Y/N
student work?
Has the work been assessed
Y/N
accurately?
Is the feedback to the student:
Give details:
• Constructive? Y/N
• Linked to relevant assessment criteria? Y/N
• Identifying opportunities for Y/N
improved performance?
• Agreeing actions? Y/N
Does the assessment decision need
Y/N
amending?
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 Verifier
Date
signature
Programme Leader
Date
signature (if required)
M.S.M HISHMATHDEEN SAD 1

Higher Nationals - Summative Assignment Feedback Form
Student Name/ID M.S.M Hishmathdeen KLT/A-006044
Unit Title Unit 34: System Analysis & Design
Assignment Number 1 Assessor Mrs. Gagani

28.07.2021 Date Received
Submission Date
1st submission
Date Received 2nd
Re-submission Date
submission
Assessor Feedback:
LO1 Evaluate the strengths and weaknesses of the traditional and agile systems analysis
methodologies
Pass, Merit & Distinction P1 M1 D1
Descripts
LO2 Produce a feasibility study for a system for a business-related problem

Pass, Merit & Distinction P2 M2
Descripts
LO3 Analyse their system using a suitable methodology.

Pass, Merit & Distinction P3 M3 D2
Descripts
LO4 Design the system to meet user and system requirements.

Pass, Merit & Distinction P4 M4
Descripts
Grade: Assessor Signature: 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.

Pearson Higher Nationals in
Computing
Unit 34: Systems Analysis & Design
Assignment 01

General Guidelines
1. A Cover page or title page – You should always attach a title page to your assignment. Use
previous page as your cover sheet and make sure all the details are accurately filled.
2. Attach this brief as the first section of your assignment.
3. All the assignments should be prepared using a word processing software.
4. All the assignments should be printed on A4 sized papers. Use single side printing.
5. Allow 1” for top, bottom , right margins and 1.25” for the left margin of each page.
Word Processing Rules
1. The font size should be 12 point, and should be in the style of Time New Roman.
2. Use 1.5 line spacing. Left justify all paragraphs.
3. Ensure that all the headings are consistent in terms of the font size and font style.
4. Use footer function in the word processor to insert Your Name, Subject, Assignment No, and
Page Number on each page. This is useful if individual sheets become detached for any
reason.
5. Use word processing application spell check and grammar check function to help editing your
assignment.
Important Points:
1. It is strictly prohibited to use textboxes to add texts in the assignments, except for the
compulsory information. eg: Figures, tables of comparison etc. Adding text boxes in the body
except for the before mentioned compulsory information will result in rejection of your work.
2. Avoid using page borders in your assignment body.
3. Carefully check the hand in date and the instructions given in the assignment. Late
submissions will not be accepted.
4. Ensure that you give yourself enough time to complete the assignment by the due date.
5. Excuses of any nature will not be accepted for failure to hand in the work on time.
6. You must take responsibility for managing your own time effectively.
7. 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.
8. Failure to achieve at least PASS criteria will result in a REFERRAL grade .
9. Non-submission of work without valid reasons will lead to an automatic RE FERRAL. You will
then be asked to complete an alternative assignment.
10. If you use other people’s work or ideas in your assignment, reference them properly using
HARVARD referencing system to avoid plagiarism. You have to provide both in-text citation
and a reference list.
11. If you are proven to be guilty of plagiarism or any academic misconduct, your grade could be
reduced to A REFERRAL or at worst you could be expelled from the course

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 Pearson , 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:
Hishmathdeen122@gmail.com Date: 28.07.2021

(Provide E-mail ID) (Provide Submission Date)

Higher National Diploma in Computing
Assignment Brief
Student Name /ID Number M.S.M Hishmathdeen KLT/A-006044
Unit Number and Title Unit 4: Systems Analysis & Design
Academic Year 2021/22
Unit Tutor
Assignment Title Automated system for E-Solutions Private

Limited
Issue Date
Submission Date
IV Name & Date
Submission format
The submission should be in the form of an individual written report 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 Please provide in-test citations, reference list and
bibliography using Harvard referencing system. Please also provide a bibliography using
the Harvard referencing system.
The recommended word limit is not less than 5000 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:
*Please note that assignment guidance is for reference only and should be more specific
in detail to meet customized needs.
Assignment brief
Case study
The new automated system is designed to replace the current, manual, error-prone
process of E-Solutions private Limited. The automation of existing process is to reduce the
company’s expenses and enhance the productivity significantly. This transformation also
would support for:
1) Successful teams working
2) Completing projects on time and within budget due to a better understanding of system
requirements and tasks to be completed
3) Starting projects on time through automated project scheduling system.
In the proposed system, the Project director creates a project and a “project profile” for
each project. The creation of the project profile includes identification of project
employee costs, the assignment of tasks to the project, and the assignment of a project
manager. The project profile is consisted of project id, project personnel cost, a list of
tasks assigned, and the project manager. The Project director also creates the teams for
a given project, assigns employees to the teams, and assigns a team leader. The Project
manager is responsible for assigning tasks to various teams working on the projects(s).
The Team Leader assigns tasks to the team members.
Additional functionality includes:

• Produce and update information about different software projects, project teams,
specific team member assignments and team skills.
• Perform function point analysis to identify the personnel cost of the project and provide
information to generate invoices upon completion of project phases.
• Monitor projects and identify completed tasks and ongoing tasks of each project.

Activity 01
Discuss traditional and agile system analysis methodologies used in the industry by
comparing and contrasting the strengths and weaknesses of them. Critically evaluate two
methodologies by referring to the examples to support your answer.
Activity 2
Produce a feasibility report for the scenario given above and assess the importance of
feasibility criteria used for the system investigation. Critically evaluate the strengths and
weaknesses of feasibility study with relevant to the proposed solution.
Activity 3
Analyse and review the system requirements of the proposed solution given in the
scenario using a suitable methodology. Functional and non-functional requirements of
the system should be clearly mentioned. Assessment of the effectiveness and suitability
of the chosen methodology should be provided with proper justifications.
Activity 4
Produce a system design specification for the above scenario and assess the effectiveness
of your design and the methodology used with reference to how it meets the user
requirements.
Your system design specification should include architectural design, interface design,
database design, and program design.

Table Of Content
Acknowledgement ................................................................................................................... 13
Abbreviation ............................................................................................................................. 14
Introduction ............................................................................................................................. 15
Activity 01................................................................................................................................. 16
comparing and contrasting the strengths and weaknesses of them. Critically evaluate two
methodologies by referring to the examples to support your answer. .............................. 16
What is a system .............................................................................................................. 16
A system is a grouping of elements or components that work together to achieve a
common goal. A computer system is made up of hardware components that have been
carefully selected to work well together, as well as software components or programs
that run on the computer. ............................................................................................... 16
System development life cycle ........................................................................................ 16
Traditional Software Development Methodology ............................................................... 20
Waterfall Software Development Methodology ............................................................. 22
Spiral Software Development Methodology ................................................................... 24
Agile Software Development Methodology .................................................................... 26
Strengths and weaknesses of the traditional and agile systems analysis methodologies
.......................................................................................................................................... 29
Activity 02................................................................................................................................. 33
feasibility criteria used for the system investigation. Critically evaluate the strengths and
weaknesses of feasibility study with relevant to the proposed solution. ........................... 33
What Is a Feasibility Study? ............................................................................................. 33
The goals of feasibility studies ......................................................................................... 33
Steps in a Feasibility Study ............................................................................................... 34
Types of Feasibility Study ................................................................................................. 34
Feasibility report of Automated system for E-Solutions Private Limited ........................ 36
Activity 03................................................................................................................................. 43
of the chosen methodology should be provided with proper justifications. ...................... 43
Tools and Techniques that can be used to analyse system requirements ...................... 43

Most suitable methodology for the analysis of the system and how that can be used to
improve the effectiveness of the analysis stage.............................................................. 45
Activity 04................................................................................................................................. 48
requirements. Your system design specification should include architectural design,
interface design, database design, and program design. .................................................... 48
Interface Screenshot of Fully functional system to meet user and system requirements.
And Assess the effectiveness of the system design with reference to the methodology
used and how the design meets user and system requirements. ................................... 48
Conclusion ................................................................................................................................ 67
Annexures ................................................................................................................................ 68

Table of figures
Figure 1 : System development life cycle................................................................................. 17

Figure 2 : Traditional Software Development Methodology ................................................... 20
Figure 3 : Waterfall model design ............................................................................................ 22
Figure 4 : Spiral Model ............................................................................................................. 24
Figure 5 : Agile Scrum Methodology ........................................................................................ 26
Figure 6 : Difference of development methodologies ............................................................. 27
Figure 7 : Picture 1 ................................................................................................................... 28
Figure 8 : Project Gann chart .................................................................................................. 42
Figure 9 : Agile Methodology-Scrum Process .......................................................................... 46
Figure 10 : Interface 1 .............................................................................................................. 48
Figure 15 : Login page flow chart ............................................................................................. 53
Figure 16 : Create page display flow chart............................................................................... 53
Figure 17 : Project manager flowchart .................................................................................... 54
Figure 18 : Team leader flowchart ........................................................................................... 54
Figure 19 : ER Diagram of full system ...................................................................................... 55
Figure 20 : Level 1 dataflow diagram ....................................................................................... 55
Figure 21 : Level 2 dataflow diagram ....................................................................................... 56
Figure 22 : Gann Chart ............................................................................................................. 69
Table 1 : Difference between Traditional and Agile Software Development .......................... 32

Acknowledgement
This assignment would not have been possible without the many contributors. They are our
lecturer Mrs. Gagani Thilakarathna and Mr. Indika Sadanuwan Branch Manager of Esoft
Metro College Kalutara, my friends in HND 010 and my parents. I would like to thank all of
you for my success. In addition, who helped me and motivated me to this work all are thank
you.

Abbreviation
➢ SDLC – Software Development Life Cycle

➢ CSS – Cascading Style Sheets
➢ HTML – Hyper Text Markup Language
➢ PHP – Personal Home Page
➢ SQL – Structured Query Language
➢ XP – Extreme Programming
➢ RAM – Random Access Memory
➢ VGA – Video Graphics Array
➢ OS – Operating System
➢ DFD – Data Flow Diagram
➢ ER - Entity Relationship
➢ UCD - User Case Diagram

Introduction
The new automated system is designed to replace the current, manual, error-prone process of
E-Solutions private Limited. The automation of existing process is to reduce the company’s
expenses and enhance the productivity significantly. This transformation also would support
for:
1) Successful teams working
2) Completing projects on time and within budget due to a better understanding of system
3) Starting projects on time through automated project scheduling system.

Activity 01
comparing and contrasting the strengths and weaknesses of them. Critically evaluate
two methodologies by referring to the examples to support your answer.
What is a system
A system is a grouping of elements or components that work together to achieve a common

goal. A computer system is made up of hardware components that have been carefully
selected to work well together, as well as software components or programs that run on the
computer.
System development life cycle
The system-development life cycle enables users to transform a newly-developed project into
an operational one.
The System Development Life Cycle, "SDLC" for short, is a multistep, iterative process,
structured in a methodical way. This process is used to model or provide a framework for
technical and non-technical activities to deliver a quality system which meets or exceeds a
business’s expectations or manage decision-making progression.
Traditionally, the systems-development life cycle consisted of five stages. That has now
increased to seven phases. Increasing the number of steps helped systems analysts to define
clearer actions to achieve specific goals.
Similar to a project life cycle (PLC), the SDLC uses a systems approach to describe a process.
It is often used and followed when there is an IT or IS project under development.
The SDLC highlights different stages (phrases or steps) of the development process. The life
cycle approach is used so users can see and understand what activities are involved within a
given step. It is also used to let them know that at any time, steps can be repeated or a previous
step can be reworked when needing to modify or improve the system.

Figure 1 : System development life cycle
Following are the seven phases of the SDLC
1. Planning
This is the first phase in the systems development process. It identifies whether or not there is
the need for a new system to achieve a business"s strategic objectives. This is a preliminary
plan (or a feasibility study) for a company"s business initiative to acquire the resources to
build on an infrastructure to modify or improve a service. The company might be trying to
meet or exceed expectations for their employees, customers and stakeholders too. The
purpose of this step is to find out the scope of the problem and determine solutions.
Resources, costs, time, benefits and other items should be considered at this stage.
2. Systems Analysis and Requirements
The second phase is where businesses will work on the source of their problem or the need
for a change. In the event of a problem, possible solutions are submitted and analyzed to
identify the best fit for the ultimate goal(s) of the project. This is where teams consider the

functional requirements of the project or solution. It is also where system analysis takes
place—or analyzing the needs of the end users to ensure the new system can meet their
expectations. Systems analysis is vital in determining what a business"s needs are, as well as
how they can be met, who will be responsible for individual pieces of the project, and what
sort of timeline should be expected.
There are several tools businesses can use that are specific to the second phase. They include:
• CASE (Computer Aided Systems/Software Engineering)

• Requirements gathering
• Structured analysis
3. Systems Design
The third phase describes, in detail, the necessary specifications, features and operations that
will satisfy the functional requirements of the proposed system which will be in place. This is
the step for end users to discuss and determine their specific business information needs for
the proposed system. It"s during this phase that they will consider the essential components
(hardware and/or software) structure (networking capabilities), processing and procedures for
the system to accomplish its objectives.
4. Development
The fourth phase is when the real work begins—in particular, when a programmer, network
engineer and/or database developer are brought on to do the major work on the project. This
work includes using a flow chart to ensure that the process of the system is properly
organized. The development phase marks the end of the initial section of the process.
Additionally, this phase signifies the start of production. The development stage is also
characterized by instillation and change. Focusing on training can be a huge benefit during
this phase.
5. Integration and Testing
The fifth phase involves systems integration and system testing (of programs and
procedures)—normally carried out by a Quality Assurance (QA) professional—to determine
if the proposed design meets the initial set of business goals. Testing may be repeated,
specifically to check for errors, bugs and interoperability. This testing will be performed until

the end user finds it acceptable. Another part of this phase is verification and validation, both
of which will help ensure the program"s successful completion.
6. Implementation
The sixth phase is when the majority of the code for the program is written. Additionally, this
phase involves the actual installation of the newly-developed system. This step puts the
project into production by moving the data and components from the old system and placing
them in the new system via a direct cutover. While this can be a risky (and complicated)
move, the cutover typically happens during off-peak hours, thus minimizing the risk. Both
system analysts and end-users should now see the realization of the project that has
implemented changes.
7. Operations and Maintenance
The seventh and final phase involves maintenance and regular required updates. This step is
when end users can fine-tune the system, if they wish, to boost performance, add new
capabilities or meet additional user requirements.
(Atlanta, 2019)

Traditional Software Development Methodology
Figure 2 : Traditional Software Development Methodology
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.
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.
(Indusree, 2018)

Waterfall Software Development Methodology
The first Process Model to be introduced was the Waterfall Model. A linear-sequential life
cycle model is another name for it. It is very easy to comprehend and use. In a waterfall
model, each phase must be completed before moving on to the next, and the phases do not
overlap. The Waterfall model is the most basic SDLC approach for software development.
The waterfall model depicts the software development process as a sequential flow of events.
This means that any phase of the development process can start only after the previous one
has finished. The phases in this waterfall model do not overlap.
Figure 3 : Waterfall model design
• Requirement Gathering and analysis − All possible requirements of the system to

be developed are captured in this phase and documented in a requirement specification
document.
• System Design − The requirement specifications from first phase are studied in this
phase and the system design is prepared. This system design helps in specifying
hardware and system requirements and helps in defining the overall system
architecture.

• Implementation − With inputs from the system design, the system is first developed
in small programs called units, which are integrated in the next phase. Each unit is
developed and tested for its functionality, which is referred to as Unit Testing.
• Integration and Testing − All the units developed in the implementation phase are
integrated into a system after testing of each unit. Post integration the entire system is
tested for any faults and failures.
• Deployment of system − Once the functional and non-functional testing is done; the
product is deployed in the customer environment or released into the market.
• Maintenance − There are some issues which come up in the client environment. To
fix those issues, patches are released. Also to enhance the product some better versions
are released. Maintenance is done to deliver these changes in the customer
environment.
Major advantages of the Waterfall Model

• Simple and easy to understand and use
• Easy to manage due to the rigidity of the model. Each phase has specific deliverables
and a review process.
• Phases are processed and completed one at a time.
• Works well for smaller projects where requirements are very well understood.
• Clearly defined stages.
• Well understood milestones.
• Easy to arrange tasks.
• Process and results are well documented.
Major disadvantages of the Waterfall Model
• No working software is produced until late during the life cycle.
• High amounts of risk and uncertainty.
• Not a good model for complex and object-oriented projects.
• Poor model for long and ongoing projects.
• Not suitable for the projects where requirements are at a moderate to high risk of
changing. So, risk and uncertainty is high with this process model.
• It is difficult to measure progress within stages.
• Cannot accommodate changing requirements.
• Adjusting scope during the life cycle can end a project.

Spiral Software Development Methodology
The spiral model combines the idea of iterative development with the systematic, controlled
aspects of the waterfall model. This Spiral model is a combination of iterative development
process model and sequential linear development model i.e. the waterfall model with a very
high emphasis on risk analysis. It allows incremental releases of the product or incremental
refinement through each iteration around the spiral.
Figure 4 : Spiral Model
Identification
This phase starts with gathering the business requirements in the baseline spiral. In the
subsequent spirals as the product matures, identification of system requirements, subsystem
requirements and unit requirements are all done in this phase.
This phase also includes understanding the system requirements by continuous

communication between the customer and the system analyst. At the end of the spiral, the
product is deployed in the identified market.

Design
The Design phase starts with the conceptual design in the baseline spiral and involves
architectural design, logical design of modules, physical product design and the final design
in the subsequent spirals.
Construct or Build
The Construct phase refers to production of the actual software product at every spiral. In the
baseline spiral, when the product is just thought of and the design is being developed a POC
(Proof of Concept) is developed in this phase to get customer feedback.
Then in the subsequent spirals with higher clarity on requirements and design details a
working model of the software called build is produced with a version number. These builds
are sent to the customer for feedback.
Evaluation and Risk Analysis
Risk Analysis includes identifying, estimating and monitoring the technical feasibility and
management risks, such as schedule slippage and cost overrun. After testing the build, at the
end of first iteration, the customer evaluates the software and provides feedback.
The advantages of the Spiral SDLC Model

• Changing requirements can be accommodated.
• Allows extensive use of prototypes.
• Requirements can be captured more accurately.
• Users see the system early.
• Development can be divided into smaller parts and the risky parts can be developed
earlier which helps in better risk management.
The disadvantages of the Spiral SDLC Model
• Management is more complex.
• End of the project may not be known early.
• Not suitable for small or low risk projects and could be expensive for small projects.
• Process is complex
• Spiral may go on indefinitely.
• Large number of intermediate stages requires excessive documentation.

Agile Software Development Methodology
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 expectations. The following diagram illustrates the lifecycle
process in Agile methodologies.
Figure 5 : Agile Scrum Methodology

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 final 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 where as in Agile, it is iterative. Below picture illustrate this difference.
Figure 6 : Difference of development methodologies

The main project variables like cost, time, quality etc., can be compared as shown in the
following picture.
Figure 7 : Picture 1
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.
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
(Indusree, 2018)

Strengths and weaknesses of the traditional and agile systems analysis methodologies
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.

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.

Traditional model strengths
• The SDLC is a tried and tested approach that is very suitable for the development of large-
scale information systems.
• The traditional SDLC relies on the production of system documentation and standards of
development that can be used to guide the development of an information system and can be
used as reference and training material for users.
• The sequential and phased nature of the SDLC allows a complex systems development
problem to be broken down into manageable and understandable tasks.
• The SDLC relies on the use of formalized analysis and design tools and techniques that
graphically show the nature of data and information flows within the system.
• The structured nature of the traditional SDLC allows the incorporation of formal project
management techniques and tools to guide the systems development process.
Traditional model weaknesses

✓ 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.
✓ 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.
✓ 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.

✓ The SDLC ignores or underplays end-user involvement in the systems development
process. The end user is often faced with operating an information system that is user-
unfriendly or fails to deliver the user‟s requirements for the system.
✓ Over 90 per cent of IT-based systems development occurs within the business
environment. The use of computing and information technology within business
organizations is based on small desktop machines or personal computers, usually
networked locally (in a local area network within the organization) or connected to
the wider business environment (through a wide area network).
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 In this methodology, testing and development
development phase is totally completed. processes are performed concurrently.
It provides less security. It provides high security.
It provides less functionality in the software. It provides all the functionality 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.
Table 1 : Difference between Traditional and Agile Software Development

Activity 02
feasibility criteria used for the system investigation. Critically evaluate the strengths
and weaknesses of feasibility study with relevant to the proposed solution.
A feasibility report is a document that assesses potential solutions to the business problem or
opportunity and determines which of these are viable for further analysis.
The purpose of the feasibility report is to present the project parameters and define the
potential solutions to the defined problem, need, or opportunity. Having brainstormed a
variety of potential solutions, the project team expands on each of these potential solutions,
providing enough detail, including very high-level costing information, to permit the project
leader to recommend to the approving authority all of the viable potential solutions that should
be further analyzed in the next phase (Business Case). Project constraints and limitations of
expenditure are among the various factors that will determine viability.
What Is a Feasibility Study?

A feasibility study is an analysis that takes all a project's relevant factors into account
including economic, technical, legal, and scheduling considerations to ascertain the likelihood
of completing the project successfully. Project managers use feasibility studies to discern the
pros and cons of undertaking a project before they invest a lot of time and money into it.
Feasibility studies also can provide a company's management with crucial information that
could prevent the company from entering carelessly into risky businesses.
The goals of feasibility studies
➢ To understand thoroughly all aspects of a project, concept, or plan

➢ To become aware of any potential problems that could occur while implementing the
project
➢ To determine if, after considering all significant factors, the project is viable that is,
worth undertaking

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. Feasibility studies aim for marketing strategies that could help convince
investors or banks that investing in a particular project or business is a wise choice.
(KENTON, 2020)
Steps in a Feasibility Study
Conducting a feasibility study involves the following steps:
I. Conduct preliminary analyses.
II. Prepare a projected income statement. What are the possible revenues that the project
can generate?
III. Conduct a market survey. Does the project create a good or service that is in demand
in the market? What price are consumers willing to pay for the good or service?
IV. Plan the organizational structure of the new project. What are the staffing
requirements? How many workers are needed? What other resources are needed?
V. Prepare an opening day balance of projected expenses and revenue
VI. Review and analyse the points of vulnerability that are internal to the project and that
can be controlled or eliminated.
VII. Decide whether to go on with the plan/project.
Types of Feasibility Study
1. Technical feasibility
▪ Technical: Hardware and software
▪ Existing or new technology
▪ Manpower
▪ Site analysis
▪ Transportation

2. Financial feasibility
▪ Initial investment
▪ Resources to procure capital: Banks, investors, venture capitalists
▪ Return on investment
3. Market feasibility
▪ Type of industry
▪ Prevailing market
▪ Future market growth
▪ Competitors and potential customers
▪ Projection of sales
4. Organizational feasibility
▪ The organizational structure of the business
▪ Legal structure of the business or the specific project
▪ Management team’s competency, professional skills, and experience

Feasibility report of Automated system for E-Solutions Private Limited
E-Solutions private Limited
Automated system
Table of Contents
➢ Overview
➢ Objectives
➢ Users and Functional Requirements
➢ Feasibility Study
➢ Project Schedule

Overview
This Feasibility Report is for an Automated system for E-Solutions Private The automation
of existing process is to reduce the company’s expenses and enhance the productivity
significantly. This transformation also would support for:
a) Successful teams working
b) Completing projects on time and within budget due to a better understanding of system
c) Starting projects on time through automated project scheduling system.
In the proposed system, the Project director creates a project and a “project profile” for each
project. The creation of the project profile includes identification of project employee costs,
the assignment of tasks to the project, and the assignment of a project manager. The project
profile is consisted of project id, project personnel cost, a list of tasks assigned, and the project
manager.
Objective
The objective is to identify the opportunities and the drawbacks where the implementation of
a more advanced and efficient and accurate system is taken care of.
➢ To reduce the company’s expenses
➢ Enhance the productivity significantly
➢ Replace the current, manual, error-prone process

Users and Functional Requirements of System
The main functional users of the system are;
✓ Project Director
✓ Project Manager
✓ Project employees
Functional Requirements according to the users;
Project Director
▪ Creates a project
▪ Create project profile
▪ Creates the teams
▪ Assigns employees to the teams
▪ Assigns a team leader
Project Manager
▪ Project employee costs in created project profile
▪ Assignment of tasks to the project to employees
Project employees (Team Leader)
▪ Assigns tasks to the team members

Feasibility Study
1.Technical Feasibility
The technical resources available to the organization are the focus of this assessment. It aids
organizations in determining whether technical resources are adequate for the job and
whether the technical team is capable of turning concepts into working systems. The
proposed system's hardware, software, and other technical requirements are also evaluated
for technical feasibility.
Impact of technical Feasibility
In this says about technologies for use system creation. Developer must use new technologies
for creation. If use old technologies, May be system reject. Because people
like get a new experiences.
For example –
The following software and languages are used for the development of the online auction
system.
• Visual studio code
• Bootstrap
• MySQL
• A web browser (Ex: Google Chrome, Mozilla Firefox, Internet Explorer, etc.)
• Windows 7 or above
• HTML, CSS, PHP AND JavaScript are used in coding of the system

2. Economic Feasibility
This evaluation usually includes a cost-benefit analysis of the project, which aids
organizations in determining the project's viability, cost, and benefits before allocating
financial resources. It also serves as an independent project assessment and boosts project
credibility by assisting decision-makers in determining the proposed project's positive
economic benefits to the organization.
Impact of economic Feasibility
Economic feasibility determines whether the required software is capable of generating
financial gains for an organization. It involves the cost incurred on the software
development team, estimated cost of hardware and software, cost of performing feasibility
and so on. In addition it is necessary to consider the benefits that can be achieved by
developing the software. Software is said to be economically feasibility if it focuses on the
issues listed below.
• Cost incurred on software development to produce long-term gains for an
organization.
• Cost required to conduct full software investigation.
• Cost of hardware, software, development team and training.
For example –
For example, purchasing hardware and software requirements at a relatively low cost to
meet the requirements of the system.
3. Legal Feasibility
This assessment looks into whether any aspect of the proposed project violates any laws,
such as zoning laws, data protection laws, or social media laws. Assume a company wants
to build a new office building in a specific location. A feasibility study may reveal that the

ideal location for the company is not zoned for that type of business. That organization has
just saved a lot of time and effort by discovering early on that their project was not feasible.
Impact of legal feasibility
The project team have to make a thorough analysis of the legal issues surrounding the
project, across several dimensions. a detailed legal due diligence should be done to ensure
that all foreseeable legal requirements, which have not or will not be dealt with in other
appraisal exercises, are met for the development of the project.
For example –
It should align with the Data Protection Act to processing and protect user‟s data.
4. Operational Feasibility
This assessment entails conducting research to determine whether and how well the project
will meet the organization's requirements. Operational feasibility studies also look at how a
project plan meets the requirements identified during the system development requirements
analysis phase.
Impact of operational Feasibility
In this, we consider system running correctly. If system failed operational feasibility, every
works is failed in system.
For example –
• System administrators could be add, update and delete items in the auction.
• System administrators could store registered customers details.

5. Scheduling Feasibility
This evaluation is critical for project success; after all, if a project is not completed on time,
it will fail. An organization estimates the amount of time it will take to complete a project
when scheduling feasibility.
Impact of Schedule Feasibility
The process of assessing the degree to which the potential time frame and completion dates
for all major activities within a project meet organizational deadlines and constraints for
affecting change.
For example -
If a problem arise that would have prevented the project from being completed, the project
could not be completed within the allotted time. If this happens, the system’s most
important functions can be followed by an emergency schedule to complete.
Project Schedule
Figure 8 : Project Gann chart

Activity 03
of the chosen methodology should be provided with proper justifications.
Tools and Techniques that can be used to analyse system requirements
1. Context diagram
A system context diagram defines the system’s boundary, its surrounding environment, and
all the interacting entities. The system is plotted in the middle of the diagram and identifies
customers, external or internal systems, the organization’s end users and any vendors or
suppliers providing third-party services.
2. Functional decomposition
A functional decomposition diagram provides a top-down view of the business process and/or
the system’s major functions. When I think about what the system should do, I’ll use the
functional decomposition diagram to break it down into major chunks. This view also helps
validate all the functions the system should provide. It’s similar to an organization chart and
your end user should be able to easily relate to this model.
3. Use case diagram

The use case diagram helps depict the interaction between the system and its users. Each user
role is called an “actor” and different processes, or functions are represented in the diagram.
Each of these interactions can be further broken down into steps including the “happy path”
and alternative paths.
4. Sequence diagram
A sequence diagram shows the interactions between objects over time. It provides a top-to-
bottom view with messages being sent back and forth between the different objects. The
objects can be actors, systems or sub-packages within a system.

5. Mind maps
Mind mapping is another awesome tool to capture ideas, requirements and help organize a
conversation with many tangents. When you’re in a requirement gathering session, it is easy
to run off-topic and leap to another business process needed. Mind mapping helps to organize
the conversation by aligning comments, requirements and ideas with the major thought
branches in a conversation.
6.Business process modelling notation (BPMN)

BPMN (Business Process Modelling & Notation) is a graphical representation of your
business process using simple objects, which helps the organization to communicate in a
standard manner. Various objects used in BPMN includes
• Flow objects
• Connecting objects
• Swim lanes
• Artefacts.
7.Interviews
These are a valuable resource at the start of the process for gathering background information
on business problems and gaining a real-world understanding of what the proposed system
needs to accomplish. Make sure your interviews include a diverse cross-section of different
stakeholders so that the requirements aren't skewed toward one function or area.
▪ Structured Interview – it has a fixed format where the interviewer asks a
particular set of predetermined questions. In structured interviews, the questions
are planned and created in advance.
▪ Unstructured Interview – there is generally no fixed format to follow so,
interviewer can just ask questions. As the interview is unplanned, it is an
informal interview where a friendly conversation takes place between the
interviewer and interviewee.
8.UML (Unified Modelling Language)
UML is a modelling standard primarily used for specification, development, visualization and
documenting of software system. To capture important business process and artifacts UML
provides objects like

There are 14 UML diagrams that help with modelling like the use case diagram, interaction
diagram, class diagram, component diagram, sequence diagram, etc. UML models are
important in the IT segment as it becomes the medium of communication between all
stakeholders. A UML-based business model can be a direct input to a requirements tool. A
UML diagram can be of two type's Behavioural model and Structural model.
Most suitable methodology for the analysis of the system and how that can be used to
improve the effectiveness of the analysis stage
In my point of view, I think the Scrum Methodology is the best method to analyse our
scenario.
What is Scrum?
Scrum is an agile development methodology used in the development of Software based on
an iterative and incremental processes. Scrum is adaptable, fast, flexible and effective agile
framework that is designed to deliver value to the customer throughout the development of
the project. The primary objective of Scrum is to satisfy the customer’s need through an
environment of transparency in communication, collective responsibility and continuous
progress. The development starts from a general idea of what needs to be built, elaborating a
list of characteristics ordered by priority (product backlog) that the owner of the product wants
to obtain.

Figure 9 : Agile Methodology-Scrum Process
Scrum Methodology & Process

Scrum is precisely an evolution of Agile Management. Scrum methodology is based on a set
of very defined practices and roles that must be involved during the software development
process. It is a flexible methodology that rewards the application of the 12 agile principles in
a context agreed by all the team members of the product.
Scrum is executed in temporary blocks that are short and periodic, called Sprints, which
usually range from 2 to 4 weeks, which is the term for feedback and reflection. Each Sprint
is an entity in itself, that is, it provides a complete result, a variation of the final product that
must be able to be delivered to the client with the least possible effort when requested.
The process has as a starting point, a list of objectives/ requirements that make up the project
plan. It is the client of the project that prioritizes these objectives considering a balance of the
value and the cost thereof, that is how the iterations and consequent deliveries are determined.
On the one hand the market demands quality, fast delivery at lower costs, for which a
company must be very agile and flexible in the development of products, to achieve short
development cycles that can meet the demand of customers without undermining the quality
of the result. It is a very easy methodology to implement and very popular for the quick results
it gets.

Scrum methodology is used mainly for software development, but other sectors are also
taking advantage of its benefits by implementing this methodology in their organizational
models such as sales, marketing, & HR teams etc.
Advantages of Scrum
• Scrum can help teams complete project deliverables quickly and efficiently
• Scrum ensures effective use of time and money
• Large projects are divided into easily manageable sprints
• Developments are coded and tested during the sprint review
• Works well for fast-moving development projects
• The team gets clear visibility through scrum meetings
• Scrum, being agile, adopts feedback from customers and stakeholders
• Short sprints enable changes based on feedback a lot more easily
• The individual effort of each team member is visible during daily scrum meetings
Disadvantages of Scrum
• Scrum often leads to scope creep, due to the lack of a definite end-date
• The chances of project failure are high if individuals aren't very committed or
cooperative
• Adopting the Scrum framework in large teams is challenging
• The framework can be successful only with experienced team members
• Daily meetings sometimes frustrate team members
• If any team member leaves in the middle of a project, it can have a huge negative
impact on the project
• Quality is hard to implement until the team goes through an aggressive testing process

Activity 04
requirements. Your system design specification should include architectural design,
interface design, database design, and program design.
Interface Screenshot of Fully functional system to meet user and system requirements.
And Assess the effectiveness of the system design with reference to the methodology
used and how the design meets user and system requirements.
Figure 10 : Interface 1



Above given are the interface of Automated system which developed fulfil all system
requirement and user requirements of for E-Solutions Private The automation of existing
process is to reduce the company’s expenses and enhance the productivity significantly. This
transformation also would support for:
a) Successful teams working
b) Completing projects on time and within budget due to a better understanding of system
c) Starting projects on time through automated project scheduling system.
In the proposed system, the Project director creates a project and a “project profile” for each
project. The creation of the project profile includes identification of project employee costs,
the assignment of tasks to the project, and the assignment of a project manager. The project
profile is consisted of project id, project personnel cost, a list of tasks assigned, and the project
manager.
Minimum requirements:
✓ CPU serious - Intel Core i3-3210 3.2 GHz / AMD A8-7600 APU 3.1 GHz or
equivalent
✓ RAM- 2 GB o HDD – 20GB o BANDWIDTH - 1 TB/mo
✓ GPU (Integrated): Intel HD Graphics 4000 (Ivy Bridge) or AMD Radeon R5 series
(Kaveri line) with OpenGL 4.4*
✓ GPU (Discrete): NVidia GeForce 400 Series or AMD Radeon HD 7000 series with
OpenGL 4.4 Optional - Backups / 1 Mbps
Recommended Requirements:
✓ CPU: Intel Core i5-4690 3.5GHz / AMD A10-7800 APU 3.5 GHz or Intel Xeon 2x 8
✓ Cores x 2.1 GHz or 4 Cores x 3.5 GHz
✓ RAM 8 GB, 16 GB
✓ HDD – 1 TB SSD or more
✓ GPU: GeForce 700 Series or AMD Radeon Rx 200 Series (excluding integrated
chipsets) with OpenGL 4.5

System software Requirements:
✓ For Windows Servers Hosting - Windows server 2012 or Windows server 2016
operating systems.
✓ For Linux Servers - CentOS, Fedora, Ubuntu
Software Requirements:
✓ Adobe Dreamweaver CC 2015

✓ XAMPP for Windows 5.6.40
✓ XAMPP for Linux 5.6.40
✓ Microsoft SQL Server: Versions 2005 or higher
✓ Microsoft .NET Framework 4.5+ is required (installed for you) Java version(s): 7.0,
8.0 or higher

Diagrams related to the Automated system for E-Solutions Private Limited
Figure 15 : Login page flow chart
Figure 16 : Create page display flow chart

Figure 17 : Project manager flowchart
Figure 18 : Team leader flowchart

Figure 19 : ER Diagram of full system
Figure 20 : Level 1 dataflow diagram

Figure 21 : Level 2 dataflow diagram
How the system design can be used to improve the effectiveness of the selected
methodology relevant to the above scenario
The agile development approach is a direct response to the problems with traditional software
development, both in terms of overall philosophy and specific processes. In its most basic
form, agile development provides a lightweight framework for assisting teams in maintaining
a focus on the rapid delivery of business value in the face of a constantly changing functional
and technical landscape. The advantages of agile software development are that organizations
can significantly reduce the overall risk associated with software development because of this
focus. Agile development, in particular, accelerates the delivery of initial business value and
ensures that value is maximized throughout the development process through a process of
continuous planning and feedback. As a result of this iterative planning and feedback loop,
teams are able to continuously align the delivered software with desired business needs, easily
adapting to changing requirements throughout the process. By measuring and evaluating
status based on the undeniable truth of working, testing software, much more accurate
visibility into the actual progress of projects is available. Finally, as a result of following an
agile process, at the conclusion of a project is a software system that much better addresses
the business and customer needs.

Conduct a survey to collect feedbacks from users and explain the level of satisfaction
based on user and system requirements in the conclusion
Online Survey for Automated system for E-Solutions Private Limited
An online survey is a structured questionnaire that your target audience completes over the
internet generally through a filling out a form. Online surveys can vary in length and format.
The data is stored in a database and the survey tool generally provides some level of analysis
of the data in addition to review by a trained expert.
Benefits of Surveys
Unlike traditional surveys, online surveys offer companies a way to collect information from
a broad audience for very little cost. When conducting an online survey, you have an
opportunity to learn:
• Who your users are

• What your users want to accomplish
• What information your users are looking for
There are six distinct characteristics that should ideally define online surveys.
1. Purpose of the online survey: This is the most important characteristic of online surveys.
An established survey can only lead to appalling results. Researchers should decide the
objective of conducting an online survey so that the gauged results can be used to enhance
products/service, customer service or any other pre-decided objective.
2. Accurate research design: For an online survey to bear efficient results, it is important for
the researcher to design a thorough research design. How to carry out market research and
analysis using online surveys – this can be decided by implementing research design.
Research design will help market researchers in deciding how to collect information using
online surveys and how to measure and analyze collected data. The type of research design
can be decided according to the research problem an organization is facing. Upon detecting
the research problem, a market researcher can decide from among various types of research
design: Cross-sectional, longitudinal, experimental, correlational etc. In case, an
organization intends to conduct an online survey at a particular time, the researchers can rely

on cross-sectional research design and in situations where the organization wants to observe
a change in pattern from a particular time interval to another, the researchers can rely on
longitudinal research design.
3. Precisely structured survey questions: An efficient survey should include a carefully
curated balance of open-ended and closed-ended survey questions. There are various
question types which can suffice different purposes of online surveys. The questions added
in an online survey should be effective in obtaining the required information from the
selected sample. Some of the most widely used survey questions are Multiple-choice
questions, Dichotomous questions, Matrix questions, Likert Scale questions etc.A
researcher will be able to gather effective information from online surveys only when the
purpose of the survey is justified with the type of survey questions. For example, Likert scale
questions can be used to know the level of agreement of respondents with a particular
statement, or Matrix questions can be used where there is a long list of similar questions and
there is a likelihood of respondents dropping off a survey if these questions are not
combined. Researchers should understand the purpose of an online survey to ensure that the
survey questions are well-structured to garner crucial details.
4. Clearly defined target sample: A sample is a representative section of target respondents
who represent the required characteristics for research and whose inputs can be generalized
and applied to the entire target market.After filtering a sample from the target population,
the number of individuals who are a part of the sample will be indicative of the sample size.
A sample can be formed on the basis of various aspects such as demographics, profession or
any other factor according to the researcher’s experience and knowledge.Samples can be
formed using two sampling methods:
• Probability Sampling: A theory of probability is used to form a sample using
the Probability Sampling method. In this sampling method, every individual of
a target population has an equal opportunity to be a part of a selected sample.
• Non-probability Sampling: Non-probability sampling is a technique where
the sample is chosen on the basis of the researcher’s judgment, experience and
knowledge and not on random selection.
5. Collection and Analysis of respondent feedback: Including the right survey questions and
sending the online survey to the desired sample can lead to productive results only if the
collected results are well-analyzed to make informed decisions for the organization.
With online survey software such as Question-Pro, researchers can get analyzed data on a
dashboard which keeps updating real-time as respondents take the online survey. The data
presented on this dashboard is in the form charts and graphs for the ease of statistical analysis
for market research.
6. Transparent reporting of survey responses: The research reports created using data
obtained from online surveys should be shared with all the stakeholders of the organizations
so that each member is aware of the data gathered from surveys. Every respondent should
also understand that their inputs are being implemented by the organization – this way, they
will trust the organization in being honest about providing feedback for improvement.
User Feedback Form
Figure 22 : User Feedback Form 1




Analyzing user Feedback Form
Figure 26 : Analyzing user Feedback Form result 1



Table 2 : Analyzing user feedback form in Excel Sheet
After the above feedback form was given to the Project Director, Project Manager and Team
leader the feedback received from the all users are positive. system is 100% covers all user
requirements.

Conclusion
This document consists of the process of designing an Automated system for E-Solutions
Private Limited. This document contains four activities. In the first activity, system
development techniques, traditional and agile system development methodologies were
identified, and their strengths and weaknesses were identified. Then discussed the differences
between the methodologies and the problems face by an organization in transitioning from the
traditional approach to the agile approach. The second activity based on feasibility studies,
explains what the feasibility studies are and their importance. In this activity, a feasibility report
is submitted. It is based on the online auction system. Then the impact of feasibility studies is
finally explained. The third activity stats with the user and system requirements. It identified
tools that could be used to gather user and system requirements and discussed user stories that
create user needs. Then outlines the most suitable methodology for system analysis and its
advantages and disadvantages and how the chosen methodology helps improve effectiveness
during the analysis phase. The final activity is focusing on the how the system design can be
used to improve the effectiveness of the selected methodology.

References
➢ Atlanta, 2019. Innovativearchitects. [Online]
Available at: https://www.innovativearchitects.com/KnowledgeCenter/basic-IT-
systems/system-development-life-cycle.aspx
[Accessed 01 07 2021].
➢ Indusree, 2018. KPI. [Online]
Available at: https://www.kpipartners.com/blog/traditional-vs-agile-software-
development-methodologies
[Accessed 05 07 2021].
➢ KENTON, W., 2020. Investopedia. [Online]
Available at: https://www.investopedia.com/terms/f/feasibility-study.asp
[Accessed 12 07 2021].
Annexures

Figure 33 : Gann Chart

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
the systems investigation for the business related
problem.
LO1 & LO2

D1 Critically evaluate the strengths and weaknesses of the
traditional and agile methodologies and feasibility study.
LO3 Analyse their system using a suitable

Methodology
P3 Review a system using a suitable methodology for a

business-related problem.
M3 Analyse the effectiveness of the methodology used in
providing a solution for a given business context.
LO4 Design the system to meet user and system

Requirements

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

reference to the methodology used and how the design
meets user and system requirements.
LO3 & LO4

D2 Justify the choice of the analysis methodology used in
the context of the business problem.

Unit 34 - System Analysis

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Unit 34 - System Analysis

Uploaded by

Copyright:

Available Formats

Higher Nationals

Internal verification of assessment decisions – BTEC (RQF)

Programme title HND in Computing

INTERNAL VERIFIER CHECKLIST

Do the assessment criteria awarded match

Is the Pass/Merit/Distinction grade awarded

Assessor signature Date

Internal Verifier signature Date

Confirm action completed

Assessor signature Date

M.S.M HISHMATHDEEN SAD 1

Unit Title Unit 34: System Analysis & Design

Assignment Number 1 Assessor Mrs. Gagani

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.

Grade: Assessor Signature: Date:

Grade: Assessor Signature: Date:

Internal Verifier’s Comments:

Signature & Date:

M.S.M HISHMATHDEEN SAD 2

M.S.M HISHMATHDEEN SAD 3

Word Processing Rules

M.S.M HISHMATHDEEN SAD 4

1. I know that plagiarism is a punishable offence because it constitutes theft.

Hishmathdeen122@gmail.com Date: 28.07.2021

M.S.M HISHMATHDEEN SAD 5

Unit Number and Title Unit 4: Systems Analysis & Design

Academic Year 2021/22

Assignment Title Automated system for E-Solutions Private

IV Name & Date

Unit Learning Outcomes:

M.S.M HISHMATHDEEN SAD 6

Additional functionality includes:

M.S.M HISHMATHDEEN SAD 7

M.S.M HISHMATHDEEN SAD 8

M.S.M HISHMATHDEEN SAD 10

M.S.M HISHMATHDEEN SAD 11

Figure 1 : System development life cycle................................................................................. 17

Table 1 : Difference between Traditional and Agile Software Development .......................... 32

M.S.M HISHMATHDEEN SAD 12

M.S.M HISHMATHDEEN SAD 13

➢ SDLC – Software Development Life Cycle

M.S.M HISHMATHDEEN SAD 14

M.S.M HISHMATHDEEN SAD 15

A system is a grouping of elements or components that work together to achieve a common

System development life cycle

M.S.M HISHMATHDEEN SAD 16

Following are the seven phases of the SDLC

2. Systems Analysis and Requirements

M.S.M HISHMATHDEEN SAD 17

• CASE (Computer Aided Systems/Software Engineering)

5. Integration and Testing

M.S.M HISHMATHDEEN SAD 18

7. Operations and Maintenance

M.S.M HISHMATHDEEN SAD 19

Figure 2 : Traditional Software Development Methodology

Traditional software development methodologies are based on pre-organized phases/stages

M.S.M HISHMATHDEEN SAD 20

M.S.M HISHMATHDEEN SAD 21

Figure 3 : Waterfall model design

• Requirement Gathering and analysis − All possible requirements of the system to

M.S.M HISHMATHDEEN SAD 22