Service Request 2

Service Request SR-rm-022, Part 2
Robert Mascarenas

In the ongoing process of analyzing the HR department of Riordan Manufacturing and integrate the existing tools into an application, the project transitions from the analysis phase to the design phase. This phase will include a detailed description of the application architecture and process design as well as a high-level description of recommended security tools. A description of the system’s architecture regarding data, interfaces, network, and operations are also included in this phase and will be addressed in this section of the paper. Finally, a physical data flow diagram will be included to show how the system will take in data, deliver, and output. Understanding the expectations cannot be done while you are constructing and testing the solution. The expectations must be understood up front - first in the high-level Project Charter, but more importantly in the more detailed business requirements.
The Analysis Phase is where the project lifecycle begins. “The Analysis Phase is where you break down the deliverables in the high-level Project Charter into the more detailed business requirements” (Mochal, 2008). The Analysis Phase is also the part of the project where you identify the overall direction that the project will take through the creation of the project strategy documents.
The Design Phase seeks to develop detailed specifications that emphasize the physical solution to the user's information technology needs. The system requirements and logical description of the entities, relationships, and attributes of the data that were documented during the Requirements Analysis Phase. A formal review of the high-level architectural design is conducted before detailed design of the automated system/application. To achieve confidence that the design satisfies the system requirements, is in conformance with the enterprise architecture and prescribed design standards, to raise and resolve...