Information Systems Deliverable
Capstone2020
Documentation_All.zipGantt Chart_Copy.xlsx
Gantt Chart
| Project Name | Online Inventory Development Project | ||
| Project Duration | 86 | ||
| Project Start Date | 4-Jan-21 | ||
| Project End Date | 31-Mar-21 | ||
| Start Date | Duration | End Date | |
| Planning Phase | |||
| System Request | 4-Jan | 11 | 15-Jan-21 |
| Feasibility Analysis | 5-Jan | 8 | 13-Jan-21 |
| Gantt Chart | 14-Jan | 6 | 20-Jan-21 |
| Requirements Definition | 15-Jan | 13 | 28-Jan-21 |
| Data Flow Diagram | 20-Jan | 9 | 29-Jan-21 |
| Use Cases | 20-Jan | 9 | 29-Jan-21 |
| Acquisition Strategy | 1-Feb | 8 | 9-Feb-21 |
| Entity-relationship Design | 5-Feb | 7 | 12-Feb-21 |
| Protoypes/Mockups | 15-Feb | 4 | 19-Feb-21 |
| Input/Output Design | 17-Feb | 5 | 22-Feb-21 |
| Architecture Design | 16-Feb | 10 | 26-Feb-21 |
| Hardware and Software Specification | 22-Feb | 10 | 4-Mar-21 |
| Testing | 4-Mar | 19 | 23-Mar-21 |
| Documentation | 22-Mar | 4 | 26-Mar-21 |
| Migration and Conversion | 24-Mar | 7 | 31-Mar-21 |
Online Inventory Development Project
Start Date System Request Feasibility Analysis Gantt Chart Requirements Definition Data Flow Diagram Use Cases Acquisition Strategy Entity-relationship Design Protoypes/Mockups Input/Output Design Architecture Design Hardware and Software Specification Testing Documentation Migration and Conversion 44200 44201 44210 44211 44216 44216 44228 44232 44242 44244 44243 44249 44259 44277 44279 Duration System Request Feasibility Analysis Gantt Chart Requirements Definition Data Flow Diagram Use Cases Acquisition Strategy Entity-relationship Design Protoypes/Mockups Input/Output Design Architecture Design Hardware and Software Specification Testing Documentation Migration and Conversion 11 8 6 13 9 9 8 7 4 5 10 10 19 4 7
__MACOSX/._Gantt Chart_Copy.xlsx
Inventory Management System.pptx
Online Inventory Management System Proposal
By:
Srikanth, Bhonagiri Santosh Kumar
IS5803
Introduction
Technology forms an integral part of a business organization
It allows organization to conduct their activities in a flexible manner
Most of the organizations are making fair use of the online platform
Online presence plays a significant role in the current corporate world
Business organizations are taking advantage and turning to online entirely in their operations
This presentation is a system proposal for an online inventory system
Overview of the system
Name: Online Inventory management system
Organization: Davidson convenience store, Charlotte, North Carolina
Currently, the convenience store uses offline Inventory management system
The proposal is to implement online inventory management where the system will take the data from the online business activities regarding inventory and generate their associated reports
System goals for the business
Automation of the Inventory management
Reports on the Inventory performance
Inventory tracking
History of Convenience store, Charlotte, NC
Davidson store is one of the best firm in the Charlotte area
It was first established in 1994
The store sells a wide selection of items that you use daily (bread, milk, perishable foods, house/bathroom supplies, wide variety of good beer selection and great wines etc..)
The firm has a plan to open one or two stores in other parts of Charlotte area in the mere future
Problem facing the firm
The firm faces issues with its inventory management
It has an offline inventory system which fits the current business environment where the inventory operations happens manually
It requires the store employees to be physically in the organization’s premise
The issues affect fast inventory management
Sluggish inventory management affects the achievement of organizational goals
Not able to identify accurately the slow selling stock in the inventory
Solution
Development of online Inventory management system
The system allow Inventory personnel to attend the inventory remotely
The system will also allow them to make decisions remotely and give instructions to the employees on different tasks
The manager can also observe the performance of different inventories, audit the inventory and track the sales along with generating reports
Therefore, the system will enhance the management of inventory leading to maximization of profits
Feasibility Study
Operational Feasibility: The system will automate the Inventory management system, monitor inventory remotely and execute real time decisions
Economic Feasibility: The system will reduce the staff’s cost associated with Inventory management, will reduce the number of personnel needed for Inventory management activities, and reduce Inventory operation costs
Technical Feasibility: The organization has the technology necessary to implement the system within the estimated cost and will be profitable for the convenience store
Schedule Feasibility: The development of the Inventory management system won’t take a lot of time and the anticipated duration of the project is 3 months from start to finish
Gantt Chart
Project Schedule
__MACOSX/._Inventory Management System.pptx
Feasibility Analysis.docx
Feasibility Analysis
The feasibility analysis shows the suitability of the system, considering different operational factors. Subjecting project to feasibility test helps to find out if they are worth implementing. The feasibility test finds out if the system development is within a reasonable cost and developed within a reasonable time frame if it will be economical to the organization.
This paper is a feasibility test for the project of developing an online inventory management system. Some of the factors of consideration include the following.
Operational Feasibility
By using an unautomated online system can results in several issues, as highlighted in the scope statement. The system will thus provide solutions to the issues raised. First, the system will develop an inventory management system that automates the inventory management system. Second, the system will allow the management to monitor every inventory remotely and execute real-time decisions based on the information provided. Third, the inventory management will generate reports regarding each item’s performance and give projections of sales depending on the available information. In the perspective of the store, the online inventory management system can be considered as low risk project.
Economic Feasibility
The economic feasibility assesses the benefits of system implementation. Will the system benefit the organization in the long run? The system will be beneficial in many ways. First, the system will reduce the staff’s cost associated with inventory management since it an automated one; hence, inventory managers will only access the trends and make informed decisions. Second, though it might not go well with some staff, the system will reduce the number of personnel needed for inventory management activities, saving the management’s cost. Lastly, the cost of operating the inventory management greatly reduces since the system is integrated with an online platform. The inventory management system is economically feasible and easy to use for the users and low maintenance to the Davidson convenience store.
Technical Feasibility
The organization has the technology necessary to implement the system; it uses the same resources used by its online resources. Also, during development, the organization has all the resources that will be used. Some of the technical resources are not expensive and can pressure the organization’s financial resources. The proposed project online inventory management system is technically feasible and feasible within estimated cost and will be profitable to the Davidson convenience store. Tracking the stores inventory is an important feature in the Online Inventory Management system. The system allows the users to track the inventory by serial numbers, barcodes and other IDs. Without traceability the store risk by recalling items for any clarification and therefore loosing revenue. Purchase is another feature to any warehouse that relies on vendor for goods to purchase. This feature I will be building to the system that helps the users to manage and create purchase orders.
Schedule Feasibility
The development of the inventory management system won’t take a lot of time. Three months is enough to develop it and deploy it into the working environment. The project online inventory management system follows SDLC process. Firstly, the project starts with planning phase with System Request and Feasibility Analysis are focused. Secondly, the Analysis phase to document the requirements, analyze the current offline inventory process and accordingly work on future state requirements for online inventory process. Thirdly, the design phase which includes the prototypes, architecture designs and hardware/software specifications. Finally, the implementation phase to test the online inventory process and deploy into production environment. The risk will encounter in test process and have to plan, document, test all the test scenarios and make sure there will be no production issues when deployed in production environment. Production issues might arise in any software development, the issues should be rectified and fixed as soon as they are identified.
Additional comments
The requirements of the organization to implement the system push the organization. The organization shall benefit from the implementation significantly. It will lead to the enhancement of customer service leading to customer satisfaction. The process of inventory management system is to ensure their inventory is kept at optimal level. This system will track all the products information, audit the inventory and track the sales along with generating reports. The system also helps the business by identifying the slow selling stock, which helps to look for stock that has not been sold in the last 6 to 12 months.
__MACOSX/._Feasibility Analysis.docx
Non Functional Requirements Sheet.xlsx
Non Functional Requirements
| Operational Requirements | Definition | Online Inventory Management System |
| Technical | Special hardware, software, and network requirements imposed by business requirements | System will use cloud for remote connection. The system will have real-time updates and minimize delays. The inventory manager can thus update database instantly |
| System Integration | The extent to which the system will operate with other systems | The sytem will be able to access database. However restriction will be placed on the type of data it accesses |
| Portability | The extent to which the system will need to operate in other environments | The system will be available to all devices provided that they have web browsers. The system is designed for access from different mobile devices (Android and iOS) |
| Maintainability | Expected business changes to which the system should be able to adapt | The system accomodates modifications to meet the requiremnts as well as to fit in its environment. It will be updated depending on the organization's needs. |
| Accessbility | How users can use the system | The system will be accessed remotely. The system is accessible to users even outside the company. It is available at any location globally because of cloud service. |
| Performance | How fast the system will return results | The system must not lag, because the users using it don't have down-time to wait for it to complete an action.The system should be very fast in processing users data and response time should be high. The system is developed using advanced technologies and has its servers stored in fast cloud servers. Accessibility will be fast and at any location |
| Supportability | Inherent characteristics of a system that allow efficient and effective sustainment | The application will work even on systems with minimum configurations |
| Packaging | Defines how software sotware application is structured or packaged | The system must incorporate license key authenitcation process. The packaging must come with manual that details the use of the system. The Inventory Management system contains installation disk and license key in the form of a file. User manual is also provided for the same |
| Performance Requirements | Definition | Online Inventory Management System |
| Speed | Time within which the system must perform its function | Transaction response not exceeding 5 seconds. However, speed will depend on the network connection when the system is accessed remotely. |
| Capacity | Total and peak number of users and the volume of data expected | 1000 maximum users can access the system simultaneously. |
| Availability and Reliability | Extent to which the system will be available to the users and the permissible failure rate due to errors | The system will be available 99.999%. Minimal down time will be experienced. |
| Interfacing | How well the system looks and ease of use | The system will offer a simple way of viewing the current inventory. The system will display the relationships between the various components in the system |
| Usability | How hard it may be to use the system | The system wil use a simple well-designed interface to provide easy navigation for new users, enhance their efficiency and memorability. The inventory management system uses graphic user interface that many people are conversant with and is easy to use |
| Integrity and Safety | The extent to which the data stored in the system's database can be free from integrity corruption and infortion be safe | The system will ensure that only the right users have rights to access information and only administrators can change data, remove records or add new users. The system will ensure integrity as it will not allow data manipulation |
| Accuracy | How accurate the system will be | The system will minimize and eradicate the errors. It will improve on accuracy and ease all the processes. Records updating, searching and generation of inventory reports will be accurate from the new system |
| Security Requirements | Definition | Online Inventory Management System |
| System Value Estimates | Estimated business value of the system and its data | The loss of data will lead to approximately $5 million |
| Access Control | Limitations on who can access what data | The inventory management employee has access to change items in the database through instruction from the inventory manager. Data security is ensured through access controls. The various users and their access rights are well defined and cannot be violated. |
| Encryption and Authentication | Defines what data will be encrypted where and whether authentication will be needed for user access | Data encryption will occur in the users browsers. The system requires login after sometime of inactivity. Also, users must login successfully to access information otherwise the system locks. Any failed login will be reported to the security administrator. |
| Virus Control | Controls to limit viruses | Virus checks will be done everytime the data is uploaded to the system. The system is configured to be compatible with antivirus software thus protecting its information. The system has autobackup for database after three hours. |
| Disaster Recovery | How the system will recover from problems | The system will be able to recover from unstable problems and will backup data. Back up of data will ensure that the system will recover from any problems |
| Error Handling | How best the system handles errors | The system will be able to handle unexpected errors quickly and easily. |
| Cultural/Political Requirements | Definition | Online Inventory Management System |
| Multilingual | The language(s) the system users will need | The system will operate in English language since the system is only used locally. |
| Customization | Specification of what aspects of the system can be changed by local users | Local users can customize the view of the data in the database depending on the information they are looking for in the system. The system facilitates upgrade and update anytime need arises. |
| Making Unstated Norms Explicit | Explicitly stating assumptions that differ from country to country | All prices description will be in American dollar |
| Legal | The laws and regulations that impose system requirements | The customer information shall be kept for the organizational use only and customers must be made aware. The system is licensed and cannot be installed before an agreement is made. |
__MACOSX/._Non Functional Requirements Sheet.xlsx
Architecture Design.docx
2
Architecture Design
Introduction
Development and implementation of an information system is an important process that needs more emphasis to achieve. Some of the most important aspects of the development, installation, and maintenance of an information system include the architecture and the requirements for the system. In the case of an online inventory management system for a convenience store, the system architecture is crucial in ensuring an easy to run system and maintenance. The design document will discuss the types of system architectures that will be applied in an online inventory management system and the benefits.
3-Tier Architecture
The system will use the 3-tier architecture. It is a software architecture that comprises three layers of logical computing. The architecture modularizes the user interface, business logic, and data storage layers thus making it easy for the development team to update one part of the application without interfering with the other parts. The 3-tier architecture is divided into presentation tier, application tier, and data tier protocols that help in communicating with the server. The presentation tier consists of the user interface. The user interface is graphical and can be accessed through a web application or a web browser and provides useful information to the end-user. The application tier consists of functional business logic that drives an application's core capabilities while the data tier contains a data storage system (database) and data access layer.
With the different layers/tiers available in the architecture, it is easy for administrators and the development team to work on each modular independently. The use of 3-tier architecture in the system will provide fast and secure access to services from the server. Additional benefits of 3-tier architecture include the speed of development, performance, scalability, and availability. With the architecture allowing usage of devices like mobile devices, it allows easy access and processing of information even at remote locations.
Figure 1 3-Tier Architecture
In conclusion, using thin-client server architecture and 3-tier architecture will ensure fast and secure processing of data as well as less cost in the data processing. In the system, the two architectures are used since they are easy to access, easy to maintain and scale independently when the need arises.
__MACOSX/._Architecture Design.docx
Hardware and Software Specification.docx
Hardware and Software Specification
Introduction
Hardware and software specifications form part of the requirements when implementing any given system. Deployment of VM in 3-tier architecture will require stable hardware and software resources. In assessing both hardware and software specifications in 3-tier architecture, it is worth noting that this architecture is divided into 3 (presentation tier, business logic tier, and data management tier). The document aims to provide an overview of hardware and software specifications within the three-tier architecture environment.
Hardware Specifications
Agreeably, deployment of any system in three-tier architecture depends on hardware availability, which must be associated with some features such as RAM, hard disk capacity, and processor speed. In line with the 3-tier architecture, from the client part, access to system resources is based on the presentation layer, where access information requires hardware such as tablets, smartphones, and laptops. Laptop with Windows 10 Pro, 4GB RAM, and processor of corei5 are best suited to be hardware requirements from the client part. The server-side hardware requirements from the server include Centos 7 server with CPU type of Intel XEON, 32GB DDR4 RAM, 10TB data transfer, and 1TB SSID primary storage.
Software Specifications
In the deployment of this 3-tier architecture software, requirements will be based on both the client and the server. On the client-side, the software requirements include web browsers (Mozilla, Chrome, Opera, Internet Explorer, etc.). For the server-side, software requirements include Centos 7 server, Apache 2.4 (web server), PHP 7.2 for server-side scripting. The system will have a MySQL database management system installed for storage of data. Such software will be useful in the execution and deployment of applications within the Virtual Machine environment.
The software and hardware specifications ensure resilience and easy manageability of the system and ensure that processes run swiftly.
__MACOSX/._Hardware and Software Specification.docx
UI Prototype.zip
Sign Up page.JPG
__MACOSX/._Sign Up page.JPG
Sign In page.JPG
__MACOSX/._Sign In page.JPG
Search Page.JPG
__MACOSX/._Search Page.JPG
Report.JPG
__MACOSX/._Report.JPG
Privacy Policy.JPG
__MACOSX/._Privacy Policy.JPG
Home Page.JPG
__MACOSX/._Home Page.JPG
Fruits Vegetables.JPG
__MACOSX/._Fruits Vegetables.JPG
Dashboard.JPG
__MACOSX/._Dashboard.JPG
Dairy Page.JPG
__MACOSX/._Dairy Page.JPG
__MACOSX/._UI Prototype.zip
Gantt Chart.xlsx
Gantt Chart
| Project Name | Online Inventory Development Project | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Project Duration | 86 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Project Start Date | 4-Jan-21 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Project End Date | 31-Mar-21 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Task | Start Date | End Date | 4-Jan-21 | 5-Jan-21 | 6-Jan-21 | 7-Jan-21 | 8-Jan-21 | 9-Jan-21 | 10-Jan-21 | 11-Jan-21 | 12-Jan-21 | 13-Jan-21 | 14-Jan-21 | 15-Jan-21 | 16-Jan-21 | 17-Jan-21 | 18-Jan-21 | 19-Jan-21 | 20-Jan-21 | 21-Jan-21 | 22-Jan-21 | 23-Jan-21 | 24-Jan-21 | 25-Jan-21 | 26-Jan-21 | 27-Jan-21 | 28-Jan-21 | 29-Jan-21 | 30-Jan-21 | 31-Jan-21 | 1-Feb-21 | 2-Feb-21 | 3-Feb-21 | 4-Feb-21 | 5-Feb-21 | 6-Feb-21 | 7-Feb-21 | 8-Feb-21 | 9-Feb-21 | 10-Feb-21 | 11-Feb-21 | 12-Feb-21 | 13-Feb-21 | 14-Feb-21 | 15-Feb-21 | 16-Feb-21 | 17-Feb-21 | 18-Feb-21 | 19-Feb-21 | 20-Feb-21 | 21-Feb-21 | 22-Feb-21 | 23-Feb-21 | 24-Feb-21 | 25-Feb-21 | 26-Feb-21 | 27-Feb-21 | 28-Feb-21 | 1-Mar-21 | 2-Mar-21 | 3-Mar-21 | 4-Mar-21 | 5-Mar-21 | 6-Mar-21 | 7-Mar-21 | 8-Mar-21 | 9-Mar-21 | 10-Mar-21 | 11-Mar-21 | 12-Mar-21 | 13-Mar-21 | 14-Mar-21 | 15-Mar-21 | 16-Mar-21 | 17-Mar-21 | 18-Mar-21 | 19-Mar-21 | 20-Mar-21 | 21-Mar-21 | 22-Mar-21 | 23-Mar-21 | 24-Mar-21 | 25-Mar-21 | 26-Mar-21 | 27-Mar-21 | 28-Mar-21 | 29-Mar-21 | 30-Mar-21 | 31-Mar-21 |
| Planning | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System Request | 4-Jan-21 | 15-Jan-21 | X | X | X | X | X | X | X | X | X | X | X | X | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Feasibility Analysis | 5-Jan-21 | 13-Jan-21 | X | X | X | X | X | X | X | X | X | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Analysis Phase | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Gantt Chart | 14-Jan-21 | 20-Jan-21 | X | X | X | X | X | X | X | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Requirements Definition | 15-Jan-21 | 28-Jan-21 | X | X | X | X | X | X | X | X | X | X | X | X | X | X | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Data Flow Diagram | 20-Jan-21 | 29-Jan-21 | X | X | X | X | X | X | X | X | X | X | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Use Cases | 20-Jan-21 | 29-Jan-21 | X | X | X | X | X | X | X | X | X | X | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Design Phase | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Acquisition Strategy | 1-Feb-21 | 9-Feb-21 | X | X | X | X | X | X | X | X | X | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Entity-relationship Design | 5-Feb-21 | 12-Feb-21 | X | X | X | X | X | X | X | X | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Protoypes/Mockups | 15-Feb-21 | 19-Feb-21 | X | X | X | X | X | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Input/Output Design | 17-Feb-21 | 22-Feb-21 | X | X | X | X | X | X | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Architecture Design | 16-Feb-21 | 26-Feb-21 | X | X | X | X | X | X | X | X | X | X | X | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Hardware and Software Specification | 22-Feb-21 | 4-Mar-21 | X | X | X | X | X | X | X | X | X | X | X | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Implementation Phase | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Testing | 4-Mar-21 | 23-Mar-21 | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Documentation | 22-Mar-21 | 26-Mar-21 | X | X | X | X | X | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Migration and Conversion | 24-Mar-21 | 31-Mar-21 | X | X | X | X | X | X | X | X |
__MACOSX/._Gantt Chart.xlsx
Alternative Matrix.xlsx
Sheet1
| Criteria | Weight | option1 | score | weighted score | option2 | score | weighted score | option3 | score | weighted score |
| Technical | Outsource | Prepackaged | In house | |||||||
| Efficiency | 20 | Efficient | 5 | 25 | Efficient | 5 | 100 | Very efficient | 5 | 100 |
| Technical Resources | 10 | More expensive | 3 | 30 | More expensive | 2 | 20 | Not expensive | 5 | 50 |
| Easy user management for tracking the products in inventory | 15 | Easy User Interface | 5 | 75 | Easy User Interface | 5 | 75 | Easy User Interface | 5 | 75 |
| Economic | ||||||||||
| Cost efficient in budget | 25 | Most expensive | 3 | 75 | Most expensive | 3 | 75 | Less expensive | 5 | 125 |
| Cost of maintenance | 10 | High maintenance | 3 | 30 | High maintenance | 3 | 90 | Low maintenance | 5 | 50 |
| Organizational | ||||||||||
| Suit organizational culture on the online automation process | 10 | Online automation process | 5 | 50 | Online automation process | 5 | 50 | Online automation process | 5 | 50 |
| Easy acceptance | 10 | User acceptance | 5 | 50 | User acceptance | 5 | 50 | User acceptance | 5 | 50 |
| 100 | 1 through 5 | 335 | 460 | 500 | ||||||
__MACOSX/._Alternative Matrix.xlsx
Acquisition Strategy.docx
2
Acquisition Strategy
The alternative matrix enabled us to determine which of the three options – outsourcing, prepackaged, and in-house is the best and fits the current organizational situation. From the scores obtained, we can see that developing the system in-house is the best option. The in-house option scores 500. Technical, financial, and organizational factors were the main areas of consideration when deciding which is the best method to develop the online inventory system.
Technical – here, we considered the efficiency and update of the system. For efficiency, we prefer a system that will solve the organization’s issues comprehensively. The in-house development provides a comprehensive solution since the developers understand the system requirements exhaustively what is needed by the system. Also, the inventory management technical team can receive the required updates and work promptly. The other options will require to consult the vendors who will perform their techniques for the implementation of the update, hence consuming time. Loss of control, high development and maintenance costs are other factors for not opting to Outsourcing and Prepackaged solutions. In-house solution saves significant costs, has a significant advantage on response time when compared to other options.
Financial – the cost of developing the system varies significantly. Outsourcing or having the prepackaged system costs more than developing in-house. Developing a system in-house is less expensive since the firm purchases all resources required for the process. The technical resources which include development, system support is relatively low cost efficient and has control over the system with low development and maintenance costs.
Organizational – The system best fits with the organizational needs. The three options might fit the requirements, but the outsourced and prepackaged does not guarantee. Lack of control, communication issues and problems with crossing the budget even though the quality is good are the other factors which may impact the system support and maintenance. It cannot be accepted quickly and also may fail to match the organizational culture.
The benefits of using an in-house inventory management system includes greater cost savings, simplified inventory management and better product visibility. The main reason to opt for in-house is that the software is developed by a team of our choice which gives access to knowledgeable support rather than dealing with team with outsourcing team who might not understand the difficult situations. Finally, we have decided to go for in-house development because it fits the organizational technical and economical requirements.
__MACOSX/._Acquisition Strategy.docx
Requirements Definition Statement.docx
2
System Requirements
The organizational needs drive the Davidson Convenience Store online inventory system requirements. These requirements consist of those required during the development process and after the system deployment. These requirements are categorized into five categories: output, input, process, performance, and control.
Output
The system will output different information depending on what the Systems Analyst wants from the system. They will perform the duty locally regardless of their location, provided that they have an internet connection. The system’s information includes viewing each product’s performance in the inventory, the products’ suppliers, and the inventory shelf age. The system will allow the management to monitor every inventory remotely and execute real-time decisions based on the information provided. The system allows the users to track the inventory by serial numbers, barcodes and other IDs. The system will help the users to manage and create purchase orders. The information can be in a graphical display such as graphs and charts, and they are critical for making decisions.
Input
Our system is an online system that allows the organizational personnel to manage inventories locally. Some of the operations include monitoring and updating inventory. Therefore, the inputs of the system will comprise the inventory details. These details include suppliers’ details, date of purchase, expiry date, date of sale. The input of serial numbers, barcodes and other IDs can track the inventory. Through the analysis of this information, the organization can observe each product’s performance and organizational decisions. The inputs will also include details of the personnel and the system’s duties which the System Analyst can update. The system also helps the business by identifying the slow selling stock, which helps to look for stock that has not been sold in the last 6 to 12 months based on barcodes or item numbers.
Process
The system will also conduct some processes. The Systems Analyst will entirely manage the inventory processes in the system. The processes include monitoring the inventory and giving alerts on the expired inventory and those overstayed on the shelves. It can also calculate the selling price through the recorded buying prices, depending on the organization’s percentage for the profit. Also, the manager can order inventory depending on the stock performance. The system collects the data from each product, and it visually shows the analysis that will enable management to observe how they perform and use them to make management decisions. The Online Inventory Management system will allow the users to track goods across the business supply chain. It gives the system user, the information about the entire process from the order placement with the vendor to the customer delivery where the business can track the complete journey of the product.
Performance
The Online Inventory Management system is a useful tool to improve the business productivity and process efficiency. This automated software reduces human error. The system is entirely online, and thus it must always be operational; it must be operating seven days a week and 365 days - This is not possible but must operate 99.9999 % of the time. The downtime must be insignificant. This high availability time will ensure that the system is always available every time the users require it.
The system will support up to a maximum of 1000 users simultaneously. The performance will drop when the number is surpassed. This high number shows that the organization will always have many users who mostly are remote users consisting of the organization’s vendors and customers.
Lastly, response times should not exceed three seconds. The time is not guaranteed at low internet connection speed. The users who access the system remotely might experience these sluggish internet connections but those; however, the organization’s internet connection is always good, and the response time will not be affected significantly.
Control
The system must also ensure that there is safety of the resources. Thus, it is important to control who accesses the system. The logon security will be implemented; the users will need to supply their login details when they want to access the system. The design will maintain different levels of protection for users and system administrators. Also, the system will keep audit transactions and backup of all transactions.
The system will also beef up data security by implementing strong security strategies to protect the data from cybercriminals’ access. These measures include encryption of the data so that the criminal cannot decipher the content of different files to access them.
Conclusion
The system requirements are crucial for the process of developing the system. The developers need to understand they are developing through the stated requirements and develop as the specification. The common requirements discussed include input, output, process, performance, and control. The Online Inventory Management system will help to manage and maintain the business as it continues to develop and grow. The system helps the business to provide knowledge on how to shape the product offering. With the Online Inventory Management system, the business can prevent overstock by setting their products catalog. The system helps the business to identify what needs to change to develop the business based on the stock analysis and report metrics.
__MACOSX/._Requirements Definition Statement.docx
System Request.docx
System Request: Inventory Management System
Project Sponsor
Name(s): Davidson Convenience Store, Charlotte, NC
Title(s): Systems Analyst
Business Need – Why is this request being made:
Most of the organization are making fair use of the online platform. Online presence plays a significant role in the current corporate world. Since most clients have turned online, business organizations should take advantage and turn to online entirely in their operations. Currently, the convenience store uses offline inventory management system that requires users to transfer data from offline operations and enter into the system to manage their inventory. Therefore, with the online inventory management implementation, the system will take the data from the online business activities regarding inventory and generate their associated reports. Therefore, it will save time and allow the organization to perform other activities.
Business Requirements – What is needed explicitly from this system:
· Automation of the inventory management
· Reports on the inventory performance
· Inventory tracking
Business Value – how will this benefit the business:
The system will benefit the organization by managing their inventory. The information obtained from the system will help organization management make better and informed decisions regarding the inventory drawn from each inventory's performance.
Special Issues or Constraints:
The issues with the system development include:
· Resources for development.
· The development will also require trained people to implement
· Time constrained for the entire development process
