CIS3002 Business Analysis

Work Breakdown Structure

Activity	Duration
Developing the Work Breakdown Structure to complete the assignment	04 days
Preparing diagram for “To-be” design activity according to case study of Su Ying’s Noodle Bar	03 days
Comparing AS-IS with To-BE process for assessing the impact of new system and illustration on the impact on business	03 days
Developing the screen designs after analyzing the identified two must user stories	04 days
Writing the acceptance criteria for the identified user stories	02 days
Drawing of an application architecture diagram to illustrate the various interfaces	03 days
Writing the executive summary to be included for presenting report to client to explaining the undertaken processes	02 days
Preparing the brief paper for client to present the key differences between Agile and Waterfall model	01 day
Preparing the video for presenting it to the client as a brief report of the project	01 day

Organisational change

The analysis of existing business operations within Su Ying’s Noodle Bar has reflected that they are facing difficulties with their manual system. Hence, it has been decided that a new information system along with website will prove to be beneficial for their business. The website will help to take the orders online so that there will be no errors or mistaking of orders as the customers will be able to see the different items before placing an order. The information system will help to perform the business operations smoothly and efficiently. The information system will also cater the needs of the business activities.

Acceptance Criteria

The major acceptance criteria for the new system is the user interface that means the users must be able to easily understand the functionality being offered by every component. The interface must be user friendly so that users can easily operate the system and does not face difficulty while accessing the system. The presentation of the system should be well defined and structured so that the modules within the system can be easily understood by the users. The security measure is also an important aspect of acceptance so proper security measure have also to be implemented as the system will record the information of customers as well as business related documents.

Applications Architecture

The supplier selection was carried out with the help of various steps that comprise of firstly identifying the suppliers based on requirements specification. Then the supplier selection process was started by collecting data from the suppliers and shortlisting them on that basis. After that, evaluation of the sample was carried out to determine feasibility of the supplier. Technical review was done as a due diligence process and cross functional visit was made to determine suitability of the supplier.

Agile and Waterfall differences

The key differences that exist between the Agile and Waterfall approach is illustrated as below:

	Pros	Cons
Waterfall Approach	· Simple and easily understood by the developers. · Clear documentation of all phases · Provides high visibility to developers · No requirement of engaging customers in later phases (Serrador and Pinto 2015) · Deadline can be easily controlled	· It is rigid and does not provided flexibility to easily change requirements during development phase · Identification of progress is difficult · Expensive than other approaches (Hiekata et al. 2016) · Completion time may vary if project assumptions are not done correctly
Agile Approach	· Focuses on team collaboration · Development is much quicker and easier · Cost efficient and cost can be easily managed (Komai, Saidi and Nakanishi 2016) · Involvement of customer at every step	· Cost is not always predictable · Difficult to understand but suitable for large projects · Easily development can be achieved with the support of customers by providing resources

Video Transcript

First of all, I would like to thank you for your kind consideration to give me this opportunity to carry out your project. As we all know this project is related to Su Ying’s Noodle Bar which is very popular in among the residents and nearby famers of Farawaytown located in remote northern China. The increase in their reputation is attracting more and more customers so it is getting difficult for them to handle their business operations manually. I have undertaken this project to propose an information system along with website which help them to handle their business operations smoothly and efficiently. So, in the first assignment I have identified the different modules that will be included in the system and presented them with the help of use case diagrams. I have identified the various stakeholders who will be associated with the system and I have also conducted MoSCoW analysis to determine their requirements. A “AS-IS” process diagram was designed to present the existing system within the business however it has been modified in assignment as “TO-BE” design to demonstrate the process that will be followed after implementation of the new system.

In assignment 2, I have conducted a thorough analysis of activities that are required for fulfilling the assignment criteria and the business requirements of Su Ying’s Noddle Bar. I have also presented discussions on the impact of new system on the business. After that, I have developed the screen designs after analyzing the identified two must user stories from assignment 1. Then, I have also written the acceptance criteria for the designed screens from identified user stories. I have designed the screens using Balsamiq Mockup tool which is a powerful tool for designing interfaces. I have also drawn the application architecture diagram with the help of MS Visio application for the system to demonstrate the various interfaces. After that, I was involved with writing the executive summary to be included for presenting report to client to explaining the undertaken processes. Finally, I have presented illustrations on the key differences existing between Agile and Waterfall approach so that proper decision can be made to select the right system development methodology. Lastly, I would like to thank you for your kind patience and hearing.

References

Aitken, A., Coombs, C. and Doherty, N., 2015. Towards benefit orientated business process modelling: a canonical action research study.

Doumeingts, G. and Browne, J. eds., 2016. Modelling techniques for business process re-engineering and benchmarking. Springer.

Goedertier, S., Vanthienen, J. and Caron, F., 2015. Declarative business process modelling: principles and modelling languages. Enterprise Information Systems, 9(2), pp.161-185.

Hiekata, K., Mitsuyuki, T., Goto, T. and Moser, B.R., 2016, October. Design of Software Development Architecture Comparison of Waterfall and Agile Using Reliability Growth Model. In ISPE TE (pp. 471-480).

Jeston, J., 2014. Business process management. Routledge.

Komai, S., Saidi, H. and Nakanishi, H., 2016. Man-Hour Comparison Between Two Methods of Agile and Waterfall in IT System Development. INNOVATION AND MANAGEMENT, p.1707.

Rosemann, M. and vom Brocke, J., 2015. The six core elements of business process management. In Handbook on business process management 1 (pp. 105-122). Springer Berlin Heidelberg.

Serrador, P. and Pinto, J.K., 2015. Does Agile work?—A quantitative analysis of agile project success. International Journal of Project Management, 33(5), pp.1040-1051.