Scribd
Upload
11 views14 pages

Requirments (IN UML)

The document discusses requirements engineering and the Unified Modeling Language (UML). It states that requirements engineering is the practice of collecting requirements from users and stakeholders. It identifies different types of requirements like business, user, and software functional and non-functional requirements. The document also provides an overview of UML, describing it as a standardized modeling language used in software engineering to create visual models. It discusses UML's history and how it combines techniques from different modeling approaches.

Uploaded by

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

Requirments (IN UML)

The document discusses requirements engineering and the Unified Modeling Language (UML). It states that requirements engineering is the practice of collecting requirements from users and stakeholders. It identifies different types of requirements like business, user, and software functional and non-functional requirements. The document also provides an overview of UML, describing it as a standardized modeling language used in software engineering to create visual models. It discusses UML's history and how it combines techniques from different modeling approaches.

Uploaded by

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

Requirements

© PKD, Asst. Professor, CIT Dept @ UPES | Sept 2013 |


© PKD, Asst. Professor, CIT Dept @ UPES | Sept 2013 |
© PKD, Asst. Professor, CIT Dept @ UPES | Sept 2013 |
Requirement Engineering

• It is the practice of collecting the


requirements of a system from users,
customers and other stakeholders.

© PKD, Asst. Professor, CIT Dept @ UPES | Sept 2013 |


Types of Requirements
• Business Requirements
• User Requirements
• Software Requirements
– Functional Requirement
– Non Functional Requirement

© PKD, Asst. Professor, CIT Dept @ UPES | Sept 2013 |


© PKD, Asst. Professor, CIT Dept @ UPES | Sept 2013 |
© PKD, Asst. Professor, CIT Dept @ UPES | Sept 2013 |
© PKD, Asst. Professor, CIT Dept @ UPES | Sept 2013 |
What is UML?
• Unified Modeling Language (UML) is a standardized, general-
purpose modeling language in the field of software engineering.
• UML includes a set of graphic notation techniques to create visual
models of object-oriented software-intensive systems
• It was developed by Grady Booch, Ivar Jacobson and James
Rumbaugh at Rational Software in the 1990s.

• It was adopted by the Object Management Group (OMG) in 1997, and


has been managed by this organization ever since.
• In 2000 the Unified Modeling Language was accepted by
the International Organization for Standardization (ISO) as industry
standard for modeling software-intensive systems.

© PKD, Asst. Professor, CIT Dept @ UPES | Sept 2013 |


• Unified Modeling Language (UML) combines
techniques from data modeling (entity
relationship diagrams), business modeling (work
flows), object modeling, and component
modeling.
• It can be used with all processes, throughout
the software development life cycle, and across
different implementation technologies.

© PKD, Asst. Professor, CIT Dept @ UPES | Sept 2013 |


• The Unified Modeling Language (UML) offers a
standard way to visualize a system's architectural
blueprints, including elements such as:
 activities
 actors
 business processes
 database schemas
 (logical) components
 algorithms
 reusable software components.

© PKD, Asst. Professor, CIT Dept @ UPES | Sept 2013 |


Advantages of UML
 Captures business processes
 Enhance communication and ensures the
right communication
 Capability to capture the logical software
architecture independent of the
implementation language
 Manages the complexity
 Enables reuse of design

© PKD, Asst. Professor, CIT Dept @ UPES | Sept 2013 |


OOAD with UML
Building a Building software
house

Design and OOAD


layout

Blueprint UML

Actual Coding
construction

© PKD, Asst. Professor, CIT Dept @ UPES | Sept 2013 |


A conceptual model of the UML:
To understand the UML, you need to form a conceptual
model of the language, and this requires learning
three major elements:
 The UML’s basic building blocks.
 The rules that dictate how these building blocks put
together.
 Some mechanisms that apply throughout the UML.
© PKD, Asst. Professor, CIT Dept @ UPES | Sept 2013 |

You might also like