Infrastructure and Security

Anonymous
timer Asked: Nov 19th, 2016

Question description

Project Deliverable 4: Infrastructure and Security

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 five to ten (5-10) 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:

  • Be typed, double spaced, using Times New Roman font (size 12), with one-inch margins on all sides; citations and references must follow APA or school-specific format. Check with your professor for any additional instructions.
  • 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.

Running Head: PROJECT DELIVEVRY THREE Project Delivery Three Name Course Tutor Date 1 PROJECT DELIVERY THREE 2 Introduction Organizations running businesses that are dependent on applications with databases need to ensure that the database is well-designed. This principle of having a proper design of the database is critical as it determines how the companies will meet their goals. Further, taking the time to come up with a good design allows flexibility because organizations can plan in advance on how changes can be accommodated in future. It is essential for organizations to consider certain fundamental principles in the database design framework. One of the principles is the reduction of redundant data because it wastes the amount of data allocated for databases. Also, the duplicated data at times may lead to inconsistencies and errors within the database. Ensuring that the data in the database is correct and complete is necessary as it determines the effectiveness of data that will be pulled from the database. This directly implies that having incorrect data will result into making flawed decisions which might affect the organization negatively. Additionally, in developing a good database, organizations ensure that their data is accurate and its integrity can be relied upon. The organizations’ reporting and data processing needs are also highly influenced by the kind of database that is designed. This design will be impacted by the kind of framework the developers decide to implement. Database Schema Database schemas in database management systems provide a logical view of what the database entails. It comprises of information on objects within a database, how they are arranged, and the associations that exist between them. It defines the checks that are applicable on the data. In most instances, the schema is used to describe the entities and how they relate to each other. PROJECT DELIVERY THREE 3 These entities include the indexes, views, tables, functions, and database links. Database developers design the schemas with the view of assisting the programmers to make the expected use of the database. The company will require a database that incorporates information of their employees, the products they sell, the suppliers they deal with and the order details made by their customers. Based on this information it will imply that the developers will design an OLTP database because the company will be using a transactional application. This is because this kind of application requires the creating, reading, updating and deleting of records by the end users. This approach takes the key first steps of the database design process which requires that developers establish what they intend to do with the database with the help of their users. Basically, this stage covers the requirements gathering process where information is gathered and refined for it meets the needs of the organization. See appendix 1. Tables Tables comprise of records and fields that contain information. They provide a snapshot of all the possible records available in a database. They are generated by the developers of a database schema after gathering information about an organization’s operations. The tables for this organization will include the following products, category, order details, orders, suppliers, employees, customers, and shippers. These entities will be captured in tables and their respective attributes listed. The tables used will be for a start as such it might not be exhaustive. Thus, the database is flexible as it will allow modifications that may result in changes to the organization’s operations. PROJECT DELIVERY THREE 4 In developing tables, relationships are modeled out of the data stored in those tables. It is therefore, expected that the relationship remains consistent to achieve referential integrity. This integrity is as a result of implementing entity integrity which requires that entities have unique keys. For the tables developed for this organizations, entities have unique keys as captured in the database schema diagram. Also, foreign keys have been used to ensure that relationships between tables synchronize whenever there are updates and deletes. See appendix 3. Entity-relationship diagrams Entity-relationship diagrams provide a mechanism for modeling entities captured in as system and the relationship that exists between them. Standard entity-relationship diagrams comprise of three main components, the entities which represent items or people, attributes which provide descriptions of the entities and the relationships which show the links that exist among different entities. These three components can be illustrated by using either conceptual, physical or the logical models. Different models represent unique complexities. It is advisable that designers consider starting with the conceptual model as they proceed to the physical model. It is imperative that designers of data storage applications consider the efficiency and future need that the organizations might require from the systems. The stability of the model should be dependable especially regarding instances in which business needs may change. Also, the model should be able to cater for all the data storage needs of an organization. In developing the ERD for this organization, some key considerations were made. For instance, the ERD is illustrated in a manner that it can be easily understood by the users and programmers. The model used matches with the database structure that is in place currently. The PROJECT DELIVERY THREE 5 ERD provides an effective solution with symbols and words that users can easily resonate with.See appendix 2. Data Flow Diagram A Data Flow Diagram (DFD) is a diagrammatic illustration used in object oriented analysis to depict how data flows within a system. Specifically, it captures details on how data moves into and out of the system, processes carried out on the data and where data resides. In modeling DFDs, processes, data stores, data flows are represented. The use of DFDs is common in software development where analysts need to show how information flows within the system they are developing or intend to develop. The rationale behind the design of the ERD for this organization’s system is to show the functions that the system performs. The DFD is designed with the view of allowing the programmers in understanding the internal operations of the system. It supports seamless communication in technical and nontechnical audiences since it is easier to understand. The data flow diagram is critical in the database design and programming especially in the early stages of design or when there is a desire to change the current system. The DFD is developed with the aim of helping programmers in developing the system in an organized and timely manner. Having the DFD will enable programmers in making decisions regarding the processes needed for the system to handle the information it is given. It will assist programmers in explaining what the system entails to normal users thus they save time that otherwise would be used if it didn’t exist. The DFD also will serve as a document for reference if there are any changes that need to be accommodated by the system. Additionally, the DFD will serve as a PROJECT DELIVERY THREE 6 reference point together with the help of debugging tools in detecting any errors within the system. See appendix 4. Queries Queries are used in a database environment to retrieve data from tables. Different queries are used to serve different purposes such as adding information by using the insert or append queries or removing information from tables with the use of the delete queries. Queries thus allow users to view data incorporated from several tables in a single sheet. Queries also allow the use of filters which enable users to limit the scope to some set of data they want to utilize. For this organization, the method of query by language will be used. It implies that requests will be made regarding some specified queries. This method is the most powerful in database management systems. Query 1 DROP TABLE IF EXISTS Employees_tbl; CREATE TABLE Employees_tbl ( Employee_IDint unsigned NOT NULL auto_increment, # Unique ID for the record FullNamevarchar(255) NOT NULL, # Full name of the employee LastNamevarchar(255) NOT NULL, # The last name of the employee Job_Idint(10) NOT NULL, Email # The job ID of the employee varchar(255) NOT NULL PROJECT DELIVERY THREE PRIMARY KEY 7 (Employee_ID) ); Query 2 USE diaperstore; INSERT INTO shippers ( Shipper_ID, Business_Name, Contact ) VALUES ( 3422, "Texas Shipping Limited", 00110011111 ), Interface Interfaces are objects through which users can interact with the system. The human design interface principles require that the designers of the interfaces understand their user’s skills and experience, what the users need and what the goals of their users are. In doing so, they are able to achieve the consistency that is expected of any interface. What does that imply? The users of the system will have the easy time working with the application that has been developed because it has components they are familiar with. Also, users will be able to complete their tasks faster because the design of the interface will be straight-forward. Designers of these interfaces will benefit as it will be easier for them to document the application. Providing support to users in case of issues in the systems will be easier and the time used in dealing with bugs will be lessened. See appendix 5. PROJECT DELIVERY THREE 8 References Doyle, M. (2011, August 25). MySQL for Absolute Beginners. Retrieved May 14, 2016, from http://www.elated.com/articles/mysql-for-absolute-beginners/ Anderson, M. (2008, October 24). Marc D Anderson's Blog. Retrieved May 14, 2016, from http://sympmarc.com/tag/database-programming-design-magazine/ Data Flow Diagrams. (n.d.). Retrieved May 14, 2016, from http://www.eis.mdx.ac.uk/staffpages/geetha/bis2030/DFD.html Introduction to database design. (n.d.). Retrieved May 14, 2016, from http://www.datanamic.com/support/lt-dez005-introduction-db-modeling.html Koirala, S. (2014, February 25). 11 important database designing rules which I follow. Retrieved May 14, 2016, from http://www.codeproject.com/Articles/359654/important-databasedesigning-rules-which-I-fo What is an Entity Relationship Diagram (ERD)? (n.d.). Retrieved May 14, 2016, from http://www.datanamic.com/support/lt-dez006-what-is-an-erd.html PROJECT DELIVERY THREE Appendices Appendix 1 Database Schema 9 PROJECT DELIVERY THREE Appendix 2 Entity Relationship Diagram 10 PROJECT DELIVERY THREE 11 PROJECT DELIVERY THREE 12 Appendix 3 Tables Table Name Attribute Name Products_tbl Product_ID Product_Name Supplier_ID Category_ID Product_Price UnitsinStock UnitsOnOrder Table Name Attribute Name Category Category_ID,INT,PK Category_Name Table Name Attribute Name Suppliers Supplier_Id Business_Name Contact Address Email Phone Country PROJECT DELIVERY THREE 13 Table Name Attribute Name Orders_tbl Order_ID CustomerID Employee_ID Shipper_ID OrderDate RequireDate ShippedDate ShipAddress ShipCountry Table Name Attribute Name Customers_tbl Customer_Id Company_Name Address Country City State Zip PROJECT DELIVERY THREE 14 Table Name Attribute Name Employees_tbl Employee_ID FirstName LastName Job_id Email Table Name Attribute Name Shippers_tbl Shipper_ID Business_Name Contact Table Name Attribute Name Order_Details_tbl Order_ID Product_ID UnitPrice Quantity PROJECT DELIVERY THREE Appendix 4 Data Flow Diagram 15 PROJECT DELIVERY THREE 16 PROJECT DELIVERY THREE Appendix 5 Screen Layouts 17 PROJECT DELIVERY THREE 18
ID Task Mode 0 1 2 3 4 5 6 7 8 9 10 11 12 13 Task Name Duration Start Finish Predecessors 10 Apr '16 S Project Management inception Project Objective Project Scope Document Scope Management Plan Scope Define Document Assumptions Project Risk Assessment Document Risk Management Plan Identify Risks Analyze Risks Document Risk Management Plans Project Integration Project Analysis Project: Project Management Date: Mon 14-11-16 146 days Thu 28-04-16 17 days 130 days 8 days 3 days Thu 28-04-16Fri 20-05-16 Fri 20-05-16 Thu 17-11-161 Fri 20-05-16 Tue 31-05-16 Fri 20-05-16 Tue 24-05-16 3 days 2 days Wed 25-05-16Fri 27-05-16 4 Mon Tue 5 30-05-16 31-05-16 Wed Tue 3 01-06-16 14-06-16 Wed Mon 01-06-16 06-06-16 10 days 4 days 08 May '16 S T T Thu 17-11-16 3 days 1 day 2 days Tue 07-06-16 Thu 09-06-168 Fri 10-06-16 Fri 10-06-16 9 Mon Tue 10 13-06-16 14-06-16 10 days Wed 15-06-16 Wed 29-06-16 8 days 24 Apr '16 F W M W 05 Jun '16 M S Project Director Project Manager Project Manager Project Manager Project Manag Project Man Project Ma Project Tue 7 28-06-16 Fri 08-07-16 12 Task Inactive Summary External Tasks Split Manual Task External Milestone Milestone Duration-only Deadline Summary Manual Summary Rollup Progress Project Summary Manual Summary Manual Progress Inactive Task Start-only Inactive Milestone Finish-only Page 1 22 May '16 S F ID Task Mode 14 15 16 Task Name Duration Start Finish Predecessors 10 Apr '16 S Project Report Budgeting Development 17 4 days 4 days 60 days Application 50 days Development Fix Bugs 5 days 18 19 Testing 20 Implementation 32 days 21 Maintenance Project: Project Management Date: Mon 14-11-16 30 days 2 days Wed Mon 29-06-16 04-07-16 Tue 05-07-16 Fri 08-07-16 Mon Fri 19-08-16 30-05-16 Mon Fri 05-08-16 30-05-16 Mon Fri 12-08-16 08-08-16 Mon Fri 30-09-16 22-08-16 Mon Tue 03-10-16 15-11-16 Wed Thu 16-11-16 17-11-16 24 Apr '16 F W M 08 May '16 S T T W 05 Jun '16 M S 14 13 App 17 16 19 20 Task Inactive Summary External Tasks Split Manual Task External Milestone Milestone Duration-only Deadline Summary Manual Summary Rollup Progress Project Summary Manual Summary Manual Progress Inactive Task Start-only Inactive Milestone Finish-only Page 2 22 May '16 S F 05 Jun '16 S T 19 Jun '16 T S 03 Jul '16 F W M 17 Jul '16 S T T 31 Jul '16 S F W 14 Aug '16 M S T 28 Aug '16 T S 11 Sep '16 F W M 25 Sep '16 S T T 09 Oct '16 S F irector ct Manager oject Manager Project Manager Project Manager,Acceptor Project Manager Project Manager Project Manager,Acceptor Project: Project Management Date: Mon 14-11-16 Task Inactive Summary External Tasks Split Manual Task External Milestone Milestone Duration-only Deadline Summary Manual Summary Rollup Progress Project Summary Manual Summary Manual Progress Inactive Task Start-only Inactive Milestone Finish-only Page 3 W 23 Oct '16 M S T 06 Nov '16 T S 20 Nov '16 F W 05 Jun '16 S T 19 Jun '16 T S 03 Jul '16 F W M 17 Jul '16 S T Project Manager T 31 Jul '16 S F W 14 Aug '16 M S T 28 Aug '16 T S 11 Sep '16 F W M 25 Sep '16 S T T 09 Oct '16 S F Project Manager Application Architect Application Architect,Acceptor Project: Project Management Date: Mon 14-11-16 Task Inactive Summary External Tasks Split Manual Task External Milestone Milestone Duration-only Deadline Summary Manual Summary Rollup Progress Project Summary Manual Summary Manual Progress Inactive Task Start-only Inactive Milestone Finish-only Page 4 W 23 Oct '16 M S T 06 Nov '16 T S 20 Nov '16 F W

Tutor Answer

(Top Tutor) Studypool Tutor
School: UCLA
Studypool has helped 1,244,100 students
flag Report DMCA
Similar Questions
Hot Questions
Related Tags
Study Guides

Brown University





1271 Tutors

California Institute of Technology




2131 Tutors

Carnegie Mellon University




982 Tutors

Columbia University





1256 Tutors

Dartmouth University





2113 Tutors

Emory University





2279 Tutors

Harvard University





599 Tutors

Massachusetts Institute of Technology



2319 Tutors

New York University





1645 Tutors

Notre Dam University





1911 Tutors

Oklahoma University





2122 Tutors

Pennsylvania State University





932 Tutors

Princeton University





1211 Tutors

Stanford University





983 Tutors

University of California





1282 Tutors

Oxford University





123 Tutors

Yale University





2325 Tutors