Measures and Models in Software Engineering Assignment Sample

Measures and Models in Software Engineering Assignment

Want the Best Assignment Help in the UK? Look to Native Assignment Help for unparalleled expertise and support. Our dedicated team of professionals goes above and beyond to ensure you receive top-quality assignments that exceed your expectations.

Task 1

For developing such a booking system the departments of the computer science of Dublin University need to have an appropriate process model (Bajeh et al. 2020). Since focus has been made for the proper development of the booking system, so there has been selection made for the proper usage of the agile methodology. The usage of the agile methodology will help in the suitable accumulation of the resources. Moreover, there has been development of the Agile method will help in the considerable increase in the project efficiency through the proper allocation of resources in different parts of the project. For developing a booking system as well as a research system the department of computer science of Dublin University has chosen the agile process model. Agile methodology is indeed a technique that helps inside the software design process and allows for looking to the next level between testing and development.

With reference to the case study, the characteristics that could be highlighted for this agile approach are as follows:

• Delivery of predictable tasks with fixed delivery.
• There will be a significant increase in the visibility for the different stakeholders
• Adaptability, improvement and continuous testing.
• Increase in the transparency level for sharing relevant information about the project budget.

 However, unlike the Waterfall model, the testing phase is done in conjunction with this research method (Becker et al. 2021). This method leads to enhanced cooperation between users, programmers, executives, as well as testers. The agile process model is one of the best process models which has the ability to help and develop the booking system as well as the research system. There are some reasons which will support the agile process model to develop the booking system and the research system. The Agile process model will help to store or to keep the details about staffing, the details about the working time, and expenses of the project or the funding of the project. The process model of agile is an approach for the development of software. It basically the form of iterative development. With the use of this agile model process the project of developing a research and booking system will divide into comparatively smaller parts or iteration. As it breaks the development process booking and research into smaller parts, the chances of failing in the development process will minimum (Polyvyanyy et al. 2020).

With the use of the agile process model, the computer science department of Dublin University will get some advantages (Lavazza et al. 2021). Those advantages of the agile process model in the development of the research and booking system can be described in some points. The first one is, with the use of the agile process model, the delivery of the booking system and the research system will be unremitting. Secondly, the user of the research and booking system will be able to access each and every feature of the system. The third advantage can be said as if the developer of the system uses this process model then they will be able to introduce any further requirements to the system after implementing the system successfully. The fourth advantage can be described as, implementing this agile process model in the development of research and booking system; the user of that booking system will be able to provide any further need or requirement for the research system as well as for the booking system.

As there are advantages of using the agile process model, there are also some disadvantages or consequences, the developer have to face for the use of this agile process model (Syriani et al. 2019). The consequences or the disadvantages of the agile process model can be described in some points. Those are first if the developer uses agile process model to develop the system of research as well as booking they will get minimum documentation of their system, Secondly, with the use of agile methodology the requirement and the need in the system of the research and booking will not be clear properly and for that, there is a possibility to give a defected outcome, the third disadvantage can be described as the features of the agile process model are considered as ever-evolving, a risk factor is always there that is about the project’s over lasting. And the fifth disadvantage of the use of this agile process model in the development of the booking system as well as in the development of the research system it will be very difficult for the requirements of the resources to be estimated.

1. In the development of the booking system as well as for the research system of the Dublin University, the developer has used the agile process model. But there is also some other process model. One of them is the waterfall process model (Moreschini et al. 2021). In this development process, the waterfall process model was not chosen; there are several reasons for not choosing the waterfall process model and choosing the agile process model.

There are some key differences between the agile process model and the waterfall process model. Those differences can be described in some parts. An agile process model can be described as The Agile process model is indeed a method of program management that breaks work into phases (Lwakatare et al. 2019). Agile methodology is indeed a technique that helps inside the software design process and allows for looking to the next level between testing and development involves continuous user engagement as well as continuous improvement at each level. Whenever the job starts, groups have been through a cycle of planning, performing, as well as evaluating. Teamwork is essential, including both the project team and project users. And the waterfall process model can be described as a Waterfall process model that seems to be a sequential model that would be built on defined deadlines, objectives, as well as outcomes. Separate implementation groups really aren't needed to have been in constant communication that uses this method, and therefore are normally self-contained unless specialized connections are required. Members of the team generally chose to work independently and are often not required to submit status reports as regularly since they are with both the Agile approach. Usually, each step somehow doesn't start till it previous one was finished.

