Team presentations…

Thurs 6th April 17

In today’s class we had to do our team presentations. Our team had to present The Spiral Model. Unfortunately three of our team members weren’t able to contribute towards our work, so myself and Rosie took it for the team 🙂 (GIRLS DO IT BETTER!!!!!!)

Here’s a brief of what we went over…

The Spiral model defined- The spiral model is similar to the incremental model, with more emphasis placed on risk analysis. The spiral model has four phases: Planning, Risk Analysis, Engineering and Evaluation. A software project repeatedly passes through these phases in iterations (called Spirals in this model). The baseline spiral, starting in the planning phase, requirements are gathered and risk is assessed. Each subsequent spirals builds on the baseline spiral. Its one of the software development models like Waterfall, Agile, V-Model.

Planning Phase: Requirements are gathered during the planning phase. Requirements like ‘BRS’ that is ‘Business Requirement Specifications’ and ‘SRS’ that is ‘System Requirement specifications’.
Risk Analysis: In the risk analysis phase, a process is undertaken to identify risk and alternate solutions. A prototype is produced at the end of the risk analysis phase. If any risk is found during the risk analysis then alternate solutions are suggested and implemented.
Engineering Phase: In this phase software is developed, along with testing at the end of the phase. Hence in this phase the development and testing is done.
Evaluation phase: This phase allows the customer to evaluate the output of the project to date before the project continues to the next spiral.

🙂 We also spoke about the Advantages and disadvantages…

Advantages of Spiral model:

High amount of risk analysis hence, avoidance of Risk is enhanced.
Good for large and mission-critical projects.
Strong approval and documentation control.
Additional Functionality can be added at a later date.
Software is produced early in the software life cycle.

Disadvantages of Spiral model:

Can be a costly model to use.
Risk analysis requires highly specific expertise.
Project’s success is highly dependent on the risk analysis phase.
Doesn’t work well for smaller projects.

🙂 We also spoke about when The Spiral model should be used…

When to use Spiral model:

When costs and risk evaluation is important
For medium to high-risk projects
Long-term project commitment unwise because of potential changes to economic priorities
Users are unsure of their needs
Requirements are complex
New product line
Significant changes are expected (research and exploration)

This was all the research myself and Rosie did in order to make sure we understood the concepts of what makes the Spiral model, as well as be able to try explain it to the class.

We made the decision that The Spiral model wouldn’t be practical for us in the end, as this is generally used in larger projects, whereas ours is based on a much smaller scale. It’s a good model, just not the right one for us. 🙂

Among listening to the other group presentations, we are having thoughts into which model we want to choose….the decision is yet to be made!!

We had to take a few notes on each group presentation….Here’s a few pics I took on our group comments-