7COM1024 Measures and Models in Software Engineering Assignment Sample
Here’s the best sample of 7COM1024 Measures and Models in Software Engineering Assignment, written by the expert.
Part 1: Software Process Models
Task 1
-
a) Analysis of appropriate software process model for the booking system
“Software process models” represent different types of models and their actual process through software. All the process models are very much simple to understand and the representation of those models is also very simple. Each and every process model has a specific type of perspective. There are various types of process models available in the digital market. Those models are the Workflow model, waterfall model, dataflow model, “evolutionary development model”, Action model, etc (Jamshidi, et al 2018). Process various types of hardware components software instructions set is very much essential. The software instructions-making process is not very simple; there are various types of sets that are essential. These sets of activities of sets are called sometimes “a software process”.
There are various types of components are required to make a software process, those are program, documentation, as well as operating procedures. Instructions are involved in the programming portion of the software processes. The next component is the documentation; various types of design, code details as well as documents are required in this part. The final component is operating procedures, this part help to instruct an organization on managing their work (Hersén, et al 2021). To make a complex routine, this part of the software process is most essential. There are different types of basic keys are available in the process activities, like specifications of software, development of software, validation as well as evolution. The specification of software id depends on the functional as well as non-functional requirements. A detailed analysis of the software is taking place in the specification part. There are various types of development also require in any software in the competitive world. The designing, documenting, bug identifying, bug fixing, programming are involved in the development part of the software. The validation of the software is based on the requirements of an organization. There are various types of needs that have to meet through the software; the validation part of the software can evaluate the product of the specifying software. The update is very much essential for each and every software to make it very much smart. So there are various types of evaluations are taking place in any software process (Amershi, et al 2019). Software initialization is also involved in the evolution portion of the software to make it very much smart.
In the software process, various types of crises are also taking place like the size of software, the cost of the software, the quality of the software. Nowadays, various types of complexity are taking place in the software, so the size of the software is most essential. If the size of the software will short, then the complexity will not huge. The cost of the software is also an important factor and is also an important crisis. If the software is more expensive, then it will not be affordable for everyone. The quality of the software depends on the cost sometimes, if the cost of the software will huge, then the quality will be very good. Good quality of the software is badly needed in the digital market, so the quality of the software is an important factor (Tantithamthavorn, et al 2018). The developing time of software will not be huge if it takes more time to create a bad effect on the developing organization, so the delivery time has to develop in the case of developing software.
In the “software process model” the workflow model is very much reputed because it is used to optimize various types of business processes of an organization. In the case of a booking system of an organization, the workflow model is very efficient. This model is helpful to show all the processes of booking of an organization, to achieve various types of goals this model is very much helpful (Siegmund, et al 2017). There are various types of advantages “of the brainstorming” is also takes place in the case of workflow model in the software process. “The waterfall model” is also an important model of the booking system of an organization. There are various types of factors are involved in the waterfall model like implementation of software, design of software, specification as well as testing. The next appropriate model for a booking system is the dataflow model. This model basically represents various types of diagrams of software in the case of information flowing purposes. The data exchanging process is also taking place in the dataflow model, it is essential for the software process also.
The Evolutionary Model is a useful model for any type of booking system of an organization. In the “software development life cycle” the model of the Evolutionary is the combination of various types of models like an iterative model (Azzeh, et al 2018). The data delivering process is an important factor in the software process. In this model delivering process is enhanced, various types of architecture envisioning as well as initial requirements are also involved in this model. This model is better than any other model because there are various types of features ate take place in the model like user feedback and so on. This model can divide the development part of the software in various ways, so it creates a big advantage in any organization. The final model of the software process is the auction model. This model is based on the role of the employee, who is involved in the “software process”. In the prototype model, various types of prototypes are set for the understanding purpose (Dandekar, et al 2019). The requirements of the customer are very much essential; the prototype model can help to achieve all the requirements of the customer. The feature of various types of products is also involved in the prototype model. The spiral model of the software process is used to reduce various types of risk from software. In the critical project, different types of risk came and hampered work, in this time the spiral model works. This model is not very much affordable, because the cost of the model is very much high. In the case of long-term type risky processes, the spiral model is used.
-
b) Compensation with other “Software Process Model”
In the “software possess models” various types of models are taking place, like waterfall model, incremental model prototype model as well as spiral model. All the models have some advantages and disadvantage disadvantages also. In the booking system of an organization, various types of features are involved. The waterfall model is appropriate for the booking system, but the incremental model is not much more appropriate for the booking system. There are various types of features are required in the booking system of an organization, but the incremental model did not fulfil all the requirements (Striuk, et al 2019). There are various types of troublesome factors are came due to the booking of an organization. The spiral model can reduce various types of risk from the system; the incremental model is not efficient to reduce various types of risk from the system. In the incremental model, various types of new technology are used. New technology is required in the system; sometimes new technologies create different types of risk in the whole system. It can hamper all the booking systems, so this model is not efficient. In the waterfall model technologies are used, but all the technology of the waterfall model is very much familiar so the issues on the technology are not taking place in this model. So in the booking system of an organization, the waterfall model is appropriate.
The prototype models are essential in the booking system because they can clearly describe all the requirements of the customers. The customers are the key to the growth of an organization. So if any model of software process looks at the requirements of costumes very carefully, then this model will be very much efficient (Botchkarev, et al 2018). The incremental model customers’ requirements are not given any priority, so this model is not appropriate for the booking system of any organization. The design, different types of developments, and the testing portions also take place in this model. The main requirement of the software model is text, this part is needed but in the booking system text is a less important factor. The next appropriate model for a booking system is the dataflow model. This model basically represents various types of diagrams of software in the case of information flowing purposes. The data exchanging process is also taking place in the dataflow model, it is essential for the software process also. In the incremental model, the diagram portion does not take place (Galhotra, et al 2017). The diagram representation is very much an essential factor in the case of the booking system, so the incremental model is not very much appropriate for the booking system of an organization. The requirements of the customer are very much essential; the prototype model can help to achieve all the requirements of the customer. The feature of various types of products is also involved in the prototype model. In the incremental model, customers are not given any type of preference so this software model is not appropriate for the booking system.
Part 2: Software Measurement and Metrics
Task 2
In the booking system, various types of software programming are required. In the Dublin University approximately, 5000 staffs are works. So the booking will be complex for all the members of the university as well as for students also. There are different types of facilities are available in the specific university like swimming pool, gym and others. If the booking software of the university faces some kinds of problems, it will take a loge time to identify all the problems from the booking software. A strong software development team is taking place at the Dublin University (Sobri, et al 2017). In the programming code, various types of troublesome issues come. The software development team is very much strong in the case of Dublin University. To reduce various types of errors from a programming code, firstly the programming team has to recognize the debugging function. In this research, various types of complexity reduction processes are proposed to reduce the time from the programming code. If the programming time is reduced, it will be very much beneficial for any organization. The next step is software testing where the software is tested for development and implementation. The very first-time reduction process is a cyclomatic process; this process can identify various types of troublesome functions from any programming code. There are different types of complexity are come due to the branch code of the programming code. Each and every statement has different types of branch code and that makes a program very much complex.
In the case of Npath complexity, various types of functions are involved, these function makes the programming code much more complex. The method of various types of functions is calculated in this stage. In this complexity, the input functions of the programming code will be huge. The if/else statement is also a very important factor in the case of programming code. In the case of the time reduction process in programming code, the software developer has to use the easiest programming language. The complexities arise that says that sometimes the platform can’t understand the details that the coding wants to show in the system and thus the error occurs in the execution of the coding. The software developer may use python because this is one of the easier programming languages nowadays. A small method can make a programming code much easier, as well as it can reduce time. The team of Dublin University has to adopt a few lines programming method so that if any types of error come in the programming code, it will be reduced easily. The improvement of the programming code can reduce the time for a certain time. The coders must apply the method of cyclomatic complexity so that the time that is required for the development of the code reduces. The Time reduction process can be done, by reducing of if/else “statement” from the programming code. This program can be done by using the if statement only, there is no need for else statement in the programming code (Jelodar, et al 2019). The else statement makes a programming code much more complex. The developer has to use a recent programming language to reduce the time from the programming code. The old programming language was very much lengthy as well as complex, but the new programming language is very much easier than others.
This part of the research is discussed all the questions, that are come due to this research. Knowing about the research clearly this portion of the research is very much essential. The code in python uses the cyclomatic method for the reduction of the complexities and thus the overall development of the system requires the coders to show the reduction of the system time that the development of the software takes. In every research, there are several research questions that are faced in the reporting time in every research; there are several research questions that are faced the reporting time.
What is the need for proper planning to develop software in a certain coding platform? This question can justify the software metric, planning. There are various types of characteristics are involved in the software metric. The very first characteristic is quantitative; this can process the quantitative nature of the software matrices’. So it is clear that the quantitative metric can express different types of value of software matrices’ (Fifo et al. 2019). The understanding characteristic is the most important characteristic of the software metric. In this part, it is clear that the software matrices are very much easier so that they can be understandable for each and every person.
Why an organizing system arrangement is mostly needed in an organization?
The software metrics can apply in the initial phase of the software portion. There are various types of development that can do in the software portion by using software metrics. The product metrics are also important in the programming code; these metrics can reduce various types of risk in the product purpose.
Is the controlling process badly needed for the growing purpose of an organization?
The team is very much important to control all the management of an organization. So teamwork is very much a necessary part to grow an organization. The process metric can help to control the software portion.
Is improving the programming code necessary for the booking system?
There are various types of improvements that are needed in the software development purpose, the teamwork purpose. The cost is a very much an important factor of a project, so the improvement on the cost is very much essential factor (George, et al2017). The team organization is also a crucial factor; the management has to improve the teamwork. It is also involved in the software metric, and the metric can improve all.
Reference List
Journals
Amershi, S., Begel, A., Bird, C., DeLine, R., Gall, H., Kamar, E., Nagappan, N., Nushi, B. and Zimmermann, T., 2019, May. Software engineering for machine learning: A case study. In 2019 IEEE/ACM 41st International Conference on Software Engineering: Software Engineering in Practice (ICSE-SEIP) (pp. 291-300). IEEE.
Botchkarev, A., 2018. Performance metrics (error measures) in machine learning regression, forecasting and prognostics: Properties and typology. arXiv preprint arXiv:1809.03006.
Dandekar, K.R., Begashaw, S., Jacovic, M., Lackpour, A., Rasheed, I., Rey, X.R., Sahin, C., Shaher, S. and Mainland, G., 2019, June. Grid software defined radio network testbed for hybrid measurement and emulation. In 2019 16th Annual IEEE International Conference on Sensing, Communication, and Networking (SECON) (pp. 1-9). IEEE.
Fifo, M., Enoiu, E. and Afzal, W., 2019, April. On measuring combinatorial coverage of manually created test cases for industrial software. In 2019 IEEE International Conference on Software Testing, Verification and Validation Workshops (ICSTW) (pp. 264-267). IEEE.
Galhotra, S., Brun, Y. and Meliou, A., 2017, August. Fairness testing: testing software for discrimination. In Proceedings of the 2017 11th Joint Meeting on Foundations of Software Engineering (pp. 498-510).
George, E., Liacouras, P., Rybicki, F.J. and Mitsouras, D., 2017. Measuring and establishing the accuracy and reproducibility of 3D printed medical models. Radiographics, 37(5), pp.1424-1450.
Hersén, N., Hacks, S. and Fögen, K., 2021. Towards measuring test coverage of attack simulations. In Enterprise, Business-Process and Information Systems Modeling (pp. 303-317). Springer, Cham.
Jamshidi, P., Velez, M., Kästner, C. and Siegmund, N., 2018, October. Learning to sample: exploiting similarities across environments to learn performance models for configurable systems. In Proceedings of the 2018 26th ACM Joint Meeting on European Software Engineering Conference and Symposium on the Foundations of Software Engineering (pp. 71-82).
Jelodar, H., Wang, Y., Yuan, C., Feng, X., Jiang, X., Li, Y. and Zhao, L., 2019. Latent Dirichlet allocation (LDA) and topic modeling: models, applications, a survey. Multimedia Tools and Applications, 78(11), pp.15169-15211.
Siegmund, J., Peitek, N., Parnin, C., Apel, S., Hofmeister, J., Kästner, C., Begel, A., Bethmann, A. and Brechmann, A., 2017, August. Measuring neural efficiency of program comprehension. In Proceedings of the 2017 11th Joint Meeting on Foundations of Software Engineering (pp. 140-150).
Sobri, W.A.W.M., Fauzi, S.S.M., Nasir, M.H.N.M., Ahmad, R. and Suali, A.J., 2017. Measuring The Impact of Socio-Technical Congruence in a Different Types of Software Life Cycle. Sains Humanika, 9(1-3).
Striuk, A. and Semerikov, S., 2019. The Dawn of Software Engineering Education.
Tantithamthavorn, C., Hassan, A.E. and Matsumoto, K., 2018. The impact of class rebalancing techniques on the performance and interpretation of defect prediction models. IEEE Transactions on Software Engineering, 46(11), pp.1200-1219.
Wagner, S. and Ruhe, M., 2018. A systematic review of productivity factors in software development. arXiv preprint arXiv:1801.06475.
________________________________________________________________________________
Know more about UniqueSubmission’s other writing services:
