This document discusses different software development life cycle (SDLC) models including iterative and spiral models. The iterative model involves building a product incrementally in iterations, with requirements evolving in each iteration based on user feedback. The spiral model similarly progresses in iterations but places more emphasis on risk analysis. Each spiral involves planning, risk analysis, engineering, and evaluation phases. The document also covers advantages and disadvantages of each model, as well as the role of management in software projects, including planning, monitoring and control, and termination analysis.
Software Lifecycle Models / Software Development Models
Types of Software development models
Waterfall Model
Features of Waterfall Model
Phase of Waterfall Model
Prototype Model
Advantages of Prototype Model
Disadvantages of Prototype model
V Model
Advantages of V-model
Disadvantages of V-model
When to use the V-model
Incremental Model
ITERATIVE AND INCREMENTAL DEVELOPMENT
INCREMENTAL MODEL LIFE CYCLE
When to use the Incremental model
Rapid Application Development RAD Model
phases in the rapid application development (RAD) model
Advantages of the RAD model
Disadvantages of RAD model
When to use RAD model
Agile Model
Advantages of Agile model
Disadvantages of Agile model
When to use Agile model
Software Design
Design principles
Problem partitioning
Abstraction
Top down and bottom up-design
Structured approach
Functional versus object oriented approach
Design specifications and verification
Monitoring and control
Cohesiveness
Coupling
Fourth generation techniques
Functional independence
Software Architecture
Transaction and Transform Mapping
Software Lifecycle Models / Software Development Models
Types of Software development models
Waterfall Model
Features of Waterfall Model
Phase of Waterfall Model
Prototype Model
Advantages of Prototype Model
Disadvantages of Prototype model
V Model
Advantages of V-model
Disadvantages of V-model
When to use the V-model
Incremental Model
ITERATIVE AND INCREMENTAL DEVELOPMENT
INCREMENTAL MODEL LIFE CYCLE
When to use the Incremental model
Rapid Application Development RAD Model
phases in the rapid application development (RAD) model
Advantages of the RAD model
Disadvantages of RAD model
When to use RAD model
Agile Model
Advantages of Agile model
Disadvantages of Agile model
When to use Agile model
Software Design
Design principles
Problem partitioning
Abstraction
Top down and bottom up-design
Structured approach
Functional versus object oriented approach
Design specifications and verification
Monitoring and control
Cohesiveness
Coupling
Fourth generation techniques
Functional independence
Software Architecture
Transaction and Transform Mapping
Software Process Models, The Linear Sequential Model, The Prototyping Model, The RAD Model, Evolutionary Process Models, Agile Process Model, Component-Based Development, Process, Product and Process.
Life-Cycle Phases
Engineering and Production Stages
Inception Phase
Elaboration Phase
Construction Phase
Transition Phase
Artifacts of the Process
The Artifact Sets
Management Artifacts
Engineering Artifacts
Pragmatic Artifacts
Model-based software Architectures
Architecture: A Management Perspective
Architecture: A Technical Perspective
Workflows of the Process
Software Process Workflows
Iteration Workflows
Checkpoints of the Process
Major Milestones
Minor Milestones
Periodic Status Assessments
CP7301 Software Process and Project Management notesAAKASH S
UNIT I DEVELOPMENT LIFE CYCLE PROCESSES 9
Overview of software development life cycle – introduction to processes – Personal Software
Process (PSP) – Team software process (TSP) – Unified processes – agile processes –
choosing the right process Tutorial: Software development using PSP
20
UNIT II REQUIREMENTS MANAGEMENT 9
Functional requirements and quality attributes – elicitation techniques – Quality Attribute
Workshops (QAW) – analysis, prioritization, and trade-off – Architecture Centric
Development Method (ACDM) – requirements documentation and specification – change
management – traceability of requirements
Tutorial: Conduct QAW, elicit, analyze, prioritize, and document requirements using ACDM
UNIT III ESTIMATION, PLANNING, AND TRACKING 9
Identifying and prioritizing risks – risk mitigation plans – estimation techniques – use case
points – function points – COCOMO II – top-down estimation – bottom-up estimation – work
breakdown structure – macro and micro plans – planning poker – wideband delphi –
documenting the plan – tracking the plan – earned value method (EVM)
Tutorial: Estimation, planning, and tracking exercises
UNIT IV CONFIGURATION AND QUALITY MANAGEMENT 9
identifying artifacts to be configured – naming conventions and version control –
configuration control – quality assurance techniques – peer reviews – Fegan inspection –
unit, integration, system, and acceptance testing – test data and test cases – bug tracking –
causal analysis
Tutorial: version control exercises, development of test cases, causal analysis of defects
UNIT V SOFTWARE PROCESS DEFINITION AND MANAGEMENT 9
Process elements – process architecture – relationship between elements – process
modeling – process definition techniques – ETVX (entry-task-validation-exit) – process
baselining – process assessment and improvement – CMMI – Six Sigma
Tutorial: process measurement exercises, process definition using ETVX
Process Improvement: Process and product quality, Process Classification, Process Measurement, Process Analysis and Modeling, Process Change, The CMMI Process Improvement Framework.
Service Oriented Software Engineering: Services as reusable components, Service Engineering, Software Development with Services.
SOFTWARE RELIABILITY AND QUALITY ASSURANCE
Reliability issues
Reliability metrics
Reliability growth modeling
Software quality
ISO 9000 certification for software industry
SEI capability maturity model
comparison between ISO and SEI CMM
Introduction: What is software engineering? Software Development Life Cycle, Requirements Analysis, Software Design, Coding, Testing, Maintenance etc.
Software Requirements: Functional and Non-functional requirements, User Requirements, System Requirements, Documentation of the software requirements.
Software Processes:
Process and Project, Component Software Processes.
Software Development Process Models.
Waterfall Model. Prototyping.
Iterative Development.
The RAD Model
Esoft Metro Campus - Diploma in Software Engineering - (Module I) Introduction to Software Engineering
(Template - Virtusa Corporate)
Contents:
What is software?
Software classification
Generic Software vs Custom Software
Attributes of Software
What is Software Engineering?
Software Engineering Process Model
Waterfall Model
Waterfall Model Stages
Extended Waterfall Model
Prototype Model
Throw away prototype model
Evolutionary prototype model
Rapid application development model (RAD)
Stages in the RAD
Software Process Models, The Linear Sequential Model, The Prototyping Model, The RAD Model, Evolutionary Process Models, Agile Process Model, Component-Based Development, Process, Product and Process.
Life-Cycle Phases
Engineering and Production Stages
Inception Phase
Elaboration Phase
Construction Phase
Transition Phase
Artifacts of the Process
The Artifact Sets
Management Artifacts
Engineering Artifacts
Pragmatic Artifacts
Model-based software Architectures
Architecture: A Management Perspective
Architecture: A Technical Perspective
Workflows of the Process
Software Process Workflows
Iteration Workflows
Checkpoints of the Process
Major Milestones
Minor Milestones
Periodic Status Assessments
CP7301 Software Process and Project Management notesAAKASH S
UNIT I DEVELOPMENT LIFE CYCLE PROCESSES 9
Overview of software development life cycle – introduction to processes – Personal Software
Process (PSP) – Team software process (TSP) – Unified processes – agile processes –
choosing the right process Tutorial: Software development using PSP
20
UNIT II REQUIREMENTS MANAGEMENT 9
Functional requirements and quality attributes – elicitation techniques – Quality Attribute
Workshops (QAW) – analysis, prioritization, and trade-off – Architecture Centric
Development Method (ACDM) – requirements documentation and specification – change
management – traceability of requirements
Tutorial: Conduct QAW, elicit, analyze, prioritize, and document requirements using ACDM
UNIT III ESTIMATION, PLANNING, AND TRACKING 9
Identifying and prioritizing risks – risk mitigation plans – estimation techniques – use case
points – function points – COCOMO II – top-down estimation – bottom-up estimation – work
breakdown structure – macro and micro plans – planning poker – wideband delphi –
documenting the plan – tracking the plan – earned value method (EVM)
Tutorial: Estimation, planning, and tracking exercises
UNIT IV CONFIGURATION AND QUALITY MANAGEMENT 9
identifying artifacts to be configured – naming conventions and version control –
configuration control – quality assurance techniques – peer reviews – Fegan inspection –
unit, integration, system, and acceptance testing – test data and test cases – bug tracking –
causal analysis
Tutorial: version control exercises, development of test cases, causal analysis of defects
UNIT V SOFTWARE PROCESS DEFINITION AND MANAGEMENT 9
Process elements – process architecture – relationship between elements – process
modeling – process definition techniques – ETVX (entry-task-validation-exit) – process
baselining – process assessment and improvement – CMMI – Six Sigma
Tutorial: process measurement exercises, process definition using ETVX
Process Improvement: Process and product quality, Process Classification, Process Measurement, Process Analysis and Modeling, Process Change, The CMMI Process Improvement Framework.
Service Oriented Software Engineering: Services as reusable components, Service Engineering, Software Development with Services.
SOFTWARE RELIABILITY AND QUALITY ASSURANCE
Reliability issues
Reliability metrics
Reliability growth modeling
Software quality
ISO 9000 certification for software industry
SEI capability maturity model
comparison between ISO and SEI CMM
Introduction: What is software engineering? Software Development Life Cycle, Requirements Analysis, Software Design, Coding, Testing, Maintenance etc.
Software Requirements: Functional and Non-functional requirements, User Requirements, System Requirements, Documentation of the software requirements.
Software Processes:
Process and Project, Component Software Processes.
Software Development Process Models.
Waterfall Model. Prototyping.
Iterative Development.
The RAD Model
Esoft Metro Campus - Diploma in Software Engineering - (Module I) Introduction to Software Engineering
(Template - Virtusa Corporate)
Contents:
What is software?
Software classification
Generic Software vs Custom Software
Attributes of Software
What is Software Engineering?
Software Engineering Process Model
Waterfall Model
Waterfall Model Stages
Extended Waterfall Model
Prototype Model
Throw away prototype model
Evolutionary prototype model
Rapid application development model (RAD)
Stages in the RAD
A software process model is an abstraction of the software development process. The models specify the stages and order of a process. So, think of this as a representation of the order of activities of the process and the sequence in which they are performed
Introduction to Software Engineering and Software Process Modelssantoshkawade5
S/W Engineering
Software Engineering Fundamentals: Introduction to software engineering, The Nature of Software, Defining Software, Software Engineering Practice.
A Generic Process Model, defining a Framework Activity, Identifying a Task Set, Process Patterns, Process Assessment and Improvement, Prescriptive Process Models, The Waterfall Model, Incremental Process Models, Evolutionary Process Models, Concurrent Models, A Final Word on Evolutionary Processes. Unified Process, Agile software development: Agile methods, plan driven and agile development.
1. What are the differences between a DBMS and RDBMS?
2. Explain the terms database and DBMS. Also, mention the different types of DBMS.
3. What are the advantages of DBMS?
4. Mention the different languages present in DBMS
5. What do you understand by query optimization?
6. Do we consider NULL values the same as that of blank space or zero?
7. What do you understand by aggregation and atomicity?
8. What are the different levels of abstraction in the DBMS?
9. What is an entity-relationship model?
10. What do you understand by the terms Entity, Entity Type, and Entity Set in DBMS?
11. What are relationships and mention different types of relationships in the DBMS
12. What is concurrency control?
13. What are the ACID properties in DBMS?
14. What is normalization and what are the different types of normalization?
15. What are the different types of keys in the database?
16. What do you understand by correlated subqueries in DBMS?
17. Explain Database partitioning and its importance.
18. What do you understand by functional dependency and transitive dependency in DBMS?
19. What is the difference between two and three-tier architectures?
20. Mention the differences between Unique Key and Primary Key
21. What is a checkpoint in DBMS and when does it occur?
22. Mention the differences between Trigger and Stored Procedures
23. What are the differences between Hash join, Merge join and Nested loops?
24. What do you understand by Proactive, Retroactive and Simultaneous Update?
25. What are indexes? Mention the differences between the clustered and non-clustered index
26. What do you understand by intension and extension?
27. What do you understand by cursor? Mention the different types of cursor A cursor is a database object which helps in manipulating data, row by row and represents a result set.
28. Explain the terms specialization and generalization
29. What do you understand by Data Independence?
30. What are the different integrity rules present in the DBMS?
31. What does Fill Factor concept mean with respect to indexes?
32. What is Index hunting and how does it help in improving query performance?
33. What are the differences between network and hierarchical database model?
34. Explain what is a deadlock and mention how it can be resolved?
35. What are the differences between an exclusive lock and a shared lock?
=>Concept of Governance
=>Risk and Control (GRC) as applicable to IT operational risk
=>Importance of documentation
=>DATA FLOW DIAGRAM for every application
=>Review of changes in the Data flow, reporting, etc.
=>Parameters for review
=>Importance of review on SLA compliance
=>Reporting to IT Strategy committee, Board etc.
Importance of Data - Where to find it, how to store, manipulate, and characterize it
Artificial Intelligence (AI)- Introduction to AI & ML Technologies/ Applications
Machine Learning (ML), Basic Machine Learning algorithms.
Applications of AI & ML in Marketing, Sales, Finance, Operations, Supply Chain
& Human Resources Data Governance
Legal and Ethical Issues
Robotic Process Automation (RPA)
Internet of Things (IoT)
Cloud Computing
What is Data ?
What is Information?
Data Models, Schema and Instances
Components of Database System
What is DBMS ?
Database Languages
Applications of DBMS
Introduction to Databases
Fundamentals of Data Modeling and Database Design
Database Normalization
Types of keys in database management system
Distributed Database
CASE (COMPUTER AIDED SOFTWARE ENGINEERING)
CASE and its Scope
CASE support in software life cycle documentation
project management
Internal Interface
Reverse Software Engineering
Architecture of CASE environment.
Software Testing
Different Types of Software Testing
Verification
Validation
Unit Testing
Beta Testing
Alpha Testing
Black Box Testing
White Box testing
Error
Bug
Introduction to software engineering
Software products
Why Software is Important?
Software costs
Features of Software?
Software Applications
Software—New Categories
Software Engineering
Importance of Software Engineering
Essential attributes / Characteristics of good software
Software Components
Software Process
Five Activities of a Generic Process framework
Relative Costs of Fixing Software Faults
Software Qualities
Software crisis
Software Development Stages/SDLC
What is Software Verification
Advantages of Software Verification
Advantages of Validation
Cloud Computing
Categories of Cloud Computing
SaaS
PaaS
IaaS
Threads of Cloud Computing
Insurance Challenges
Cloud Solutions
Security of the Insurance Industry
Cloud Solutions
Insurance Security in the Insurance Industry with respect to Indian market
Application Software
Applications Software
Software Types
Task-Oriented Productivity Software
Business Software
Application Software and Ethics
Computers and People
Software:
Systems and Application Software
Identify and briefly describe the functions of the two basic kinds of software
Outline the role of the operating system and identify the features of several popular operating systems
Discuss how application software can support personal, workgroup, and enterprise business objectives
Identify three basic approaches to developing application software and discuss the pros and cons of each
Outline the overall evolution and importance of programming languages and clearly differentiate among the generations of programming languages
Identify several key software issues and trends that have an impact on organizations and individuals
Programming Languages
A formal language for describing computation?
A “user interface” to a computer?
Syntax + semantics?
Compiler, or interpreter, or translator?
A tool to support a programming paradigm?
Number Codes and Registers
2’s complement numbers
Addition and subtraction
Binary coded decimal
Gray codes for binary numbers
ASCII characters
Moving towards hardware
Storing data
Processing data
PROGRAMMING AND LANGUAGES
Describe the six steps of programming
Discuss design tools
Describe program testing
Describe CASE tools & object-oriented software development
Explain the five generations of programming languages
Data Formats used by Computers
ISO – International Standards Organization
CSA – Canadian Standards Association
ANSI – American National Standards Institute
IEEE – Institute for Electrical and Electronics Engineers
Language,
Low-level languages,
High-level languages,
CHARACTERSTICS OF LOW LEVEL LANGUAGES
Third generation languages (3GL)
Types: - C++
VISUAL BASIC
JAVA
JAVASCRIPT
More from Amity University | FMS - DU | IMT | Stratford University | KKMI International Institute | AIMA | DTU (20)
Macroeconomics- Movie Location
This will be used as part of your Personal Professional Portfolio once graded.
Objective:
Prepare a presentation or a paper using research, basic comparative analysis, data organization and application of economic information. You will make an informed assessment of an economic climate outside of the United States to accomplish an entertainment industry objective.
Biological screening of herbal drugs: Introduction and Need for
Phyto-Pharmacological Screening, New Strategies for evaluating
Natural Products, In vitro evaluation techniques for Antioxidants, Antimicrobial and Anticancer drugs. In vivo evaluation techniques
for Anti-inflammatory, Antiulcer, Anticancer, Wound healing, Antidiabetic, Hepatoprotective, Cardio protective, Diuretics and
Antifertility, Toxicity studies as per OECD guidelines
Honest Reviews of Tim Han LMA Course Program.pptxtimhan337
Personal development courses are widely available today, with each one promising life-changing outcomes. Tim Han’s Life Mastery Achievers (LMA) Course has drawn a lot of interest. In addition to offering my frank assessment of Success Insider’s LMA Course, this piece examines the course’s effects via a variety of Tim Han LMA course reviews and Success Insider comments.
Synthetic Fiber Construction in lab .pptxPavel ( NSTU)
Synthetic fiber production is a fascinating and complex field that blends chemistry, engineering, and environmental science. By understanding these aspects, students can gain a comprehensive view of synthetic fiber production, its impact on society and the environment, and the potential for future innovations. Synthetic fibers play a crucial role in modern society, impacting various aspects of daily life, industry, and the environment. ynthetic fibers are integral to modern life, offering a range of benefits from cost-effectiveness and versatility to innovative applications and performance characteristics. While they pose environmental challenges, ongoing research and development aim to create more sustainable and eco-friendly alternatives. Understanding the importance of synthetic fibers helps in appreciating their role in the economy, industry, and daily life, while also emphasizing the need for sustainable practices and innovation.
Acetabularia Information For Class 9 .docxvaibhavrinwa19
Acetabularia acetabulum is a single-celled green alga that in its vegetative state is morphologically differentiated into a basal rhizoid and an axially elongated stalk, which bears whorls of branching hairs. The single diploid nucleus resides in the rhizoid.
Read| The latest issue of The Challenger is here! We are thrilled to announce that our school paper has qualified for the NATIONAL SCHOOLS PRESS CONFERENCE (NSPC) 2024. Thank you for your unwavering support and trust. Dive into the stories that made us stand out!
How to Make a Field invisible in Odoo 17Celine George
It is possible to hide or invisible some fields in odoo. Commonly using “invisible” attribute in the field definition to invisible the fields. This slide will show how to make a field invisible in odoo 17.
June 3, 2024 Anti-Semitism Letter Sent to MIT President Kornbluth and MIT Cor...Levi Shapiro
Letter from the Congress of the United States regarding Anti-Semitism sent June 3rd to MIT President Sally Kornbluth, MIT Corp Chair, Mark Gorenberg
Dear Dr. Kornbluth and Mr. Gorenberg,
The US House of Representatives is deeply concerned by ongoing and pervasive acts of antisemitic
harassment and intimidation at the Massachusetts Institute of Technology (MIT). Failing to act decisively to ensure a safe learning environment for all students would be a grave dereliction of your responsibilities as President of MIT and Chair of the MIT Corporation.
This Congress will not stand idly by and allow an environment hostile to Jewish students to persist. The House believes that your institution is in violation of Title VI of the Civil Rights Act, and the inability or
unwillingness to rectify this violation through action requires accountability.
Postsecondary education is a unique opportunity for students to learn and have their ideas and beliefs challenged. However, universities receiving hundreds of millions of federal funds annually have denied
students that opportunity and have been hijacked to become venues for the promotion of terrorism, antisemitic harassment and intimidation, unlawful encampments, and in some cases, assaults and riots.
The House of Representatives will not countenance the use of federal funds to indoctrinate students into hateful, antisemitic, anti-American supporters of terrorism. Investigations into campus antisemitism by the Committee on Education and the Workforce and the Committee on Ways and Means have been expanded into a Congress-wide probe across all relevant jurisdictions to address this national crisis. The undersigned Committees will conduct oversight into the use of federal funds at MIT and its learning environment under authorities granted to each Committee.
• The Committee on Education and the Workforce has been investigating your institution since December 7, 2023. The Committee has broad jurisdiction over postsecondary education, including its compliance with Title VI of the Civil Rights Act, campus safety concerns over disruptions to the learning environment, and the awarding of federal student aid under the Higher Education Act.
• The Committee on Oversight and Accountability is investigating the sources of funding and other support flowing to groups espousing pro-Hamas propaganda and engaged in antisemitic harassment and intimidation of students. The Committee on Oversight and Accountability is the principal oversight committee of the US House of Representatives and has broad authority to investigate “any matter” at “any time” under House Rule X.
• The Committee on Ways and Means has been investigating several universities since November 15, 2023, when the Committee held a hearing entitled From Ivory Towers to Dark Corners: Investigating the Nexus Between Antisemitism, Tax-Exempt Universities, and Terror Financing. The Committee followed the hearing with letters to those institutions on January 10, 202
2. Contents
1. Iterative model
2. Advantages of Iterative model
3. Disadvantages of Iterative model
4. When to use iterative model
5. Spiral Model
6. Advantages of Spiral model
7. Disadvantages of Spiral model
8. When to use Spiral model
9. Role of Management in Software Development
4. • An iterative life cycle model does not attempt
to start with a full specification of
requirements.
• Instead, development begins by specifying
and implementing just part of the software,
which can then be reviewed in order to
identify further requirements.
• This process is then repeated, producing a
new version of the software for each cycle of
the model.
5.
6. For Example:
• In the diagram above when we work iteratively we
create rough product or product piece in one
iteration, then review it and improve it in next
iteration and so on until it’s finished. As shown in
the image above, in the first iteration the whole
painting is sketched roughly, then in the second
iteration colors are filled and in the third iteration
finishing is done. Hence, in iterative model the
whole product is developed step by step.
7. Advantages of Iterative model
• In iterative model we can only create a high-level design of the
application before we actually begin to build the product and define
the design solution for the entire product. Later on we can design
and built a skeleton version of that, and then evolved the design
based on what had been built.
• In iterative model we are building and improving the product step
by step. Hence we can track the defects at early stages. This avoids
the downward flow of the defects.
• In iterative model we can get the reliable user feedback. When
presenting sketches and blueprints of the product to users for their
feedback, we are effectively asking them to imagine how the
product will work.
• In iterative model less time is spent on documenting and more time
is given for designing.
8. Disadvantages of Iterative model
• Each phase of an iteration is rigid with no
overlaps
• Costly system architecture or design issues
may arise because not all requirements are
gathered up front for the entire lifecycle
9. When to use iterative model:
• Requirements of the complete system are
clearly defined and understood.
• When the project is big.
• Major requirements must be defined;
however, some details can evolve with time.
11. • 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
12. • 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.
13.
14. Spiral development
• Process is represented as a spiral rather than
as a sequence of activities with backtracking.
• Each loop in the spiral represents a phase in
the process.
• No fixed phases such as specification or design
- loops in the spiral are chosen depending on
what is required.
• Risks are explicitly assessed and resolved
throughout the process.
16. Spiral model sectors
• Objective setting
– Specific objectives for the phase are identified.
• Risk assessment and reduction
– Risks are assessed and activities put in place to
reduce the key risks.
• Development and validation
– A development model for the system is chosen
which can be any of the generic models.
• Planning
– The project is reviewed and the next phase of the
spiral is planned.
17. 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.
18. 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.
19. 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)
20. Role of Management in Software
Development
• Proper management is an integral part of
software development.
• A large software development project involves
many people working for a long period of
time. We have seen that a development
process typically partitions the problem of
developing software into a set of phases.
21. • To meet the cost, quality, and schedule
objectives, resources have to be properly
allocated to each activity for the project, and
progress of different activities has to be
monitored and corrective actions taken, if
needed.
• For a large project, a proper management
process is essential for success. The activities in
the management process for a project can be
grouped broadly into three phases:-
• I Planning
• II Monitoring and control
• III Termination analysis
22. Planning
• Project management begins with planning, which
is perhaps the single largest responsibility of the
project management.
• The goal of this phase is to develop a plan for
software development following which the
objectives of the project can be met successfully
and efficiently.
• Project monitoring and control phase of the
management process is the longest in terms of
duration. It encompasses most of the
development process.
23. Monitoring and control
• It includes all activities the project
management has to perform while the
development is going on to ensure that
project objectives are met and the
development proceeds according to the
developed plan. As cost, schedule, and quality
are the major driving forces, most of the
activity of this phase revolves around
monitoring factors that affect them.
24. Termination analysis
• Termination analysis is performed when the
development process is over. The basic reason for
performing termination analysis is to provide
information about the development process.
Remember that a project is an instantiation of the
process. To understand the properties of the
process, data from many projects that used the
process can be used to make predictions and
estimations about future projects. The data about
the project is also needed to analyze the process.
25. Role of Matrices and Measurement
• During all the software development life cycle
it is very important to apply metrics and
measurement because metrics and
measurement set expectations.
• If there are well established metrics and
measurements in project then the test analyst
can easily track and report quality results to
the management.
26. You can consider some the following
areas where you can apply metrics and
measurement.
• Schedule of project
• Coverage
• Planned & actual cost
• Workload & resource usage
• Product risk & project risk
• Defects
27. Three Main Areas to check about
Metrics and Measurement.
• 1.) Defining Test Metrics:
Small and quality set of metrics should be chosen, large
set of metrics should be avoided as it is very confusing to
understand large set of metrics. Metrics should also be
uniform and everybody in team should agree with it.
• 2.) Tracking test metrics
After defining the metrics the next step is to track the
metrics. Since tracking is a constant activity so its always
nice to automate the tracking part. Automation reduces
time required to track the metrics, analyze them and
measure them.
• 3.) Reporting
Reporting of the metrics is the most important step, you
should report test metrics to stakeholders so that they
have clear picture of project progress.
28. Problem Analysis
• Problem analysis is the process of understanding
real-world problems and user needs and
proposing solutions to meet those needs.
• A problem can be defined as the difference
between things as perceived and things as desired.
– “what is” vs. “what should be”
– “what is given” vs. “what is needed”
• The goal of problem analysis is to gain a better
understanding of the problem being solved before
development begins.
29. The Five Steps in Problem Analysis
1. Gain agreement on the problem definition.
2. Understand the root causes—the problem
behind the problem.
3. Identify the stakeholders and the users.
4. Define the solution system boundary.
5. Identify the constraints to be imposed on the
solution.
31. ThankYou&
KeepLearning!
?Follow us :
You can find me at
https://www.linkedin.com/in/drkamalgulati/
https://mybigdataanalytics.in/
https://www.facebook.com/DrKamalGulatiBig
DATA/