Modesto Bank Project Documentation
Version 1.3
March 8, 2016
Modesto Bank Project
Project Participants:
Brandon Miller
Subathra Aravamudhan
Wenjie Li
Jae-Eun Russell
Modesto Bank
Modesto Bank System Requirements Documentation
533581666
Version: 1.3
Save Date: 3/8/2016
Contact Information
Project Name: Modesto Bank
Project Specifications Document
Project Sponsor: Samuel Burer, CEO
Email: samuel-burer@uiowa.edu
Phone: (319)-335-0931
Participants
Name
Phone
E-Mail Address
Business Unit Represented
Brandon Miller
353-5148
brandon-r-miller@uiowa.edu
System Development
Subathra
Aravamudhan
341-8089
subathraaravamudhan@uiowa.edu
System Development
Wenjie Li
353-4734
wenjie-li@uiowa.edu
System Development
Jae-Eun Russell
358-7636
jae-russell@uiowa.edu
System Development
Reference Document(s)
Date
Version
Author
Document Title
Page 2 of 48
Modesto Bank
Modesto Bank System Requirements Documentation
533581666
Version: 1.3
Save Date: 3/8/2016
Table of Contents
1 System Request ...................................................................................... 5
2 Executive Summary ................................................................................ 7
3 Work Plan................................................................................................. 9
4 Project Charter ...................................................................................... 10
5 Risk Analysis ......................................................................................... 15
6 Economic Feasibility Analysis ............................................................. 15
7 Requirements Specification ................................................................. 16
8 Process Model: Current Business Process Flows.............................. 18
9 Process Model: Proposed Business Process Flows ......................... 19
10 Entity Relationship Diagram ................................................................. 19
11 Program Specifications ........................................................................ 23
12 Database Tables .................................................................................... 26
13 Screen Mockups .................................................................................... 31
14 Testing Documentation......................................................................... 32
15 Potential Improvements ........................................................................ 48
Page 3 of 48
Modesto Bank
Modesto Bank System Requirements Documentation
533581666
Version: 1.3
Save Date: 3/8/2016
Signoff Page
The purpose of this document is to provide you, the stakeholder, with a clear understanding of the
requirements identified for the effort. This document contains the detailed system requirements that have
been identified, as well as all of the business requirements necessary to implement the identified solution
for this effort.
Please provide your signature (or email approval) to the Project Manager to indicate that you have
reviewed and are in agreement with the contents of this document.
Should you have any questions or concerns pertaining to this document, please feel free to contact the
Project Manager for additional information or clarification.
Approved:
I have read and agree to the project documentation details.
Name
Position
Deliverable Point
Signoff
Date
Samuel Burer
Modesto Bank, CEO
Milestone 1
SB
2-18-03
Samuel Burer
Modesto Bank, CEO
Milestone 2
SB
3-25-03
Samuel Burer
Modesto Bank, CEO
Milestone 3
SB
4-21-03
Samuel Burer
Modesto Bank, CEO
Milestone 4
SB
5-8-03
Page 4 of 48
Modesto Bank
Modesto Bank System Requirements Documentation
533581666
1
Version: 1.3
Save Date: 3/8/2016
System Request
1.1
Business Need
To increase efficiency and customer service through the development of a user-friendly, web-based
banking information system, which will:



1.2
Allow for maintenance of a centralized database for the managers of Modesto Bank
Function through an interactive user-friendly website with entry, update, add, and delete options
Deliver the most recent product information to all managers and officers of Modesto Bank via the
internet
Functionality & Scope
The system (website & database) will have the following functionalities:





1.3
Equipped to handle four different types of products, namely:
1. Money market products.
2. Credit card products.
3. Mortgage products.
4. Certificate of deposit products.
Enabled to allow the bank managers to make changes in the products.
Permits multiple users to be able to access the database at any given time
Secured website interface that will allow easy navigation of various parts of the site after
confirming the login ID and password.
Update/add/delete functionalities to edit the fields in the database to allow for the most
recent information about the products.
Expected Value
Tangible:

Increased customer service by being able to provide the customer with the most up-todate information. Rates will be updated in the timeliest fashion.

Reduction of paper by not having to print and distribute weekly product rate specification
sheets
Intangible:



Recognition of Modesto Bank as a forerunner for incorporating information technology in
their central database.
Increased work efficiency among managers and other top officials
Less possibility for distortion of product information among the various branches of the
bank and the central bank.
Page 5 of 48
Modesto Bank
Modesto Bank System Requirements Documentation
533581666
1.4
Version: 1.3
Save Date: 3/8/2016
Special Issues & Constraints




The completion of the project, including the functioning interactive website, by the second
week in May
This project is expected to end before the peak period of mortgage loans, which
coincides with the end of the school year.
The project team is planning to extend our support of Modesto bank by giving a formal
presentation in May after the successful completion of the project.
The presence of a support team will be available to aid managers in using the interface.
However, since the website requires few skills to navigate and use, the time required for
training on the functionality should be relatively small.
Page 6 of 48
Modesto Bank
Modesto Bank System Requirements Documentation
533581666
2
Version: 1.3
Save Date: 3/8/2016
Executive Summary
The strategic plan for the development of this web based application can be divided into four units. They
are;
 Mission statement
 Information technology goals
 Information technology work plan
 Formal presentation and Future support.
Mission statement
The mission of this project is to provide the highest quality of information and support in promoting
sensitive information transfer among the various managers through the internet of the Modesto Bank.
Information technology goals
The following goals would be accomplished by pursuing the following standards for the project:
 Login and security standards
 Requirements standards
 Code standards
 Table standards
 Website standards
 Reporting/Form standards
 Testing standards
 Documentation and training standards
.
Login and security standards
This website would be enabled with the following security features:
 A login and password prompt would be built in the “To be” system to enable clients to identify
themselves. The password feature of the website would help ensure the security of the site
 The team is aiming to add an extra security feature to the site allowing only certain managers to
update the fields
 The team would eventually set cookies on the website for easy navigation of the various links in
the site
Requirement Standard
A website with a centralized database for the managers of Modesto Bank will be developed with four
different kinds of bank products. These products include:
 The money market accounts
 The certificate of deposit accounts
 The mortgage accounts
 The credit card accounts
Code Standard
The coding style includes the following:
 The code will be clearly commented
 A standard indention of the code will be practiced for future readability of the code
 Include the date for all code pages
Page 7 of 48
Modesto Bank
Modesto Bank System Requirements Documentation
533581666
Version: 1.3
Save Date: 3/8/2016
Table Standards:
 All the tables would be normalized up to the third normal form
 Primary keys such as the product IDs will be used to uniquely identify the records
 All the products have fields that can be updated by some of the senior managers of the bank
 The tables do not give permission for any fields in the various products to be deleted
 Even though only a few managers are given permission to update the fields of the product all
managers are given permission to view and query from different fields
 Field independence would be assured in all the tables
Form Standards:
 The font used would be sans-serif
 Every form would have a title
 All the reports would be both viewable and printable.
Website Standards:
 A easily navigable and user-friendly website would be developed
 Review and update of the fields by the clients would be allowed
 The site would be empowered to carry on the querying and reporting capabilities.
 The website would be compatible with the most commonly used web browsers, such as
“Internet Explorer and ”Netscape”
 The site would be enabled to grow with the company’s expansion.
