R-paper and Discussion
Discussion posts:
Discussion post1:
Discussing three traditional software processing models
In an organization, the developers certainly have the role to play for creating a successful system, and for that reason, they are seen to be utilizing some of the important processing models that deal with the traditional software (Dasoriya, 2017). The development of these models always helps the developers to do their work in a proper way as the contribution of these models directly connects to provide support in building the system successfully. Further discussion would be done on the three models that are usually utilized by the developers. There are not only three models that have been utilized by the developers but from my point, they are the important ones along with their benefits and some of their drawbacks.
Waterfall model
A sequential model through which development of the software could be divided into phases that are pre-defined. The phases are seen to be designed for providing performance on some particular activities with the phase of SDLC starts its work (Kaushik, Bharadwaj, Awasthi & Sharma, 2017). It is seen that before starting the next phase, the other phases would be completed so that there is no overlap between any of the phases. Different phases have a different function during the time of their utilization by the developers. The waterfall model could be utilized when the requirements are clear and the length of the project work is seen to be short.
Advantages
Each phase is certainly seen to be completed before starting the next one. The model is seen to be best when the project is small with well-defined requirements. It has the ability to perform a quality assurance test before proceeding to the next stage.
Disadvantages
One of the main drawbacks of this model is that only the errors could be reduced during the time of doing work within the phase. The period of testing is seen to be coming late during the time of the developing process. Developers waste their maximum time on doing the documentation.
Iterative model
This model is certainly found to be focusing on implementing the simple and initial phase but finds it difficult and complex when setting the broader feature when it gets completed. It is also a part of SDLC and the concept could be interchanged with the incremental model technique at some point of time (Arora & Arora, 2016). It is actually seen to be describing the alterations which relate to the incremental procedure that happens during the implementation and design of the latest iteration process. The utilization of this model is seen to be done during the time of analysis and doing some planning in the system.
Advantages
The model is seen to be productive and best for the agile organizations and the version is found to be inherent. Planning of parallel development is certainly found to be possible with the help of this model technique. It is found to be cost-effective during the time of changing the requirements in the system.
Disadvantages
The requirement of the resources is certainly found to be more as compared to the other models during the time of the work process. It is not applicable to the projects whose size is small. In doing skill analysis, it requires resources that are high-skilled. During the time of engaging the user, the pressure is certainly found to be increased.
Spiral model
The combination of waterfall and iterative model actually describes the spiral model and the development is done in a systematic manner with getting the condition right for the developers when maintaining the system in a successful way. The model actually consists of four phases and these four phases certainly have a different role to play during the time of its implementation (Singh & Kaur, 2017). The starting of this model’s work with the goal of the design and finishes with the progress from a review of the client. The utilization of this model has been done mainly on larger projects and this is the difference with the others.
Advantages
The main benefits come with the change in the requirements and this could be easily accommodated by this model. It helps in allowing the use of prototypes that are seen to be expensive. It is seen that through this model, capturing the requirements is found to be simple and easy.
Disadvantages
Complexity is mainly found during managing the development of the process. The process that is seen to be used is found to be complex. The end time of the project could not be known properly through this model at the early stage.
Discussion post -2
Prototyping model
Most relevant model of software processing is prototyping. The system which is developed to identify the demands of the customers can be defined by the model of the prototype. The model is beneficial to get the support of the entire developing system while the developer wants to develop the software (Gebert, Onken & Tracht, 2018). The developer will get the appropriate information with the model about the desired requirement of the customers. Thus the customers can get satisfaction with the model.
Advantage
The developer can use the proper algorithm for developing the software with respect to the requirement. The set up for developing the efficiency and the response time also be done with respect to the knowledge getting from the model about the demand. The customers are involved with the entire process of development. Therefore the development is appropriately done with the regular supervision of the customers. The customer is easily willing to accept the project as the entire process is known for them. The satisfaction level is more with the model of the developing the software. In the system designing the process is mainly used. The developer can easily design the system with respect to the customer’s point of interest.
Disadvantage
In the practical field, the method creates more complexity. Sometimes the changing demand of the customers became a challenge for the developer to develop the software with the model. In the model, the incomplete applications are used. The model helps to develop the entire system. Thus the complete application is not effectively used.
Spiral model
The combination of the interactive and the waterfall model for developing the software is described by the spiral model. In the traditional model, this type of model is more beneficial to design the ultimate goal for developing the software. In the initial stage, the model helps to compute the design of the goal, and the client reviewing is also involved with the model proceedings. The development process is conducted by going through small sets. The sets are associated with the requirement of the clients and after that, it helps to configure each phase of the development.
Advantage
Processing model regarding the spiral model is beneficial to analyze the higher amount of the risk. The assessment process is helped to avoid risk factors while developing the software. It is also beneficial for controlling the documentation (Chen, Zhang, Wen, Looi & Yeo, 2019). The smeller set of requirements provides support for the development of the software. The customers have easily approved the development of the software as they are effectively involved with the process. The desired outcome can be achieved in a short time.
Disadvantage
It is a costly model in the various types of traditional models. Creating various requirement sets needs more money. It is only useful for the bigger price. The huge budgeted project only preferred the model. The model is disadvantaged for the smaller projects which have no sufficient budget. The low-risk project is also not appropriate for the model as it is beneficial for assessing the higher amount of risk.
Agile Model
The development of the software is accomplished with the incremental type of model which cannot be defined by the agile model of processing. The process is included in the rapid cycle of the process. The method of developing with the model is related to the interactive types of development (Lano, 2017). The rapid cycle is beneficial for testing the software. Therefore the quality of the software maintained properly. The process is popular for the unique types of views points which is related to the traditional attributes.
Advantage
In the model, the interactions of the customers are emphasized. The model is beneficial to deliver the working software very frequently. Therefore the development of the software became easier for the developers. The process of interaction provides a greater influence on the developers for developing efficient software which goes with the requirement of the clients. The face to face communication is held with the support of the model. The technique of the conversation is beneficial for gathering feedback and gets accurate knowledge about customer demand. The developer also creates the design as per the requirement easily.
Disadvantage
The model is not appropriate for examining the larger size of the system. The developer faces the issues while the larger size software examined. The more effort is required for developing the larger size of the software which takes more time. The development of the software is not time-saving while using the model of Agile. The project of developing the software can lose track while using the model for big projects.
Discussion post-3:
A software process model signifies the order in which the actions of software development will be assumed. Three main traditional “software processing” models and their respective advantages and disadvantages discuss as follows:
1. Waterfall Model
It is one of the most popular and widely employed methods to develop software. This model is also used as the classic way of developing software. The method of returning to the previous step to fix improvements in specifications is not specified by this creation strategy (Sarker, Faruque, & Hossen, 2015).
Advantages: It is very easy to understand and use a method, and for the novice or existing developer, it is very beneficial. For smaller programs where specifications are well understood, this type of development model works most efficiently.
Disadvantage : The only disadvantage of this method is that it is not feasible to go back and change it until a program is in the evaluation stage. In the last stage of the cycle, there is little chance of producing any working software (Misra, Omorodion, & Fernandez-Sanz, 2014).
2. Agile Software Development
It is a method for developing a structured software management process that often facilitates a minimum amount of regular improvements in the implementation project. It is a type of method to build software that is one conceptual structure for numerous “software development” projects.
Advantages: An Agile / Scrum approach promotes creativity and invention in order to optimize the solution’s market worth. Planning and management over-emphasis continues to hamper ingenuity and progress (Holland, 2016). It typically contributes to faster time-to-market because of shorter start-up periods.
Disadvantage: This method focuses more than documents on working software so that it may result in a lack of data. If consumers are not sure regarding the ultimate results of their programs, therefore a software development project will go off course.
3. Spiral Model
It is a sophisticated model that concentrates on detecting early project risks and growing them (Misra, Omorodion, & Fernandez-Sanz, 2014). The development progresses as it progressively passes through the various phases of the growth process – as though it were a spiral. Based on the project size, there can be some number of loops.
Advantages: It is one of the most flexibly applied SDLC types. Development stages based on the scope of the project may be decided by the project manager. It is ideal for programs of high risk, where market conditions may be unpredictable.
Disadvantage: This model generally entails large costs. Expertise required, from time to time, for the assessment and analysis of the project (Sarker, Faruque, & Hossen, 2015). It can continue indefinitely and never complete, as the great danger of this technique.
Discussion post 4:
Traditional software process models
There are various type of software system which organisation uses in the time of production so that they can get accurate product which can satisfy human wants. Traditional software process is basically a software which is used from many years has it is one of the traditional software system which generates many type of models as this model serves Organisation in a positive way. One of the major traditional software process model is waterfall model. With the help of waterfall model the organisation can design it system correctly and accurately as with the help of the systems organisation can be able to deal with every situation correctly and properly without damaging the name and the reputation of the organisation in the market. There are various benefits which the company enjoy whenever the use different software models like v-shaped model in it as because of V-shaped model the company can make any changes during the time of process and hence it is very essential for the company as because of flexibility of v shaped model if there is any type of errors in the system that because of this benefit the organisation can make their correct and then let the system work accordingly (Omar, 2017).
Also because of another software processor like evolutionary prototype model the organisation can do a quality test on their products as with the help of this test the organisation can know how suitable the product has been and how it can impact the life of the human in a positive way as if there is any type of problems all defect in the product then the organisation can make it correct and then send it into market for the sale. Therefore, whenever there are different types of models used in the organisation then, there is less chances of having a defective products and hence this is very useful for the organisation during the time of manufacturing. Because of this reasons waterfall model, v-shaped model and evolutionary prototype model are major of software process model which can be use by the organisation to be Victorious in the market (calpoly.edu, 2018).
Discussion
posts:
Discussion
post
1:
Discussing three traditional software processing model
s
In an organization, the developers certainly have the role to play for creating a successful system,
and for that reason, they are seen to be utilizing some of the important processing models that deal
with the traditional software (Dasoriya, 2017). The de
velopment of these models always helps the
developers to do their work in a proper way as the contribution of these models directly connects to
provide support in building the system successfully. Further discussion would be done on the three
models that a
re usually utilized by the developers. There are not only three models that have been
utilized by the developers but from my point, they are the important ones along with their benefits
and some of their drawbacks
.
Waterfall mode
l
A sequential model throug
h which development of the software could be divided into phases that are
pre
-
defined. The phases are seen to be designed for providing performance on some particular
activities with the phase of SDLC starts its work (Kaushik, Bharadwaj, Awasthi & Sharma,
2017). It is
seen that before starting the next phase, the other phases would be completed so that there is no
overlap between any of the phases. Different phases have a different function during the time of their
utilization by the developers. The waterfa
ll model could be utilized when the requirements are clear
and the length of the project work is seen to be short
.
Advantage
s
Each phase is certainly seen to be completed before starting the next one. The model is seen to be
best when the project is small
with well
-
defined requirements. It has the ability to perform a quality
assurance test before proceeding to the next stage
.
Disadvantage
s
One of the main drawbacks of this model is that only the errors could be reduced during the time of
doing work within
the phase. The period of testing is seen to be coming late during the time of the
developing process. Developers waste their maximum time on doing the documentation
.
Iterative mode
l
This model is certainly found to be focusing on implementing the simple an
d initial phase but finds it
difficult and complex when setting the broader feature when it gets completed. It is also a part of
SDLC and the concept could be interchanged with the incremental model technique at some point of
time (Arora & Arora, 2016). It
is actually seen to be describing the alterations which relate to the
incremental procedure that happens during the implementation and design of the latest iteration
process. The utilization of this model is seen to be done during the time of analysis and
doing some
planning in the system
.
Discussion posts:
Discussion post1:
Discussing three traditional software processing models
In an organization, the developers certainly have the role to play for creating a successful system,
and for that reason, they are seen to be utilizing some of the important processing models that deal
with the traditional software (Dasoriya, 2017). The development of these models always helps the
developers to do their work in a proper way as the contribution of these models directly connects to
provide support in building the system successfully. Further discussion would be done on the three
models that are usually utilized by the developers. There are not only three models that have been
utilized by the developers but from my point, they are the important ones along with their benefits
and some of their drawbacks.
Waterfall model
A sequential model through which development of the software could be divided into phases that are
pre-defined. The phases are seen to be designed for providing performance on some particular
activities with the phase of SDLC starts its work (Kaushik, Bharadwaj, Awasthi & Sharma, 2017). It is
seen that before starting the next phase, the other phases would be completed so that there is no
overlap between any of the phases. Different phases have a different function during the time of their
utilization by the developers. The waterfall model could be utilized when the requirements are clear
and the length of the project work is seen to be short.
Advantages
Each phase is certainly seen to be completed before starting the next one. The model is seen to be
best when the project is small with well-defined requirements. It has the ability to perform a quality
assurance test before proceeding to the next stage.
Disadvantages
One of the main drawbacks of this model is that only the errors could be reduced during the time of
doing work within the phase. The period of testing is seen to be coming late during the time of the
developing process. Developers waste their maximum time on doing the documentation.
Iterative model
This model is certainly found to be focusing on implementing the simple and initial phase but finds it
difficult and complex when setting the broader feature when it gets completed. It is also a part of
SDLC and the concept could be interchanged with the incremental model technique at some point of
time (Arora & Arora, 2016). It is actually seen to be describing the alterations which relate to the
incremental procedure that happens during the implementation and design of the latest iteration
process. The utilization of this model is seen to be done during the time of analysis and doing some
planning in the system.