A spiral model was developed by Barry Bohem in year 1986.
As a part of SEI
Software Engineering Institute It is called meta model Because it contains all life
cycle model . Spiral model is a risk driven software development process it is
combination of waterfall model and iterative [Link] phase of spiral model in
software engineering began with a design goal and end with client reviewing process.
Planning - Identify object of phase it includes estimating cost schedule and resource
for [Link] the system requirement for continuous communication
between system analyst and culture .
Risk analysis - Identification of potential risk mitigation strategy is planned and
finalised for each identified project risk . A detail analysis is carried out steps are
taken to reduce the risk
Engineering - It incloud testing coding and deploy Software at the customer [Link]
include identifying and monitoring risk .
Evolution - Review a result at you so for with customer and plan the next iteration
around the Spiral and repeat the cycle In the end software company readies in
market
Advantages
In Additional functionality Or changes can be done At a later stage
Cost estimation become easy so the prototype Building Is done In Fragments
Continuous or repeat development help in risk management
This is always a space for customer feedback
Disadvantage
Spiral software development is not advisable for smaller But it might cost them a lot
to visit
Managing and tracking multiple iteration could be challenging in development
process
To explain V shape model
V shape model is also called a V model .It is structural software development model
That is considered an extension of waterfall model It emphasises verification and
validation by linking each development phase with corresponding testing phase
forming V shaped [Link] model is used when requirement are clear and
quality testing is very important
In V shape model project is planned into streame
Verification phase - Development page
Validation phase - Testing phase
Requirement analysis- User requirement are collected and documented clearly
Acceptance cases are planned here This is like a most important planning step for
whole project
System design - High level system design is created System level tage cases are
planned The main model subsystem and their interaction are decided
Architecture design - System is divided into sub system or model It integration test
cases are designed to check how model work together Communication between
modules is defined
Modern design - Loliwal component level design is done Unit test cases are written
for every small function or class Each model is broken into small component and
function
Coding-Actual code is written based on design Kugra must write actual code based
on detailed design document After coding unit testing is run on each model
Validation phase
Unit testing - Individual components or function are tested Done at the lowest level
of [Link] goal is find bugs at smallest cable
Integration test - The tested model are combined and tested together If any
integration problem is found it is fixed and re tested Mainfocus check if models talk
to each other correctly
System testing - The entire system is tested as a single unit Both functional testing
(feature , work correctly) And non functional testing (performnsncr,load,security) are
done
Accepting test -The system is tested with real user data and real user. It ensure The
software satisfy actual user requirement .End user accept it and software is
delivered and move to maintain the phase
Explain what is data modelling and explain the elements of data modelling
Data modelling is a process of Designing a clear and organised structure for data in
system
It show the word data store and how it is organised and how data elements are
related to each other
Data models are used to design database and ensure data consistency accuracy and
easy access
It translate business requirement into data structure
The main elements of data modelling
Entities - Entity represent a real word object or concept like customer ,product or
order
Attribut - Attributes are properties or details of entity example customer entity
Keys - A primary key uniquely identifies each record in entity
Relationship - Show how entities are connected such as one to one
Multiplicity - Describe how many instance of one entity can relate to another
Constant and rules - Business rules applied on data and help maintain data entry and
quality