Assignment Guidelines For this week’s assignment, you will be developing the requirements specification for this integration. You should use all of the tools available to you to elicit requirements (such as one-on-one interviews with all major stakeholde
Table of Contents
2.1 Work breakdown Structure 5
3. System Integration Best Practice’s 6
3.2 System Integration Architecture Flow Chart 7
4. Requirement Specification 8
5. Enterprise System Integration Approach Evaluation and Selection 9
6. Proposed System Integration Components Architecture 10
7. Implementation Framework 11
8. System Integration Implementation 12
Quality Payment Program
Integration Specification
<Page 1 of 11>
This system will use the following major components:
· Engineer
· Data
· Hardware
· Software
· Network
Diagram 1 System Components
System boundary will include:
· Farewells
· System Environment
· Security Application components (HTTPS)
· Information System.
Diagram 2 System Boundary
Quality Payment Program System
1.1 Initiation, Concept and Planning
1.1.1 Engineer review / Architectural review
1.1.2 Stakeholder selection review
1.1.3 Project Review
1.2 Requirement Analysis and Design
1.2.1 Project Requirement Review
1.2.2 Create Preliminary Design Review
1.2.3 Develop a detail Design Review
1.3 Development And Testing
1.3.1 System Environment Review
1.3.2 System Environment Validation
1.3.3 Design System Implementation
1.3.4 Procure Hardware/Software
1.3.5 Install Development System
1.3.6 System Testing Phase
1.3.7 Install Live System
1.4 Implementation
1.4.1 System Implemented
1.4.2 Documentation
1.4.3 Go Live
1.4.4 Sign off from the Stakeholder
1.5 Operation And Maintenance / Disposition
1.5.1 Post Implementation
1.5.2 Annual Testing of the security component of the system
1.5.3 Update Documents
1.5.4 Disposition / End live
The project is proposed to start by October 4th, 2017 and all projects deliverables are ready and submitted by November 7th, 2017.
System Integration Best Practice’s
Because CMS as an organization is committed to strengthening their own information system development life cycle processes. For the organization to respond quickly to business demands and as specified by FISMA law. CMS created the Expedited Life Cycle (XLC) to help coordinate and develop IT projects.
These XLC provide steps by steps process in developing a system, create a good communication between the stakeholder and the project manager to communicate. Through the planning / initiation phase, it allows the system engineer and designers to communicate with each other and decide whether the clients’ requirements of the system are meets.
System Integration Architecture Flow Chart
(TBD)
Enterprise System Integration Approach Evaluation and Selection
(TBD)
Proposed System Integration Components Architecture
(TBD)
(TBD)
System Integration Implementation
(TBD)
Shelly, G., & Rosenblatt, H. (2012). System analysis and design. Mason, OH: Cengage Learning.
Clark,K. (March 18, 2005) Comparing web APIs with service-oriented architecture and enterprise application integration
https://www.ibm.com/developerworks/websphere/library/techarticles/1503_clark/1305_clark.html
https://qpp.cms.gov/docs/Quality_Payment_Program_Overview_Fact_Sheet.pdf
https://security.ufl.edu/wp-content/uploads/2014/06/Bad-System-Diagram.png
https://www.cms.gov/Research-Statistics-Data-and-Systems/CMS-Information-Technology/XLC/index.html
https://www.cms.gov/Research-Statistics-Data-and-Systems/CMS-Information-Technology/XLC/Phases.html