KEMBAR78
Software Engineering Assignment | PDF | Software Development Process | Scrum (Software Development)
Scribd
Upload
18 views2 pages

Software Engineering Assignment

The document outlines various software development methodologies including Agile, Scrum, Spiral, and Waterfall models, each with distinct processes, advantages, and disadvantages. It also discusses the Capability Maturity Model (CMM) for measuring software process maturity, UML diagrams for visualizing systems, and requirement models for structured representation of system needs. Additionally, it covers software metrics, function point-based estimation techniques, and specific applications such as SRS for a university management website and DFD for a library management system.

Uploaded by

talkwithhexa420
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
18 views2 pages

Software Engineering Assignment

The document outlines various software development methodologies including Agile, Scrum, Spiral, and Waterfall models, each with distinct processes, advantages, and disadvantages. It also discusses the Capability Maturity Model (CMM) for measuring software process maturity, UML diagrams for visualizing systems, and requirement models for structured representation of system needs. Additionally, it covers software metrics, function point-based estimation techniques, and specific applications such as SRS for a university management website and DFD for a library management system.

Uploaded by

talkwithhexa420
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

Q1) Agile Process and Scrum Process Model

Agile Process:

Agile is a software development methodology focused on iterative delivery, customer collaboration,


and flexibility.
It values individuals and interactions, working software, customer collaboration, and responding to
change.

Scrum Process Model:

Scrum is an Agile framework that works in short iterations called sprints (2–4 weeks). Roles include
Product Owner, Scrum Master, and Development Team.
Artifacts include Product Backlog, Sprint Backlog, and Increment. Activities include Sprint Planning,
Daily Scrum, Sprint Execution, Sprint Review, and Retrospective.

Q2) Spiral Model


Definition: Spiral model is a risk-driven software development model introduced by Barry Boehm. It
combines iterative development with systematic risk analysis.

Phases: Planning, Risk Analysis, Engineering, and Evaluation. Each cycle of the spiral delivers an
incremental version of the product, addressing risks early.

Advantages: Handles changing requirements well, focuses on risk management.

Disadvantages: Costly, requires expertise in risk analysis.

Q3) Waterfall Model


Definition: The Waterfall Model is a linear SDLC model where each phase is completed before
moving to the next. Phases: Requirements, Design, Implementation, Testing, Deployment,
Maintenance.

Advantages: Simple, structured, good for fixed requirements.

Disadvantages: Inflexible, late feedback, poor fit for dynamic requirements.

Q4) Capability Maturity Model (CMM)


CMM is a framework to measure and improve software process maturity. Levels:

1. Initial – Ad-hoc processes.

2. Repeatable – Basic project management.

3. Defined – Standard organization-wide processes.

4. Managed – Measured and controlled processes.

5. Optimizing – Continuous improvement.


Q5) UML Diagrams
UML is a standardized modeling language for visualizing and documenting software systems.
Types:

Structural: Class, Object, Component, Deployment, Package diagrams.

Behavioral: Use Case, Sequence, Activity, State, Communication diagrams.

Q6) SRS for University Management Website


Includes purpose, scope, functional and non-functional requirements, user classes, constraints,
architecture diagram, and acceptance criteria. Functional modules for students, faculty, and admin.
Non-functional requirements: security, performance, scalability, usability.

Q7) DFD for Library Management System


Context diagram shows system interactions with members, librarians, suppliers. Level-1 DFD
breaks processes into Search & Catalog, Membership Mgmt, Issue/Return, Fine & Payments,
Reports. Level-2 DFD details Issue/Return steps.

Q8) Requirement Model


Requirement Model is the structured representation of functional and non-functional system needs.
Includes behavioral modeling (use case, sequence diagrams) and data modeling (ERD, DFD).
Steps: elicitation, analysis, specification, validation.

Q9) Software Metrics & Function Point-Based


Estimation
Software metrics measure process, product, and project attributes. Function Point Analysis
measures functionality delivered to users. Steps: Identify functions, assign weights, calculate UFP,
determine VAF, compute FP.

Q10) FP Estimation Technique in Detail


Steps: Identify functions (EI, EO, EQ, ILF, EIF), assign complexity weights, calculate UFP,
determine VAF from 14 general system characteristics, compute FP. Useful for early,
language-independent estimation.

You might also like