Question

QUESTION 1

     

1. One of the approach to SDLC is the adaptive approach. Within this approach, discuss the difference of the iterative, incremental, and walking skeleton development.

2. An organization can choose from a variety of alternatives to obtain a system. A weighted score method is usually applied to decide among the alternative systems.

   1. List the FIVE (5) steps to the weighted score method.

2. Should the results from the weighted score method be used as a final decision to select a new system? Justify your answer.

Answer 1

Iterative Model

The iterative process begins with a basic implementation of a small set of software specifications in the Iterative model and iteratively develops the developing iterations until the full framework is implemented and ready to be deployed.

An iterative model of the life cycle does not try to start with a complete specification of requirements. Instead, development starts with only part of the programme being defined and implemented, which is then reviewed to identify more specifications. This process is then repeated, creating at the end of each iteration of the model a new version of the programme.

Design for Iterative Model

The iterative approach begins with a basic implementation of a subset of software specifications and iteratively develops the developing versions until the complete framework is implemented. Design changes are made at every iteration and fresh functional capabilities are introduced. The basic concept behind this technique is to build a mechanism (iterative) through repeated cycles.

Incremental Model

The Incremental Model is a software development process where specifications are broken down into several standalone software development cycle modules. Incremental development takes place in phases from design, execution, testing / verification, maintenance of analysis.

The specifications, design , coding and testing phases pass through each iteration. And and subsequent device release adds functionality to the previous release until all of the features designed have been introduced.

When the first increment is delivered, the system is put into production. The first increment is always a core product where the basic specifications are addressed and in the next increments, new features are introduced. If the core product is evaluated by the client, the next step is to create a strategy.

Walking Skeleton

In a software development context, a walking skeleton is a minimal initial implementation of the design of an application that contains and connects the system's basic components. The framework is in place and functional in a rudimentary way, as the name suggests, but the system is not fleshed out and does not provide the end product with the quality of service necessary. Subsystems are incomplete, but mutually hooked.

In test-driven development (TDD), in which unit testing is repeatedly performed on the source code, walking skeletons are widely used. The code is refactored and reevaluated after each test until each unit works according to the desired specifications.

Weightage score method in selecting systems:

Definition: Prioritization of weighted scoring uses numerical scoring to score the strategic strategies against categories of profit and cost. For product teams looking for objective prioritisation strategies that factor in several data layers, it is useful.
Weighted scoring is a tool for prioritisation designed to help determine how to prioritise features on our product roadmap and other initiatives. In this system, initiatives are scored on a cost-to-benefit basis according to a set of standard criteria and then graded by their final scores. It can also be a dynamic and subjective process to determine which product features to focus on first, or which initiatives should receive the greatest share of development capital. If product managers use weighted scoring prioritisation, they may apply objectivity to their roadmap decisions.

This is a technique for comparing software system alternate selection from among all possible variations.

It’s not the only approach and we should be aware that the outcome of the comparison is highly dependent on the understanding of the software features (criteria), the amount of information we have on each software, as well as the subjective perception of the importance of each feature to different stakeholder groups.

A weighted scoring model can also be called as project management technique used for weighing certain decisions, such as prioritizing project actions, prioritizing the development of product features, purchasing new software, etc.

While a weighted scoring model can be used for all kinds of decisions and actions, in terms of project management, this model will help us figure out our priorities during the planning phase of the project life cycle.

The Six Sigma prioritization matrix is one of the most well-known weighted scoring models in project management.

Steps of weightage score model are:

1.) List out the options

2.) Brainstormingon ideas

3.) Give weights to the options based on criteria

4.) Create weight scoring chart

5.) Select from the chart, the corresponding system with highest weight value.

The weigth score method for choosing alternate systems use several ordered scales which are weighted according to perceived notion of importance. A particular attibute which one find important may not be actually important for the ystem. In risk analysis, many widely used scoring approaches are based on flaky theoretical foundations. They are also used without any validation to exacerbate the problem. Wellknown and beloved risk matrix is a particularly ubiquitous example. It is already shown how risk matrices can often lead to decisions that are worse than those taken on the basis of a coin toss in his paper on risk matrices. Without an awareness of their limits, the fact that this is a possibility, even if only a small one, should concern everyone using risk matrices (or other inaccurate scoring techniques).

So, until and unless we have requirements well understood and scope of software very well defined, we must should not use weighted score method.