Based on the Project Plan details, develop the following documentation for your project. All information in the documentation should align to these details in your Project Plan over Internet Banking Project:
1. System diagram – a visual representation—a graphic or chart—of the components of your project
2. Network diagram – a visual representation of how data flows in your network
3. Database Design document to represent all data that is stored and maintained in the context of your project and includes these specific items:
a. An entity-relationship diagram
b. A data dictionary
c. Table definitions
4. Cybersecurity plan – a clearly articulated plan that explains how the project data and processes will be secured
5. Simple source code (may be partial source code) code in HTML/JavaScript, Java, C++, or another programming language for at least one software application
6. Quality assurance and software test plan
a. Review the Sample Software Test Plan for an example of what information is typically included and how it is typically organized in a software test plan
Note: All 6 assignment deliverables must be portfolio ready, which means each piece should be as complete and error-free as possible.
BSA/425v2
Project Plan Second Draft
Fill out each of the sections below with information relevant to your project. Be sure to include the
company name associated with your project.
Company Name:
EBanking Inc.
Network Technology Recommendations
Network Technology Selection Criteria
Selection
Criteria Name
(short name
to ID the
criteria)
Selection Criteria Description
Selection Criteria Value
(Weighting in Points)
(Define the criteria for technology to
associate with a point value.)
(e.g., 3 – Excellent, 2 – Good, 1 –
Acceptable)
Security
Can the technology guarantee the safety of
the data transmitted through it? The
technology must integrate industry-accepted
best practices and a multi-level
authentication system to validate all users
requesting access before they are allowed to
access the system and initiate transactions.
3
Interoperability
The criteria determine how well the
technology communicates with the
organization’s other technologies. The
technology should have a comprehensively
documented set of APIs and tools that
enable it to work effectively with other
technologies.
3
Network Technology Recommendation
Recommended
Network
Technologies
Description
Benefits
Aggregate
Selection
Criteria Score
(Score for this
technology
based on the
selection
criteria detailed
above.)
Copyright 2022 by University of Phoenix. All rights reserved.
Project Plan Draft
BSA/425 v2
Page 2 of 12
Router
It is a networking device that
receives and transmits data
between connected devices on
the network
It is responsible for receiving,
analyzing, and forwarding data
packets among the connected
devices.
When a data packet is received,
the router assesses the
destination address, checks the
routing table, and decides the
optimal route through which the
traffic should be transmitted.
10
Firewall
It is a device that monitors the
inbound and outbound traffic
and makes a decision whether
to permit or block the traffic
based on predefined rules
(Javid, Riaz & Rasheed,
2014)
It protects the internet banking
traffic by blocking the application
layer and malware attacks.
A firewall can perform a quick
inspection to detect suspicious or
invasive activity on the network
and shut it down promptly.
10
Network Technology Vendor Selection Criteria
(Third-party technology provider)
Selection
Criteria
Name
Selection Criteria Description
Selection Criteria Value (Weighting in
Points)
Bandwidth
requirements
It is essential to work with a vendor that
evaluates the current needs of the
organization and projects the amount of
capacity that will be needed upon
deployment of the Internet banking
service
3
Cost
The ultimate objective should be to get
the most value for the lowest probable
cost. The costs must be favorable to both
the company and the vendor
3
Network Technology Recommended Vendors
Vendor
Name
Cisco
Vendor Strengths
•
Established
technology
leader
Vendor
Weaknesses
Products/Services Provided to
Project
Aggregate
Selection
Criteria
Score
•
Networking hardware such as
routers, hubs, gateways, hubs,
etc
10
Delays in
the supply
chain
Copyright 2022 by University of Phoenix. All rights reserved.
Project Plan Draft
BSA/425 v2
Page 3 of 12
Juniper
Networks
•
Strong
research
and
development
•
Reducing
storage
networking
market
Security appliances such as
Next-Generation Firewalls
(NGF)
•
Economies
of scale and
lower costs
•
Strong
portfolio of
products on
networking
•
Weak
product
demand
forecasting
•
Strong R&D
•
•
A good
relationship
with
customers
Short
technology
life cycle
Networking hardware such as
routers, hubs, gateways, hubs,
etc
Security appliances such as
Next-Generation Firewalls
(NGF)
•
Limited
brand
awareness
10
Network Technology Deployment Challenges
Deployment
Challenge
(short name to
ID the
challenge)
Deployment Challenge Description
(What obstacles can potentially complicate or delay the deployment of technology,
and affect the project timeline?)
Centralizing
traffic
There are several sites and subnets for the Internet Banking project. Network
management, monitoring, and visibility may become almost impossible without a
centralized hub. Centralizing all the network traffic can prove to be a severe challenge.
Vendor lock-in
This is a challenge that the project may grapple with considerably. Getting the best out of
the vendors implies figuring out how to integrate, interoperate and support numerous
solutions or figuring out how to retire the legacy systems without impacting the whole
network.
Technology Adoption Methods
Method Name
Method Description
(short name to
ID the method)
(Summarize the process for adopting the technology.)
Phased
Parts of the new network technology will be implemented one at a time to enable users to
get used to the particular procs and identify any arising problems before other areas are
implemented.
Copyright 2022 by University of Phoenix. All rights reserved.
Project Plan Draft
BSA/425 v2
Page 4 of 12
The new networking technology is deployed to run in parallel with the old technology. It
enables project managers to examine and compare the reliability and efficiency of the
new system.
Parallel
Cost/Benefit Considerations
Benefits
Costs
Considerations
Efficiency, security
Direct costs
such cost of
labor and
equipment
The ultimate benefits in terms of security and
efficiency outweigh the direct costs.
Savings
Indirect costs
such as the cost
of power
Savings will be more than the indirect costs of the
project.
Database System Recommendation
Database System Selection Criteria
Selection
Criteria
Name
Selection Criteria Description
Selection Criteria Value (Weighting in Points)
Scalability
The database system must have the
capacity to scale with the data and the
business in general
3
Integration
The chosen system must be able to
integrate with other banking
applications the organization is using.
3
Security
The database system must adhere to
the latest security protection protocols
and regulation standards. (Security is
an essential aspect of any database
system. It protects the company and
clients from unintentional and
intentional loss of data. This in return
protects the stakeholders too)
3
Database System Recommendation
Recommend
ed Database
System
Description
Benefits
Copyright 2022 by University of Phoenix. All rights reserved.
Aggregate
Selection
Criteria Score
Project Plan Draft
BSA/425 v2
Page 5 of 12
Relational
Database
Management
system
(RDMS)
It is a form of database that stores
and facilitates access to related
data.
RDBMS improves the accuracy of
data. Tables are related to one
another through primary and
foreign keys hence eliminating
the chance of data duplication.
RDBMS also improves data
integrity.
10
Analytics
solution
It is a solution used to perform an
analysis of the data stored in the
database
It is used to draw insights from
the stored data to help the
organization make better
business decisions
10
Database System Vendor Selection Criteria
Selection
Criteria
Name
Selection Criteria Description
Selection Criteria Value
(Weighting in Points)
Performance
The vendor must focus on the scalability and
performance of the database engine.
3
Cost
The project must be delivered within some cost
constraints. The organization should be able to
get adequate value for the lowest probable cost
3
Support
The vendor must provide 24/7 support with fast
response contact. (Support is an important
selection criterion when searching for a vendor.
Companies need to be able to contact the
vendor when the database is down or having
issues to reduce overall downtime)
3
Database System Recommended Vendors
Vendor
Name
Vendor Strengths
Oracle
•
Fast data
processing
•
Multi-platform
•
Better clustering
of services
•
Reliable
availability
Microsoft
Vendor Weaknesses
•
Higher prices
compared to
competitors
•
Not suitable
for small
applications
•
It is a complex
platform
Products/Services
Provided to Project
Aggregate
Selection
Criteria
Score
Relational database
system
10
Analytics and data
warehousing
services
10
Copyright 2022 by University of Phoenix. All rights reserved.
Project Plan Draft
BSA/425 v2
Page 6 of 12
•
Sophisticated,
automated
management
•
Advanced
security
•
Easy integration
with other apps
•
Slow support
process
•
Complicated
pricing model
Database System Deployment Challenges
Deployment
Challenge
Deployment Challenge Description
Hardware
availability
The organization may not have sufficient hardware capacity to accommodate the new
advanced database system.
Optimization for
administration
The database administrators may grapple with how to make the database as easy as
possible to administer, more so if there is significant accidental complexity.
Technology Adoption Methods
Method Name
Method Description
Parallel
adoption
The new database system will be configured to run parallel to the old one. A switchover to
the new system will happen once the project managers are convinced of the performance
of the new system.
Canary
adoption
The database system will be made available and tested by a subset of users before
making it available to everybody in the organization.
Cost/Benefit Considerations
Benefits
Costs
Considerations
Increased data integrity, security,
and availability
Costs of
purchasing
and
implementing
the RDBMS
Proceed with the project if the resulting benefits are
more than the related costs
Improved decision-making
Costs of
purchasing
and
implementing
the analytics
and data
warehouse
platform
Proceed if the benefits outweigh associated costs
Copyright 2022 by University of Phoenix. All rights reserved.
Project Plan Draft
BSA/425 v2
Page 7 of 12
Software Application Recommendations
Software Application Selection Criteria
Selection Criteria
Name
Selection Criteria Description
Selection Criteria
Value
(Weighting in
Points)
Features/functions
This criterion involves examining how well the software
meets the user requirements
3
Operating costs
Consider the maintenance level required to maintain
and operate the system constantly.
Costs of updating or adding data that the software
uses.
3
Software Application Recommendation
Recommended
Software
Application
Description
Aggregate
Selection
Criteria
Score
Benefits
Temenos
It is a market-leading
application and service
solution used by many banks
and other financial institutions
It provides essential financial
services to individuals. The
organization must integrate its
core banking system into
Temenos’ high-value internet
banking solution.
9
eBanking
This solution is owned by
FPS GOLD and supports
online banking
It gives customers what is
expected and easy to use and
secure online banking with a
significant degree of flexibility,
great design, and performance.
8
Software Application Vendor Selection Criteria
Selection Criteria
Name
Interoperability
Selection Criteria Description
The internet banking solution from the vendor must be able to
interoperate with other applications currently being used by
the organization.
Copyright 2022 by University of Phoenix. All rights reserved.
Selection
Criteria Value
(Weighting in
Points)
3
Project Plan Draft
BSA/425 v2
Page 8 of 12
Assess the background and history of the software vendor.
Check if the vendor’s customer service team can handle the
concerns and questions.
Credentials
3
Software Application Recommended Vendors
Vendor
Name
Vendor Strengths
Temenos
FPS Gold
•
Real-time
customer
data
•
Embedded
product
builder
•
Infinite
scalability
•
•
Vendor Weaknesses
•
Costly for a small
organization
•
Transactions take
time to post on a
slow network
Streamlined
p2p2
payments
•
Adding new
functionality is
challenging
Real-time
fraud
detection
•
It May have
incompatibility
issues with other
legacy
applications
Products/Services
Provided to Project
Aggregate
Selection
Criteria
Score
Internet Banking
Solution /Core
Banking
10
Internet Banking
Solution/Core
Banking
9
Software Application Deployment Challenges
Deployment
Challenge
Deployment Challenge Description
Hidden costs
Even though the new system’s goal should be to reduce operational costs and simplify
the system, the organization should be aware of the additional costs. Besides the cost of
software acquisition, it is also essential to consider the cost of software development,
updating, and maintenance.
Lack of support
past the
implementation
phase
During the vendor selection process, it is imperative to consider how the vendor will
support the application after the deployment stage has ended.
Compatibility
New software must be able to be integrated with existing systems and remain stable
throughout the deployment. (Compatibility can become a major issue to delay deployment
and must be addressed early on and revisited throughout the project)
Copyright 2022 by University of Phoenix. All rights reserved.
Project Plan Draft
BSA/425 v2
Page 9 of 12
Technology Adoption Methods
Method Name
Method Description
Canary
adoption
The adoption method involves implementing the software for a small subset of users
before it is rolled to the whole organization.
Parallel
adoption
Under this adoption mechanism, the new software will be implemented and run parallel to
the old one. Tests will be done for some time, and the old system will be switched off
once the project team is convinced about the performance of the new software.
Cost/Benefit Considerations
Benefits
Costs
Considerations
Increased efficiency
Cost of
software and
implementati
on
Consider if the costs outweigh the associated
benefits.
Improved security and fraud
detection
Cost of
security
implementati
on
Improved security and fraud detection will help the
company to make significant cost savings
associated with the theft of customer funds and the
resultant reputational damage.
Cloud Services Recommendations
Cloud Services Selection Criteria
Selection
Criteria
Name
Selection Criteria Description
Selection Criteria Value (Weighting in Points)
Uptime
This criterion offers information
regarding the assured complete
operational readiness of the services.
The uptime may differ significantly
based on the business model of the
respective organization
3
Security
The security of cloud services is critical.
The customer data may be used
negatively if it falls into the wrong hands
3
Copyright 2022 by University of Phoenix. All rights reserved.
Project Plan Draft
BSA/425 v2
Page 10 of 12
Cloud Services Recommendation
Recommended
Software
Application
Description
Benefits
Aggregate
Selection
Criteria
Score
SaaS
Allows customers to access
applications over the
internet(Kim,2009)
The multi-tenancy architecture of
SaaS enables it to lower the
organization’s computing costs. It
also provides internal integrations
that are more callable than the
traditional offerings.
10
IaaS
Provides a standardized
methodology for accessing
computing capabilities of
demand over the internet.
With this service, the
organization can access
services such as networks,
storage facilities, VPNs, and
processing power.
Decreased capital expenditures
and increased performance. The
cloud vendor provides and
maintains the IaaS cloud service.
Increased flexibility and scalability
10
Cloud Services Vendor Selection Criteria
Selection
Criteria Name
Selection Criteria Description
Selection Criteria
Value (Weighting
in Points)
Cost
It is essential to ensure that the vendor offers pricing
structures within the budget. It is important to seek clarity in
cloud service pricing
10
Security
standards and
certifications
The vendor must be compliant with industry certifications
that ensure data security. Appropriate data governance
technique, coupled with structured service support, is at the
top of cloud selection criteria for a cloud service provider.
10
Cloud Services Recommended Vendors
Vendor
Name
Amazon
AWS
Vendor Strengths
Vendor Weaknesses
Products/Services
Provided to Project
Aggregate
Selection
Criteria
Score
Storage, networking,
applications
10
•
Flexible
•
Price variations
•
Secure
•
Limited control
•
Userfriendly
•
Default limitations
on resources
which may differ
Copyright 2022 by University of Phoenix. All rights reserved.
Project Plan Draft
BSA/425 v2
Page 11 of 12
Microsoft
Azure
•
Fast
deployment
•
Scalability
•
Costeffective
•
High
availability
•
Security
from one region to
the next
•
It can be
complicated for
some
organizations
•
Complicated
pricing model
•
Slow support
process for a large
volume of
customers
Storage, networking,
applications
10
Cloud Services Deployment Challenges
Deployment
Challenge
Deployment Challenge Description
Inter-cloud
architecture
Transitioning between the private cloud and the hybrid cloud can be challenging for the
implementation team. Significant changes may need to be made to the architecture of the
data center.
Application
deployment
The app deployment process can be intricate if the instances are deployed to multiple
clouds. A different deployment process may be needed for each cloud.
Technology Adoption Methods
Method Name
Method Description
Phased
adoption
The legacy and new systems will operate side-by-side, using live data. This will enable
the project manager to assess and make a comparison of the reliability and efficiency of
the new system.
Direct cutover
Some components of the old system will be stopped, and processing switched to the new
system.
Cost/Benefit Considerations
Benefits
Costs
Considerations
Reduced configuration and
maintenance time
Utility costs
Benefits from reduced configuration and
maintenance time are more than the costs.
Quick deployment and scalability
Licensing
costs
The project should proceed if the licensing costs
are lower than the associated benefits.
Copyright 2022 by University of Phoenix. All rights reserved.
Project Plan Draft
BSA/425 v2
Page 12 of 12
References
Kim, W. (2009). Cloud computing: Today and tomorrow. J. Object Technol., 8(1), 65-72.
Javid, T., Riaz, T., & Rasheed, A. (2014, June). A layer2 firewall for software defined network.
In 2014 Conference on Information Assurance and Cyber Security (CIACS) (pp. 39-42). IEEE.
Copyright 2022 by University of Phoenix. All rights reserved.
BSA/425 v2
Sample Software Test Plan
Project name:
Purpose of project:
Features To Be Tested/Not To Be Tested
Identify all features and combinations of features that will be tested. Also, describe features that will not
be tested and explain why.
Testing Pass/Fail Criteria
Define the pass/fail criteria for each of the tests defined in this test plan.
Testing Approach
Describe the testing processes, testing types, and testing methods that will be used in this testing project.
Discuss the testing strategy and how it will be applied to test this application.
Testing Cases
Define 12 to 15 test cases for your project.
Testing Materials (Hardware/Software Requirements)
Identify the resources needed for testing in this project. Include the physical facilities, hardware, software,
tools, and any other resources that will be used during testing.
Testing Schedule
Testing Activity
Duration
Resource
Test Plan Creation
5 days
Test Manager
Test Specification
Creation
10 days
Test Leads
Test Specification Team
Review
5 days
Project Team
Component Testing
20 days
Component Testers
Integration Testing
20 days
Component and System
Testers
System Testing
15 days
System Testers
Performance Testing
5 days
System Testers
Copyright 2022 by University of Phoenix. All rights reserved.
Comments
Sample Software Test Plan
BSA/425 v2
Page 2 of 2
Testing Activity
Duration
Resource
Comments
Use Case Validation
10 days
System Testers
Alpha Testing
5 days
Product
Managers/Analysts
Beta Testing/Pilot
Program
20 days
Pilot Program End-Users
Risks and Contingencies Matrix
Risk
Probability
Risk Type
Owner
Contingencies/Mitigation
Approach
Do not have
enough skilled
workers to test
components
as they are
ready for
testing.
25%
Project
Resources
Testing Manager
Testing schedule will be
adjusted based on available
resources.
Testing team
member
turnover
10%
Project
Resources
Testing Manager
Adjust testing schedules.
Make sure testing team
members are cross-trained on
testing techniques in case a
team member leaves the
organization.
Copyright 2022 by University of Phoenix. All rights reserved.
BSA/425 v2
Company’s name:
EBanking Inc.
Project Proposal
Project Scope Statement
•
Project Title: A Project Proposal for a Technical Architecture to Support an Internet Bank
•
Project Sponsor(s): (The project sponsor is the project’s commissioner. This party promotes and
provides vision and guidance for the project.)
•
Business Context for the System: This project will deliver the technical architecture over which
the client will run the internet bank business.
•
Project Scope Description: The deliverables for this project are all the technical components that
will form the framework over which all the business processes in internet banking will be
delivered. Upon the completion of the project, the client will have a fully functioning digital
platform over which to run the internet banking business.
•
Date Prepared: 07/11/2022
Problems/Issues/Opportunities the Proposed System Expected to
Solve
Problems
Issues
Opportunities
Scalability
Evolution of technology and
growth of customer base
There is an opportunity to set up
the system to be scaled up to
incorporate new technologies in
internet banking, cloud
computing, and electronic
finance while also allowing the
expansion of the system to
enable it to serve a larger
customer base.
Security
Cybersecurity
Cybersecurity is an enduring
threat in internet banking
(Alghazo et al., 2018). The
project has the opportunity to
employ the latest robust
solutions to ensure the security
of online financial transactions
Availability
Around-the-clock support system
for customers
People choose internet banking
to avoid the time constraints of
traditional banking. Therefore,
the project has the opportunity to
provide around-the-clock
services and support for the
customers.
Copyright 2022 by University of Phoenix. All rights reserved.
Project Proposal Template
BSA/425 v2
Page 2 of 6
Manageability
Ease of use and management
The applications over which the
internet banking processes are to
be performed must be userfriendly. They must also be easy
to update.
Project Objectives
Project Objective Name
Project Objective Description
(Organizational and departmental goals/objectives
addressed by the proposed work)
Technical architecture
The project’s objective is to provide the technical
architecture the client requires to run an efficient, scalable,
secure, available, and manageable internet banking
business.
Project Deliverables
Project Deliverable Name
Project Deliverable Description
(Specific products to be delivered)
Application Programming Interfaces
These interfaces will allow the internet bank to link its
products and services with other third-party applications and
services within and without its operational environment.
Instant payment solutions
This framework will allow the internet bank to facilitate its
customers to transfer money between their own accounts and
other accounts in real-time. This solution will include all the
associated processes to ensure safe and convenient
transactions.
Account management solutions
Given the products the client wants to offer, the technical
architecture will include the framework for private ledger
account management to facilitate the integration with other
service providers to allow value-added services and payment
schemes to facilitate deposits and withdrawals.
Biometric technology solution
This deliverable will include the technical framework to allow
the use of biometric technology for authentication and
authorization.
Copyright 2022 by University of Phoenix. All rights reserved.
Project Proposal Template
BSA/425 v2
Page 3 of 6
Project Acceptance Criteria
Project Acceptance
Criteria Name
Project Acceptance Criteria Description
(What are the requirements the project must meet in order to be considered
complete?)
Goals
Provide the technical architecture the client requires to run an efficient, scalable,
secure, available, and manageable internet banking business.
Requirements
All the deliverables will be completed within the stipulated time, human, technical,
and financial resources.
Performance
The deliverables’ codes will be flawless and aligned with the best industry
processes for digital financial services.
Acceptance
The project will be complete when it can be demonstrated that the implementation
of the technical infrastructure will allow the smooth running of the internet banking
business and will satisfy the identified criteria by the client.
Project Exclusions
Project Exclusion
Name
Licensing
Project Exclusion Description
(What aspects of the work are outside of the scope of the project?)
Some of the components will require the client to purchase licenses. The scope of
the project excludes the purchase of the licenses.
Project Constraints
Project Constraint Name
Project Constraint Description
(What are the limitations that the team must work within?)
Time
The project is limited to a workday of eight hours and a five-day workweek.
Copyright 2022 by University of Phoenix. All rights reserved.
Project Proposal Template
BSA/425 v2
Page 4 of 6
Financial
The project will be limited to the budget approved by the client. Any additional
work components will have to remain within the budget unless a
supplementary budget accompanies them.
Scope
The project’s scope remains the provision of technical architecture for internet
banking businesses. The project is limited to the components that fall within
this scope.
Project Assumptions
Project Assumption
Name
Project Assumption Description
(What information should the team know at this point in the planning?)
Project delivery times
The team should know when the client requires the final product to inform
decisions on financial planning, workflow planning, human resource planning,
and the timelines for various deliverables.
Emerging technologies
The team should know whether the client wants to adopt emerging digital
technologies, such as cloud computing, to enable the design and execution of
the deliveries to incorporate the capabilities.
Project Methodology
The proposed project will use the agile methodology. This is a methodology in software development where
the project transitions from the planning phase to the deployment phase through iterative and incremental
steps (Al-Saqqa et al., 2020). The agile methodology is suitable for this project because, in addition to
reducing the overheads, it facilitates the adoption of changes without jeopardizing the previous steps or
necessitating excessing rework (Al-Saqqa et al., 2020). The steps of the methodology will include gathering
requirements, analysis of the concept, design, coding the technical framework, testing, partial delivery, and
final product. Customer feedback will be solicited and incorporated in between the steps to ensure alignment
of the product with the client’s desires to avoid major reworks later in the process.
High-Level Work Schedule: Project Scope
Description of Work
Assumptions and Constraints
The development of a technical infrastructure for
running an internet banking business. The
deliverables will include all the Application
Programming Interfaces, account management
solutions, biometric technology solutions, and instant
payment solutions.
The project has financial, time, and scope
constraints. It is assumed that the client will provide
all the requirements.
Milestones
Due Dates
Copyright 2022 by University of Phoenix. All rights reserved.
Project Proposal Template
BSA/425 v2
Page 5 of 6
Commencement date
7/11/2022
Partial handover
9/12/2022
Completion date
9/30/2022
ID
Activity
Resource
Labor
Hours
Labor
Rate
Labor
Total
Material
Units
Material
Cost
Material
Total
Total
Cost
1
Requirements
gathering
Client
56
$120
$6720
2
Concept
design
Client
100
$120
$12000
5
$750
$3750
$15750
3
Testing
Client
20
$120
$240
5
$750
$3750
$3990
$6720
Quality Requirements
The technical infrastructure will align with the best industry practices in software engineering. It will also have
inbuilt security features in line with the best practices in cybersecurity from the perspective of financial
services.
Acceptance Criteria
The technical components required for a platform on which an internet business will run will be provided upon
the completion of the project.
Technical Information
The technical architecture will include all the codes for the components the client will require to run an internet
banking business. The technical architecture will consist of rudiments through which the client will integrate
other emerging applications and services to enable scalability as technologies emerge without needing an
architectural overhaul.
Agreement Information
The agreement on which this project is based places responsibility upon each party to perform their duties.
The agile methodology allows flexibility in the work processes to ensure that the project captures the ideas
and desires of the client. However, the established work process must be followed during the various phases
of the methodology. The agreement binds both parties to the project timelines, budgets, and other
constraints.
Copyright 2022 by University of Phoenix. All rights reserved.
Project Proposal Template
BSA/425 v2
Page 6 of 6
References
Al-Saqqa, S., Sawalha, S., & Abdelnabi, H. (2020). Agile software development: Methodologies and
trends. International Journal of Interactive Mobile Technologies, 14(11), 246–270.
https://doi.org/10.3991/IJIM.V14I11.13269
Alghazo, J. M., Kazmi, Z., & Latif, G. (2018). Cyber security analysis of internet banking in emerging
countries: User and bank perspectives. 4th IEEE International Conference on Engineering
Technologies and Applied Sciences, ICETAS 2017, 2018-January, 1–6.
https://doi.org/10.1109/ICETAS.2017.8277910
Copyright 2022 by University of Phoenix. All rights reserved.