Systems Analysis and Design: A Comprehensive Systems Investigation

This report provides a comprehensive overview of Systems Analysis and Design principles, focusing on the System Development Life Cycle (SDLC), feasibility studies, and system investigations. It begins by evaluating various SDLC models, including Rapid Applications Design (RAD), Spiral, Iterative, Agile, Waterfall, V-Shape, and Prototyping, highlighting their advantages and disadvantages. The report then discusses the importance of feasibility studies, detailing the components of a feasibility report and assessing the impact of different feasibility criteria on a systems investigation. Furthermore, it outlines the steps involved in undertaking a systems investigation to meet a business need, utilizing appropriate systems analysis tools and techniques such as Entity Relationship Diagrams, Context Diagrams, and Data Flow Diagrams (DFDs). The document also emphasizes the creation of supporting documentation and evaluates how user and system requirements are addressed throughout the systems investigation process. The report references a case study of Adroit Ads, a London-based advertising agency, to contextualize the application of these principles.

Systems Analysis and Design
0

Table of Contents
Introduction................................................................................................................................3
LO1 Understand different systems life cycles...........................................................................4
1.1 Evaluate different systems lifecycle models....................................................................4
M1. Identify and apply strategies to find appropriate solutions...........................................11
1.2 Discuss the importance of following a procedural/staged lifecycle in a systems
investigation.........................................................................................................................12
System Analysis and Design for systems investigation:......................................................12
M2. Select/ design and apply appropriate methods/ techniques..........................................13
LO2 Understand the importance of a feasibility study............................................................14
2.1 Discuss the components of a feasibility report..............................................................14
2.2 Assess the impact of different feasibility criteria on a systems investigation................16
LO3 Be able to perform a systems investigation.....................................................................17
3.1 Undertake a systems investigation to meet a business need..........................................17
3.2 Use appropriate systems analysis tools and techniques to carry out a systems
investigation.........................................................................................................................19
M3. Present and communicate appropriate findings............................................................21
3.3 Create documentation to support a systems investigation.............................................22
3.4 Evaluate how user and systems requirements have been addressed..............................24
Conclusion................................................................................................................................26
References................................................................................................................................27
1

List of Figure
Figure 1: SDLC Lifecycle..........................................................................................................4
Figure 2: Rapid Applications Design Model............................................................................5
Figure 3: Spiral Model...............................................................................................................6
Figure 4: Iterative Model...........................................................................................................7
Figure 5: Agile Development Model.........................................................................................8
Figure 6: Waterfall model..........................................................................................................9
Figure 7: V- Shape Model........................................................................................................10
Figure 8: Prototyping Model....................................................................................................11
Figure 9: Entity Relationship Diagram....................................................................................19
Figure 10:Context Diagrams....................................................................................................20
Figure 11: Data Flow Diagrams (DFDs)..................................................................................20
Figure 12: use case Diagram....................................................................................................21
List of Table
Table 1: Table of Questionnaires for adroit Ads......................................................................15
Table 2: Table of user documentation......................................................................................23
Table 3: Technical review question.........................................................................................24
Table 4: Customer review question.........................................................................................25
2

Introduction
Adroit Ads is a London based advertising agency which is created commercials
advertisements such as video, poster, and short film. Adroit Ads want to award of the best
advert companies. In the Adroit Ads Company, the creative team handles all activities of the
company. Here, I will be developed system application for Adroit Ads.
The report is divided by into three sections. The first section will be explained SDLC life
cycle and various type of Model. The second section will be described FSR report and their
components. The third section will be included the user and system requirement with
documentation.
.
3

LO1 Understand different systems life cycles
1.1 Evaluate different systems lifecycle models
What is SDLC?
System Development Life Cycle is a procedure that developed a system with low price and
high quality in the shortest time. It is also included the process of development, maintain,
modify and upgrade the system or software. It develops only software, only hardware, and
combine a form of both which fulfill the client need (Alwan, 2015).
SDLC have planning, building, design, testing, defining and deployment stage. SDLC Model
type
 Waterfall Model
 Spiral Model
 Agile Model
Figure 1: SDLC Lifecycle
Rapid Applications Design (RAD) Model: RAD is combined form of iterative development
and prototyping model that is no need more planning. It writes software according to
4

