What is software development?
It’s the process of designing,
creating, testing, and
maintaining computer
programs and application
What is software engineering?
It’s applying systematic and
structured approach, utilizing
engineering principles to
software development to
create high-quality, reliable,
and maintainable software
What is a software process?
It’s sequence of activities to produce software
What are the four fundamental components of Software process?
1.Specification
2.Development
3.Validation
4.Evolution
What is specification
It’s defining functionalities and constraints (non-functional requirements) by Elicit the requirements, Model / formalize the requirements and validate the requirements
What is development
It’s designing and producing the software that meets the requirements like Functionalities and constraints,Architecture (organize the components),Databases,Interfaces etc
What is Validation
ensuring that the developed software meets the
requirements(.Does the software meet the requirements?
* Is the software reliable?
* Is the software efficient?
* Is the software secure?)
What is evolution
changing the software to reflect changes required by the customer or
market requirements
Name the two types of Software processes
1.Plan-driven development
2.Agile development
Define plan-driven development
It’s a software process where all activities are planned in advance and progress is measured against the plan
Define agile development
It’s a software process where planning is always incremental and easy to change according to the customer requirements
Define software process models
These are simplified representation of a software processes also known as software development life cycle model.They are high level and generic descriptions of a software process and different software process models represent different software processes applicable to diverse contexts.
Name different types of software process models
1.Waterfall model
2.Incremental model
Define waterfall model
- It’s a linear Software Process Model
- Processes are divided into different stages
- Each stage must be finished before starting the next one (cascading
shape) - One should move to the next phase only when its preceding stage
is completed and perfected. - It’s one of the oldest models
-It’s a plan-driven process
What are the advantages/Pros of waterfall model?
- Useful in cases where the
rigidity of the process is a plus
. Embedded systems: software must interface with the hardware systems
What are the disadvantages/cons of waterfall model?
- It’s not flexible – cannot
accommodate for the evolving needs from different stakeholders - No feed back between stages
Define incremental model
It’s a successive version model which builds on an initial version and successive versions(or iterations) are built with new refined features.
What are the advantages/Cons of incremental model
- It’s flexible
- Client can be actively involved to provide feedback
- Correct mistakes
- Change requirements
- Delivery and deployment early without all functionalities
What are the disadvantages/cons of incremental model?
- Too flexible?
* Hard to manage among large teams - Limited Overall View
* Design decisions are difficult to establish - Systems can degrade with new increments
- Continuous maintenance
overhead
- Continuous maintenance
Is incremental model Agile or plan-driven?
- It can be agile (iterations planned incrementally) or plan-driven (iterations
planned in advance) - Usually both
- Early iterations planned,
with possibility to adapt in
later iteration
- Early iterations planned,
Define agile manifestos and principles
1.Individuals & Interactions > Processes & Tools
2.Working Software > Comprehensive Documentation
3.Customer Collaboration > Contract Negotiation
4.Reacting to Change > Following a Plan
What does Individuals & Interactions > Processes & Tools as an agile manifesto & principles entail
- Build projects around motivated individuals
- Give them support they need
- Trust them to get the job done
- Face-to-face conversation is the most effective method of
conveying information - Applies to inter- and intra-team communication
What does Working Software > Comprehensive Documentation as an agile manifesto & principles entail
- Working software should be the primary measure of progress
* Iterate on prototypes
that deliver Minimum
Viable Products (MVPs) - Top priority is customer satisfaction
* Achieved through early
and continuous delivery
of valuable software - Simplicity is essential
What does Customer Collaboration > Contract Negotiation as an agile manifesto & principles entail
- Developers must work together with other team members
- Daily interaction throughout the project
- Deliver working software frequently every:
* Month, Week, Day
* Preference is given to
shorter timescales! - Project cadence should be sustainable
* Stakeholders should
maintain a constant pace
-
Software Engineering and Software Process37
-
Requirements (Part I and part 2)30
-
Version control systems, Git and GitHub and databases39
-
Databases and ORM23
-
JUnit, Build Systems, and CI/CD30
-
Framework-Driven Application Development & RESTful Services17
-
Software Quality Assurance Verification and Validation (Part I)29
-
Software Quality Assurance Verification and Validation (Part II)29
-
Architectural Design, Modelling, and Styles15
-
Web Basics (Part I)12