Testing Standards
 The team members have developed the testing phase with the utmost care. Each part of the
program and website would be tested individually and as a group by the team members.
 The testing team would concentrate on the security and functionality of the site
Documentation and training standards
 The documentation of the work inclusive of the past milestones would be placed as a link to
the website.
 This is expected to aid in future developments to the website for current and future users.
Information technology work plan
The team members would work together in building a successful project. Any changes to the system or
proposed changes would be duly communicated to the client and carried on after receiving the client’s
written approval.
Formal presentation and Future support.
A formal presentation of the project would be delivered after the successful implementation of the
project. A written document supporting the project is also to be delivered along with the presentation.
Page 8 of 48
Modesto Bank
Modesto Bank System Requirements Documentation
533581666
3
Version: 1.3
Save Date: 3/8/2016
Work Plan
Page 9 of 48
Modesto Bank
Modesto Bank System Requirements Documentation
533581666
4
Version: 1.3
Save Date: 3/8/2016
Project Charter
This document will describes the project’s rules and guidelines that all team members should comply with. The
purpose of this project charter is to coordinate group members; match team members’ skills with the project need;
and minimize conflicts, misunderstanding, and problems between members as the project progresses.
 Team Structure
The following chart illustrates the proposed team structure of our project. Each role is defined and assigned to
team member as listed in the Staffing Plan table below. The roles will stay consistent throughout the project. The
structure is based on the principle that each team member’s skill should match with the needs of the project in
order to motivate each individual and fulfill the objectives of the project. In forming the team structure, each team
member’s technical skills as well as the interpersonal skills are considered. For example, the persons with most
technical experience with information system design were assigned as the System Analysts. Team members who
have knowledge about the project’s business aspect will take the role of Business Analyst. The person with strong
interpersonal skills is assigned to be liaison with the Client.
1. Team Structure Chart
Project Manager
Brandon Miller
Official Team Secretary
Aravamudhan Subathra
Business Analyst
Brandon Miller
System Analyst
Jane Russell
Wenjie Li
Aravamudhan Subathra
Wenjie Li
Web Site Coordinator
Jane Russell
Brandon Miller
Formal Liaison with Client
Aravamudhan Subathra
2. Table of Staffing Plan
Role
Project Manager
Business Analyst
System Analyst
Web Site Coordinator
Formal Liaison with
Client
Official Team Secretary
Description
Oversees the project and ensures that
it meets its objective in time, function,
and cost according to the project plan
Ensures the system will provide the
business with value and meet the
business’s requirements
Design the information system and
ensure the system conforms to
information systems standards
Design the project website
Communicate and negotiate with the
client
Create team meeting agenda and
coordinates the team members
Assigned To
Brandon Miller
Brandon Miller, Wenjie Li,
Aravamudhan Subathra
Wenjie Li, Jane Russell
Brandon Miller,
Jane Russell
Aravamudhan Subathra
Aravamudhan Subathra
Page 10 of 48
Modesto Bank
Modesto Bank System Requirements Documentation
533581666
Version: 1.3
Save Date: 3/8/2016
 Decision Making
Major decisions, such as the ones that will affect the objectives of the project and thus will involve all team
members, will be made on a consensus base. The reason for this is: the project team consists of a small amount
of team members and each member’s work is closely related. Therefore, a high level of coordination and
understanding between group members is crucial to the success of the project. Majority vote or individual
discretion will be used to make minor decisions. This method is more efficient and reasonable for minor decisions
that have only negligible affect on the project.
 Work Load
Work load for our project will be distributed mainly based on each team members’ relative expertise. Any
members who want to develop some specific skills are also encouraged to work together with the person mainly
responsible for that work task. The following list demonstrates the proposed work task distribution among the
project team.
Database Design and Maintenance:
HTML/Web Design:
SQL/ Instruct via FTP Application:
ASP Application:
Wenjie Li
Brandon Miller
Aravamudhan Subathra
Jane Russell
Before each milestone, a detailed work plan that describes each person’s work load during that milestone should
be discussed and agreed upon among all members. Detailed work load and responsibilities should be addressed
as specifically as possible before working on each milestone.
 Communication and Meetings
Email will be the main tool to communicate among members. We are not going to have regular meetings,
however, we are going to use the section time for communication on important topics. We will also frequently
meet on an as-needed basis.
 Peer Evaluation
We will divide the work load based on individual specialties with the individual’s approval. Therefore we expect
every member should complete each part that is assigned by the given time. We will evaluate the quality of the
work when we have a meeting.
100% attendance for every meeting is required unless there is a pre-arranged appointment or conflict.
Promptness for every email is expected as well.
We expect every member to participate fully in each stage throughout the whole project. If a member misses a
meeting or deadline more than once without any notification to other members or does not respond to e-mails two
times in a row, a meeting will be set-up with all members to resolve any problems.
 Interaction with Client
We will update the Client only when major portions of the project have been completed. The Project Manager or
Formal Liaison with Client will be the main contact person for our client.
We will try our best to meet the cost that is approved by our customer. However, if we have to go over budget, we
will set-up a meeting with our customer and give full explanation about the matter. Then we will let the customer
decide whether it goes over budget with full functionalities or curtail some of them that were planned at the initial
planning and analysis stages of project. We will try to convince our customer to have full functionalities if they are
relevant to the business value, even though it may require going over budget.
Page 11 of 48
Modesto Bank
Modesto Bank System Requirements Documentation
533581666
5
Version: 1.3
Save Date: 3/8/2016
Risk Analysis
Risk Analysis usually reveals important problems that may naturally occur during the course of the project. Risk
management involves risk identification, impact analysis, risk monitoring, and control.
This document identifies the risks in the Modesto Bank project. A complete analysis of the project requirements
has enabled the team members to identify the following risks in the project, which are listed in descending order
of severity:
1.
2.
3.
4.
5.
6.
7.
Schedule conflict among project members
Incorrect initial project effort estimate
Shortfalls in externally furnished Data (data given by the bank)
Continuing stream of requirement changes
Personnel Shortfalls
Developing the wrong functions and properties
Poor system maintainability.
We will analyze these risks, their potential impact on the project schedule, cost, and quality, and how we plan to
monitor and control the risks.
1. Schedule conflict among project members
Risk identification: As each one of the project members is involved in various tasks, their ability to
meet in person with the rest of the group to discuss the problems may be difficult.
Impact Analysis: Since this project has been planned as a group project, the contribution of each
member of the team is very important for the success of the project as a whole. Failing to put in a joint
effort will result in a serious impact on Project Schedule and Quality and may also affect delivered
functionality.
Risk Monitoring: The team will meet regularly to take stock of the progress achieved by each team
member and the overall project objectives.
Risk Control: During the initial meeting among the project members, the available meeting times
between members was discussed .The project members decided to meet once a week during
discussion and on an as-needed basis. The team also agreed to use email to communicate about the
latest work. In case of severe necessities, the members promised to rearrange their schedule to
accommodate the urgent meeting.
Likelihood of Risk: High
2. Incorrect initial project effort estimate
Risk identification: The team has used MS Project to plan the project. However, the estimate for the
tasks involved is based on the experience of the team members and a “Rule of Thumb” technique has
been used. Thus, this type of estimation could be wrong for some tasks involved. This is a risk due to
erroneous effort estimation and not due to incorrect requirements specification.
Impact Analysis: Any error in effort estimated will impact the Project Schedule.
Risk Monitoring: The team will closely monitor the effort actually required to complete a task and
compare it with the estimated effort and highlight any difference. The project schedule will require
careful monitoring and updating.
Page 12 of 48
Modesto Bank
Modesto Bank System Requirements Documentation
533581666
Risk Control: The team will:


Version: 1.3
Save Date: 3/8/2016
Work extra to complete the project on time.
Seek innovative methods, such as the use of templates and the re-use of code, to reduce the
task time required
Likelihood of Risk: Moderate
3. Shortfalls in externally furnished data
Risk Identification: It is possible that the customer has not supplied all details related to the existing
system. This may be a serious risk if basic relationships and attributes have been captured incorrectly.
Impact Analysis: This risk will result in changes to the system during acceptance testing by the
customer. This will have an impact on Schedule, Quality and Cost.
Risk Monitoring: The requirements given will be reviewed for completeness and missing or
incompatible requirements will be brought to the attention of the client.
Risk Control: The system will be developed with flexibility to accommodate minor changes. Also, the
team will work with the client to identify the specific nature of the data.
Likelihood of Risk: Moderate
4. Continuing stream of requirement changes
Risk identification: A continuous stream of increased requirements placed by the project sponsor or
Modesto Bank after the initial agreement has been solidified.
Impact Analysis The newly included requirements will pose a threat that would hinder the spirit of the
members involved, increase the cost of the project, possibly decrease the quality of the project, and
increase the estimated time of completion of the project.
Risk Monitoring: The team will communicate with the project sponsor regarding any changes to the
requirements. Only if time permits will requirement additions be allowed without sacrificing other
functionality.
Risk Control: During the first meeting with the client, all the requirements of the project, including the
completion date, were discussed in detail. A written document from the client also supports this. It has
been agreed that any change in the requirements would result in an impact analysis being conducted to
determine the impact on schedule, cost, and the functionality of the project.
Likelihood of Risk: Minimal to moderate
5. Personnel Shortfalls:
Risk Identification: The project members were selected based on their ability to handle similar sized
projects. The members have worked with others on similar projects and have proved themselves in
solving many problems. However, it is possible that one or more of the members will not be able to
deliver the required amount of effort due to several extraneous reasons.
Impact Analysis: Since the project has been planned with an aggressive schedule, it is very essential
that all team members contribute fully. Failing to do so will cause an impact on Project Schedule and
Quality (delivered functionality).
Page 13 of 48
Modesto Bank
Version: 1.3
Modesto Bank System Requirements Documentation
Save Date: 3/8/2016
533581666
Risk Monitoring: The team will meet regularly to take stock of the progress achieved by each team
member and the overall project objectives.
Risk Control: The rest of the group would work extra as members of a team and complete the project
on time. However, if the impact is too much to accommodate, then an assessment would be made and
brought to the attention of the client, in a professional way to seek a revision in schedule, functionality
or both.
Likelihood of Risk: Minimal to Moderate
6. Developing the wrong functions and properties
Risk Identification: The application software developed may fail to deliver designed functions and
customer requirements.
Impact Analysis
This is an important risk and needs to be closely watched. If this risk is not
monitored and controlled, it will result in re-work, delay, poor quality, and client dissatisfaction. The
impact is on Quality, Schedule, and Cost.
Risk Monitoring: The team will regularly review, test the work done by each other, and ensure that
functions work as designed and required.
Risk Control: Each team member is expected to suggest their opinions and feedback regarding the
work of other members before actual delivery of the developed functionality. This review process will
greatly reduce the risk of functionality not being delivered. Also the client will review the deliverables
and provide specific feedback, which will then be used by the team in further work. The team members’
background knowledge and team spirit will also aid them in the analysis of the situation and ensure
good quality of work.
Likelihood of Risk: Minimal
7. Poor system maintainability:
Risk Identification: Though the application developed may meet all the requirements of the customer,
it may be developed in such way that making future enhancements to it will be very difficult.
Impact Analysis: This will cause additional wasteful effort in future projects and will also result in the
inability to deliver seemingly simple changes quickly.
Risk Monitoring: The team will attempt to design the system in a flexible manner to support future
enhancements, and the code will be reviewed to ensure good coding practices.
Risk Control: The team members will walk through the code and review the design to ensure
maintainability.
Likelihood of Risk: Minimal
Page 14 of 48
Modesto Bank
Modesto Bank System Requirements Documentation
533581666
6
Version: 1.3
Save Date: 3/8/2016
Economic Feasibility Analysis
Economic Feasibility Analysis
2003
2006
2007
Total
$8,400
$60
$8,460
$8,820
$60
$8,880
$9,261
$60
$9,321
$9,724
$60
$9,784
$44,205
$300
$44,505
$8,150
$800
$8,950
$0
$0
$0
$0
$0
$0
$0
$0
$0
$0
$0
$0
$8,150
$800
$8,950
$300
$21
$1,000
$1,321
$10,271
-$2,211
$300
$21
$1,200
$1,521
$1,521
$6,939
$300
$21
$1,440
$1,761
$1,761
$7,119
$300
$21
$1,728
$2,049
$2,049
$7,272
$300
$21
$2,074
$2,395
$2,395
$7,389
$1,500
$105
$7,442
$9,047
$17,997
$26,508
$8,000
$60
$8,060
Development Costs:
Development Labor
Training
Total Development Costs
Operational Costs:
Remote Hosting
Domain Name Registration
Database/Site Maintenance
Total Operational Costs
Total Costs:
Total
2004
2005
Benefits:
Improved Customer Service
Reduction of Paper
Total Benefits
Present Value of Total assumming 6% annual interest:
Return on Investment
$19,653
147.30%
*Total costs for year 1 may be subject to additional travel expenditures we incur, but total
travel expenditures shall not exceed 8% of total cost.
Page 15 of 48
Modesto Bank
Modesto Bank System Requirements Documentation
533581666
7
Version: 1.3
Save Date: 3/8/2016
Requirements Specification
The strategic plan for the Modesto Bank project has been developed by the team members of the project
according to the information and requirements received from Mr. Burer, the client. After a detailed
analysis of the various requirements stated by the client, the team has proposed the following system
specifications. Any changes to this specification can be carried out only with the written joint approval
of the client and the team members. A special thanks to Mr. Burer from the members of the team for his
time and effort in this project.
Executive Summary
The strategic plan for the development of this web based application can be divided into four units.
They are the:
 Mission Statement
 Login & Security Standards
 Salient Features of the New System
Mission Statement
The mission of this project is to provide the highest quality of information and support in promoting
sensitive information transfer in the most efficient fashion among the various managers throughout the
intranet of the Modesto Bank.
Login and Security Standards:
The website will consist of important and highly sensitive information for the bank, which will require
deployment with the following security features:



A login and password prompt will be built in the “To be” system to enable the client to identify
themselves. The password feature of the website will help ensure the security of the site and its
information.
The team is aiming to add an extra security feature to the site allowing only certain managers to
update the fields.
Cookies may be added to the system for easier navigation throughout different areas of the site
without requiring additional logins.
Salient Features of the New System