planning phase which is a need for developing the product. It focuses on customer need
which is collected from workshops and group (Daassnet, 2015).
Advantages:
 RAD is decreased the development time and Iteration time due to powerful RAD
tools.
 RAD is getting reviews initial stage which is encouraged the developer.
 It rises reusability of system components.
 It also solves integration issues in the beginning stage.
 RAD can be measured the Progress.
Disadvantages:
 It only works for small development times.
 It is a modularized system which is built on RAD.
 RAD system is depended on modeling skills and user interaction.
 It needs experienced developers/designers.
 RAD Management complexity is high.
Figure 2: Rapid Applications Design Model
Spiral Model: Spiral Model is combined form of iterative development and water model.
Spiral model has four phases such as Identification, Design, Construct or Build, and
Evaluation & Risk Analysis (Boehm, 1988).
Advantages:
5

 The need of client is more accurately defined and Changing need is acceptable during
any phase.
 It is supported extensive prototypes.
 The user can be connected with the system until early phase.
 It is broke the system small part and risk is managed by risk management.
Disadvantages:
 In the spiral model, system Management is a complex process.
 System product is not defined early phase.
 It is an indefinite process.
 It is an expensive process for the small project.
Figure 3: Spiral Model
Iterative Model: Iterative Model is broke the project small parts and then developed in each
iterative process. After all part developed, the complete system is implemented and
developed. It is not attempted full specification of need in the starting phase. In the starting
phase of development, the model is implementing and specifying of software. It is a
repeating process where each repeating process created a new product at the end of the
iteration (Powell-Morse, 2016).
Advantages:
6

 It is easily measured Progress of project.
 It is offered the debugging and Testing process for each smaller iteration
 It has processed Parallel development cycle.
 In the project, less risk or easily manage the risk due to risk analysis.
 It supports changing requirements.
 It is needed less time for Initial Operating.
 It is suitable for large and critical projects.
Disadvantages:
 It cannot apply when user need change after the start model.
 Management of the project is required attention due to complexity.
 It is not suitable for smaller projects.
 It has design issues.
 It is needed a risk analysis for skilled resources.
Figure 4: Iterative Model
Agile Model: Agile is a collection of the incremental and iterative process model. Agile
model is work on a realistic approach. It is mainly aimed that software is fast delivery with
the customer satisfaction and process adaptability. Agile Model is broke the large system into
a small system which is built as incremental. Iterations of the small system are offered by
incremental built. It takes 1 to 3 weeks to complete each iteration (Smartsheet, n.d.).
Advantages:
 It is no need of planning or less.
7

 Agile process is appropriate for fixed or changing need.
 Agile process is needed min Resource and rule for system development.
 It is easy to manage because agile process offered flexibility to developers.
Disadvantages:
 It does not handle complex dependencies during system development.
 In the Agile process, Customer interaction is more which may be the wrong direction
to the team.
 It holds risk in the form maintainability, extensibility, and sustainability. Not suitable
for handling complex dependencies.
Figure 5: Agile Development Model
Waterfall Model: It is also called the linear-sequential life cycle model. It is used where
requirements and Product are well defined. Technology and Ample resources for waterfall
model are freely available. In the waterfall model, customer interaction is less because
customer interacts with the software after completed (Calikus, 2015).
Advantages:
 Waterfall model is working small project because its needs are well defined.
 It is work single stage at a time so waterfall phase is not overlapped
8

 Waterfall model is easy and simple Model because it is easily managed due to
rigidity.
Disadvantages:
 Water model is the worst model for the long, complex, and ongoing object-oriented
projects.
 The software is working after all stage completed.
 It is included large amount uncertainty and risk.
Figure 6: Waterfall model
V- Shape Model: It is also called Verification and Validation model. It is called V-Shape
mode because their execution processes are executed in sequential V-shape manner. In the V-
Shape, Each stage development cycle is directly depended on testing phase. V-shape stages
are not overlapped (Sami, 2012).
Advantage:
 At a time, it is work single stage so it easily manages the project.
 V- Shape model is working smaller projects because the need for project is well-
defined.
 V- Shape Model is highly-disciplined, simple and essay learning model.
Disadvantage:
 V- Shape Model contains uncertainty and risk in the project.
9

 V- Shape Model is a poor model for the long, complex, and ongoing object-oriented
projects.
 After the testing stage, V- shape Model cannot go back or change in the functionality.
Figure 7: V- Shape Model
Prototyping: In the prototyping Model, the model is a plan with a prototype in the early
stage then design, test, and developed. Also, Analyses are collecting the user feedback earlier
stage (Thakur, 2015).
Advantage:
 It is recognized errors in the early phase.
 It is a fast process because the prototype is developed a system in the week.
Disadvantage:
 There is performance, security, system recovery & backup issue which can be
overlooked in the model.
 Documentation of system is not available or incomplete.
10

Figure 8: Prototyping Model
M1. Identify and apply strategies to find appropriate solutions.
M1 is needed to explain the various type of system development life cycle so it is
successfully achieved by me in 1.1 sections.
11

1.2 Discuss the importance of following a procedural/staged lifecycle in a systems
investigation
System Analysis and Design for systems investigation:
System Analysis: In System, the Analysis process is examining and analyzing the existing
or new systems and then recognizes the client need.
System Design: It is part of SDLC life cycle. In this process, a new system design according
to client need. After exploration and analysis of the system, the system is designed.
Here, I have explained seven stage for developed application for Adroit Ads. Using this
stage, I will be able to design application given time and cost.
Initiation Stage: It is the first stage which is examining the existing system and finding the
Problems. In this stage, also study costing, software or hardware requirements, staffing, and
timescales issue. The analysis process is a time-consuming process so it takes hours and
days’ time to identify the error in the pre-installed system. In the Initiation Stage, gather all
information related system elements and software.
Analysis of the requirement: In this stage, System analyst recognizes the software function
and their working for the new system. Also, the analyst makes a report on requirements of
system and clients and system performance which they are going to be developed.
System design: In this stage, System analyst design number of the design according to client
need. Firstly, Analyst makes the rough image on the computer or the paper then check it
fulfills all requirements or not. Mainly focus; analyst will choose the best design for the
system
System coding: It is a time-consuming process of SDLC life cycle. The analyst is converted
system design into the coding. Coding or program is only readable for the machine. In stage,
a number of chance to error occurs.
System testing: After the completion of system coding stage, System analyst tests the system.
He has checked the system that system is working according to expectations or not.
System implementation: In this stage, the analyst is forward the system to client and hope for
a positive feedback.
12

System maintenance: It is the last stage of SDLC life cycle. Analyst requirements to maintain
the system and check system is working with their standards set (Freddy, 2009).
M2. Select/ design and apply appropriate methods/ techniques
I have chosen the waterfall model for Adroit Ads application because
 It is fulfilled all requirement of the company and also built an error-free system.
 This method is useful in application implementation process (Adroit Ads). of the
application
 Waterfall model is helped to the delivery project at the time.
13

LO2 Understand the importance of a feasibility study
2.1 Discuss the components of a feasibility report
FSR is a formal document of the feasibility study. It includes the analysis result summarizes.
FSR is estimations the proposed solution and alternatives solution to investigate project and
find out the system is cost-effective, profitable and feasible In the FSR report, supports and
describes a most feasible solution for the project. FSR Report is a document which is
recognized the goal, search, and estimate the project solutions for save time and money
(Lewinson, 2010).
A system is contained four type of feasibility which must be passed by the system.
1. Technological Feasibility
2. Operational Feasibility
3. Schedule Feasibility
4. Economic Feasibility
Feasibility Components: As System Analyst in the Adroit Ads, I have discussed the feasibility
components which are found a feasible solution for the project.
 Purpose: The aim of new well-organized system application is designed for Adroit
Ads Advertisement agency because it will be growth in the market and performs their
operation well. It is not possible with the current system. There is an interconnection
between Creative Team and their other department (such as account team, HR Team,
IT Team, Media Team). There is only Creative Team which handles all load of the
company so Adroit Ads is needed a new well-organized system application.
 Structure: Structure of Adroit Ads application is depended on recommended by the