First of all, the process model of the waterfall is a sequential as well as a linear process model, so if the developer of fitness centre booking system used this they will have to face some hard difficulties to make the booking system and it also will happen in the development of the research system as well (Gollagi et al. 2017). So the developer has used the agile process model. The reason for that is this process model creates some small parts to develop the system successfully. Secondly, the agile process model will help to develop the booking system and the research system with flexibility whereas the process model of the waterfall work in a structured way for this if any frequent change or need should be introduced in the booking system or in the research system that will be very difficult for the developer of the Dublin University. For that, the department of computer science at Dublin University should use the agile process model to develop the booking system as well as to develop the research system for their university. There is also another reason for the developers to choose the agile process model instead of the waterfall process model (Krutauz et al. 2020). That is if the developer uses the agile process model in their development then the system of booking and research can be tested concurrently and make some changes if needed but if the developer uses the waterfall process model for the development then the test of the system will happen after the total development of the system. So, if any changes will be required then those will not be possible in between the process of development.

This is the comparison between the agile process model and the waterfall process model for choosing the agile process model over the waterfall process model for the development of the booking system and research system.

Task 2

Metrics are little more than established standards. Agile process models are the benchmarks that enable the team of the software that measures whether efficient individuals are now at different stages of the SDLC (Perdomo et al. 2021). Questions might be raised based in the four simple aspects for the booking system.

• Different matrices that is required for the generation of the system for measuring the software.
• Requirement for the product matrices that will help in the proper evaluation of the system state for research and booking. This will help in the proper implementation of the agile approaches for the software generation.
• Necessity for the process matrices that will help in the research and booking system development.
• Proper description of the project matrices that will help in the proper improvement of the system and thereby will assist in the suitable implementation of the agile methods.

References

Journals

Bajeh, A.O., Oluwatosin, O.J., Basri, S.H.U.I.B., Akintola, A.G. and Balogun, A.O., 2020. Object-oriented measures as testability indicators: an empirical study. J. Eng. Sci. Technol, 15, pp.1092-1108.

Becker, A. and Becker, J., 2021. Dataset shift assessment measures in monitoring predictive models. Procedia Computer Science, 192, pp.3391-3402.

Gollagi, S.G., Murthy, N., Pai, A., Swathi, K. and Pareek, P.K., STUDY OF SOFTWARE SECURITY MEASURES ADAPTION IN SME’S IN BENGALURU.

Krutauz, A., Dey, T., Rigby, P.C. and Mockus, A., 2020. Do code review measures explain the incidence of post-release defects?. Empirical Software Engineering, 25(5), pp.3323-3356.

Lavazza, L. and Liu, G., A Study of the Correlation between Functional Size Measures and Object-oriented Measures from UML Requirements Models. IWSM Mensura 2018, pp.54-69.

Li, X., Moreschini, S., Zhang, Z. and Taibi, D., 2021. Exploring factors and measures to select open source software. arXiv preprint arXiv:2102.09977.

Lwakatare, L.E., Raj, A., Bosch, J., Olsson, H.H. and Crnkovic, I., 2019, May. A taxonomy of software engineering challenges for machine learning systems: An empirical investigation. In International Conference on Agile Software Development (pp. 227-243). Springer, Cham.

Perdomo, W. and Zapata, C.M., 2021. Software quality measures and their relationship with the states of the software system alpha. INGENIARE-Revista Chilena de Ingeniería, 29(2).

Polyvyanyy, A., Solti, A., Weidlich, M., Ciccio, C.D. and Mendling, J., 2020. Monotone precision and recall measures for comparing executions and specifications of dynamic systems. ACM Transactions on Software Engineering and Methodology (TOSEM), 29(3), pp.1-41.

Syriani, E., Bill, R. and Wimmer, M., 2019. Domain-Specific Model Distance Measures. J. Object Technol., 18(3), pp.3-1.