Assignment OverviewType: Individual ProjectUnit: System Integration EvaluationDue Date: Tue, 8/28/18Grading Type: NumericPoints Possible: 150Points Earned: Deliverable Length: 7-10 pagesView objec

System Architecture and Integration (ITCO425-1804A-01)

Systems Integration Design Plan 

Jacqueline Calloway

AIU

August 14, 2018

Table of Contents

Project Information .....................................................................................................................3-4

Project Plan ………...............................................................................................................................5

System Integration Best Practice.........................................................................................................6

Requirements Specifications.................................................................................................................TBD

Enterprise System Integration Analysis.................................................................................TBD

Systems Integration Approach Evaluation and Selection...........................................................TBD

Proposed System Integration Components Architecture............................................................TBD

Implementation Framework.................................................................................................................TBD

System Integration Implementation Plan......................................................................................TBD

Project Information (Week1)

The MaintMax Project will be implemented in Ace Corp.’s Maintenance Division to replace the existing maintenance tracking system which is inadequate for expanding operations. The implementation of this database is a deliberately planned and highly technical effort. This description of the implementation will provide all stakeholders with a detailed understanding of how the implementation will occur.

Upon completion of the design for the MaintMax Database, a beta version of the database will be loaded in Ace Corp.’s virtual testing server. Ace Corp.’s IT Group will capture all existing data from the existing database and load that data into the MaintMax database in order to test data integrity and compatibility between how maintenance data is captured and the new MaintMax database. Once testing is complete and functionality of the MaintMax database is verified, operator training will be conducted with maintenance staff on the new tool. Once training is complete, the MaintMax Database will be loaded onto Ace Corp.’s maintenance servers and partitioned off to prevent user access. Ace Corp.’s IT Group will then verify functionality of the database on the actual Ace Corp. maintenance servers.

Once functionality on maintenance servers is confirmed, a notification will be distributed to the entire organization communicating the transition from the legacy maintenance database to the new MaintMax Database. At this point in time, the maintenance staff, in conjunction with the IT Group will conduct a final data capture of all maintenance data on the legacy system and the data will be imported by the IT Group to the MaintMax Database. Once the data import has been deemed successful by the IT Group, the legacy system will be turned off. At this point in time a manual contingency operation will be employed wherein maintenance technicians capture all maintenance actions manually for a period of two days while the MaintMax Database is prepared to go live. Upon approval from the IT Group, the MaintMax Database will go live and be used for a period of forty-eight hours by the maintenance technicians with IT Group support to ensure acceptance criteria are met. Once the team verifies that the acceptance criteria have been met, the manually captured maintenance data will then be entered into the MaintMax Database. Completion of entering the manual data and achievement of the acceptance criteria formally ends the implementation phase of this project.

Project Plan (WEEK1)

This Implementation and Migration Plan has been developed to communicate how the MaintMax Maintenance Database Project will be implemented, installed, and migrated to its operational environment within Ace Corporation’s Maintenance Division. The purpose of this plan is to ensure all stakeholders are aware of the details, requirements, and responsibilities involved in successfully completing this project and migrating the product to the operational group. Any requested changes to this plan should be submitted through the project’s change control process for review and approval prior to implementation.

System Integration Best Practice (WEEK1)

The MaintMax Database Project requires a database design on an upgraded Smarttech II platform as opposed to a Smarttech platform where the existing database resides. While this allows improved functionality and capability, it does not require any additional hardware or upgrades to existing hardware. Likewise, no additional facilities are required to complete the implementation and migration of this project. This project will be completed within the existing capabilities of Ace Corp.’s hardware and current facility.

The MaintMax Database will provide not only the same capabilities as the legacy database, but additional functionality as well. As such, these additional functions have been included by the design team in planning for ongoing performance monitoring of the MaintMax Database. To accomplish this, additional monitoring criteria have been added to the operational environment to collect real-time data once the database is migrated to its operational environment. The Maintenance Operations Lead is responsible for monitoring performance and producing weekly reports which will be provided not only to Ace Corp. senior management, but to the IT Group Lead as well. If MaintMax performance monitoring indicates any database performance outside of the acceptable levels, the issue will be escalated immediately to the Ace Corp. staff leads to determine and execute corrective measures and initiate a root cause analysis. This is the existing procedure Ace Corp. utilizes for all IT tools.