client which is a help to design application. Then I will found need of an application
that is clear for the introduction. After that, I will define the design criteria. Then the
application is developed according to the recommendation and design criteria. At end
test the application, it is met client requirements or not.
 Intended audience: Intended audience of new system application (Adroit Ads
Advertisement agency) is staff (account team, creative team, HR Team, IT Team,
Media Team), Adroit Ads Company and their customer. For this, I have designed a
system application because in the current system is an only creative team. The
intended audience of the current system is the intended audience distributed by
creative Team of Adroit Ads Advertisement agency.
14

 Outcomes: New system application is well planned and designed which is reduced the
load of the creative team. It is a solid application that is supported the processes of Adroit
Ads company creative team. It will also manage their customer and logical approach
(Anon, 2015).
Fact-finding techniques: Here, I have discussed Fact-finding techniques of Adroit Ads
Company such as Interviews, Observation, and Questionnaires. Fact-finding is a formal
process that is collecting the information through questionnaires, research, interviews,
meetings, sampling, and other techniques. Information may be related the system issue, need,
and preferences.
 Interviews: Interviews is a technique of fact-finding. Conduct timing of interview
takes more time because it is depended on other person od organize. Interview with
Adroit Ads Company CEO is difficult so there is need for questions asked are in the
right order. It helps to find out company aim and working process.
 Observation: Observation is a technique of fact-finding that is Observe the person or
organize activities and learn about them. In Adroit Ads, CEO is Observe all organize
that is help control and manage the company.
 Questionnaires: Questionnaire is a method of fact-finding. The Adroit Ads company is
used Questionnaires for gathering the information from the client. Questionnaires are
helped to find the goal of project and need of the client. Here, I have developed the
questionnaires for adroit Ads (Slideshare, 2015).
Table 1: Table of Questionnaires for adroit Ads
S.no Questions
1 Which type of system application is needed by Adroit?
2 What type of security do Adroit Ads want in the application?
3 Which of the functions did Adroit Ads require the application?
4 What is the budget of Adroit Ads for the application?
5 Do Adroit Ads want a distributed application?
15

2.2 Assess the impact of different feasibility criteria on a systems investigation
Legal: Legal feasibility of Adroit Ads company is covered all legal requirements. Adroit Ads
is covered customers rights law, data protection, and revenue laws. All legal information
provides the customer and staff.
Social: Social criterion is told about the service and least trend of the market. Adroit Ads
Company is offered Advertisement service for the customer. They focused to fulfill the
customer need because customer rejected the service if it is not meet their requirements.
Economic: Economic feasibility is played a major role early stage of the project. Feasibility
criteria for Economic, Analyst is determining the changing of the current system which is
useful and cost saving for the Adroit Ads Company. Analyst designed and developed the
Adroit Ads system application which is also fulfilled all market standard.
Technical: Adroit Ads is focused on a technical resource which is needed to fulfill their
requirements. In the check, the Adroit Ads system needs for any updating or modification. It
is covered all technical issue like online payment system, a database of company, hardware,
and software of the system.
Timescales: Timescales is a basic feasibility criterion in the Adroit Ads company because it
is measured the timing (apply the change in the current system, how much time need the
system application to come in the market, how much time need to complete the client
project).
16

LO3 Be able to perform a systems investigation
3.1 Undertake a systems investigation to meet a business need
System investigation is a process that is found requirements of the system. It is helped built
the system. Here, I have explained a System investigation steps for the Adroit Ads.
Assurance of quality: It is a systematic approach that is helped to improve the reliability of
the organization. Quality assurance is a process that is checked application met the client
requirements or not. For Adroit Ads, Quality assurance is defined for the application because
it is helped to found error and faults in the current application of Adroit Ads. It also
improves the user experience of Adroit Ads (Rouse, 2012).
Name of stakeholders: Stakeholder is a single person or group of person that is effect by
organize actives. A stakeholder is directly or indirectly manner affected by the company. HR
and payroll team, Creative team, IT team, Account Team and other team are Stakeholder in
Adroit Ads. Adroit Ads have also included CEO, User, and client as Stakeholder (Landau,
2017).
Measurement of requirements: It is a type of document that is measured the application
preformation. I have explained requirement specifications for Adroit Ads which are given
below:
 Goal: It is explained application scope that is developed for Adroit Ads. The goal is
helped to manage the activities of the creative team.
 Substitute solutions: It is used as backup plan during the application development.
