Software Engineering: V-shaped model
This past January the domain for Baud, the largest Chinese search site, Was taken over by a group calling itself the “Iranian Cyber Army. ” In that case, Baud filed suit against its U. S. Registrar, Register. Com, claiming it was slow to respond to the site’s plea for help. How to avoid this fate: “Eternal vigilance? ” asks Rasmussen. ‘You want to monitor the hell out of what you and other people are doing with your domains and theirs, so you can turn off the system and anything that connects to it if you or someone you trust has a problem. Some registrars are hardening their defenses against hijacking and making it tougher to change DNS records, but mostly it’s up to domain owners themselves to police their own records and respond quickly when they’ve been compromised. * Name and describe the different Software Process Models/Software Development Process Models The most common software development models applied for the development process are: 1. Waterfall model. This model is mainly apt for small and relatively easy software projects.
Software companies working according to this model complete each stage in consecutive order and review its results before proceeding to another stage, which renders the waterfall model inflexible and unsuitable for complex long-term software projects. [pick 2. Spiral model. The essence of this model is in the underscored importance Of a risk-analysis during the development process. The spiral model presupposes that each stage of the classical waterfall model is divided into several iterations, and each iteration undergoes planning and risk analysis.
As result this model allows a software company to produce working software after each iterative stage, while evaluating the risks on an ongoing basis. However, adopting the spiral model may result in notably higher costs. [pick] 3. V-shaped model. This model is similar to the waterfall model, though the main emphasis is placed on the verification stage and testing, which overlap all the other stages of the software development lifestyle. Tests are planed starting from the documentation stage, then throughout integration and coding and after the actual implementation of a software product testing itself is initiated.
Therefore, the V-shape is formed due to the upward direction of testing, I. E. Test execution. [pick 4. Iterative model. This model allows a software company to spot and mend problems at the earlier stages of the software development lifestyle, which makes the development process more flexible. This aim is achieved by breaking down the whole lifestyle into several iterations, thus handling the process in smaller portions. The iterative model allows creating the initial version of a software product straight after the first iteration. [pick] 5. Agile development model.