Description
Pick an application here from one of the areas https://www.my.gov.sa/wps/portal/snp/content/appsltCollege of Computing and Informatics
System Integration
IT440
PROJECT
Deadline: Sunday 13/02/2023 @ 23:59
[Total Mark for this Assignment is 14]
Student Details:
Name:
Name:
CRN:
ID:
ID:
Instructions:
• This project must be submitted on Blackboard (WORD and pdf format) .
• Email submission will not be accepted.
• You are advised to make your work clear and well-presented; marks may be reduced for poor
presentation. This includes filling your information on the cover page.
• You MUST show all your work, and text must not be converted into an image, unless specified
otherwise by the question.
• Late submission will result in ZERO marks being awarded.
• The work should be your own, copying from students or other resources will result in ZERO marks.
• Use Times New Roman font for all your answers.
14 Mark
Pg. 01
Instructions
• Each group can have a minimum of 3 and a maximum of 4 students.
• Govt. of Kingdom is providing hundreds of services to its people. The list of these
services and applications are available on the following link:
https://www.my.gov.sa/wps/portal/snp/content/appslist, a list of application areas
is as under:
•
•
•
•
Government sectors that have launched applications for mobile devices
1. Healthcare Sector
2. Education and Training Sector
3. Security and Safety Sector
4. Business Sector
5. Trade and Consumer Protection Sector
6. Human Resource Sector
7. Municipal Services and Housing Sector
8. Environment, Water and Agriculture Sector
9. Industry, Mineral Resources and Local Content Sector
10. Justice and Legal Affairs Sector
11. Financial Sector
12. Tourism and Travel Sector
13. Islamic Affairs Sector
14. Telecom Sector
15. Media and Culture Sector
16. Sports and Entertainment Sector
17. Charitable and Voluntary Sector
Pick any of the application from above listed areas
In your group, propose a refinement or adding new requirements in to enhance a
running any one of the Application provided above.
Formulate these refinements as a case study. Your project scenario should be
approved by your instructor.
After selecting your challenging IT project, perform the following tasks. Then submit
your answers in a form of:
1- IT technical report (10 marks). Please use the proposed report template.
2- Presentation (4 marks). Please use the proposed presentation template.
Think of the report and the presentation will be for your organization decision
makers (IT directors, Business managers, …).
IT Project Title:
Case Study Overview:
Pg. 02
Task One
Learning
Outcome(s): 2.2
2 Marks
• Select the Application from the list, collect the requirements using brainstorming,
or any other requirements collection techniques, come up with a set of unique
defined functional requirements (minimum 2) and a set of non-functional
requirements (minimum 3).
• Write the collected requirements in a form of English form using (Shall
statements).
• Prioritize and rank these requirements in terms of their importance to the
customers’ needs.
• Deliver the requirements in the form requirement specifications.
Pg. 03
Task Two
Learning
Outcome(s): 3.1
.
3 Marks
DevOps is now the project development practices that guarantee good quality, fast
product delivery and efficient system integration.
• Find research paper about DevOps practices and use the paper suggested method to
create your IT project DevOps plan and strategy.
• To make your strategy works also find suitable DevOps automated tools. List them
in tables with a brief description of each tool.
Adapt your selected DevOps strategies, methods, and tools suitable for your project
process. Mention the paper reference in the report.
Pg. 04
Task Three
Learning
Outcome(s): 2.3
,3.1
2 Mark
From the suggesting requirements, create the test scenarios that will be used for
system test and system integration test.
• Formulate the scenarios in a table with assessment metrics and prioritizing
techniques.
Pg. 05
Report Template
Learning
Outcome(s):
10 Marks
The submission Format for the Technical Report:
1. Executive Summary (1 mark)
2. The project Scope (1 mark)
2.1 The problem identification
2.2 The objectives
3. Task1: The requirement Specification (2 marks)
4. Task2: The Project Strategy (3 marks)
5. Task3: The System Integration Test Specification (2 marks)
6. Conclusion & Lessons Learned (1 mark)
Note: The work should be your own using the tool, copying from students or
other resources will result in ZERO marks in whole project.
System Analysis And Design project (Orders
of Stitching uniforms)
T. Ashwaq Aldossari
By
Jwaher Aljebreen – 14-116445
Tokka Mohammed – 140144256
Nawal Alghamdy – 140110201
CRN 11207
Dec 2016
Planning phase : Project Identification
Student information
Jwaher Aljebreen
ID: 140116445
CRN: 11207
Tokka Mohammed
ID: 140144256
CRN: 11207
Nawal Alghamdey
ID: 140110201
CRN: 11207
Requirements
System for stitching uniform provides following services:
1.customer order: customer can make order, exchange and
return uniform.
2.buy uniform: Customer ask the sales person for a product
and then the user specify on the system the
• Kind of uniform
• fabric and colors
• Number of pieces
• Sizes
• Delivery date (output)
Receipt (output)
3.Exchange uniform:
If the delivery product is not corresponding to what customer
request, then system must allow for exchange then the
employee will inter to the system
• Receipt
• Adjustment
• Delivery date
4.return uniform: one condition:
• Manager approval request.
Then the system must allow for return then the
employee will enter to the system
• receipt
• Refund with take 20% for the company effort.
5. customer delivery: customer accepts the order, and we
have two cases if he wants to make changes or return the
uniform, then enter customer feedback.
6.manager order:
manager receives sales reports and track work flow and
allows validations.
7. factory order:
factory sends completion notifications to the system, and
sends report to the manager.
Planning phase: Feasibility Analysis
Introducing the benefits and the risk that associated with the project. The current system is
manual and new system is computerized so, there will be benefits and risks which will be
determined as following:
Technical feasibility:
to discuss the and answer the question “Can we built it?” the following points considered to
measure the risks:
1- Familiarity with the application: the development team (IT team)- that the organization
hired – are familiar with the applications and fully understand the environment of company
and the needs that system has to meet. the users of the new system (employee and
managers ) are understand what the system will do and how it respond and they will need 4
weeks training in order to use and handle the new system and its technical equipment
(hardware & software) effectively and efficiently .
2- Familiarity with the technology: the development team are familiar with the technology
that will be used to generate and apply the new system they will use java language to
develop the program and implement it, and they will need PCs with windows 10 along with
its devices such as mouse, keyboards and HP printers, to use it as environment to the new
system. also they will need to build network infrastructure and they will use servers inside
the company. meanwhile company staff must be teaching and training how to use and
interact with the system.
3- Project size: the project size is reasonable. there is no complexity. requirements are clear
and the system has specific countable functions to perform. and there is compatibility
between the number of development team member and the time that required to
complete the project.
4- Compatibility between the new system and the existing technology: basically the
organization doesn’t have technology since it has been using manually system.
So back to the question, yes we can build but with high potential risks: the time required to
train company’s staff and managers. the cost required to provide technical environment
including technical devices such as PCs servers. etc. but the revenue to the company is
worth it and that’s explain in detail as the following:
Economic feasibility: To Identifies The financial risks and answer the question “should we
built it “. There are estimated costs shown below:
Identify
costs
and
benefit
& assign
values
to costs
and
benefits
Developmen
t costs
Operational
costs
Total costs
Tangible
benefits
salaries
Hardware &
software expenses
Consultant fees
Office spaces and
equipment
300000
400000
20000
50000
Salaries for operation
staff
Software license
& fees
User
Training
Communication
charges
300000
20000
20000
50000
1340000
Reduce operational costs by 60%
Increase operational speed to 40%
Intangible
benefits
Communicate with customers and
measure satisfactions
Improve product quality
Item
Estimate
profits
and
benefits
per
month
Previous monthly
expenditure
Proposed monthly
expenditure
Amount cut down
monthly
40000
300000
40000
5000
150000
10000
35000
150000
30000
380000
165000
183500
Paper work
Salaries
Customer
complains
Total
present
value per
year
Total profits
Total expenses
PV
Estimate
benefits
cash
flow
Manual system
500000
208500
291500
Computerize system
11500000
1914550
9585450
2016
2017
2018
2019
120000
170000
220000
300000
500000
520000
580000
700000
70000
30000
100000
73000
30000
100000
76000
30000
100000
79000
30000
100000
User training
200000
50000
30000
200000
50000
30000
200000
50000
30000
200000
50000
30000
Hardware & software
400000
10000
10000
10000
Break-Even Point
Net Present Value
7 months
Total benefits – total expenses
1345000- 1340000=50000>0
Reduce operational costs
Increase sales
Increase operational speed
Reduce error rate
Reduction in organization staff
Salaries
Costs
Reduce error rate
Increase sales to
to 5%
70%
Reduction in
organization staff
by 20%
Easier work progress supervision for
managers
Increase brand recognition
Communication charges
Organizational feasibility:
To determine how well the new system ultimately will be accepted by its users and incorporate
into the ongoing operations of the organization. And to state how well the project goals align
with business objectives. from an organizational perspective this project has low risk.
1- all organization departments are collaborating and providing the development team with the
information and that would be helpful & useful to the project.
2- the top executive of the company have a strong interest in the project, and the project
champion. Ahmed Khalid is initiate and promote the project and willing to provide the time &
resources to the project and create a prototype to demonstrate the project value.
3- the project users will be asking constantly to provide their feedback during project
evaluation.
4- management may have concerns regarding the time delay for training company’s staff.
Planning Phase : Methodology used for development
According to obtain the approval committee and business value that confirmed by feasibility
study for the project based on technical, organizational and economic feasibilities, and
providing new services with high quality for community diversity, and duo to:
1.
2.
3.
4.
5.
the project size is reasonable.
there is no complexity.
requirements are clear.
the system has specific countable functions to perform.
there is compatibility between the number of development team member and the time
that required to complete the project.
then we will use Iterative methodology for the project duo to it is very accommodate with
the project requirements:
Planning Phase : Work plan: Gant chart
Analysis phase : Determine main business requirements
1) Main business requirement:
Functional requirement:
1- Customer order:
1.1- The system will allow customer to make request and select a fabric type, fabric
color, custom style, sizes, the quantity to purchase. the system will produce receipt
with ID contains details about the customer request.
1.2- The system will allow customer to exchange his request (by receipt) with fees.
1.3- The system will allow customer to return the uniform (by receipt) with fees.
1.4- The system will deliver the uniform to the customer, accept the payment and take
his feedback.
2- Manager order:
2.1- The system will allow manager to track data flow and validate customer requests for
exchange or return
2.2- The system will generate sales report to the manager.
3- Factory order:
3.1- The system will allow factory accept customer request and inform him after
completion to deliver the custom.
3.2 – The system will allow factory to request for fabric lack.
Nonfunctional requirements:
1- Operational:
1.11.2-
The system should run on tablet PCs to be used by salespeople.
The system should connect to printer wirelessly.
2- Performance:
2.1-The system should support a sales staff of 30 salespeople.
2.2-The interaction between system and user should not exceed 3 second.
3- Security:
3.1- No salesperson can access any other salesperson’s customer contact.
3.2- Only sales manager can approve and accept and validate any customer order.
4- Cultural and political:
4.1- Company policy says that all computers equipment should purchase from ASUS.
4.2-personal information should be protected in compliance with the data protection Act.
Analysis phase : Create use cases
Use case name: customer order
ID: 1
Important level: 1
Primary Actor: customer
Short Description: use case describe the customer requests
Trigger: customer request
Type: external
Major input:
Major output:
Description
Source
Description
Destination
1- order
1- customer
1- make order
1-buy use case
2- change order
2- exchange
3-return order
use case
3- return use
case
Information for Steps
Major Steps Performed
1- Customer make order
order
1.1- customer want to buy uniform
make order
1.2- customer want to exchange uniform
change order
1.3-customer want to return uniform
return order
Use case name: buy uniform
ID: 2
Important level: 1
Primary Actor: customer
Short Description: use case describe how to purchase the uniform
Trigger: customer want to purchase uniform
Type: external
Major input:
Major output:
Description
Source
Description
Destination
1. Customer
1. customer
1. Receipt
1. Customer
information
2. customer
2. Update data
2. Data store
2. Uniform detail
store
Information for Steps
Major Steps Performed
1- Enters customer information
Customer information
• Customer name
• Customer phone
2- Customer selects product details:
• quantity
• style
• color
Uniform details
• fabric
• size
Receipt
3- customer take the uniform receipt
Update inventory
4- Data story will be update
Use case name: Exchange uniform
ID: 3
Important level: 1
Primary Actor: customer
Short Description: use case describe how to exchange the uniform
Trigger: customer want to exchange uniform
Type: external
Major input:
Major output:
Description
Source
Description
Destination
1- Old Receipt number
1- Customer
1- Fee amount
1- Customer
2- Product changes
2- Customer
2- Fee payment
2- Customer bank
3- Fee count
3- Exchange
3- New receipt
account
4- Manager approved
4- Exchange
4- Manager feedback
3- Customer
request
5- Manager approved
4- Data store
6- Manager not approve 5- Customer
7- Update data store
6- Customer
7- Data store
Information for Steps
1- inters old receipt number to system
to provide product information
2- Customer selects changes for
uniform
3- Send to the manager approved
request,
if manager don’t approved end use
case, if he approved go to next step
(his feedback will be saved in the data
store):
3.1- request manager approved will
obtain manager feedback from data
store and will send to customer.
3.2- checks fee of changes : request
to count fee amount from fee file .
3.3- fee file will count and send fee
amount to customer.
3.4- customer accept to pay fee.
4.5 – withdraw fee amount from
customer bank account .
4- give the customer new receipt
Major Steps Performed
Old Receipt
Receipt description
Uniform details
Manager feedback
Manager approved
Manager not approve
Count fee
Fee amount
Fee payment
New receipt
4- Update date store
Data store
Use case name: return uniform
ID:4
Important level: 1
Primary Actor: customer
Short Description: use case describe how to return uniform
Trigger: customer want to return uniform
Type: external
Major input:
Major output:
Description
Source
Description
Destination
1. Receipt
1. Customer
1. Manager feedback 1. Data store
2. Manager approved
2. Customer
request
2. Customer
request
3. Fee file
2. Fee amount
3. Bank account
3. Fee count
4. Customer
3. Fee payment
4. Bank account
4. Deposit money
5. data store
5. Update data store
Information for Steps
1. enters receipt number to provide receipt
product information
2. Send to the manager approved request,
if manager don’t approved end use case, if
he approved go to next step his feed (his
feedback will be saved in the data store):
2.1 request manager approved will
obtain manager feedback from data
store and will send to customer.
2.2 checks fee of return : request to
count fee amount from fee file .
2.3 fee file will count and send amount
to customer
2.4 deposit money after taking fee
amount
Major Steps Performed
Receipt
Manager approved request
Manager feedback
Fee amount
Fee payment
Deposit money
3. Update data store
Update inventory
Use case name: customer delivery
ID: 6
Important level: high
Primary Actor: customer
Short Description: use case describe the uniform delivery to customer
Trigger: the customer want to take the uniform that he requested
Type: external
Major input:
Major output:
Description
Source
Description
Destination
Price
Customer
Completion
Customer
Feedback request
Manager
notification
Change request
Customer
Sold uniform report
Data store
Return request
Customer
Payment
bank account
Order Completing
factory
Customer feedback
Data store
Change uniform
Exchange use
case
Return uniform
Return use
case
Information for Steps
Major Steps Performed
1- the system will send notification for
Completion notification
completing order to customer and
Price
price of the order to pay .
2- customer pay .
Payment
3- The system asks the customer for his
Feedback
feedback.
4- The system will send customer
Sold uniform record
feedback and sold uniforms report to
Customer feedback
data store .
5- There is a chance that customer want
to return or exchange his order
Change uniform
Return uniform
Feedback record
Use case name: manager order
ID: 7
Important level: 1
Primary Actor: manager
Short Description: use case describe the how the manager supervise business progress
Trigger: manager
Type: external
Major input:
Major output:
Description
Source
Description
Destination
Track work flow
Manager
Generating sales
Data store
Validation
exchange or return report
Use case
Validation
Return and
exchange
usecase
Information for Steps
1-The system will send customer
receipt to the manager and
generate sales reports
2–manager can track work flow
and validate any customer order
Major Steps Performed
Generate sales report
Track work flow
Validation
Use case name: factory order
ID: 8
Important level: 1
Primary Actor: employee in the factory
Short Description: use case describe the completion of customer order and inform for
fabric lake
Trigger: completion of the order and lake of fabric
Type: external
Major input:
Major output:
Description
Source
Description
Destination
1- receipt number
1- employee
1- order
1- customer
completion report delivery use case
2- fabric report
2-data base
3- fabric lack
3-manager
Information for Steps
Major Steps Performed
1- factory complete the order and send
receipt number
notification to the system of completion
orders
2- factory send report to the manager that
order completion report
there is lake of fabric
fabric report
3- factory send report of work , orders and
fabrics.
Analysis phase : model process Data Flow Diagram
Context Diagram
Level Zero
Level 1
Level 2 : Exchange
Level 2 : Return
Analysis phase : model data (ER modeling)
Design phase : Create Architecture Design
1) Architecture design
Now we should take a strong step regarding to the type of architecture design, we focus in the system
needs depends on nonfunctional requirements as following;
1-Operational Requirements:
Operational requirements specify the operating environment in which the organization system
must perform and how those may change over time.
1- technical environment requirement;
The system will be work over web environment with internal and external networks, the
organization will use network to contact with inventory, and to enable real time database
updates, we need ASUS computers with mouse, keyboards and HP printers, also we need
internal network within company and its branches, and external network between company
and its suppliers and aliens.
2-system integration requirements;
The system must be able to import and export important information quickly and
provide report about inventory and product status, to ensure that the system interact
and connect with other systems in a good way. We will use PC and portable devices to
support all branches with computers that they need.
3-Portability Requirements;
The system must deal with suppliers’ and allies` factory to export and Import raw
materials and goods, they may be used different operating system then we need system
able to work and communicate with different OS that located outside the company.
Then we need middleware.
4-Maintainability requirements;
Maintainability requirements may also define the update cycle for the system, such as the
frequency with which new versions will be released. In the future we need to extend
system to operate with handheld devices. To provide high customer services and
satisfaction. New versions of the system will be released every year.
2-Performance Requirement:
focus on performance issues such as response time, capacity, and reliability.
1- Speed Requirements:
How long does it take the system to respond to a request between branches and
inventory or between managers, employee, inventory and the system. While employee
entering customer requirements he will typing, dragging and dropping then the
response time should be fast and the computers speed must be within 3 seconds. And
the inventory database must be updated in real time. and the orders will be transmitted
to the factory floor every 3 minutes.
2- Capacity Requirements:
The system must be support multiple employees within organization in different
branches to interact with the system without freezing or crashing while inter orders,
reports, requests and customers’ information that need to store immediately, we need
software that store thousands of data per hour. We need database size accommodate
with more than this size. As far as reasonably fit with basic system needs of the
organization.
3-Availability and Reliability Requirements:
The system available for 24 hours and 7 days for employees from different branches to
be more reliable to contact with inventory. But the system is available for customers for
5 days and for 11 hours divided for three shifts, first shift starts at 9 AM to 1 PM, second
shift from 2 PM to 6 PM, the third shift from 7 PM to 10 PM.
3- Security Requirements:
We need for system that has ability to protect the information system from disruption and data
loss, whether caused by an intentional act or not. And Security of the system is the
responsibility of the operations group (the staff responsible) for installing and operating
security controls (firewalls), and routine backup and recovery operations. The company offers
retail services and wholesale for customers, then the system should be ensuring the privacy of
stored customer information or payment information to avoid financial losses and privacy we
will install protection programs is the last version of firewall.
1- System value estimates:
system outage is estimated to cost between 20000 per hour in all branches. Then the
organization has a proper security measures. To secure the organization’s data also.
2- Access Control Requirements:
Some of the data stored in the system need to be kept confidential, some of data
readable only by the personnel department and the employee’s supervisor; to avoid
unauthorized actions. Like confidential company information or data, such as account
numbers and information confidential staff.
3- Encryption and Authentication Requirements:
The system used A symmetric encryption algorithm (Data Encryption Standard [DES])
within organization between stuff to provide or read any order information. And use an
asymmetric encryption algorithm to private information and data about bank transfers
and financial transactions only managers have permeation to access this types of data.
4- Virus control:
to avoid destruction of data the system already installed Anti-virus software
program.
5- Cultural and Political Requirements:
The system operates in The Kingdom of Saudi Arabia and we followed the rules and polices
of the country.
1- Multilingual Requirements:
the system available for two languages Arabic and English
2- Customization Requirements:
capture country-specific information about what they are prefer and based on what is
compatible with religion and tradition with additions commensurate with product.
3- Unstated Norms:
user interface designed to compatible with employee to easy usage and deal with
4- Legal Requirements:
we focus in the government’s legal regulations that compatible with the organization`s
system,
finally, after provided all nonfunctional requirements in details we decided to use the
architecture that fit with many nonfunctional requirements it is; Server Based Architecture
specifications of hardware and software:
•
Operating system
•
Windows 10
•
Special software
•
•
Microsoft suit
Java application
•
Hardware
•
•
•
•
•
250-GB disk drive
Intel®-Core i3-2100 dual core
processor
19-inch LCD Monitor
ASUA computers
HP printers
•
•
Always-on Broadband, preferred
Dial-up at 56 Kbps.
•
Network
The architecture team decided that the only components that needed to be acquired for the
project were a server Host (mainframe computer) to store data and access and retrieve it also
for application and presentation logic, a Web server, and 100 new computers include its mouse
with 40 HP printers. They developed a hardware and software specification for these
components, prepared an RFP, and worked with the purchasing department to acquire the
hardware and software.
Design phase : Interface structure design
0
System
authentication
1
System main menu
4
Factory
3
customer
2
manager
4.1
Customer
orders
4.2
Order delivery
4.3
Factory
report
3.1
Buy product
3.2
Exchange
3.3
Return
3.1.1
Customer info
1.1.4
3.2.1
Enter receipt
number
3. 1.2
Select uniform
details
3.2.2
Select changes
3.3.2
Manager
approval
3.1.3
Print receipt
3.2.3
Manager
approval
3.3.3
Fee amount
3.1.4
Order delivery
3.2.4
Fee amount
3.1.5
Payment
3.2.5
Order delivery
3.1.6
Feedback
3.2.6
Payment
3.2.7
Feedback
3.3.1
Enter receipt
number
3.3.4
Return money
2.1
Track workflow
2.2
Manager
approval
2.3
Sales report
2.4
Factory
report
Design phase : Database specification
Selecting a Storage Format depending on :
Data Type : the data type that will need to be stored in the system application is simple
data type (text , dated and numbers ) that will be applied in : customer information as his name
and his number . date of deliver product .receipt number . fabrics names and numbers .
uniform or model name , type and number . prices and fee amount .
Type Of Application System : the system has to accept and process many simultaneous
request such as customer order to purchase , change and return as well payment process and
others . so the system will use transaction processing system which need data storage format
that are tuned for a lot of data updates and fast retrial of predefine. Also the system will
support decision making such as business intelligence : management information system to
support decision makers who need to examine large amount of historical data to take decision .
Existing Storage Format : the existing format is physical files contain all company data
that typed manually .
Future Need : considering the trends and technology that are being used by other
companies . so the storage format should be “safe” when large amount of installation and
updating is done .also it preferred to be easy and less expensive format .
So, considering all above system storage format needs the best format choice will be
relational DBMS .
Project team construct this table to be more certain form the storage format that the
system need :
Data
Type
Customer Information Simple ( mostly text)
Factory Information
Simple (text mostly) fabrics name ,
Use
Transaction
Transaction
Suggested Format
Relational
Relational
Transaction
Transaction
Transaction
Relational
Relational
Relational
model number.. etc.
Order Information
Payment
Sales Information
Simple ( mostly text)
Simple ( mostly text, integers)
Simple ( mostly text, integers)
Design phase : physical ER modeling
Please open the link below to have clearer picture
https://drive.google.com/file/d/0B6H6FTRI9XU8M0NBVXBUQ2lVb2s/view?usp
=sharing
System Integration
College of Computing and Informatics
IT 440
Project Presentation
[10 marks for the project report and 4 Marks for Presentation, total mark is 14)
Title:
Student Details:
CRN:
Name:
ID:
Name:
ID:
Name:
ID:
Use of Template
Use the same template, however you can mention the headings and
content of your choice.
Introduction
Problem Identification
Scope
Objectives
Requirement Specifications
Requirement ID
Requirement
Functional requirements
Priority
Rank
Requirement Specifications (cont.)
Requirement ID
Non-functional requirements
Requirement
Priority
Rank
DevOps Strategy
DevOps Tools
Automated tools
Tool
Description
DevOps Adaptation Plan
Test Scenarios
Test
scenario
No
Requirement
Test scenario
ID
description
Test cases
Test Scenarios (cont.)
Test Scenarios (cont.)
Test Scenarios (cont.)
Assessment metrics and prioritizing techniques.
Test
No of
No of
scenario
test
passed
No
cases
test cases
Cost of
No of failed
No of critical
test cases
bugs
Test design efficiency finding the
defect
Priority
Integration Test Plan
Integration Test Plan (cont.)
Lesson Learned
Conclusion
Thank You
Purchase answer to see full
attachment
