AssignmentDetails_2_8_2016 (2).pdf For this assignment, complete the following steps:Write a research paper of 3–4 pages (cover and references pages not included in page count) that details the design and layout characteristics of Android phone applications.Specifically describe the design process for an Android phone application.Include a discussion of the role of Extensible Markup Language (XML) in the design process and how XML is used in the Android application files.Discuss the best practices and also the problems and solutions regarding design, layout, performance, compatibility, and security.Explain the difference between a light and a heavy layout and how they both relate to overall performance.unit_1_ip_by_sherry_l_cooper_beck.docx7:41 AM (CST)
Unit 1 – Individual Project
Assignment Overview
Go To:
Type: Individual Project
Unit: Introduction to Mobile Applications
Due Date: Sun, 2/14/16
Grading Type: Numeric
Points Possible: 125
Points Earned: 0
Deliverable Length: 3-4 pages (not including cover and references pages)
Assignment Details
Learning Materials
Reading Assignment
My Work:
Online Deliverables: Submissions
Assignment Details
Assignment Description
For this assignment, complete the following steps:
1. Write a research paper of 3–4 pages (cover and references pages not included in page count) that details the design and layout characteristics of Android phone
applications.
2. Specifically describe the design process for an Android phone application.
Include a discussion of the role of Extensible Markup Language (XML) in the design process and how XML is used in the Android application files.
3. Discuss the best practices and also the problems and solutions regarding design, layout, performance, compatibility, and security.
4. Explain the difference between a light and a heavy layout and how they both relate to overall performance.
Please submit your assignment.
This assignment will also be assessed using additional criteria, provided here.
For assistance with your assignment, please use your text, Web resources, and all course materials.
Reading Assignment
Meier, Chapters 1, 2, and 3
Assignment Objectives
Identify characteristics of mobile applications
Design and develop a Web application targeted for a mobile device
Other Information
There is no additional information to display at this time.
Legend
Extra Credit
View Assignment Rubric
Assignment Details
Assignment Description
For this assignment, complete the following steps:
1. Write a research paper of 3–4 pages (cover and references pages not included in page count) that details the design and layout characteristics of Android phone
applications.
2. Specifically describe the design process for an Android phone application.
Include a discussion of the role of Extensible Markup Language (XML) in the design process and how XML is used in the Android application files.
3. Discuss the best practices and also the problems and solutions regarding design, layout, performance, compatibility, and security.
4. Explain the difference between a light and a heavy layout and how they both relate to overall performance.
Please submit your assignment.
This assignment will also be assessed using additional criteria, provided here.
For assistance with your assignment, please use your text, Web resources, and all course materials.
Reading Assignment
Meier, Chapters 1, 2, and 3
Assignment Objectives
Assignment Objectives
Identify characteristics of mobile applications
Design and develop a Web application targeted for a mobile device
Other Information
There is no additional information to display at this time.
Legend
Extra Credit
View Assignment Rubric
Privacy Statement
Terms and Conditions
© 2015 American InterContinental University.
All Rights Reserved. Authorized Users Only.
Contact Us
Running Head: ANDROID
1
ITSD427 Android Phone Applications
Sherry L. Cooper Beck
February 2, 2016
ANDROID
2
Project Information
Description
This is a project for system integration of Jumi Mall which has main branch in
Washington, DC at United States of America. Jumi Mall has started to expand to all over the
world by create more braches. Currently the mall is facing a problem with their systems since
they are not integrated. Mall branches have started operating although they do not a suitable
integrated system.
Jumi Mall has web based systems, window based systems and smart device applications
which are not integrated to form a single system. The systems are not linked hence posing a
problem when tracking transactions.
New offices systems have not yet been integrated to the main branch system. This forces
customers to visit main branch in case they have a problem.it concern that the branches do not
contain useful information from other branches due to lack of system integration.
Project objectives
To form a single system which carries complex tasks .different units and components will be
integrated to carry complex tasks with minimal interaction from user.
Another objective is to increase usability of the system and achieving users’ goals by
optimization of the system. Output from one software output maybe an input of another software
unit and therefore system integration will allow software units to communicate and pass data to
each other without the need of user (Shen et al., 2012).
ANDROID
3
To have shared resources such as data by having a single database this provides all
applications with data. Data from different parts of the system will be available during
organizational decision making which is important by having shared resources.
To have a manageable system which can be easily be maintained instead of many different
systems that cannot be easily maintained.
To make sure systems from different office blocks communicate to achieve a certain goal
such as data storing and retrieving, that is, making sure all system form a single logical system
which can be used to manage Jumi Mall.
To provide best services to the Jumi Mall customers by having an integrated system that
meets their needs.
To minimize data loss and data anomaly in Jumi Mall by having an integrated system
chances of data loss will be reduced. Data anomalies will be avoided by making sure the system
performs and behaves as required (Shen et al., 2012).
Goals of the project
The project will ensure Jumi Mall has an integrated system that carries complex tasks
with minimal interaction to the user.
The integrated system will ensure there is no data loss in the system. it will be easy to
manage data in one integrated system than in multiple systems.
Data anomalies will be eliminated. Data access controls will be implemented to ensure
only accurate data is kept and without losing important information. Data redundancy will be
eliminated to ensure the system uses consistent data and other resources.
The system will ensure Jumi mall customers receive best services by having a system that
meets their needs.
ANDROID
4
Due to shared resources such as data Jumi Mall will be able to keep track of transactions
easily. The integrated system will also produce real time accurate reports used to make
managerial decisions.
The integrated system will link Jumi Mall main branch and other sub braches for easy
control and access of same services from different areas or branches.
Major systems
Jumi Mall has designed various applications in order to serve its wide range customers. The
mall has the following major systems:
➢ Web application
➢ Window based application
➢ Smart phones application
➢ Database management system
➢ Control server
This list may change after further analysis is completed.
Boundaries of the project
For system integration to occur there must be existing software units, components and
other related software and hardware needed in the system and therefore we shall integrate
existing software units and components to form a single system. Some units and components will
be modified where necessary to fit in the final system.
Jumi Mall has web applications, windows application and other smart devices
applications, which will be integrated to share same resources such as data from same
ANDROID
5
database.in other words, the project will not create new system units and components but it will
integrate the existing ones.
Project Plan
Work breakdown structure (WBS)
The project shall contain the following main activities:
•
Requirements definition
•
Requirement analysis-component and subsystem specifications
•
Stakeholder agreement on requirements and signing the project charter
•
Component check out for integration entry
•
Tracking integration process
•
Continuous testing
•
Mission thread and stress testing
•
acceptance testing
•
project sign off
Completion dates
The following is a Gantt chart which shows time to be taken for each activity. The project
will start on 3rd January 2016 and it will at 6th February 2016.
Task /Date
3rd to
7th to
10th to 14th to
17th to
21st to
24th to
28th
4th to
6th Jan
9th Jan 13rd
16th
20th
23rd
27th
Jan to
6th
2016
2016
Jan
Jan
Jan
Jan
Jan
3rd
Feb
2016
2016
2016
2016
2016
2016
ANDROID
6
Feb
2016
Requirements
definition
Requirement
analysiscomponent
and
subsystem
specifications
Stakeholder
agreement on
requirements
and signing
the project
charter
Component
check out for
integration
entry
Tracking
integration
process
ANDROID
7
Continuous
testing
Mission
thread and
stress testing
acceptance
testing
project sign
off
Other resources required
•
Software component and units simulators used for testing and verification.
•
Tools for project management
•
Tools for tracing project progress
System Integration Best Practices
Best practices
•
Backup the existing system and its data and settings. This ensures there is no data loss in
case a fault occurs during system integration.
•
The team will have to develop integration plan to be followed during program planning.
•
The overall system will be defined as configuration items against their sub systems.
ANDROID
•
8
In each level of integration there shall be appropriate requirements, design and
verification specifications to be followed.
•
Necessary diagrams which show configuration of items and subsystems will be designed.
•
The team will have to ensure requirements, designs and specifications are maintained at
all levels of the project each team will’ be assigned a specific task with a certain time
frame.
•
Configuration Management (CM) will have to ensure the all items configurations have
integrity.
•
Have a continuous rhythm in the system integration as defined by System Architecture
Skeleton (SAS).
•
Every system component shall have to be checked prior to the system integration. This
ensures component interfaces are verified and conform to the requirements by use of
tools such simulators. Component boundaries, memory leak testing and error handling is
also checked.
•
First the subsystem integration using a written procedure is carried out prior to the actual
system integration to ensure end to end conformance and other system level capabilities
are in place.
•
System integration will be done first by use of written procedure prior to verification.
ANDROID
Systems integration architecture
9
ANDROID
10
Requirements Specifications
Process to elicit requirements
Determining software requirement is one of key issues in system development life cycle.
Requirements allow developers to execute other development phases basing their focus on them.
In this project Agile method is used to gather project requirements. The advantage of using agile
method is to ensure high quality products are delivered by promoting collaboration between
stake holders and creating incremental process which optimize the program budget.
The process involves use of questionnaires, interviews, research and other reporting
methods. Any requirement can be added to the project because agile method permits that.
Stakeholders and their roles
Jumi Mall
Jumi Mall provides any necessary resources such as funds for the projects. The mall also
provides requirements for the project.
Users
Provide necessary information used to determine requirements of the project. The also
test the system and provide feedback to the project team.
Project team
Project team ensures they deliver all products to the user as required by implementing
them. The team also offers technical support to other stakeholders such as users.
Microsoft community
In case of problems that project team cannot solve then assistance is requested from
Microsoft community. Microsoft community always offers technical support if needed.
ANDROID
11
Components and interfaces
The following are major interfaces and components:
•
Smart application interface
•
Web application interface
•
Windows application interface
•
Database components
All above interfaces shall be integrated with server allow it to process various requests.
The server allows all applications to communicated to a shared database.it also processes client
request faster from various users. This makes it have components which control and implement
the interfaces. The following are the main components of the server:
•
web component
•
smart system component
•
windows application component
•
database connector component
web component is a component in the server that will allow users who are use web based
applications to access resources from the server such data stored in the database. The
component has algorithms which ensure security in type connections such as authentication
algorithm. Users will interact direct with websites directly from their browsers. Web
application interface is responsible for translating data from web pages and sending it to the
web component through internet.
ANDROID
12
Smart system component capture data and commands send over internet from smart
applications. It enables applications from smart devices such as smart phones and smart watches
to communicate with server and other devices. Smart application interface is an interface which
sends data and commands from users’ smart devices through internet to the Smart system
component.
Windows application component allows computers with window application to send data and
commands.it acts as an intermediate between windows application and server. Windows
application interface is the interface responsible for sending data from windows application to
the windows application component in the server.
Database connector component allows server to connect with the database. The component
translates data and commands used in the database. The components will also capture data form
database to the server.
The diagram below shows how the interface and components shall be integrated.
ANDROID
13
Measurable functional requirements
The following are the functional requirements for the project:
•
The system should be reliable be able to handle errors. This requirement can be measured
by how system captures errors resulting from user input and other system errors.
•
Data integrity should be ensured to make sure only correct data is used within the system.
Data stored and underuse should be reliable to use by any process. This requirement can
be measured by how data anomaly is avoided by have concurrency control.
•
The system display should have many features as possible to allow the user to access
various parts and feature of the system. A quality system should be easy to learn
understand how to use it.
ANDROID
•
14
The system should also provide warnings on some of the hardware requirements such as
shortage of storage space in the system. Some system information is important to the user
and should be provided where necessary.
Measurable nonfunctional requirements
The following are the functional requirements for the project:
•
The system should have sufficient security to withstand any kind of attack and
provide any necessary information to the user. Security ensures system is safe from
any kind of attack. The attack can be physical and may cause business interruptions.
•
The system should have high speed perform to process all user requests within
minimal time as possible. Most of user do not like wait for a machine time because
they think it is a waste of time.
•
The system should provide user with necessary information go help him/her on how
to use it, that is, the system should have help and support features.
•
The system where the database is store should have sufficient space for data storage.
Necessary data need to be stored in the system so that it can be retrieved back for
more use. In order to ensure operation won’t stop then the system should have enough
storage space.
•
The system should be easy to service and maintain by providing the necessary
documents concerning the system. Modern hardware should be used because allows
easy upgrade and maintenance of system.
ANDROID
•
15
The system should be reliable by having feature to recover in case of a failure.
Backup is a necessary requirement for any system.it eliminates risk of permanent loss
of data. Malicious attack can delete all data in the system and therefore backup is
needed to retrieve the data as soon as possible.
Scope assumptions
The following are assumptions made on the project scope:
•
The time scheduled shall be enough to complete the system integration without any
problem.
•
We assume Jumi Mall has an existing network with sufficient bandwidth.
•
All units and components have all interfaces implement to allow easy system integration.
Pros of proceeding with the project
Proceeding with this project will have the following benefits:
•
Proceeding with this project will allow developers to create an integrated system which
will be used by Jumi Mall to perform complex task.
•
The project will also allow the team to develop a system which is easy to use. That is, the
project will increase usability of the system.
•
The project will allow creation of a system which needs minimal interaction from the
user. That is, operations will be automated where possible make it easy to operate the
system with minimal efforts.
Cons of proceeding with the project
The project also has some following disadvantages:
ANDROID
16
•
The project will need qualified personnel to back up the current system.
•
Jumi mall will also incur backup cost of the system.
•
Some of services provided by any existing system will not be offered until the final
product from the project is complete.
•
In case of an error made on the project it may cause a lot of losses on Jumi Mall.
Enterprise System Integration Analysis
Quality assurance considerations
It is important for board to ensure it uses best methods that ensure system of high quality is
developed. Quality assurance measures should be used to determine if the system produced will
be suitable for use in any environment. The board will have to consider the following during the
discussion to come up with the best method of proceeding with the system integration:
Error handling
The board will have to ensure if the method or any practice chosen will ensure errors are
handled and if possible eliminated. Every system should be able to handle any error and provide
necessary information to the user that will enable him/her to move forward with the operation.
The following are some considerations:
Recovery capabilities
In case of failure the system should be able to recover without losing user information or
data. It is import for the integrated system to recover from any error or failure.
Usability
ANDROID
17
The option selected to integrate the system should take care of usability of the system.
any practice used should produce a system which is easy to use by any user. This means the
system should be complicated for anyone to use.
Effective
System should be able to complete the intended task within reasonable time or even faster
than the user anticipation. For a system to be quality should be effective to satisfy user needs.
The board should use best practices which ensure effectiveness of a system.
Data integrity
Data integrity is very important in any system.it ensures accurate and correct data is kept in
the system. Due to many integrated components and software units, data integrity should be a
major concern. It is obvious the board should come up with a way of ensuring data integrity is
maintained in the system.
Options for considering during systems integration
There are different options that are used during system intergration.it is important to
choose an effective option to ensure the final integrated system is of high quality. Also the
option chosen should be easy to use during the actual system integration. Each method has its
advantages and disadvantages. The following are options for consideration in order to move
forward with system integration:
Point-to-point
This method uses hand coding integration, which involves moving data from one point to
another. Every app must be connected to each other in order to transfer data.
ANDROID
18
Middleware
This approach creates a layer between applications and allows the software units and
components to communicate. The middle layer receives data from different components,
translates it and then sends it to the intended receiver.
Web services
Web services allow different applications to communicate over the open protocols in the
internet. Different applications from different platforms can send data over the internet by
use of web services.
Systems Integration Approach Evaluation and Selection
Evaluation and comparison of Systems Integration Approach
The following table shows how different approaches put into priority quality assurance.
The highest priority will have a value of 1 while the lowest priority will have a value of 0. The
best approach will try as much as possible to attain priority value 1. The priority in the table is
determined by how the approach attains the quality assurance measures.
POINT-TO-POINT APPROACH
QUALITY
LOW
MEDIUM
HIGH
MEASURE
PRIORITY
PRIORITY
PRIORITY
TOTAL
Effective
0.5
Usability
0.5
Maintenance cost
0.0
ANDROID
19
Data integrity
0.0
TOTAL
1
MIDDLEWARE APPROACH
QUALITY
LOW
MEDIUM
HIGH
MEASURE
PRIORITY
PRIORITY
PRIORITY
TOTAL
Effective
1.0
Usability
1.0
Maintenance cost
1.0
Data integrity
1.0
TOTAL
4
WEB SERVICES APPROACH
LOW PRIORITY MEDIUM
PRIORITY
HIGH
TOTAL
PRIORITY
Effectiveness
1.0
Usability
1.0
Maintenance cost
0.5
Data integrity
1.0
TOTAL
3.5
The table below shows the average priority. The approach with the highest average is the
most suitable approach for this project.
ANDROID
20
AVERAGE PRIORITY
Approach
Total Priority
Average(Total/4)
Point-to-point approach
1
0.25
Middleware approach
4
1
Web services approach
3.5
0.88
Summary
Point-to-point approach is not a suitable approach for this project because has low
maintenance cost and does not care about data integrity.in case an integrated app is changed then
all other apps need to be change hence making maintenance difficult (Leznov et al., 2012).
Web services approach is a better way of system integration but it is faced by challenges
such as security since it uses internet. Web services need constant maintenance due to malicious
attacks performed on the internet.
The best approach of system integration is the Middleware approach because it produces
a system of high quality (Buede, 2011). According to the above table this approach has the
highest average priority of value 1 compared to the others.
Approach selection
Middleware approach has been selected as the best approach of system integration to
continue with in this project.
ANDROID
21
Proposed System Integration Components Architecture
Architecture of the proposed integrated system
System integration process should use the best architecture that will ensure all software
components and units are integrated and function together as required. The proposed system has
levels of components and interface which will be integrated.
The integration levels in this architecture are:
Application integration level architecture
This level involves application integrations which shall be used by user to interact with
the whole integrated system. Application such as web application, smart application and
windows applications shall have components integrated with them so that they can communicate
with the database by use of network.
Server integration level architecture
This level involves all components that form server system. Server components receive
data from all application and process their requests.in fact server acts as medium to access all
system resources.
Database integration level architecture
Database integration level has all data related components. These components processes,
store and retrieve data from the storage medium. Other components also control concurrence in
access the data.
ANDROID
22
Represent this architecture diagrammatically.
Components and interfaces to be acquired and to be developed from scratch
Most of the components and interfaces are readily available from the market and even in
Jumi mall existing system. The available components include:
•
Smart application interface
•
Web application interface
•
Windows application interface
•
Database connector component components
•
Database management component.
Other components and interface need to be developed from scratch so that the can meet the
specific system requirements.it is important to develop this kind of component to ensure
accuracy and specified behavior and functionality is attained. The following are components to
be developed from scratch:
•
web component
•
smart system component
•
windows application component
Implementation Framework
C2 Style framework
Best framework produces a system of high quality and which is acceptable by the user. In
this project we shall use the C2 Style framework which will allow best practices to be practiced.
ANDROID
23
Project framework
The C2 Style framework allows different components to be connected from top to down
approach by use connectors.in our case connectors will be used to integrated different
components and interfaces where possible. Each component has a top and bottom interface
connected to a connector then to other components. This interface allows components to send
messages to each other.
Advantages of C2 Style framework
C2 Style framework has a lot of advantages which makes it suitable for determining the
nature of the integrations in most systems. The following are the main advantages of the frame
work:
•
It allows traceability by fai0thfull mapping architectural elements and their
implementation.
•
It allows platform independence by considering the programing languages and their
communication protocol.
•
It has better way of distributing system by not assuming any single element in which the
components are going to reside.
•
It allows dynamism by allowing modification of the system with minimal effect on
existing components.
•
The framework promotes extensibility by allowing addition of more elements in the
existing system.
•
The frame work allows efficiency by making sure platform with different characteristics
and requirements.
ANDROID
24
Challenges of using C2 Style framework
The following are challenges of using C2 style.
•
The framework requires all components to be connected by connector. Use of connectors
might not be possible in some cases of system integration.
•
The framework does not give room for assumptions such as programing language used.
System Integration Implementation Plan
The following is time frame to be used in this project and resources to be used.
Start and completion dates
Activity and
1st Feb to
3rd Feb to
5th Feb
6th Feb
7th Feb
time
2nd Feb
4th 2016
2016
2016
2016
2016
Testing
Activities
Final
migration
activities
Final
migration
activities
ANDROID
25
Project
closeout
activities
Transition to
operational
support
team
Resources to support activities
The following resources are required to complete project activities:
•
System testing tools used for overall system testing.
•
System experts to train the users and administrators.
•
Copies of user applications to be supplied to the users during training sessions.
•
User manuals to be distributed during training sessions.
Testing activities
Different processes will be used to test the integrated system to ensure there are no errors
or bugs. White box and black box testing methods will be used to test the integrated system. The
following are the main testing area:
ANDROID
26
Unit testing
Different units and components are tested to ensure they meet specified requirements and
behaviors. Different units have different functions and they perform certain task which should be
computed with accuracy. For this reason we shall test or units to ensure there are no errors.
System integration testing
Integration testing is a key issue in any system development. Units and components are
integrated together to perform a complex task and due to different components and units it is
important to test system after integration. This ensures all components and units pass message to
each other and behave as required.
Acceptance testing
All stakeholders are involved at this process of testing. Users determine whether the
system works as they expect while other stakeholders determine whether the systems meets their
business requirements. This testing process is important because it determines if all stakeholders
are satisfied. In case of a problem i0t should be corrected in time.
Final migration activities
Backup the old system
It is important to back up the old system to ensure we do not lose any information or
system configuration or settings. In case of the successor system fails to work as required, it will
be easy to retrieve data from the old system and if the situation is worse the old system can be
restored.
ANDROID
27
Install the new system
After system back up we can know install the new system. This involves deploying the
new system according to its requirements. All software should be installed in the specified
hardware. The process also involves physical connections of the hardware as specified.
Configuration of the new system
Relevant data from old system will be transferred to the new system to ensure that the
organization contains all important information. This data may involve customers’ details,
customers’ transactions among other minor details.
The system will be configured to ensure it meets the user preferences. Preferences may
differ from one user to another but common preference will be used to configure the system.
Later users can configure the system according to their own preferences.
Training activities
Training activities involves training all the users to use the system without any difficult.
All users will be provided with the necessary manuals which will help them in understanding and
using the system (van der Meij et al., 2013).
Administrator training
System administrators will be trained on how to use the overall system together with
administrator tools in it.
ANDROID
28
Customer and other user training
Customers and other users will be trained on how to use the system effectively. They will
be shown new features in the system and the overall functionalities of the system.
Project closeout activities
All stakeholders will have a meeting during the project closeout. This meeting will enable
all stakeholders to ask questions to the project team. This is important to ensure all stake holders
are satisfied (Verzuh, E. 2015).
Stakeholders shall also rate our service provided by the project team. They shall also
point out the areas we did well and the areas we need to improve. Finally the stakeholders will
sign the project completion form.
Operational support team
The new system requires to be supported to ensure smooth operation in the organization. A
new team will be appointed to offer support to the system. The support team will be available at
any time to solve the challenges users are facing. It is important to have a 24 hours support
through the week.
Lessons from this project
The following are lessons learned from this project:
•
It is important for any project to understand user requirements.
•
It is good to involve all users full in the system development.
ANDROID
•
29
There should be good relation and communication and relationship between the project
team and the stake holders.
•
Project planning requires proper documentations.
•
Project team should use best practices to ensure they deliver quality products.
•
System testing is important in all development life cycle and is used as a tool for quality
assurance.
ANDROID
30
References
Buede, D. M. (2011). The engineering design of systems: models and methods (Vol. 55). John
Wiley & Sons.
Leznov, A. N., & Saveliev, M. V. (2012). Group-theoretical methods for integration of nonlinear
dynamical systems (Vol. 15). Birkhäuser.
Shen, W., Hao, Q., & Xue, Y. (2012). A loosely coupled system integration approach for
decision support in facility management and maintenance. Automation in Construction,
25, 41-48.
van der Meij, H., & van der Meij, J. (2013). Eight guidelines for the design of instructional
videos for software training. Technical communication, 60(3), 205-228.
Verzuh, E. (2015). The fast forward MBA in project management. John Wiley & Sons.
Purchase answer to see full
attachment
Why Choose Us
- 100% non-plagiarized Papers
- 24/7 /365 Service Available
- Affordable Prices
- Any Paper, Urgency, and Subject
- Will complete your papers in 6 hours
- On-time Delivery
- Money-back and Privacy guarantees
- Unlimited Amendments upon request
- Satisfaction guarantee
How it Works
- Click on the “Place Order” tab at the top menu or “Order Now” icon at the bottom and a new page will appear with an order form to be filled.
- Fill in your paper’s requirements in the "PAPER DETAILS" section.
- Fill in your paper’s academic level, deadline, and the required number of pages from the drop-down menus.
- Click “CREATE ACCOUNT & SIGN IN” to enter your registration details and get an account with us for record-keeping and then, click on “PROCEED TO CHECKOUT” at the bottom of the page.
- From there, the payment sections will show, follow the guided payment process and your order will be available for our writing team to work on it.