Substitute solutions have reduced the risk and utilize the time and effort of Adroit Ads.
 Input and output: For the development of the application, various type of programing
language and resource are used as Inputs. As output, Adroit Ads want a system
application which supports creative team and through this application, they will be able to
get an award of the best advert company.
 Limitations: Each project has some limitation in the development phase. For of an
application for Adroit Ads is also some limitations like as
1. Application security is less so easily attack by a hacker.
2. Cost for application development is less.
3. Availability of resources in the application is less.
17

Documentation of Requirement: Company Requirements are defined objectives and goals
for the project. Adroit Ads Company Requirement has developed an application which
improves the function of the creative team. Requirements are defined in two terms like as
non-functional requirements and functional requirements. Here, I have defined the non-
functional requirements and functional requirements of Adroit Ads.
 Functional Requirements:
1. It is help identifying working and functionality of the application. For the
Adroit Ads, the application manages the all staff & client information and
defined each team (account, creative, HR, IT) function.
2. Functional requirements have defined the behavior of the application in the
limitations, conditions or rule. For the Adroit Ads, account department has
managed the account and communicated the client and creative department is
create video, the short film according to client need.
3. Functional requirements of application is connected with security and
interface of application Non-functional requirements
1. Non-functional requirements Of Adroit Ads application is defined on
accessibility, efficiency, loading time, and quality.
2. Non-functional requirements Of Adroit Ads application is told how the
application completed its task in given condition. For example, payment
process
3. Non-functional requirements Of Adroit Ads application has defined the
behavior of an application during the development phase (Adroit Ads)
(Eriksson, n.d.). For example, what issues are raised during the development
of application?
18

3.2 Use appropriate systems analysis tools and techniques to carry out a systems
investigation
Performing the performing system investigation for Adroit Ads, I have used lots of tools and
techniques like as DFD, ERD, context diagram and use case diagram. All these tools and
techniques are used during the development phase of the application. Here, I have explained
these tool and techniques.
ER Diagram: ERD is a data model that is describing relations between entities. Logical
ERD and physical ERD are two type of ERD. It is also known as ERD, Entity Relationship
Diagram or ER model Here, I have designed ER Diagram for Adroit Ads Company
(Brandenburg, n.d.).
Figure 9: Entity Relationship Diagram
Context Diagrams: It is a graphic design which is defined the boundaries and interface of
project or application. It is also showed the interactions of application with other. Here, I
have designed Context Diagrams for Adroit Ads Company (Modernanalyst, n.d.).
19

Figure 10:Context Diagrams
Data Flow Diagrams (DFDs): DFD is a graphically representation of system requirements.
It is showing information flow in the system. It is a automated, manual and combination of
both. Here, I have designed Data Flow Diagrams for Adroit Ads Company (Visual-paradigm,
2012).
Figure 11: Data Flow Diagrams (DFDs)
20

Use Case Diagrams: It is a graphic illustration that is defined the interaction between system
elements. Here, I have designed Use Case Diagrams for Adroit Ads Company
(Sourcemaking, n.d.).
Figure 12: use case Diagram
M3. Present and communicate appropriate findings.
M3 is needed to explain context diagram, data flow diagram (DFD), use case diagram, and
ERD (entity relation diagram) so it is successfully achieved by me in 3.2 sections.
21

3.3 Create documentation to support a systems investigation
Documentation is an outline that is need to complete the project or task. Internal
Documentation and ongoing documentation are types of documentation which is tell how the
system is developed and what system effect in organizing is. Documentation is made a
connection between non-technical and technical background. It guides the staff, manager, and
customer.
Documentation of Adroit Ads is also tracking the development of the application. The
tracking process helps the new staff in the learning and training process. Documentation steps
are explained below:
1. Gathering information: Adroit Ads is London based advertising agency which offered
to advertise with the help of video, articles, and poster. Adroit Ads is held a creative team
for creating the advertising. As a system analyst, I have collected Adroit Ads background
information from company history and CEO.
2. Data assembly process: Data is playing major role in any organization. Data is collected
from a various type of sources such as surveys, questionnaires, interview, and research.
As a system analyst, I have assembled Adroit Ads Company data through CEO interview,
questionnaires (staff member) and observation. This data is help to a developed
application.
3. Problem Statement: Each project, Problem statement is defined in a single statement.
Problem statement has defined the problem in the current system. These problems are
resolved in the new system. Problem Statement of Adroit Ads company
“Designed and implement a system application that helps the creative team”
4. Suggestion Or Recommendations: Recommendation is an important part of the
documentation process. According to user feedback and reviews suggested
recommendations. Recommendations have improved the application or system.
Recommendations may be positive and negative. For the Adroit Ads Company, first
Recommendations is related to security. System security is improved using encryption
technique. Second, Application response time should be reduced.
For the system investigation, user documentation is explained below:
22

Table 2: Table of user documentation
Characteristics Explanation
Client Here, I have designed the application for Adroit Ads company.
Organize contain a creative team and their staff. creative directors,
actors, ad directors, models, and art directors.
Requirements
for Client
The client wants an application that helps to manage organize and
reduced the load of the creative team. They also want communication
and interaction between staff member through the application
Limitations
During
Application
development
 Application budget
 Resources availability
23

3.4 Evaluate how user and systems requirements have been addressed.
User requirements: It tells about the user need. User requirements also tell about how the
user interacts with the application. It also includes that user needs a response application
which is easily response the user without any delay. Adroit Ads Company want a system
application which is support and manages the creative team. The application should be user-
friendly and more responsive. In the application, they want Accounts department, HR
department, and so-on departments that is fulfilled the payments, media availability, and
actor recruitment.
System requirements: It is included system requirements that are needed for the application
development time. It tells about how is application is work. Wrikle (need for the work
management), AccountAbility (for the manage account), IDLE (for developing the
application), and todo.iv (for the time-tracking) are system requirements to developed Adroit
Ads Company application. ,
Verification and validation of requirements:
Adroit Ads is followed Verification and validation process for the system. The validation
process is checked that system is developed correct or not (according to user requirement).
The verification process is checked that system has fulfilled all need of client or not. There
are following step for the checked Verification and validation of requirements of the system.
1. Technical review: In this section, Adroit Ads creative team is taking review of the
application. It is based on user experience after the use of the application. Here, I have
explained questionnaire for the Technical review that is showed below:
Table 3: Technical review question
24
Technical review question User A User B User C User D
How is creative teamwork
in the application?
Good Avg Good Excellent
Application Interaction
with Staff
Good Excellent Avg Good
Application
Communication with the
user
Avg Good Excellent Avg

2. Manage Review: Adroit Ads company review is managed by IT Team. Adroit Ads
IT Team is collecting the reviews and feedbacks form a different type of people.
These reviews and feedbacks may be positive and negative which is help the system
improvement. Here, I have told about some recommendations according to user
review.
 Update the application time to time so the user can be got update application.
 Application security level should be increased using encryption data. Because
current system security is poor so the hacker easily attacks.
 Make the system can be made more responsive user can easily assess the
system.
3. Customer review: In this section, the system is reviewed by Customer with a
different type of questionnaires. Here, I have explained questionnaire for the
Customer review that is showed below:
Table 4: Customer review question
Customer review question Customer 1 Customer 2 Customer 3 Customer 4
Security of Access Excellent Avg. Avg. Good
Response and loading time
of application
Avg. Good Poor Good
GUI of Application Good Excellent Good Excellent
25

Conclusion
Here, I have successfully designed a report on System Analysis and Design for Adroit Ads. I
have described the SDLC Lifecycle which is used for developed of application. Adroit Ads
application is designed and developed using waterfall model because it is Adroit Ads budget
and developed given time.
The learner will be able to learn about FSR report & their components, and fact-finding
technique. In the report, I have explained tool and technique (like as DFD, ERD, Use case,
and context diagram) that is used for development of the application. Future, I have also
included application documentation, user requirements and system requirements in the report.
26

References
 Alwan, M., 2015. What is System Development Life Cycle?. [online] Airbrake Blog.
Available at: https://airbrake.io/blog/sdlc/what-is-system-development-life-cycle
[Accessed 26 Jan. 2018].
 Anon, 2015. [online] Available at: https://www.linkedin.com/pulse/key-components-good-
