Software Development Basic Design Used in a Software Design Process

Question: 1. Explain why the odds of a risk arising and the impact of those risks occurring are likely to change over the course of the project.2. Explain why a software estimation model, like COCOMO, might not apply to a very large software project the exceeds one million lines of code. Answer: Project Planning and Approach Waterfall model is a sequential approach of the basic design used in a software design process. The main steps of the design are approached sequentially in order to maintain a balance in the designing phase of the software. The sequences followed are as shown below. Figure 1: Waterfall Sequence used in Software Design (Source: Created by Author) In the requirements phase, the requirements and the necessary tools and parameters are analyzed and collected. For example, during coding process, the necessary values of the parameters of the software are analyzed and determined. In the design phase, the basic design of the software is made according to the determined values of parameters and the requirements of the software. In the implementation phase, the values are implemented into the design framework in the form of codes or command lines. Operations of these command lines drive the software according to requirements. In the verification phase, the command lines are verified whether they meet the requirements of the software or not. Moreover, verification also enables the designer to detect any error in the command sequence. Maintenance phase is needed to execute the commands in a proper sequence for the whole running time of the software (Kumar Singh, 2015). The waterfall is more suitable for the design processes of simple so ftwares that have low running time. For complex software programming, the SCRUM based approach is used. In the SCRUM approach, no particular approach is followed. Rather the complex parts of the program are coded and then matched with real world results. Since the running times of the complex softwares are extremely high, the total time is divided into several phases and modifications are done to each phase. After all the modifications and new entries are complete, all the phases are integrated together. The main working theory of this approach is that, in this method, the unnecessary parts of the software program are eliminated and fixed values or constants are added to the command lines (Bosnic et al., 2015). The SCRUM methodology includes a fixed set of rules, guidelines and steps that must be followed during the course of the project. 1. During the course of the project, the odds of risks and their effects change gradually because the codes are constantly changed after testing and checking. During the course of the project, the parts of the software design codes are checked and evaluated using software estimation tools. If errors are detected, the code line (or lines) is changed accordingly. Hence, the odds of risk also changes accordingly (Alam et al., 2013). The possible effects of risks also change since changes are made to the software coding constantly. 2. COCOMO is a basic software estimation model that is used to determine the running time of a software. In a large software design containing more than millions of code lines, the running time gradually tends to infinity with respect to the start time estimation. Hence, if COCOMO is used in determining the running time, it will encounter infinite time and will show errors (Garg et al., 2014). COCOMO is basically designed to determine the running time of only a part of the software during designing phase. References Alam, O., Kienzle, J., Mussbacher, G. (2013). Concern-oriented software design. InModel-Driven Engineering Languages and Systems(pp. 604-621). Springer Berlin Heidelberg. Bosnic, I., Ciccozzi, F., Di Nitto, E., Feljan, J., Mirandola, R. (2015). Introducing SCRUM into a Distributed Software Development Course. Garg, K., Kaur, P., Kapoor, S., Narula, S. (2014). Enhancement in COCOMO Model Using Function Point Analysis to Increase Effort Estimation. Kumar, B., Singh, K. (2015). Testing UML Designs Using Class, Sequence and Activity Diagrams.International Journal for Innovative Research in Science and Technology,2(3), 71-81.