The system will satisfy the increased need for high speed & efficient information transfer among
the different branches of the Modesto Bank
The system will be enabled to allow multiple people to view different fields of the products at
the same time.
Even though the system will allow multiple users, only a few of the senior managers will be
given higher privileges like updating and adding data in the fields.
Any change in the database will immediately be reflected on the website.
Details of the different products and the related attributes will be clearly stated
Easy navigation throughout the site to different products offered by the bank.
Page 16 of 48
Modesto Bank
Modesto Bank System Requirements Documentation
533581666
Version: 1.3
Save Date: 3/8/2016
Update Fields
 The system will accommodate numerical changes in the fields of the products.
 The system will allow the managers (senior level) to update and add information in the database
tables.
 The system will not allow the all branch managers to make changes/updates to the tables or the
fields
 Any changes made in the database will be updated immediately, and the changes will be
viewable to all the branch offices.
 New product tables may not be added to the system from the website interface.
 The intranet users will not be allowed to update any of the existing products or information in the
fields.
Delete Fields
 The system will allow the managers (senior level) to update fields, but not delete them.
 Permission to delete any of the fields in the table will not be allowed for any manager including
the senior members.
 The intranet users will not be allowed to delete any of the existing products or information in the
fields.
Page 17 of 48
Modesto Bank
Modesto Bank System Requirements Documentation
533581666
8
Version: 1.3
Save Date: 3/8/2016
Process Model: Current Business Process Flows
Management
Weekly Meeting
Update/Delete/Add
Banking Product
Document
Preperation after
Meeting
Credit Card
Accounts
CD Accounts
Money Market
Accounts
Home Mortgages
Officers/Employees
Page 18 of 48
Modesto Bank
Modesto Bank System Requirements Documentation
533581666
9
Version: 1.3
Save Date: 3/8/2016
Process Model: Proposed Business Process Flows
Management
Weekly Meeting
Update/Delete/Add
Banking Product
Bank Products
Database
Workstation
Workstation
Officers/Employees
Page 19 of 48
Modesto Bank
Modesto Bank System Requirements Documentation
533581666
Version: 1.3
Save Date: 3/8/2016
10 Entity Relationship Diagram
Database Features
A website with centralized database for the managers of Modesto Bank will be developed with four
different types of bank products. The products are:
1. The Money Market product that will include the following fields which can be altered by the
managers according to the changes in the economy:
 Product ID* - It is field that is used to uniquely identify each one of the product.
 Minimum Balance Range – The lower balance limit for that particular interest rate.
 Maximum Balance Range – The upper balance limit for that particular interest rate.
 Interest Rate – The rate of interest the bank will be paying.
 Compounding Rate – The compounding rate for the product expressed in days.
 Minimum Opening Deposit – Any minimum deposit requirement the bank may have.
 Fees – Any fee amount that the bank may require.
 Initial Offering – The date the product becomes available.
 Expiration – The date of expiration of the product.
2. The Mortgage Product includes the following product features which can be updated
according to changes in the economy by specific managers:
 Product ID* - It is field that is used to uniquely identify each one of the product.
 Fixed (Boolean) - The type of interest charged (either fixed for the entire duration of the
mortgage or a variable rate.)
 Length – The duration of the mortgage period expressed in years
 Interest Rate- The interest rate charged for the mortgage loan.
 Discount Points - A percentage of the total loan amount that is needed to be paid in order to
reduce the interest rate on the mortgage loan.
 Origination Fee %- The percentage fee charged by the bank for various origination costs.
 Minimum. Down Payment % -The minimum percentage of the total mortgage loan amount
to be paid by the clients of the bank in order to purchase the mortgage loan
 Maximum Loan Amount- The limit of total mortgage loan amount that will be approved by
the bank.
 Initial Offering – The date the product becomes available.
 Expiration – The date of expiration of the product.
3. The Credit Card Products will include the following fields that can be adjusted and viewed by
the managers of the Modesto Bank:
 Product ID*- The field used to uniquely identify the products.
 Type –The different types of credit cards offered by the bank, which include the Classic,
Student and Platinum cards.
 APR- The annual percentage rate charged for balance on the cards.
 Maximum Credit Limit- The maximum credit limit offered on the different products.
 Eligible for Rewards Program (Boolean) - Expresses whether the card is eligible for the
rewards program.
 Initial Offering – The date the product becomes available.
 Expiration – The date of expiration on the product card.
Page 20 of 48
Modesto Bank
Modesto Bank System Requirements Documentation
533581666
Version: 1.3
Save Date: 3/8/2016
4. The Certificate of Deposit (CD) includes the following adjustable features:









Product ID*- The field used to uniquely identify the products.
Type – The type of CD being offered (fixed or market.)
Minimum Deposit – The minimum deposit requirement for this CD product.
Amount – The amount required for this CD (usually either >$100,000 or < $100,000.)
Term – The length required for this CD product expressed in years.
Interest Rate – The rate of interest the bank will be paying.
Compounding Rate – The compounding rate for the product expressed in days.
Initial Offering – The date the product becomes available.
Expiration – The date of expiration on the product
5. The Accessrights table includes the following features:




Rights_ID*- The field used to uniquely identify the right.
Add – Right for adding data (It indicates with y/n)
Update – Right for updating data (It indicates with y/n).
View – right for viewing data (It indicates with y/n).
6. The Users table includes the following adjustable features:







Username*- The field used to uniquely identify the users.
Password – The field entered by each user
First_name – Users’ first name
Last_name – Users’ last name
Department – Users’ department
Position – Users’ position
Rights_ID – The field that is defined rights for each user. The reference table is Accessrights.
Page 21 of 48
Modesto Bank
Modesto Bank System Requirements Documentation
533581666
Version: 1.3
Save Date: 3/8/2016
Users
username
CHAR(10)
password
First_name
Last_name
department (O)
position (O)
Rights_ID (FK)
CHAR(10)
CHAR(10)
CHAR(10)
CHAR(10)
CHAR(10)
CHAR(10)
CD
AccessRights
Rights_ID
INTEGER
add
update
view
CHAR(10)
CHAR(10)
CHAR(10)
has
CreditCard
ProductID
COUNTER
ProductID
COUNTER
CD_Type
Minimum_Deposit
Above_100000
CD_Terms
APR
Compound_Day
Offering_Date
Expiration_Date
CHAR(50)
CURRENCY
CHAR(10)
DOUBLE
DOUBLE
INTEGER
DATETIME
DATETIME
Type
APR
Credit_Limit (O)
Reward_Eligible (O)
Offering_Date
Expiration_Date
CHAR(50)
DOUBLE
CURRENCY
CHAR(10)
DATETIME
DATETIME
Mortgage
MoneyMarket
ProductID
COUNTER
ProductID
COUNTER
Minimum_Balance
Maximum_Balance
APR
Compound_Day
Minimum_Deposit (O)
Offering_Date
Expiration_Date
CURRENCY
CURRENCY
DOUBLE
INTEGER
CURRENCY
DATETIME
DATETIME
Fixed_Mortgage
Apr
Duration
Point (O)
Origination_Fee (O)
Minimum_Payment (O)
Maximum_Amount (O)
Offering_Date
Expiration_Date
BIT
DOUBLE
SHORT
DOUBLE
DOUBLE
DOUBLE
CURRENCY
DATETIME
DATETIME
Page 22 of 48
Modesto Bank
Modesto Bank System Requirements Documentation
533581666
Version: 1.3
Save Date: 3/8/2016
11 Program Specifications
The following code samples will be used to execute business tasks in the MySQL database.
1. Insert a new mortgage product
<Before Insert command>
ProductID
MG_Fixed
MG_Duration
MG_Apr
MG_Point
MG_OriginationFee
MG_MinPayment
MG_MaxAmount
MG_Offering
MG_Expiration
1y
30
6.094000
0.00
0.00
20.00
650000 2003-04-01 00:00:00 2005-04-01 00:00:00
2y
15
5.530000
0.25
0.00
20.00
650000 2003-04-01 00:00:00 2005-04-01 00:00:00
3n
1
4.304000
0.00
0.00
0.00
650000 2003-04-01 00:00:00 2005-04-01 00:00:00
4n
3/1
4.055000
0.00
0.00
0.00
650000 2003-04-01 00:00:00 2005-04-01 00:00:00
5n
5/1
4.220000
0.00
0.00
0.00
650000 2003-04-01 00:00:00 2005-04-01 00:00:00
6y
10
5.350000
0.00
0.00
20.00
500000 2003-04-01 00:00:00 2004-12-31 00:00:00
7y
13
5.660000
0.00
0.00
5.00
50000 2003-04-01 00:00:00 2006-12-31 00:00:00
8y
10
5.900000
0.25
0.00
10.00
125000 2003-04-01 00:00:00 2003-12-31 00:00:00
SQL Command:
INSERT INTO `mortgage` ( `ProductID` , `MG_Fixed` , `MG_Duration` , `MG_Apr` , `MG_Point` , `MG_OriginationFee` , `MG_MinPayment` ,
`MG_MaxAmount` , `MG_Offering` , `MG_Expiration` ) VALUES ('', 'n', '5', '4.895', '0.00', '0.00', '5', '500000', '2003-04-01 00:00:00', '2005-04-01
00:00:00');
<output>
ProductID MG_Fixed MG_Duration MG_Apr MG_Point MG_OriginationFee MG_MinPayment MG_MaxAmount
MG_Offering
MG_Expiration
1y
30
6.094000
0.00
0.00
20.00
650000 2003-04-01 00:00:00 2005-04-01 00:00:00
2y
15
5.530000
0.25
0.00
20.00
650000 2003-04-01 00:00:00 2005-04-01 00:00:00
3n
1
4.304000
0.00
0.00
0.00
650000 2003-04-01 00:00:00 2005-04-01 00:00:00
4n
3/1
4.055000
0.00
0.00
0.00
650000 2003-04-01 00:00:00 2005-04-01 00:00:00
5n
5/1
4.220000
0.00
0.00
0.00
650000 2003-04-01 00:00:00 2005-04-01 00:00:00
6y
10
5.350000
0.00
0.00
20.00
500000 2003-04-01 00:00:00 2004-12-31 00:00:00
7y
13
5.660000
0.00
0.00
5.00
50000 2003-04-01 00:00:00 2006-12-31 00:00:00
8y
10
5.900000
0.25
0.00
10.00
125000 2003-04-01 00:00:00 2003-12-31 00:00:00
9n
5
4.895000
0.00
0.00
5.00
500000 2003-04-01 00:00:00 2005-04-01 00:00:00
Page 23 of 48
Modesto Bank
Modesto Bank System Requirements Documentation
533581666
Version: 1.3
Save Date: 3/8/2016
2. Update the expiration date of an existing money market product.
<Before update sql command>
ProductID MM_MinBalance MM_MaxBalance MM_Intrest MM_Compound MM_MinDeposit
1
0
MM_Offering
MM_Expiration
99
0.000000
365
1000 2003-04-01 00:00:00 0000-00-00 00:00:00
2
100
999
1.040000
365
1000 2003-04-01 00:00:00 2005-04-01 00:00:00
3
1000
4999
1.390000
180
1000 2003-04-01 00:00:00 2006-05-01 00:00:00
4
5000
24999
1.630000
365
1000 2003-04-01 00:00:00 2005-04-01 00:00:00
5
25000
NULL
1.880000
365
1000 2003-04-01 00:00:00 2004-12-31 00:00:00
SQL Command:
UPDATE moneymarket SET MM_Expiration = ‘2006-04-01’ WHERE ProductID = ‘4’
<output>
ProductID MM_MinBalance MM_MaxBalance MM_Intrest MM_Compound MM_MinDeposit
MM_Offering
MM_Expiration
1
0
99
0.000000
365
1000 2003-04-01 00:00:00 0000-00-00 00:00:00
2
100
999
1.040000
365
1000 2003-04-01 00:00:00 2005-04-01 00:00:00
3
1000
4999
1.390000
180
1000 2003-04-01 00:00:00 2006-05-01 00:00:00
4
5000
24999
1.630000
365
1000 2003-04-01 00:00:00 2006-04-01 00:00:00
5
25000
NULL
1.880000
365
1000 2003-04-01 00:00:00 2004-12-31 00:00:00
Page 24 of 48
Modesto Bank
Modesto Bank System Requirements Documentation
533581666
Version: 1.3
Save Date: 3/8/2016
3. Update the rights of an existing users
<Before update sql command>
Username Password Fname Lname Department Position Rights_ID
NULL
samuel@bank burer
Samuel Burer
CEO
1
jane@bank
russel
jane
russell IT
programmer
2
brandon@bank millar
Brandon Millar
Finance
Manager
1
wenjieli@bank li
wenjie
li
IT
Manager
1
subatha@bank raravamu raravamu subathra Marketing Manager
1
smith
12345
Robert Smith
Marketing Manager
2
SQL Command:
UPDATE users SET Rights_ID = ‘1’ WHERE Username = ‘smith’
<output>
Username Password Fname Lname Department Position Rights_ID
NULL
samuel@bank burer
Samuel Burer
CEO
1
jane@bank
russel
jane
russell IT
programmer
2
brandon@bank millar
Brandon Millar
Finance
Manager
1
wenjieli@bank li
wenjie
li
IT
Manager
1
subatha@bank raravamu raravamu subathra Marketing Manager
1
smith
12345
Robert Smith
Marketing Manager
1
Page 25 of 48
Modesto Bank
Modesto Bank System Requirements Documentation
533581666
Version: 1.3
Save Date: 3/8/2016
12 Database Tables
SQL result
Host: tcbis.biz.uiowa.edu
Database : bank
Generation Time: Apr 11, 2003 at 03:18 PM
Generated by: phpMyAdmin 2.3.3pl1
SQL-query: SELECT * FROM `users` LIMIT 0, 30;
Username
Password First_name Last_name Department
Position
Rights_ID
sam@bank
burer
Samuel
Burer
Marketing
CEO
1
jane@bank
russel
jane
russell
IT
programmer
2
brandon@bank miller
Brandon
Miller
Finance
Manager
1
wenjieli@bank li
wenjie
li
IT
Manager
1
subatha@bank raravamu raravamu
subathra
Marketing
Manager
1
russe
russe
Jane
russell
russe
russe1
1
admin
admin
sam
smith
IT
manager
2
test
test
test
person
none
none
2
testAdmin
test
test
admin
none
none
1
dave
dave
Dave
Mitchell
marketing
senior
2
Chung
password Chung
Han
IT
senior
2
brandon
brandon
Miller
Audit
Internal Auditor
1
Brandon
Page 26 of 48
Modesto Bank
Modesto Bank System Requirements Documentation
533581666
Version: 1.3
Save Date: 3/8/2016
SQL result
Host: tcbis.biz.uiowa.edu
Database : bank
Generation Time: Apr 11, 2003 at 03:19 PM
Generated by: phpMyAdmin 2.3.3pl1
SQL-query: SELECT * FROM `accessrights` LIMIT 0, 30;
Rights_ID Add Update View
1 yes yes
yes
2 no
yes
no
SQL result
Host: tcbis.biz.uiowa.edu
Database : bank
Generation Time: Apr 11, 2003 at 03:34 PM
Generated by: phpMyAdmin 2.3.3pl1
SQL-query: SELECT * FROM `cd` LIMIT 0, 30;
Product_ID CD_Type Minimum_Deposit Above_100000 CD_Terms
APR
Compound_Day
Offering_Date
Expiration_Date
4 Fixed CD
500 no
2 years
2.530000
365 2001-09-01 00:00:00 2003-09-01 00:00:00
5 Fixed CD
500 no
3 years
2.800000
365 2003-01-01 00:00:00 2005-01-01 00:00:00
6 Fixed CD
500 no
5 years
3.580000
365 2003-02-01 00:00:00 2005-02-01 00:00:00
9 Fixed CD
500 yes
1 year
2.150000
365 2003-07-01 00:00:00 2005-07-01 00:00:00
10 Fixed CD
500 yes
2 year
2.680000
365 2002-01-01 00:00:00 2004-01-01 00:00:00
11 Fixed CD
500 yes
3 years
2.950000
365 2003-01-01 00:00:00 2005-01-01 00:00:00
12 Fixed CD
500 yes
5 years
3.730000
365 2002-07-01 00:00:00 2004-07-01 00:00:00
13 Market CD
500 no
1 year
2.250000
365 2000-05-08 00:00:00 2002-05-08 00:00:00
14 Market CD
500 no
2 year
2.720000
365 1998-02-01 00:00:00 1998-05-01 00:00:00
15 Market CD
500 yes
3 years
2.830000
365 1999-10-01 00:00:00 2000-11-01 00:00:00
16 Market CD
500 no
3 years
2.790000
365 1998-04-30 00:00:00 1999-03-10 00:00:00
Page 27 of 48
Modesto Bank
Modesto Bank System Requirements Documentation
533581666
Version: 1.3
Save Date: 3/8/2016
SQL result
Host: tcbis.biz.uiowa.edu
Database : bank
Generation Time: Apr 11, 2003 at 03:20 PM
Generated by: phpMyAdmin 2.3.3pl1
SQL-query: SELECT * FROM `creditcard` LIMIT 0, 30;
Product_ID
Type
1 Platinum Credit Card
Apr
11.150000
2 Student Visa Credit Card 13.990000
Credit_Limit Reward_Eligible
Offering_Date
Expiration_Date
500 yes
2000-04-05 00:00:00 2005-02-05 00:00:00
250 no
2000-04-05 00:00:00 2009-05-09 00:00:00
3 Classic Credit Card
11.100000
25000 yes
2005-05-05 00:00:00 2006-06-06 00:00:00
4 Classic Credit Card
10.000000
25000 yes
2000-03-12 00:00:00 2000-12-12 00:00:00
5 Platinum Credit Card
10.600000
25000 yes
1999-12-01 00:00:00 2000-12-01 00:00:00
6 Platinum Credit Card
11.200000
20000 yes
1998-10-01 00:00:00 1999-10-01 00:00:00
7 Student Visa Credit Card 12.800000
2500 no
1999-03-01 00:00:00 2001-03-01 00:00:00
8 Classic Credit Card
12.300000
20000 yes
1998-01-01 00:00:00 1999-10-01 00:00:00
9 Classic Credit Card
13.100000
2500 no
1997-06-30 00:00:00 1999-06-30 00:00:00
10 Student Visa Credit Card 12.900000
2500 yes
2000-10-10 00:00:00 2002-10-10 00:00:00
11 Student Visa Credit Card 10.500000
15000 yes
2002-02-20 01:00:00 2002-02-20 03:00:00
Page 28 of 48
Modesto Bank
Modesto Bank System Requirements Documentation
533581666
Version: 1.3
Save Date: 3/8/2016
SQL result
Host: tcbis.biz.uiowa.edu
Database : bank
Generation Time: Apr 11, 2003 at 03:21 PM
Generated by: phpMyAdmin 2.3.3pl1
SQL-query: SELECT * FROM `moneymarket` LIMIT 0, 30;
Product_ID
Minimum_Balance
Maximum_Balance
APR
Compound_Day
Minimum_Deposit
Offering_Date
Expiration_Date
1
0
99 0.000000
180
1000 2001-10-01 00:00:00
2003-02-03 00:00:00
2
100
999 1.040000
365
1000 2000-01-05 00:00:00
2004-01-08 00:00:00
3
1000
4999 1.390000
180
1000 2003-04-01 00:00:00
2006-05-01 00:00:00
4
5000
24999 1.630000
365
1000 2003-04-01 00:00:00
2006-04-01 00:00:00
8
100000
200000 3.200000
180
80000 2003-01-01 00:00:00
2004-01-01 00:00:00
9
1000
100000 0.880000
365
100 2003-01-01 00:00:00
2003-06-01 00:00:00
10
0
100000 0.150000
365
0 2002-01-01 00:00:00
2005-01-01 00:00:00
11
5000
25000 2.300000
354
100 2002-01-20 02:00:00
2003-01-20 02:00:00
12
100
999 1.040000
365
1000 2003-04-01 00:00:00
2005-04-01 00:00:00
13
1000
4999 1.390000
180
1000 2003-04-01 00:00:00
2006-05-01 00:00:00
14
5000
24999 1.630000
365
1000 2003-04-01 00:00:00
2006-04-01 00:00:00
15
25000
NULL 1.880000
365
1000 2003-04-01 00:00:00
2004-12-31 00:00:00
Page 29 of 48
Modesto Bank
Modesto Bank System Requirements Documentation
533581666
Version: 1.3
Save Date: 3/8/2016
SQL result
Host: tcbis.biz.uiowa.edu
Database : bank
Generation Time: Apr 11, 2003 at 03:21 PM
Generated by: phpMyAdmin 2.3.3pl1
SQL-query: SELECT * FROM `mortgage` LIMIT 0, 30;
Product_ID Fixed_Mortgage Duration
APR
Point Origination_Fee Minimum_Payment Maximum_Amount
Offering_Date
Expiration_Date
1 yes
30
6.095000 0.25
20.00
20.00
650000 2001-05-01 00:00:00 2005-07-01 00:00:00
2 yes
30
5.530000 0.25
0.00
30.00
65000 0000-00-00 00:00:00 0000-00-00 00:00:00
3 no
15
4.304000 0.00
0.00
0.00
650000 2008-07-20 09:00:00 2004-06-20 08:00:00
4 no
30
4.055000 0.00
0.00
0.00
650000 2003-04-01 00:00:00 2005-04-01 00:00:00
5 no
5
4.220000 0.00
0.00
0.00
650000 2003-04-01 00:00:00 2005-04-01 00:00:00
6 yes
10
5.350000 0.00
0.00
20.00
500000 2003-04-01 00:00:00 2004-12-31 00:00:00
7 yes
15
5.660000 0.00
0.00
5.00
50000 2003-04-01 00:00:00 2006-12-31 00:00:00
8 yes
10
5.900000 0.25
0.00
10.00
125000 2003-04-01 00:00:00 2003-12-31 00:00:00
9 no
5
4.895000 0.00
0.00
5.00
500000 2003-04-01 00:00:00 2005-04-01 00:00:00
10 no
15
8.055000 0.00
0.00
15.00
650000 2003-04-01 00:00:00 2005-04-01 00:00:00
Page 30 of 48
Modesto Bank
Modesto Bank System Requirements Documentation
533581666
Version: 1.3
Save Date: 3/8/2016
13 Screen Mockups
Page 31 of 48
Modesto Bank
Modesto Bank System Requirements Documentation
533581666
Version: 1.3
Save Date: 3/8/2016
14 Testing Documentation
The goal of testing is to locate system errors before installation these system errors can take different
forms including the coding errors that reduce system efficiency. For this reason the Modesto team
project members designed a systematic testing procedure that covers all functions, even the ones that are
certain to work. The following are the testing approaches used by the team:
1. Black box testing
2. White box testing
3. User interface testing
4. Use scenario testing
5. Security testing
1. Black box testing
The test was based on checking the requirements stated on the system request in the first
milestone of the project. The team crosschecked the fully developed product with functionality stated in
the system request document and is proud to announce that it has completed all the promised features
(except the few mentioned and discussed with the client by the members of the team).The products
developed include the four different bank accounts equipped with update and add features for each one
of them. The team has also ensured a secure login with user name and password features .The tests
conducted by the team members on the functionality of the products were successful.
2. White box testing
The code for the interactive products is coded in visual-basic andASP.net.
The programmers of the project team added comments to the processes performed by the system. This is
done for future readability and a guide line for the code. The coding for the interface follows the formal
coding standard and has been reviewed by the members of the team. The system analyst and the
programmers have conducted several sessions of “code walk-through” to avoid errors. Thus the team is
proud to say this part of program testing was completed successfully.
3. User interface testing
The user interface testing includes the following subcategories identified by the team:
3.1 The three click rule testing
3.2 The two click rule testing
3.3 Loading time testing
3.4 Query time testing
3.5 Query results testing
3.6 Product Headings
3.7 Aesthetics /consistency testing
3.8 Format Testing
3.9 User experience testing
4. Use scenario testing
The use scenario testing includes the following subcategories defined by the team:
4.1 Testing results for appropriate data
4.2 Testing results for different data format
4.3 Testing results for inappropriate data
4.4 Testing results for unfilled data fields
4.5 Testing links for different areas.
5. Security testing
The security testing for the team involved the following:
5.1 login /password security.
Page 32 of 48
Modesto Bank
Modesto Bank System Requirements Documentation
533581666
Test Condition Id: 3.1
Version: 1.3
Save Date: 3/8/2016
Tester: subathra
Requirements Addressed: User interface/usability.
Test Objective: Test conducted to check if the feasibility” three mouse click rule” .
Data Field:
NA
Value Entered:
NA
Expected Result: A test conducted to check if the user is able to navigate from main page
to any action within three mouse clicks for all the products offered by the team.
Observed Result : The team members were able to navigate from main page to any action
within three mouse clicks
Test Passed / Failed: The test was successful.
Page 33 of 48
Modesto Bank
Modesto Bank System Requirements Documentation
533581666
Test Condition Id: 3.2
Version: 1.3
Save Date: 3/8/2016
Tester: subathra
Requirements Addressed: User interface/usability
Test Objective: Test conducted to check if the two mouse click rule is plausible.
Data Field:
NA
Value Entered:
NA
Expected Result: Test conducted to check if the user could navigate from sub menu to any
action within two mouse clicks for all the products offered by the team.
Observed Result: The team was able to navigate from sub menu to any action within two
mouse clicks for all the products.
Test Passed / Failed: The test was successful.
Page 34 of 48
Modesto Bank
Modesto Bank System Requirements Documentation
533581666
Test Condition Id: 3.3
Version: 1.3
Save Date: 3/8/2016
Tester: subathra
Requirements Addressed: User interface/usability
Test Objective: Test conducted to record the time taken for each page to load.
Data Field:
Login and password field.
Navigation among different products.
Value Entered:
Login –id and password.
Mouse clicks.
Expected Result: Except for the login page (which accesses a data base to cross check for
the login and password) all the other products take a very minimum time of two seconds to
load.
Observed Result: The observed result was same as the expected result.
Test Passed / Failed: The test was successful.
Page 35 of 48
Modesto Bank
Modesto Bank System Requirements Documentation
533581666
Test Condition Id: 3.4
Version: 1.3
Save Date: 3/8/2016
Tester: subathra
Requirements Addressed: User interface/usability
Test Objective: Test conducted to record the time to run a query using update,
for each product.
Data Field:
Update link.
Show-all link.
features
Value Entered:
Mouse clicks.
Mouse clicks.
Expected Result: The results are expected to appear within two seconds of clicking the
mouse .This applies to the most complicated query.
Observed Result: The observed result was same as the expected result.
Test Passed / Failed: The test was successful.
Page 36 of 48
Modesto Bank
Modesto Bank System Requirements Documentation
533581666
Test Condition Id: 3.5
Version: 1.3
Save Date: 3/8/2016
Tester: subathra
Requirements Addressed: User interface/usability
Test Objective: Test conducted to crosscheck the readability of the query and the
information provided by the query results of each product.
Data Field:
Update link.
Show-all link.
Value Entered:
Mouse clicks.
Mouse clicks.
Expected Result: The fields of the query results are expected to be user friendly and the
results of the query are expected to carry the most recent information.
Observed Result: The observed result was same as the expected result.
Test Passed / Failed: The test was successful.
Page 37 of 48
Modesto Bank
Modesto Bank System Requirements Documentation
533581666
Test Condition Id: 3.6
Version: 1.3
Save Date: 3/8/2016
Tester: subathra
Requirements Addressed: User interface/usability
Test Objective: Test conducted to crosscheck the headings in each product for user-friendly
names.
Data Field:
Update link.
Show-all link.
Login page.
Money market page
Mortgage page
Certificate of deposit page
Credit card page.
Update field
New product
Value Entered:
Mouse clicks.
Mouse clicks.
Mouse clicks.
Mouse clicks
Mouse clicks.
Mouse clicks
Mouse clicks.
Mouse clicks
Mouse clicks.
Expected Result: The column names for each product is expected to have every word
separated by an underscore for example (First_Name).This naming convention is used to
enable the users to understand the various the functionality of various fields in each
product.
Observed Result: The observed result was same as the expected result.
Test Passed / Failed: The test was successful.
Page 38 of 48
Modesto Bank
Modesto Bank System Requirements Documentation
533581666
Test Condition Id: 3.7
Version: 1.3
Save Date: 3/8/2016
Tester: subathra
Requirements Addressed: User interface/usability
Test Objective: Test conducted for the aesthetics feature of each product.
Data Field:
Login page.
Money market page
Mortgage page
Certificate of deposit page
Credit card page.
Update field
New product
Value Entered:
Respective passwords.
Mouse clicks.
Mouse clicks.
Mouse clicks.
Mouse clicks.
Mouse clicks.
Mouse clicks.
Expected Result: All the products are required to be consistent in appearance and a trade off
between the loading time and aesthetics is considered for all the products developed by the
team.
Observed Result: The lodging time for all the pages were very minimal except the login
page ( which was required to cross check data between a database and user entered values)
Test Passed / Failed: The test was successful
Page 39 of 48
Modesto Bank
Modesto Bank System Requirements Documentation
533581666
Test Condition Id: 3.8
Version: 1.3
Save Date: 3/8/2016
Tester: subathra
Requirements Addressed: User interface/usability
Test Objective: Test conducted to explain the format of entry in each data field for the users
Data Field:
Login page.
Money market page
Mortgage page
Certificate of deposit page
Credit card page.
Update field
New product
Value Entered:
Respective passwords.
Data.
Data.
Data.
Data.
Data.
Data.
Expected Result: The interface is expected to balance the requirement of both the novice
and experienced users by displaying the format for entry of data in all the products.
Observed Result: The interface developed by the team displayed the format for entry of data
in each field in all the products
Test Passed / Failed: The test was successful.
Page 40 of 48
Modesto Bank
Modesto Bank System Requirements Documentation
533581666
Test Condition Id: 3.9
Version: 1.3
Save Date: 3/8/2016
Tester: subathra
Requirements Addressed: User interface/usability
Test Objective: Test conducted to crosscheck between user experience and the interface
development for each product.
Data Field:
Login page.
Money market page
Mortgage page
Certificate of deposit page
Credit card page.
Update field
New product
Value Entered:
Respective passwords.
Mouse clicks.
Mouse clicks.
Mouse clicks.
Mouse clicks.
Mouse clicks.
Mouse clicks.
Expected Result: The interface is expected to balance the requirement of both the novice
and experienced users.
Observed Result: The observed result was same as the expected result.
Test Passed / Failed: The test was a success.
Page 41 of 48
Modesto Bank
Modesto Bank System Requirements Documentation
533581666
Test Condition Id: 4.1
Version: 1.3
Save Date: 3/8/2016
Tester: subathra
Requirements Addressed: Use scenario
Test Objective: Test conducted to explain the result of data entry when a correct format of
data entry was used
Data Field:
Login page.
Money market page
Mortgage page
Certificate of deposit page
Credit card page.
Update field
New product
Value Entered:
Respective passwords.
Data.
Data.
Data.
Data.
Data.
Data.
Expected Result: The interface is expected to use the data ( in the correct format
only)provided by the users and produce appropriate result to let the user know the changes
that were made.
Observed Result: The interface produced a message confirming the entry of a new product
after processing the data provided by the users.
Test Passed / Failed: The test was successful.
Page 42 of 48
Modesto Bank
Modesto Bank System Requirements Documentation
533581666
Test Condition Id: 4.2
Version: 1.3
Save Date: 3/8/2016
Tester: subathra
Requirements Addressed: Use scenario
Test Objective: Test conducted to explain the result of data entry when an incorrect format
of data was used.
Data Field:
Login page.
Money market page
Mortgage page
Certificate of deposit page
Credit card page.
Update field
New product
Value Entered:
Respective passwords.
5/89/2005
5/89/2005
5/89/2005
5/89/2005
5/89/2005
5/89/2005
Expected Result: The interface is expected to let the user know the correct data format ( in
add new product section only) for each field in an eye-catching font color.
Observed Result: The interface produced a error message requesting data entry in the
special format
Test Passed / Failed: The test was successful.
Page 43 of 48
Modesto Bank
Modesto Bank System Requirements Documentation
533581666
Test Condition Id: 4.3
Version: 1.3
Save Date: 3/8/2016
Tester: subathra
Requirements Addressed: Use scenario
Test Objective: Test conducted to explain the result of data entry when an inappropriate data
was used.
Data Field:
Login page.
Money market page
Mortgage page(APR))
Certificate of deposit page
Credit card page.
Update field
New product
Value Entered:
Respective passwords.
5/89/2005
5/89/2005
5/89/2005
5/89/2005
Expected Result: The add feature is expected to request the user for appropriate data
whereas the update method is not fully equipped to handle this kind of situation .The team
has decided to incorporate this feature in the future versions of the project
Observed Result: the observed result was same as the expected result
Test Passed / Failed: The test was successful.
Page 44 of 48
Modesto Bank
Modesto Bank System Requirements Documentation
533581666
Test Condition Id: 4.4
Version: 1.3
Save Date: 3/8/2016
Tester : subathra
Requirements Addressed: Use scenario
Test Objective: Test conducted to check the behavior of the interface when a unfilled or
partially field form is submitted
Data Field:
Login page.
Money market page
Mortgage page
Certificate of deposit page
Credit card page.
Update field
New product
Value Entered:
Respective passwords.
Data.
Data.
Data.
Data.
Data.
Data.
Expected Result: The interface is expected to request the users to fill in all the data before
submitting the form.
Observed Result : A message appeared requesting the users to fill all the data fields
Test Passed / Failed: The test was successful.
Page 45 of 48
Modesto Bank
Modesto Bank System Requirements Documentation
533581666
Test Condition Id: 4.5
Version: 1.3
Save Date: 3/8/2016
Tester: subathra
Requirements Addressed: Use scenario
Test Objective: Test conducted to check the links for different products form a single
product
Data Field:
Login page.
Money market page
Mortgage page
Certificate of deposit page
Credit card page
Update field
New product
Value Entered:
Mouse click
Mouse click
Mouse click
Mouse click
Mouse click
Mouse click
Mouse click
.
Expected Result: The interface is expected to request the users to fill in all the data before
submitting the form.
Observed Result : A message appeared requesting the users to fill all the data fields
Test Passed / Failed: The test was successful.
Page 46 of 48
Modesto Bank
Modesto Bank System Requirements Documentation
533581666
Test Condition Id: 5.1
Version: 1.3
Save Date: 3/8/2016
Tester: subathra
Requirements Addressed: Security features.
Test Objective: Test conducted to check the special features offered only to managers
Data Field:
Login/password
Login /password
Login /password
Login /password
Login /password
Value Entered
Wuewiueow
Wieiowioqeuoi
29893982398
null
kdhhfh
.
Expected Result: Different sets of permissions are granted based on the user id. Senior
mangers are allowed to view and make changes to the fields of the products whereas some
managers are granted permission only to view the products.
Observed Result: The observed result was same as the expected result when the user id
matched the senior manager or manager.
Test Passed / Failed: The test was successful.
Page 47 of 48
Modesto Bank
Modesto Bank System Requirements Documentation
533581666
Version: 1.3
Save Date: 3/8/2016
15 Potential Improvements
The following functions could be improved in the current information system as future enhancements:
1. Security.
In the current system, even if a user should login with an appropriate username and password in order
to get into the bank intranet site, the site is not completely secure. For instance, if a user copies and
pastes the url of one of the manager pages, she/he can go to the same page without login. This problem
should be prevented with using cookies or session variables.
2. Data validation
In the current system there is data validation for numeric and date fields for all adding pages, but not
for the updating pages. Data validation should be added throughout for all the updating pages in case a
user makes a mistake during the updating process.
3. Page Index Function
If there is the page index function in the table view page, the search from dropdown menu does not
behave appropriately. For instance, when a user views the all product and goes to the second page, a
user can not select any other options from dropdown box. With this problem, the page index function
was removed from the current system.
4. Sort Function
For the column-by sort function, we had to select the exact same table column names as the database.
If we named the column name differently for user friendly purpose, the column-by sort does not
function appropriately.
Page 48 of 48