Requirements Specifications (WEEK2)

Process used to elicit the requirements

Interviews

Interviews were used to gather requirements. The various stakeholders such as software reviewers to Database Administrators were interviewed on a one-on-one interview

Questionnaires

Since there are several end users of the database, having a one-on-one interview with them was impossible. I used questionnaires where end users answered questions on a questionnaire.

Facilitated workshops

Facilitated workshops were used where various stakeholders met with an aim of coming up with requirements

Documentation studies

Various documents such as manuals and policies such as data security policy were studied with an aim for coming up with requirements.

List of stakeholders and their roles

End users

These are the people who will use the MaintMax Database on a daily basis.

Database administrators

These are the people who will administer the MaintMax database while giving rights and privileges to users

Network administrators

These are the people who manage the network within the organization, Ace. Corporation so that the MaintMax database can be accessed with ease from any workstation.

Board of directors of Ace Corporation

These are the people who will approve the release of funds for the MaintMax database to be designed from conceptual to physical design

Financial officers

These are the people that will release the funds for the design and maintenance of MaintMax database

Software reviewers

These are the people that will review the database and analyze the errors produced when the database is being developed

Software developers

These are the people that will build the user interface that will help end users access, interact and manipulate data in the MaintMax database

Functional requirements

Data storage

Maint Max database should be able to facilitate storage of data, retrieval and other manipulation of data

Transaction handling

Transaction in databases can be seen as a logical unit that is executed independently for data retrieval or updates. Database transactions ensure that inconsistencies in a database do not occur. It is either the data is updated or if an error occurs, the data is rolled back but it cannot be updated partially. Maint Max database should support transaction. That is, a transaction should either complete successfully or it is aborted.

Authentication

Authentication in relation to database is the process of confirming that a user attempting to log in to the system is authorized to do so, and is given the rights that he or she is authorized to do. For example, a user who has only the right to retrieve and read data should not be able to write and update the data. Maint Max database should be able to authenticate users and also offer rights and privileges.

Business rules

Business rules in relation to databases are statements that enforce certain constraints in a database. Business rules are also known as constraints. MaintMax should be able to enforce business rules.

Certification requirements

A database should be able to encrypt data such as passwords. MaintMax database should be able to perform encryption of data.

User interface

There should be a user interface that will be used by end users in order to access the database and manipulate the data

Non-functional requirements

Performance

Performance can be seen as how fast or slow data is retrieved or updated in a database. Maint Max database should have a high performance

Recoverability

Recoverability in relation to databases can be seen as restoration of lost data. Data can be lost by accidental deletion, corrupt data etc. MaintMax database should ensure restoration of data in case of any failure such as network failure etc.

Reliability and maintainability

MaintMax database should be able to be relied upon and it should produce data that is reliable to the users. It should also be able to be maintained by the necessary stakeholders such as database administrators.

Interoperability

MaintMax database should be able to be accessed from any workstation running on any platform. For example, a person working on a workstation running on Windows should be able to access the MaintMax and so should the person working on a workstation running on Linux.

Capacity

MaintMax database should have a huge capacity and should be able to save a lot of data and also retrieve huge chunks of data without hindering its performance

Availability

The MaintMax database should be available at any time whenever it is needed

Assumptions

The following are the assumptions for the scope of the project

Availability of technical staff

Technical staff such as Software Developers, Software Reviewers, and Database Administrators etc. will be available as needed

Budget limitations

The entire budget of the project is dependent on the approval by the board of directors

Pros and cons of proceeding with the project

Pros

The project will ensure database performance compared to the one currently running

The project will ensure huge capacity of data storage where a lot of data can be saved without hindering the database performance compared to the one currently running

Cons

There will be time wastage during the data entry phase where data is migrated from the current database to the new MaintMax database

Enterprise System Integration Analysis (WEEK3)

TBD

Systems Integration Approach Evaluation and Selection (WEEK3)

TBD

Proposed System Integration Components Architecture (WEEK4)

TBD

Implementation Framework (WEEK4)

TBD

System Integration Implementation Plan(WEEK5)

TBD