Project 4
instructions attached
●
Project Deliverable 4: Infrastructure and Security Instructions
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 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:
This course requires use of Strayer Writing Standards (SWS). The format is
https://blackboard.strayer.edu/bbcswebdav/institution/STANDARDIZED/StrayerWritingStandards/Strayer_Writing_Standards
●
●
●
●
●
●
●
●
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.
Running Head: SECTION 1: PROJECT INTRODUCTION 1
SECTION 1: PROJECT INTRODUCTION 2
Section 1: Project Introduction
Name
Institution
Date
Section 1: Project Introduction
Background information
The company background explores the significance of data regarding the firm taken into account in the scenario. In this exploration, fictional e-commerce cooperation, “XYZ Inc., an advanced e-commerce startup.” The company comprises of a semi-automated system whose major function is analyzing its statistics. The firms do not have an information system that is responsible for executing its operations. Recently, XYZ Inc. decided to lend a “Chief Technology Officer” to convey an “Information Technology Project Plan” with hopes that he/she will stir the company into obtaining a new office block (Ambler, 2018).
The primary purpose of the project plan report is to help the cooperation get rid of all possible complications during the changeover to the new office block and to avoid bringing company operations to a halt during all this time. “We must come up with a new automated information system which will be designed in line with the existing infrastructure and technology. I was requested by the cooperation to deliver my plan within 60 days in line with company growth. The company lacks a building and technology infrastructure because it is a starting company. the primary requirement is implementation of hardware and software in on-site solution or hosted solution. CEO expects that various technologies will be integrated together for the company growth in the industry. The facility expects to increase the number of employees and annual revenue from 5 10 to 30 and $5 to $30 respectively in the coming years.”
Types of Business the company is involved
The little information available narrates that the firm will be involved in the e-commerce business. For example, XYZ firm will be entangled with reservation of traveling bookings using a built online platform or application. The firm can also venture into the mobile system application as an extension of the online reservations. XYZ can even venture into an e-commerce site that will be facilitating activities in the transport industry. The need for CTO is to accelerate the rate of innovations in the company.
Information system of the company to support business
CTO’s role in formulating a plan will be used to design how the organization will look after the adoption and implementation of an information system. The firm might also consider adopting social media platforms to uphold the business. Clients’ satisfaction through the reviews they give needs to be respected at all times.
Databases
The database system in place will be used as an alternative solution while the business is small. This is because it is not capable of providing solutions when dealing with big data. Thus, accepting the adoption of Big Data Analytics will imply that databases are used to supplement complex operations
System analysis
CTO suggests that “Rapid Application” needs to be put in place through the “waterfall” technique. The waterfall technique should be used because it is among the most conservative approach for new and emerging schemes. To overcome its main challenge of integrating variations, a Rapid method will be put in place. This technique allows the expansion of user data since the business might grow any soon. With scrum system development implemented, consumer feedback will be used positively in ensuring that the consumers reflect the smoothness with which the activities are undertaken.
Security
In any organization, security remains an imperative aspect in the contemporary world where cybersecurity issues are common among the organization, particularly when activities involve the utilization of data. The information available needs to be scrambled well so that if unauthorized people access it, it remains pointless. Anti-malware products need to be installed. Vulnerabilities and threats remain regulated.
Networking
Networking relies on CISCO procedures. IT will support the adoption of high-speed networks that will facilitate task execution in the organization. Linksys based routers, together with CISCO, best define the kind of system to be implemented (Cisco, 2018).
Computer Infrastructure
Accessibility and office layout will remain essential when it comes to PC arrangements. The firm will be supposed to have a 24X seven scope of the entire site. This will allow clients to issue reservations anytime they wish.
Human-Computer Interaction
The application will be typed using Java language and will be based on portable adaptation. All the applications will be accessible using IoS, Android, and windows as well. The requests will be granted descent controls and appealing layout.
Web design
The best design to apply in this case will be JavaScript and HTML since they give very good site scheming appearance (Satzinger, Jackson & Burd, 2017). The anticipated website will be comprehensive and will be capable of providing real-time updates to the clients and new users.
References
Ambler, S. (2018). The Agile System Development Life Cycle (SDLC). Ambysoft.
Cisco. (2018). Cisco on Cisco Best Practices. Retrieved from cisco:
http://www.cisco.com/c/dam/en_us/about/ciscoitatwork/downloads/ciscoitatwork/pdf/how_cisco_it_achieved_a_highly_available_wide_area_network
Satzinger, J. W., Jackson, R. B., & Burd, S. D. (2017). Systems Analysis & Design in a changing world. Cengage Learning.
>Sheet 0
20
0, 2020
Saturday, August 01, 2020 , 2020
, 2020
2 12 , 2020
, 2020
, 2020
5 , 2020
, 2020
1 1 Sunday, October 04, 2020 1 1 Thursday, October 08, 2020 1 Friday, October 09, 2020 12 Saturday, October 10, 2020 2 , 2020
, 2020
3 , 2020
4 Saturday, October 31, 2020 2 1 Sunday, November 08, 2020 7 1 , 2020
system
2 2 , 2020
1 1 Saturday, November 28, 2020 16 29 1 1 Thursday, September 24, 2020 Friday, September 25, 2020 9 Thursday, October 08, 2020 5 53 3 Sunday, October 25, 2020 Wednesday, October 28, 2020 5 Wednesday, October 28, 2020 3 Wednesday, November 04, 2020 62 Hardware Testing 9 Saturday, November 07, 2020 1 Saturday, November 07, 2020 Sunday, November 08, 2020 1 Sunday, November 08, 2020 Monday, November 09, 2020 2 Wednesday, November 11, 2020 1 Sunday, November 15, 2020 Monday, November 16, 2020 2 Wednesday, November 18, 2020 Friday, November 20, 2020 1 Friday, November 20, 2020 Saturday, November 21, 2020 1 Saturday, November 21, 2020 1 Sunday, November 22, 2020 Monday, November 23, 2020 3 Wednesday, November 25, 2020 Saturday, November 28, 2020 3 Saturday, November 28, 2020 1 Wednesday, November 18, 2020 1 Thursday, November 19, 2020 Friday, November 20, 2020 1 Friday, November 20, 2020 Saturday, November 21, 2020 1 Saturday, November 21, 2020 Sunday, November 22, 2020 1 Sunday, November 22, 2020 Monday, November 23, 2020 Wednesday, November 25, 2020 3 Wednesday, November 25, 2020 Saturday, November 28, 2020 3 Thursday, November 19, 2020 Sunday, November 22, 2020 3 Friday, November 27, 2020 1 2 1 Friday, January 01, 2021 2 Saturday, January 02, 2021 51 3 5 Saturday, January 09, 2021 1 1 Sunday, January 17, 2021 1 Sunday, November 08, 2020 Monday, November 09, 2020 Running Head: XYZ INC. INFORMATION SYSTEM IMPROVEMENT 1 XYZ INC. INFORMATION SYSTEM IMPROVEMENT 14 XYZ Inc. Information System Improvement Professor’s Name Student’s Name Course Title Date
Table of Content Page
Project Overview ………………………………………………………………………….3
Steps That Will Be Undertaken in Implementing This Project…………………………….3 Background including current process………………………………………………..……4 Objectives of the Project…………………………………………………………………….4 Goals of the Project…………………………………………………………………………4 Scope of Project ……………………………………………………………………………5 Project Scope Description…………………………………………………………………..5 Constraints and Assumptions ……………………………………………………………….7 Constraints Associated With This Project………………………………………….……….7 Risks ………………………………………………………………………………………..8 Possible Risks Associated with This Project………………………………….…………….8 Scope Control …………………………………………………………….…………………8 How the Scope Will Be Controlled………………………………………………………….8 Relationship to Other Systems/Projects ………………………………………………….…9 Integration with other Systems and Infrastructure………………………………………..…9 Cloud Services………………………………………………………………………………11 Benefits of Cloud Services to XYZ Inc……………………………………………..………11 Definition of Terms ………………………………………………………………..……….12 Relevant Terms…………………………………………………………………….……….12 References…………………………………………………………………………..……….13 1.1 Project Overview
The database system in place will be used as an alternative solution since XYZ Inc. is a starting corporation. This is because the already existing database is not capable of providing solutions when dealing with big data. Thus, accepting the adoption of Big Data Analytics will imply that databases are used to supplement complex operations. This makes cloud computing the best alternative in synchronizing the existing and the upgraded database (Abdel-Basset, Mohamed, & Chang, 2018). The Chief Technology Officer made a suggestion which required that “Rapid Application” needs to be put in place through the “waterfall” technique. The waterfall technique will be utilized because it is among the most conservative approach for new and emerging schemes. To overcome its main challenge of integrating variations, a Rapid method will be put in place. This technique allows the expansion of user data since XYZ Inc.’s business might grow as time goes by. With crowd system development implemented, consumer feedback will be used positively in ensuring that the consumers reflect the smoothness with which the activities are undertaken (Moon et al. 2016).
Steps That Will Be Undertaken in Implementing This Project
The first step will be scope analysis and requirements ration; this will entail scope definition, system requirements analysis, feasibility study, and the generation of the project proposal. System Design; this will involve the preparation of design specification documents, design review, and setting up the development environment. There is also the hardware installation and system development, which will entail the hardware system procurement, hardware system configuration, software installation, and configuration and managing the operating systems (Jiang et al. 2018). There will be testing, training as well as hardware testing stages; these stages will specifically entail the general hardware and software testing, the development of the training materials because the staff will need to be trained on the changes made on the XYZ Inc. information systems to ensure that they don’t get stuck during the system utilization. Finally, there will be a deployment stage, which will entail the determination of the final deployment stage, the technique that will be used in the deployment, and the deployment software to be applied (Jiang et al. 2018).
1.2 Background including current process
Objectives of the Project
The primary goals of this project are; a) To improve the efficiency of service delivery to XYZ Inc. customers. This objective is purposely aimed at increasing the loyalty of the customers to the organization. b) To improve the competitive advantage of XYZ Inc. in the market through enhancing its operational excellence. c) To enhance the customer as well as supplier intimacy besides facilitating the decision-making process.
Goals of the Project
The principle goals of this project include; a) Increasing productivity of XYZ Inc., it’s important to note that nowadays, there are faster central processing units, faster hard drives, as well as faster processors. With these resources, the processing workload is made quicker concerning the already existing ones in XYZ Inc. b) Secondly is to attain higher efficiency besides better data security; the presence of remote access through the mobile devices implies that the sales representatives of XYZ Inc. can take quick take orders while on the road while being aware of the exact delivery timeframe. There is also an enhanced security check-in place, hence reducing the vulnerability of having information stolen or compromised. Data security is the most critical asset of any organization, and that is why organizations tend to invest much in their data heavily. Therefore, XYZ Inc. is one of them and can’t take exception (Williams, & Griffin, 2018). c) Finally is the support of Information Technology; the core of this project implementation is to offer the XYZ Inc. IT department. This is why there was a need for hiring a Chief Technology Officer to facilitate the innovations in the Corporation’s information technology section.
1.3.1 Scope of Project
Project Scope Description
XYZ Inc. is a firm that can be described as new in the industry, even if it has already operated for a while. This Corporation operates in the e-commerce industry. The company comprises of a semi-automated system whose primary function is analyzing its statistics. The firms do not have an information system that is responsible for executing its operations. However, it must be noted that as it grows, the data collected and stored in the company’s servers is exponentially increasing in every department. With almost ten departments now under the umbrella of XYZ Inc., managing to store all the data that flows into the servers from all these departments have become a significant challenge (Tsai, & Lo, 2015). For this reason, this project is aimed at upgrading the current information management system into a more efficient management system that is already compatible with the current system to avoid any inconveniences in the daily business of the company more when it’s looking forward to obtaining a new office block. To prevent the possible complications during the changeover to the new office block, it’s essential that a new automated information system is developed, which will be designed in line with the already existing infrastructure and technology (Mohmmed, & Osman, 2017). The most effective and efficient upgrading technique which will help in the integration of the current information system of XYZ Inc. into the existing alternatives in the market, which will allow for data visualization, as well as reporting with a more centralized system is to make use of cloud services via Office 365. This will be compatible with the company’s current information systems besides offering both online and offline services. The use of cloud services will not only be more economical to XYZ Inc. but more efficient since it will not require any change of software or hardware in the company since it will automatically be compatible with the current information system of the Corporation. Therefore, the upgrading process’s magnitude will be felt in on all the organization’s operations with minimal impact on its budget (Mohmmed, & Osman, 2017). It’s anticipated that upon the completion of this project, XYZ Inc. will save over $0.60 billion annually on its data storage besides increasing the number of employees as well as annual revenue from 10 to and from $5 billion to $30 billion respectively in the coming financial years. The service delivery to the customers will also be significantly improved due to the efficiency in data analysis through the improved system speed. For this project to be effectively implemented there is need to engage the XYZ Inc. shareholder and sponsors for project funding, the departmental heads as well as supervisors for ensuring smooth running of the project activities and training upon execution, and finally, the employees should be made aware of the system upgrade. They must be trained on the few changes on the updates to catch up (Williams, & Griffin, 2018).
1.3.2 Constraints and Assumptions
Constraints Associated With This Project
Five main constraints are associated with this project; these constraints include; Time constraint that is contributed by the support from the chief executive officer, user investment as well as Information System planning. For instance, the chief executive officer of XYZ Inc. may put a time limit for the project to be completed; therefore when it happens so, the project manager will tend to be very much strained in ensuring he or she meets the project time-line (Williams, & Griffin, 2018). The second constraint is financial. This constraint is mainly caused by information system investment in this project. If the information systems investment requires a lot of capital for implementation, it becomes a challenge, hence a constraint. The third constraint is expertise constraint. The expansion of XYZ Inc.’s information system may require extra expertise during its implementation. For instance, XYZ Inc.’s management from the beginning requested for the recruitment of the Chief Technology Officer to facilitate the process of developing an automated information system for the organization. Therefore, bearing in mind XYZ Inc. hasn’t very much advanced in the industry, thus raising the necessary amount that is usually required to hire the expertise becomes a challenge, hence a constraint (Williams, & Griffin, 2018).
1.3.3 Risks
Possible Risks Associated with This Project
There are five main identified risks associated with this project. These risks include; hardware and software failure; this risk may come about as a result of abrupt power loss or even data corruption. The other risk is malware, which comes up as a result of malicious software designed to disrupt computer operation specifically. The third risk is the viruses; these come about when a computer code, for instance, can copy itself and spread from one computer to another, hence disrupting the computer operations. The fourth risk is spam, scams as well as phishing. These come as a result of unsolicited email which seeks to fool computer operators into revealing personal details or even purchasing fraudulent goods. Finally, there is a human error risk resulting from incorrect data processing, careless data disposal, or accidental opening of infected email attachments (Jiang et al. 2018).
1.3.4 Scope Control
How the Scope Will Be Controlled
There are five techniques that I will correctly use to ensure that I effectively control the scope of this project. These techniques include; a) Writing a good scope statement; this will correctly form the boundaries around the limits of the project, hence avoiding going outside the project definitions. b) Definition of the project requirements; these will be generated with the help of a matrix traceability matrix, which will be correctly be used in tracking the changing nature of the elements in the entire project. c) Maintenance of secure communication; this is purposely meant to ensure that there is always an understanding with all the project leaders, the project manager, the project team, and stakeholders. This is because scope creeps usually tend to be inversely proportional to the amount of communication between these key individuals in the project. d) Creating reasonable estimates; will be aimed towards avoiding the tug of war, which usually leads to many frustrations more, especially towards the project execution stage. e) Monitoring of external influences; there is a negative influence from the foreign power of throw monkey, which tends to wrench into the plans of a well and smoothly managed project scopes.
1.3.5 Relationship to Other Systems/Projects
Integration with other Systems and Infrastructure
The database system in place will be used as an alternative solution since XYZ Inc. is a starting corporation. This is because the already existing database is not capable of providing solutions when dealing with big data. Thus, accepting the adoption of Big Data Analytics will imply that databases are used to supplement complex operations. This makes cloud computing the best alternative in synchronizing the existing and the upgraded database (Abdel-Basset, Mohamed, & Chang, 2018). In terms of security, it’s important to note that, in any organization, security remains a domineering aspect in the contemporary world where cyber-security issues are shared among the organization, mainly when activities involve the utilization of data. The information available will be encrypted well so that if unauthorized people access it, it remains pointless. Anti-malware products will also be installed in a situation that will always ensure that vulnerabilities and threats remain regulated (Moon et al. 2016). On networking, we will explicitly rely on CISCO procedures. Information Technology will support the adoption of high-speed networks that will facilitate task execution in the organization. Linksys based routers, together with CISCO, will be utilized, hence helping in define the best kind of system to be implemented (Cisco, 2018). Accessibility and office layout will be given priority more specifically when it comes to Personal Computer arrangements. XYZ Inc. will be supposed to have a 24X seven scope of the entire site. This will allow clients to issue reservations anytime they wish (Jacobsson et al., 2020). In human-computer interaction or interface, Java language will be used with consideration to portable adaptation. All the applications will be accessible using IoS, Android, and windows as well. The requests will be granted descent controls and appealing layout. On the web-design, the best design to apply in this case will be JavaScript and HTML since they give excellent site scheming appearance (Satzinger, Jackson & Burd, 2017). The anticipated website will be comprehensive and will provide real-time updates to XYZ Inc. clients and new users (Jiang et al. 2018).
Cloud Services
Cloud Services refers to those services usually made available to users upon their demand through the internet. These services are made available from the cloud computing provider’s servers rather than from XYZ Inc.’s servers. From the designing point of view, the cloud services are prepared to offer more easy, scalable access to the application, resources besides other facilities. Cloud service providers usually manage these cloud services. Therefore, XYZ Inc. will have to pay for the services upon completion of the system upgrade process. However, the payment will be much less than the expenses incurred in operating its servers, hence economic and efficient. It’s important to note that the implementation of the cloud services will not cost XYZ Inc. anything since the software and the cloud provider will provide the hardware necessary for the upgrade. There will be no need for XYZ Inc. either to allocate Information Technology staff in managing the service. Everything will be left with the cloud service provider (Williams, & Griffin, 2018).
Benefits of Cloud Services to XYZ Inc.
From research, there is an identified solution that can be used in data analysis as well as storage without any threat in data security. The answer is to make use of cloud computing services. In this cloud services, first, the data is not stored in the XYZ Inc. servers, the collection, as well as processed information, is transmitted in an encrypted form to the cloud provider’s servers. The cloud providers are mandated to ensure that all the data in their servers is secured from any threat. Also, the cloud providers’ servers store information from various organizations in a segmented form. This implies that even the data owners like XYZ Inc. can’t precisely know which server is carrying their data, but they can access it through a highly secured internet channel. This is much economical to XYZ Inc. in terms of data storage, data security, and data management by hiring the data expert individuals. With cloud services, all these expenses are eradicated from the information management system budgetary of XYZ Inc. (Abdel-Basset, Mohamed, & Chang, 2018).
1.3.6 Definition of Terms
Relevant Terms
Information; refers to the processed data which is ready to be consumed or utilized. Systems: these are set of equipment working together via following the instructions as the input to give an output. Information system; this refers to the information and communication technology used by XYZ Inc. or any other organization in carrying out their daily businesses.
References:
Abdel-Basset, M., Mohamed, M., & Chang, V. (2018). NMCDA: A framework for evaluating cloud computing services. Future Generation Computer Systems, 86, 12-29. Chan, J. O. (2018). Customer Knowledge Management In the Cloud Ecosystem. Communications of the IIMA, 16(2), 3. Fu, Z., Sun, X., Liu, Q., Zhou, L., & Shu, J. (2015). Achieving efficient cloud search services: multi-keyword ranked search over encrypted cloud data supporting parallel computing. IEICE Transactions on Communications, 98(1), 190-200. Jaisinghani, D. R. (2016). U.S. Patent No. 9,442,810. Washington, DC: U.S. Patent and Trademark Office. Jacobsson, S., Arnäs, P. O., & Stefansson, G. (2020). Automatic information exchange between interoperable information systems: Potential improvement of access management in a seaport terminal. Research in Transportation Business & Management, 100429. Retrieved from https://www.sciencedirect.com/science/article/pii/S2210539519302123 Jiang, Q., Chen, Z., Li, B., Shen, J., Yang, L., & Ma, J. (2018). Security analysis and improvement of bio-hashing based three-factor authentication scheme for telecare medical information systems. Journal of Ambient Intelligence and Humanized Computing, 9(4), 1061-1073. Retrieved from https://link.springer.com/article/10.1007/s12652-017-0516-2 Moon, J., Choi, Y., Kim, J., & Won, D. (2016). An improvement of robust and efficient biometrics-based password authentication scheme for telecare medicine information systems using extended chaotic maps. Journal of medical systems, 40(3), 70. Retrieved from https://link.springer.com/article/10.1007%2Fs10916-015-0422-0 Mohmmed, A. G. M. & Osman, S. E. F. (2017). Cloud Computing & Big Data challenges & Security Challenges. World, 3(6). Qu, H., & Wang, Y. P., (2015). U.S. Patent No. 9,223,860. Washington, DC: U.S. Patent and Trademark Office. >Sheet 0
0-Sep-20
-Aug-20
-Aug-20
2 12 -Aug-20
-Sep-20
-Sep-20
5 -Sep-20
-Sep-20
1 1 4-Oct-20 1 1 8-Oct-20 1 9-Oct-20 12 10-Oct-20 2 -Oct-20
-Oct-20
3 -Oct-20
4 31-Oct-20 2 1 8-Nov-20 7 1 -Nov-20
system
2 2 -Nov-20
1 2 1 28-Nov-20 16 29 1 1 24-Sep-20 25-Sep-20 9 8-Oct-20 5 53 3 25-Oct-20 28-Oct-20 5 28-Oct-20 3 4-Nov-20 7-Nov-20 62 Hardware Testing 9 7-Nov-20 1 7-Nov-20 8-Nov-20 1 8-Nov-20 9-Nov-20 2 11-Nov-20 1 15-Nov-20 16-Nov-20 2 18-Nov-20 20-Nov-20 1 20-Nov-20 21-Nov-20 1 21-Nov-20 1 22-Nov-20 23-Nov-20 3 25-Nov-20 28-Nov-20 3 28-Nov-20 1 18-Nov-20 1 19-Nov-20 20-Nov-20 1 20-Nov-20 21-Nov-20 1 21-Nov-20 22-Nov-20 1 22-Nov-20 23-Nov-20 25-Nov-20 3 25-Nov-20 28-Nov-20 3 19-Nov-20 22-Nov-20 3 1 2 1 1-Jan-21 2 2-Jan-21 51 3 5 9-Jan-21 1 1 17-Jan-21 1 8-Nov-20 9-Nov-20 1 Information Technology Upgrading and Expansion Plan 60 1-Aug-20 Gantt Chart
Start Information Technology Upgrading and Expansion Plan Scope Analysis and Requirements ration System Design Hardware Installation and system development Testing Training Hardware Testing Software Testing Implementation Deployment Expansion Plan Completed 44044 44099 44114 44146 44099 44129 44142 44146 44160 44508 44143 Duration Information Technology Upgrading and Expansion Plan Scope Analysis and Requirements ration System Design Hardware Installation and system development Testing Training Hardware Testing Software Testing Implementation Deployment Expansion Plan Completed 60 5 12 7 16 53 9 5 153 51 1 RunningHead: Project Deliverable 3 Project Deliverable 3
Project Deliverable 3: Database and Programming Design
Student’s name
Professor’s name
Course title
Date
Table of Contents 4 Section 1: Design Document The availability of an acceptable schema for the database allows the company involved handle their enterprise with minimal internal capital. For the company’s overall impact an appropriate database scheme has been involved in this project plan. The database architecture required for the present company involves the transitional ( Hoffer et al, 2016). The goods that the business offers on its e-commerce site are provided by the corporation’s reputable suppliers. Such goods are held in the firm’s inventory. Details of the specific commodity provide
Figure 1: Database Schema
(Source: Created by Learner) The corresponding Server Schemas allows to establish a specific data management system within the company (Pavlo et al, 2017). The new information system contains Supplier Information, Item Info, Stock Data, Order Details, and User Info intermediate sections. These software components are described below pertaining to the database schema: The corporation’s reputable vendors are specified in the database along with information of the Supplier Name, Supplier ID, Supplier Address, Distribution Rate and Brand ID. Supplier ID’s characteristic is known as the special distinguishing feature (Patil et al. 2018). Each company commodity is distributed to the client from numerous reputable sources to distributors. The corporation holds a significant range of diversified goods for the company’s market gain (Noll et al, 2019). Consumer information are provided in the client inventory in terms of their characteristics and include The items are processed in the warehouse before being shipped according to the criteria to the consumer address (Poerner & Winkelmann, 2017). This transient inventory holding of goods is conducted utilizing the associated attributes of The organization derives the share of income from the goods offered to the clients (Lu & Holubová, 2017). This drug sales purchases are registered in the database using the Purchasing Date, Purchasing Type, Company Type and Consumer ID attributes. A product’s consumer records are used in the business database on the basis of the actual customer information (Prananosa, 2019). This specific information include Consumer Name, Customer ID, Customer Address, Last Sales Number and Order Number. Depending on the correct Customer ID and last Transaction Amount, the business managers recognize the faithful customers. Under the database architecture, the appropriate Database tables are generated to store information linked to the various database objects. The tables of the server store the necessary details in terms of special entity specific attributes. Unique identification of entities is performed using Primary core theoretical element. The key value is described as a characteristic that has a significant value for quick recognition of the entity involved (Peñaherrera, 2018). The Supplier ID identifier is included in the actual database design for distinguishing vendors from the database system. Referential honesty is used in the software cycle planning for the company’s ultimate market benefit. As per description, a database’s contextual honesty is characterized as the value of the data state that it is linked to the authenticity of the public databases (Hingorani, 2017).
Figure 2: Database Tables
(Source: Created by Learner)
The existing database object contains Manufacturer Information, Commodity Descriptions, Production Information, and Purchase Details. In terms of the available key present in each independent relational database, each of these tables is linked to each other (Amin et al, 2019). The primary key is listed as Supplier ID in the Server Table of Supplier Information. That is because the significance of the Supplier ID is determined to be specific by default. The Foreign Key concerned is known as Brand ID. That is since the special meaning of Commodity ID from Product Descriptions is used to scan for a manufacturer and the supplier’s matching items. The Primary Key of Commodity Information Database Table is Commodity ID and the International Key is Manufacturer ID. Product ID value for the particular product selection is classified as special (Sharma, 2017). Business executives use the special benefit of Supplier ID to recognize the goods provided by specific suppliers. The preferred key of Import Information Server Table is known to be Item ID, and the Supplier ID is defined as Foreign Key. Brand ID’s primary key feature is given a special meaning as to its successful recognition. The Foreign Key connected to the Supplier ID is used by stakeholders of the company to monitor the supplied goods and is currently deposited in the company warehouse. The main key of Purchase Information Server Table is known to be Purchase ID. On the opposite, the related International Keys are classified as Brand ID and Consumer ID. A special attribute is provided in the main key of Purchase ID (Papenbrock & Naumann, 2017). In comparison, the Company ID and Consumer ID International Keys are linked to defining a particular sales process between the client and the commodity. The main key of customer information relational database is recognized as Customer ID and the linked Foreign Key is recognized as the Purchase ID. Customer ID’s main key is assigned with and uniquely identifies value. The accompanying Customer ID International Key is used to successfully connect to their unique transactions of an item.
Recognition of characteristics as main key in a related table maintains the contextual validity in a data base list. These unique constraint attributes are further listed in specific tables as International Keys (Győrödi, 2016). The main keys are used for the exclusive recognition of an item in the database. The primary keys are used to discover the common connection among a database table entities. Within this database table, the server managers are instructed by business members to lock the Primary Key feature in the database table in order to prevent editing risks. To the commercial advantage of the client, the intermediary database tables for the construction of databases are entitled to the normalization process (Tyagi & Singh, 2017). Supplier Details Supplier Name Supplier ID Supplier Address Frequency of Supply Product ID
Table 1: Supplier Details
(Source: Created by Learner)
Supplier Details Supplier Name Supplier ID Supplier Address
Table 2: Normalized Form
(Source: Created by Learner) Supplier Details Supplier ID Frequency of Supply Product ID
Table 3: Normalized Form
(Source: Created by Learner)
Product Details Product Name Product ID Price Supplier ID
Table 4: Product Details
(Source: Created by Learner)
Normalized Form in 3NF Product Details Product Name Product ID
Table 5: Normalized Form
(Source: Created by Learner) Product Details Product ID Price Supplier ID
Table 6: Normalized Form
(Source: Created by Learner)
Inventory Details Product ID Product Name Stock Status Reinforcement Date Supplier ID Last Order Placed
Table 7: Inventory Details
(Source: Created by Learner)
Normalized Form in 3NF Inventory Details Product ID Product Name Stock Status Last Order Placed
Table 8: Normalized Form
(Source: Created by Learner) Inventory Details Product ID Supplier ID Reinforcement Date
Table 9: Normalized Form
(Source: Created by Learner)
Purchase Details Purchase Date Purchase ID Product ID Customer ID
Table 10: Purchase Details
(Source: Created by Learner)
Normalized Form in 3NF Purchase Details Product ID Product Name Stock Status Last Order Placed
Table 11: Normalized Form
(Source: Created by Learner) Purchase Details Product ID Supplier ID Reinforcement Date
Table 12: Normalized Form
(Source: Created by Learner)
Customer Details Customer Name Customer ID Customer Address Last Purchase Amount Purchase ID
Table 13: Customer Details
(Source: Created by Learner)
Normalized Form in 3NF Customer Details Customer Name Customer ID Customer Address
Table 14: Normalized Form
(Source: Created by Learner) Customer Details Customer ID Last Purchase Amount Purchase ID
Table 15: Normalized Form
(Source: Created by Learner)
The Entity-Relationship (ER) Diagram is utilized in renowned organizations for the configuration of the gain framework (Burke, 2017). Both diagrams show the root of the data inside the database architecture, and its corresponding path. This ERD requires the involvement of multiple data providers within the framework of the database. Supplier Information, Item Info, Stock Data, Order Details, and Consumer Info are assumed data points within database architecture. Such data points relate to the Suppliers, Goods, Supply, Order, and Consumer divisions involved (Hoffer, 2016). The output of the related data is inserted into a server using a correct markup language.
[Referred to Appendix 2]
The Data Flow Diagram (DFD) collection means that the appropriate data flow can be traced from its reference to the endpoint (Elmasri & Navathe, 2017). Such data flow analysis is useful in terms of market prospects for the respective client. create database company_name; use company_name; create table customers ( Customers_ID int not null, Customers_Name varchar(255) not null, Customers_Address varchar(255), Customers_Last_Purchase_Amount int, Purchase_ID int, );
Figure 4: Table Creation
(Source: Created by Learner)
Figure 5: Insertion of Data into Table
(Source: Created by Learner)
The implementation of successful database architecture improves the enterprise’s total market profit. Appropriate software implementations are created by related managers to handle the overall volume of data produced in the organization.
Books
Hoffer, J. A., Ramesh, V., & Topi, H. (2016). Modern database management (p. 600). London: Pearson. Elmasri, R., & Navathe, S. (2017). Fundamentals of database systems (Vol. 7). London: Pearson.
Journals
Pavlo, A., Angulo, G., Arulraj, J., Lin, H., Lin, J., Ma, L., Menon, P., Mowry, T.C., Perron, M., Quah, I. and Santurkar, S., 2017, January. Self-Driving Database Management Systems. In CIDR (Vol. 4, p. 1). Patil, N. S., Kiran, P., Kiran, N. P., & KM, N. P. (2018). A survey on graph database management techniques for huge unstructured data. International Journal of Electrical and Computer Engineering, 8(2), 1140. Noll, S., May, N., Böhm, A., Mühlig, J., & Teubner, J. (2019). From the Application to the CPU: Holistic Resource Management for Modern Database Management Systems. IEEE Data Eng. Bull., 42(1), 10-21. Poerner, N., & Winkelmann, R. (2017). Interfacing the BAS speech science web services and the EMU speech database management system. Preface & Acknowledgements, 141. Lu, J., & Holubová, I. (2017, March). Multi-model Data Management: What’s New and What’s Next?. In EDBT (Vol. 17, pp. 602-605). Prananosa, A. G., Wahyudi, M., & Widodo, S. E. (2019). Model Development of School Database Management Information System. OSF Preprints. January, 13, pp.1-10. Peñaherrera, F., Reinhardt, R., & Kousaiti, A. (2018). Conceptual design for data flow for a database management system for the sustainable recovery of critical metals from waste electrical and electronic equipment. Global NEST Journal, 20(4), 700-705. Hingorani, K., Gittens, D., & Edwards, N. (2017). Reinforcing Database Concepts by Using Entity Relationships Diagrams (ERD) and Normalization Together For Designing Robust Databases. Issues in Information Systems, 18(1), 148-155. Amin, M., Romney, G. W., Dey, P., & Sinha, B. (2019). Teaching Relational Database Normalization in an Innovative Way. The Journal of Computing Sciences in Colleges, 48. Sharma, N. (2017). Overview of the Database Management System. International Journal of Advanced Research in Computer Science, 8(4), pp.1-14. Papenbrock, T., & Naumann, F. (2017). Data-driven Schema Normalization. In EDBT (Vol. 17, pp. 342-353). Győrödi, C., Győrödi, R., Ștefan, A., & Bandici, L. (2016). A Comparative Study of Databases with Different Methods of Internal Data Management. Database, 7(4), pp.1-8. Tyagi, N., & Singh, N. (2017). Comparative Analysis of Graph Database and a Relational Database. M. Tech Scholar1, Assistant Professor2 Dept of Computer Science & Engineering GEU Dehradun, India, IJESC, 7, pp.1-8.
Online Articles
Burke, E. (2017). Database Management Systems–Kernel. Database Systems, 381. (Source: Created by Learner)
(Source: Created by Learner) Section 2: Project Gantt Chart
Figure 1: Gantt Chart
(Source: Created by Learner) The database design requires an advance planning process which involves the selection of an appropriate database management system. The existing database was created after the project planning process integrated the appropriate ERD and DFD diagram.
Information Technology Upgrading and Expansion Plan Analysis Scope Analysis and Requirements ration System Design Hardware Installation and system development Testing Training Hardware Testing Software Testing Implementation Development Deployment Expansion Plan Completed 44044 44046 44099 44114 44146 44099 44129 44142 44146 44160 44160 44508 44143 Duration Information Technology Upgrading and Expansion Plan Analysis Scope Analysis and Requirements ration System Design Hardware Installation and system development Testing Training Hardware Testing Software Testing Implementation Development Deployment Expansion Plan Completed 60 15 5 12 7 16 53 9 5 153 30 51 1 >Sheet 1 0
0-Sep-20
/Hardware Requirements
-Aug-20
-Aug-20
12 -Aug-20
-Sep-20
-Sep-20
3 3-Aug-20 6-Aug-20 5 7-Aug-20 -Aug-20
6 -Aug-20
1 16-Aug-20 -Aug-20
5 -Sep-20
-Sep-20
1 1 4-Oct-20 1 1 8-Oct-20 1 9-Oct-20 12 10-Oct-20 2 -Oct-20
-Oct-20
3 -Oct-20
4 31-Oct-20 2 1 8-Nov-20 7 1 system
2 21-Nov-20 2 -Nov-20
1 1 28-Nov-20 -Nov-20
16 1 1 24-Sep-20 25-Sep-20 9 8-Oct-20 5 3 25-Oct-20 28-Oct-20 5 28-Oct-20 3 4-Nov-20 7-Nov-20 Hardware Testing 9 7-Nov-20 1 7-Nov-20 8-Nov-20 1 8-Nov-20 9-Nov-20 2 11-Nov-20 Configure hardware 2 13-Nov-20 1 15-Nov-20 16-Nov-20 2 18-Nov-20 20-Nov-20 1 20-Nov-20 21-Nov-20 1 21-Nov-20 1 22-Nov-20 23-Nov-20 3 25-Nov-20 28-Nov-20 3 28-Nov-20 Software Testing 5 11-Nov-20 16-Nov-20 1 18-Nov-20 1 19-Nov-20 20-Nov-20 1 20-Nov-20 21-Nov-20 1 21-Nov-20 22-Nov-20 1 22-Nov-20 23-Nov-20 25-Nov-20 3 25-Nov-20 28-Nov-20 3 19-Nov-20 22-Nov-20 3 1 2 1 1-Jan-21 2 2-Jan-21 30 25-Nov-20 10 25-Nov-20 5-Dec-20 5 2 8 51 3 5 9-Jan-21 1 1 17-Jan-21 1 8-Nov-20 9-Nov-20 Information Technology Upgrading and Expansion Plan Analysis Scope Analysis and Requirements ration System Design Hardware Installation and system development Testing Training Hardware Testing Software Testing Implementation Development Deployment Expansion Plan Completed 44044 44046 44099 44114 44146 44099 44129 44142 44146 44160 44160 44508 44143 Duration Information Technology Upgrading and Expansion Plan Analysis Scope Analysis and Requirements ration System Design Hardware Installation and system development Testing Training Hardware Testing Software Testing Implementation Development Deployment Expansion Plan Completed 60 15 5 12 7 16 53 9 5 153 30 51 1
2
1
PROJECT PLAN
ID
Task Name
Duration (in days)
Start
Finish
Predecessors
1
Information Technology Upgrading and Expansion Plan
6
Saturday, August 01,
20
Wednesday, September
3
2
Identify the Scope
5
Thursday, August 06, 2020
3
Analysis/Hardware Requirements
10
Wednesday, August
12
Saturday, August
22
4
Design
Saturday, August
2
9
Thursday, September 10, 2020
8
5
Hardware Installation and Configuration
7
Wednesday, September
16
Wednesday, September
23
18
6
Scope Analysis and Requirements ration
Friday, September
25
Wednesday, September
30
29
7
Define the scope
Saturday, October 03, 2020
Sunday, October 04, 2020
36
8
Analyze the system requirements
Monday, October 05, 2020
37
9
Conduct Feasibility Study
Wednesday, October 07, 2020
Thursday, October 08, 2020
38
10
Preliminary project plan and project proposal
Friday, October 09, 2020
39
11
Project plan complete
Saturday, October 10, 2020
40
12
System Design
Thursday, October 22, 2020
41
13
Prepare design specification document
Monday, October
26
Wednesday, October
28
42
14
Design Review
Wednesday, October 28, 2020
Saturday, October
31
43
15
Revise documents
Wednesday, November 04, 2020
44
16
Set up development environment
Friday, November 06, 2020
Sunday, November 08, 2020
45
17
Design Process complete
Monday, November 09, 2020
46
18
Hardware Installation and system development
Wednesday, November 11, 2020
Wednesday, November 18, 2020
47
19
Hardware System Procurement
Friday, November 20, 2020
Saturday, November
21
48
20
Configure hardware
Saturday, November 21, 2020
Monday, November 23, 2020
49
21
Software Installation
Wednesday, November 25, 2020
Friday, November
27
50
22
Configure and Manage Operating Systems
Friday, November 27, 2020
Saturday, November 28, 2020
51
23
Installation Completion
Sunday, November 29, 2020
52
24
Testing
Friday, September 25, 2020
Sunday, October 11, 2020
25
Develop unit test plans using product specifications
Wednesday, September 23, 2020
Thursday, September 24, 2020
53
26
Develop integration test plans using product specifications
55
27
Hardware Testing
Tuesday, September 29, 2020
56
28
Software Testing
Sunday, October 18, 2020
Friday, October 23, 2020
54
29
Training
Sunday, October 25, 2020
Thursday, December 17, 2020
60
30
Develop test plans
62
31
Develop user training materials
Monday, November 02, 2020
63
32
Schedule trainings
Saturday, November 07, 2020
33
Monday, November 16, 2020
64
34
Review hardware components
35
Test component modules to product specifications
66
36
Identify anomalies to product specifications
Friday, November 13, 2020
67
37 Configure hardware 2 Friday, November 13, 2020
Sunday, November 15, 2020
68
38
Re-test configured hardware
69
39
Hardware testing complete
70
40
Develop training specifications for end users
65
41
Develop training specifications for help desk support staff
Sunday, November 22, 2020
72
42
Finalize training materials
73
43
Signoffs
74
44
Get signoffs on the plans and deliverables
Tuesday, December 01, 2020
75
45 Software Testing 5 Wednesday, November 11, 2020 Monday, November 16, 2020
76
46
Develop the test cases
Thursday, November 19, 2020
77
47
Unit Testing
78
48
Integrating Testing
79
49
Functionality Testing
80
50
Testing Evaluation
81
51
Implementation
153
Tuesday, April 27, 2021
82
52
Implement changes suggested in system
83
53
Component Design implementation
84
54
Implementation starts
Tuesday, November 24, 2020
85
55
Assessment Evaluation
Sunday, December 27, 2020
Monday, December 28, 2020
86
56
System evaluation
Wednesday, December 30, 2020
Friday, January 01, 2021
87
57
Prepare user manual
Saturday, January 02, 2021
88
58
User sign-offs
Monday, January 04, 2021
89
59
Deployment
Monday, November 08, 2021
Wednesday, December 29, 2021
61
60
Determine final deployment strate
Wednesday, January 06, 2021
Saturday, January 09, 2021
61
gyDevelop deployment methodolog
Thursday, January 14, 2021
92
62
yDeploy software
Saturday, January 16, 2021
Sunday, January 17, 2021
93
63
Deployment complete
Monday, January 18, 2021
94
64
Expansion Plan Completed
95
The Chief Technology Officer made a suggestion which required that “Rapid Application” needs to be put in place through the “waterfall” technique. The waterfall technique will be utilized because it is among the most conservative approach for new and emerging schemes. To overcome its main challenge of integrating variations, a Rapid method will be put in place. This technique allows the expansion of user data since XYZ Inc.’s business might grow as time goes by. With crowd system development implemented, consumer feedback will be used positively in ensuring that the consumers reflect the smoothness with which the activities are undertaken (Moon et al. 2016).
2
1
PROJECT PLAN
ID
Task Name
Duration (in days)
Start
Finish
Predecessors
1
Information Technology Upgrading and Expansion Plan
6
1-Aug-
20
3
2
Identify the Scope
5
1-Aug-20
6-Aug-20
3
Analysis/Hardware Requirements
10
12
22
4
Design
2
9
10-Sep-20
8
5
Hardware Installation and Configuration
7
23
24
18
6
Scope Analysis and Requirements ration
25
30
29
7
Define the scope
3-Oct-20
4-Oct-20
36
8
Analyze the system requirements
5-Oct-20
37
9
Conduct Feasibility Study
7-Oct-20
8-Oct-20
38
10
Preliminary project plan and project proposal
9-Oct-20
39
11
Project plan complete
10-Oct-20
40
12
System Design
22-Oct-20
41
13
Prepare design specification document
26
28
42
14
Design Review
28-Oct-20
31
43
15
Revise documents
4-Nov-20
44
16
Set up development environment
6-Nov-20
8-Nov-20
45
17
Design Process complete
9-Nov-20
46
18
Hardware Installation and system development
11-Nov-20
18-Nov-20
47
19
Hardware System Procurement
20-Nov-20
21
48
20
Configure hardware
21-Nov-20
23-Nov-20
49
21
Software Installation
25-Nov-20
27
50
22
Configure and Manage Operating Systems
7-Nov-20
28-Nov-20
51
23
Installation Completion
29-Nov-20
52
24
Testing
25-Sep-20
11-Oct-20
25
Develop unit test plans using product specifications
23-Sep-20
24-Sep-20
53
26
Develop integration test plans using product specifications
55
27
Hardware Testing
29-Sep-20
56
28
Software Testing
18-Oct-20
23-Oct-20
54
29
Training
25-Oct-20
17-Dec-20
60
30
Develop test plans
62
31
Develop user training materials
2-Nov-20
63
32
Schedule trainings
33
16-Nov-20
64
34
Review hardware components
35
Test component modules to product specifications
66
36
Identify anomalies to product specifications
13-Nov-20
67
37 Configure hardware 2 13-Nov-20
15-Nov-20
68
38
Re-test configured hardware
69
39
Hardware testing complete
70
40
Develop training specifications for end users
65
41
Develop training specifications for help desk support staff
22-Nov-20
72
42
Finalize training materials
73
43
Signoffs
74
44
Get signoffs on the plans and deliverables
1-Dec-20
75
45 Software Testing 5 11-Nov-20 16-Nov-20
76
46
Develop the test cases
19-Nov-20
77
47
Unit Testing
78
48
Integrating Testing
79
49
Functionality Testing
80
50
Testing Evaluation
81
51
Implementation
153
27-Apr-21
82
52
Implement changes suggested in system
83
53
Component Design implementation
84
54
Implementation starts
24-Nov-20
27-Nov-20
85
55
Assessment Evaluation
27-Dec-20
28-Dec-20
86
56
System evaluation
30-Dec-20
1-Jan-21
87
57
Prepare user manual
2-Jan-21
88
58
User sign-offs
4-Jan-21
89
59
Deployment
8-Nov-21
29-Dec-21
61
60
Determine final deployment strate
6-Jan-21
9-Jan-21
61
gyDevelop deployment methodolog
14-Jan-21
92
62
yDeploy software
16-Jan-21
17-Jan-21
93
63
Deployment complete
18-Jan-21
94
64
Expansion Plan Completed
95
Task Name Duration (in days) Start Finish
30-Sep-20
6 Scope Analysis and Requirements ration 5 25-Sep-20 30-Sep-20
12 System Design 12 10-Oct-20 22-Oct-20
18 Hardware Installation and system development 7 11-Nov-20 18-Nov-20
24 Testing 16 25-Sep-20 11-Oct-20
29 Training 53 25-Oct-20 17-Dec-20
33 Hardware Testing 9 7-Nov-20 16-Nov-20
45 Software Testing 5 11-Nov-20 16-Nov-20
51 Implementation 153 25-Nov-20 27-Apr-21
59 Deployment 51 8-Nov-21 29-Dec-21
64 Expansion Plan Completed 1 8-Nov-20 9-Nov-20
1
3
Section 1: Design Document
Introduction 4
a. Creation of Database Schema 4
b. Explanation of Database Schema 5
Supplier Details 6
Product Details 6
Inventory Details 6
Purchase Details 6
Customer Details 6
c. Creation of Database Tables 7
Identification of Foreign Keys and Primary Keys 8
Fulfillment of Referential Integrity in Database Table 9
d. Database Normalization 9
Supplier Details Database Table 9
Normalized Form in 3NF 9
Product Details Database Table 10
Normalized Form in 3NF 10
Inventory Details Database Table 10
Normalized Form in 3NF 11
Purchase Details Database Table 11
Normalized Form in 3NF 11
Customer Details Database Table 12
Normalized Form in 3NF 12
e. Entity-Relationship Diagram 12
f. Rationale for ERD 12
g. DFD 13
h. Rationale for DFD 13
i. Sample Queries 13
Query for Customer Table Creation 13
Query for Data Entry into Customer Table 13
j. Screen Layouts 13
Layout for Database Creation 13
Layout for Data Entry into Database 14
Conclusion 14
Reference List 15
Appendices 17
Appendix 1: ERD 17
Appendix 2: DFD 18
Section 2: Project Gantt Chart 20
Introduction
a. Creation of Database Schema
Consumer Information, quantitative Information, and supplier evaluation modules
. The purpose of this database is to provide consumer and manufacturer information related to the business in terms of the numbers of stock and service revenue
Product Name, Product ID and Product Price,
as well as applicable manufacturer information. The Supplier Specifics often provide
Supplier Name, Supplier ID and Supplier Address
. Such stored goods are delivered to the consumer’s address as defined in the order according to their specifications (Elmasri & Navathe, 2017). The related consumer records that are recorded in the business database contain
customer name, customer ID
and descriptions of transactions. All sensitive records are grouped within the archive, in a hierarchical format.
b. Explanation of Database Schema
Supplier Details
Product Details
Brand Title, Product ID, Cost, and Supplier ID
. Such characteristics aid with tracking suppliers’ commodity distribution and procurement.
Inventory Details
Product Type, Model Number, Stock Position, Date of Replacement, Supplier Type, and Last Order Put.
Purchase Details
Customer Details
c. Creation of Database Tables
Identification of Foreign Keys and Primary Keys
Fulfillment of Referential Integrity in Database Table
d. Database Normalization
Supplier Details Database Table
Normalized Form in 3NF
Product Details Database Table
Inventory Details Database Table
Purchase Details Database Table
Customer Details Database Table
e. Entity-Relationship Diagram
[Referred to Appendix 1]
f. Rationale for ERD
g. DFD
h. Rationale for DFD
i. Sample Queries
Query for Customer Table Creation
Query for Data Entry into Customer Table
j. Screen Layouts
Layout for Database Creation
Layout for Data Entry into Database
Conclusion
Reference List
Appendices
Appendix 1: ERD
Appendix 2: DFD
2
1
Information Technology Upgrading and Expansion Plan
6
1-Aug-
20
3
2
Identify the Scope
5
1-Aug-20
6-Aug-20
3
Analysis
10
12
22
4
Design
2
9
10-Sep-20
5
Hardware Installation and Configuration
7
23
24
6 Analysis
15
3-Aug-20
1
7-Aug-20
7
Initial Meetings
8
Discussion and Stakeholders
11
9
Document current systems
12-Aug-20
16
10
Analysis Complete
17
11
Scope Analysis and Requirements ration
25
30
12
Define the scope
3-Oct-20
4-Oct-20
13
Analyze the system requirements
5-Oct-20
14
Conduct Feasibility Study
7-Oct-20
8-Oct-20
15
Preliminary project plan and project proposal
9-Oct-20
16
Project plan complete
10-Oct-20
17
System Design
22-Oct-20
18
Prepare design specification document
26
28
19
Design Review
28-Oct-20
31
20
Revise documents
4-Nov-20
21
Set up development environment
6-Nov-20
8-Nov-20
22
Design Process complete
9-Nov-20
23
Hardware Installation and system development
11-Nov-20
18-Nov-20
24
Hardware System Procurement
20-Nov-20
21-Nov-20
25
Configure hardware
23-Nov-20
26
Software Installation
25-Nov-20
27
27
Configure and Manage Operating Systems
2
7-Nov-20
28-Nov-20
28
Installation Completion
29
29
Testing
25-Sep-20
11-Oct-20
30
Develop unit test plans using product specifications
23-Sep-20
24-Sep-20
31
Develop integration test plans using product specifications
32
Hardware Testing
29-Sep-20
33
Software Testing
18-Oct-20
23-Oct-20
34
Training
53
25-Oct-20
17-Dec-20
35
Develop test plans
36
Develop user training materials
2-Nov-20
37
Schedule trainings
38
16-Nov-20
39
Review hardware components
40
Test component modules to product specifications
41
Identify anomalies to product specifications
13-Nov-20
42
15-Nov-20
43
Re-test configured hardware
44
Hardware testing complete
45
Develop training specifications for end users
46
Develop training specifications for help desk support staff
22-Nov-20
47
Finalize training materials
48
Signoffs
49
Get signoffs on the plans and deliverables
1-Dec-20
50
51
Develop the test cases
19-Nov-20
52
Unit Testing
53
Integrating Testing
54
Functionality Testing
55
Testing Evaluation
56
Implementation
153
27-Apr-21
57
Implement changes suggested in system
58
Component Design implementation
59
Implementation starts
24-Nov-20
27-Nov-20
60
Assessment Evaluation
27-Dec-20
28-Dec-20
61
System evaluation
30-Dec-20
1-Jan-21
62
Prepare user manual
2-Jan-21
63
User sign-offs
4-Jan-21
64
Development
2
5-Dec-20
65
Develop system modules
66
Integrate system modules
6-Dec-20
10-Dec-20
67
Perform initial testing
11-Dec-20
13-Dec-20
68
Development complete
14-Dec-20
21-Dec-20
69
Deployment
8-Nov-21
29-Dec-21
70
Determine final deployment strategy
6-Jan-21
9-Jan-21
71
Develop deployment methodology
14-Jan-21
72
Deploy software
16-Jan-21
17-Jan-21
73
Deployment complete
18-Jan-21
74
Expansion Plan Completed
Task Name
Duration (in days)
Start
Finish
Information Technology Upgrading and Expansion Plan 60 1-Aug-20
30-Sep-20
Analysis 15 3-Aug-20
17-Aug-20
Scope Analysis and Requirements ration 5 25-Sep-20 30-Sep-20
System Design 12 10-Oct-20 22-Oct-20
Hardware Installation and system development 7 11-Nov-20 18-Nov-20
Testing 16 25-Sep-20 11-Oct-20
Training 53 25-Oct-20 17-Dec-20
Hardware Testing 9 7-Nov-20 16-Nov-20
Software Testing 5 11-Nov-20 16-Nov-20
Implementation 153 25-Nov-20 27-Apr-21
Development 30 25-Nov-20
25-Dec-20
Deployment 51 8-Nov-21 29-Dec-21
Expansion Plan Completed 1 8-Nov-20 9-Nov-20