feasibility-study-mwanzoni-ltd/ [Accessed 26 Jan. 2018].
 Boehm, 1988. Boehm’s spiral model of the software process. [online] Software
Engineering 10th Edition. Available at: http://iansommerville.com/software-engineering-
book/web/spiral-model/ [Accessed 26 Jan. 2018].
 Brandenburg, L., n.d. How to Create an Entity Relationship Diagram (ERD). [online]
Bridging-the-gap. Available at: http://www.bridging-the-gap.com/erd-entity-relationship-
diagram/ [Accessed 26 Jan. 2018].
 Calikus, E. ,2015. [online] Available at: https://www.researchgate.net/figure/Figure-6-
Waterfall-Model_283048282_fig5 [Accessed 26 Jan. 2018].
 Daassnet., 2015. Design and Development. [online] Available at:
http://www.daassnet.com/new/index.php/en/professionalservices/d-d.html [Accessed 26
Jan. 2018].
 Eriksson, U., n.d.. Functional Requirements vs Non Functional Requirements. [online]
ReQtest. Available at: https://reqtest.com/requirements-blog/functional-vs-non-
functional-requirements/ [Accessed 26 Jan. 2018].
 Freddy, 2009. Which life cycle are more crucial, systems investigation, systems. [online]
JustAnswer. Available at: https://www.justanswer.com/computer/20cgg-life-cycle-
crucial-systems-investigation-systems.html [Accessed 26 Jan. 2018].
 Landau, P., 2017. What is a Stakeholder? - Definition of Stakeholder -
ProjectManager.com. [online] ProjectManager.com. Available at:
https://www.projectmanager.com/blog/what-is-a-stakeholder [Accessed 26 Jan. 2018].
 Lewinson, M. , 2010. How to Write a Feasibility Study Report (FSR). [online]
Mymanagementguide. Available at: http://www.mymanagementguide.com/feasibility-
study-reporting-steps-to-writing-a-feasibility-study-report-fsr/ [Accessed 26 Jan. 2018].
 Modernanalyst, n.d.. Introduction to Context Diagrams > Business Analyst Community &
Resources | Modern Analyst. [online] Available at:
http://www.modernanalyst.com/Resources/Articles/tabid/115/ID/1355/Introduction-to-
Context-Diagrams.aspx [Accessed 26 Jan. 2018].
27

 Powell-Morse, A., 2016. Iterative Model: What Is It And When Should You Use It?.
[online] Airbrake Blog. Available at: https://airbrake.io/blog/sdlc/iterative-model
[Accessed 26 Jan. 2018].
 Rouse, M., 2012. What is quality assurance (QA)? - Definition from WhatIs.com. [online]
SearchSoftwareQuality. Available at:
http://searchsoftwarequality.techtarget.com/definition/quality-assurance [Accessed 26
Jan. 2018].
 Sami, M., 2012. Software Development Life Cycle Models and Methodologies. [online]
Mohamed Sami. Available at: https://melsatar.blog/2012/03/15/software-development-
life-cycle-models-and-methodologies/ [Accessed 26 Jan. 2018].
 Slideshare, 2015. Fact finding techniques. [online] Available at:
https://www.slideshare.net/imthiyasbtm/fact-finding-techniques-53785925 [Accessed 26
Jan. 2018].
 Smartsheet., n.d.. What's the Difference? Agile vs Scrum vs Waterfall vs Kanban.
[online] Available at: https://www.smartsheet.com/agile-vs-scrum-vs-waterfall-vs-kanban
[Accessed 26 Jan. 2018].
 Sourcemaking., n.d.. Design Patterns and Refactoring. [online] Available at:
https://sourcemaking.com/uml/modeling-business-systems/external-view/constructing-
use-case-diagrams [Accessed 26 Jan. 2018].
 Thakur, D. , 2015. Prototyping Information Systems Analysis Presentation. [online]
Slideplayer. Available at: http://slideplayer.com/slide/4913149/ [Accessed 26 Jan. 2018].
 Visual-paradigm, 2012. What is Data Flow Diagram (DFD)? How to Draw DFD?.
[online] Available at: https://www.visual-paradigm.com/tutorials/data-flow-diagram-
dfd.jsp [Accessed 26 Jan. 2018].
28