System Development Life Cycle (SDLC) is a systematic frameworks that helps to deliver products on time with high quality. This presentation gives some real time case studies and establishes case for having a standard framework. It also covers major phases involved in product development.
Software design is a process through which requirements are translated into a ― blueprint for constructing the software.
Initially, the blueprint shows how the software will look and what kind of data or components will be required to in making it.
The software is divided into separately named components, often called ‘MODULES’, that are used to detect problems at ease.
This follows the "DIVIDE AND CONQUER" conclusion. It's easier to solve a complex problem when you break it into manageable pieces.
This Presentation will describe you,
01. What is software project management
02. The Role of Software Project Manager
03. Risk Management
04. People Management
not only these point you will have with example.
Layer between OS and distributed applications,Hides complexity and heterogeneity of distributed system ,Bridges gap between low-level OS communications and programming language abstractions,Provides common programming abstraction and infrastructure for distributed applications.
Requirements analysis, also called requirements engineering, is the process of determining user expectations for a new or modified product. These features, called requirements, must be quantifiable, relevant and detailed. In software engineering, such requirements are often called functional specifications. Requirements analysis is an important aspect of project management.
Real Time Systems,Issues of real time system,Notations, state oriented Petrinets,Milestones, Walkthroughs, Inspections, Test plans,Functional test,Performance test,Stress test,Structural test
System Testing. SYSTEM TESTING is a level of software testing where a complete and integrated software is tested. The purpose of this test is to evaluate the system's compliance with the specified requirements. system testing: The process of testing an integrated system to verify that it meets specified requirements.
Software design is a process through which requirements are translated into a ― blueprint for constructing the software.
Initially, the blueprint shows how the software will look and what kind of data or components will be required to in making it.
The software is divided into separately named components, often called ‘MODULES’, that are used to detect problems at ease.
This follows the "DIVIDE AND CONQUER" conclusion. It's easier to solve a complex problem when you break it into manageable pieces.
This Presentation will describe you,
01. What is software project management
02. The Role of Software Project Manager
03. Risk Management
04. People Management
not only these point you will have with example.
Layer between OS and distributed applications,Hides complexity and heterogeneity of distributed system ,Bridges gap between low-level OS communications and programming language abstractions,Provides common programming abstraction and infrastructure for distributed applications.
Requirements analysis, also called requirements engineering, is the process of determining user expectations for a new or modified product. These features, called requirements, must be quantifiable, relevant and detailed. In software engineering, such requirements are often called functional specifications. Requirements analysis is an important aspect of project management.
Real Time Systems,Issues of real time system,Notations, state oriented Petrinets,Milestones, Walkthroughs, Inspections, Test plans,Functional test,Performance test,Stress test,Structural test
System Testing. SYSTEM TESTING is a level of software testing where a complete and integrated software is tested. The purpose of this test is to evaluate the system's compliance with the specified requirements. system testing: The process of testing an integrated system to verify that it meets specified requirements.
The second part of SDLC talks about various types of life cycles - Waterfall, Prototype, Spiral, V Model and Incremental. Special focus provided for Agile. Good number of case studies are provided to understand which life cycle to choose during what type of project. The slide deck concludes with detailed description of Requirement Engineering and Sytem modelling.
QCon Shanghai: Trends in Application DevelopmentChris Bailey
Presented at QCon Shanghai:
Trends in Application Development
The last few years have seen a number of growing trends in application development, driven by the disruptive changes around cloud, mobile and engaging applications. These have led to a wider set of languages being used for production applications, the emergence of asynchronous and reactive programming, and interest in micro-services based architectures. This keynote will review some of the growing trends in application development, and highlight which skills you should be developing and which architectures you should be using.
Deliver a great web design project without getting into deadly feedback loops. Standardize your design process into a few easy phases to make sure you meet your client's expectations and then some!
Presentation made at 21212 workshop, covering agile concepts like lean, kanban, mpv applied to product development and project management in an startup environment.
David Peres and Rob Patterson of Minalytix discuss what the typical product development process looks like, what development model options are there, and their experiences as entrepreneurs.
Applying Quality to the Project and Product Management ProcessKaali Dass PMP, PhD.
Quality Management is one of the nine knowledge areas of PMBOK, and also an important factor in IT project success. This discussion will be centered on practices in both project and product management that fully enable a technology team to deliver high quality software. In today’s fast paced technology field, often times quality is seen as a luxury item that can or will be built in as an afterthought. The discussion in this presentation is to show how an escalated attention to quality actually provides faster, more reliable and predictable results.
Develop a Defect Prevention Strategy—or Else!TechWell
Defects occurring throughout the development of a software project penalize the project. The effort spent remediating these defects robs the project team of valuable time, resources, and money that could otherwise be used for further innovation and delivering the highest possible quality product to wow the customer. The occurrence of a large percentage of these defects can be avoided with preventive defect removal strategies. Scott Aziz describes various methods for removing defects during the early design and development phases―long before testing. Methods include requirements-based testing that eliminates 95 percent of requirements defects prior to the coding phase, code reviews and inspections, and establishing model-based test design practices that allow for testing business requirements before any code is developed. Take back and adopt in your environment some of the most effective early defect prevention practices known and practiced in the industry today.
Applying TQM and the Toyota Production System in Development of Software Arti...Dave Litwiller
Adapting TPS Tools and Techniques for Enterprise TQM to Software, Artificial Intelligence, Machine Learning and Deep Learning Development Organizations
Building & launching mobile & digital productsAnurag Jain
These slides are an introduction to Product Management for building & launching mobile & digital products for consumers. It covers the basics of Product Management as well as gives an overview of the Product Management process and a practical, iterative approach to building products.
In every successful technology businesses Jeff has worked in, the key challenge has been understanding how to scale technology and when to tackle the technical debt that inevitably accrues as a company runs ever faster and faster in pursuit of its business objectives. Jeff draws on his experience to help you understand what challenges emerge as a company moves from a Developer Centric environment to become more business focused. How can you get the business people to have influence on a developer centric environment? How can you manage the challenges that marketing will present?! What principles can you apply to be aware of problems early? How do you trade Agile Practioners vs Architectural Astronauts in a fast growing business? What are the technical debt trade-offs, what problems can you buy yourself out of? What problems will kill you if you don’t move now?
Software organizations that want to maximize the yield of Software Testing find that choosing the right testing strategy is hard, and most testing managers are ill-prepared for this. The organization has to learn how to plan testing efforts based on the characteristics of each project and the many ways the software product is to be used. This tutorial is intended for Software professionals who are likely to be responsible for defining the strategy and planning of the testing effort and managing it through its life cycle. These roles are usually Testing Managers or Project Managers.
Keeping Product Success Metrics in Check by Microsoft Product LeadProduct School
Main Takeaways:
- Parameters to check that can hamper the velocity of your team
- Factors that can influence the volume and/or adoption challenges
- Are you worried about defect inflow and unsure where to start?
- Key points that can impact CSAT/NPS scores, but generally ignored
- Areas to consider while struggling to control the cost of the product
How the relationship with a BUsiness Analyst is important in all phases of a project and how a Project Manager can use this relationship to be successful
Why Value Stream is key to Digital Product Delivery Mani Maun
Using Value Stream to visualize the end-to-end Flow of Digital Products and Services
Managing what flows through Value Stream can help bridge the gap Business and IT
Measurement of key metrics can enable data-driven decision making to improve value delivered to customers
UiPath Test Automation using UiPath Test Suite series, part 3DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 3. In this session, we will cover desktop automation along with UI automation.
Topics covered:
UI automation Introduction,
UI automation Sample
Desktop automation flow
Pradeep Chinnala, Senior Consultant Automation Developer @WonderBotz and UiPath MVP
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
Kubernetes & AI - Beauty and the Beast !?! @KCD Istanbul 2024Tobias Schneck
As AI technology is pushing into IT I was wondering myself, as an “infrastructure container kubernetes guy”, how get this fancy AI technology get managed from an infrastructure operational view? Is it possible to apply our lovely cloud native principals as well? What benefit’s both technologies could bring to each other?
Let me take this questions and provide you a short journey through existing deployment models and use cases for AI software. On practical examples, we discuss what cloud/on-premise strategy we may need for applying it to our own infrastructure to get it to work from an enterprise perspective. I want to give an overview about infrastructure requirements and technologies, what could be beneficial or limiting your AI use cases in an enterprise environment. An interactive Demo will give you some insides, what approaches I got already working for real.
Dev Dives: Train smarter, not harder – active learning and UiPath LLMs for do...UiPathCommunity
💥 Speed, accuracy, and scaling – discover the superpowers of GenAI in action with UiPath Document Understanding and Communications Mining™:
See how to accelerate model training and optimize model performance with active learning
Learn about the latest enhancements to out-of-the-box document processing – with little to no training required
Get an exclusive demo of the new family of UiPath LLMs – GenAI models specialized for processing different types of documents and messages
This is a hands-on session specifically designed for automation developers and AI enthusiasts seeking to enhance their knowledge in leveraging the latest intelligent document processing capabilities offered by UiPath.
Speakers:
👨🏫 Andras Palfi, Senior Product Manager, UiPath
👩🏫 Lenka Dulovicova, Product Program Manager, UiPath
Smart TV Buyer Insights Survey 2024 by 91mobiles.pdf91mobiles
91mobiles recently conducted a Smart TV Buyer Insights Survey in which we asked over 3,000 respondents about the TV they own, aspects they look at on a new TV, and their TV buying preferences.
Builder.ai Founder Sachin Dev Duggal's Strategic Approach to Create an Innova...Ramesh Iyer
In today's fast-changing business world, Companies that adapt and embrace new ideas often need help to keep up with the competition. However, fostering a culture of innovation takes much work. It takes vision, leadership and willingness to take risks in the right proportion. Sachin Dev Duggal, co-founder of Builder.ai, has perfected the art of this balance, creating a company culture where creativity and growth are nurtured at each stage.
Accelerate your Kubernetes clusters with Varnish CachingThijs Feryn
A presentation about the usage and availability of Varnish on Kubernetes. This talk explores the capabilities of Varnish caching and shows how to use the Varnish Helm chart to deploy it to Kubernetes.
This presentation was delivered at K8SUG Singapore. See https://feryn.eu/presentations/accelerate-your-kubernetes-clusters-with-varnish-caching-k8sug-singapore-28-2024 for more details.
LF Energy Webinar: Electrical Grid Modelling and Simulation Through PowSyBl -...DanBrown980551
Do you want to learn how to model and simulate an electrical network from scratch in under an hour?
Then welcome to this PowSyBl workshop, hosted by Rte, the French Transmission System Operator (TSO)!
During the webinar, you will discover the PowSyBl ecosystem as well as handle and study an electrical network through an interactive Python notebook.
PowSyBl is an open source project hosted by LF Energy, which offers a comprehensive set of features for electrical grid modelling and simulation. Among other advanced features, PowSyBl provides:
- A fully editable and extendable library for grid component modelling;
- Visualization tools to display your network;
- Grid simulation tools, such as power flows, security analyses (with or without remedial actions) and sensitivity analyses;
The framework is mostly written in Java, with a Python binding so that Python developers can access PowSyBl functionalities as well.
What you will learn during the webinar:
- For beginners: discover PowSyBl's functionalities through a quick general presentation and the notebook, without needing any expert coding skills;
- For advanced developers: master the skills to efficiently apply PowSyBl functionalities to your real-world scenarios.
State of ICS and IoT Cyber Threat Landscape Report 2024 previewPrayukth K V
The IoT and OT threat landscape report has been prepared by the Threat Research Team at Sectrio using data from Sectrio, cyber threat intelligence farming facilities spread across over 85 cities around the world. In addition, Sectrio also runs AI-based advanced threat and payload engagement facilities that serve as sinks to attract and engage sophisticated threat actors, and newer malware including new variants and latent threats that are at an earlier stage of development.
The latest edition of the OT/ICS and IoT security Threat Landscape Report 2024 also covers:
State of global ICS asset and network exposure
Sectoral targets and attacks as well as the cost of ransom
Global APT activity, AI usage, actor and tactic profiles, and implications
Rise in volumes of AI-powered cyberattacks
Major cyber events in 2024
Malware and malicious payload trends
Cyberattack types and targets
Vulnerability exploit attempts on CVEs
Attacks on counties – USA
Expansion of bot farms – how, where, and why
In-depth analysis of the cyber threat landscape across North America, South America, Europe, APAC, and the Middle East
Why are attacks on smart factories rising?
Cyber risk predictions
Axis of attacks – Europe
Systemic attacks in the Middle East
Download the full report from here:
https://sectrio.com/resources/ot-threat-landscape-reports/sectrio-releases-ot-ics-and-iot-security-threat-landscape-report-2024/
"Impact of front-end architecture on development cost", Viktor TurskyiFwdays
I have heard many times that architecture is not important for the front-end. Also, many times I have seen how developers implement features on the front-end just following the standard rules for a framework and think that this is enough to successfully launch the project, and then the project fails. How to prevent this and what approach to choose? I have launched dozens of complex projects and during the talk we will analyze which approaches have worked for me and which have not.
The Art of the Pitch: WordPress Relationships and SalesLaura Byrne
Clients don’t know what they don’t know. What web solutions are right for them? How does WordPress come into the picture? How do you make sure you understand scope and timeline? What do you do if sometime changes?
All these questions and more will be explored as we talk about matching clients’ needs with what your agency offers without pulling teeth or pulling your hair out. Practical tips, and strategies for successful relationship building that leads to closing the deal.
GraphRAG is All You need? LLM & Knowledge GraphGuy Korland
Guy Korland, CEO and Co-founder of FalkorDB, will review two articles on the integration of language models with knowledge graphs.
1. Unifying Large Language Models and Knowledge Graphs: A Roadmap.
https://arxiv.org/abs/2306.08302
2. Microsoft Research's GraphRAG paper and a review paper on various uses of knowledge graphs:
https://www.microsoft.com/en-us/research/blog/graphrag-unlocking-llm-discovery-on-narrative-private-data/
4. Get the basics right
SDLC and related areas are very critical for engineers
Technical success v/s business success
• Building technically great product is nice
• Making them commercially successful is the key
Standard frameworks like SDLC helps to do that
Evolved over three decades
Let us get our basics right!
6. Customer need
I want an Embedded device with 40$ price with device
performance as the key priority.
I would like to have a NOR flash with 20 MB space with
1 MB RAM.
User experience should be really excellent.
I can compromise on price for performance and user
experience. Quality is a non-negotiable item
8. How do I deliver?
Assuming customer challenges are understood, how to
deliver the product?
How do I ensure:
• Quality of end product is very good
• Customer perceives quality
• Control quality in my product development
• Make it repeatable and scalable
Often perceived as trust, brand, goodwill etc…
Challenge 2: How do I deliver a quality product?
10. Outsourcing blues
Ajay is an owner of small business, which has partnered with Arun’s
organization for re-branding
This includes our logo, caption, digital identity, website, branding
artifacts, social media etc
During vendor evaluation, Ajay was very happy with Arun’s
capability and awarded the project
As time progressed Ajay observed the following:
• Consistently not keeping up with time commitments
• Delays in responding to emails, phone-calls, no-response
• Quality issues (Broken defect fixes, implementation flaws etc…)
• Behavioral problems (“you didn’t tell this before!”, “It’s your
problem”, “Why should I fix this?”, “you check this first!”)
Ponder upon:
• What are the possibilities of problems with Arun?
• What experience Ajay is getting out of this activity?
• Would Ajay recommend Arun to his other business associates?
Key observations: Planning, Estimation, Team capability and skills
11. eCommerce project
One of the newly formed company came up with idea of selling niche
products online
They came up with an online portal which has excellent UI, e-commerce
and product listings
During product development and testing everything worked fine
Product was successfully launched on-time, initial customer reviews were
very positive
Traffic to the website suddenly stared picking up for which the site
couldn’t handle. This resulted in multiple transaction failures, delays and
incorrect shipments
This created a crisis in the organization
Ponder upon:
• What did the company do right?
• Where did they go wrong?
• What element did they miss during product requirement gathering?
Key observations: Non-functional requirement handling (scalability, security,
regulation compliance, high-availability etc..)
12. Bad news
Subbu was project manager, heading a complex system integration
project by combining many modules
He understood the importance of making all modules working
together and created a system integration plan
During initial days none of the modules worked well with each
other created a lot of issues
In senior management meetings he raised it as a ‘RISK’ item and
consistently raised alarm, which initially created some confusion
To address these issues an expert team was formed who figured
out all issues and solved the integration problem
Product was released on time, customer was happy
Ponder upon:
• What did Subbu do right?
• Confusion caused by Subbu initially was correct or wrong?
• What would be the side effects if Subbu didn’t raise issues on time?
Key observations: Risk raising and mitigation, Early handling, Being paranoid
13. Estimation challenges
Ram was team leader of device driver team. For a new project he
was asked to estimate the time required to complete it.
In the recent department change, Ram ended up getting
experienced engineers who were completely new to the device
driver domain.
Ram went with his initial estimation and started the project
Team members started feeling the heat when they actually started
implementing the project. With lesser or no previous knowledge
about device drivers, team was struggling
Customer reported quality issues in the deliverable. Both Ram and
team were frustrated for letting each other down
Ponder upon:
• What did Ram do incorrectly?
• How the team would have felt in the situation?
• If you were asked to take charge of project, what would you do?
Key observations: Team competency in estimation, Importance of estimation,
Team training and development, Customer expectations
14. Process for Process
Chaithra was a highly quality conscious project manager who strongly
believes in establishing strong processes. Starting from the scratch she
built quality system of her team, which delivered quality products
consistently to customers. Chaithra and her team was highly regarded as
‘champions-of-quality’.
However over a period of time, team started introducing too many new
processes and created a “checklist-and-approval” culture. For anything
and everything it became a world of excel sheets, check-lists, and
introducing new templates.
Senior technical and management members started enjoying this
“approval” based culture as they started enjoying the “pseudo power”
that came along with
Over a period of time customers started observing that Chaithra’s team is
slow in delivering products
Ponder upon:
• What was the problem with Chaithra?
• Process based approach followed by the team is correct or incorrect?
• Why the customer is feeling delay in product releases?
Key observations: Process should help team and customer, Keeping it simple,
Impact of process in team culture
19. Processes
Parameter Aravind Benchmark
Number of operation 400 / month 25 / month
Post infection cases 4 / 10000 patients 6 / 10000 patients
Time taken for operation 10 minutes 30 minutes
Key point: Make it as a standard, Make it repeatable and scalable
21. What is SDLC?
System Development Life Cycle
A conceptual model used in project management
Describes the stages involved, from an initial
feasibility study through maintenance
22. Why SDLC?
To have a successful system
To execute large projects
To understand customer requirements
To deliver on-time with high quality
Process framework
23. Failures
Schedule slippage
• No planning of development work (e.g. no milestones
defined)
• No control or review
Cost over-runs
• Poor understanding of cost and effort by both developer
and user
Does not solve user’s problem
• Deliverables to user not identified
• Poor understanding of user requirements
Poor quality of software
• Technical incompetence of developers
Poor maintainability
24. Success
Taking an “engineering” approach - To design,
develop (build, fabricate) an artefact that meets
specifications efficiently, cost-effectively and
ensuring quality
That comes from:
• Attempt to estimate cost/effort
• Plan and schedule work
• Involve user in defining requirements
• Identify stages in development
• Define clear milestones so that progress can be measured
• Schedule reviews both for control and quality
• Define deliverables
• Plan extensive testing
25. Process
Process consists of activities/steps to be carried out in
a particular order
Software process deals with both technical and
management issues
26. Process Types
Process - Manage the project
• Defines project planning and control
• Effort estimations made and schedule prepared
• Resources are provided
• Feedback taken for quality assurance
• Monitoring done.
Process – Change & Configuration management
• Resolving requests for changes
• Defining versions, their compositions
• Release control
Process - For managing processes
• Improving the processes based on new techniques, tools, etc.
• Standardizations and certifications (ISO, CMM)
27. Steps in process
Each step has a well-defined objective
Requires people with specific skills
Takes specific inputs and produces well-defined outputs
Step defines when it may begin (entry criteria) and
when it ends (exit criteria)
Uses specific techniques, tools, guidelines,
conventions.
28. Characteristics
Precisely defined
Predictable
Quality
Statistically controlled
Supports testing and maintainability
Facilitates early detection of and removal of defects
Facilitate monitoring and improvement
30. Initiation
Is this project worth doing?
Defining the project scope
Key deliverable is a
feasibility report
31. Concept Development
Feasibility Study (will it
work?)
Identify system interfaces.
Identify basic functional and
data requirements to satisfy
the business need.
Cost/Benefit Analysis (is the
cost really worth it?)
System Boundary (how far
should the project go?)
Risk Management (what will
happen if we don't do it?)
32. Planning
During this phase, a plan is
developed that documents
the approach to be used
It includes a discussion of
methods, tools, tasks,
resources, project
schedules, and user input.
Personnel assignments,
costs, project schedule,
and target dates are
established.
A Project Management
Plan is created
33. Feasibility study
Economic
• Cost / Benefit Analysis
Technical
• Hardware, Software,
People etc.
• Identify and estimate
to see if user needs
can be satisfied using
current techniques
and technologies.
Legal
Alternative
• More tan one way
would be possible
34. Requirement Analysis
Define the client’s
requirements
Further define and refine the
functional and data
requirements and document
them in the Requirements
Document.
Develop detailed data and
process models including
system inputs and outputs.
Develop the test and
evaluation requirements that
will be used to determine
acceptable system
performance.
35. Design
Define how the system will be
implemented
Generate a number of design
options based on technical,
operational, economic, scheduling
and tendering constraints
The client selects the best option
for their needs (assess feasibility
again)
Acquire the necessary hardware
and software
Design interfaces, databases,
networks as required
Specify integration requirements
and software requirements
(programs)
36. Implementation
Build and deliver the system
Build/modify databases and
networks as required
Build and test programs
• Acceptance testing, user
documentation, user
training, maintenance
procedures
Prepare users for new system
Finalize system and technical
documentation
Install the system
37. Integration & Testing
Subsystem integration,
system, security, and user
acceptance testing is
conducted.
The user, with those
responsible for quality
assurance, validates that
the functional
requirements, as defined
in the functional
requirements document,
are satisfied by the
developed or modified
system.
38. Deployment
This phase is initiated after the
system has been tested and
accepted by the user.
The system is installed to
support the intended business
functions.
System performance is
compared to performance
objectives established during
the planning phase.
Implementation includes user
notification, user training,
installation of hardware,
installation of software onto
production computers, and
integration of the system into
daily work processes.
39. Evaluation
Evaluation measures how
well the original ambitions
of the new system (i.e. the
logical design laid down
during the analysis phase)
have been achieved.
Evaluation doesn't really
serve to improve the
system that is being
evaluated; it serves to
improve the next system
you will work on
40. Evaluation
Typical evaluation criteria include:
• Speed
• Accuracy
• Quality of output
• Reliability
• Cost of operation
• Attractiveness
• Ease of use
• Robustness
• Capacity
• Compatibility with other systems
• Functionality (does it have the features it needs?)
• Security
• Flexibility (can it be upgraded, modified, adapted, tweaked,
configured?)
• Size, portability
43. Stay connected
About us: Emertxe is India’s one of the top IT finishing schools & self learning kits
provider. Our primary focus is on Embedded with diversification focus on Java,
Oracle and Android areas
Emertxe Information Technologies,
No-1, 9th Cross, 5th Main,
Jayamahal Extension,
Bangalore, Karnataka 560046
T: +91 80 6562 9666
E: training@emertxe.com
https://www.facebook.com/Emertxe https://twitter.com/EmertxeTweet https://www.slideshare.net/EmertxeSlides