Business Processes For Home Design Limited And Comparison Of Predictive And Adaptive System Development Approaches

Business Processes for Home Design Limited

The project development depends on many of the factors and an evaluation is required to be made on the requirement of the project for effective development of the project. The requirement of the project is required to be made clear with the arrangement of the stakeholder meetings and the goals and objectives of the project is required to be created (Francalanza, Borg & Constantinescu, 2017). The familiarity of the project for the project development team is required to be considered for the adoption of the predictive or adaptive project development approach. The known projects can be developed easily with the adoption of the predictive development planning methodology (Hollensen, 2015).

The predictive method can be the waterfall method and a planning of the development of the project is done according the structure followed by the waterfall model. For the project that have some uncertainty the predictive model cannot be used and thus the adaptive model such as the agile methodology can be applied for the development of the project (Khodakarami & Chan, 2014). The two methodology are compared and contrasted with each other for the helping the manager to take effective decision for the application of the project development methodology in the current project and get the best outcome.

The main targeted audience for the development of the project are the business executives who have more knowledge in the business filed than the computer and the software development. The project required to be developed is a customer relationship management system for the Home Design Limited that would record all the details of the customer and their purchase and manage the supply chain of the business for providing effective service to the customer. A joint application development session is required to be arranged with the stakeholders associated with the development of the system for understanding the requirement of the project (Van De Walle, Turoff & Hiltz, 2014).

In the project different home ware stores can register for business with the Home Design Limited by registering into the system and for the verification of the register form a time is taken and if all the points are found valid a link is required to be sent for opening an account for the home ware stores. The Name, Business number, Address, Telephone, Email, Application date, Discount level, Sales area, and Date last visited are required to be recorded in the registration form for contacting the business (Duncan, 2014).

The sales area of the business is required to be defined and the areas that have insufficient salesperson is required to be identified for recruiting more number of sales person for serving the customer in the sales area (Goetsch & Davis, 2014). A management team is required to be created for the management of the sales records and reports for the management of the sales personnel. The report is required to be consisted of amount of sales as per the sales area and person recruited in the area (Hill, Jones & Schilling, 2014). The payment records is required to be included in the system for reducing the complexity and the main focus of the system is on the improvement of the current business process and increase the efficiency for serving more number of customer at a time. 

Comparison of Predictive and Adaptive System Development Approaches

For the development of the information system the requirement is not clear regarding the creation of the module for the sales area and inclusion of the sales person for serving the customer and thus an adaptive approach is used for the development of the project. With the adoption of the predictive planning the all the condition of the project is required to be clear and the project team members should have previous experience or knowledge regarding the development of the project (Dennis, Wixom & Tegarden, 2015).

The project does not fulfill all the criteria important for the adoption of the predictive approach and thus it cause a risk of uncertainty and over budget if the predictive methodology is applied in the development process of the project. The requirement of the project is assumed to change during the final stage of the project development and due to the incremental nature of the agile methodology the change in the project can be managed easily and the risk of over budget can be resolved (Coronel & Morris, 2016). The project is developed into different functional module and a specific time limit is required to be assigned for the development of the project.

For the adoption of the agile methodology the objectives of the project is required to be cleared and the flexibility of the objectives are required to be made clear and prioritized for the determination of the outcome of the development of the project. The customer relationship management system is required to be developed in stages and a series of deliverables are provided to the client for analysis (Niu et al., 2014).

The modification that is required to make in the functional modules are identified by the client and returned to the project development team for revision and recasting. The main principal of the agile model is the modelling of the software product and the main goal of the development is to embrace the changes in the project and building of multiple models. The main focus is required to be given on the contents of the project and the team members is required to be communicate with each other for the adaptation of the needs of the project.

With the adaptation of the agile method the design is required to be kept simple and each of the model created should have a definite purpose. The agile methodology can be adopted and for the development of the software platform and other methodology like UP, XP and the SCRUM can also be used for the development of the functional module (Inam et al., 2015). Under the unified process the UML models are used and the set of the activities involved in the process can be identified for the development of the customer relationship management system (Peppard & Ward, 2016).

With the application of the agile software development methodology the clients are also involved in the development stage and thus it results in better productivity and it improves the quality of the finally build software product. There are different steps that are involved in the development of the software product following the agile technique such as conducting a brainstorming session for the identification of the parameters required for the development (Schnoll, 2015). The functional components are required to be produced and is required to be delivered to the client for evaluation and feedback.

Use Cases for Predictive and Adaptive System Development Approaches

The feedback gained from the client are analyzed and implemented in the project goals and another component is developed following the feedback. It is best suited for the undetermined condition for the project and if the project development team is flexible to adopt the change in the project (Djakovic & Kleiner, 2015). The project development team is required to be kept small and the project manager is required to be experienced about the software development for monitoring the progress of the work. For a large project the project tem is required to be divided into sub teams and the communication between them is required to be improved such that broader input can be given in the project from different sources.   

The agile methodology is the best project development approach for in house development of the project. For the development of the project many software packages are required such as Microsoft project, Project kickstart, etc. The project manager is responsible to create a schedule and work breakdown structure for estimation of the time required for the creation of the functional module (Caiani et al., 2016). The resource available for the organization is required to be listed and assigned with each of the project development phase for proper estimation of the budget and the cost of the project. A risk management plan is also required for prioritizing the risk associated with the development of the project.

It can be concluded the project required to be developed is a customer relationship management system for Home Design Limited and the system is required to include the records of the retail outlets. The system is developed for including the selling and the ordering system in the database and use it for the preparation of the report. The stock of the products, geographical area assigned to the sales person is required to be included in the system for management of the team.

