Fluent Essays

Click the link above to submit your assignment. Students, please view the "Submit a Clickable Rubric Assignment" in the Student Center. Instructors, training on how to grade is within the Instructor Center. Project Deliverable 4: Infrastructure and Security Due Week 8 and worth 150 points This assignment consists of two (2) sections: an infrastructure document and a revised Gantt chart or project plan. You must submit both sections as separate files for the completion of this assignment. Label each file name according to the section of the assignment for which it is written. Additionally, you may create and / or assume all necessary assumptions needed for the completion of this assignment. The last section of the project plan will present the infrastructure in accordance with the parameters set forth at the outset of the project. The network solution that is chosen should support the conceived information system and allow for scalability. The network infrastructure will support organizational operations; therefore, a pictorial view of workstations, servers, routers, bridges, gateways, and access points should be used. In addition, access paths for Internet access should be depicted. A narrative should be included to explain all the nodes of the network and the rationale for the design. Lastly, using the Confidentiality, Integrity and Availability (CIA) Triangle, define the organizational security policy. CIA is a widely used benchmark for evaluation of information systems security. Section 1: Infrastructure Document 1. Write a six (6) page infrastructure document in which you: a. Design a logical and physical topographical layout of the planned network through the use of graphical tools in Microsoft Word or Visio, or an open source alternative such as Dia. Note: The graphically depicted solution is not included in the required page length. b. Illustrate the possible placement of servers including access paths to the Internet and firewalls. Note: Facility limitations, workstations, printers, routers, switches, bridges and access points should be considered in the illustration. c. Explain the rationale for the logical and physical topographical layout of the planned network. d. Create a comprehensive security policy for the company that will: i. Protect the company infrastructure and assets by applying the principals of CIA. Note: CIA is a widely used benchmark for evaluation of information systems security, focusing on the three core goals of confidentiality, integrity and availability of information. ii. Address ethical aspects related to employee behavior, contractors, password usage, and access to networked resources and information. Your assignment must follow these formatting requirements: This course requires use of Strayer Writing Standards (SWS). The format is different than other Strayer University courses. Please take a moment to review the SWS documentation for details. Include a cover page containing the title of the assignment, the student’s name, the professor’s name, the course title, and the date. The cover page and the reference page are not included in the required assignment page length. Include charts or diagrams created in MS Visio or Dia as an appendix of the infrastructure document. All references to these diagrams must be included in the body of the infrastructure document. Section 2: Revised Gantt Chart / Project Plan Use Microsoft Project or an open source alternative, such as Open Project, to: 2. Update the Gantt chart or project plan (summary and detail) template, from Project Deliverable 3: Database and Programming Design, with all the project tasks. The specific course learning outcomes associated with this assignment are: Demonstrate an understanding of existing and emerging information technologies and strategic impact on organizational operations. Evaluate the issues and challenges associated with information technology integration. Evaluate the ethical concerns that information technology solve or present in a global context. Use technology and information resources to research issues in information technology. Write clearly and concisely about strategic issues and practices in the information technology domain using proper writing mechanics and technical style conventions. Grading for this assignment will be based on answer quality, logic/organization of the paper, and language and writing skills, using the following rubric found here. ProjectSchedule Create a Project Schedule in this worksheet. Enter title of this project in cell B1. Information about how to use this worksheet, including instructions for screen readers and the author of this workbook is in the About worksheet. Continue navigating down column A to hear further instructions. Gantt Chart Enter Company Name in cell B2. Enter the name of the Project Lead in cell B3. Enter the Project Start date in cell E3. Project Start: label is in cell C3. Project Start: Wed, 2/19/2020 The Display Week in cell E4 represents the starting week to display in the project schedule in cell I4. The project start date is considered Week 1. To change the display week, simply enter a new week number in cell E4. The starting date for each week, starting with the display week from cell E4, starts in cell I4 and is auto calculated. There are 8 weeks represented in this view from cell I4 through cell BF4. You should not modify these cells. Display Week: label is in cell C4. Display Week: 1 Feb 17, 2020 Feb 24, 2020 Mar 2, 2020 Mar 9, 2020 Mar 16, 2020 Mar 23, 2020 Mar 30, 2020 Apr 6, 2020 Apr 13, 2020 Apr 20, 2020 Apr 27, 2020 May 4, 2020 May 11, 2020 May 18, 2020 Cells I5 through BL5 contain the day number for the week represented in the cell block above each date cell and are auto calculated. You should not modify these cells. Today's date is outlined in Red (hex #AD3815) from today's date in row 5 through the entire date column to the end of the project schedule. 17 18 19 20 21 22 23 24 25 26 27 28 29 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 This row contains headers for the project schedule that follows below them. Navigate from B6 through BL 6 to hear the content. The first letter of each day of the week for the date above that heading, starts in cell I6 and continues through cell BL6. All project timeline charting is auto generated based on the start and end dates entered, using conditional formats. Do not modify content in cells within columns after column I starting with cell I7. TASK ASSIGNED TO PROGRESS START END DAYS M T W T F S S M T W T F S S M T W T F S S M T W T F S S M T W T F S S M T W T F S S M T W T F S S M T W T F S S M T W T F S S M T W T F S S M T W T F S S M T W T F S S M T W T F S S M T W T F S S Do not delete this row. This row is hidden to preserve a formula that is used to highlight the current day within the project schedule. Cell B8 contains the Phase 1 sample title. Enter a new Title in cell B8. Enter a name to assign the phase to, if it applies for your project, in cell C8. Enter Progress for the entire phase, if it applies for your project, in cell D8. Enter the start and end dates for the entire phase, if it applies for your project, in cells E8 and F8. The Gantt chart will automatically fill in the appropriate dates and shade according to the progress entered. To delete the phase and work only from tasks, simply delete this row. Project cycle 2/19/20 5/24/20 96 Cell B9 contains the sample task "Task 1." Enter a new task name in cell B9. Enter a person to assign the task to in cell C9. Enter progress of the task in cell D9. A progress bar appears in the cell and is shaded according to the number in the cell. For example, 50 percent progress would shade half of the cell. Enter task start date in cell E9. Enter task end date in cell F9. A status bar shaded for the dates entered appears in blocks starting from cell I9 through BL9. Requirements and delivery CIO 0% 2/19/20 2/20/20 2 Rows 10 through 13 repeat the pattern from row 9. Repeat the instructions from cell A9 for all task rows in this worksheet. Overwrite any sample data. A sample of another phase starts in cell A14. Continue entering tasks in cells A10 through A13 or go to cell A14 to learn more. Network design 0% 2/21/20 2/28/20 8 review business model/design 0% 2/29/20 3/1/20 2 Finalize design and review 0% 3/2/20 3/8/20 7 Network security design 0% 3/9/20 3/11/20 3 Site development needs 3/12/20 3/14/20 Rack requirements and locations to be included 3/15/20 3/16/20 Identification of the cabling needs 3/17/20 3/19/20 Finalize design review 3/20/20 3/25/20 Incorporation of customer data 3/26/20 3/28/20 Database design layout 3/29/20 4/4/20 inventory require for inclusion 4/5/20 4/7/20 inventory database design 4/8/20 4/14/20 creation and testing of customer database 4/15/20 4/20/20 creation and testing of inventory database 4/21/20 4/26/20 Testing of the designed databases 4/21/20 4/25/20 insta Installation, config,and Testing infrastructure 4/25/20 4/27/20 Rack install 4/28/20 4/30/20 hardware install 4/28/20 4/30/20 Cabling install 4/28/20 4/30/20 Testing and configuration of network devices 4/30/20 5/10/20 Server config 4/30/20 5/2/20 database installation 5/2/20 5/4/20 installation of monitoring stations 5/4/20 5/6/20 Installation of computers and testing stations 5/6/20 5/8/20 End to end testing 5/8/20 5/10/20 web Website connectivity and testing of database 5/10/20 5/13/20 full system online 5/14/20 5/15/20 data Database design and programming design 5/16/20 5/17/20 D Database schema 5/18/20 5/19/20 E-R diagram 5/20/20 5/21/20 Data flow diagram 5/22/20 5/23/20 Data overall flow 5/23/20 5/24/20 User training 5/24/20 5/25/20 Initial maintenance and closure 5/25/20 5/25/20 Database Design: Franchise Management System 1 13 Database Design: Franchise Management System Database Design: Franchise Management System Charles Foley CIS 498: Information Technology Capstone 2/19/20 Database Design: Franchise Management System Introduction Over the years, there has been a rise in the level of use of the latest technologies in facilitating the operations of various business entities. Business leaders and managers have realized that the success of their entities relies on the strategies employed and adopted in the long run. Businesses in various regions have utilized the latest technologies to create a competitive advantage over rivals. In this case, the creation of competitive advantage, in the long run, helps to achieve improved sales and hence profits. However, determining the right technology to implement remains a significant challenge for many businesses. In this case, it, therefore, follows that the management teams should ensure that they understand the role and benefits of each of the available technologies which in the long run may aid in the improvement of the overall level of insight into the operations carried out on the day to day basis. One of the most common technologies which many businesses adopted over the years involves the aspect of the use of relational databases (Hoffer, Ramesh & Topi, 2016). The development and use of database systems help in the creation of a platform for improved business operations in the long run. While database systems help in the improvement of the operations carried out on the day to day basis, it is worth noting that the ability to achieve positive outcomes revolves around the aspects of the selection of the right approaches to design the ultimate systems and solutions. Information system development helps in the provision of the ultimate success and efficiency of the respective entities in the long run. This project looks at the case of a franchise business which manages different branches and deals in the sale of various products. The business needs a system which will facilitate not only communication and reporting but also the overall operations carried out in the various branches. Therefore, the business will benefit from the use of a relational database based on the idea that it will facilitate the provision of a platform for improved storage and retrieval of information about the various branches, products and people involved in the various processes. The system will help in redefining the requirements for the business while at the same time aiding in process reengineering activities. The first section looks at the database schema of the proposed system. The second part looks at the aspects of normalization, tables and the entire database using SQL. On the other hand, the paper will look at the creation of a data flow diagram which graphically represents the movement of information throughout the database. Database schema design A database schema acts as a diagrammatic representation of a database using various attributes and aspects such as the tables, relationships, views and indexes. In this context, the creation of a schema helps to show a high-level view of the database and the various entities involved in the storage and retrieval of information. Also, a database schema helps on the variation of a high-level perception of the details which the system will store and deal with. Therefore, it is essential to look at the needs of the business in the context in the development of the schema. Hence, to ensure that all the data is covered and included in the final structure. The database, in this case, will comprise five main tables. These tables will store data such as the franchiser, franchisee, commodities, orders and products. The diagram shown in the appendix represents the graphical view of the schema of the database. See attached appendix the Franchise management database schema. Tables’ construction with normalized design When it comes to the construction of tables and the entire database, it is essential to look at the aspects of normalization. Normalization helps in the creation of a platform for reducing the risks of redundancies in the final database system and structure. Failing to normalize the tables will result in storage of multiple similar records throughout the database. In the long run, such a practice will increase the level of inconsistency achieved as far as the management of data and records is concerned. On the other hand, it is essential to look at the best ways to implement the database to guarantee referential integrity. Referential integrity helps in the creation of a platform for improved insight into the efficiency of the storage and retrieval of data (Greenstein, Grunin, Schwenger & Swamikrishnan, 2019). In addition, it helps to eliminate the problems of redundant records while at the same time promoting the creation of an efficient system. Referential integrity is achieved through the use if the right relationships and links. Therefore, to achieve referential integrity, the database will use both primary and foreign keys in the various tables. Foreign keys help in connecting database tables according to their relationships. The following code helps in the creation of the database tables for the system in the context. The code below creates the database tables observing the aspects of referential integrity and maintaining the desired level of efficiency. The main tables are franchiser, franchisee, item, invoice, order, order-item and item type. Franchiser CREATE TABLE Franchiser ( Franchiser id int PK, name varchar, email varchar ); Franchisee CREATE TABLE Franchisee ( Franchisee id int PK, name varchar, email varchar, franchiser id int FK ); Item CREATE TABLE item ( Item id int PK, description varchar, franchiser id int FK, item-type id FK ); Invoice CREATE TABLE Invoice ( Invoice id int PK, order id FK, status BOOL ); Order CREATE TABLE order ( Order id int PK, franchiser id int FK, franchisee id int FK, status int ); Item-type CREATE TABLE item-type ( Item-type id int PK, description varchar ); Order item CREATE TABLE order-item ( Order-item id int PK, item id int FK, qty int, order id FK ); Entity-relationship diagram and explanation An entity-relationship diagram shows the links and associations of the various tables in a database. It is worth noting that the creation of an entity-relationship diagram helps in providing a high-level view of the links between or among the various tables which make up the entire system (Greenstein, Grunin, Schwenger & Swamikrishnan, 2019). The diagram presented in this case shows the connection between and among the various tables referred to as entities. The diagram shows the different types of relationships, such as one to many, which connect the various tables to enforce referential integrity and eliminate redundancies. See the appendix for the entity-relationship diagram. Data flow diagram for the business A data flow diagram shows a graphical representation of the logical movement of data within a database. The primary aim for the creation of a data flow diagram is to show the logical movement of information within the system and the respective primary processes involved in the long run (Elmasri & Navathe, 2017). The figure attached in the appendix shows the DFD diagram for the database in the context. See the appendix for the data flow diagram. Example query 1 The navigation of a database involves the creation of both inbuilt and customized queries to meet the needs of the users at a given time. This section outlines two queries to retrieve data from the database and to add details to a given table. Retrieval query SELECT name from franchiser WHERE franchiser id = “f001”; This query returns a name of the franchiser whose ID is F001. Example query 2 This section presents a query for adding information into one of the tables mentioned above. The section will add a product into the item table. INSERT INTO Item (Item id int PK, description varchar) VALUES (‘NK001’, ‘Nike Air men's sports shoes’); Example screen layout 1 The screen layout provided below represents a platform for viewing the available stores or franchises. See appendix for the screen layout. Example screen layout 2 The layout below shows a stock management screen. See appendix for the screen layout. References Hoffer, J. A., Ramesh, V., & Topi, H. (2016). Modern database management (p. 600). Pearson. Elmasri, R., & Navathe, S. (2017). Fundamentals of database systems (Vol. 7). Pearson. Greenstein, M. A., Grunin, G., Schwenger, M. N., & Swamikrishnan, P. (2019). U.S. Patent No. 10,380,083. Washington, DC: U.S. Patent and Trademark Office. Appendix Database schema Entity-relationship diagram DFD diagram Screen layout 1 Screen layout 2