Capabilities of the System
The paper mainly focuses on the organization named “Alvarado Street Bakery” that is one of the worker owned bakery which generally helps in producing certified organic whole grain breads as well as bagels. The organization used manual system in order to manage all the functions as well as operations of the organization. Due to the utilization of manual system, the organization faces lot of difficulties and issues due to inconsistent data entry, duplication of data entry as well as large ongoing costs. In addition to this, the organization is not able to share proper information as well as services to the customers in a shorter period of time. In order to resolve the issue, the organization wants to develop an information system so that they can be able to manage the operations as well as functions of the organization properly. It is found that with the development of information system, the organization will be able to reach the customers quite easily.
The capabilities of the system are as follows:
- Generation of database management system for storing data and information of the organization
- Registration by new users by providing user ID and password
- Collection of food items that will be served by the Alvarado Street Bakery
- Providing simple and easy access to the customers
The expected benefits that can be achieved due to the development of the information system are as follows:
- Maintaining the competition levels with other organization of its type
- Enhancing online experience of the customers
- Reaching the customers widely
- Serving the customers of the organization 24×7
- Storing data as well as information about the sales
- Maximizing the chances of attracting more number of customers
- Reaching to maximum number of customers
- Decreasing the work requirement in context to management system.
The estimated time for the completion of entire information system is provided in the table below:
WBS |
Task Name |
Duration |
Start |
Finish |
0 |
Development of information system |
179 days |
Tue 19-06-18 |
Wed 27-02-19 |
1 |
Project initiation phase |
43 days |
Tue 19-06-18 |
Thu 16-08-18 |
1.1 |
Analyzing requirements of project |
8 days |
Tue 07-08-18 |
Thu 16-08-18 |
1.2 |
Project plan development |
4 days |
Tue 19-06-18 |
Fri 22-06-18 |
1.3 |
Feasibility testing |
5 days |
Mon 25-06-18 |
Fri 29-06-18 |
1.4 |
Milestone 1: Completion of initiation phase |
0 days |
Fri 29-06-18 |
Fri 29-06-18 |
2 |
Project planning phase |
37 days |
Mon 02-07-18 |
Tue 21-08-18 |
2.1 |
Scheduling activities of project |
4 days |
Mon 02-07-18 |
Thu 05-07-18 |
2.2 |
Estimation of resource |
6 days |
Fri 06-07-18 |
Fri 13-07-18 |
2.3 |
Allocation of resources |
9 days |
Mon 16-07-18 |
Thu 26-07-18 |
2.4 |
Communication plan development |
9 days |
Fri 27-07-18 |
Wed 08-08-18 |
2.5 |
Project team allocation |
9 days |
Thu 09-08-18 |
Tue 21-08-18 |
2.6 |
Milestone 2: Completion of planning phase |
0 days |
Tue 21-08-18 |
Tue 21-08-18 |
3 |
Project designing phase |
40 days |
Wed 22-08-18 |
Wed 17-10-18 |
3.1 |
Blueprint development |
7 days |
Wed 22-08-18 |
Thu 30-08-18 |
3.2 |
Assigning IT needs |
6 days |
Fri 31-08-18 |
Fri 07-09-18 |
3.3 |
Assigning necessary software |
7 days |
Mon 10-09-18 |
Tue 18-09-18 |
3.4 |
Website development requirement |
20 days |
Wed 19-09-18 |
Wed 17-10-18 |
3.5 |
Milestone 3: Completion of designing phase |
0 days |
Wed 17-10-18 |
Wed 17-10-18 |
4 |
Development phase |
63 days |
Thu 18-10-18 |
Wed 16-01-19 |
4.1 |
Interface design |
7 days |
Thu 18-10-18 |
Fri 26-10-18 |
4.2 |
prototype design |
8 days |
Mon 29-10-18 |
Wed 07-11-18 |
4.3 |
Database design |
20 days |
Thu 08-11-18 |
Wed 05-12-18 |
4.4 |
Development of admin dashboard |
10 days |
Thu 06-12-18 |
Wed 19-12-18 |
4.5 |
Interconnection between developed overall information system |
10 days |
Thu 20-12-18 |
Fri 04-01-19 |
4.6 |
Implementation of final website |
8 days |
Mon 07-01-19 |
Wed 16-01-19 |
4.7 |
Milestone 4: Completion of execution phase |
0 days |
Wed 16-01-19 |
Wed 16-01-19 |
5 |
Testing Phase |
19 days |
Thu 17-01-19 |
Tue 12-02-19 |
5.1 |
Testing of the Hardware |
7 days |
Thu 17-01-19 |
Fri 25-01-19 |
5.2 |
Testing of the software |
7 days |
Mon 28-01-19 |
Tue 05-02-19 |
5.3 |
Data Warehouse Testing |
5 days |
Wed 06-02-19 |
Tue 12-02-19 |
5.4 |
Milestone 5: Completion of testing phase |
0 days |
Tue 12-02-19 |
Tue 12-02-19 |
6 |
Closing Phase |
11 days |
Wed 13-02-19 |
Wed 27-02-19 |
6.1 |
Post project review |
2 days |
Wed 13-02-19 |
Thu 14-02-19 |
6.2 |
Stakeholder sign off |
4 days |
Fri 15-02-19 |
Wed 20-02-19 |
6.3 |
Maintenance of the Data Warehouse |
5 days |
Thu 21-02-19 |
Wed 27-02-19 |
6.4 |
Milestone 6: Completion of closure phase’ |
0 days |
Wed 27-02-19 |
Wed 27-02-19 |
The cost that is required for developing the information system is mainly provided in the table below:
WBS |
Task Name |
Duration |
Resource Names |
Cost |
0 |
Development of information system |
179 days |
AUD49,032.00 |
|
1 |
Project initiation phase |
43 days |
AUD3,760.00 |
|
1.1 |
Analyzing requirements of project |
8 days |
Project Manager |
AUD1,600.00 |
1.2 |
Project plan development |
4 days |
Project Manager |
AUD800.00 |
1.3 |
Feasibility testing |
5 days |
Tester, Designer |
AUD1,360.00 |
1.4 |
Milestone 1: Completion of initiation phase |
0 days |
AUD0.00 |
|
2 |
Project planning phase |
37 days |
AUD7,480.00 |
|
2.1 |
Scheduling activities of project |
4 days |
Contractor |
AUD640.00 |
2.2 |
Estimation of resource |
6 days |
Financial Manager |
AUD720.00 |
2.3 |
Allocation of resources |
9 days |
Team Leaders, Supervisor |
AUD2,160.00 |
2.4 |
Communication plan development |
9 days |
Project Manager, Team Leaders |
AUD2,880.00 |
2.5 |
Project team allocation |
9 days |
Team Leaders |
AUD1,080.00 |
2.6 |
Milestone 2: Completion of planning phase |
0 days |
AUD0.00 |
|
3 |
Project designing phase |
40 days |
AUD4,912.00 |
|
3.1 |
Blueprint development |
7 days |
Designer |
AUD952.00 |
3.2 |
Assigning IT needs |
6 days |
Team Leaders |
AUD720.00 |
3.3 |
Assigning necessary software |
7 days |
Financial Manager |
AUD840.00 |
3.4 |
Website development requirement |
20 days |
Financial Manager |
AUD2,400.00 |
3.5 |
Milestone 3: Completion of designing phase |
0 days |
AUD0.00 |
|
4 |
Development phase |
63 days |
AUD21,920.00 |
|
4.1 |
Interface design |
7 days |
Hardware [1] |
AUD4,000.00 |
4.2 |
prototype design |
8 days |
Software [1] |
AUD5,000.00 |
4.3 |
Database design |
20 days |
Financial Manager, Contractor |
AUD5,600.00 |
4.4 |
Development of admin dashboard |
10 days |
Network cost[1] |
AUD3,000.00 |
4.5 |
Interconnection between developed overall information system |
10 days |
Business Consultant, Tester |
AUD2,720.00 |
4.6 |
Implementation of final website |
8 days |
Project Manager |
AUD1,600.00 |
4.7 |
Milestone 4: Completion of execution phase |
0 days |
AUD0.00 |
|
5 |
Testing Phase |
19 days |
AUD8,216.00 |
|
5.1 |
Testing of the Hardware |
7 days |
Designer, Additional cost [1] |
AUD4,952.00 |
5.2 |
Testing of the software |
7 days |
Tester, Designer |
AUD1,904.00 |
5.3 |
Data Warehouse Testing |
5 days |
Tester, Designer |
AUD1,360.00 |
5.4 |
Milestone 5: Completion of testing phase |
0 days |
AUD0.00 |
|
6 |
Closing Phase |
11 days |
AUD2,744.00 |
|
6.1 |
Post project review |
2 days |
Project Sponsor, Project Manager |
AUD400.00 |
6.2 |
Stakeholder sign off |
4 days |
Business Consultant, Project Manager |
AUD1,344.00 |
6.3 |
Maintenance of the Data Warehouse |
5 days |
Project Manager |
AUD1,000.00 |
6.4 |
Milestone 6: Completion of closure phase’ |
0 days |
AUD0.00 |
The estimated annual operating cost for the project is provided in the table below:
Recurring expenses |
Amount |
Server Hosting |
$7,000 |
Internet Connectivity |
$3,000 |
Training |
$2,000 |
Renewal (Equipment) |
$3,000 |
Total Costs |
$15,000 |
The anticipated benefits from the deployment of information system is provided below. This generally comprises of both tangible as well as intangible benefits.
- Enhanced orders due to simple nature of payment and purchase
- Maximizes the chances for attraction of new students
- Minimization of work requirements in context to management system
- Minimization of possibilities of inconsistencies and glitches
Tangible benefits: The tangible benefits of the project are as follows:
- Enhanced recognition with the help of advertisement
- Reducing technological related expenses
- Reducing employment for the staffs
Intangible benefits: The intangible benefits of the project are as follows:
- Enhancing the level of satisfaction among the staffs and customers
- Improving the level of competition
- Maximizing glitches and inconsistencies
The estimated annual benefits that is gained is provided below:
Benefit |
Amount |
Enhancing enrolments and registrations |
$4,000 |
Enhanced social media recognition |
$6,000 |
Reduction of technological expenses |
$5,000 |
Reduced employment hours for office staff |
$5,00 |
Total amount |
$20,000 |
The organizational risks as well as feasibility is elaborated below:
Inability as well as unfamiliarity to adapt: It is found that despite of the intention of the new information system, lack of preparation of organizational staffs can cause unfamiliarity which further indicates that they do not have proper knowledge about the new system. Thus, the older employees who have limited knowledge about the technologies can face lot of difficulties to use the system.
Fear of Automation: The new information system helps the organization in achieving certain objectives and the facilities of the new information system helps in managing the operations of the organizations properly and as a result the staffs of the organization views this facility as a negative way.
Problems related with reliability and integrity: In spite of the capabilities of the information system that is developed, it is found that there are number of technological problems that are generally related with the system. In order to resolve the technological risks, it is quite important to implement steps that are related below:
- Proper training facility must be provided to the employees of the organization
- New tasks must be assigned to the staffs so that they can substitute workload with the new system
It is found that all the staffs and employees of the organization will generally undertake proper training for 2 days in case the new system that is developed is found to be very much complex to comprehend. In addition to this, both instruction as video resources made to be available in case of revising or future training for the information system. Overall, this assistance would generally ensure that who are mainly responsible for the management of the new information system must understand the requirement for handling the system in case of any type of malfunctions.
Expected Benefits
It is found that online platform assists the organization “Alvarado Street Bakery” to get online orders which can also pose risks. It is found that before using the system it is necessary to test the system so that it can be ensured that the platform is entirely functional. In addition to this, the customer support service would helpful in resolving the issues that the customers will face in buying and making payment. This further assists in providing a solution for users as per the requirements of the customers.
It is the task of the employees or staffs of the organization to fully understand the responsibilities as well as requirements that are related with the subsystem of the organization. If they are not able to understand the requirement of the project properly then number of issues and challenges can occur.
It is found that due to improper scheduling, the tasks that are needed to be executed in order to develop the information system get postponed and as a result they can face lot of challenges and issues. It is found that in order to resolve the issue, it is very much necessary to properly schedule the activities of the project so that they can completed within the time that is approved by the higher management of the organization.
Information capture
Information capture |
Electronic tools |
User accessibility |
Schedule of the project |
MS-Project |
Project manager |
Total annual cost for operating the project |
MS-Project |
Project manager |
Total annual benefits |
MS-Project |
Project Manager |
Status of the project |
MS-Project |
All user |
Documentation for the users |
MS-Word |
All User |
Design specification |
Microsoft Visio |
Project manager |
Code Version control |
Git |
Work environment is one of the most vital part for the project team and the completion of the project. A list is provided below which is reflecting on the resources that are required for the project work environment:
Hardware and software
Item |
Description |
Resource |
Server for hosting the system |
Dell PowerEdge T440 Tower Server |
Alvarado Street bakery (Expense) |
Computers |
Dell inspiron 3477 and Dell inspiron 5000 |
Alvarado Street bakery (Expense) |
MS-Project |
Microsoft Project 360 |
License-Owned by programmers |
MS-Word |
Microsoft Word 360 |
License-Owned by programmers |
MS-Visio |
Microsoft Visio 360 |
License-Owned by programmers |
HTML, CSS, JavaScript |
Adobe |
License-Owned by programmers |
PHP |
PHP.net |
License-Owned by programmers |
MySQL |
Xampp |
License-Owned by programmers |
Support Staff
Item |
Description |
Resource |
Admin Staff |
Staff of the organization |
Alvarado Street bakery |
The processes as well as procedures that are generally used in the project are listed below:
Documentation: All the meetings, feedback as well as design specifications are mainly documented with the help of Microsoft word. This documentation is generally done in order to keep record about things that are needed to be performed for the organization.
Programming: Programming like HTML, CSS as well as java programming languages are generally utilized by the entire project team. The entire tasks of programming are mainly divided into number of individual tasks between single project manager as well as developers.
Testing: Testing the code will generally need final testing as well as error testing. For undertaking testing it is necessary to do tasks that include approval from the higher management. It is found that in case of failure, the improvements that are needed will generally be performed in the next tests.
After completion of the project the organization can track their all order via website. The customers can order food via Alvarado Street bakery website. Moreover, all staffs can access this website for managing their inventory and orders of the customer. The administrative staffs can control all other staff’s details and account details. This process will help the Alvarado Street bakery to reduce the ordering and delivery time and help them to receive more orders then previous. All their process and details will be stored in this system.
The system development process for the Alvarado Street bakery by the developer and programmers will be sent to the GIT which is verified by the GIT version control. This system helps to track all the changes in program files. Moreover, this system will help to track all type of errors and reduce as many as possible.
The work breakdown structure for the project is provided below:
WBS |
Task Name |
Duration |
Start |
Finish |
Predecessors |
0 |
Development of information system |
179 days |
Tue 19-06-18 |
Wed 27-02-19 |
|
1 |
Project initiation phase |
43 days |
Tue 19-06-18 |
Thu 16-08-18 |
|
1.1 |
Analyzing requirements of project |
8 days |
Tue 07-08-18 |
Thu 16-08-18 |
|
1.2 |
Project plan development |
4 days |
Tue 19-06-18 |
Fri 22-06-18 |
2 |
1.3 |
Feasibility testing |
5 days |
Mon 25-06-18 |
Fri 29-06-18 |
3 |
1.4 |
Milestone 1: Completion of initiation phase |
0 days |
Fri 29-06-18 |
Fri 29-06-18 |
4 |
2 |
Project planning phase |
37 days |
Mon 02-07-18 |
Tue 21-08-18 |
|
2.1 |
Scheduling activities of project |
4 days |
Mon 02-07-18 |
Thu 05-07-18 |
4 |
2.2 |
Estimation of resource |
6 days |
Fri 06-07-18 |
Fri 13-07-18 |
7 |
2.3 |
Allocation of resources |
9 days |
Mon 16-07-18 |
Thu 26-07-18 |
8 |
2.4 |
Communication plan development |
9 days |
Fri 27-07-18 |
Wed 08-08-18 |
9 |
2.5 |
Project team allocation |
9 days |
Thu 09-08-18 |
Tue 21-08-18 |
10 |
2.6 |
Milestone 2: Completion of planning phase |
0 days |
Tue 21-08-18 |
Tue 21-08-18 |
11 |
3 |
Project designing phase |
40 days |
Wed 22-08-18 |
Wed 17-10-18 |
|
3.1 |
Blueprint development |
7 days |
Wed 22-08-18 |
Thu 30-08-18 |
11 |
3.2 |
Assigning IT needs |
6 days |
Fri 31-08-18 |
Fri 07-09-18 |
14 |
3.3 |
Assigning necessary software |
7 days |
Mon 10-09-18 |
Tue 18-09-18 |
15 |
3.4 |
Website development requirement |
20 days |
Wed 19-09-18 |
Wed 17-10-18 |
16 |
3.5 |
Milestone 3: Completion of designing phase |
0 days |
Wed 17-10-18 |
Wed 17-10-18 |
17 |
4 |
Development phase |
63 days |
Thu 18-10-18 |
Wed 16-01-19 |
|
4.1 |
Interface design |
7 days |
Thu 18-10-18 |
Fri 26-10-18 |
17 |
4.2 |
prototype design |
8 days |
Mon 29-10-18 |
Wed 07-11-18 |
20 |
4.3 |
Database design |
20 days |
Thu 08-11-18 |
Wed 05-12-18 |
21 |
4.4 |
Development of admin dashboard |
10 days |
Thu 06-12-18 |
Wed 19-12-18 |
22 |
4.5 |
Interconnection between developed overall information system |
10 days |
Thu 20-12-18 |
Fri 04-01-19 |
23 |
4.6 |
Implementation of final website |
8 days |
Mon 07-01-19 |
Wed 16-01-19 |
24 |
4.7 |
Milestone 4: Completion of execution phase |
0 days |
Wed 16-01-19 |
Wed 16-01-19 |
25 |
5 |
Testing Phase |
19 days |
Thu 17-01-19 |
Tue 12-02-19 |
|
5.1 |
Testing of the Hardware |
7 days |
Thu 17-01-19 |
Fri 25-01-19 |
25 |
5.2 |
Testing of the software |
7 days |
Mon 28-01-19 |
Tue 05-02-19 |
28 |
5.3 |
Data Warehouse Testing |
5 days |
Wed 06-02-19 |
Tue 12-02-19 |
29 |
5.4 |
Milestone 5:Completion of testing phase |
0 days |
Tue 12-02-19 |
Tue 12-02-19 |
30 |
6 |
Closing Phase |
11 days |
Wed 13-02-19 |
Wed 27-02-19 |
|
6.1 |
Post project review |
2 days |
Wed 13-02-19 |
Thu 14-02-19 |
30 |
6.2 |
Stakeholder sign off |
4 days |
Fri 15-02-19 |
Wed 20-02-19 |
33 |
6.3 |
Maintenance of the Data Warehouse |
5 days |
Thu 21-02-19 |
Wed 27-02-19 |
34 |
6.4 |
Milestone 6:Completion of closure phase’ |
0 days |
Wed 27-02-19 |
Wed 27-02-19 |
35 |
Boardman, A. E., Greenberg, D. H., Vining, A. R., & Weimer, D. L. (2017). Cost-benefit analysis: concepts and practice. Cambridge University Press.
Buede, D. M., & Miller, W. D. (2016). The engineering design of systems: models and methods. John Wiley & Sons.
Chen, Y. C., Chung, T. Y., Lin, C. S., Wu, T. S., & Leu, H. S. (2015). Investigation report on an event of neurosurgical postoperative surgical site infections. Journal of Microbiology, Immunology and Infection, 48(2), S115.
Hosseini, M., Shahri, A., Phalp, K. & Ali, R., (2016). June. A modelling language for transparency requirements in business information systems. In International Conference on Advanced Information Systems Engineering (pp. 239-254). Springer, Cham.
Ismail, N. A., & King, M. (2014). Factors influencing the alignment of accounting information systems in small and medium sized Malaysian manufacturing firms. Journal of Information Systems and Small Business, 1(1-2), 1-20.
Mir, F. A., & Pinnington, A. H. (2014). Exploring the value of project management: linking project management performance and project success. International journal of project management, 32(2), 202-217.
Preston, R. P., & Roy, J. (2017). Use of unmanned aerial vehicles to supplement conventional investigation methods for underground open void stability and mitigation.
Razak, S. A., Othman, S. H., Aldolah, A. A., & Ngadi, M. A. (2016). Conceptual investigation process model for managing database forensic investigation knowledge. Res. J. Appl. Sci., Eng. Technol., 12(4), 386-394.
Serrador, P., & Pinto, J. K. (2015). Does Agile work?—A quantitative analysis of agile project success. International Journal of Project Management, 33(5), 1040-1051.
Snyder, C. S. (2014). A guide to the project management body of knowledge: PMBOK (®) guide. Project Management Institute: Newtown Square, PA, USA.
Volk, R., Stengel, J., & Schultmann, F. (2014). Building Information Modeling (BIM) for existing buildings—Literature review and future needs. Automation in construction, 38, 109-127.
Wolken-Möhlmann, G., Bendlin, D., Buschmann, J., & Wiggert, M. (2016). Project schedule assessment with a focus on different input weather data sources. Energy Procedia, 94, 517-522.