The different project development methodology is analyzed according to the requirement of the project and it has been found that the application of the adaptive system for the development of the project would be useful for developing the project. The project is complex and there are some uncertain factors that can affect the development of the project and thus the adaptive approach is the best solution for the accommodation of the changes in the project. It also helps in active involvement of the project stakeholders and thus produces a good quality final software product. The project team members is required to be divided into smaller sun groups and communicate with each other to implement innovative ideas in the project and help in increasing the efficiency of the current business process of the organization.

Caiani, A., Godin, A., Caverzasi, E., Gallegati, M., Kinsella, S., & Stiglitz, J. E. (2016). Agent based-stock flow consistent macroeconomics: Towards a benchmark model. Journal of Economic Dynamics and Control, 69, 375-408.

Coronel, C., & Morris, S. (2016). Database systems: design, implementation, & management. Cengage Learning.

Dennis, A., Wixom, B. H., & Tegarden, D. (2015). Systems analysis and design: An object-oriented approach with UML. John Wiley & Sons.

Conclusion

Djakovic, R., & Kleiner, B. (2015). Excellence In The Implementation And Design Of Effective Customer Focused Business Information Systems. Business Journal for Entrepreneurs, 2015(1).

Duncan, O. D. (2014). Introduction to structural equation models. Elsevier.

Francalanza, E., Borg, J., & Constantinescu, C. (2017). Development and evaluation of a knowledge-based decision-making approach for designing changeable manufacturing systems. CIRP Journal of Manufacturing Science and Technology, 16, 81-101.

Goetsch, D. L., & Davis, S. B. (2014). Quality management for organizational excellence. Upper Saddle River, NJ: pearson.

Hill, C. W., Jones, G. R., & Schilling, M. A. (2014). Strategic management: theory: an integrated approach. Cengage Learning.

Hollensen, S. (2015). Marketing management: A relationship approach. Pearson Education.

Inam, A., Adamowski, J., Halbe, J., & Prasher, S. (2015). Using causal loop diagrams for the initialization of stakeholder engagement in soil salinity management in agricultural watersheds in developing countries: A case study in the Rechna Doab watershed, Pakistan. Journal of environmental management, 152, 251-267.

Jiraporn, P., Jiraporn, N., Boeprasert, A., & Chang, K. (2014). Does corporate social responsibility (CSR) improve credit ratings? Evidence from geographic identification. Financial Management, 43(3), 505-531.

Kaner, S. (2014). Facilitator’s guide to participatory decision-making. John Wiley & Sons.

Khodakarami, F., & Chan, Y. E. (2014). Exploring the role of customer relationship management (CRM) systems in customer knowledge creation. Information & Management, 51(1), 27-42.

Messersmith, C., & McIntosh, B. (2015). Capturing Bad Design Practices in Object-Oriented Code.

Milanese, M., Norton, J., Piet-Lahanier, H., & Walter, É. (Eds.). (2013). Bounding approaches to system identification. Springer Science & Business Media.

Nikolaou, I., Evangelinos, K., & Leal Filho, W. (2015). A system dynamic approach for exploring the effects of climate change risks on firms’ economic performance. Journal of Cleaner Production, 103, 499-506.

Niu, N., Da Xu, L., Cheng, J. R. C., & Niu, Z. (2014). Analysis of architecturally significant requirements for enterprise systems. IEEE Systems Journal, 8(3), 850-857.

Peppard, J., & Ward, J. (2016). The strategic management of information systems: Building a digital strategy. John Wiley & Sons.

Rosen, M., Lublinsky, B., Smith, K. T., & Balcer, M. J. (2012). Applied SOA: service-oriented architecture and design strategies. John Wiley & Sons.

Sachdeva, A., & Sunita, M. (2015). An Empirical and Analytical View of New Inheritance Metric for Object-Oriented Design.

Sanderson, E., & Windmeijer, F. (2016). A weak instrument F-test in linear IV models with multiple endogenous variables. Journal of Econometrics, 190(2), 212-221.

Schnoll, H. J. (2015). E-government: Information, technology, and transformation. Routledge.

Setianto, N. A., Cameron, D., & Gaughan, J. B. (2014). Identifying archetypes of an enhanced system dynamics causal loop diagram in pursuit of strategies to improve smallholder beef farming in Java, Indonesia. Systems Research and Behavioral Science, 31(5), 642-654.

Sharon, A., & Dori, D. (2015). A Project–Product Model–Based Approach to Planning Work Breakdown Structures of Complex System Projects. IEEE Systems Journal, 9(2), 366-376.

Smith, B. (2015). Object-Oriented Design… A Revisit. In Advanced ActionScript 3 (pp. 357-371). Apress.

Soni, N., & Khaliq, M. (2015). Maintainability estimation of object-oriented software: Design phase perspective. Int. J. Adv. Res. Comput. Commun. Eng, 4(3), 538-542.

Van De Walle, B., Turoff, M., & Hiltz, S. R. (2014). Information systems for emergency management. Routledge.

Vir, R., & Mann, P. S. (2013). A hybrid approach for the prediction of fault proneness in object oriented design using fuzzy logic. journal of academia and industrial research, 661-666.

Wu, P. P. Y., Fookes, C., Pitchforth, J., & Mengersen, K. (2015). A framework for model integration and holistic modelling of socio-technical systems. Decision Support Systems, 71, 14-27.

Zhou, Y., Yang, Y., Xu, B., Leung, H., & Zhou, X. (2014). Source code size estimation approaches for object-oriented systems from UML class diagrams: A comparative study. Information and Software Technology, 56(2), 220-237.

Order an Essay Now & Get These Features For Free:

Turnitin Report

Formatting

Title Page

Citation

Outline

Place an Order